Configuration Management Support forLong Haul C2 Circuit Switched Services

Robert SlighThe MITRE Corporation

M/S W6557515 Colshire Drive

McLean, VA 22101-7508

George WongThe MITRE Corporation

M/S W6557515 Colshire Drive

McLean, VA 22101-7508

Sandi VestCenter for DISN Services

Defense Information System Agency5275 Leesburg Pike

Falls Church, VA 22041

Report Documentation Page Form ApprovedOMB No. 0704-0188

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if itdoes not display a currently valid OMB control number.

1. REPORT DATE SEP 2002 2. REPORT TYPE

3. DATES COVERED 00-00-2002 to 00-00-2002

4. TITLE AND SUBTITLE Configuration Management Support for Long Haul C2 Circuit SwitchedServices

5a. CONTRACT NUMBER

5b. GRANT NUMBER

5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S) 5d. PROJECT NUMBER

5e. TASK NUMBER

5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) The MITRE Corporation,7515 Colshire Drive M/S W655,McLean,VA,22101-7508

8. PERFORMING ORGANIZATIONREPORT NUMBER

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)

11. SPONSOR/MONITOR’S REPORT NUMBER(S)

12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited

13. SUPPLEMENTARY NOTES The original document contains color images.

14. ABSTRACT

15. SUBJECT TERMS

16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT

18. NUMBEROF PAGES

14

19a. NAME OFRESPONSIBLE PERSON

a. REPORT unclassified

b. ABSTRACT unclassified

c. THIS PAGE unclassified

Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18

Abstract

To ensure our warfighting edge in information superiority across all joined forces, we must keeppace with technology advancement and build a state of the art network infrastructure that canadapt to changing needs and provide fast and reliable service delivery anytime, and anywhere inthe world. This paper addresses the challenges that the Defense Switched Network (DSN) faces,and offers a Configuration Management (CM) solution that is built upon a common DSN CoreCM database with automated support systems to support integration of various NetworkManagement functions.

1.0 IntroductionThe primary function of the Defense Switched Network (DSN) is to provide non-secure dial-upvoice service. It also supports Switched Data and dial-up Video Teleconferencing (VTC) for theDepartment of Defense (DOD) common-user video teleconferencing system. The DSN supportsthree types of users: Special C2 Users, C2 Users, and Other Users.

Within DSN, there are multiple organizations that take part in the overall DSN Program. Eachorganization is responsible for a certain operational functions and performs a sub-section of theConfiguration Management process (identification, audits, control, and status accounting). MostCM functions are performed manually and have received minimal automated support. This wasdue to Operations and Maintenance needs, which dictated that automation efforts focus on Faultand Performance management.

1.1 Purpose

This paper addresses how Configuration Management (CM) will be enhanced, automated, andapplied in support of the Defense Switched Network (DSN). It includes the approach indeveloping requirements, a summary description of the functional model used in analyzingexisting processes and modifying and/developing additional processes, the operational concept,the development and implementation approach and current status.

1.2 Limitation

This paper focus on the DSN and its long-haul circuit switched services. Other networks andservices within the Defense Information System Network (DISN) are not being addressed hereinbut will be incorporated after the DSN CM is operational.

1.3 Background

To ensure our warfighting edge and information superiority across all joined forces, we mustkeep pace with technology advancement and build a state of the art network infrastructure thatcan adapt to changing needs and provide fast and reliable service delivery anytime, anywhere inthe world. To achieve this objective, DISA must form a solid foundation that combinesintelligent network platforms with sound management principles and a well-engineeredinformation infrastructure. With this foundation, DISA can capitalize on new technologies whilecontinuing to meet our rapid customer service and applications delivery requirements. Figure 1

depicts the overall transformed DSN concept and its role in the future telecommunicationsenvironment.

Figure 1 Transformed DSN Concept and Vision

