Shared Information Data (SID) is TM Forum's guidelines for abstract data model. https://www.tmforum.org/information-framework-sid/

1. TMF – SID Overview
Ayub Qureshi
Dec 15, 2015

2. 2

3. 3

4. 4
TM Forum’s Frameworx
SID (Shared Information and data Model) is a component of TM Forum’s
Frameworx. Now called as Information Framework.
Applications
Framework
(Telecom Applications
Map - TAM)
Information
Framework
(Shared Information
and data Model - SID)
Integration
Framework
(Technology Neutral
Architecture - TNA)
Business
Process
Framework
(eTOM)

5. 5
SID Modeling
• An information model independent of platforms, languages &
protocols
• Abstraction of real world scenario
• Logical view of “things of interest” (entities such as customer,
product, resources etc.)
• Also data model & represents physical implementation of SID’s
logical view of “things of interest” or Objects
• Federated model – use many industry models like CIM, DEN, MTMN,
MTOSI etc.
• Holistic model – links distributed & diversified info into common
structure - Hence, it is common information model
• Not a home grown model
• Conforms to Technology Neutral Architecture (TNA)

6. 6
 Business Entity – represents something of interest to business; a tangible
thing (e.g. Customer, Device), an active thing ( e.g. Customer Order), or a
conceptual thing (e.g. Customer Account)
 Attribute – a fact that describes business entity
 Relationship – an association of business interest between two business
entities or itself
 Aggregate Business Entity (ABE) – a well-defined set of information and
operations that characterize a high cohesive, loosely coupled set of
business entities
 Domain - a collection of ABEs associated with a specific management
area e.g. service, resource etc.
SID Definitions
Domain ABE Business
Entity
Attribute
Relationship
Behavior

7. 7
SID Domains and eTOM Process Mapping
Market/Sales
Product
Customer
Service
Resource
Supplier/Partner
Enterprise
Common
Business
SID Domains
Customers
Supplier/Partner
Strategy, Infrastructure & Product Operations
Enterprise Management
Shareholder Employee Other Stakeholder
Operation
Supports &
Readiness
Fulfillment Assurance BillingStrategy
& Commit
Infrastructure
Lifecycle
Product
Lifecycle
Customer Management
Service Management & Operations
Resource Management & Operations
Marketing & Offer Management
Service Development &
management
Resource Development &
Management
Supplier/Partner Management
Supply Chain Development &
Management
eTOM Level 1 Process Grouping

8. 8
SID – eTOM Mapping - Level 0
OperationsStrategy, Infrastructure &
Product
Service
Resource
Supplier/Partner
Common Business EntitiesEnterprise
Market/Sales Product Customer

9. 9
Example of Mapping eTOM to SID
Product ABEs eTOM
Process
Groupings
Primary eTOM
Level 2 Processes
Secondary eTOM Level 2
Processes
Strategic Product Portfolio Plan
Is concerned with the plans of the product
portfolio, which product offerings to make
available to each market segment and the
plans to development and deploy product
offerings, as well as retirement of products
M&OM – SC Product & offer Portfolio
Strategy, Policy, &
Planning
Market Strategy & Policy
Product & Offer Business Planning &
Commitment
Product Development & Retirement
Product Specification
Defines the functionality and characteristics
of product offerings made available to the
market
M&OM – PLM Product Development &
Retirement
Order Handling
Service Configuration & Activation
Product Offering
Represents tangible and intangible goods and
services made available for a certain price to
the market in the form of product catalogs.
This ABE is also responsible for targeting
market segments based on the appropriate
market strategy
M&OM – PLM Product Development &
Retirement
Marketing Fulfillment Response
Marketing Communications & Promotion
Selling
Product
Represents an instance of a product offering
subscribed to by a party, such as a customer,
the place where the product is in use, as
well as configuration characteristics, such as
assigned telephone numbers and internet
addresses. The Product ABE also tracks the
services and/or resources through which the
product is realized
CRM – F Order Handling Selling
Service Configuration & Activation
Problem Handling
Customer QoS/SLA Management
Service Problem Management
Service Quality Analysis. Action, & Reporting
Service & Specific Instance Rating
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• Both SID and eTOM are Technology Neutral Architecture
• The SID level 1 ABE is mapped to eTOM level 2 processes

