DISAC310-70-86_01-28-09 DRSN CM Guide.pdf

DEFENSE INFORMATION SYSTEMS AGENCY

P. O. Box 4502

ARLINGTON, VIRGINIA 22204-4502

DISA CIRCULAR 310-70-86*

METHODS AND PROCEDURES

Defense Red Switch Network (DRSN) Configuration Management (CM) Guide

1. Purpose. This Circular assigns responsibilities and provides methods and procedures for Defense Red Switch Network (DRSN) configuration management (CM). It also outlines the functions of the Network Configuration Control Board (NCCB).

2. Applicability. This Circular applies to DISA Global NetOps Center (GNC), DISA Global NetOps Support Center (GNSC), DISA Theater NetOps Centers (TNCs), DISA combatant command field offices, Military Departments (MILDEPS), and other Department of Defense (DoD) activities responsible for providing DRSN services to authorized users.

3. Authority. This Circular is published in accordance with the authority contained in DoD Directive (DoDD) 5105.19, Defense Information Systems Agency (DISA), 25 July 2006. The specific authorities for providing CM procedures, operational direction, and management control for the DRSN are cited in the chapters.

4. References.

4.1 ASD(NII) Memorandum, Appointment of Defense Information

Systems Agency (DISA) as End-to-End Configuration Control Manager for the Defense Red Switch Network (DRSN), 17 March 2008.

4.2 MIL-HDBK-61A(SE), Configuration Management Guidance

(revision A), 7 February 2001.

4.3 CJCSI 6215.01C, Policy for Department of Defense (DoD)

Voice Networks with Real Time Service (RTS), 9 November 2007.

4.4 Joint Staff J-6A 01665-92, Operational Requirements

Document for Secure Voice Requirements, 17 November 1992.

4.5 DISAC 300-175-9, Global Information Grid (GIG) Operating- Maintenance Electrical Performance Standards, 8 June 1998.

4.6 DISAC 300-115-7, Defense RED Switch Network (DRSN) Security Classification Guide, 26 January 1995.

4.7 DoDI 8100.3, Department of Defense (DoD) Voice Networks, 16 January 2004.

4.8 DISAC 310-70-84, Defense RED Switch Network (DRSN) System Control Guide, 27 July 1994.

5. Glossary of Terms. A glossary of terms follows the table of contents.

6. Responsibilities. Overall DRSN CM responsibilities are assigned below. Additional descriptions of the roles and responsibilities of the participating organizations are described in chapter C2.

6.1 Defense Information Systems Agency (DISA).

6.1.1 DRSN Management Office (MO). The DRSN MO develops, implements, and manages the DRSN baseline configuration. The DRSN MO develops, coordinates, and publishes network CM guidance through this Circular. The DRSN MO, as the DRSN operational manager, performs planning and financial management, cutover planning, implementation of new RED switches into the network, other major network changes, and status accounting and auditing of DRSN operational changes; such as, switch routing changes, Promina multiplexing changes, trunk classmarking changes, and others. The DRSN MO is the office within DISA that executes DISA’s responsibilities as End-to-End Configuration Control Manager, in accordance with reference 4.1.

6.1.2 Global NetOps Support Center (GNSC). The GNSC, located

at Scott AFB, performs the primary day-to-day, real-time control functions of the worldwide DRSN, while also providing a view to the theaters and the Europe and Pacific TNCs.

6.1.3 Europe and Pacific Theater NetOps Centers (TNCs).

The Europe-TNC and Pacific-TNC provide backup capabilities for real-time control functions of their respective theater DRSN elements, and assist DRSN sites in their theaters.

6.1.4 DRSN Engineering Group. The DRSN Engineering Group

provides systems engineers to perform DRSN engineering in support of all aspects of network configuration management and operation. The DRSN systems engineers oversee all DISA DRSN systems engineering activities and report to the DRSN MO.

6.2 Joint Task Force – Global Network Operations (JTF-GNO).

The JTF-GNO maintains a worldwide view of the entire DRSN, as well as all other DISA-managed (i.e., Defense Information Systems Network (DISN)) networks. The Global NetOps Center (GNC) assesses and coordinates resolution of intertheater network problems and advises key personnel of network status.

The JTF-GNO issues Warning Orders and is empowered to enforce compliance with configuration control.

6.3 Military Departments (MILDEPs) and Other DoD Agencies.

The MILDEPs and other DoD agencies develop and implement internal policies and procedures relating to their support of the operational management of the DRSN and develop and implement supporting procedures related to specific site operations.

6.4 Operations and Maintenance (O&M) Commands and Users.

O&M commands and users implement Service- and Agency-directed policy and procedures, develop site-specific practices, and perform O&M activities for fielding hardware, software, and firmware solutions; database changes; troubleshooting methodologies; testing; and other functions.

6.5 Network Configuration Control Board. The Network

Configuration Control Board (NCCB) plays a key role in change management by reviewing and approving significant changes to the configuration of the DRSN. Chapter C8 details the authority, responsibilities, membership and procedures of the NCCB.

7. Procedures. Detailed procedures for performing CM functions are provided in chapters C3 through C8.

8. Other Related Documents. The users of this Circular should be familiar with other documents which relate to DRSN opera-tions, acquisition guidelines, CM principles, and operations support of DoD communications assets as listed below:

8.1 DISAC 310-130-1, Submission of Telecommunications Service Requests, 4 April 2000.

8.2 DISAC 310-65-1, Circuit and Trunk File Data Elements

