case study on the development of inventory interface standards...

Implementing NGOSS with MTOSICase Study on the Development of Inventory Interface Standards

© Cramer Systems Europe Ltd, 2003. All rights reserved.Commercial in confidence.

Agenda

Standards and standardization

About MTOSI

MTOSI Implementation Case StudyNortel + Cramer @ Bell Canada

Conclusions

Q+A


High Integration Costs Drive Need for Standards

While about 4% of service provider revenues are spent on operation systems…

50%+ of operations costs devoted to integration [source: Keith Willets, TMW Dallas 2003]

OSS interface standards could drive down the high cost of integration

Need to re-focus TMW work on development of an “integration framework”

Process

(eTOM)

Applications

(OSS/J)

Integration

(MTOSI,MTNM)

Data (SID,

MTNM)

Frameworks

Adapted from Keith Willets “Lean Operator” talk, TMW Dallas 2003


Standards and Standardization

StandardsAgreed reference definitions for information exchange or proceduresDocuments and codeSuccess requires technical expertise

StandardizationThe process of driving the adoption of standardsDegree of adoptionSuccess depends on commercial and political viabilityEnabled by business owners and budget holders

This industry needs both!


Origins and Objectives of MTOSI

> Multi-Technology Operations Systems Interface

> Started as MTNM subteam mid 2003

> Objective: Extend MTNM model for OS-OS interfaces

> Based on MTNM 513 (BA), 608 (IM) and 814 (IDL)

> XML / Web Services integration interface

> Uses NGOSS and SOA design principles

Mtosi: A rare tropical fish found only in Tanzania


MTOSI Initial Focus

> Northbound interfaces between NMS/EMS and higher-level applications

> Version 1.0 designed for:Inventory Retrieval from NMS/EMSInventory-Inventory SyncActive Alarm Retrieval Inventory and Alarm Notification

Common Communications Vehicle

Inventory A Inventory B

Fault Management

EMS

MEsMEsEMS

MEsMEs

MTOSI

MTOSI MTOSI

MTOSI

814

TL1

SNMP


MTOSI 1.0 Feature Highlights

Support for SOA / ESB principles: loosely coupled, coarse grain, reliable messaging

JMS binding and implementation guidelines

Supports backwards and forwards compatibility, major/minor versions

Module level versioningSupports web service standardsXSD, SOAP, WDSL definitions

Group operations by business process. Reduces compliance complexity requirements

Operations profilingTurns off notifications if desiredSource notification suppression

Scope and Filter replaces many fine grain operations

Inventory and fault notifications with scope/filter

Simplify requesting OS code, communicationsBulk inventory and alarm operationsBackwards compatible with 814-like interfacesFine grain operations

Flexible to support different interaction needsMultiple communication styles: sync, async, file transfer

Leverage existing deployments and expertise608 model with MD and OS extensions


MTOSI: Deliverables

TMF 513osMTOSI Addendum to TMF 513

Extensions to TMF 608

TMF 854MTOSI XML Solution Set

TMF 854AMTOSI Implementation Statement for XML Solution SetBusiness Function Profiles

Supporting Documents:

> MTOSI overview

> Communication Styles

> JMS Guidelines

> HTTP/S Guidelines

> Notifications

> Inventory File description

> Versioning

> Naming


MTOSI Status and Roadmap

> V1.0 and submitted for MTNM review ~Nov/Dec 04> TMF member ratification ~1Q 05> MTOSI to split from MTNM into separate team for V2.0> Intermediate versions 1.X to address miscellaneous technical enhancements (e.g., versioning, transport, state, filtering, etc.)> Version 2 may address new OS-OS interfaces such as:

Service ActivationService ProvisioningService Performance Management

> Will require extension of 608 model and unification with SID> Input and suggestions welcome. Please contact team lead Steve Fratini, [email protected]


MTOSI Standards Team, Implementation Team

Implementation supported by Bell Canada….

MTNM TeamBritish TelecomToborg Technology Strategies

CramerSiemensTTI

NortelLucentTelcordia


Bell Canada Today

Bell Canada provides:Wired and wireless voice and data services to residential and business customers

E.g. High speed wireless Internet access, IP-broadband services, e-business solutions and satellite television services

Nortel Networks Provides:Approximately 80% of Bells network infrastructureNetwork Management via Nortel Preside

Cramer provides:Consolidated inventory for GigE (RPR), SONET, T-Carrier, DWDM & DSLAutomated & semi-automated flow-through provisioning

But what of the future?


Bell Canada - Next Generation Inventory objectivesThe program delivers infrastructure building blocks that will simplify Operations and Business Processes through enabling technology.

StrategyStrategy

PeoplePeople

ProcessProcess

TechnologyTechnology

New Enabling Technology:• ONE Inventory Repository• Integrated Systems• Network Planning Tools• New Technology Support• Scalability & Flexibility

Simplify Processes:• Network Planning• Physical Design & Assignment• Logical Design & Assignment• Network Provisioning• Configuration Management