10. 10
ProductComponent
ProductSpecCharacteristicValue
(f rom Product Specif ication ABE)
ProductSpecCharacteristic
(f rom Product Specif ication ABE)
ProductOffering
(from Product Offering ABE)
ProductBundle
ProductCharacteristic
productCharacteristicValue
validFor
0..1
0..n
0..1
0..n
ProdSpecCharValueInstantiatedAsProductCharacteristic
0..1
0..n
0..1
0..n
ProdSpecCharDescribesProdCharacteristic
Product
name : String
description
productStatus
productSerialNumber
validFor : TimePeriod
1
0..n
1
0..n
ProdOfferDescribes
0..1
0..n
0..1
0..n
ProductBundleComprisedOf
0..n 0..n0..n
ProductReferences
0..n
0..n 10..n 1ProdCharDefinesTheConfigurationOf
Place
(fromEntities)
0..n
0..n
0..n
0..n
ProductLocatedVia
Enterprise Management
Strategy, Infrastructure & Product Operations
Fulfillment Assurance BillingProduct
Lifecycle
Management
Infrastructure
Lifecycle
Management
Operations
Support &
Readiness
Customer Relationship Management
Service Management & Operations
Resource Management & Operations
Supplier/Partner Relationship Management
Strategy &
Commit
Marketing & Offer Management
Service Development & Management
Resource Development & Management
Supply Chain Development & Management
(Application, Computing and Network)(Application, Computing and Network)
Customer
Enterprise Effectiveness
Management
Knowledge & Research
Management
Enterprise Risk
Management
Strategic & Enterprise
Planning
Financial & Asset
Management
Stakeholder & External
Relations Management
Human Resources
Management
Corporate
Knowledge
Base
NGOSS
Knowledge
Base
Shared
SID
eTOM
TNA
NGOSS Lifecycle Knowledge Base
A Repository of Reusable
Best PracticesTAM

11. 11
Market/Sales
Product
Customer
Management
Service
Management
Resource
Management
Supplier /
Partner
Enterprise
Management
Campaign
Management
Product /
Service
Product Life
Cycle
Channel Sales
Management
Customer
Management
Order
Management
Customer
QOS/SLA
Management
Customer Service /
Account Problem
Resolution
Fraud
Management
Custom Billing
Management
Invoice / Receivable
management
Service
Design /
Assign
Service
Configuration
Management
Service
Performance
Management
Service
Quality
Management
Service
Problem
Management
Revenue
Assurance
Management
Service Rating /
Discount
management
Resource
Inventory
Management
Workforce
Management
Resource
Design /
Assign
Resource
Provisioning /
Configuration
Resource
Performance
Management
Correlation &
Root Cause
Analysis
Resource
Testing
Management
Resource
Planning
Resource
Logistics
Resource
Status
Monitoring
Resource
Activation
Resource
Problem
Management
Billing Data
Mediation
Partner
Management
Supply
Chain
Management
Wholesale
Billing
Asset
Management
Financial
Management
HR
Management
Security
Management
Knowledge
Management
- TAM is mapped to eTOM & SID domains. A TAM domain is decomposed into application area.
- Each application area is mapped to SID level 1 ABE and eTOM level 2 process
TAM - Telecom Application Map

12. 12
SID Framework – Level 1 ABEs
Marketing/Sales
Product
Customer
Service
Resource
Enterprise Common Business
DOMAINS
ABEs
Service
Service Test
Resource Test
Supplier/Partner
S/P Bill Inquiry
S/P Order
S/P OrderS/P Problem
S/P Performance S/P PlanSupplier/Partner S/P Interaction S/P Bill
S/P Product S/P SLA S/P Statistic S/P Payment
Resource Strategy & Plan
Party Policy
Business InteractionAgreementLocation
Resource Trouble
Resource Performance
Resource Usage
Resource Topology
Resource
Configuration
Resource
Resource Specification
Service Trouble
Service PerformanceService Applications
Service UsageService Configuration
Service Strategy & Plan
Service Specification
Customer Bill CollectionApplied Customer Billing Rate
Customer Bill InquiryCustomer BillCustomer SLA
Customer ProblemCustomer Order
Customer Statistics
Customer
Customer Interaction
Product Specification
Product
Product Offering Product Usage Statistics
Strategic Product Portfolio Plans
Product Performance
Market Segment Competitor Sales Statistic Sales Channel
Marketing Strategy & Plan Marketing Campaign Contact/Lead/Prospect

