DISN_OSS_ProgPlan-v0.3-29Feb08.doc

For Official Use Only

DEFENSE INFORMATION SYSTEM NETWORK (DISN)

Operational Support Systems (OSS)

GS28

PROGRAM PLAN

FISCAL YEARS 2008-2015

Draft Version 0.3 29 February 2008

Defense Information Systems Agency Network Services Directorate (NS)

Operational Support Systems Division (GS28)

P.O. Box 4502 Arlington, Virginia 22204-4502

Revision History

This document will be reviewed and updated annually. The changes will be reflected in the revision history table.

SIGNATURE PAGE FOR KEY OFFICIALS

“I support the Line of Business (LOB) Program Plan that is contained in this document.”

Approved by:

Program Manager (GS28)

Date

Chief, LOB Division

Ms. Linda Safford (GS2)

DISN Program Manager, Center for Network Services

Mr. Thomas McCrickard III (GS2)

DISN Technical Director, Center for Network Services

Ms. Cindy Moran (GS2)

Chief, Center for Network Services

This page intentionally left blank

Line of Business (LOB)

TABLE OF CONTENTS

1-1Executive Summary

SECTION 1 - Introduction 1-1

1.1 Scope

1-1

1.2 Defense Information Systems Network (DISN) Mission

1-1

1.3 Line of Business (LOB) Mission

1-2

1.4 Background

1-3

1.5 Need for Change

1-4

1.6 Goals/Benefits

1-5 SECTION 2 - Program Overview 2-1

2.1 Objectives and Priorities

2-3

2.2 Service Descriptions

2-4

2.2.1 Alarm Service

2-6

2.2.2 Inventory Service

2-7

2.2.3 Trouble Ticket Service

2-8

2.2.4 Order Service

2-10

2.2.5 Service Reporting Service

2-11

2.3 Service Level Agreements (systems reliability standards)

2-11

2.4 Baseline Description

2-12

2.4.1 Element Management System

2-12

2.4.1.1 ATM Management System

2-13

2.4.1.2 IP Management System

2-14

2.4.1.3 I3Tel

2-14

2.4.1.4 Concord Nethealth

2-15

2.4.1.5 ESONET Management System

2-15

2.4.1.6 IDNX Management System

2-15

2.4.1.7 Switched Voice Management System

2-15

2.4.1.8 DISN Core Element Management System

2-16

2.4.2 Network Management System

2-18

2.4.2.1 INMS

2-19 2.4.2.1.1 INMS Functional Overview 2-20

2.4.2.2 ICATS

2-27

2.4.2.3 Trouble Management System

2-28

2.4.2.4 Report Management System

2-30

2.4.3 Service Management System

2-30

2.4.3.1 DISA Direct

2-31

2.4.3.2 DISA Direct Order Entry

2-32

2.4.3.3 World Wide Online System – Replacement

2-34

2.4.3.4 Provisioning Automated Workflow System

2-35

2.4.3.5 Warehouse Management System

2-36

2.4.4 Data Communications Network

2-37

2.4.4.1 DCN Regional Site

2-39

2.4.4.2 DCN Edge

2-40

2.4.4.3 DCN Tail Site

2-41

2.4.4.4 DCN IP Addressing

2-41

2.4.4.5 DCN Security

2-42

2.5 Change Drivers

2-42

2.5.1 Business Objectives

2-43

2.5.2 User Requirements

2-44

2.5.3 Technology

2-44 SECTION 3 - Goal /Strategies 3-1

3.1 Near Term (FY08-11) Goal Capabilities and Services

3-4

3.2 Mid Term (FY12 – 13) Goal Capabilities and Services

3-5

3.3 Future Vision (FY14-16) Goal Capabilities and Services

3-6

3.4 Maintenance

3-6

3.5 Benefits

3-6

3.5.1 Operational Benefits

3-6

3.5.2 Integration and Sustainment Benefits

3-7

3.5.3 Customer Relation Benefits

3-7

3.5.4 Business Benefits

3-7 SECTION 4 - Program Management 4-1

4.1 Program Management Office (PMO)

4-1

4.1.1 Element Management System Branch (GS281)

4-1

4.1.2 Network Management System Branch (GS282)

4-2

4.1.3 Service Management System Branch (GS283)

4-3

4.1.4 Logistics and Support Branch (GS284)

4-4

4.1.5 Policy and Architecture Group

4-5

4.2 Overarching Strategy

4-5

4.3 Near Term (FY08-11)

4-6

4.3.1 EMS Consolidation

4-8

4.3.1.1 Unclassified DCN Enhancements

4-9

4.3.1.2 Classified DCN

4-10

4.3.1.3 Central NIDS & Firewall Management

4-11

4.3.2 Central NMS

4-11

4.3.3 Network Change and Configuration Management

4-12

4.3.4 COTS-based Order Management System

4-13

4.3.5 OSS Central

4-13

4.3.6 Cross-Domain Solution

4-14

4.3.7 Real-Time Services Network Management

4-15

4.3.8 DECC Relocation

4-15

4.4 Mid Term (FY12 – 13)

4-15

4.4.1 Single Sign-on at the EMS layer

4-16

4.4.2 Automated provisioning

4-17