Improve Efficiency:• Transport Network Management• Access Network Management• Assign & Design• New Product intro• New Technology intro• Sales, Marketing• Help Desks, IS/IT

Business Drivers:• Build Reusable Assets• Reduce OPEX / CAPEX• Enable New Services• Digital Assembly Line

Simplify


Bell Canada - Requirements for COTS solutions

Agreed target architecture:Regular architecture and design discussions with Cramer and Nortel

Simplify OSS integration effort

Use of standards wherever possible:Existing standards – TMF 513/814/608

Emerging standards - MTOSI

Deploy fully supported integration solutions:Fully documented

Upgrade independent

Product roadmap

Technical support


Cramer-Nortel MTOSI Solution OverviewInventory Management Domain

The addition SyncEngine delivers reconciliation capability:

Scaleable J2EE architectureScheduled or event-driven synchronizationSynchronization set-up/GUISynchronization reports/Sync rules

Network Management DomainThe addition of TMF ‘Light’ delivers inventory export capability:

Discovery/collection of NE configuration dataConsolidation of data from multiple NEsTransformation to XML formatUses existing TMF 814 data model

SyncEngine

ResourceManager

Adapter

Preside for Optical

TMF Light

EC EC

NortelEquipment


TMF vs TMF Light Interface Comparison

>Logical Inventory

>Physical Inventory

>Activation

>Fault

>Logical Inventory

>Physical Inventory

>Performance

Functions

HighestLowestComplexity>Fault Event Notifications

>Logical Topology Notifications

>Flow-through Provisioning

>Scheduled OSS inventory alignment

>Logical Network Topology Extraction

>Physical Equipment Inventory Extraction

Uses

Growing Complete todayPortfolio Coverage

YesNoNotification Based

TMF 814>TMF 814 data conformant

>Compliant with future MTOSI

Standards Compliance

YesYesData Extract

TMF 814TMF Light


Cramer-Nortel MTOSI Solution Overview

Two-part adapter solutionOSS/inventory management side

Request/Response APISends scheduled/ad-hoc requestsReturns XML results for reconciliation

NMS sideRequest/Response APIListens for synchronization requestsReturns batched XML based on scope of request

…….We each work to MTOSI

SyncEngine

ResourceManager

Adapter for Preside Optical

Preside for Optical

TMF Light

EC EC

NortelEquipment

CramerDevelopment

NortelDevelopment


Adapter ArchitectureUser-selectable sync profiles

Operational decision

Dynamic constraintsE.g. specific node instance

XML sync request contains scope/filter information

As per profile

Request acknowledgementConfirms response possible

Scoped XML data returnedBatched and provided in response message(s)

Comparison/sync with inventory

ResourceManager

SyncEngine

Nortel Programmatic API

Nortel Data Mining Interface

NetworkElements

XML File Structure

MTOSI Messaging Adapter

JMS

OAI HubJMS

MTOSI Interface

Cramer

Nortel

SyncEngine Config.

MTOSI Messaging Adapter

Cra

mer

-Nor

t el S

ynch

roni

zatio

nA

d ap t

er


Status & Next Steps

Functional spec of the two adapters complete

JMS adapter stubs tested & working

Adapter development under way2 x 2 development teamTarget availability mid-2005

Possible second trial with BT

Standard will be made available for other vendors to develop to

Encourage others to adopt the same approach (and interface)Vendors and service providers


Future Considerations

NE Type description interfacePublishing of new NE modelsShelf/slot/card/port capabilityDescribed using XMLStandardized modellingUploadable into inventory

BenefitsVendor provides new NE modelsVerified NE modellingNo manual configurationFaster technology introduction

Pub

lishT

ype

St r

and

Syn

cObj

ectS

tran

d

ResourceManager

SyncEngine

Nortel Programmatic API

Nortel Data Mining Interface

NetworkResources

Configurator

XML File Structure NE Type

ConfigurationDescription

DeviceDescriptionNortel Messaging Adapter

JMS

OAI Hub

JMS

MTOSI Interface

Cramer

Nortel

SyncEngine Config.

Cramer Messaging Adapter

Cra

mer

-Nor

t el S

ynch

roni

zatio

nA

d ap t

er


Findings

MTOSI works!

MTOSI allows faster, simpler integration of NMS-to-OSS

MTOSI enables vendors to more easily integrate to a wider range of equipment (or OSS)

RAD-type development: standard + development + refinement

‘Two-part’ adapter approach decouples vendor productsHigh-value transactional interfaces

The ‘top-down’ approachSimplifies the interfaceEnables re-use – everyone can build to same interface


What does that mean for me?Good news for TMF

Practical experience as inputA complete and proven standard

Good news for vendorsA standardized northbound interface for equipment vendorsA standardized dataload/synchronization interface for inventory vendors

But most of all….

….Good news for Service ProvidersImproved vendor inter-workingLoosely coupled applicationsReduced integration costsReduced deployment timescalesReduced deployment riskReduced cost of ownership

OSS

EMSs

MTOSI

Questions?

[email protected]