Sprint’s Early Interest in TINA-C

1. Sprint’sEarly Interest inTINA-C

2. Introduction • Sprint had a number of projects during the 1991 through 1994 time-period aimed at unifying the architecture used to build computer systems. • Drivers • Cost of duplication of data and functions in computer systems • Development for each product or service • Multiple order entry systems - voice and each data product (X-25, FR, IP, ATM) • Cost of maintaining interfaces between systems • As services become more complex, interface maintenance is significant drain on resources • Ability to manage multiple services over ATM • Frame Relay over ATM, IP over ATM, Voice over ATM, Voice using ATM • Fault Management needs to be able to correlate alarms from all network elements • Separate systems for each element type require manual interpretation of alarms • Need for very fast service (product) development • First to market gets a disproportionately large share of sales • Focus - 2 main categories • Technical architecture - how systems are built • Functional architecture - grouping like functions - build each process once • Data architecture depends on these being defined first

3. Functional Architecture • My involvement has been with the functional architecture for which there are a number of names: • Enterprise Total Computing - ETC • My preference - its scope is all functions except Human Resources and Stockholder Services • Integrated Service Management - ISM • Used by Sprint associates since 1993 - we were unaware of the GE-Bull product, ISM. • Misleading as many think it only includes network and element management. • Communications Business Model - CBM • Used by those Sprint developers responsible for including new developments from both TINA and Telemanagement Forum. • 2 Primary Approaches • Top down - business developers saw many functions that used a single network • Bottom up - the traditional TMN pyramid, heavy at element level and ignoring business complexity • Merged Functional Architecture - ISM - December 1994

4. Components • Standards based whenever possible • Industry standards for common objects • Open systems interfaces • Electronic bonding for network management interfaces • Functional Architecture • Grouping of processes by function to simplify reuse of common procedures • Will be replaced by an Object Architecture when analysis and design are sufficient • Data Architecture • Enterprise Object Model developed and being tested and improved • Program View - grouping of functions for re-engineering by: • Service Creation • Service Delivery • Service Assurance • Billing • Asset Management • Planning

5. Functional Architecture (before TINA) Corporate Strategic Planning Financial Management Accounts Payable Management Sales Management Customer Service Customer Invoicing Operations Management Market Analysis & Planning Resource Modeling & Planning Marketing Strategy Implementation Vendor Contract Management Accounts Receivable Management Customer Product Request Management Service Capability Assembly Service Capability Development ServiceRequest Validation Service Configuration Service Status Analysis Service Event Integration & Rating Network Capability Customization Capacity & Capability Management Work Force Management Fault Isolation & Integration Performance Analysis Bandwidth Allocation Materials & Inventory Management Testing Integration Usage Analysis Element Management

6. The TINA Discovery • A Sprint colleague met Hendrik Berndt in 1994 or 1995 • Have you looked at TINA? • We looked at TINA • Many man years of expert work was available for us to improve ETC • The documentation included the reasons for decisions: • Why items were in or out • What was need to complete them (e.g. IDL --> ODL) • Many of our conclusions were reinforced • Most of it made sense • We discussed a few problems with Hendrik who was often in KC • Many carriers with whom we interface were TINA-C members • Using TINA would help when developing future interfaces • Our enterprise object model incorporated TINA concepts • We made some changes to our functional architecture

7. Functional Architecture (with TINA-C changes) Corporate Strategic Planning Financial Management Accounts Payable Management Sales Management Customer Service Customer Invoicing SECURITYMANAGEMENT SESSIONMANAGER Market Analysis & Planning Resource Modeling & Planning Marketing Strategy Implementation Vendor Contract Management Operations Management Accounts Receivable Management Subscription Management Service Capability Assembly Service Capability Development Service Management Service Event Integration & Rating Network Capability Customization Capacity & Capability Management Work Force Management Fault Isolation & Integration Service & Subscriber Analysis Performance Analysis Usage Analysis Testing Integration ConnectionManagement Resource Configuration Configuration Fault Usage Data

8. Configuration Management - Network Provisioning SECURITY MANAGEMENT SECURITYMANAGEMENT SESSION MANAGER SESSIONMANAGER Corporate Strategic Planning Market Analysis & Planning Marketing Strategy Implementation Resource Modeling & Planning Vendor Contract Management Operations Management Capacity & Capability Management Work Force Management Resource Configuration Testing Integration ConnectionManagement Configuration

