Solving OSS Challenges through Standards

1. Solving OSS Challenges through Standards Global OSS Summit 2001 Session A3 9:45 a.m.-11:15 a.m. Tuesday, March 6, 2001 Miami, Florida

2. ATIS Overview • A member organization of U.S. and North American telecommunications companies that represent every segment of the industry. • The sponsor of sixteen critical industry committees, which address the most pressing technical, operational issues affecting telecom facilities and services. • ATIS activities involve 3,000+ participants from 400+ telecommunications companies. • Provides an open, established environment where the industry reaches consensus on technical, operational, and business issues.

3. ATIS Overview ATIS produces telecommunications... • standards • guidelines • operating procedures • verification testing . . .that provide innovative responses to complex industry problems. . . .that speed new telecommunications products and services to market.

4. For More Information ... • See ATIS staff • John Bernhards, Director of Marketing and Public Relations, jbernhards@atis.org, 202-434-8850 • Kristen Nye, Business Development Specialist, knye@atis.org, 202-434-8837 • Visit ATIS Booth Number 513

5. Speakers • Stephanie Cowart (Chairperson), Manager, Billing, BellSouth, and Ordering and Billing Forum (OBF) Moderator • Michael Fargano, Distinguished Member of Technical Staff, Qwest, and T1M1 Chairman • Jan Johnson, Industry Staff Specialist, WorldCom, Inc, and Advisor/Coordinator of the OBF/T1M1/ECIC Cross-Forum Team • Debbie Stipe, Director of Market Development, Cap Gemini Ernst & Young, and TCIF Chair

6. Stephanie Cowart OBF Moderator BellSouth 205/321-2878 stephanie.cowart@bridge.bellsouth.com Ordering and Billing Forum Structure and InitiativesMarch 6, 2001

7. OBF Mission • To provide a forum for customers, providers and vendors in the telecommunication industry to identify, discuss and resolve national issues which affect ordering, billing, provisioning and exchange of information about access services, other connectivity and related matters.

8. OBF Process • Participation: 400+ representing 90+ companies • Meeting Frequency: quarterly in week-long General Sessions; Interim meetings scheduled to meet work load • Activity virtually on-going • Nature of Outputs: design of or changes to business processes which include: • Specific interface guidelines • Informational requirements

9. OBF Top Initiatives • UNE Remand Issues • Line Sharing Issues • Internet Protocol Detail Record Interfaces • Digital Subscriber Line Services • Uniform Order Modeling Implementation • SMS/800 System Constraints • National Repository for Line, Switch and Company Level Information

10. Seven OBF Standing Committees • Billing (BLG) Committee • Addresses access and local interconnection billing related issues. • Directory Services (DSC) Committee • Addresses issues pertaining to the ordering and exchange of end user listing information • Interconnection Services Ordering (ISOP) Committee • Responsible for all business processes and documentation management associated with the Access Services Ordering Guidelines (ASOG)

11. Seven OBF Standing Committees • Local Services Ordering (LSOP) Committee • Responsible for all business processes and documentation management associated with the Local Services Ordering Guidelines (LSOG) • Message Processing (MSG) Committee • Addresses non-access issues relative to message processing and maintains the Exchange Message Interface (EMI) document

12. Seven OBF Standing Committees • Subscription (SUB) Committee • Addresses national subscription issues and maintains the CARE document • SMS/800 Number Administration (SNAC) Committee • Addresses issues related to the toll free number administration

13. BLG Committee Meri-Louise Thompson, AT&T Randall Reeves, BellSouth DSC Committee Sharon Neighbors, SBC Andy Fitzsimmons, AT&T ISOP Committee Debbie Sartino, BellSouth Georgina Young, AT&T LSOP Committee Christine Cole, Verizon Gail Grenier, MCI Worldcom MSG Committee Chris Read, SBC Pat Keatley, Telus SUB Committee Frank Culmone, Verizon Dave Thurman, Sprint SNAC Pat Parker, Verizon Leslee Strohm, Qwest OBF Committee Co-Leaders