As shown in Figure 1 the key element that integrates all entities within the foundation underDISA’s control as well as those entities external to DISA is Configuration Management (CM).Without CM it is almost impossible to satisfy performance requirements. Therefore DISA isconstantly looking to improve its CM capability. The criticality of good CM becomes mostobvious in tension-crisis situations where system elements must be quickly adjusted or deployedwith high reliability in an unstructured situation. Much time and performance is saved when thefield forces “get it right the first time”.

This paper will articulate how CM will be applied in support of the vision for long-haul inter-switch circuit switched services and end–to–end Command and Control circuit switchedservices.

CUSTOMERS/WARFIGHTERS

BUSINESS

DECCDMS

GCCS GCSS

APPLICATIONS

• Near-real Time Service Provisioning/Configuration• On-demand Status/Performance Reporting• Trouble Management/Resolution System• New Application Development• Multi -Media Desktop Information Delivery

Customer CareProject Management

Network Interface

Network Applications

FOUNDATION

Sub-NetworkSub-Network

Intelligent Network Platform

Sub-NetworkSub-Network

Sub-Network

NETWORKS

Network Operations

Implement

Acquire

Plan

Requirements

Assess/Survey

Information Infrastructure Management Model

Information Database

OthersCM

Planning

Engineering

Provisioning

Operations

Billing

Security

CM

CM

CM

CM

CM

CM

CoreConfigurationManagement

(CM)Database

CM Functions

CM Functions

CM Functions

CM Functions

CM Functions

CM Functions

2.0 Current System Description

DSN consists of multiple systems and sub-systems that represent voice circuit switches(Multifunction Switches and End-office Switches), transmission facilities, timing andsynchronization, signaling, operation centers, integrated network management systems, varioussoftware and hardware components, and customer premises equipment. It interconnects with theMilitary Department’s (MILDEP’s) base/post/camp/station facilities to provide inter-basecommunications. Refer to Figure 2 below.

Figure 2 Defense Switched Network (DSN) System Overview

Due to the diverse geographical locations, DSN is further separated into four operating Theaters:WESTHEM (including Continental US (CONUS), Puerto Rico, the Azores, and Iceland), Pacific(including Alaska), Europe, and CENTCOM (previously Central Area/Southwest Asia). Due tothe unique environments, the network within each Theater consists of different vendor hardware,software, operating procedures, and support systems.

P S N / P T T / F T S / G E T S

D S NS w i t c h i n g

N o d e

D S NS w i t c h i n g

N o d e

D S NS w i t c h i n g

N o d e

D S NS w i t c h i n g

N o d e

E n dO f f i ce

E n dO f f i ce

T r a n s m i s s i o n F a c i l i t i e s

L o c a l M e t r o A r e a

L o c a l M e t r o A r e a

E n dO f f i ce

E n dO f f i ce

V o i c eF a x

V o i c e -B a n d D a t a

V o i c eF a x

V o i c e -B a n d D a t a

V o i c eF a xV o i c e -B a n d D a t a

V o i c eF a xV o i c e -B a n d D a t a

L o c a l M e t r o A r e a

L o c a l M e t r o A r e a

S M U S M U

S M U S M U

S i g n a l i n g , T i m i n g a n d S y n c h r o n i z a t i o n S y s t e m s

I n t e g r a t e dN e t w o r k M a n a g e m e n t

S u p p o r t S y s t e m

O t h e r G o v e r n m e n t N e t w o r k s a n d S y s t e m s

3.0 Approach/SolutionDefense Switched Network (DSN) Configuration Management is the technical andadministrative process used to identify and document functional and physical characteristics ofthe DSN network. CM also controls changes to those characteristics, records, and reports onchange processing. CM ensures that proposed changes to the network’s configuration arereviewed and approved by management before implementation. Once implemented, networkchanges are confirmed and recorded. This process helps ensure the baseline network areefficiently managed and network data is accurately presented to support other networkmanagement functions i.e. fault management, performance management, accountingmanagement, and security management.

Because CM data form the basis to support other Network Management functions, it is mostcritical to have a common set of tools and automated system support to ensure CM data ismaintained and shared amongst all the functional groups. In addition, interface agreements andprocedural guidelines (Practices and Procedures, P&P’s) must be established to guide the day-to-day operation of the DSN.