4.4.3 Common workflow management system

4-17

4.4.4 Multi-Level Operator Terminal

4-18

4.5 Future Vision (FY14-16)

4-18

4.6 Challenges

4-18

4.7 Risk Assessments

4-19

4.7.1 Technical

4-19

4.7.2 Cost

4-19

4.7.3 Schedule

4-20

4.8 Communications

4-20

4.9 Quality Assurance

4-21 SECTION 5 - Funding Profile 5-22

5.1 Funding Profile Overview

5-22

5.2 DISA GS28 Baseline Funding Profile

5-1

5.3 EMS Consolidation Funding Profile

5-4

5.4 Central NMS Funding Profile

5-5

5.5 Network Change and Configuration Management Funding Profile 5-6

5.6 Order Management System Funding Profile

5-7

5.7 Cross-Domain Solution Funding Profile

5-8

5.8 Real-time Services Network Management Development Funding Profile 5-9

5.9 DECC Relocation Funding Profile

5-10

5.10 Network Operations Funding Profile

5-11

5.11 Mid Term (FY12-13) (Required, Budget, Unfunded)

5-12

5.12 Future Vision (FY14-16) (Required, Budget, Unfunded

5-12

REFERENCES

5-1

ACRONOYMS

5-1

GLOSSARY

5-1

LIST OF TABLES AND FIGURES

1-3Figure 1‑1 GIG Combat Support (GS) Directorate Organization

Figure 2. DISN TMN Transformational Architecture 1-6 Figure 3. GS28 TMN Reference Model 2-2 Figure 4. Current Element Management Environment 2-5 Figure 5. DISN TMN Element Management Architecture 2-6 Figure 6. DISN Alarm Service 2-7 Figure 7. DISN Inventory Service 2-8 Figure 8. Trouble Ticket Service 2-9 Figure 9. Order Service 2-10 Figure 10. Service Reporting Service 2-11 Figure 11. Manager-of-Managers Architecture 2-20 Figure 12. INMS Integrated Situational Awareness Display 2-22 Figure 13. INMS Distributed Architecture 2-24 Figure 14. JDCS Server Suite 2-25 Figure 15. INMS External Alarm Interfaces 2-26 Figure 16. ICATS Architecture 2-28 Figure 17. TMS Architecture 2-29 Figure 18. DCN Hierarchy 2-38 Figure 19. DCN Regional Site 2-40 Figure 20. DCN Edge Site 2-41 Figure 21. Service-Oriented Integration (SOI) Architecture 3-3 Figure 22. DISN OSS Two-site Architecture 3-4 Figure 23. FY08-11 Project Work Breakdown Structure 4-7 Figure 24. Near-term Timeline 4-8 Figure 25. OSS Central 4-14 Figure 26. Mid-term Timeline 4-16

2-26Table 1. List of networks monitored by the INMS

Table 2. DISA Direct System Components 2-32 Table 3. DDOE System Components 2-33 Table 4. WMS Components 2-37 Table 5. GIG Network Management Tenets 3-1 Table 6. GS281 Baseline Funding Profile 5-1 Table 7. GS282 Baseline Funding Profile 5-2 Table 8. GS283 Baseline Funding Profile 5-3 Table 9. EMS Consolidation Project 5-4 Table 10. Central NMS Funding Profile 5-5 Table 11. NCCM Funding Profile 5-6 Table 12. Order Management Funding Profile 5-7 Table 13. Cross-Domain Solution Funding Profile 5-8 Table 14. RTS Network Management Development Funding Profile 5-9 Table 15. DECC Relocation Funding Profile 5-10 Table 16. Network Operations Funding Profile 5-11

Executive Summary The Operational Support Systems Division is responsible for providing and sustaining the Information Technology (IT) that instruments and automates the Operations, Administration, Maintenance, and Provisioning (OAM&P) functions for the Defense Information Systems Network (DISN). Collectively, the OAM&P systems under the responsibility of the Operational Support Systems are known as the DISN Telecommunications Management Network (TMN). Several needs drive the continued evolution of these systems:

· Supporting operational goals for the DISN

· Providing continued positive control and support of the DISN as it evolves and matures

· Supporting the business need to become more cost efficient

· Supporting the network user/customer needs for information services in a timely manner

· Supporting Net-Centric operations (NCO) with composable data services

The DISN TMN plays a significant role in meeting these needs as DISA and the Department of Defense (DoD) implement Net-Centric solutions, as directed in DoD Directive 8100.1, “Global Information Grid (GIG) Overarching Policy,” and DoD Directive 8320.02, “Data Sharing in a Net-Centric Department of Defense”. In addition, several other initiatives within DISA materially change the networking infrastructure and how it is used, compelling the TMN to change and evolve.

A significant part of the cost of providing network services is tied up in the installation, operations, maintenance, and provisioning of those services. The TMN provides the tools used to perform these functions. In response to continued budgetary pressures in the foreseeable future, improving the TMN toolset will minimize the amount of labor required to sustain services, and simultaneously enhance information awareness.

The above change drivers translate into the following initiatives:

Near-Term (2008-2011):

1. Maintain current systems, applying upgrades and corrective code as required to maintain their operational effectiveness in managing the networks.

2. Consolidate the Element Management Systems to reduce operational expenses and improve situational awareness about the DISN.

a) Establish a single IP Element Management System (fault, configuration, and performance) for all IP networks.