14. OBF/IPDR Organization Activities • Message Processing Issue 2101 opened at OBF #69 on February 10, 2000 • Desired Result of the Issue • Initiate a liaison with the Internet Protocol Detail Record Organization to establish guidelines for IPDR record exchange to bill IPDR Usage Records (VoIP) in Billing Systems outside of the IP Network arena (e.g., a wire-line or wireless customer). • Issue Champions • Marcia Lucus, AT&T Broadband • Kelly Anderson, SCC Communications

15. Exchange Message Interface • General Description • The EMI is a guideline used for the exchange of telecommunications message information between Sending and Billing Companies. Data is provided between companies via multiple unique record layouts that contain message data, customer billing information, account summary information and tracking analysis.

16. Exchange Message Interface • Types of Records • End User Billing • Access/Local Interconnection Billing • Informational, Statistical, Notification • Settlements • Miscellaneous

17. IPDR/OBF Liaison • Message Processing Letter to IPDR dated August 20, 2000 • Requested a formal liaison be established between OBF and IPDR • OBF #71 Activities • Kelly Anderson, SCC Communications, is the IPDR Liaison to the OBF Message Processing Committee • Consensus to establish an OBF Message Processing Committee Liaison to the IPDR Organization • OBF Message Processing Task Force established • Mike Norris, Telus • Kelly Anderson, SCC Communications

18. IPDR/OBF Activities • Possible new issue to be opened at OBF #74 • Requesting new EMI record types be established for exchange of information between IP companies and telecommunications companies • End User Records • Access/Local Interconnection Records • Task Force is reviewing other possible IP message exchange requirements • More OBF issues will be opened as new record exchange requirements are identified.

19. For More Information……. • Visit the ATIS/OBF website at: • http://www.atis.org/atis/clc/obf/obfhom.htm

20. T1M1Business Driven OAM&P Standards Michael J. Fargano - T1M1 Chairman (Qwest, 303-541-6081, mfargan@qwest.com) March 6, 2001

21. Outline • OAM&P/OSS Challenges • T1M1 Strategy • T1M1 Basic Value proposition • OAM&P Simplified Systems Interface Reference Model • Major Initiatives: • Overview • 2000 Highlights • 2001 High Level Plans • T1M1 Leadership Team

22. OAM&P/OSS Standards Challenges • OSS/OSS interconnect • Rapidly changing IT environment (to facilitate network management) • Rapidly changing network technology environment (to be managed)

23. T1M1 Strategy • Market Driven approach, e.g.: • Rapid adopter of technology that needs standards • Implementation centric mindset, i.e., the wide availability of implementations being the measure of success • Focus on Industry Priorities: Leverage industry priorities and industry fora collaborations • Attract and Retain Talent: Challenging work with growth potential; Fair & open process for interests

24. T1M1 Basic Value Proposition • Provide high interest and essential telecommunications OAM&P guidelines, requirements, and standards • Support voluntary and mandated systems interoperability in a rapidly changing industry • Business value seen in operations cost reductions, opening of markets, improved time to market for services, and scaling of services and operations. • The end result is an effective and efficient multi-supplier and multi-service-provider telecommunications OAM&P environment.

25. OAM&P Simplified Systems Interface Reference Model Suite of standard telecomm B2B (interconnect) interfaces (CORBA, CMIP, EDI, ...); including tML(XML T1M1/ITU work) X Core OSS Infrastructure Q Standard T1M1/ITU CORBA (going forward); potential tML (XML) play Q EMS Infrastructure Various standards (i.e., SNMP, CMIP, CORBA, MML, TL1 …) Q Network Infrastructure

26. Major Initiatives - Overview The following major initiative areas categorize the T1M1 work efforts and value delivery: • Common OAM&P Functionality and Technology • Inter-Administration OAM&P • Network Technology Specific OAM&P