Figure 3 Network Management/CM Information Integration

To combat the challenges that DSN faces, a systematic approach is required to model the currentDSN functions and activities and document/analyze its existing processes. This will help toestablish an overall operational concept; determine process re-engineering; generate automatedsystem support and Practices & Procedures enhancement requirements. Figure 4 illustrates thisapproach.

CM

DS

N In

form

ation

Co

ord

inatio

n &

Integ

ration

D S N N MApplications

D S N N MApplicationsConfiguration

Management

ConfigurationManagement

N e twork Management Funct ions

FaultManagement

FaultManagement

C M

Performance ManagementPerformance ManagementC M

AccountingManagement

AccountingManagement

C M

SecurityManagement

SecurityManagement

C M

Fault Management Database

Performance Management Database

Accounting Management Database

Security ManagementDatabase

•Id

entificatio

n•

Au

dits

•C

han

ge C

on

trol

•S

tatus A

ccou

ntin

g

Configuration ManagementDatabase

Figure 4 DSN CM Approach

The current DSN implementation must be captured and analyzed to form a System Model. Thissystem model provides a blueprint of the DSN functions to include management, planning,engineering, provisioning, and operations. The associated processes within DSN and supportsystems must also be documented and analyzed. The analysis of current DSN processes andsupport systems will help to determine the user and automated support system requirements, aswell as to identify immediate improvements. The current DSN system model will reveal thenetwork elements necessary to operate and manage the DSN as a whole as well as its theaterspecific requirements. The network elements will include all the critical network componentsneeded to provide services to the user community.

An over all DSN CM Operational Concept that is independent of hardware, software andnetwork restrictions must be formed to meet the users’ requirements. The current/existingdatabase systems must be compared to this Operational Concept and network elementrequirements resulting from the DSN modeling. This will allow the formation of implementationpriorities and phase-in approaches that lead to database integration and standardization whileminimizing the impact on existing operations.

Develo

pm

ent an

d Im

plem

entatio

nD

evelop

men

t and

Imp

lemen

tation

A u t o m a t e d C M S u p p o r t

R e q u i r e m e n t s

A u t o m a t e d C M S u p p o r t

R e q u i r e m e n t s

D S N C MR e q u i r e m e n t s A n a l y s i s a n d

R e e n g i n e e r i n g

D S N C MR e q u i r e m e n t s A n a l y s i s a n d

R e e n g i n e e r i n g

D S N C M F u n c t i o n a l

M o d e l

D S N C M F u n c t i o n a l

M o d e l

B a s e d o n i n t e r n a l a n de x t e r n a l o r g a n i z a t i o n a li n f o r m a t i o n f l o w s , C M m o d e l f u n c t i o n s a n d C M p r o c e s s e s

D S N C ME x i s t i n g

O p e r a t i o n a lP r o c e s s

D S N C ME x i s t i n g

O p e r a t i o n a lP r o c e s s

C M P r o o f o f C o n c e p t /

P r o t o t y p i n g

C M P r o o f o f C o n c e p t /

P r o t o t y p i n g

I S O 9 0 0 0I S O 9 0 0 0

O p e r a t i o nC o n c e p t

O p e r a t i o nC o n c e p t

C M P r a c t i c e s & P r o c e d u r e sR e q u i r e m e n t s

C M P r a c t i c e s & P r o c e d u r e sR e q u i r e m e n t s

4.0 DSN CM Functional Model

The DSN management model for CM comprises of functional layers that are tailored toDepartment of Defense (DOD) voice services and networks. The DSN CM Model is developedusing information from DOD standards and guidance, as well as commercial industry standardsand practices, these including:

q DOD, Military Handbook for CM (MIL-HDBK-61a)q DSN Configuration Management Planq ISO/OSI Basic Reference Model for Network Managementq Telestrategies, Operational Support System – Functional Matrixq ITU-T, Telecommunications Management Network (TMN)

Figure 5 DSN CM Functional Model