b) Reduce the total number of EMS applications to the minimum number required to manage the networks effectively.

c) Implement a Security Event Correlation system at the Element Management Layer to isolate the security events from the network events.

3. Improve integration among Element Management System (EMS), Network Management System (NMS) and Service Management System (SMS) layers to support NetOps, contain costs, improve situational awareness, facilitate information sharing, and enable net-centric operations.

d) Implement the Telemanagement Forum (TMF) standardization initiative for all data sharing interfaces between TMN applications.

e) Implement a Shared Information Data Model (SID)

f) Implement a Service-Oriented Integration (SOI) environment and publish all necessary data to the NetOps community for consumption

4. Centralize the Network Management System applications to reduce operational expenses, provide global situational awareness from a single system, and implement a Continuity-of-Operations (COOP) configuration.

5. Unify the configuration management, property management, and provisioning tool sets to improve customer support, reduce provisioning flow times, and contain costs.

g) Establish a single change and configuration management system for the entire DISN

h) Implement a commercial off-the-shelf (COTS) solution for service order management that will provide a self-service, customer-facing service ordering interface. It will be highly integrated with the network change and configuration management system, which will enable automated service ordering based on accurate network resource availability. As a result, customers will be able to complete service requests within minutes or hours instead of weeks or months.

6. Implement a DISN Information Sharing Services DMZ that will consolidate, aggregate, and normalize all information pertaining to the DISN. This information will be made available via web content for end-users, and through Web Services for application-to-application sharing.

7. Expand the Data Communications Network (DCN) to all DISN locations to provide a single, ubiquitous communications network for the transport of all network management traffic over a secure, out-of-band data path.

i) Implement a secure virtual private network (VPN) extension for the DCN to manage devices that are not located at DISN sites.

j) Implement a classified DCN to separate the data paths of the management and data planes, providing a more secure and reliable classified network.

8. Implement Bi-Directional Cross Domain Solution (CDS) that will allow transaction-based, near real-time transfer of data between classification environments.

Mid-Term (2012 – 2013)

1. Single sign-on access control for the DISN OSS element management applications.

2. Automated provisioning of DISN services.

3. Multi-level Security Thin Client for network operators to access all unclassified and classified OSS applications and network elements from a single terminal.

Future (2014 – 2015)

TBD

SECTION 1 - Introduction

1.1 Scope

The Joint Mission Need Statement (JMNS) defines the Defense Information Systems Network (DISN) as the protected Department of Defense (DoD) network that allows warfighters to exchange information in a seamless, interoperable, global battle space. The DISN provides consolidated worldwide telecommunications infrastructure and services that support national defense, command, control, and intelligence requirements, and an essential element of the Global Information Grid (GIG). DISN provides a system of integrated networks to support multimedia requirements with sufficient bandwidth for high volume exchange of voice, data, imagery, and video transport services, to satisfy all mission areas. Within a Network Centric Warfare (NCW) environment, these information delivery capabilities enable the warfighter’s capabilities and our information and decision superiority.

To successfully meet its mission, the DISN must have the necessary systems and infrastructure to support Operations, Administration, Maintenance, and Provisioning (OAM&P) activities that will ensure operational efficiency of the DISN by providing the right services, to the right place, at the right time, and in a manner consistent with DoD’s net-centric operations (NCO) concept and vision.

This program plan outlines the initiatives that the DISA Network Services Directorate (NS), Operational Support Systems (OSS) Division (NS8) will undertake during fiscal years 2008–2016 in order to meet the NCO objectives, improve operational efficiencies, and enhance information sharing.

1.2 Defense Information Systems Network (DISN) Mission

The Defense Information System Network (DISN) provides the interoperable telecommunications connectivity and value-added services required to plan, implement, and support any operational missions any time and anywhere. The DISN is a complex program of services focused on sustainment and modernization. The DISN provides long-haul connections among the Combatant Commanders, Service and Defense Agency bases, and deployed forces. The DISN provides dynamic routing of voice, data, imagery (both still and full motion), and bandwidth services on a fee-for-service basis. DISN subscription services are described as follows:

Transmission Services provide a robust worldwide capability to transmit voice, video, data and message traffic for the Combatant Commanders, Military Departments and Defense Agencies. Transmission Services provide the information transport for other Services described below, as well as for specialized services.

Joint Worldwide Intelligence Communications System (JWICS) provides comprehensive worldwide secure high-speed multimedia Top Secret/Sensitive Compartmented Information communications services for the DoD Intelligence Community and the intelligence estimates of other federal agencies.

Data Services provide secure Internet protocol router network (SIPRNet) and non-classified Internet protocol router network (NIPRNet) capabilities

Voice Services provide day-to-day commercially competitive services plus unique secure military requirements. Voice Services include the operation of the Defense Switched Network and Defense Red Switch Network.

Video Services provide both routine and classified video teleconference capabilities for the DoD and other government agencies.

Messaging Services provide day-to-day organizational messaging capabilities for the DoD. The network provides Top Secret, Secret and Unclassified messaging capabilities using four regional Security Operations Centers.