9. Configuration Management - Service Provisioning Sales Management Customer Service Subscription Management SECURITYMANAGEMENT SESSIONMANAGER Service Capability Assembly Service Management Service Capability Development Network Capability Customization ConnectionManagement Resource Configuration Testing Integration Work Force Management Configuration

10. Accounting Management SECURITYMANAGEMENT SESSIONMANAGER Customer Service Accounts Receivable Management Customer Invoicing Service Event Integration & Rating Work Force Management Service & Subscriber Analysis Usage Analysis Fault Isolation & Integration Performance Analysis Fault Usage Data

11. Fault Management SECURITYMANAGEMENT SESSIONMANAGER Accounts Payable Management Vendor Contract Management Customer Service Accounts Receivable Management Customer Invoicing Operations Management Service Event Integration & Rating Fault Isolation & Integration Work Force Management Service & Subscriber Analysis Usage Analysis Performance Analysis Testing Integration Configuration Fault Usage Data

12. Performance Management SECURITYMANAGEMENT SESSIONMANAGER Accounts Payable Management Vendor Contract Management Customer Service Accounts Receivable Management Customer Invoicing Operations Management Service Event Integration & Rating Fault Isolation & Integration Performance Analysis Service & Subscriber Analysis Usage Analysis Testing Integration Configuration Usage Data

13. Communications Business Model SECURITYMANAGEMENT SESSIONMANAGER Corporate Strategic Planning Financial Management Accounts Payable Management Sales Management Customer Service Customer Invoicing Market Analysis & Planning Resource Modeling & Planning Marketing Strategy Implementation Vendor Contract Management Subscription Management Operations Management Accounts Receivable Management Service Capability Assembly Service Capability Development Service Management Service Event Integration & Rating Network Capability Customization Capacity & Capability Management Work Force Management Fault Isolation & Integration Service & Subscriber Analysis ConnectionManagement Performance Analysis Usage Analysis Resource Configuration Testing Integration Service Delivery Asset Management Service Assurance Configuration Usage Data Fault Service Creation Planning Billing

14. ETC, TINA-C, & TMN Comparison Enterprise Total Computing Business Processes Native Computing & Comm DPE Service Providers Services agent User Session IN Services { agent Network Manager TMN Functions Resources Communications Provider Element Manager BBIN Elements Elements Session Computing Hardware TINA-C Current ETC Assumptions: Business Processes are linkages to Services DPE uses CORBA ORBs

15. Connection Manager (CM) System Diagram Legacy Systems PhysicalNetworkResource Order Management GUI Application Frameworks TopologyManagement Subnetwork Proxy [Vendor independent / Technology Specific] Connection Performer [System dependent / Device Specific]

16. Connection Manager - Components • Topology Manager • TINA-C Based Model • ATM Bandwidth Management and PVC Routing • Service Inter-working & Adaptation Between Technologies • Business Rules for Network Utilization • CORBA Interface to CP Based on M4 Model • Network Address Management • Physical Network Resource • Provide Mechanism for Instantiating Network Resources • Element, Card, Port, Link with Capabilities • Domains (Administrative, Management) • Networks (Grouping Container for Elements and Networks) • CORBA Interface to CP/SA for Topology Changes • Interface to the Topology Manager for Logical Representations • Order Manager • Provide Mechanism for Instantiating Owner & Order Objects • Schedule Order Flow Through Connection Manager • Framework Supports the Definition of any Process • Provides Validation of ATM, Frame Relay & IP Services • Exposes an External Interface for Service & Owner Info

17. Connection Manager - Components (continued) • Application Framework • Provides for a Common GUI Framework • Graphical View of Network Topology • Hierarchical Lists for Networks, Customers, Ordes • Persistence Layer Framework • Logging Services • Security • Reporting Tool • On-Line Help Tool

18. Connection Performer (CP) System Diagram Other Connection Manager Systems Subnetwork Proxy [Vendor independent / Technology Specific] Connection Performer Element Agent Location Services Element Agents Element Agents Element Agents Element Agents System/Vendor Dependent Agents CPE Legacy Systems ATM IP