The 8-layer model focuses on the Management Functions of DSN Configuration Management:

Layer 8: The Business Management Layer represents the highest layer where all high-leveldecisions and strategies are being made.

Layer 7: The next layer of Service Management Layer provides additional feasibility planningof the DSN technologies, configurations, service features, and P&P’s.

Layer 6: Detailed system engineering functions are being done at the TechnologyManagement Layer where items such as Call-routing designs, Signal and

Other Network Equipment

Other Network Equipment

D S N Switch

D S N Switch

Physical (1,2,3)Management Layers(Unit /Sub-Unit /Component)

Link (4)Management Layer

Network Services (5)Layer

Technology (6)Management Layer

Service (7)Management Layer

Business (8)Management Layer

Inter-Switch Trunk (IST)AccessLine

AccessLine

Call RoutingDesign Switching

Voice overIP

SignalingSystems

Timing &Synchronization

(Planning)

Department of Defense (DoD)

DecisionMaking

PolicySetting

StrategyPlanning

DSN CM Funct ional Model

ServiceFeaturesPlanning

Practices &Procedures

ServiceOrder

Distribution

ServiceConfiguration

Planning

Technology/EngineeringFeasibility

ServiceDelivery:

Voice,Data

Video

ServiceDelivery:Voice,DataVideo

CPE CPE

UsersUsersUsersUsersUsersUsers

(High Level Direction Setting)

(Engineering)

(Operations/Provision)

(Change Recording)

Plan

nin

gP

lann

ing

En

gin

eering

En

gin

eering

Hig

h-L

evelH

igh

-Level

Plan

nin

gP

lann

ing

Pro

vision

ing

Pro

vision

ing

Installatio

nIn

stallation Ch

ang

eC

han

ge

Reco

rdin

gR

ecord

ing

Timing/Synchronization systems, and other transport and switching technologies arebeing engineered.

Layer 5: The Network Services Layer focuses on the end-to-end delivery of DSN services(voice, data, and video) to the end-users.

Layer 4: The Link Management Layer provides the management functions for Inter-SwitchTrunks (IST) and access lines that are providing transport the DSN services.

Layer 3/2/1: Each of the lowest three layers (Physical Management Layers) are dedicated tothe functional management of Physical Unit (PU, Layer 3), Physical Sub-unit (PSU,layer 2), and Physical Component (PC, Layer 1).

These eight (8) layers represent the transitioning of Planning (at higher levels), Engineering,Provisioning, Installation, and Operations/Change Recording (at lower levels) within the DSNConfiguration Management structure. There are two-way interactions between each layer andmost interactions are from top down (i.e. from a higher layer to a lower layer).

4.1 Model Comparison

The DOD Military Handbook for CM addresses the procurement and configuration managementstandards for weapon systems. It does not offer a configuration management reference model.The DSN CM Functional Model incorporates the functionality from the DSN CM Plan andHandbook, along with other functions from the ISO (OSI Model), ITU-T (TMN Model), andTelestrategies (OSS).

The OSI Basic Reference Model addresses the interconnection and communication of an opensystem. The DSN CM Functional Model focuses on the various configuration managementfunctions that are specific to Defense Switch Network (DSN). The OSI Model deals with theopen system’s software, hardware, and application. Therefore, the OSI model can only berelated to the DSN’s first five layers (i.e. from Physical Layer up to Network Services layer).The remaining DSN CM Functional Model management layers (Network Technology, Service,and Business) are not covered by OSI.

The ITU-T model is the Telecommunications Management Network (TMN) model. This ITU-Tstandard is used for managing telecommunications networks and the services they provide. TheDSN CM Functional Model resembles the TMN management model.

4.2 Description of Layers within the DSN CM Functional Model

The table below provides a detail description on each of the eight functional layers within theDSN CM Model:

Functions

Layers Planning Engineering Provisioning Installation ChangeRecording

Example

8 BusinessManagement

Layer 8: Business Management Layer

The management of high-level direction setting for DSN services.

Planning ofstrategy,policy, anddecisionmaking

