Tmw dallas ngoss1 dacco covino

1

TITOLO PRESENTAZIONE, ALLINEATO IN BASSO E A DESTRA, MASSIMO 2 RIGHE

P1

TMW – 9 Nov 2005

NGOSS1

Real SID Implementions-Part 2:Using the SID for broadband provisioning-interfacing delivery platforms to CRM and to GBE network

Marco Daccò – Telecom Italia, OSSGiuseppe Covino, Bruno Foresi, Giuseppe Ricucci – Telecom Italia Lab, OSS

2


P2

TMW – 9 Nov 2005

NGOSS1

OutlineTelecom 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)

network model

lesson learnt

What’s next & expectations

3


P3

TMW – 9 Nov 2005

NGOSS1

1MB

Time

Ricaricabile

Free

4MB

GPRS

HSDPA

Videocall

Complex Services

Time to Market

Process Innovation

Telecom Italia Business Scenario - OSS

4


P4

TMW – 9 Nov 2005

NGOSS1

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)

-DIAGNOSYS-

Service Assurance

(Motive/Custom)

Network Inventory

- CIC -Network

Assurance (Micromus

e)

- PERSEO -Performanc

e Mgmt (ADC

Metrica)

- USAGE - Broadband (HP/Amdoc

s)

- CPC - Broadba

nd 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 - Narrowb

and 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

Telecom Italia OSS Platform

OPE

N

COT

S

EAI

XM

L

5


P5

TMW – 9 Nov 2005

NGOSS1

The Service Fulfillment Scenario in 2003-2004

Legacy casting off already in place but:

BSS platforms organized by Customer segment OSS platforms organized by network technologyMultiple 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 MarketCRM

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


P6

TMW – 9 Nov 2005

NGOSS1

BSS&OSS – Data Issues for renovation 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)

SAP

DELIVERY DATI

DWH

DELIVERYFONIA

TROUBLE

USAGE

CRM / R

CREDITO

PORTALI

OLO

FRAUD

CRM / B

7


P7

TMW – 9 Nov 2005

NGOSS1

Telecom Italia eFoundation Project

P1 P2

A11

A12

A13

A14

A15

A21

A22 A23

IF

IF

IF

IF IF

IF

IF

IF

IF

IFIF

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

IFIF

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

IFIF

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

IFIF

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 ManagementMiddleware

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)IslandSet of System focused on a specific telco process (eg. Activation, workforce, etc.). The island uses a proprietary Data ModelAdapter 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)IslandSet of System focused on a specific telco process (eg. Activation, workforce, etc.). The island uses a proprietary Data ModelAdapter Provides the Data Model mapping between the CORE & Island

CORE

ISLAND

ADAPTER

8


P8

TMW – 9 Nov 2005

NGOSS1

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

Eventbased

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

IFIF

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

IFIF

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

IFIF

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

IFIF

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

IFIF

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

IFIF

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

IFIF

IF

IF

IF

IF

IF

IF

IF

IF

IF

IF

SID Based model

Telecom Italia eFoundation Project: AdapterNotesAdapter

9


P9

TMW – 9 Nov 2005

NGOSS1

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


P10

TMW – 9 Nov 2005

NGOSS1

Data Model Guidelines, Patterns & Lesson Learnt1) 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


P11

TMW – 9 Nov 2005

NGOSS1

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


P12

TMW – 9 Nov 2005

NGOSS1

Lower part of management platform: network interactionLong term Telecom Italia’s vision

introduction of a vendor-neutral mediation layer instead 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


P13

TMW – 9 Nov 2005

NGOSS1

Network context: multi-technology/vendor

IP Packet Backbone

14


P14

TMW – 9 Nov 2005

NGOSS1

Packet Layer-2 Model Application

network/subnetwork

NAS

SNP Link SNP Link

subnetwork

DSLAM

ATM

GBE

VPC/VCC

VLAN

XC

