1. 1 Network Management Chapter 3 OSS Development POSTEC Lecture April 15-May 1, 2008 Masayoshi Ejiri Japan

2. 2 Agenda 1.ICT Operations and Management - Service Industries - ICT Services and Networks— - Target of the Management 2, Architecture,Function,Information Model and Business Process - ITU-T TMN( Telecommunications Management Network) - TeleManagement Forum Telecommunications Operations Map ( TOM) - Multi domain management and System Integration - Standardization 3. OSS( Operations Support System ) Development - Software Architecture,Key Technologies and Product Evaluation— 4. SLA( Service Level Agreement) and QoS( Quality of Service) - SLA Definition, reference point and policy based negotiation 5, IP/eBusiness Management - Paradigm shift, Architecture beyond TMN and enhanced TOM 6. NGN( Next Generation Networks) Management - NGN Networks and Services, New Paradigm of ICT Business and Management

3. 3 ・ Software Architecture ・ Platform ・ COTS/PnP ・ Software Architecture ・ Platform ・ COTS/PnP ・ Business Process ・ Functional Architecture ・ Information Model ・ Business Process ・ Functional Architecture ・ Information Model Management ManagementSystem System Management System Development Strategy/ Policy Customers Demand Interoperability Profit Strategy/ Policy Customers Demand Interoperability Profit COTS:Commercial Of The Shelf PnP: Plug and Play Target (Why) Technology (How) Business (What) Development

4. 4 OSS Development Target Software Architecture and Foundation TMF Goal and NGOSS Products evaluation Proof of Interoperability

5. 5 OSS Development - from Built to Assemble- Software Manufacturing  Package integration, Use Tools Proprietary BP and Interface  Common BP and Standards interface Software Module  Software Component (Atomic Component and Objects ??)

6. 6 Consensus of Business Process and OSS ・ COTS:Commercial Off the Shelf Software ・ Proof of Interoperability Globally Acceptable Software Packages and OSS Software Packages and OSS ----> Not Built but Buy ----> Not Built but Buy For Faster, Cheaper and Better OSS

7. 7 Object Oriented Software Architecture MO Generation MO Service Common Application Domain Specific Application Distributed Processing Environment

8. 8 B.M.L S.M.L. N.M.L. E.M.L. User Interface(GUI/CUI) Q3 Management Application OS Hardware Protocol Stack Distributed Environment Development Environment MO's Behavior MIB Management Manager/Agent Core Manager /Agent Manager /Agent Agent Q3 OSS Framework Application Platform OS Hardware Q3

9. 9 ICT management systems architecture Process Control Communication Control AP MO Generation MIB GW GUI Other Systems

10. 10 OSS Software Architecture (1) Other NMS NMS User Application GUI Communication Control NMS Data Base Managed Objects NMS:Network Management System

11. 11 OSS Software Architecture (2) Management Service Plane Management Service Plane Execution Plane Execution Plane Support Plane Support Plane System Management System Management Application Event Management Event Management GUI Data Base Communication Control Communication Control Object Manipulation Object Manipulation Distributed Environment Distributed Environment Testing Tools Testing Tools Development Tools Development Tools

12. 12 Requirements for the Platform Operability –Easy Operation, End User Computing Oriented, Easy GUI Interoperability –Provide seamless information exchange between applications Portability –Software package Scalability –Easy to extend Flexibility –Evolution of Business Process and Operability

13. 13 OSS Application View NE Technology TMN Management OSI Management Function Fault Management Configuration Management Account Management Performance Management Security Management Business Management Service Management Network Management NE Management PDH SDH SONET ATM FR

14. 14 Process Specific Foundation NW Technology Specific Foundation Business Specific Foundation ICT Common Foundation (C.F) Telco C.F. SM / NM C.F.EM C.F A Business B BusinessC Business NM C.FSM C.F SO F.TT F. SDH F.ATM F. Foundation Core NWF. Access NWF. NW Domain Specific Foundation