13. 13
SID Framework – Level 2 ABEs
Service
CustomerFacingService
ResourceFacingfService
ABELevel2
Service
DOMAIN
ABELevel1
Service
Service TestService Trouble
Service PerformanceService Applications
Service UsageService Configuration
Service Strategy & Plan
Service Specification

14. 14
Thing
Attribute1: Type1
Attribute2: Type2
Operation1
Operation2
Name of Entity
Behavior
Attributes
AnotherThing
Attribute3: TypeA
Attribute4: TypeB
Operation3
Operation4
Relationship/Association
* *0:1
Composition
Aggregation
Inheritance
Association
Relationship:
SID – Modeling Techniques
Object-Oriented Analysis and Design
UML

15. 15
SID – Modeling Patterns
 Abstract Superclass
 Inheritance & Specialization
 Entity Specification – separates the invariant properties of an object
from its changeable properties
 Composite – provides a common structure for stand-alone and
aggregate objects
 Role Entity – uses role objects to extend an object
 Self Relationship Pattern
Entity1
SimpleEntity CompoundEntity
Composite Pattern
Vehicle
Mini VanSedanTruck
Engine
Break
Vendor:
Model:
Year:
Specialization Pattern
turnRight()
turnLeft()

16. 16
Firewall
Role
Router
Role
Switch
Role
Device
Role
Physical
Device
Role Entity
HasDeviceRole
Cisco
6506
Cisco
7120
Juniper
SA-5040
Physical
Device Spec
Firewall
Spec
Entity Specification
Router
Spec
Switch
Spec
0:n 0:1
0:10:n
 Entity Specification
 separates the invariant properties of an object from its
changeable properties
 for example, a data spec sheet for equipments
 Role Entity
 uses role objects to describe an object’s roles and
responsibilities
SID – Modeling Patterns - cntd

17. 17
Resource Domain – Level 1 ABEs
Resource
Resource Domain
Resource Management
Resource Configuration
Resource Usage
Resource Specification
Resource Topology
Resource Performance
Resource Strategy &
Planning
Resource Trouble Resource Test

18. 18
Resource
Resource Domain
Physical Resource
Physical Resource Role
Logical Resource
Logical Resource Role
Compound Resource
Compound Resource Role
Resource Specification
Physical Resource
Specification
Physical Resource Role
Specification
Logical Resource Specification
Logical Resource Role
Specification
Compound Resource
Specification
Compound Resource Role
Specification
Resource Domain – Level 2 ABEs

19. 19
Product
Resource
Physical
Resource
Logical
Resource
0..n0..n
PResourceSupportLResource
ProductHasResource
0..n
Service
Customer
Facing
Service
Resource
Facing
Service
1..n0..n
CFServiceRequiresRFService
0..n
0..n
ServiceUseResource
1..n
 Physical Resource – Router, Device, Chassis, Card, Port, Cable
 Logical Resource – Service, Software, Protocol
Physical & Logical Resource

20. 20
Physical
Resource
Power
Supply
Slot
0..1
0..n
Physical Device Hardware
Equipment
Card
Router
Role
Switch
Role
Device
Role
Equipment
Holder
Auxiliary
Component
0..n
ChassisRack
System
Card
Network
Card
Memory
Card
0..1
0..10..n
ConsistOf
EquipmentIn
Holder
Firewall
Role
ContainsHardware
CardOnCard
Physical Resource – Router Example

21. 21
Resource Port
Resource
Port
Device
Interface
1..n
Termination Point
Logical
Device
Physical Port
Pipe
1..n
1
1
Physical DomainLogical Domain
2..n
1
• Resource Port – serve as bridge to enable the
interaction between Physical and Logical Domains

22. 22
Logical
Resource
Operating
System
Network
Address
0..1
0..n Logical
Device
Logical
Device
Composite
Logical
Device
Atomic
Managed
Transmission
Software Protocol Device
Interface
Logical Resource