Centralized Services are made up of provisioning support to DISN users and operators and network management support to all programs that make up the DISN as described above.

DISA also provides long-haul connections between the Combatant Commands/Service/Agency, bases, and deployed forces. DISA provides government and contract engineering, modeling, simulation and assessment, and system control resources to support the operational DISN networks.

1.3 Line of Business (LOB) Mission

The DISN Operational Support Systems Division (NS8) is a program office within the Defense Information Systems Agency (DISA) GIG Network Services (NS) Directorate: Center for Network Services (GS2).

The mission statement for the organization is as follows:

DISA NS8 is responsible for systems engineering/integration, planning, resourcing, fielding, sustaining and evolving secure NetOps tools in support of network centric operations to Operate, Administer, Maintain, and Provision (OAM&P) the GIG which provides information superiority to the Commander-in-Chief, Combatant Commanders, DoD, DISA, Services, Agencies, and the Warfighter.

There are two major parts to the mission: (1) providing resources for the data-to-day mission of operating the networks that make up the fixed asset aspect of the GIG; and (2) providing the tools required to configure and manage those assets to meet customer requirements.

As illustrated in Figure 1‑1, GS28 is one of the GS2 divisions, and is responsible for the systems, collectively known as the DISN Telecommunications Management Network (TMN), that support OAM&P activities for the DISN. The GS28 OSS division is organized with four branches according to the TMN reference model, with a branch for EMS (EMS integration and sustainment branch), a branch for NMS (NMS integration and sustainment branch), and a branch for SMS (Fulfillment and Services branch). The Program Support and Logistics branch provides common support across the division for administrative, financial, and task management activities. In addition, there is a Policy and Architecture group that provides the overarching direction for the DISN TMN.

Figure 1‑1 DISA Network Services (NS) Directorate Organization

1.4 Background

The systems that support the OAM&P of the DISN must be enhanced to meet the information and decision superiority goals for the Joint Force. The DISN is a complex, global network of networks that has evolved over time to meet DoD requirements. Through the years, the DISN has expanded through individual programs, a process that created islands of network management environments that are network/service centric. In addition to network management silos, the systems used for ordering services were splintered across several other organizations that were not part of any network management environment. This disjointed arrangement of applications, organizations, and process used to operate the DISN causes issues with data integrity, inaccurate situational awareness, and long delivery times for services.

As the DISN evolves to meet customer demands, so too must its network management infrastructure. The DISN network management environment must adapt and align itself with DoD and industry initiatives for the OAM&P of advanced, transformational telecommunications services. Given the global reach of the DISN, along with the large number of vendors supplying network elements across many network technologies, the task of managing the DISN, as a single entity, is an enormous challenge. The evolution is necessary in order to contain costs, rapidly deploy new services, and to secure a single, efficient, end-to-end operational view.

The contractual, security, and isolation of current network management environments make it difficult to realize accurate situational awareness of the DISN at any given point in time. Network operators in each of the DISN Network Operations (NetOps) Support Centers must coordinate NetOps information across multiple network organizations in order to stitch together the final operational picture, which is outdated by the time it has been created. The personnel, systems, and security policies for each of the DISN network management silos must collapse into a single environment to realize the greatest efficiencies in operating the DISN.

The management of the DISN in a consolidated environment will be accomplished at three levels – Element Management, Network Management, and Service Management. The goal is to provide an OAM&P infrastructure for the DISN that will provide timely and accurate end-to-end situational awareness, and automated, flow-through service fulfillment while maintaining a flexible and scalable architecture to meet the telecommunications service demands of the DoD. However, this goal requires a paradigm shift from the existing program structure and integration practices.

1.5 Need for Change

DoD envisions the Joint Force functioning in a Net-Centric Environment (NCE) that fully exploits shared knowledge and technical connectivity in order to significantly increase mission effectiveness and efficiency. The NCE is a framework for full human and technical connectivity and interoperability that allows all DoD users and mission partners to share necessary information in a timely, comprehensible, reliable, and secure way.

The NCE Joint Functional Concept describes how joint forces might support DoD information and decision superiority within a fully networked environment 10 to 20 years in the future. This networking of all Joint Force elements enables unparalleled information sharing and collaboration, increased organizational adaptivity, and greater unity of effort via synchronization and integration of force elements at the lowest levels.

Operating in the NCE includes interacting through a capability interface, accessing services, and sharing information. Evolving the NCE includes guiding and directing NCE evolution; the architecting, development, and implementation of NCE capabilities; and governing NCE evolution.

Transforming the DISN network management environment to operate in a local (within the DISN TMN boundary) and global (with the entire Joint Force NetOps Community) NCE will generate significant business and operational advantages for DISA and allow DISA to share information concerning the health and status of the DISN more effectively.

In addition to fulfilling the NCE goals of the DoD, the DISN TMN’s transformational evolution will satisfy four additional goals outlined in the CONOPS for GIG NetOps:

4. The Joint Task Force-Global Network Operations (JTF-GNO) shall be fully capable of responding to, or directing the operations and defense of the GIG with clear lines of authority, responsibility, tactics, techniques, and procedures across command, geographic and technical boundaries.