15. 15 TMF TeleManagement Forum? Non-profit global organization of 600+ service providers, systems integrators, ISV and NE vendors, established 1988 TM Forum Events - TMW( TeleManagement Forum) : General Meeting, Twice a year with Discussion, Education, Catalyst projects and Products Exhibition - TAW( Team Action Week) : Experts Meeting, 4 times a year and additional meeting and frequent Conference Call, defines de facto standards

16. 16 TMF Direction Interoperable OSS: as the de-facto standard. –Multi-Service Providers, Vendors, Technologies,.… –Common Business process and Components Source of new technologies for OSS developments. –COTS, CORBA, XML, SOAP, JINI, … International Promotion for OSS products. –Catalyst Showcase ， Product Expo…

17. 17 TMF Goals TMF is committed to enabling: Real world solutions Implementation Tested models Available COTS products that plug and play Lead industry in definition and realization of New Generation OSS OSS Development less than 3 Months ???

18. 18 SMART TMN SMART TMN Approach Telecom Operations Map Process Flow Architecture Technology Integration Map Plug and Play Integration Catalyst Projects Implementation Demos Central Information Facility Object Models, Data Dictionary

19. 19 TMF Telecom Operations Map

20. 20 TMF Technology Integration Map

21. 21 System View Implementation View NGOSS Knowledge Base Need Model Validate Run Business View Contract Interface Service Implementation Run-Time View TMF NGOSS Methodology Methodology – system of principles and procedures applied to a discipline

22. 22 Logical View Physical View Service Developers View Service Providers View Implementation Deployment BusinessSystem Deployment Capabilities, Constraints & Context Implementation Capabilities, Constraints & Context Business Capabilities, Constraints & Context System Capabilities, Constraints & Context Corporate Knowledge Base NGOSS Knowledge Base Shared NGOSS Lifecycle with Iteration

23. 23 NGOSS™ Architecture Technology Specific Architecture Mappings Implementation Specific Projects NGOSS™ Project Organization Requirements Business Case Tech. Neutral Arch.

24. 24 NGOSS NGOSS New Generation Operations Systems and Software Define and rationalize the new generation of architectures and frameworks NGOSS™ is the term the TMF uses to describe a “loosely coupled” distributed component architecture along with “business aware” application components upon which ICSP business can run. The components interact through a common information bus The components can be programmed through the use of a process management tool to control the business processes of the service provider using the functionality provided by the components.

25. 25 Communications Technology Services Process Flow Engine FS BAC Process Definition Tool Process Flow BAC: Business Aware Component FS: Framework Service NGOSS Framework TM NGOSS Framework TM NGOSS Registry TM NGOSS Shared Data Model TM

26. 26 Business Requirements for Industry Stakeholders Service Provider –Richer Services Offerings –Faster Time to Market –Buy vs. Build –Multi- vendor ･ Systems Integrator –Faster/ Complete Solution –Predictable –Outcomes/ Costs –Grow the Market Independent Software Vendor –Build Once, Sell Many –Less Custom –Development –Customizable Software –Components –Grow the Market Network Equipment Provider –More/ Faster Equipment Sales

27. 27 OSS Requirements Interoperability Scalability Evolvability/ Migration Modularity/ Distribution Backward Compatibility Reliability, Availability, Survivability Flexibility Manageability/ Serviceability Data Accessibility Security etc.

28. 28 Major Technology Selection Process Definition: using UML (Unified Modeling Language) Interface Definition: by XML (Extensible Markup Language ) Application Definition: on Java Contents Exchange deploying Web Services using WSDL(Web Service Description Language), SOAP(Simple Object Access Protocol) and UDDI(Universal Description,Discovery and Integration )

29. 29 Technology selections

30. 30 Paradigm shift of Business Process Analysis Operator view point  Customer view pointOperator view point  Customer view point Enumeration of conventional process  Top down process analysisEnumeration of conventional process  Top down process analysis Individual,isolated process  Process flow throughIndividual,isolated process  Process flow through Closed, Internal process  Cooperative process with customer and partner Closed, Internal process  Cooperative process with customer and partner Presume matured technology  Exploit prospective technologyPresume matured technology  Exploit prospective technology