and Codes Manual of the Global Information Grid (GIG), 25 April 2002.

8.3 DoDI 4640.14, Base and Long Haul Telecommunications

Equipment and Services, 6 December 1991.

8.4 CJCSI 6211.02B, Defense Information System Network (DISN):

Policy, Responsibilities and Processes, 31 July 2003.

9. Circular Composition. Network CM concepts and operational functions addressed in this Circular are organization, data management, configuration identification, configuration control, configuration status accounting, and configuration audits.

FOR THE DIRECTOR:

ROBERT L. BETHEA, JR.

Colonel, USA Chief of Staff

SUMMARY OF SIGNIFICANT CHANGES. Organizational changes for the DISA DRSN Management Office (MO) are included in chapter C2.

Chapter C3 has been extensively revised and reflects data management equipment changes. The functions of the Network Configuration Control Board (NCCB) Secretariat have been clarified and are now detailed in chapter C8. Guidance on deviations from requirements of the network (paragraph C5.5) has been revised. Figure F5.1 (Request for Change Process), F5.2 (NCCB Directive [DISA Form 202: DRSN Configuration Control Board Response/Directive]), and Table T5.1 (Request for Change Submittal Matrix) have been updated. The Engineering Change Proposal (ECP) form DD-1692 and accompanying references have been deleted. The change of the Air Force Logistics Manager (AFLM) from Sacramento Air Logistics Center to Ogden Air Logistics Center, Hill AFB, Utah, and updated command titles are also included.

*This Circular cancels DISAC 310-70-86, 1 February 1995.

OPR: NS4

DISTRIBUTION: W

CONTENTS

BASIC CIRCULAR

1. Purpose

2. Applicability

3. Authority

4. References

5. Glossary of Terms

6. Responsibilities

7. Procedures

8. Other Related Documents

9. Circular Composition

C1. CHAPTER 1. OVERVIEW

C1.1 General C1.2 Scope C1.3 System Description C1.4 Focus

C2. CHAPTER 2. ROLES AND RESPONSIBILITES

C2.1 General C2.2 DRSN Management Office C2.3 Participating Organizations C2.4 DISA CM Organization C2.5 Organizational Interfaces

C3. CHAPTER 3. DATA MANAGEMENT

C3.1 General C3.2 Data Management Functions C3.3 Data Processing Requirements

C4. CHAPTER 4. CONFIGURATION IDENTIFICATION

C4.1 General C4.2 Selection C4.3 Baselines C4.4 Identifiers

C5. CHAPTER 5. CONFIGURATION CONTROL

C5.1 General C5.2 Change Processing C5.3 Action on Change Proposals C5.4 Engineering Change Proposals

C5.5 Deviations C5.6 Request for Change (RFC)

C6. CHAPTER 6. CONFIGURATION STATUS ACCOUNTING

C6.1 General C6.2 Data Collection and Reporting C6.3 Reports C6.4 Change Control Status Log C6.5 CM Database

C7. CHAPTER 7. CONFIGURATION AUDITS

C7.1 General C7.2 Objectives C7.3 Functional Configuration Audit C7.4 Physical Configuration Audit

C8. CHAPTER 8. NETWORK CONFIGURATION CONTROL BOARD

C8.1 Authority C8.2 Responsibilities C8.3 Membership C8.4 Meetings C8.5 Duties C8.6 Results of NCCB Action C8.7 Baseline Management C8.8 Cancellation of Approved Changes

ILLUSTRATIONS

Figures

F2.1 DRSN CM Organization F3.1 Network CM Data Processing F4.1 Network Configuration Items F5.1 Request For Change Process F5.2 Example NCCB Directive F5.3 Example DRSN Request For Change F6.1 Data Collection F7.1 Auditing Process

Tables

T5.1 Request For Change Submittal Matrix T7.1 Auditing Responsibilities

GLOSSARY OF TERMS

ADIMSS Advanced DSN Information Management Support System AFCA Air Force Communications Agency AFMC Air Force Materiel Command AFLM Air Force Logistics Manager AFSPC Air Force Space Command AIA Air Intelligence Agency ANSI American National Standards Institute ARDIMSS Advanced Red DSN Information Management Support

