ResourceFacingService

: Public abstract <<TMF_BusinessEntity>> Business Entity

Created:	1/10/2022 12:00:38 PM
Modified:	4/15/2022 10:26:00 AM

Project:
Author:	Giu Platania
Version:	22.0
Phase:	prop
Status:	Implemented
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{6A83122F-3F44-4ab1-8F47-731C93E061A6}
Appears In:	Figure SO.12 - Modeling Stand-Alone and Aggregate Services, Figure SO.06 - Basic Service Model – A Starting Point, Figure SO.07 - Representing BGP as a LogicalResource, Figure SO.20 - The Concept of ServiceRoles, Figure SO.08 - Service Specifications and other Domains, Figure SO.09 - VPNService – VPNServiceSpecification Example , Figure SO.03 - Subclassing ServiceSpecification (OLD SO.10), Figure SO.29 - ServiceBundles and ServiceBundleSpecifications, Figure SO.30 - Summary Relationships Between ServicePackage and ServiceBundle, Figure Res.02 - Interaction between ProductSpecification and ResourceSpecification (OLD LR.65), Figure LR.06 - Concept of CustomerFacingServices vs. ResourceFacingServices, Figure LR.07 - Relationship between Product, Service and Resource, Figure LR.30 - Protocol Interactions, Figure PF.02 - Service, Resource, and Performance, Resource-Service-PartyRole, NOT USEFUL = LR.07 Figure PR.34 - Relationship Between Product, Service and Resource, Figure Pr.02a - Product, Service, Resource Domain Relationships, Figure PF.02 - Service, Resource, and Performance

This is an abstract base class for ResourceFacingServices. A ResourceFacingService is an abstraction that defines the characteristics of a particular Service which support the network/infrastructure facing part of the service. ResourceFacingServices are “internal” Services (i.e. technical solutions) that are required to support a CustomerFacingService. The Customer obtains CustomerFacingServices via Products, and is not aware of the ResourceFacingServices which support the CustomerFacingService(s) that is being obtained directly by the Customer via a Product. For example, a VPN is an example of a CustomerFacingService. This particular type of VPN may require BGP to support it. Customers don’t purchase BGP, and hopefully aren’t even aware that BGP is running. Therefore, BGP is an example of a ResourceFacingService. CustomerFacingServices are directly related to Products as well as to ResourceFacingServices. ResourceFacingServices are indirectly related to Products through the relationship between Product and Resource. This enforces the relationship to Products while keeping Services that are not directly obtainable via Products (i.e., ResourceFacingServices) separated from Products.

Attributes
Associations To
Associations From
Tagged Values
Advanced
Other Links

Attribute

Public Integer
rfsStatus

Details:

Alias:
Initial:
Stereotype:	<<required>>
Ordered:
Range:
Transient:	False
Derived:	False
IsID:	False

Notes:

This is an enumerated integer that defines the status of this particular ResourceFacingService. Values include: 0: Operational and supporting CFS 1: Degraded but supporting CFS 2: In Violation and not supporting CFS 3: Operational but not yet supporting a CFS 4: Being Tested 5: Being Deployed 6: Failed Value 0 means that this ResourceFacingService is acting per specification, and is also currently supporting one or more CustomerFacingServices. Value 1 means that this ResourceFacingService is operational, but is currently in a degraded state. This degraded state indicates congestion or some other problem, but has not yet comprimised the operation of its associated CustomerFacingServices. Value 2 means that this ResourceFacingService is operational, but is currently in violation of its associated specification(s). This in turn means that its associated CustomerFacingServices are violating their contractual specification(s) unless automatic fail-over has been enabled. Value 3 means that this ResourceFacingService is acting per specification, but is not yet currently supporting one or more CustomerFacingServices. Value 4 means that this ResourceFacingService is currently being tested, and is not yet ready to support a CustomerFacingService. Value 5 means that this ResourceFacingService is currently being deployed, and is not yet ready to support a CustomerFacingService. Value 6 means that this ResourceFacingService 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
«TMF_BusinessEntity» ServiceCandidate Business Entity	Name: resourceFacingService	Name: serviceCandidate
Details:
«TMF_BusinessEntity» Resource Business Entity	Name: _resourceFacingService	Name: _resource
Details:
«TMF_BusinessEntity» ResourceFacingServiceRole Business Entity	Name: _resourceFacingService	Name: _resourceFacingServiceRole
Details:
«TMF_ABE» Resource Facing Service ABE ABE «TMF_ABEIsComposedByEntity»	Name:	Name:
Details:
«TMF_BusinessEntity» Protocol Business Entity	Name: _resourceFacingService2	Name: _protocol
Details:

Element	Source Role	Target Role
«TMF_BusinessEntity» CustomerFacingService Business Entity	Name: _customerFacingService	Name: _resourceFacingService
Details:
«TMF_BusinessEntity» LogicalResource Business Entity	Name: logicalResource	Name: resourceFacingService
Details:
«TMF_BusinessEntity» ResourceFacingServiceSpec Business Entity	Name: _resourceFacingServiceSpec	Name: _resourceFacingService
Details:
«TMF_BusinessEntity» ResourceFacingServiceComposite Business Entity	Name: _resourceFacingServiceComposite	Name: _resourceFacingService
Details:

Tag	Value
IsCoreEntity	False
Details: Values: true,false Default: False
rsa_guid	_3E3F0EC000E93D5091AC0353
Details:

Property	Value
isActive:	0
isFinalSpecialization:	0

Object	Type	Connection	Direction	Notes
«TMF_BusinessEntity» ResourceFacingServiceAtomic	Business Entity	Generalization	From
«TMF_BusinessEntity» ResourceFacingServiceComposite	Business Entity	Generalization	From
«TMF_BusinessEntity» Protocol	Business Entity	Class	To
«TMF_BusinessEntity» Service	Business Entity	Generalization	To