1. 1
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P
TMW – 9 Nov 2005NGO SS1
Real SIDImplementions-Part 2:
Using the SIDforbroadband provisioning-interfacing delivery
platforms to CRMand to GBE network
Marco Daccò – Telecom Italia, OSS
Giuseppe Covino, Bruno Foresi, Giuseppe Ricucci – Telecom Italia
Lab, OSS
2. 2
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P
TMW – 9 Nov 2005NGO SS1
Outline
Telecom Italia business scenario
TI OSS Platform
Data issues and requirement for higher layer management platform (CRM)
Efoundation Project
lesson learnt
Data issues and requirements for lower layer OSS platform (GBE network)
networkmodel
lesson learnt
What’s next & expectations
3. 3
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P
TMW – 9 Nov 2005NGO SS1
1MB
Time
Ricaricabile
Free
4MB
GPRS
HSDPA
Videocall
Complex Services
Time to Market
Process Innovation
TelecomItalia Business Scenario - OSS
4. 4
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P
TMW – 9 Nov 2005NGO SS1
Telecom Italia OSS Platform
Order to Bill
-CRM -
Sales Force, Customer Care,
Retail Order Entry, Commercial TT
(Siebel)
CRM -
Retail Billing Post-paid
(Kenan Arbor)
- SISTINA -
Wholesale Billing
(Intec interconnect)
- PITAGORA -
Wholesale Order Entry
(Custom)
CRM -
Retail Billing Pre-paid
(Infranet Portal)
- Web Portals -
Multimedia Content
Rosso Alice
(Broadvision)
WholeSale
Order to Delivery
- DAI -
Outsourced
Work Force
(Custom)
- WFM -
Insourced Work
Force
(Telcordia Force)
- GEM -
Material
Mgmt
(SAP)
Resource & Workforce Management
- TTM -
Technical
Trouble
Ticketing
(Remedy)
-DIAGNOSY
S-
Service
Assurance
(Motive/Cus
tom)
Network Inventory
- CIC -
Network
Assurance
(Micromus
e)
- PERSEO -
Performanc
e Mgmt
(ADC
Metrica)
- USAGE -
Broadband
(HP/Amdoc
s)
- CPC -
Broadban
d
Activatio
n
(Syndesi
s)
- ATOM -
Provisioning/ Delivery
(Tibco BWW)
- USAGE -
Narrowban
d (Intec)
DWH/Service Inventory
Business Activity Monitoring
Usage CollectionService Activation
Assurance
& Performance
- ADAS -
Narrowba
nd
Activatio
n
(Custom)
- UNICA -
Network Inventory
(Telcordia Granite
Inv.)
OSS BUS
- LIDO -
Operational DWH
(Ascential, Oracle)
EFoundation
In order to accept the “Next Generation
Challenges”, in 2001 Telecom Italia started
a complete Renovation Program of its
OSS/BSS Platform.
This Program is based on four base principles :
1. Selection of best in class COTS and Packages (BUY Approach)
2. Usage of SW Middleware (EAI, ETL, SOA, etc.) for integration
3. Process Driven Architecture according to eTOM framework
4. Adoption of standard model for business entities, msg and IF
EFoundation Program
TelecomItalia OSS Platform
OPE
N
COT
S
EA
I
XM
L
5. 5
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P
TMW – 9 Nov 2005NGO SS1
The Service Fulfillment Scenario in 2003-2004
Legacy casting off already in place but:
BSS platforms organized by Customersegment
OSS platforms organized by networktechnology
Multiple representation of principal business entities (large XML adoption)
customer, service order, etc. (No Common Data Model)
Heterogeneous technologies for multiple
point-to-point interface (large EAI adoption)
CRM
Mass Market
CRM
Business
CRM
WholeSale
Narrowband
Provisioning
Platform
xDSL
Provisioning
Platform
ATM/IP VPN
Provisioning
Platform
focus on ICT (eg. XML,EAI)
instead of Business Entities
6. 6
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P
TMW – 9 Nov 2005NGO SS1
BSS&OSS – Data Issues forrenovation program
Data Redundancy due to multiple
representation
Enterprise Data not aligned
Extra cost (and Time) in manual
data reconciliation
Impact on “post sales” KPIs (e.g.
usage and billing)
Delay in delivery of new services
Increase of development cost
(professional services, SW
licenses)
SA
P
DELIVERY
DATI
DWH
DELIVERY
FONIA
TROUBL
E
USAG
E
CRM / R
CREDITO
PORTA
LI
OLO
FRAUD
CRM / B
7. 7
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P
TMW – 9 Nov 2005NGO SS1
TelecomItalia eFoundation Project
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
eFoundation
CRM/R CRM/B
CRM
WholeSale
Provisioning
System
Business Project
Management
Middleware
SID Based
Information
Model
Core
A Business process
automation BUS between
vertical platform (island)
focused in a specific business
process.
The Core use a Standard
Data Model (SID Based)
Island
Set of System focused on a
specific telco process (eg.
Activation, workforce, etc.).
The island uses a proprietary
Data Model
Adapter
Provides the Data Model
mapping between the CORE
& Island
Core
A Business process
automation BUS between
vertical platform (island)
focused in a specific business
process.
The Core use a Standard
Data Model (SID Based)
Island
Set of System focused on a
specific telco process (eg.
Activation, workforce, etc.).
The island uses a proprietary
Data Model
Adapter
Provides the Data Model
mapping between the CORE
& Island
CORE
ISLAN
D
ADAPT
ER
8. 8
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P
TMW – 9 Nov 2005NGO SS1
The adapter provides real
time remapping between
Core Data Model (SID
Based) & proprietary data
Model of the Island
The Metadata Repository
of the Adapter (Catalog) is
unique for the three
different communication
channels supported:
• On line transaction
• Message driven
• Massive data batch
The Master Repository is
deployed in the Core
infrastructure
Scenario
Event
based
On line
Batch
Piattaforma di
Integrazione locale
P1
A11
A12
A13
A14
A15
P1
A21
A22
A23
Platform specific object
model
Legenda
- Primary Platform
- Secondary platform
- Data Model
- Interface
Pi
Aik
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
CORE
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
P1 P2
A11
A12
A13
A14
A15
A21
A22 A23
IF
IF
IF
IF IF
IF
IF
IF
IF
IF IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
IF
SID Based model
TelecomItalia eFoundation Project: Adapter
NotesAdapter
9. 9
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P
TMW – 9 Nov 2005NGO SS1
eFoundation Project: SID-Based Information Model
Efoundation project has used TMF SID Model as a starting point in
order to model the business entity involved in the fulfilment process. In
particular the following domain/aspects:
•The Customer
•The Site
•The Commercial Offer
•The Service
•The Resource
10. 10
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P1
TMW – 9 Nov 2005NGO SS1
Data Model Guidelines, Patterns & Lesson Learnt
1) Order Decomposition Pattern
Service Order ►Element ►Component
3-level hierarchy is Perfect Mix between flexibility and performance
2) Change Order Pattern
In every modification order, old & the new values must always be inserted
When you are adopting a loosely coupled approach, the receiver shouldn’t be required
to maintain data versioning
3) Focus in attribute modeling
Identify quickly the “Enterprise Attributes” (attributes common between all the types
of a specific business entity) from the specific ones (flow-through attributes). Model
the Flow-through attributes in other two category :
• Declared (on which is possible implement validation syntax check only)
• Not Declared (black box management)
11. 11
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P1
TMW – 9 Nov 2005NGO SS1
Data Model Guidelines, Patterns & Lesson Learnt
4) Focus on the envelope (not only the payload)
•Schema Naming Policy
•Versioning Mechanism
•Logging Standard
•Repository
•Catalog distribution & Synchronization
5) Re-mapping logic in the Boundary
•The adapter, that has in charge the data remapping, MUST be developed inside
the island development team
•The CORE Project can define implementation guidelines or develop a
customizable adapter (e.g. XSLT transformer, Rule Engine Based , etc.)...
•But the “knowledge” of each “island dialect” must not be managed at the center.
12. 12
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P1
TMW – 9 Nov 2005NGO SS1
Lowerpart of management platform: network
interactionLong term Telecom Italia’s vision
introduction of a vendor-neutral mediation layerinstead of EMs
different roles in Inventories:
mediation databases for real-time
processes
OSS inventory for other
processes (e.g. planning, network creation)
Information model Requirements
interface between mediation layer and OSS:
vendor independent
features common to all network technologies
specific extensions for technology specific features
adoption of standards
interface between mediation layer and OSS:
open interfaces on network nodes
migration towards standard protocols and data models
13. 13
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P1
TMW – 9 Nov 2005NGO SS1
Networkcontext: multi-technology/vendor
IP Packet
Backbone
14. 14
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P1
TMW – 9 Nov 2005NGO SS1
Packet Layer-2 Model Application
network/subnetwork
NAS
SNP Link SNP Link
subnetwork
DSLAM
ATM
GBE
VPC/VCC
VLAN
XC
similarto
logicalPort
concept
ATM VC - SNC ATM VC/VLAN - SNC
CTP
TTP
TRAIL = e2e xDSL service
LC LC
PhysicalPort
snTP
snpLink
Subnetwork-objects
snpLink
Equipment-objects
Subnetwork-objects
Equipment-objects
PhysicalLink PhysicalLink
SNPLinkcan represent a
physical linkoran
abstract link
(networkmanaged
as a link)
15. 15
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P1
TMW – 9 Nov 2005NGO SS1
Service Domain & high level Resource Domain
SID Classes
TI Classes
NetworkServicecatalog
NetworkServicecomponent
forOSSinventory
NetworkServiceWorkOrder
16. 16
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P1
TMW – 9 Nov 2005NGO SS1
Logical Resource Domain – basic Connectivity part
SID Classes
TI Classes
Usage of SID as a high-
level representation of
connectivity, while other
models (e.g. MTNM/MTOSI
for specific network
technologies)
sim ilar to MTNMPTP
a nd SID
Re so urce Po rt
18. 18
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P1
TMW – 9 Nov 2005NGO SS1
Lesson Learnt
• SID coverage is ideal for a SP “umbrella” information model.
• Specific models for network technologies can be plugged in from other
models (e.g. MTNM/MTOSI, ITU-T, etc.). Integration guidelines and
boundary classes are not always fully documented.
• SID models are not so easy to be managed: large and complex
documentation, getting the overall picture is not that easy, model versioning
would help tracking updates.
• SID patterns are very powerful.
• Implementation (mainly performance issues) sets constraints that may
discourage a direct implementation of SID models.
19. 19
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P1
TMW – 9 Nov 2005NGO SS1
Conclusions – what’s next?
TI next steps
• completion of vendor neutral information model for all broadband networks,
starting fromaccess networks
• extension of process coverage fromFulfillment to Assurance;
• convergence in information models between fixed and mobile networks
What TI needs from TMF
• convergence and integration of SID and MTNM/MTOSI: guidelines &
boundaries;
• TMF leading role forstandard adoption by vendors’ offerings and SPs’ RFPs
• endorsement of TMF models into ITU standards
• guidelines to move from the business to the system and then implementation
view.
20. 20
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P2
TMW – 9 Nov 2005NGO SS1
ThankYou ForYourAttention
Marco Daccò
Marco.dacco@telecomitalia.it
Giuseppe Covino
giuseppe1.covino@telecomitalia.it
Bruno Foresi
bruno.foresi@telecomitalia.it
Giuseppe Ricucci
giuseppe.ricucci@telecomitalia.it
22. 22
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P2
TMW – 9 Nov 2005NGO SS1
eFoundation: example forcommercial offercomposition
1/3
Third layer of
decomposition
“Component”
Second layer of
decomposition
“Element”
First layer of
decomposition
“Service”
23. 23
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P2
TMW – 9 Nov 2005NGO SS1
eFoundation: example forcommercial offercomposition
2/3
Change Order
Patterns
24. 24
TITOLO PRESENTAZIONE, ALLINEATO IN
BASSO E A DESTRA, MASSIMO 2 RIGHE
P2
TMW – 9 Nov 2005NGO SS1
eFoundation: example forcommercial offercomposition
3/3
Enterprise
Attributes
Declared
Attributes
Not Declared
Attributes