27. Common OAM&P Functionality and Technology • Basic Value: Standards efficiency and industry efficiency via common frameworks and models • ANSs and key contributor to and driver of ITU, e.g: • CORBA Framework and Information Model for OAM&P • tML (XML) Framework for OAM&P • Public Key Infrastructure (PKI) for TMN Security • Alarm Report Control (ARC) Function

28. Inter-Administration OAM&P • Basic Value: Provide for interoperability among service providers • Collaboration with other ATIS Fora, e.g., OBF, TCIF • Common Language for Information Interchange - Provides the structure and coding of information that is essential for inter-administration communications, e.g., Identification of IP NEs • OSS to OSS Interconnect Interface Applications - Provides for applications that are essential for automated inter-administration communications, e.g, Local Pre-Order

29. T1M1 and Other ATIS Fora Collaborations • Business Requirements (e.g., OBF - OSS/OSS Interconnect) • Technical Guidelines (e.g., TCIF - Implementation) Other ATIS Fora (e.g., OBF &TCIF) • Written Liaison • Personal Liaison • Joint work teams (e.g., Unified Ordering Model team) • ANSI Accredited Standards Formulation Process • OAM&P Standards T1M1

30. Network Tech Specific OAM&P • Basic value: Network tech specific OAM&P inter-op among service providers' and suppliers' systems (OSS, EMS, NEs, …) • Various types of collaborations with T1 TSCs and other forums, i.e., joint work, support work, etc. • Transport layer 1 in-service digital performance monitoring: T1.231.x - general/common and specific documents (OTN, SONET, xDLS, DSx,…) • Optical Networking OAM&P: Major in-progress work effort - joint work between T1X1 and T1M1 • Other areas: SS7, IP Telephony, and Wireless

31. 2001 High Level Plans • Common OAM&P Func and Tech: Continued expansion - tML (framework, etc.) and CORBA (Alarm Surveillance and Performance Mgt) • Inter-Admin OAM&P: High interest common language standards (e.g., Company Code expansion); mandated and high interest OSS interconnect standards (e.g., Unified Ordering Model); first tML application standard is expected • Network Tech Specific OAM&P: Continued support for high interest network technology standards (i.e., Optical Networking, xDSL, Wireless, etc.)

32. T1M1 Leadership Team • T1M1 Vice Chairman - Jim Stanco (Siemens) • T1M1.3 (Al White - Chair / Sprint LD, Bill Cardarette - Vice Chair / Motorola Broadband, Bill Goodson - Secretary / Lucent) • Transport - Jon Neubaum (Tellabs) • Common Language - Paul Levine (Telcordia) • Signaling & Protocol - Norb Lucash (USTA) • T1M1.5 (Gopal Iyengar - Chair/Nortel, John Portschy - Vice Chair/Lucent, Greg Bain - Secretary/NCS) • Architecture - Beth Marshburn (Lucent) • Management Services - Lakshmi Raman (Teraburst) • Ordering & Billing - Brian Bearden (SBC) • Security - Bob Barker (Verizon) • Unified Ordering Model AHG - Jay Whitney (WorldCom) • tML AHG - Ed White (WorldCom) • Information Director - Beth Marshburn (Lucent)

33. Conclusion • Business value provided: • Operations cost reductions • Opening of markets • Improved time to market for services • Scaling of services and operations • Goal: • Effective and efficient multi-supplier and multi-service-provider telecommunications OAM&P environment

34. IEC OSS Global Summit 2001 OSS Challenges and Standards Presented by: Debbie Stipe, Cap Gemini Ernst & Young TCIF Chair dstipe@usa.capgemini.com (904) 491-0201

35. TCIF Purpose and Scope • Develop guidelines for use by the telecommunications industry that facilitate effective information exchange among trading partners • Use existing voluntary standards and/or industry requirements related to the exchange of information

36. TCIF Value Proposition Facilitate Bi-lateral definition and implementation • Implementation Requirements for a uniform industry solution • Identify and resolve the issues effecting the implementation of mechanized interconnection • Identify cost effective solutions • Strike a balance between technology & business process