similar to logicalPort

concept

ATM VC - SNC ATM VC/VLAN - SNCCTP

TTPTRAIL = e2e xDSL service

LC LC

PhysicalPort

snTP snpLink

Subnetwork-objectssnpLink

Equipment-objects

Subnetwork-objects

Equipment-objectsPhysicalLink PhysicalLink

SNP Link can represent a physical link or an abstract link (network managed as a link)

15


P15

TMW – 9 Nov 2005

NGOSS1

Service Domain & high level Resource Domain

SID Classes

TI Classes

Network Service catalog

Network Service componentfor OSS inventory

Network Service WorkOrder

16


P16

TMW – 9 Nov 2005

NGOSS1

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)

similar to MTNM PTP and SID ResourcePort

17


P17

TMW – 9 Nov 2005

NGOSS1

Physical Resource Domain

ManagedHardware(from Hardware Enti ties ABE)

PhysicalContainer(from Hardware Enti ties ABE)

EquipmentHolder(from Equipment Holder Enti ties ABE)

Equipment(from Equipment Entities ABE)

0..n0..1

0..n

EquipmentInEquipment

0..1

0..10..n 0..10..n

EquipmentInHolder

PhysicalDevice(from Physical Device Enti ties ABE)

Hardware(from Hardware Enti ties ABE)

0..n

0..1

0..n

ContainsHardware

0..1

0..1 0..n0..1 0..n

ConsistsOf

Card(from Equipment Entities ABE)

0..n0..1

0..n

CardOnCard

0..1

PhysicalPort(from Hardware Entities ABE)

0..1

0..n

0..1

0..n

PortsOnCard

CardPlus(from TILab Classes)

PhysicalPortPlus(from TILab Classes)

EquipmentHolderPlus(from TILab Classes)

PhysicalResourceTypePlus(from TILab Classes)

PhysicalResource(from PhysicalResource Enti ties ABE)

0..n 0..10..n 0..1

PRTypeCategorizesPhysicalResource

LocationPlus(from TILab Classes)

PhysicalDevicePlus(from TILab Classes)

0..n

0..10..1

PhysicalDeviceLocatedAt

0..n

SID Classes

TI Classes

physical containment structure of the node

18


P18

TMW – 9 Nov 2005

NGOSS1

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


P19

TMW – 9 Nov 2005

NGOSS1

Conclusions – what’s next?

TI next steps

• completion of vendor neutral information model for all broadband networks, starting from access networks

• extension of process coverage from Fulfillment 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 for standard 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


P20

TMW – 9 Nov 2005

NGOSS1

Thank You For Your Attention

Marco Daccò

[email protected]

Giuseppe Covino

[email protected]

Bruno Foresi

[email protected]

Giuseppe Ricucci

[email protected]

21


P21

TMW – 9 Nov 2005

NGOSS1

Annex

22


P22

TMW – 9 Nov 2005

NGOSS1

eFoundation: example for commercial offer composition 1/3

-ID_SO-Tipo_Richiesta-Causale_SO-Categoria_Richiesta-Data_SO-Data_Emissione-Origine_SO-Stato_SO-Data_Creazione_Record-Data_Richiesta_Cliente-Data_Prevista_Attivita-Desc_Lavori-Richiesta_Temporanea-Data_Prevista_Cessazione-Fascia_Appuntamento-Data_Appuntamento-Data_Esecuzione_Attivita-Non_Annulabile

CIM_Service_Order

-Id_SOE-Azione_Richiesta-Esito_Azione_Richiesta-Data_Attivazione-Tipo_SOE-Dominio_Delivery-Stato_SOE-Data_Cessazione

CIM_SOElement

-ID_Soec-Tipo_SOEC-Azione_Richiesta-Stato_SOEC-Esito_Azione_Richiesta

CIM_SOE_Component

1

0..*

1 1

