SID Fundamentals
SID Fundamentals
SID Fundamentals
Fundamentals
Information Framework Foundation - Part 1
Day 9 Introduction to Information Framework
In this training you will
Exercise learn about
-Information Framework uses
SID
Information Framework Foundation - Part 2
Foundation
Modelling Patterns in Framework
Day 10
Information Framework Extension Guidelines
Information Framework - Conformance
Information Framework Expert - Part 1
Day 11 Review - Information Framework
Exercise - Information Framework uses
Information Framework Expert - Part 2
Day 12 Review - Modelling Patterns in Framework
SID Exercise - Applying Modelling Patterns
Expert Information Framework Expert - Part 3
Day 13 Guidelines for Extending the Information Framework
Exercise - Information Framework Extension
Information Framework Expert - Part 4
Day 14 Transforming the Information Framework
Operational Data Store and Master Data Management
Acknowledgement, Disclaim & Copyright
Reducing time to
market /introduction Reducing the cost
of new of integration
technologies
Reduce Facilitate
management time new/existing
and cost development
Support multiple
implementations
from
a single model
The Information Framework
Five common questions that help explain what the framework is:
Customer ABE
Customer
Customer
Customer
Account
Account
Contact
And grows by including
closely related entities
Customer
Credit
Profile
Customer
Customer ABE Mapping with Telconet Entities
info_persona info_persona_forma_contacto
Customer ABE
info_persona_forma_contacto
Customer
Customer
Customer Account
Account
Contact
Customer
Credit
Profile
Structure of a domain
All ABEs that completely define a key management area are grouped together.
Customer
Customer Roles Customer Order Customer Problem Customer Bill Customer Bill Inquiry
Customer Interaction Customer Statistic Applied Customer Billing Rate Customer Bill Collection Customer SLA
An ABE may be further decomposed into any number of lower levels ABEs.
An ABE at any level can be developed from the top down or the bottom up.
Market/Sales domain decomposition – Top-down Approach
Market / Sales
Market Segment Marketing Campaign Competitor
Customer
Product
Service
Resource
Business Partner
Enterprise
Sample Unified Modeling Language (UML) Class Diagram
Information Framework Uses
Developing APIs
Mapping to the
Process Framework
Product Catalog Lifecycle – Sample
Using SID for Requirements
Exercise – Scoping a Project
▪ Telconet is building Application Platform with the following capabilities:
- Provides a standardized solution for rapidly adding partners’ products to an existing Catalog
- Provides mechanism for placing a Product Order with all of the necessary order parameters.
- The Product Order is created based on a product offering that is defined in a catalog. The product offering
identifies the product or set of products that are available to a customer, and includes characteristics such as
pricing, product options and market.
- Provides mechanism for retrieval of the representation of a product and its subscribers.
- Provides a standardized mechanism to book an appointment with all the necessary appointment
characteristics
▪ As an Architect, you are tasked with providing a solution by identifying the scope of this project with the
corresponding L1 ABEs that will be present in the Platform and what requirements these ABEs map to.
Modeling
patterns
Review of Unified
Modeling
Language (UML)
The scenario
GeorgeG has found his way to the Home Shoppers’ Network web
site. He is identified as a business type of shopper. Shoppers of
this type are provided with a business rewards account number so
that they can earn points on their purchases.
George goes about filling up his shopping cart with items he plans
to purchase. He may choose to empty his cart and not purchase
anything. Home Shoppers’ Network hopes he will checkout his
purchases and pay for them.
We’ll look at how to model a shopper and shopping cart with UML.
Business entities
EntitySpecification/Entity
Composite/Atomic
Entity/EntityRole
Business Interaction
The
CharacteristicSpecification/CharacteristicValue
Patterns
The scenario
An individual named George G has decided to order wireless service, IPTV, and
Broadband Internet from a single provider at one time.
The IPTV service is a bundle that consists of a set-top box, wireless router, basic
TV service, Internet connectivity, and video on demand (VoD). Once installed
VoD can be accessed by the customer, who can choose from a variety of videos
categories, such as comedy, drama, sports, and so forth. The request for service
can include VoD in standard or high-definition format as well as whether to
watch the video now or at a specific date and time.
EntitySpecification/Entity pattern
Entity Specification
An instance of an entity
Basic TV
Set-top Box
Wireless Router
Broadband Internet
VoD George G’s IPTV Service Basic TV
George G’s IPTV Service Set-top Box
George G’s Wireless Router
George G’s IPTV Service Broadband Internet
George G’s IPTV Service VoD
Other applications of EntitySpecification/Entity pattern
Composite/Atomic pattern
Example of Composite/Atomic
Also includes:
• Recording in the Telconet cloud for up to 7 days
Composite/Atomic in UML
0,1 *
0,1 *
Composite/Atomic enabling bundled offering
George G – Customer
George G George G - Employee
Party Role as an ABE example
George G (playing
the role of a
customer)
George G’s
American Express Account
George G
(playing the role George G’s
of a customer) American Express Account
BusinessInteraction example -Part 2
This pattern is often used with the EntitySpecification/Entity and Composite/Atomic patterns
to enable near complete freedom (dynamic extensibility) in defining any type of entity
(subclass) and its attributes together with various ways to group the entities.
CharacteristicSpecification example
The VoD has a category and set of titles associated to it, as well as the
format (hi-definition or standard) and an optional date and time at
which the customer wants to start viewing the video.
There are two options that could be used.
Using the “Blade” concept
Using CharacteristicSpecification/CharacteristicValue
VoD
Category - Comedy
Category - Drama
Category - Sports
Title - The Queen
Title - Alien
Category Title - Sound of Music
Title Format - Hi-definition
Format Format - Standard
StartDateTime
CharacteristicValue example
Category
Title
Format
StartDateTime
Category - Drama
Title – Sound of Music
Format – Hi-def
GG’s VoD StartDateTime – 12AM
Category - Comedy
Category - Drama
Category - Sports
Title - The Queen
Title - Alien
Title - Sound of Music
Format - Hi-definition
Format - Standard
SID & Modeling Pattern Usage
SID & Modeling Pattern Usage - New Services
SID & Modeling Pattern Usage - Capabilities
SID & Modeling Pattern Usage – ABEs used
Which parts of the framework were used?
Product, Service, Resource usage
Us ageSpecification
nam e : String
des cription : String
validFor : Tim ePeriod
1
lifecycleStatus : Integer
SpecifiesUsage
1
Res ourceUs ageSpec ServiceUs ageSpec 0..n ProductUs ageSpec
1 1 1..n
0..n ServiceUsageSpecParticipatesIn
0..n
SpecifiesServiceUsage
Us age
0..n
us ageDate : Date
us ageStatus : Integer SpecifiesProductUsage
SpecifiesResourceUsage
0..n
0..n Res ourceU... 1 ServiceUs age 0..n ProductUs age
1..n
ProductBundleUsageCom prisedOf
0..n
ServiceUsageParticipatesIn
0..n 0..1
ResourceUsageParticipatesIn 0..n ProductCom ponentUs age ProductBundleUs age
Exercise – Applying SID Modeling Patterns
▪ Telconet operates in 4 countries and has plans to expand to many more countries. Because of this there are a
number of different address formats that must be supported. You are designing for maintaining a central
repository of addresses.
▪ The stakeholders have expressed the desire to define different formats for addresses and then to use these as
“templates” to collect address information from various sources, including customers. As they do not know all the
countries in which Telconet will operate, they also want the flexibility to be able to dynamically define the
attributes associated with new types of addresses.
▪ They also want to be able to define addresses that are made up of components, such as a street address that is
made up of house number, street name, and street suffix, like St., Ave, and so forth.
▪ One more requirement that arose at the end of one session was the need for the same address to represent
different types, such as a customer address, an address for network elements, an installation address and so forth.
▪ Your Activity
▪ As an Architect, you are tasked with providing a solution by identifying what Information Framework modeling
patterns would you use to model these requirements? Your solution should also include the justification for
using the pattern.
Modeling patterns
Extending Information Framework
Common Market / Sales
Customer
Product
Domains
Service
cannot be
Resource
added
Business Partner
Enterprise
Blade Concept
ResidentialCustAcctCreditApp OrganizationCustAcctCreditApp
Extension guidelines
Keep in mind that if you decide to add a new Level 1 ABE there should be a corresponding
first level core process in the Business Process Framework. If not, you may have to add the
core process that manages the lifecycle of the ABE to your Process Framework
implementation. Similar additions may be needed in your implementation of the
Application and Integration frameworks.
Alarms TroubleTicket
alarmS alarmI alarmS alarmD alarmL …
ource D everity escripti ocation TTID alarmI TTStatu TTPrior TTAssig …
on D s ity nedTo
TicketedAlarms
alarmS alarmI alarmS alarmD alarmL …
ource D everity escripti ocation
on
Technique 1 - Adding Attributes to an Existing Entity
Alarms
Used when entity to be extended is stable and there are a large number
of entities to be extended
Technique 2 - Adding Attributes to an Existing Entity
TicketedAlarms
alarmID
alarmSource
alarmTicketID
alarmTicketStatus
Technique 3 - Adding Attributes to an Existing Entity
Alarms
AlarmsExtendedBy
TicketExtensions
NetworkAlarms SystemAlarms
AlarmID
AlarmSource
AlarmType
AlarmSeverity
AlarmsGenerateTickets
Adding New Entities – Scenario 2
Alarms
TicketedAlarms
TicketedAlarms
AlarmsGenerateTickets
Tickets
Sometimes following the first association naming guideline results in a duplicate name.
If this occurs, then the naming convention shown here should be used.
Attribute naming guidelines
Card
cardCompatibilityResults : String
daughterCardInstallStatus : Integer
daughterCardOperatingStatus : Integer
daughterCardRequirements : Integer
isConfigurablePhysically : Boolean
isMotherBoard : Boolean
isUniquePhysical : Boolean
maxDataWidth : Integer
slotLayout : String
slotsRequired : Integer = 1
uniqueRequirementsPhysical : String
hardwareVersion : String
getAllPhysicalPorts()
General Modeling Guidelines
▪ Your Activity
❑ As Information Architect, identify the ABEs that need to be modified to meet this requirement.
Exercise – Extending the Framework – Modeling Requirements Part 2
▪ Service Level Specification shows the overall Service Level Specification model.
▪ The prescribedAction attribute defines the details of what happens when a ServiceLevelObjective is not
met.
▪ Telconet wants to have capability to dynamically offer such discounts for different services and to be able
to change the discounts offered dynamically.
• Identify what are the other ABEs that will be required to be associated or
modified. Note that the relationship would be used to indicate what type of
adjustment would be made to a customer’s bill/invoice for an unmet
ServiceLevelObjective.
Exercise – Extending the Framework – Modeling Requirements Part 3
▪ Now that you have identified to establish a relationship to some portion of the framework’s
▪ There are some facts that Telconet would like to keep about the relationship.
▪ The attributes include a sequenceOfApplication, to define the order in which adjustments are applied.
▪ If an adjustment has already been applied to a product offering for a customer the next adjustment in
▪ sequence is used.
▪ Another attribute is the total number of times that an adjustment has been applied for an offering.
▪ Telconet wishes to keep a monthly summary that represents the total number of each applied
adjustment.
Exercise – Extending the Framework – Modeling Requirements Part 3
Activity by participants:
Note: The association of this adjustment with the ProductPrice entity and the
CustomerBill entity is out of scope for this exercise.
Class Discussion – Implementing the
Information Framework
Implementation Planning
• Awareness seminars/webinars
• In depth training for those involved in or using information/data models
• Mapping current models to the Information Framework
• Extending where necessary
Mapping to the Framework
• The SID will be used as the basis for a Telconet’s information model as part
of the new application development
• Putting a mapping team in place is an important step
• There are a number of techniques that can be used, including spreadsheets
and mapping tools
• Some examples will be shown, followed by some considerations for
choosing a technique
The Mapping Team
Composed of:
– Information modelers and subject matter experts (if applicable)
– Knowledge of the framework and organization’s current information/data
model
Forming mapping teams:
– Think about domains to do this
Workshop environment:
– White boards
– Current models available
Expected results:
– Domain/ABE (to lowest level) coverage
– Used as input for subsequent mapping to entities/attributes
SID ABE Mapping
Using the Mappings
Options:
– Commercial tool
– Desktop tool, such as Word or Excel
Desktop/laptop tool may be the tool of choice:
– Commercial tool
• Not everyone may have access to it
• Expertise in the tool may be required
• SID may require importing into tool
– Desktop/laptop tool
• Most desktops/laptops have this software already installed
• Most users have knowledge of these tools
• Simpler to develop mappings
Entity/Attribute Mapping Methods -Tools
▪ In the Telconet’s Sales Process ERD, map the Product Catalog related entities to SID L1 ABEs.
▪ Hint: Start by identifying only the Product Catalog related entities in your process & list them. Look at the SID
model related to Product catalog & create a mapping table.
Information Framework Conformance
Module 5:
Conformance to
the framework
1
Information Framework Conformance
Initial scope
defined at
Level 1 ABE
Assessment Product
Offering
Problem
performed at
lowest level ABE Verify Proper
Isolate
Product Customer
Offering
Product Use
Problem
Entities
PerformCustomer
Report
Product
Product -
RelatedCatalog
Problem Diagno
Diagnos
Track & Customer
Identify
Product
Price
Manage
Offering Provide
Close
Product
Problem
Customer
Problem
Offering
Report
Price Rules
Notification
Information Framework Conformance
Information Framework R17.0: Adoption Conformance Scoring Guidelines
SID Component Weighted Scoring Calculation
Lowest Level ABE (ABE) Equivalent – 1 score point
Core Entity (CE) Equivalent – 2 score points
Core Entity Required Attribute (CR) % equivalent * 2 [Must support min 50% of Required Attributes]
Dependent Entity (DE) % equivalent * 1.5
Dependent Entities – Required Attributes (DR) % equivalent * 1.5
Core Entity – Optional Attributes (CO) % equivalent * 1.2
Dependent Entity – Optional Attributes (DO) % equivalent * 0.8
Adoption Conformance Score Graduation