5. The JTF-GNO shall realize full situational awareness of the Global Information Grid through common processes, standards and instrumentation, enabling near real time manipulation of any asset in order to optimize net-centric services.

6. The JTF-GNO shall be fully capable of projecting, defining, advocating and defending JTF-GNO resource requirements to include budget, personnel, training and certification.

7. The JTF-GNO shall be fully capable of maintaining relevant, current and operationally sound NetOps doctrine across the DoD, and collaborating to establish similar guidance for all federal partners.

1.6 Goals/Benefits

The DISA OSS Division has the responsibility to define, integrate, implement, and sustain the systems necessary to support the OAM&P activities for the DISN. The continued sustainment and evolution of these systems is driven by the need to:

Support the NetOps goals for the DISN and the GIG

Provide consistent positive controls and support of the DISN as it continues to evolve and mature

Increase cost efficiency Provide high-quality service delivery and management to network users/customers These needs give rise to the following goals:

Consolidate and implement the organizational structure. A consolidated network management organization is a different approach for DISA in satisfying the NetOps mission. Previously, multiple organizations, or network programs held responsibility for NetOps. The new GS28 organization consolidates all systems and personnel used in the management of the DISN into a single organization.

Consolidate the NetOps contract support under a single task order. This will eliminate the redundant roles and responsibilities that support individual task orders. It will also increase information sharing in NetOps Centers because contract support staff will look at the entire DISN rather than focusing narrowly on a single DISN sub-network. Additionally, a single NetOps task order will guarantee common processes and procedures worldwide.

Reduce the total cost of network operations by eliminating redundancy and duplication across the systems and organizations that perform operations functions.

Develop the metrics and methodologies to measure the processes and activities within NetOps to ensure that the new configuration of tools reduces flow time and total cost of ownership, while improving quality of the services.

Maintain and sustain the systems to meet or exceed the service level objectives for cost, performance, availability, and quality.

Share a common set of DISN information with the NetOps Joint Force to aid in decision-making.

This new approach for DISN network management is a necessary transformation that will allow the DISN to smoothly incorporate new technology, network elements, and processes. The evolving DISN TMN architecture will leverage industry’s application integration technology and process advancements, while incorporating legacy systems where appropriate.

Figure 2 illustrates the transformational DISN TMN architecture that will help achieve DISA’s NetOps goals in the NCE. While the current approach of point-to-point integration for each introduction of new technology and service cannot meet customer demands, and significantly increases the integration burden (schedule and cost), the new, scalable TMN architecture can respond flexibly to the demands of the DISN and the Joint Force. This target DISN TMN environment collapses multiple security and operating boundaries into one, and uses the latest integration technologies to reduce integration costs, increase integration efficiencies, and provide a highly interoperable, data-centric environment that lets customers focus on the data rather than on the application.

Figure 2. DISN TMN Transformational Architecture The DISN TMN has both an intra-NCE and an inter-NCE, where the intra-NCE employs the NCE principles and technologies, but is localized to the sharing of information between DISN TMN applications within its closed boundaries. The same NCE principles, technologies, interfaces, and services are also used to share information with Joint NetOps community outside of DISA. The difference between intra-NCE and inter-NCE is that the inter-NCE only provides a subset of information to the external community because not all information that is used to integrate the TMN components is relevant to the external Joint NetOps community. Sharing NCE principles and technologies for sharing data internally to the DISN TMN and with external organizations will maximize software re-use, and minimize the level of effort expended on integration activities and administration, resulting in greater efficiencies for DISA.

SECTION 2 - Program Overview As previously mentioned, DISA GS28 is responsible for systems engineering, integration, planning, fielding, and sustaining the necessary tools that will directly support the collection, processing, and sharing of information for and about the DISN.

The mission for GS28 is very similar to that of a commercial Communications Service Provider (CSP) that manages a complex telecommunications network supplying commercial business and residential voice, video, and data services. A CSP operates in a very competitive market and relies heavily on industry standards to help reduce the time it takes to implement the necessary management tools for new technologies and services. Likewise, GS28 will be looking to industry for models, frameworks, specifications, technologies, and solutions that have proven successful and target the specific CSP market. Leveraging the pool of knowledge and experience of many international CSPs, network equipment manufacturers, system integrators, and software application vendors that have ventured the same path of transforming their management systems will significantly decrease the amount of time for GS28 to achieve its goals.

GS28 has selected the International Telecommunications Union Telecommunication Standardization Sector (ITU-T) Telecommunications Management Network (TMN) Reference Model as the basis for the new DISN TMN architecture for the systems under its domain of authority.

According to the ITU-T, a TMN supports the management requirements of a CSP to plan, provision, install, maintain, operate, and administer telecommunications networks and services. Within the context of the TMN, management refers to a set of capabilities to allow for the exchange and processing of management information to assist CSPs in conducting their business efficiently. A TMN provides management functions for telecommunications networks and services, and offers communications between itself and the network elements, services, and other TMNs.

The concept behind a TMN is to provide an organized architecture to achieve the interconnection between various types of Operation Support Systems (OSS), Business Support Systems (BSS), and network equipment for the exchange of management information using standardized interfaces, protocols, and messages. It provides management functions and communications between the OSS applications, between the OSS and the network equipment, and between the OSS and external parties, to include the BSS.

