Sid integration view
Download as PPTX, PDF1 like454 views
1) The document discusses using the TMF SID framework and extending it for the telecom industry to enable integration and sharing of information across systems. 2) It describes the SID entity model including roles, relationships, and views to represent objects, relationships between entities, and their operations. 3) Examples are provided of how business processes, services, resources, and customers would map and share information using the SID framework.
![Definition: Association Behavior of an Object
Role
Role is an ABE which has several specializations such as PartyRole, ResourceRole (among others)
Note that a PartyRole can be defined independently of any possible involvement with a Product, a Service or a Resource (same remark applies as
well to ResourceRole).
Involment Role
Involvement Role classes represent the association between two classes. These are association classes that were ‘promoted’ to become normal
classes. ProductInvolvementRole, for example, describes the association between Product and other entities.
Up to release 9.5, the TMF Information Framework Model captures the concept of InvolvementRole for a given Product through the
ProductInvolvementRole abstract artifact (up to release 9.5, there is no equivalent for ServiceInvolvementRole and ResourceInvolvementRole;
these entities are proposed to be added in the present document – see below);
[5] defines a ProductInvolvementRole as “a role a Party or Resource plays in the relationship with a Product (such as user, subscriber…), the model
implementation also includes CustomerAccount which is missing from the definition”
In other words, it characterizes the involvement of a Party, CustomerAccount or Resource w.r.t. a Product
Entity Specification
The Specification ABE contains entities that define the shared characteristics of both types of defined entities. This enables multiple instances to
be derived from a single specification entity. In this derivation, each instance will use the characteristics defined in its associated specification.
Entities in this ABE focus on adherence to standards, distinguishing features of a Service, dependencies (both physical and logical, as well as on
other services), quality, and cost. In general, entities in this ABE enable Services to be bound to Products and run using Resources.
Network services are one example of Services that can be built. Additional examples include installation, maintenance, monitoring, and content
authentication, authorization, accounting, and auditing functions.
This is an abstract base class that represents the key features of this Specification. For example, bandwidth is characteristic of many different types
of services; if bandwidth is important (e.g., from the point-of-view of a Customer obtaining this Service via a Product) then bandwidth would be a
ServiceSpecCharacteristic for that particular Service.
CharacteristicValue object is used to define a set of attributes, each of which can be assigned to a corresponding set of attributes in a
SpecCharacteristic object. The values of the attributes in the SpecCharacteristicValue object describe the values of the attributes that a
corresponding SpecCharacteristic object can take on.
Characterisic view](https://image.slidesharecdn.com/sidintegrationview-200604163053/85/Sid-integration-view-4-320.jpg)
Sid integration view
- 1. Integration View Using Tmforum SID and its Extension in Telecom Industry (Service and Resource)
- 2. Executive Summary • Shared data and information framework – an overview including entity type with example and its Use • SID Entity and Business and function Interaction View • Business process specific information model introduction and information shared across enterprise • Integration View using SID – API-fication approach and Telco specific API • Use of SID XSD in Application Integration Framework View • order and Inventory Attribute view using SID
- 3. Object Representation :Relationship View and Operational View Entity Role Characteristic View Involvement Role Relationship Entity Strategy and plan Performance and problem Specification & Configuration Usage and Test Entity operation view Entity: Domain Entity Relationship view Entity :ABE Entity:Market,Sales,product,customer,service,resource,supplier,partner and Enterprise Has Relationship Object Abstract class representation Operation specific object customization as per operation need Operation Specific object Characteristic value and character representation as per operation need Operation Specific object Role and involvement Role as per operation need
- 4. Definition: Association Behavior of an Object Role Role is an ABE which has several specializations such as PartyRole, ResourceRole (among others) Note that a PartyRole can be defined independently of any possible involvement with a Product, a Service or a Resource (same remark applies as well to ResourceRole). Involment Role Involvement Role classes represent the association between two classes. These are association classes that were ‘promoted’ to become normal classes. ProductInvolvementRole, for example, describes the association between Product and other entities. Up to release 9.5, the TMF Information Framework Model captures the concept of InvolvementRole for a given Product through the ProductInvolvementRole abstract artifact (up to release 9.5, there is no equivalent for ServiceInvolvementRole and ResourceInvolvementRole; these entities are proposed to be added in the present document – see below); [5] defines a ProductInvolvementRole as “a role a Party or Resource plays in the relationship with a Product (such as user, subscriber…), the model implementation also includes CustomerAccount which is missing from the definition” In other words, it characterizes the involvement of a Party, CustomerAccount or Resource w.r.t. a Product Entity Specification The Specification ABE contains entities that define the shared characteristics of both types of defined entities. This enables multiple instances to be derived from a single specification entity. In this derivation, each instance will use the characteristics defined in its associated specification. Entities in this ABE focus on adherence to standards, distinguishing features of a Service, dependencies (both physical and logical, as well as on other services), quality, and cost. In general, entities in this ABE enable Services to be bound to Products and run using Resources. Network services are one example of Services that can be built. Additional examples include installation, maintenance, monitoring, and content authentication, authorization, accounting, and auditing functions. This is an abstract base class that represents the key features of this Specification. For example, bandwidth is characteristic of many different types of services; if bandwidth is important (e.g., from the point-of-view of a Customer obtaining this Service via a Product) then bandwidth would be a ServiceSpecCharacteristic for that particular Service. CharacteristicValue object is used to define a set of attributes, each of which can be assigned to a corresponding set of attributes in a SpecCharacteristic object. The values of the attributes in the SpecCharacteristicValue object describe the values of the attributes that a corresponding SpecCharacteristic object can take on. Characterisic view
- 5. Customer Product CFS RFS and Physical Logical Resource Relationship with Example Customer 1 Platinum pkg with high bw protection feature enabled in resource level Customer 2 Silver pkg with protection feature enabled in resource level Customer 3 Basic pkg with no protection feature enabled in resource level
- 6. Business Specific Information Model :Reference Information Model Identify Primary and Secondary Process intersection Identify Function within the process intersection Identify Managed and Management Entity specific information model Managed and management Extension for Organization specific Information Model Organization Specific Function Organization Specific Process
- 7. Business Process Mapping with SID: Service ABE Service ABE Primary Vertical Business Process Framework Process Grouping Layer Layer Primary L2 process Secondary L2 process Service Capability delivery Service configuration and activation Service Problem Management Service Quality Management Service guiding and mediation SM &Operation support and readiness Service Capability delivery SM &Operation support and readiness Resource Provisioning SM &Operation support and readiness Problem Handling Service Quality Management Resource Trouble Management Product offer and protfolio planning Service Capability delivery Service Development and Retirement Resource strategy and planning Service Quality Management Service Problem Management Service Management and Operation Support and readiness Resource Problem Management Resource Data Collection & Processing Service Quality Management Service Development and Retirement Service Quality Management Service Test Service Management and operation - Fulfillment Service Configuration and Activation Business process(eTOM) Service Development&Management -Product life cycle managamnet Service Development and retirementService Specification Service Management and operation - Billing Service Guiding & MediationService Usage Service Configuration Service Management and operation -Fulfillment Service Configuration Activation Service Strategy & Plan Service Development&Management -Strategy and commit Service strategy and Planning Service Problem Service Management and operation -Assurance Service Problem Management Service Performance Service Management and operation - Assurance
- 8. Business Process Mapping with SID: Resource ABE Resource ABE Primary Vertical Business Process Framework Process Grouping Layer Layer Primary L2 process Secondary L2 process Resource Management and Operation Support and Readiness Resource Provisioning Resource Capability Delivery Resource Trouble Management Resource Performance Management Resource Capability Delivery Resource Management and Operation Support and Readiness Resource Provisioning Resource Management and Operation support and rediness Resource Development and Retirement Resource Data collection and processing Resource Management and Operation support and Readiness Resource Performance Management Service Problem Management Billing and Collection Management Service Guding and Mediation Resource Development and Retirement Service strategy and planning Resource Capability Delivery Resource Management and Operation Support and Readiness Resource Trouble Management Resource Performance Management Resource Development and Retirement Resource Management and Operation Support and Readiness Resource Configuration Resource Management and operation - Fulfillment Resource Provisioning Business process(eTOM) Resource Specification Resource Development&Management - Product life cycle managamnet Resource Development and Retirement Resource Data collection and processing Resource Test Resource Management and operation - Fulfillment Resource Provisioning Resource Topology Resource Development&Management - Infrastructure LifeCycle Management Resource Capability Delivery Resource Performance Resource Management and operation - Assurance Resource Performance Management Resource Strategy & Plan Resource Development&Management - Strategy and commit Resource strategy and Planning Resource Trouble Resource Management and operation - Assurance Resource Trouble Management Resource usage Resource Management and operation - Billing Resource Data Collection & Processing
- 9. TAM and CRUD View: Service Entity ABE Primary function Secondary Function Primary function Secondary Function Service ABE Service catalog Management Service Inventory Management CRUD CRU Service Quality Management RU Service Performance Management RU Service Order Management Service Inventory Mnagment CRUD CRUD Resource Inventory Management RUD Resource Domain Management CRD Service Problem Management Service Quality Management CRUD RUD Fault Management RU Service catalog Management Resource Lifecyle Management CRUD RUD Resource catalog Management RUD Service Test Management Service Inventory Management CRUD R Resource Test Management R Service Performance Management Resource Performance Mamagment CRUD R Fault Management RU Service Quality Management RU Service Inventory Management Resource Inventory Management CRUD RUD Service Usage Usage Management R CRUD VIEW Service Performance Service Test Service Problem Service Strategy & Plan TAM Service Specification Service Configuration
- 10. TAM and CRUD View: Resource Entity ABE Primary function Secondary Function Primary function Secondary Function Resource ABE Resource LifeCycle Management Resource Inventory Management CRUD CRUD Wrokforce Management R Location Management R Network Number invntory Management CRUD Resource Domain Management RU Resource process Management R Resource Inventory Management CRUD RU Service Inventory Management RU Workforce management RU Resource Doamin management RU Resource Inventory Management CRUD U Fault management R Workforce management U Service Performance Management U Service Quality Management U Service Problem Management U Location Management U Resource Performance Management CRUD RU Resource Inventory Management U Resource Performance Management U Service Performance Management U Service Quality Management U Service Problem Management U Workforce management U Location Management U Usage Management Resource Inventory Management CRUD R Resource LifeCycle Management Resource inventory Management CRUD RUD Resource Order Mnagment RUD Resource process Management UD Resource Test Management Resource Domain Management CRUD RU Resource Test Resource Inventoty Management Location Management CRUD UD Resource Domain Management R TAM Resource Specification Resource Topology CRUD VIEW Resource Strategy & Plan Resource usage Resource Performance Resource Configuration Resource Performance Management Fault Management Resource Trouble Resource Order Managment
- 11. SID ABE Mapping with Telecom Application Resource Inventory Management Service Allocation and reservation Resource Performance Management Resource Fault Management Resource Planning tool Resource Activation Management N/W Physical and logical inventory N/W Sync management (Discovery and reconciliation) N/W Topology view Service Catalog Management Service Inventory Management Service Order Management Order Feasibility Check Order Instance configuration and validation Order Decomposition Product and Service catalog synchronization Service Quality Management Service Performance Management Service Activation Management Service Specification Service Configuration Service ABE:CFS and RFS :Resource Service Specification: Service package and bundle verification Service Strategy and plan Resource Strategy and plan Resource Specification Resource ABE: Resource Order Resource Configuration Resource ABE: Resource Topology Service ABE: Service Usage Resource ABE: Physical, Logical resource Resource Usage ABE
- 12. API-fication View Entity Role Characteristic View Involvement Role Relationship Entity Operation API /CRUD Exposed Resource Consumed Resource Strategy and Plan Planning Request/Response Planning System Product/Service/Resource inventory Management System Specification Catalog Request/Response Catalog Management system Order Management System and Service/Resource Inventory Management system Configuration Order and Activation/Deactivation Request/response Order Management System Resource Inventory, Resource Inventory and activation system Usage Usage Management Request/Response inventory management system Reporting Tool Test Test Management Request/Response Entity Test System Entity(s) are participating in testing procedure Problem and Trouble Trouble Ticket Request/Response TT System Assurance System available in Enterprise
- 13. SID within an Application Integration Framework SID XSD applicable for industry specify solution SID XSD applicable for organization specify solution SID XSD applicable for application specify solution Organization specific requirement Application specific requirement
- 14. API Approach API Life Cycle Business Operational Technical Define Early Customer Feedback Develop Publish Support Retire Rapid Prototyping Classification & Security Enablement Notifications Of Changes Standardize Product Customer Centric Design Managing Infrastructure Consistent Development Eco-System Expansion Policy Enforcement & Analytics Governance Ease Of Migration Monitoring & Distributed Support Model Evolution API Transformation API Security API Management API Administration API Governance API Development API Services & Management API Services API Gateway Resource WEB Apps Cloud Services Mobile Apps Legacy Application IoT Services Partner Application Supplier Application Customer API Life-Cycle Management
- 15. API Platform API-Gateway Roles Orchestration Message Security Authorization API-Centric Architecture for a TELCO TELCO B/OSS End Points Proxy End Point API-Proxy Roles Transport Security Monitoring Firewall . . . Application 1 Application 2 Application n IoT Simple & Secure EnterpriseAPICatalog Authorize Validate Throttle Route Transform Mediate Monitoring Logging Reporting Auditing Analytic REST,SOAP,FTP,Oauth,Kerberos,JMS,SAML,etc. API Gateway Cluster API Management Portal
- 16. API:Order Attributes :Service and ResourceOrder Who is the system for placing order and when What is the quantity What is the order for (instance) • Id • State • Priority • Category • Order Date • Related Party • Number of instance • Action • State • Place • Dependency Order Quantity • Start Date • Requested Start Date • Completion Date • Requested Completion Date • Expected Completion Date • Note • Linked Order System Attributes for an Order Service Instance Resource
- 17. API:Inventory Attributes :ServiceInstance Specification View Characteristic View ref Relationship view ref • Name • value • Id • Description • Type/category • State • isServiceBundle • isServicePkg • Service Pkg Description (isServicePkg == true) Entity Instance view derived from specification Instance characteristic ref • Service Bundle Description (isServiceBundle == true) • Order Date • Note • Linked Service instance (isServicePkg == false) • Lined Resource instance (isServiceBundle ==false) Instance Service • Type • Instance Description • Id Instance characteristic ref
- 18. API:Inventory Attributes :ResourceInstance TIP Resource view Characteristic View ref Relationship view ref • Name • value • TIP Resource Object Entity Instance view derived from specification Instance characteristic ref Instance Resource • Type • Instance Description • Id Instance Relationship ref TIP Resource View provides standard MTOSI interface for resource MTOSI standard shall be followed by the