Sprints Early Interest in TINAC

1
SprintsEarly 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
Customer Service
Customer Invoicing
Accounts Payable Management
Sales Management
Operations Management
Accounts Receivable Management
Market Analysis Planning
Marketing Strategy Implementation
Vendor Contract Management
Customer Product Request Management
Resource Modeling Planning
Service Status Analysis
Service Capability Assembly
Service Configuration
Service Event Integration Rating
Service Capability Development
ServiceRequest Validation
Capacity Capability Management
Work Force Management
Network Capability Customization
Performance Analysis
Fault Isolation Integration
Materials Inventory Management
Bandwidth Allocation
Usage Analysis
Testing Integration
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
Customer Service
Customer Invoicing
Accounts Payable Management
Sales Management
SECURITYMANAGEMENT
SESSIONMANAGER
Accounts Receivable Management
Operations Management
Market Analysis Planning
Marketing Strategy Implementation
Vendor Contract Management
Subscription Management
Resource Modeling Planning
Service Capability Assembly
Service Management
Service Event Integration Rating
Service Capability Development
Capacity Capability Management
Service Subscriber Analysis
Work Force Management
Network Capability Customization
Fault Isolation Integration
Usage Analysis
Testing Integration
Performance Analysis
Resource Configuration
ConnectionManagement
Fault
Configuration
Usage Data
8
Configuration Management - Network Provisioning
SECURITY MANAGEMENT
SESSION MANAGER
SECURITYMANAGEMENT
SESSIONMANAGER
Corporate Strategic Planning
Market Analysis Planning
Marketing Strategy Implementation
Operations Management
Vendor Contract Management
Resource Modeling Planning
Work Force Management
Capacity Capability Management
Resource Configuration
Testing Integration
ConnectionManagement
Configuration
9
Configuration Management - Service Provisioning
Customer Service
Sales Management
Subscription Management
SECURITYMANAGEMENT
SESSIONMANAGER
Service Capability Assembly
Service Management
Service Capability Development
Network Capability Customization
Resource Configuration
ConnectionManagement
Work Force Management
Testing Integration
Configuration
10
Accounting Management
SECURITYMANAGEMENT
SESSIONMANAGER
Customer Service
Customer Invoicing
Accounts Receivable Management
Service Event Integration Rating
Work Force Management
Service Subscriber Analysis
Usage Analysis
Fault Isolation Integration
Performance Analysis
Usage Data
Fault
11
Fault Management
SECURITYMANAGEMENT
SESSIONMANAGER
Customer Service
Customer Invoicing
Accounts Receivable Management
Vendor Contract Management
Accounts Payable Management
Operations Management
Service Event Integration Rating
Fault Isolation Integration
Work Force Management
Service Subscriber Analysis
Usage Analysis
Testing Integration
Performance Analysis
Fault
Usage Data
Configuration
12
Performance Management
SECURITYMANAGEMENT
SESSIONMANAGER
Customer Invoicing
Accounts Receivable Management
Customer Service
Vendor Contract Management
Accounts Payable Management
Operations Management
Service Event Integration Rating
Performance Analysis
Fault Isolation Integration
Service Subscriber Analysis
Usage Analysis
Testing Integration
Configuration
Usage Data
13
Communications Business Model
SECURITYMANAGEMENT
SESSIONMANAGER
Corporate Strategic Planning
Financial Management
Customer Service
Customer Invoicing
Accounts Payable Management
Sales Management
Accounts Receivable Management
Operations Management
Market Analysis Planning
Marketing Strategy Implementation
Vendor Contract Management
Subscription Management
Resource Modeling Planning
Service Capability Assembly
Service Management
Service Event Integration Rating
Service Capability Development
Capacity Capability Management
Service Subscriber Analysis
Work Force Management
Network Capability Customization
Fault Isolation Integration
Resource Configuration
ConnectionManagement
Usage Analysis
Testing Integration
Performance Analysis
Service Delivery
Asset Management
Fault
Configuration
Usage Data
Service Assurance
Service Creation
Planning
Billing
14
ETC, TINA-C, TMN Comparison
Enterprise Total Computing
Business Processes
Native Computing Comm
DPE
Services
Service Providers
User Session
agent
IN Services

agent
Network Manager
TMN Functions
Resources
Communications Provider
Element Manager
BBIN
Elements
Elements
Session
Computing
Hardware
Current
TINA-C
ETC Assumptions
Business Processes are linkages to Services
DPE uses CORBA ORBs
15
Connection Manager (CM) System Diagram
Legacy Systems
PhysicalNetworkResource
Order Management
Application Frameworks
TopologyManagement
GUI
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

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 Agents
Element Agent Location Services
Element Agents
Element Agents
Element Agents
System/Vendor Dependent Agents
Legacy Systems
IP
ATM
CPE