The TMN partitions the management functions of operating the network into layers, where each layer is focused on a specific domain of management functions. Standardized service contracts, or interfaces, are used between layers to share management information.

DISA GS28 has modified the ITU-T TMN reference model to meet its mission. The modifications made are the inclusion of the Common Communications Vehicle (CCV) and Support System. Since GS28 is only involved with the operations of the DISN, the Business Management Layer of the ITU-T TMN Reference Model is not included in the DISN TMN architecture. The DISN TMN will, of course, have an interface with the DISA business systems for sharing information about services ordered by customers.

Figure 3 illustrates the DISN TMN reference model and architecture. This architecture is vastly different than the current method of managing the DISN, and is a paradigm shift from existing DISA integration practices. It provides a very flexible and scalable environment for expanding and contracting the TMN as it evolves to meet the OAM&P requirements for the DISN. The focus of the new DISN TMN architecture is on the data, not the tool used to collect, process, and present the data.

Figure 3. GS28 TMN Reference Model The DISN TMN consists of three management layers, a Data Communications Network (DCN), the CCV, and a suite of Support Systems. As illustrated in Figure 3, the OSS component of the DISN TMN consists of the three management layers, the CCV, and the Support Systems.

· Service Management Layer (NML) – This management layer includes the systems, data, and processes that are responsible for ordering, creating, and activating services. It provides the customer-facing applications that allow DISN customers to order new services, get status on existing service orders, obtain reports on operational service levels, and report troubles. Data required by these systems comes from the Network Management Layer.

· Network Management Layer (NML) – This management layer includes the systems, data, and processes that provide the end-to-end health and status view of the aggregate DISN. It includes fault management, performance management, inventory and configuration management, and presentation of all DISN sub-networks and their relationships to each other. Data required by these systems comes from the Element Management Layer and the Service Management Layer.

· Element Management Layer (EML) – This management layer includes the systems, data, and processes that actively monitor and control a population of network elements. These systems provide mediation between the network elements and the network management layer. This layer provides direct control of the network elements and executes commands from the upper layers. Only the Element Management Systems have direct communications with the network elements.

· Data Communications Network – The DCN provides the communications transport between the DISN OSS and the network elements. It is an out-of-band network that is isolated from the operational networks and only has connections with the DISN OSS and the network elements. It operates as an autonomous system under the authority of DISA GS28.

· Support Systems – This DISN TMN sub-system provides a suite of tools that are shared among all DISN OSS applications, the DCN, and the network elements for services such as access control, time-of-day synchronization, storage, name services, intrusion detection, and auditing.

· Common Communications Vehicle – This DISN TMN sub-system is responsible for marshalling data between the OSS applications, mediating the data between different interface protocols, and governing the data interfaces through a UDDI Registry.

In addition to the ITU-T TMN Reference Model, DISA GS28 will leverage the resources (data models, process definitions, and interface specifications) of the TeleManagement Forum (TMF). Specifically, DISA GS28 will base its TMN data model on the TMF Shared Information Data (SID) model and use the TMF OSS through Java (OSS/J) and Multi-Technology Open Systems Interface (MTOSI) specifications for the application data interfaces of the DISN OSS applications.

2.1 Objectives and Priorities

To gain efficiencies, provide optimal situational awareness, streamline the ordering and provisioning of new services, and implement a single network management enclave for the entire DISN, it is in DISA’s best interest to consolidate all systems that directly support the OAM&P functions for the DISN into a single organization. As that organization, GS28’s priority is to ensure the greatest return on investment (cost efficiencies and increased value to the customer) for the systems under its domain of authority. To achieve its mission, GS28 will need to re-architect many facets of the OAM&P systems currently being used to manage the DISN.

This document outlines the architectural objectives of the new DISN TMN and the initiatives that will guide the evolution toward the end-sate architecture. The objectives for transforming the network management environment for the DISN include:

· Accurate configuration management through the consolidation or replacement of tools, and the enforcement of naming standards;

· A common data model for sharing information between all DISN TMN applications and for sharing with external organizations;

· A service-oriented integration environment that will satisfy DoD’s Net-Centric and Data Strategy requirements;

· A single security boundary and operating environment for all DISN TMN systems and personnel;

· Effective situational awareness through automation of configuration management information and operational status;

· Automated flow-through provisioning and activation of services;

· A single point of access (portal) for all information for and about the DISN;

· Commercial off-the-shelf (COTS) solutions for all Service Management Systems;

· Service level reporting with customer-centric views of service performance;

· Multi-level secure workstation for network operators to allow access to all DISN TMN systems regardless of classification;

· A classified Data Communications Network (DCN) for full separation between the network management and user planes;

· A bi-directional cross-domain solution that will support automated flow-through provisioning messages and network alarms.

2.2 Service Descriptions

As outlined in the Joint Concept of Operations (JCONOPS) for Network Operations (NetOps), the NetOps Centers for each network must cooperate with each other to consolidate and integrate information regarding the operational health and status of their networks. The fusion of the information from the NetOps Centers within each theater of operations, and up to Joint Task Force – Global Network Operations (JTF-GNO), will provide end-to-end Situational Awareness (SA) of the GIG to improve decision making for the Commander, US Strategic Command (CDRUSSTRATCOM) and, ultimately, to the warfighters.