7 ServicesManagement

Layer 7: Services Management Layer

The management of service planning on technology, configuration, andcustomer-focused services.

Planning oftechnologiesfeatures, &ordering

6 TechnologyManagement

Layer 6: Technology Management Layer

The management of technology and engineering in order to deliver DSNservices at the lower DSN CM functional layers.

Engineering& design ofrouting,signaling,switching

5 NetworkInfrastructure

Layer 5: Network Services Layer

The management of DSN services (switched voice, voice-band data, andvideo). This layer represents the operations and end-to-end service deliveryto the users.

Operation ofSwitchedvoice, data,and videoservices

4 LinkManagement

Layer 4: Link Management Layer

The management of Link, or connectivity, between physical layers. Thiscould be the transmission facilities/circuits that connect two DSN switches, oraccess lines that connect the user’s CPE to the DSN.

IST’s andAccess Lines

3Physical

UnitManagement

Layer 3: Physical Unit Management Layer

The management of a physical configuration unit (hardware/software). Thisrepresents the highest level within the three Physical Layers.

DSN Switch,ATM Switch,and PBX

2PhysicalSub-Unit

Management

Layer 2: Physical Sub-Unit Management Layer

The management of sub-unit (hardware/software) within a physicalconfiguration unit.

DSNSwitch’sTrunkModule

1Physical

ComponentManagement

Layer 1: Physical Component Layer

The management of the lowest-level physical configuration item(hardware/software) i.e. components within a unit or sub-unit. Thisrepresents the lowest level within the three Physical Layers.

DSNSwitch’sTrunk Card

Table 1 DSN Functional Model

5.0 Operational ConceptThe critical element of this operational concept is having a common DSN database with a coredatabase structure which allows access by all CM functions. This will allow a standard processof evaluation/recommendation/approval prior to implementing the network changes. Once thechanges are implemented, they will be uniquely identified, audited, and stored within the DSNCore CM Database.

Figure 6 illustrates the proposed DSN CM Operational Concept.

Figure 6 Proposed DSN CM Operation Concept

5.2 DSN CM Database System

The DSN database will provide system interfaces to other existing DSN support systems such asnetwork requirement ordering, provisioning, engineering, planning, accounting, management,and other administration systems. This will facilitate the information sharing necessary tosupport the CM processes of identification, audit, change control, and status accounting. Figure7 shows the DSN CM operation concept with the automated support systems.

SWITCHES- 5ESS’s- SL100’s- PBX’s

TRANSMISSION- Access- Backbone

SUPPORT SYSTEMS- Timing/Synchronization- Signaling

Defense Switched Network (DSN)

User Profiles/Requirements

FaultManagement

SecurityManagement

PerformanceManagement

AccountingManagement

Planning &Engineering

Engineering & PMEvaluation/

Recommendations

ProposedChange Requirements

(CI’s specific)

Approval Process

CCBApprovedNetwork Changes

(related CI’s)

NetworkImplementation/Testing

Core CM Database

CI’sCI’s

DSN Databases - ADIMSS

CI’s

CI’s

CI’s

CI’s

CI’s

CI’s

CI’s

CM CoreDatabaseUpdate

CM DatabaseLinkage

Baseline DSN Network Model Network Change Drivers

Network Change Initiation

Network Change Process (Approval, Provisioning, Implementation)

And others…

Major Network Changes

Routine Network Changes

ADIMSS

Figure 7 Overall DSN CM Operational Concept

Establishing a DSN CM Database with a core database structure is the critical path in building asuccessful DSN CM Program. The core CM database contains only the installed and operationalDSN network elements, and it provides the support for the automated CM support systems andother DSN support systems.

DSN Configuration Management users include Management, Operations, Maintenance,Engineering, and Administration personnel. These users can be located locally (MILDEP),within each Theater, or at the Global level. Users at multiple levels and locations can access thiscore database structure to perform various DSN functions.

