A CustomerFacingService defines the properties of a particular related CustomerFacingServiceSpec (i.e. know-how) that represents a realization of a Product within an organization's infrastructure; This is in direct contrast to ResourceFacingServices, which support the network/infrastructure facing part of the service (i.e. the technical solution). For example, a VPN is an example of a CustomerFacingService, while the sub-services that perform different types of routing between network devices making up the VPN are examples of ResourceFacingServices. <br/><br/><br/><br/>CustomerFacingServices are directly related to Products as well as to ResourceFacingServices. ResourceFacingServices are indirectly related to Products through the relationship between Product and CustomerFacingServices. This enforces the relationship to Products while keeping Services that are not directly realized by Products (i.e., ResourceFacingServices) separated from Products.<br/>
Attributes
Associations To
Associations From
Tagged Values
Advanced
Other Links
Attribute
Scope
Type
status
Public
Integer
Notes:
This is an enumerated integer that defines the status of this particular CustomerFacingService. Values include:<br/><br/><br/><br/> 0: Operational and billable<br/><br/> 1: Degraded but billable<br/><br/> 2: In Violation and billable<br/><br/> 3: Operational but not billable<br/><br/> 4: In Test and not billable<br/><br/> 5: Being Deployed and not billable<br/><br/> 6: Failed<br/><br/><br/><br/>Value 0 means that this CustomerFacingService is acting per specification, and is fully billable.<br/><br/><br/><br/>Value 1 means that this CustomerFacingService is operational, but is currently in a degraded state. However, it has not violated any contractual specification and is fully billable.<br/><br/><br/><br/>Value 2 means that this CustomerFacingService is operational, but is currently in violation of its associated contractual specification(s). Whether it is billable or not is determined by its associated Policy for handling service violations.<br/><br/><br/><br/>Value 3 means that this CustomerFacingService is currently operational, but has not been enabled for this particular customer yet and is therefore not billable for this customer.<br/><br/><br/><br/>Value 4 means that this CustomerFacingService is currently being tested, and is not yet ready to be enabled for this particular customer. Consequently, it is therefore not billable for this customer.<br/><br/><br/><br/>Value 5 means that this CustomerFacingService is currently being deployed, and therefore has not been enabled for this particular customer yet. Consequently, it is therefore not billable for this customer.<br/><br/><br/><br/>Value 6 means that this CustomerFacingService has currently failed. The set of actions that should be taken, as well as whether this service can still be billed or not, are determined by its associated Policy for handling service violations.<br/>