In support of the JCONOPS, the DISN TMN will provide a set of composable services to internal and external customers that can be consumed and processed to meet the mission of a given Command. The services available to each customer base are the same. It is the level of information provided through the services that will be different for each customer base.

Internal customers include the Tier I & II network operators, the Tier III engineers, Service Managers, traffic engineering, the DISN Program Office, and the contractual and financial organizations of DISA. This population of DISN TMN customers requires detailed information about the DISN for long-term capacity engineering, ensuring service level agreements are being met, designing and provisioning services using available network resources, to react to network events to minimize operational outages, and to track status of inventory and orders.

External customers include those that have ordered DISN telecommunications services, DoD NetOps Centers, Joint Task Force – Global Network Operations (JTF-GNO), and Commercial Service Providers.

Both internal and external customers of the DISN TMN will use the following services to obtain information about the DISN, provide information to DISA related to DISN services, or order DISN services:

· Alarm Service

· Inventory Service

· Order Service

· Trouble Ticket Service

· Service Level Reporting Service

Except for the Trouble Ticket Service, the above services rely directly or indirectly on the information provided by the EML. To ensure accurate and efficient information flow to and from the EML, it is essential that the current element management environments for be transitioned from the silo-based approach of managing the various DISN sub-networks as shown in Figure 4, to a single, consolidated, and integrated common architecture as shown in Figure 5.

Figure 4. Current Element Management Environment

Figure 5. DISN TMN Element Management Architecture As illustrated in Figure 5, not only will the integration and data flow be improved with the new architecture, but the transition to a single security boundary will significantly improve the OAM&P activities of the DISN.

Along with the consolidation to a single EML environment, DISA GS28 will implement a common data model and standard naming convention for alarms, inventory, and performance data to be used for passing information between the EML and the Network Management Layer (NML).

2.2.1 Alarm Service

The DISN alarm service will provide information concerning the health and status of network elements. The alarm service will provide information via a web-based client and Web Services. The web-based client will be used for a graphical operational picture of the DISN that includes alarms, topology, and performance information, where the user will actually log into an application and browse for the necessary information.

The Web Services is a machine-to-machine interface used for sharing alarms with other network management systems. The alarm Web Services will support bi-directional sharing of alarms where DISA may receive alarms from other GIG networks for processing and presentation within the DISN Network Event Manager and relayed to other network management systems.

The key component of the DISN alarm service is the Integrated Network Management System (INMS), as shown in Figure 6.

Figure 6. DISN Alarm Service

2.2.2 Inventory Service

The DISN inventory service will provide information concerning the planned and operational (as-is) configuration of network elements, and their relationship to each other in the DISN. The inventory service will provide information via a web-based client and Web Services. The web-based client will be used for entering data, querying the database, running reports, and a graphical representation of the DISN that includes topology, site layouts, rack elevations, and cabling.

The Web Services is a machine-to-machine interface used for sharing operational inventory data with other network management applications. The inventory Web Services will support bi-directional sharing of inventory data, where DISA may receive inventory data from other GIG networks or commercial service providers to aid in providing end-to-end situational awareness and troubleshooting activities.

The key component of the DISN inventory service is the Integrated Configuration and Tracking System (ICATS), as shown in Figure 7.

Figure 7. DISN Inventory Service

2.2.3 Trouble Ticket Service

The DISN trouble ticket service will provide web-based client access to open, close, and update trouble tickets for managing problems and scheduled maintenance activities on the DISN. The primary users of the web client interface will be DISN network operators, DISN service managers, and the GNC.

The Web Services component of the trouble ticket service will provide a machine-to-machine interface for sharing reportable tickets between GIG NetOps Centers, civilian agencies relying on DISN for telecommunications services, and CSPs that are providing transport services to DISA. Unlike the other DISN information sharing services, the trouble ticket service will utilize two Web Services definitions for sharing trouble tickets – the GIG Standard Ticket (GST), and the OSS through Java (OSS/J) Trouble Ticket. Figure 8 illustrates where these two Web Services interfaces will be used.

Figure 8. Trouble Ticket Service Within the DoD, the GIG Standard Ticket (GST) will be used for sharing reportable trouble tickets. The GST is a trouble ticket interface developed by DISA in response to requirements established by the Joint Task Force-Global Network Operations (JTF-GNO) for interoperability across DoD trouble management systems.

The GST is DISA’s solution for sharing a common trouble ticket throughout the DoD to ensure situational awareness across the GIG and disparate communities of interest. In essence, the GST establishes a standard trouble ticket Application Program Interface (API) using standardized data elements that allows the Combatant Commands, Services, Agencies, and Allied Forces to easily share information concerning the health and status of the operational networks. Since a trouble management system is a common tool for organizations to log and track scheduled and unscheduled service affecting events, using a standardized interface between the various trouble management systems is an obvious choice for realizing an end-to-end GIG situational awareness in the shortest amount of time. Using Web Services as the messaging technology abstracts the information sharing to a level that allows each organization to implement a trouble ticketing system that best satisfies their requirements, promoting flexibility, scalability, and autonomy while maintaining end-to-end situational awareness for the GIG.

