CustomerFacingService

CustomerFacingService : public abstract class

Created:	3/12/2005 12:00:00 AM
Modified:	11/22/2006 7:30:46 AM

Project:
Author:	AutoMagic KB LLC
Version:	6.2
Phase:	SID
Status:	Approved
Complexity:	Medium
Advanced:
UUID:	{B32EFA6A-15AA-4f7b-9D69-A8A62CD81AF4}
Appears In:	ManagedEntity Generalization Tree, Service Generalization Tree, Figure Pr.02 - Product, Service, Resource Domain Relationships, Product-Service-Resource Relationships, Product-ServicePackage-ServiceBundle-QoS, CFS and RFS Summary, NetworkForwardingService Diagram, ProductSpec-ServiceSpec-ResourceSpec, QoS Entities Summary, QoS-Package-Bundle, Service Class Diagram, Service-Location Summary, Service-PhysicalResource Interaction, Service-Resource-Product Summary, ServiceBundle and ServicePackage, ServiceBundle-QoS, ServiceSpec-PhysicalSpec Interaction, Simple Service-Spec Diagram, Simplified Service Class Diagram, Fig 4SO-06 - High Level Product-Service-Resource, Fig 4SO-08 - ServiceSpec, Fig 4SO-09, Fig 4SO-10 - ServiceSpec subclasses, Fig 4SO-12 - CFS and RFS, Fig 4SO-20 - ServiceRoles, Fig 4SO-27 - ServicePackage, Fig 4SO-30 - ServicePackage and ServiceBundle, Fig 4SO-41 - CFS and RFS Biz Model, Fig 4SO-42 - CFS-RFS Atomic-Composite Biz Models, Fig 4SO-43 - ServiceSpec Biz Model, Fig 4SO-47 - ServiceRole Biz Model, Fig 4Q-11 - ServicePackage, Service Trouble Info, Resource-Service-PartyRole, Fig 5LR-08 - Service concept, Fig 5LR-09 - Product - Resource - Service, Fig 5LR-57 - ProductSpec-ResourceSpec Interaction, Resource Trouble Info, AMKB-BusinessInteraction, Fig 39 - Service Overview, Fig 40 - Contracts and Services, Fig 41 - Contracts and Products-Resources-Services, Service Inventory Layout

Copyright TM Forum 2005 This is the base class for defining CustomerFacingServices in the Service model. A CustomerFacingService is an abstraction that defines the characteristics and behavior of a particular Service as seen by the Customer or other appropriate PartyRole. This means that this PartyRole purchases, leases, uses and/or is otherwise directly aware of this type of Service. This is in direct contrast to ResourceFacingServices, which support CustomerFacingServices but are NOT seen or purchased directly by the Customer. 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.

Attributes
Associations To
Associations From
Other Links

Attribute

Details

public Integer
cfsStatus

Notes:

This is an enumerated integer that defines the status of this particular CustomerFacingService. Values include: 0: Operational and billable 1: Degraded but billable 2: In Violation and billable 3: Operational but not billable 4: In Test and not billable 5: Being Deployed and not billable 6: Failed Value 0 means that this CustomerFacingService is acting per specification, and is fully billable. 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. 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. 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. 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. 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. 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.

Element	Source Role	Target Role	Details
CustomerFacingServiceSpec Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of CustomerFacingServices that can be defined from a particular CustomerFacingServiceSpecification. Bundled sets of CustomerFacingServices can be built by combining multiple CustomerFacingServiceSpecifications. This enables the CustomerFacingServiceSpecification to define the invariant attributes, methods, relationships, and constraints of a CustomerFacingService, and the CustomerFacingService to define different variations of the Service that are all built off of the same CustomerFacingServiceSpecification.<br/></p>
CustomerFacingServiceComposite Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of CustomerFacingServices that form a part of a CustomerFacingServiceProduct, such as a ServicePackage or a stand-alone CustomerFacingService such as VoIP.<br/></p>
Product Class	Name:	Name:

Element	Source Role	Target Role	Details
CustomerFacingServiceRole Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of CustomerFacing ServiceRoles that a particular CustomerFacingService has. This enables the CustomerFacingService to be defined abstractly using Roles instead of specific Services.<br/></p>
ResourceFacingService Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This defines the set of ResourceFacingServices that are required for a particular CustomerFacingService to operate correctly.<br/></p><p><br/></p><p>Note that the cardinality of the CFServiceRequiresRFServices is 0..n on the CustomerFacingService (aggregate) side and 1..n on the ResourceFacingService (component) side. This is because a ResourceFacingService can exist without being bound into a CustomerFacingService (e.g., in testing the network), but a CustomerFacingService requires at least one ResourceFacingService to function.<br/></p>

Object	Type	Connection	Notes
CustomerFacingServiceRole	Class	Weak	Copyright TM Forum 2005 This aggregation defines the set of CustomerFacing ServiceRoles that a particular CustomerFacingService has. This enables the CustomerFacingService to be defined abstractly using Roles instead of specific Services.
ResourceFacingService	Class	Weak	Copyright TM Forum 2005 This defines the set of ResourceFacingServices that are required for a particular CustomerFacingService to operate correctly. Note that the cardinality of the CFServiceRequiresRFServices is 0..n on the CustomerFacingService (aggregate) side and 1..n on the ResourceFacingService (component) side. This is because a ResourceFacingService can exist without being bound into a CustomerFacingService (e.g., in testing the network), but a CustomerFacingService requires at least one ResourceFacingService to function.
CustomerFacingServiceAtomic	Class	Tree
CustomerFacingServiceSpec	Class	Weak	Copyright TM Forum 2005 This aggregation defines the set of CustomerFacingServices that can be defined from a particular CustomerFacingServiceSpecification. Bundled sets of CustomerFacingServices can be built by combining multiple CustomerFacingServiceSpecifications. This enables the CustomerFacingServiceSpecification to define the invariant attributes, methods, relationships, and constraints of a CustomerFacingService, and the CustomerFacingService to define different variations of the Service that are all built off of the same CustomerFacingServiceSpecification.
CustomerFacingServiceComposite	Class	Weak	Copyright TM Forum 2005 This aggregation defines the set of CustomerFacingServices that form a part of a CustomerFacingServiceProduct, such as a ServicePackage or a stand-alone CustomerFacingService such as VoIP.
CustomerFacingServiceComposite	Class	Tree
Service	Class	Tree
Product	Class	Weak