23. 23
RootEntity
ManagedEntity
Entity
commonName
description
objectID
Service
Role
Management
Info
Specification Characteristic Capacity Collection
Management
Domain
Policy
Resource
Physical
Resource
Logical
Resource
Root Entity of SID

24. 24
ManagedEntity
Entity
Management
Method
Management
Info
Fault
Info
Resource
State Info
Accounting
Info
Configuration
Info Performance
Info
Service
State
Info
Resource
Statistics
Info
RMON
Method
TL1
Method
SNMP
Method
CLI
Method
CMIP
Method
0..n
SuppotMgmtMethods
1..n 1 1
DescribedByMgmtInfo
Management Info and Method

25. 25
Product, Service & Resource Associations
ServiceUtilizes
CustomerFacingService
Product
0..n0..n 0..n
ProductReferences
0..n
0..1
0..n
0..1
0..n
ProductHasCustomerFacingServices
ResourceFacingService
0..n1..n 0..n1..n
CFServiceRequiresRFServices
ServiceSpecification
0..n0..n 0..n
InvolvedServiceSpecs
0..n
Service
1 0..n1 0..n
SpecifiesService
ProductOffering
1 0..n1 0..n
ProdOfferDescribes
CustomerFacing
ServiceSpec
1
0..n
1
0..n
SpecifiesCustomerFacingService
PhysicalResourceSpec
ProductSpecification
0..n0..n 0..n0..n
ProdSpecReferences
1
0..n
1
0..n
ProdSpecMadeAvailableAs
0..n
0..n
0..n
0..n
ProductSpecDefinesCFSSpecs
0..n
0..n
0..n
0..nProductSpecDefinesPRSpecs
Resource
0..n
0..n
0..n
0..n
ResourceSpecification0..n
0..n
0..n
0..n
InvolvedResourceSpecs
1 0..n1 0..n
SpecifiesResource
ResourceFacing
ServiceSpec
1 0..n1 0..n
SpecifiesResourceFacingService
0..n 1..n0..n 1..n
RequiresResourceFacingServiceSpec
1
1..n
1
1..n
RFServiceSpecHasResourceSpecs

26. 26
Domain ABE
Common Business Party
Location
Interaction
Agreement
Policy
Customer Customer
Customer Order
Product Product
Product Offer
Service Service
Service Configuration
Resource Resource
Resource Configuration
Resource Trouble
Some Aggregate Business Entities (ABEs)

27. 27
A Few Definitions
Domain A collection of Aggregate Business Entities (ABE) associated with a specific
management area. Domains that make up the SID framework are consistent
with eTOM level 0 concepts
Aggregate Business Entity
(ABE)
A well-defined set of information and operations that characterize a highly
cohesive, loosely coupled set of business entities
Business Entity Something of interested to the business which could be tangible (e.g.
Customer) or intangible (e.g. Customer Account)
Attribute A fact that describes a Business Entity
Relationship An association between 2 Business Entities or between a Business Entity and
itself (recursive)
Object A specific entity or concept that has meaning in an application domain
Class A definition of a set of potential objects that have the same data, behavior,
and relationships
Attribute A data value defined in a class and held within an object that has meaning
within the application domain
Behavior A service defined in a class and provided by an object.
Method The implementation of a behavior in an object-oriented programming
language
Association A "peer-to-peer" relationship between classes.
Aggregation A "whole/part" relationship between classes.
Inheritance A "generalization/specialization" relationship between classes.
Cardinality/
Multiplicity
The minimum and maximum number of objects that participate in an
association or aggregation. The common (interesting) ones are 0..*, 0..1,
1..*, and 1..1

28. 28
e-TOM enhanced Telecommunication Operating
Model
SID Shared Information and data Model
TAM Telecom Applications Map
ABE Aggregated Business Entity
NGOSS Next Generation Operating Systems
FCAPS Fulfillment, Configuration, Accounting,
Performance & Security
TNA Technology Neutral Architecture
Links for TM Forum https://www.tmforum.org
Links for SID https://www.tmforum.org/information-
framework-sid/
Glossary