37. Telecommunications Industry Forum

38. OSS Challenges • Telecom Act • Local Competition • Open OSSs • New Technology • Corba • XML • Regulatory Mandates • PIC Requirements

39. TCIF Highlights • Response to the Telecom Act • Industry agreement reached on technology to support local ordering • SOSC defines the EDI specifications for the implementation of the LSOG (OBF defined Local Service Ordering Guideline) • ECIC developed Generic Implementation Guidelines for Local Ordering using EDI, TCP/IP and Local Pre-order using Corba • ECIC developed a technical specification (Interactive Agent) enabling rapid and secure transport of Local Order transactions

40. TCIF Highlights • React to the FCC • The California PUC Slamming Cramming rulemaking required the development of new data elements to support PIC changes • OBF, T1M1 and ECIC worked together to deliver the required data elements, process flows and documentation eight weeks before PUC deadline

41. TCIF Highlights • Technology Advances • Worked with T1 to define Corba Pre-order interface for Local • Investigating the formation of a committee to support XML

42. TCIF Leadership

43. TCIF Leadership • EDI Committee • SOSC Chair - Buzz Swanston, SBC Vice Chair - Carolyn Mitchell, Accenture / BellSouth • TBWG Chair - Nancy Porter, Verizon Vice Chair - Jim Horton, QWEST • Guideline Consistency TBD

44. TCIF Leadership • ECIC • Access Ordering Co-chair1 – Jay Whitney, WorldCom Co-chair2 – vacant • Trouble Administration Co-chair1 – Glen Cantrell, SBC Co-chair2 – Dan Busetti, QWEST • Pic/CARE Co-chair1 – Gary Baker, BellSouth Co-chair2 – Morgynne North, Verizon • LOPO Co-chair1 – Barbara Wallace, BellSouth Co-chair2 - vacant • Technology Support Co-chair1 – Bob Buegler, Sprint Co-chair2 – Jim Bertsch, Mantiss

45. TCIF Leadership • BCSC • Product Change Administration Dennis Miller, Fujitsu • Product Marking Bob Fox, Telcordia • Shipping Label Committee Allan Gilligan, Lucent • U.P.C. Implementation Bob Fox, Telcordia

46. Conclusion The TCIF will work toward developing a greater understanding and coordination of existing voluntary standards and guidelines relating to the exchange of information for provision, procurement, and use of telecommunications equipment, products, and services. Where appropriate or necessary standards do not exist, the TCIF will act as a catalyst to ensure that an appropriate standards setting organization addresses the need for such standards.

47. Unified Ordering Model (UOM) Jan Johnson - OBFWorldCom 972-792-5690 Jan.Johnson@wcom.comMarch 6, 2001

48. Outline • Challenges of Service Ordering • UOM Strategy • UOM Benefits • 2001 UOM Project Plans • 2001 UOM Meetings • Cross Forum Team Leadership

49. Challenges of Service Ordering • Telecommunication Companies have different OSS Systems • Individual specific Business Requirements dictate • Unique data models • Different processing flows • Legacy Service Ordering standards have their basis in paper forms and early mainframe batch implementations • Originally forms were mailed and eventually faxed. • Electronic application to application legacy interfaces are based on transporting mainframe text files with many batch transactions via. NDM. • NDM (batch method) doesn’t support the accurate and timely gathering of information of Service Order Requests by provisioners.

50. Challenges of Service Ordering (Cont.) • Legacy Service Ordering standards are confined to ordering and ordering responses. • Pre-Order and Post-Order phases are manually accomplished through manual faxes or telephone calls, which is non-productive and often costly. • There is currently not a standard for Post-Ordering Inquiries for Access Ordering. • Pre-competition, large Telecommunication Companies using legacy interfaces were traditionally limited to providing interfaces only with each other. • In today’s environment, competition requires larger telecommunication companies interface with a variety of different size companies who use various methods of issuing Service Requests.