31. 31 New Business process Optimized Process Optimized Process  Agility process for daily business transformation by process components. based flexible BPM  Agility process for daily business transformation by process components. based flexible BPM

32. 32 Check points of OSS development What advantage customer can expect ? The business process developed is applicable in the market ? ( Modify process to meet market products and trend) How flexibility and expandability are guaranteed to meet unknown change in short time ? Can be interface clarified on system ground plan ?Can related systems agree it ? List up and evaluate reusable /available components and tools ? Evaluate current/future technologies ? Deployed technologies will become mainstream ? Can you sell the developed package ? Can you release within 6 months ?

33. 33 OSS Evaluation Point 1.Term : Faster, Cheaper and Higher Quality  6 months rule 2.Engineering : How designed rather than what can do  Deployed( Selected) Architecture, Components, Technologies ( Web, XML,CORBA,EJB etc.) 3.Interoperability : Proof of “Market In” Products  Not Built But Buy, If Built Must Sell it Proof of “Market In” Products  Not Built But Buy, If Built Must Sell it 4. Flexibility ( Agility ) : Quick Response to Specification change( Modification)  2-3days for process change, one week for AP

34. 34 Productivity of Software Vendor( Organization ) 1.Technology and Connoisseur 2.Common Information Model and Architecture ( Reusable Components) 3.Platform Selection, Stock of Software components 4.Development Environment and Tools 5.Personal Productivity

35. 35 Requirements to SE/SI group for analysis and design Vision and insight to grasp business as a whole.Vision and insight to grasp business as a whole. Foresight to depict what is essence and substantial.Foresight to depict what is essence and substantial. Ability of abstraction,description and presentation.Ability of abstraction,description and presentation. Engineering ability to embody concept to products.Engineering ability to embody concept to products.

36. 36 Project Management Control of CQD(Cost, Quality and Delivery) Does work, do things right Manage CQD, Technology, User support, Change management, Time in Market etc. Does contribute, do right things

37. 37 Project Management PMBOK(Project Management Body of Knowledge) 5 basic process group: Initiating. Planning, Executing, Controlling, Closing 9 knowledge areas: Integration,Scope,Time,Cost,Quality, Human Resource, Communications, Risk,Procurement, PMP(Project Management Professional )qualification by PMI( Project Management Institute /USA)

38. 38 Note of project management “Object oriented “ is a methodology effective only when project team well understands what is it. Only the objects which intentionally developed for the purpose of reuse can be reused. Water fall model can be applied to the objects small enough that one person can understand. Take enough time before starting programming. High technologies soon become consensus and low technologies in the next step.

39. 39 Case Study NTT Service front support systemNTT Service front support system Fujitsu Service Management system ( FLEXER –SM)Fujitsu Service Management system ( FLEXER –SM)

40. 40 Target of Service Front Issues : In the explosion of variety of services, heterogeneous technologies and competition Urgent to Establish total customer center for any services and claims By Realizing quick and accurate response to customers for 24/7/365 Kaizen : Develop Business process and OSS to concentrate necessary information to service front operator -> networking Training and team work reinforcement to operators

41. 41 Networking Service order Charge collection Construction Trouble shooting Sales Marketing Account manager Back yards Directory enquireries NE/NW Customers : service front Interaction of service front and customers General affaires

42. 42 Business process ( networking and organization) Reform of “113” test center of service claims to total customer service center Responsible HQ department create DB of service /products information accessible from any center operators. ( visual and text ) Network status information is to be reported to /can be accessed by the operators for both intra office and nationwide events. Share the knowledge and useful experiences among centers by email exchange, accumulate knowledge DB and help desk. Rule based control of information handling for security.

43. 43 Networking

44. 44

45. 45

46. 46

47. 47 OSS development Received the order at April 1993 and introduced the OSS to 90 main centers at March 1994 Process analysis,design and technology assessment for 6 months collaborating OSS developers and business practitioners( operators) Software development for 6 months. Initial OSS cut off ( first introduction ) started January 1994. Deploy Sun Solaris, embedded mail function and package middleware. Deploy end user programmable GUI and local DB.

