Case Study on the Development of Inventory Interface Standards. Implementing NGOSS with MTOSI

Transcription

1 Case Study on the Development of Inventory Interface Standards Implementing NGOSS with MTOSI

2 Agenda Standards and standardization About MTOSI MTOSI Implementation Case Study Nortel + Bell Canada Conclusions Q+A

3 High Integration Costs Drive Need for Standards While about 4% of service provider revenues are spent on operation systems Frameworks 50%+ of operations costs devoted to integration [source: Keith Willets, TMW Dallas 2003] Process (etom) Data (SID, MTNM) OSS interface standards could drive down the high cost of integration Need to re-focus TMW work on development of an integration framework Applications (OSS/J) Integration (MTOSI, MTNM) Adapted from Keith Willets Lean Operator talk, TMW Dallas 2003

4 Standards and Standardization Standards Agreed reference definitions for information exchange or procedures Documents and code Success requires technical expertise Standardization The process of driving the adoption of standards Degree of adoption Success depends on commercial and political viability Enabled by business owners and budget holders This industry needs both!

5 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

6 MTOSI Initial Focus > Northbound interfaces between NMS/EMS and higher-level applications > Version 1.0 designed for: Inventory Retrieval from NMS/EMS Inventory-Inventory Sync Active Alarm Retrieval Inventory and Alarm Notification Inventory A MTOSI Inventory B Common Communications Vehicle MTOSI Fault Management 814 EMS MTOSI MTOSI SNMP EMS MEs TL1 MEs

7 MTOSI 1.0 Feature Highlights 608 model with MD and OS extensions Multiple communication styles: sync, async, file transfer Fine grain operations Bulk inventory and alarm operations Inventory and fault notifications with scope/filter Source notification suppression Operations profiling XSD, SOAP, WDSL definitions Module level versioning JMS binding and implementation guidelines Leverage existing deployments and expertise Flexible to support different interaction needs Backwards compatible with 814-like interfaces Simplify requesting OS code, communications Scope and Filter replaces many fine grain operations Turns off notifications if desired Group operations by business process. Reduces compliance complexity requirements Supports web service standards Supports backwards and forwards compatibility, major/minor versions Support for SOA / ESB principles: loosely coupled, coarse grain, reliable messaging

8 MTOSI: Deliverables TMF 513os MTOSI Addendum to TMF 513 Extensions to TMF 608 TMF 854 MTOSI XML Solution Set TMF 854A MTOSI Implementation Statement for XML Solution Set Business Function Profiles Supporting Documents: > MTOSI overview > Communication Styles > JMS Guidelines > HTTP/S Guidelines > Notifications > Inventory File description > Versioning > Naming

9 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 Activation Service Provisioning Service Performance Management > Will require extension of 608 model and unification with SID > Input and suggestions welcome. Please contact team lead Steve Fratini, [email protected]

10 MTOSI Standards Team, Implementation Team Telcordia TTI Toborg Technology Strategies Lucent Siemens British Telecom Nortel Cramer MTNM Team Implementation supported by Bell Canada.

11 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 infrastructure Network Management via Nortel Preside Cramer provides: Consolidated inventory for GigE (RPR), SONET, T-Carrier, DWDM & DSL Automated & semi-automated flow-through provisioning But what of the future?

12 Bell Canada - Next Generation Inventory objectives The program delivers infrastructure building blocks that will simplify Operations and Business Processes through enabling technology. Improve Efficiency: Transport Network Management Access Network Management Assign & Design New Product intro New Technology intro Sales, Marketing Help Desks, IS/IT Strategy Business Drivers: Build Reusable Assets Reduce OPEX / CAPEX Enable New Services Digital Assembly Line People Technology Simplify Processes: Network Planning Physical Design & Assignment Logical Design & Assignment Network Provisioning Configuration Management Process Simplify New Enabling Technology: ONE Inventory Repository Integrated Systems Network Planning Tools New Technology Support Scalability & Flexibility

13 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

14 Cramer-Nortel MTOSI Solution Overview Inventory Management Domain The addition SyncEngine delivers reconciliation capability: Scaleable J2EE architecture Scheduled or event-driven synchronization Synchronization set-up/gui Synchronization reports/sync rules Network Management Domain The addition of TMF Light delivers inventory export capability: Discovery/collection of NE configuration data Consolidation of data from multiple NEs Transformation to XML format Uses existing TMF 814 data model ResourceManager SyncEngine Adapter Preside for Optical TMF Light EC EC Nortel Equipment

15 TMF vs TMF Light Interface Comparison TMF Light TMF 814 Functions Data Extract Standards Compliance Notification Based Portfolio Coverage Complexity Uses >Logical Inventory >Physical Inventory >Performance Yes >TMF 814 data conformant >Compliant with future MTOSI No Complete today Lowest >Scheduled OSS inventory alignment >Logical Network Topology Extraction >Physical Equipment Inventory Extraction >Logical Inventory >Physical Inventory >Activation >Fault Yes TMF 814 Yes Growing Highest >Fault Event Notifications >Logical Topology Notifications >Flow-through Provisioning

16 Cramer-Nortel MTOSI Solution Overview Two-part adapter solution OSS/inventory management side Request/Response API Sends scheduled/ad-hoc requests Returns XML results for reconciliation NMS side Request/Response API Listens for synchronization requests Returns batched XML based on scope of request.we each work to MTOSI Cramer Development Nortel Development ResourceManager SyncEngine Adapter for Preside Optical Preside for Optical EC TMF Light EC Nortel Equipment

17 Adapter Architecture User-selectable sync profiles Operational decision Cramer ResourceManager SyncEngine Dynamic constraints E.g. specific node instance XML sync request contains scope/filter information As per profile Request acknowledgement Confirms response possible Scoped XML data returned Batched and provided in response message(s) Comparison/sync with inventory Cramer-Nortel Synchronization Adapter SyncEngine Config. MTOSI Messaging Adapter OAI Hub JMS JMS MTOSI Messaging Adapter Nortel Programmatic API Nortel Data Mining Interface Network Elements MTOSI Interface XML File Structure Nortel

18 Status & Next Steps Functional spec of the two adapters complete JMS adapter stubs tested & working Adapter development under way 2 x 2 development team Target 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

19 Future Considerations Cramer ResourceManager Configurator NE Type description interface Publishing of new NE models Shelf/slot/card/port capability Described using XML Standardized modelling Uploadable into inventory Benefits Vendor provides new NE models Verified NE modelling No manual configuration Faster technology introduction Cramer-Nortel Synchronization Adapter SyncObject Strand SyncEngine SyncEngine Config. Cramer Messaging Adapter OAI Hub JMS JMS Nortel Messaging Adapter MTOSI Interface Nortel Programmatic API XML File Structure Nortel Data Mining Interface Nortel Device Description NE Type Configuration Description PublishType Strand Network Resources

20 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 products High-value transactional interfaces The top-down approach Simplifies the interface Enables re-use everyone can build to same interface

21 What does that mean for me? Good news for TMF Practical experience as input A complete and proven standard Good news for vendors A standardized northbound interface for equipment vendors A standardized dataload/synchronization interface for inventory vendors But most of all..good news for Service Providers Improved vendor inter-working Loosely coupled applications Reduced integration costs Reduced deployment timescales Reduced deployment risk Reduced cost of ownership OSS MTOSI EMSs

22 Questions?