-Tipo_Reference-ID_Reference-Titolo-Nome-Cognome-Ragione_Sociale-Telefono-Cellulare-email-FAX-Nazione-Provincia-Localita-Comune-CAP-Indirizzo-Part_Top-Civico-Indirizzo_Concatenato-Complesso-Scala-Piano-Interno-NIC_HDL-Cod_Fisc-Data_Nascita-Provincia_Nascita-Comune_Nascita-Stato_Nasc_Estero-Sesso

CIM_Reference

*0..1

-Tipo_Convenzione-Attivita-Nome_Servizio-ID_Servizio-ID_Invariante_Servizio-Came_From_ID-Versione_Servizio-Famiglia_Servizio-Stato_Service-CICLU-Tipo_CICLU-Collegamento_Fisico-Cod_Progetto-Desc_Progetto-Data_Firma_Contratto-Lotto_Fatturazione-Complesso-Scala-Piano-Interno-Sincronizza

CIM_Service

0..*

1

0..*

-ID_Cliente-Cod_Cliente_CRM-Ragione_Sociale-Cognome-Nome-Sesso-Partita_IVA-Cod_Fisc-Cod_Nat_Giuridica-Desc_Nat_Giuridica-Marcaggio_Cliente-Data_Nascita-FL_Tipo_Persona-Segmento_Cliente-Cod_Catast_Comune_Nascita-Comune_Nascita-Provincia_Nascita-FL_Dipendente_TI-Cod_Attività_ISTAT-Desc_Attività_ISTAT-Nazione-Localita-CAP-Sigla_Provincia-Provincia-Cod_Provincia_ISTAT-Comune-Cod_Comune_ISTAT-Indirizzo-UT_Cliente-Cod_Catast_Comune-Data_Ultima_Variazione

CIM_Customer

-ID_Site-Cod_Provincia_ISTAT-Provincia-Sigla_Provincia-Cod_Comune_ISTAT-Cod_Comune_ADSL-Cod_Comune_Catastale-Comune-Cod_Indirizzo_BDA-Indirizzo-Cod_Civico_BDA-N_Civico_Effettivo-Part_Top-CAP-Cod_DR-Desc_DR-Cod_AG-Desc_AG-EPA_OPA-Cod_Centrale_RR-Desc_Centrale_RR-Cod_UT-Desc_UT-Sigla_UT-Livello_Certificazione

CIM_Site

11..2

-Codice_Fattura-Flag_Fattura_Singola-Destinatario_Fattura-Indirizzo_Destinatario-Sigla_Provincia_Destinatario-Cod_Catast_Provincia_Destinatario-Provincia_Destinatario-CAP_Destinatario-Data_Ultima_Variazione

CIM_Billing_Account

-Tipo_Vendor-Nome-Cognome-Telefono-Cellulare-e-mail-Data_Ultima_Variazione

CIM_Vendor1

*

1 *

Third layer of decomposition

“Component”

Second layer of decomposition

“Element”

First layer of decomposition

“Service”

23


P23

TMW – 9 Nov 2005

NGOSS1



CIM_Service_Order


CIM_SOElement


CIM_SOE_Component

1

0..*

1 1


CIM_Reference

*0..1


CIM_Service

0..*

1

0..*


CIM_Customer


CIM_Site

11..2


CIM_Billing_Account


CIM_Vendor1

*

1 *

Change Order

Patterns

24


P24

TMW – 9 Nov 2005

NGOSS1



CIM_Service_Order


CIM_SOElement


CIM_SOE_Component

1

0..*

1 1


CIM_Reference

*0..1


CIM_Service

0..*

1

0..*


CIM_Customer


CIM_Site

11..2


CIM_Billing_Account


CIM_Vendor1

*

1 *

Enterprise

Attributes

Declared

AttributesNot Declared

Attributes

Tmw dallas ngoss1 dacco covino

Technology

Transcript of Tmw dallas ngoss1 dacco covino