System interfaces must be provided to share and exchange information with other DISA systemssuch as Telecommunications Certification Office Support System (TCOSS), World-Wide On-Line System Replacement (WWOLS-R), Defense Information System Database (DISD), andContract Support System (CSS) that are critical to the DSN operations. Users can rely on theautomated support system to support their daily operations such as network/traffic engineering,planning, cost accounting, etc…

Advance Defense Switched Network Integrated Management Support System (ADIMSS) willprovide a platform for all database functions and automated support necessary for DSN CM.While there are various system applications that support individual DSN function (i.e.financial/accounting, planning/engineering, provisioning/installation, etc…), the core CMdatabase within ADIMSS will provide the central data depository for the critical ConfigurationItems (CI’s) that are common to all DSN functions. Within the DSN domain, the core CM

AccountingAccounting

ConfigurationConfiguration

FaultFault

PerformancePerformance

SecuritySecurity

DSN NetworkManagement

Functions

GlobalLevel Users

TheaterLevel Users

LocalLevel Users

ADMISSAnalysis/

Operation CellTCOSS

WWOLS-R

DISD

CSS

ADMISS (Tier 2)DSN Domain

Physical DSN Network Elements

Circuit Switches, ATM Switches, Lines, Trunks, AIN Systems, etc….

Manual Operations Automated Support

ADIMSS System Other Support Systems

CONUS

Europe

Pacific

CENTCOM

Practices & Procedures

Core CM Database

CI’s

CI’s

CI’s

DSN Database

DISA Network Services

DISA System Engineering

DISA Program Management Office

Global NOSC

Regional NOSC

MILDEP

database tracks all critical Configuration Items (CI’s) that are common to other DSN databasesand support systems. The common CM database structure applies across all theaters (CONUS,Europe, Pacific, and CENTCOM). This will allow interoperability and accessibility at the globallevel.

The following is an example of the DSN CM Database levels and their CI’s:

Figure 8 DSN CM CI Levels

DSN CM users at different levels (i.e. Global, Theater, and Local levels) can access the coredatabase and data mart to perform their specific tasks (i.e. performance management and faultmanagement). The overall ADIMSS/CM Database Administrator will control user access to datathat is outside of their level.

The core DSN CM Database should include configuration items from the following majorcomponents:

§ DSN Switch Hardware and Software§ Transmission Equipment§ Signaling Systems (SS7/STP)§ Trunk Circuits (Inter and Intra Theater)§ Network Financial and Cost Information

Site Site

Level 1Worldwide DSN

Level 2Theaters

Level 3Regions/Sites

Level 4Major Systems

Level 5Sub-Systems

Level 6Cards/Module

Level 7Ports

HardwareSoftware, and

Firmware

Theaters Theaters

Theaters Theaters

Defense Switched Network(DSN)

Switch/Router

Major Equipment

System

CircuitUnit

TransportTermination (TT)

Unit

Circuit Card

RoutersATM Switches

MultiplexersOthers…

TransmissionSystemsSwitch/

Router

Major Equipment

System

CircuitUnit

TransportTermination (TT)

Unit

TT Card(e.g. Echo Canceler, CSU/DSU)

Circuit Card

Region Region

TT Card(e.g. Echo Canceler, CSU/DSU)

Figure 9 depicts the DSN CM Database System Operational Concept.

Figure 9 DSN CM Database Operational Concepts

The Technical Data Storage (TDS) will support all on-line CM requirements such as storage oftechnical specifications, network routing information, Practices & Procedures, and otherinformation that is not associated with the operational plant (e.g. non-core/plannedimplementation). The Data Mart will allow users to store data from multiple sources, includingthe core database, and customized data for their specific applications.

Figure 10 depicts an example using Inter-Switch Trunks (IST’s) as network elements (orconfiguration items) that are being tracked by the DSN CM database to store its connectivity andrelationships between the CI’s.

Figure 10 Example of DSN CM Database CI Levels for an Inter-Switch Trunk (IST)

C o r eD a t a b a s e

A D I M S S

D S N D a t a b a s e

N e t w o r k A p p l i c a t i o n s

D a t aM a r t

O t h e r

O p e r a t i o n