48. 48 Service creation with FLEXR-SM Identify Process Identify Information Sharing Requirements Create Process Model in SM Customize Screens & Interfaces OTHER OPERATIONS SUPPORT SYSTEMS Customer Billing system Customer Billing system Maintenance Dispatcher Maintenance Dispatcher SLA system SLA system Design System Interfaces Design System Interfaces Network Status, Fault, & Configuration [Standard with FLEXR-NM]

49. 49 Core Components of FLEXR-SM Workflow EngineWorkflow Engine Service Designer ToolsService Designer Tools –Process designer –Interface designer –Screen designer –Report designer –Templates OS AdapterOS Adapter Web ServerWeb Server DatabaseDatabase Administration ToolsAdministration Tools Database Workflow Engine Administration Tools Report Generator Web Server Service Design Tools GUI Forms Process Reports Interfaces OS Adapter Application Library Web Operators Network Management Systems

50. 50 Expertise Service Management Solution * Q3/CMIP* SNMP* TL-1 * OSI* X25* TCP/IP * HTTP * DWDM Network element * Wireless Network Element * Access Network Element * SDH Network Element * SONET Network Element Telecom Experience * SMTP* DB* Web Server * C++* XML/XSL* HTML * CORBA* Java* Java Bean * Client / Server * UNIX Development * Window Development Software Technologies Silicon Valley Innovation New Technology and Experience provide Flexible Solution

51. 51 Seamless Operations by GUI Integration N M E M N M S M WDM RTCT SDH WDM SDH SWITCH BS NM Screen EM Screen NM Screen GUI S M

52. 52 GUI of NW Management system

53. 53 Benefit to customer Web-based Business Process Management SystemWeb-based Business Process Management System –Reduce Operators Skills / Training –Prevent Operators Mistakes (Enforce Procedures and Policies to ensure quality work ) –Coordination (Different People and Applications work together to do a task) Process Monitor and Control for Customer SatisfactionProcess Monitor and Control for Customer Satisfaction –Process/application monitoring allows the operation to be streamlined –Work distribution among operators allows escalation and automatic distribution of tasks. Fully integrated to Fujitsu NMSFully integrated to Fujitsu NMS –Accurate Real-time Information of Network Condition and Inventory. Flexible Integration to Other Systems / ApplicationsFlexible Integration to Other Systems / Applications –Seamless Information Flow between People, Application and Network –Extensible and Customizable Installation and Configuration

54. 54 Proof of interoperability - TMF Catalyst Project - Business Challenges Objectives Benefit to Industry –Network Operators and Service Providers –Equipment Vendors –End Customers Scenarios Participants Copyright © FUJITSU LIMITED, 1998

55. 55 Catalyst Project Teams Common Interconnect Gateway Platform Connection Management Customer-Provided Trouble Ticket Management Plug & Play End-to-End Service Assurance Plug & Play Service Fulfillment

56. 56 SONET Interoperability Demo Network Management Service Management Business Management Network Elements Element Management CORBA Common IM Key Aspects of the NMS-EMS Interface Solution: Open and Accessible Leveraged off of key enabling technologies, (CORBA) Common Information Model derived from existing standards.

57. 57 SONET Interoperability Demo Objective: Enable Network Manageability of Complex SONET Networks Composed of Multi-Vendor, Multi-Technology, Heterogeneous Equipment. Solution: Define Common, Open Interface at the NML- EML Reference Point. Demonstration: Illustrate End-to-End Connection Management across a real SONET network

58. 58 Connection Management SONET Interoperability Demonstration

59. 59 End-to-End provisioning of IP and ATM services IP/ADSL DSLAM Web VoD Modem ISP ATM SDH CaSMIM Catalyst End-to-End provisioning of IP and ATM services ADSL/IP Domain Astracon ATM Domain Compaq TeMIP SDH Domain FLEXR-NM FLEXR-EM ATM TP SDH TP SM NM EM CaSMIM Interface (CORBA/IDL) IP TP Service Received Servic e Offere d Astracon

60. 60 Connectivity and Service Management Service Layer Cross Domain Technology Domain Existing EMS/NMS

61. 61 Connection Management Multi-Protocol Demonstration