System ASD(NII) Assistant Secretary of Defense (Networks and

Information Integration

CCB Configuration Control Board CCBD Configuration Control Board Directive CCSS Command and Control Switching System CI configuration item CJCS Chairman, Joint Chiefs of Staff CJCSI Chairman of the Joint Chiefs of Staff Instruction CM configuration management CMO Configuration Management Officer CNO Chief of Naval Operations CONUS continental United States CSA configuration status accounting CSCI Computer Software Configuration Item

DAA Designated Approving Authority DIGVAL Digit Validation DISA Defense Information Systems Agency DISAC DISA Circular DISN Defense Information Systems Network DMS Defense Messaging System DoD Department of Defense DoDD Department of Defense Directive DoDI Department of Defense Instruction DoS Department of State DPA Dual Phone Adapter DPM Digital Phone Multiplexer DRSN Defense Red Switch Network DSN Defense Switched Network DTA Dual Trunk Adapter DWCF Defense Working Capital Fund

ECP Engineering Change Proposal EIA Electronics Industry Association ESRS Enhanced Switch Reporting System

FCA functional configuration audit FOUO For Official Use Only

GFE government furnished equipment GIG Global Information Grid GOS grade of service GNC Global NetOps Center GNSC Global NetOps Support Center

IAW in accordance with IST interswitch trunk IT Implementation Team

JFCOM Joint Forces Command JTF-GNO Joint Task Force-Global Network Operations

LCM Life-Cycle Manager

MDA Miniaturized Dual-Function Adapter MILDEP military department MIL-HDBK Military Handbook MLPP multilevel precedence and preemption MO Management Office

N.E.T. Network Equipment Technologies NCCB Network Configuration Control Board NNX local telephone exchange NORAD North American Aerospace Defense Command NETCOM U.S. Army Network Enterprise Technology Command NMS Network Management System

O&M operations and maintenance O&O operational and organizational OCONUS outside continental United States OO-ALC Ogden Air Logistics Center, Hill AFB UT ORD Operational Requirements Document OSD Office of the Secretary of Defense

PAC Pacific PCA physical configuration audit PCCB Product Configuration Control Board PCM Product Configuration Management PECP Preliminary Engineering Change Proposal PLM Product Life-Cycle Manager PM Program Manager PWA Printed Wiring Assemblies

QA quality assurance

RFC Request for Change ROUVAL Route Validation

RTS Real Time Services

SAL security access level SCI sensitive compartmented information SQL Structured Query Language SSM Single System Manager

T&S timing and synchronization TNC Theater NetOps Center TSO Telecommunications Service Order TSR Telecommunication Service Request

VDD Version Description Document

WWOLS-R Worldwide On-line System Replacement

C1. CHAPTER 1. OVERVIEW

C1.1 General. This chapter identifies the scope of network configuration management (CM) in the Defense Red Switch Network (DRSN); provides a description of the DRSN system that is under CM; and describes the focus area of this Circular.

C1.2. Scope. Network CM is a process that functions to ensure the baseline functional characteristics of the network are controlled and all changes to the network and the established baseline are methodically approved and controlled. Network CM also oversees implementation of approved changes to the baseline and audits the network functionality to ensure compliance to the baseline and approved changes. Network CM is a distinct process separate from but with dependencies to product CM. Product CM is concerned with configuration control of individual vendor products that make up components of the network systems.

Product CM is the responsibility of the product vendors, or in the case of Raytheon secure voice equipment, is a joint responsibility of Raytheon and the Air Force life cycle manager at Ogden Air Logistics Center.

C1.3 System Description. The DRSN system is a secure, digital, circuit switched telecommunications network providing multilevel precedence and preemption (MLPP), multilevel security with security authentication, visible display of calling user identification, and high quality secure voice conferencing between DRSN users. Cryptographically secured interfaces are provided for interswitch trunking and access to the secure users of other DoD, civil agency, and tactical and command unique secure voice systems. The DRSN is composed of four major subsystem configuration items (CIs) that are controlled and managed, wholly or in part, by DISA. These CIs are the transmission, switching, timing and synchronization (T&S), and network management subsystems.

C1.3.1 Transmission Subsystem. The transmission subsystem consists of a combination of government furnished equipment (GFE) interfaced to the DISN transport layer and to commercially leased circuits. The major transmission system component addressed in this Circular is the Network Equipment Technologies (N.E.T.) Promina multiplexers. To a lesser extent, those equip-ment components that constitute the tail circuit connections between the RED Switch and the Promina and the transport layer are also addressed. These components are used throughout the DRSN to dynamically allocate and control bandwidth utilization and provide framing and conditioning for DRSN interswitch trunks (ISTs). The roles, responsibilities, and procedures governing CM of the commercially leased circuits have already been established through existing DoD policy guidance and Defense Information Systems Agency (DISA) Circulars and Instructions (DISACs and DISAIs) and will not be superseded by this Circular, nor will this Circular repeat the information found in those publications.

C1.3.2 Switching Subsystem. The switching subsystem consists of Raytheon RED and BLACK digital telephone switching systems that provide expanded Private Automatic Branch Exchange call features which include MLPP, hot lines, conferencing capability, and interfaces to other secure voice systems. All the elements of the switching subsystem that can affect network functionality are governed by this Circular.

C1.3.3 Timing and Synchronization (T&S) Subsystem. The T&S subsystem consists of a series of station clocks, clock distri-bution systems, filters, buffers, and cabling that provide stable T&S signals to the transmission and switching subsystem components. The timing signal quality and master or slave timing configurations between the T&S devices and the other network subsystems are governed by this Circular.

C1.3.4 Network Management Subsystem. The network management subsystem consists of a switch monitoring system known as Advanced Red DSN Information Management Support System (ARDIMSS), a Promina network management system which is a commercial product of the Promina manufacturer NET.COM, and the telemetry network and call detail history collection and report generation components known as the Enhanced Switch Reporting System (ESRS). ARDIMSS is a government owned and contractor maintained product that is a subset of the Defense Switched Network’s (DSN) Advanced DSN Information Management Support System (ADIMSS) network management system. ARDIMSS and ADIMSS software and hardware are configuration controlled under a system specific CM plan. The Promina network management system is a commercial product. The telemetry network and call detail history ESRS is a combination of commercial products.

Significant changes to the network management subsystem architecture are subject to DRSN Network Configuration Control Board (NCCB) approval. Routine changes, modifications, and upgrades to the fielded ARDIMSS, Promina network management system, and ESRS are controlled by the DRSN NCCB Secretariat and coordinated with Defense Information Systems Network (DISN) and NetOps Center Configuration Control Boards (CCBs).

C1.4 Focus. Network CM within this Circular addresses the DRSN during the operational phases of the network life-cycle, including technology insertion and sustainment (as opposed to the conceptual or design phases). The network CM organization in an operational environment is described as is how the network CM organization interfaces with other network organizations having a CM role. CM applies to the functional, allocated, and product baselines. This Circular is an adaptation of those elements contained in reference 4.2 that describes the imple-mentation and operational phases. The DISA CM mission is to manage the network functional operational baseline.

C1.4.1 Implementation and Operational Phases. A typical CM plan covers the complete life cycle of a product from its conception to its design, production, deployment, operation, and deactivation. The CM of the changes that occur during the operational phases is addressed in this Circular. The DRSN Management Office (MO) governs the technology refreshment design and implementation functions and the plans and specifications issued to support the network during the operational phases.

C1.4.2 Functional Operational Baseline. As the designated DRSN manager, the DRSN MO ensures the network, as a whole, performs according to network functional specifications. As defined in references 4.3 and 4.4, the DRSN MO role is to manage the functional configuration of the network as a whole, specifically the network, subsystems, and product level items that affect network operations and functionality. The DRSN MO also performs network level CM of the Promina equipment, as well as assisting the Air Force Logistics Manager (AFLM) (who administers the depot and operations and maintenance (O&M) contracts) with CM of switch components, including hardware and firmware. The AFLM is responsible for product CM which includes configuration changes to individual printed wiring assemblies (PWAs) and peripherals that do not affect network functions or performance. The DRSN MO participates and assists the AFLM with government verification testing and analysis of hardware and firmware changes. The DRSN MO provides recommendations of whether to approve completion of Engineering Change Proposals (ECPs) and fielding of hardware and firmware. The DRSN MO, as the responsible office for network CM, approves all firmware, hardware, and software used in the DRSN operations. The N.E.T.

Promina is a commercial product, therefore the DRSN MO CM role is to determine node configuration, manage software loaded on all nodes in the network, and control all changes made to DISA-owned DRSN Promina nodes.

C2. CHAPTER 2. ROLES AND RESPONSIBILITIES

C2.1 General. This chapter describes the roles and responsibilities of the many government and nongovernment organizations involved in the coordinated effort of DRSN CM.

C2.2 DRSN Management Office. The DRSN Management Office (MO) serves as the Single System Manager (SSM) of the DRSN and coordinates support among all participants throughout the acquisition, deployment, and operational phases. The DRSN MO performs several functions to determine the planned network objectives and to implement and manage the network.

C2.2.1 Concepts and Requirements Development. The DRSN MO coordinates and issues the overall DRSN functional requirements based on the original 1992 Operational Requirements Document (ORD) (which has not been superseded), the DRSN Operational and Organizational (O&O) Concept document, and the DRSN Program Plan (copies available from the DRSN MO on request). The DRSN MO coordinates the impact of other long-range concepts, planning, and requirements documents affecting the Global Information Grid (GIG). The DRSN MO conceptualizes, in coordination with DISA engineering and design organizations, functional requirements for major network subsystems; such as, system interface criteria and timing and synchronization (T&S) plans. The transmission subsystems of the DRSN must satisfy the functional requirements stated in reference 4.5.

C2.2.2 Planning, Design, and Implementation. The DRSN MO defines and establishes the planned baseline configuration of the network in accordance with (IAW) the DoD budgeting cycle and in coordination with DISA engineering and operational organizations. This information is documented in the DRSN Program Plan. Implementation is carried out IAW implementation and cutover plans prepared by the DRSN MO.

C2.2.3 Financial Management. The DRSN Program Plan, developed and coordinated by the DRSN MO, contains a detailed plan for sustaining the network and which describes funding requirements and sources on a year-by-year basis. This plan provides the basis for budget submissions for the Defense Working Capital Fund (DWCF) and DISA appropriated funds, which are the basic funding mechanisms for the DISA controlled network portion of the DRSN. The Services and Agencies are responsible for funding for new DRSN switches, installations, user equipment, access circuits for remote phones, and replacement equipment including switches and for supporting the cost of the DRSN sustainment IAW reference 4.3.

C2.2.4 Security Management. The DRSN MO coordinates the overall security policy for the DRSN with the Designated Approval Authorities (DAAs), for collateral and for special compartmented information (SCI) systems respectively, and issues directives and guidance through reference 4.6 and other DoD security policy documentation.

C2.2.5 Performance Management. The DRSN MO monitors the performance of the network by collecting performance data from network equipment. The data is analyzed to pinpoint problem areas and action is initiated to improve performance based on the analysis.

C2.2.6 Configuration Management. The DRSN MO uses config-uration management (CM) for controlling changes to the DRSN functional configuration. The DRSN MO oversees the approval process for all change requests, but may elect to delegate this responsibility to a designated alternate. The DRSN MO is the agent for developing, coordinating, and implementing CM for the DRSN. In carrying out this responsibility, the DRSN MO coordinates the efforts of all participating product level CM and life-cycle organizations to ensure adherence to this Circular.

C2.3 Participating Organizations. The responsibilities of each group and organization responsible for DRSN CM tasks are identified as follows: Similarly the areas of responsibility of other organizations having major interfaces with DRSN CM organizations are also identified.

C2.3.1 Defense Information Systems Agency (DISA).

C2.3.1.1 DRSN Management Office (MO). The DRSN MO develops, implements, and manages the DRSN baseline configuration and coordinates and publishes network CM policy and procedures.

The DRSN MO also performs planning and financial management functions for the network operations. As the financial planner, the DRSN MO allocates DWCF and appropriated expenditures, which include funding of Engineering Change Proposals (ECPs) that affect the network functional baseline. These ECPs change the hardware, software, or firmware baseline of DRSN equipment. The DRSN MO acts as the Network Configuration Control Board (NCCB) secretariat by processing all change proposals that require ECPs and scheduling NCCB meetings. The DRSN MO also tracks and coordinates all deviations to approved ECPs. The DRSN MO coordinates and performs cutover planning and supports implementation of new RED switches and other major network changes. As the operational manager of the DRSN, the DRSN MO performs status accounting and auditing of operational changes to the DRSN; such as, switch routing changes, Promina multiplexing changes, interswitch trunking changes, and others, as required. Operational changes do not require ECPs because they do not affect the hardware, software, or firmware of the DRSN equipment. The DRSN MO maintains records of the current network operational baseline. The specific elements of the network operational baseline (software versions, circuit board revisions, etc.) change over time; therefore, no attempt is made to list or document the baseline in this Circular. The con-figuration items (CI) that comprise the baseline are described in chapter C4. The DRSN MO maintains a workspace on the classified Defense Knowledge Online (DKO) on the SIPRNet to provide online access to DRSN information; such as, the DRSN Operations and Maintenance (O&M) Guide, Telephone Directory, System Description, points of contact, ECP status, and other information related to DRSN O&M.

C2.3.1.2 Global NetOps Support Center (GNSC). The GNSC at Scott AFB is the DISA Tier 1 Network Control Office and Facility Control Office for the worldwide DRSN. The GNSC provides real-time surveillance and limited control of the network by tracking current operational status and by taking appropriate action to resolve conditions that threaten the health of the network. The GNSC also performs Tier 2 functions for the DRSN Red Prominas, administers Promina software configuration parameters, and issues changes to Red switch software configuration parameters that affect network operations. The GNSC works with onsite maintenance and/or system administration personnel to implement approved operational changes based on guidance from the DRSN MO.

The Tier 2 functions for the Red Switches worldwide are provided by Raytheon, the Red Switch vendor, under the Depot Support Contract administered by Ogden Air Logistics Center, Hill AFB, Utah.

C2.3.1.3 Europe and Pacific Theater NetOps Centers (TNCs).

The Europe-TNC and Pacific-TNC support limited Tier II functions and limited backup Tier 1 monitoring of their respective theater DRSN elements.

C2.3.1.4 DRSN Engineering. DRSN Engineering is the system engineer for the DRSN. DRSN Engineering develops the network topology, routing, numbering, T&S, and trunking and/or multiplexing plans for DRSN MO review and approval, based upon network policy, concepts, requirements, and traffic studies.

DRSN Engineering prepares the functional requirements for major network subsystems; such as the T&S criteria and system interface criteria for the DRSN MO. DRSN Engineering is the principal technical advisor to the DRSN Service Manager and supports the DRSN MO Tier 3 functions.

C2.3.2 Department of the Air Force.

C2.3.2.1 Air Force Communications Agency (AFCA). AFCA is the DRSN support organization for the Air Force and is responsible for recommending, collecting, processing, prioritizing, and forwarding requests for additional equipment and changes that require software, firmware, or hardware upgrades. Where such changes do not affect the network and are not to be funded by the DWCF or DISA appropriated funds, AFCA is also responsible for validation, obtaining funding for the requirement, and for overseeing the implementation. AFCA is a member of the NCCB as the Air Force representative.

C2.3.2.2 Office of Warfighting Integration and Chief Information Officer (SAF/XC). SAF/XC provides overall policy for Air Force communications.

C2.3.2.3 Air Force Major Commands. Air Force Major Commands identify funding resources for the non-DISA owned DRSN resources for which they are proponents.

C2.3.2.4 Air Force Materiel Command (AFMC) Ogden Air Logistics Center (OO-ALC). As the life-cycle manager, OO-ALC provides logistical support to the Command and Control Switching Systems (CCSSs). OO-ALC administers contracts that provide maintenance, depot, and training support to the CCSS. These contracts include a depot support contract with the switch manufacturer that all switch sites must pay a fee to use and an O&M contract for onsite contractor support for selected sites. Only the depot contract is mandatory for all Red Switch locations.

OO-ALC performs CCSS product level CM on behalf of DISA and all users of the CCSS equipment and reviews and manages all hardware, firmware, and software changes. OO-ALC has established, IAW reference 4.3, a Product Configuration Control Board (PCCB) with authority to review and approve CCSS product changes that do not affect the network. Proposed changes that affect network functionality will be referred for NCCB and/or DRSN MO consideration. OO-ALC also retains membership on the

NCCB.

C2.3.2.5 690 ISS/PI AFC2ISRC, Lackland AFB, TX. The Defense Intelligence Agency has delegated to the 690 ISS/PI AFC2ISRC the authority to accredit DRSN Red switches at Sensitive Compart-mented Information (SCI) locations as the DAA for processing of

SCI.

C2.3.3 Department of the Army.

C2.3.3.1 U.S. Army Network Enterprise Technology Command (NETCOM)/9th Army Signal Command. NETCOM plans, engineers, and approves all Army communications acquisitions including DRSN subsystem assets serving Army sites. As noted in subparagraphs C2.3.1 and C2.3.2, DISA and various Air Force organizations actually manage and administer the procurement and logistical support contracts that support the DRSN subsystems. NETCOM primarily specifies functional requirements and provides funding for the Red switch, Promina, and other DRSN components serving Army sites. NETCOM represents the Department of the Army as its representative on the NCCB.

C2.3.3.2 Army Major Commands. Army Major Commands identify funding requirements for the DRSN requirements for which they are proponents; such as, user equipment and the Army site portions of the switch system.

C2.3.4 Department of the Navy.

C2.3.4.1 Chief of Naval Operations (CNO). The CNO provides overall policy on all Navy communications. A representative from the CNO serves as a member of the NCCB.

C2.3.4.2 Space and Warfare Systems Command (SPAWARSYSCOM).

SPAWARSYSCOM plans, engineers, and approves all Navy communications acquisitions, including DRSN subsystem assets serving Navy sites. As noted in subparagraphs C2.3.1 and C2.3.2, DISA and various Air Force organizations actually manage and administer the procurement and logistical support contracts supporting the DRSN subsystems. When SPAWARSYSCOM has problems with its Red switches, Promina, and other components serving the Navy sites, it contact’s the appropriate DISA NetOps Center.

C2.3.4.3 Space and Warfare Systems Center (SPAWARSYSCEN).

SPAWARSYSCEN Detachment Saint Julian Creek, Virginia, supports SPAWARSYSCOM in specifying and verifying the functional requirements for DRSN switching systems serving the Navy DRSN sites.

C2.3.4.4 Navy Commands. Navy Commands identify funding requirements for the DRSN requirements for which they are proponents.

C2.3.5 Joint Staff and Combatant Commands.

C2.3.5.1 Joint Staff. The Joint Staff provides overall policy and approves DRSN requirements IAW reference 4.3. A Joint Staff representative serves as a member of the NCCB.

C2.3.5.2 Combatant Commands. The Combatant Commands are responsible for validating DRSN requirements, supporting funding through the military departments (MILDEPS) for those requirements, and for participating in long-range planning for DRSN service in their area of responsibility (AOR). The Combatant Commands have representatives that serve as members of the NCCB.

C2.3.6 User and/or O&M Organizations. A user and/or O&M organization at individual DRSN nodes coordinates with DRSN MO and the continental United States (CONUS) GNSC or outside continental United States (OCONUS) TNCs to implement the DRSN baseline configuration and approved changes. User and/or O&M organizations recommend, review, approve, manage, and implement changes that affect only individual subscribers at their location (such as assigned features, hot lines, and type of instrument) and changes that do not require software, firmware, or hardware upgrades or affect network operations. User and/or O&M organizations are responsible for processing and forwarding requests for more extensive changes, as specified in paragraph C2.5.

C2.4 DISA CM Organization. The two levels of DRSN network and product CM are illustrated in figure F2.1. The DRSN MO has the responsibility and authority to plan, execute, and control all CM efforts affecting the network functional baseline. The product level CM organizations control the contractual aspects of actual hardware, software, and firmware procurement and logistics and are also responsible for implementing the network functional baseline and changes. The DRSN MO performs the planning, executing, and controlling functions through delega-tions, as well as being the NCCB chairman. The identification, membership, overall area of influence, and integration of the NCCB and other bodies are described below and in paragraph C2.5.

C2.4.1 NCCB. The NCCB ensures all proposed changes to the DRSN functional baseline involving hardware, software, and firmware modifications are thoroughly staffed and formally reviewed and approved. Additionally, the NCCB ensures implementation actions and funding are identified and positive direction is provided. The Network Configuration Control Board (NCCB) reviews and votes to either approve or disapprove change proposals and deviations to the baseline. Detailed roles and responsibilities of the NCCB, the NCCB Chair, NCCB Secretariat, and NCCB members are provided in chapter 8.

C2.4.2 NCCB Support Organizations. Advisory and working groups support the NCCB by reviewing proposed changes to the DRSN, deciding on the acceptability of the changes, and ensuring overall system integrity.

C2.4.2.1 Advisory Groups. An advisory group is formed to pursue and provide advice to both matrix staff and to decision-making bodies on a specific function or discipline. DRSN Engineering is the primary advisory organization to the DRSN MO on planning, design, and traffic analysis.

C2.4.2.2 Working Groups. Working groups serve as a forum for addressing various issues for all DRSN subsystems across the MILDEPs. DISA solicits opinions from these groups and issues policy and guidance without their formal coordination. The DRSN Operations Working Group is a forum for addressing operational policy and procedure issues. The DRSN CM Working Group is a forum for addressing CM policy and procedure issues. The DRSN Security Working Group is a forum for addressing security policy issues.

C2.4.2.3 DRSN MO. The DRSN MO has specific functions in support of the NCCB. It is responsible for the CM disciplines of configuration status accounting (CSA) and auditing. The CSA process of validating and documenting approved changes, maintaining status change implementation, recording the changes, and verifying that the change implemented was in fact the change approved, is an ongoing priority. The DRSN MO directs functional and physical configuration audits (PCAs) and is responsible for maintaining all network configuration information. DRSN MO oversees the implementation of approved changes to the network functional configuration; provides access to configuration data to the NCCB Secretariat and other authorized personnel; negotiates implementation schedules, and any deviations, with the product CM organization and the implementation team; validates configuration information against documentation resulting from NCCB recommendations and single system management approvals; maintains a log of critical change implementation dates; directs and maintains records on functional configuration audits (FCAs) and PCAs; generates change and CSA reports periodically and on demand; and coordinates with other MO functions that affect the configuration; such as, service provisioning, exercise contingency planning, and emergency restorals.

C2.5 Organizational Interfaces. Responsibilities of other organizations that interface with DRSN CM and the interactions are described as follows:

C2.5.1 Product CM. At the present time, OO-ALC is the only product level CM organization; however, the following responsi-bilities apply to any product level CM organization.

C2.5.1.1 Establishing a CM program for configuration control of the product baseline (hardware and software). CM of several products (network components) will be combined, where feasible, into a single CM organization.

C2.5.1.2 Establishing a product level configuration control board (CCB) to review and approve all change proposals to the product baseline. DISA participates in the product CCB as a liaison between the product CCB and the NCCB. In this capacity, DISA will elevate, for consideration by the NCCB, proposed product changes that may affect the network functional baseline. The DISA representative acts as a liaison with the product CCB on any network functional changes approved by the NCCB requiring hardware and software baseline changes.

C2.5.1.3 Forwarding all change proposals that may affect the network functional baseline to the DRSN NCCB Secretariat for consideration by the NCCB.

C2.5.1.4 Coordinating FCAs and PCAs with the DRSN MO to avoid duplication of effort and incompatible audit data between the product and network CM organizations.

C2.5.1.5 Coordinating data standards development with the DRSN MO to ensure uniformity of configuration data across all organizations.

C2.5.1.6 Working with the DISA CM organization to develop data processing systems to ensure effective exchange of CSA and auditing data between the product and network CM organizations.

C2.5.1.7 Maintaining current and complete documentation to achieve approved changes, repairs, engineering efforts, and reviews.

C2.5.1.8 Modifying and/or upgrading equipment in response to specifications from approved network ECPs and other change documents.

C2.5.1.9 Coordinating approval of deviations of ECPs with the

DRSN MO.

C2.5.1.10 Coordinating hardware and software implementation schedules with the DRSN MO for changes affecting the network functional baseline and for coordinating any changes in schedules due to deviations or missed implementation dates with the DRSN MO.

C2.5.1.11 Obtaining coordination and/or concurrence from appropriate MILDEPs and/or agencies, as requested, on documentation and updates (such as, product level technical systems specifications, product level interface specifications and drawings, product level CM plans and ECPs, and test plans) that do not affect the DRSN network.

C2.5.2 User and/or O&M Organizations. The following responsibilities apply to all user and/or O&M organizations at all DRSN nodes:

C2.5.2.1 Recommending, processing, and submitting requests for network-impacting operational changes that do not require software, firmware, or hardware upgrades, such as, FLASH OVERRIDE authorizations and trunk routing changes either to the Joint Staff IAW reference 4.3 or to the DRSN MO, as appropriate.

C2.5.2.2 Recommending, processing, and submitting requests for additional equipment or changes to the product baseline (such as, additional phones and feature enhancements) to OO-ALC through their MILDEP DRSN support organization. Independently supported user and/or O&M organizations must submit changes directly to OO-ALC.

C2.5.2.3 Exercising configuration control over DRSN switch software configuration settings affecting local subscribers without affecting the network.

C2.5.2.4 Assisting implementation teams at their sites.

C2.5.2.5 Assisting with PCAs and FCAs at their sites.

C2.5.2.6 Maintaining and providing documentation, drawings, and specifications showing the configuration of all DRSN assets at their sites.

C2.5.2.7 Reporting DRSN configuration information and changes as tasked by the GNSC or TNCs and the DRSN MO.

C2.5.2.8 Providing representation at NCCB meetings and associated advisory and working groups to participate in the decision-making process for change proposals. (Users or O&M organizations who are neither voting nor associate members will be invited as requested by the NCCB Chair.)

C2.5.3 MILDEP DRSN Support Organizations. The following responsibilities apply to the Army, Navy, and Air Force organizations tasked to provide DRSN support:

C2.5.3.1 Recommending, collecting, processing, and prioritizing requests to OO-ALC for additional equipment and changes require-ing software, firmware, or hardware upgrades.

C2.5.3.2 Validating and obtaining funding for changes that do not affect the network and will not be funded by the DWCF or DISA appropriated funds.

C2.5.3.3 Distributing proposed ECPs for technical review and forwarding ECP technical review comments back to the NCCB Secretariat.

C2.5.3.4 Reviewing and providing MILDEP comments to draft DRSN programmatic and operational plans and policies.

FIGURE F2.1 DRSN CM ORGANIZATION

DISA

DRSN Program Manager

NCCB Chair

DRSN MO

NCCB

Secretariat

DRSN MO

Operational Baseline

Manager

Network Configuration Control Board

(NCCB)

OO-ALC

(CCSS LCM)

Product CCB

Chair

Product Configuration Control Board

(PCCB)

NETWORK

Configuration Management

PRODUCT

Configuration Management

C3. CHAPTER 3. DATA MANAGEMENT

C3.1 General. This chapter defines and establishes the procedures, responsibilities, and support systems for the data management required to support operational DRSN Configuration Management (CM). Data management elements consist of the definition, organization and storage, standardization, security, control and maintenance, and distribution of the data. These elements accurately reflect the current network configuration and status of pending changes. Data management is of fundamental importance to configuration identification, control, status accounting, and auditing. The effectiveness of CM decision-making and accounting processes is heavily dependent upon the generation, maintenance, and timely distribution of accurate configuration and status data.

C3.2 Data Management Functions. The functions necessary to ensure effective management of CM data consists of the following:

C3.2.1 Data Definition. The configuration items (CIs), (identified in chapter 4), and related configuration status accounting (CSA) information are designed to facilitate effective storage, access, and distribution of the data representing those items. The data definition process consists of selecting attributes of the DRSN CIs and change documents representing those CIs when stored as data. These attributes include identifiers that uniquely specify instances or occurrences of that item. Other attributes requiring definition include characteristics of the item necessary for CM: such as, location, manufacturer, model number, and other information.

The attribute definition includes the attribute name and the data length, format, and domain of the attribute. Data sources are included as part of the definition. The DRSN Management Office (MO), as the operational baseline manager, coordinates the data definition process with various data sources and users of CM data. The DRSN MO establishes and maintains the DRSN data dictionary that contains the official data definitions.

C3.2.2 Data Standardization. Data standardization requires implementation and maintenance throughout the DRSN community by updating data definitions contained in the DRSN data dictionary. The DRSN MO maintains the data dictionary and coordinates standardization of names, formats, domains, and sources for all data entities and attributes defined in the data dictionary. This facilitates exchange of data between databases and related documentation and minimizes data conversions and translations. The most critical data attributes requiring standardization are the unique identifiers for each CI and change document. For example, the DRSN MO is the source of the facility identification code for RED switches and has determined that the facility identification code defines a unique occur-rence of a RED switch. The identification code is three characters. The first character is an "R" and the last two are digits. All organizations having a role in DRSN CM will follow the data standards defined in the DRSN data dictionary.

C3.2.3 Data Organization and Storage. Once the network configuration and change status data has been defined, the DRSN MO will organize the data for storage in and retrieval from the CM database. Data organization is based upon emerging techno-logical advances in standard database design and management practices. Change requests and status are stored in the DRSN Web site. Engineering Change Proposal (ECP) documentation is stored in the DRSN CM database illustrated in figure F3.1. The DRSN CM database and DRSN Web site serve as the official reposi-tories of the DRSN baseline documentation. These repositories contain configuration data, change status data, and change documentation. Configuration data regarding the transmission subsystem continues to be maintained in the Worldwide On-line System Replacement (WWOLS-R).

C3.2.4 Data Security. The DRSN MO is the CM database manager and system administrator and controls access to the CM database and DRSN Web site. The DRSN MO is the only organization with "write" capability to the CM database and Web site. Requests for read access will be submitted to the DRSN MO for review and approval. Upon approval, the DRSN MO will develop reports or screens, as appropriate, and assign passwords for DRSN Web access to the specific data requested. The CM database will be Unclassified and the DRSN DKO site will be handled as For Official Use Only (FOUO) although it is located on SIPRNet.

C3.2.5 Data Control and Maintenance. The DRSN MO will control the configuration data for all DRSN subsystems and their internal configuration information defined as network CIs in chapter 4. The configuration data collected through the auditing process is maintained in the CM database. It provides DISA and other DRSN related organizations an accurate picture of the current operational configuration of the network. Data maintenance is shared between the DRSN MO, the Global NetOps Support Center/Theater NetOps Centers (GNSC/TNCs), and the O&M commands by subsystem as follows.

C3.2.5.1 Switches. Because the DRSN MO controls the configu-ration of the switch network operational parameters, it must control the data internal to the switch that determines these parameters. Network routing data is found in the Route Valida-tion (ROUVAL) and Digit Validation (DIGVAL) tables in the SDS family of switches. The network routing data of the DSS family of switches is found in the Trunk Routing and Digit Conversion Screen. The local O&M command changes, maintains, and secures this internal switch configuration data, as directed by the DRSN MO through the GNSC/TNCs. The DRSN MO periodically obtains copies of the internal switch configuration data as described in chapter 7. Configuration data representing the physical connections between external switch interfaces and other network subsystems (such as, clocks, clock distribution subsystems, trunks, crypto) will be collected through periodic site surveys, as described in chapter 7.

C3.2.5.2 Promina Multiplexers. The DRSN MO controls the configuration parameters (such as voice compression and bandwidth allocation) and the data internal to the Promina that determines those parameters. The GNSC/TNC uses the Promina Network Management System (NMS) to change, maintain, and secure the internal configuration data based upon guidance from the DRSN MO. The DRSN MO maintains online access to the NMS to obtain data input for monitoring and auditing purposes.

C3.2.5.3 Timing & Synchronization (T&S) Subsystems. The DRSN MO collects configuration data describing the T&S arrangement at each DRSN node. The T&S configuration data describes the timing source, timing signal frequencies, and master-slave relation-ships verified during site audits, as described in chapter 7.

C3.2.5.4 Physical Connections. Physical connectivity data for a DRSN node is collected and verified by the DRSN MO during site audits, as described in chapter 7. Physical connectivity data includes switch port assignments for voice and signaling channels, encryption device assignments, and encryption device to switch assignment. The physical connectivity data represents the tail circuit configuration between DRSN switches and govern-ment to commercial demarcation points.

C3.2.6 Data Distribution. The DRSN MO coordinates distri-bution of all network configuration, status, and change docu-mentation data. Data maintained in the CM database and DRSN DKO site will be distributed in the form of reports, drawings, and documents to the various requesting DRSN organizations.

C3.3 Data Processing Requirements. The DRSN MO determines and implements the distributed data processing strategy and database architecture to be used for network CM. The DRSN MO coordinates decisions regarding hardware, database, applications software selections, and development with the GNSC/TNCs, the Product Life-Cycle Manager (PLM), and the local O&M Commands. The data processing requirements to support data management for network CM are described as follows.

C3.3.1 Functional Requirements. The conceptual network CM data processing system supports the CM processes of configuration identification, control, status accounting, and auditing.

Figure F3.1 provides an overview of the data processing elements.

C3.3.1.1 Configuration Identification.