S u p p o r t

S y s t e m s

D e f e n s e S w i t c h N e t w o r k ( D S N )N e t w o r k E l e m e n t s

C I ’ s

C I ’ s

C I ’ s

C I ’ s

C I ’ s

C I ’ s

C I ’ s

Q u e r y

U p d a t e s & M o d i f i c a t i o n s

R e a d / W r i t eU s e r s

R e a d O n l yU s e r s

Q u e r y

Q u e r y

Netw

ork A

pp

lication

s

N e t w o r k B a s e d A p p l i c a t i o n s

P C B a s e dA p p l i c a t i o n s

T e c h n i c a lD a t a

S t o r a g e

S w i t c h S y s t e m

T r a n s p o r t S y s t e m

T r a n s m i s s i o n S y s t e m

T e le p h o n e S w i t c h “ A ”

L e v e l4

L e v e l5

L e v e l6

L e v e l7

S w i t c h M o d u l e / C a r d

S w i t c h P o r t

E c h o C a n c e l l e r

E C M o d u l e / C a r d

P o r t

T r a n s m i s s i o n L in k

D ig i t a l C r o s s -C o n n e c t

P o r t

T r a n s m i s s i o n S y s t e m

T r a n s m i s s i o n L in k

D ig i t a l C r o s s -C o n n e c t

P o r t

T r a n s p o r t S y s t e m

E c h o C a n c e l l e r

E C M o d u l e / C a r d

P o r t

S w i t c h S y s t e m

T e le p h o n e S w i t c h “ B ”

S w i t c h M o d u l e / C a r d

S w i t c h P o r t

S i t e A S i t e B

D I S A / D S N

E n d - t o - E n d C o n n e c t i v i t y

MIL

DE

P

MIL

DE

P

D S N C M C o r e D a t a b a s e m u s t p r o v i d e a s t r u c t u r e t h a t t r a c k s t h e D S N n e t w o r k e l e m e n t s a n d t h e i r e n d - t o - e n d c o n n e c t i v i t y / r e l a t i o n s h i p . S i m i l a r s t r u c t u r e c a n b e u s e d b y t h e M I L D E P t o t r a c k t h e i rt e le c o m m u n i c a t i o n s s y s t e m s a t t h e b a s e / p o s t / c a m p / s t a t i o n . E x a m p l e b e l o w s h o w s a n I n t e r - S w i t c h T r u n k ( I S T ) c o n n e c t i n g S w i t c h A a n d S w i t c h B .

6.0 Summary of Current Status & Implementation Plan

Implementation of the above Operational Concept and Core Database Structure must be carefullyplanned and program managed. It must minimize the impact on the existing operational networkand network management systems.

Currently, the DSN CM functional model is completed. Existing operational processes aredocumented and being analyzed. A list of the immediate initiatives that will improve the short-term DSN operations was provided. A proof of concepts is completed on the automated DSNtopology tracking based on a common database of network elements (DSN voice switches andtrunks). The documentation of automated support system and Practices/Procedures (P&P)requirements are completed. Likewise, the initial requirement to establish a level structure forthe Configuration Items (CI’s) within the DSN database is completed.

The following is a list of the overall program activities:

q CM Requirements

A. Model Development

B. Process Development

C. Automated Support requirements

D. P&P Requirements

q Operational Concept

A. Operational Concept Creation

B. Documentation of Operational Concept

q Proof of Concept

q Automated CM Support SystemArchitecture

A. System Architecture Creation

B. Documentation of System Architecture

q CI Development

A. Identify CIs

B. CI Levels

C. Establish Baseline

D. Derive Data Elements

E. Develop CM Data Dictionary

F. Database Sizing

q Core Database Prototype

A. CM Requirements

B. Determine Baseline Network

C. System Design

D. System Development

E. Data Collection

F. Data Population

G. Data Verification

H. System Testing

I. System Debugging

J. System Operation

K. Feedback/Documentation

q User Support Requirements

q DSN Configuration Control BoardSupport

q Automated System Development P&PDevelopment