All non-DoD organizations will use the commercial industry’s OSS/J Trouble Ticket API for receiving reportable events concerning the DISN, and for reporting events of interest to the DISN NetOps Centers. The GST and OSS/J are very similar, and the DISN TMN will mediate between the two interface specifications through the use of its CCV so that there is only one data interface, the GST, for the DISN Trouble Management System.

2.2.4 Order Service

The order service provides the user and machine interfaces necessary to order DISN telecommunications services and / or equipment. The web user interface will allow users to order services and track their progress on-line, provided through a self-service format, where users will log into a central ordering system, browse a catalog of available services and equipment, place an order, update orders, and review order status.

The Web Services component of the order service will provide an electronic bonding (eBonding) relationship between DISA and its DISN customers, and with CSPs that are providing services to DISA to extend / enhance DISN capabilities. Using the DISN order service will minimize manual data entry, automate and speed the ordering process, allow the customer and CSP organizations to leverage their own systems and processes for tracking telecommunications service orders, and improve service order accuracy. This service will also be intimately integrated with the DISA contract and finance systems to capture and report service order information with greater speed and accuracy through automated machine-to-machine interfaces.

Figure 9 illustrates the DISN order service and its role in the service fulfillment hierarchy.

Figure 9. Order Service

2.2.5 Service Reporting Service

For the telecommunications services that DISN provides, both customers and service managers will want to understand how well the services are performing. The DISN service reporting service provides information on how well a service is performing. The DISN service reporting service does not provide any information on the detailed performance of the network elements and/or systems that are employed on the DISN to provide the service. Customers and service managers will be able to obtain information such as availability, performance degradation, usage, security events, and business events that can be used to determine if the service being provided is meeting contractual obligations.

Figure 10 illustrates the DISN order service and its role in the service fulfillment hierarchy.

Figure 10. Service Reporting Service

2.3 Service Level Agreements (systems reliability standards)

The DISN TMN is responsible for collecting and processing the necessary data from the DISN network elements and service ordering systems, and presenting service reports to DISN Service Managers and DISN customers. The data collected and the reports provided are dependent on the Service Level Agreements (SLAs) negotiated between the DISN Service Manager and its customers.

The service level requirements imposed on the DISN TMN are those that affect system reliability of the DISN TMN systems, not the network.

The DISN TMN has a .999 reliability requirement. To achieve the reliability requirement, many of the DISN TMN systems will need to be enhanced to support local and remote Continuity of Operations (COOP) that will provide survival of operations during catastrophic events, or scheduled maintenance windows.

Local COOP involves the survival of system operations at a local site, and usually involves a high-availability configuration of the system where a secondary system will immediately take over operations if the primary system fails. A remote COOP involves the survival of operations from one site to another, geographically remote site. Each site maintains the same system configuration to achieve .999 local reliability. The remote COOP will be designed and implemented to technically achieve .999 reliability, but the actual operations at a secondary, remote site will require trained personnel and is outside the scope of the DISN TMN.

2.4 Baseline Description

To a large extent the current systems that support the OAM&P functions for the DISN represent a collection of application silos, with disjointed, point-to-point integration.

One of the key objectives of the Operational Support Systems Division is to orchestrate the transformation of the application silos into a single, comprehensive integrated environment that will have a coordinated effect on the network through a collection of cooperating systems. This will be achieved through the enforcement of the layered model of the DISN TMN, where each layer is focused on the objectives of the layer and communicates with layers above and below through well defined service contracts using industry standard, service-oriented integration technologies. Along with the enforcement of the TMN architectural model, GS28 will focus on maximizing efficiencies of each layer of the model by eliminating redundant, overlapping systems, and automating all data sharing within and between layers using a standardized data model and data integration specifications defined by industry.

The remainder of this section provides an overview of each of the DISN TMN systems in their current state and how they align, or will align, with the DISN TMN architectural model.

2.4.1 Element Management System

The Element Management System (EMS) is a critical component and a major sub-system of the DISN TMN. The EMS manages all OAM&P communications between the DISN OSS applications and the managed elements. An EMS is a functional system and may consist of a single application or array of applications integrated to perform the complete set of EMS functions. Each EMS focuses on a discrete population of devices, typically delineated by communications technology.

The following DISA systems fall within the DISN TMN EMS:

· ATM Management System (AMS)

· IP Management System (NIPRnet, IP Core, SIPRNet, MHS, Push Key)

· I3Tel

· Concord

· ESONET Management System

· IDNX Management System

· Switched Voice Management System (DSN, DRSN)

· DISN Core Element Management System Each EMS listed above operates within an operational and security silo. There are several management applications that are replicated across multiple DISN EMS silos, and some applications that operate as an individual silo performing a function for multiple EMSs.

There are several EMSs that have not yet been transferred to the DISA GS28 Division. Over the time period covered by this program plan, it is envisioned that all EMSs used for the DISN will be transitioned to DISA GS28, and consolidated into a common operational and security enclave.

2.4.1.1 ATM Management System

The ATM Management System (AMS) is the management enclave for the DISN ATM System (DATMS).