"Series Number"



"Date of Instruction - Spell Month Out Completely"

6 January 1995

"Series Title"


"Long Title - Type In All Capital Letters"


This instruction implements AFPD33-1, Command, Control, Communications, and Computer (C4) Systems, and the requirements in DoD Instruction 5000.2 and Defense Information Systems Agency (DISA) Publication, "DRSN CM Guide". The process implements the network configuration control process for the CSCCSN. This instruction applies to HQ AFSPC and all subordinat units. It does not apply to Air Force Reserve nor Air National Guard units.

Section A--GENERAL

1. Introduction. The AFSPC Communications Configuration Control Subboard (Comm CCSB) is subordinate to the AFSPC Configuration Control Board chaired by AFSPC/LG. The Colorado Springs Command and Control Switch Network (CSCCSN) Configuration Control Board is a subboard of the Comm CCSB.

2. Scope. This instruction applies to changes to the operational baseline of the CSCCSN. The integration of a new system acquisition or capability into the operational baseline are further examples of changes controlled by this Instruction. Software deliveries, system enhancements, connectivity additions, capacity expansions of lines or memory, and system to system interface changes are controlled through the procedures defined herein.

3. System Description. The CSCCSN is currently divided into three command and control subsystems, see Attachment 1. The switch networks are:

3.1. NORAD Mission Center Cheyenne Mountain Air Station (CMASN). The CMASN Red Switch supports the mission requirements of CINCNORAD, USSPACECOM Mission Centers, and also provides secure voice connectivity into the Defense Red Switch Network (DRSN). The CM Black Switch serves the same mission requirements, only in an unsecured mode. The Operations/Maintenance (O/M)
organization for these mission center switches is the 721 Communications Squadron (CS).

3.2. USSPACECOM, Peterson AFB (Building 1470). The Building 1470 Red Switch provides a secure switch for USSPACECOM and NORAD Headquarters during crisis and peacetime operations and into the DRSN. The Building 1470 Black Switch serves the same mission requirements, only in an unsecured mode. The O/M organization for these headquarter switches is the 21 Communications Squadron.

3.3. AFSPC, Peterson AFB (Building 1). The Building 1 Red Switch serves AFSPC and its supporting elements for Command and Control (C2) functions. The Operations/Maintenance (O/M) organization for this headquarter switch is the 21 CS.

4. Configuration Control. The Configuration Control Manager (CCM) for the CSCCSN is HQ AFSPC/SCOSV. The CCM is responsible for:

4.1. Evaluating proposed technical changes.

4.2. Recommending approval/disapproval of changes.

4.3. Tracking the implementation of approved changes.

4.4. Overall network management of the CSCCSN in the Peterson Complex.

4.5. Serving as the chairperson of the CSCCSN Configuration Control Board (CCB).

5. Defense RED Switch Network (DRSN). All CSCCSN Red/Black Switches are an integral part of the DRSN, along with the transmission interconnect and IDNX multiplexers.

5.1. DRSN Description. The DRSN is a secure voice (Red/Black Switches) telecommunications system servicing major Department of Defense (DOD) organizations, departments, and other Government agencies located at red enclaves worldwide. The DRSN is composed of three major subsystem configuration items that are controlled and managed wholly or in part by Defense Information Systems Agency (DISA). These are the transmission, switching, and timing/ synchronization subsystems.


6. General. Modifications to the baseline shall follow the Communications-Computer System Requirements Document (CSRD) process. A change affecting the CSCCSN will be forwarded to the CCM for review and applicable CSCCSN CCB action.

7. Configuration Items (CI). The configuration item baseline for each element is listed in the Equipment Inventory Section of the Program Management Responsibility Transfer (PMRT) Package and is maintained at the communications unit level. The five designated CI categories for CSCCSN are:

7.1. Hardware. Includes the physical computer systems(s) used to execute the computer software programs.

7.2. Software. The set of instructions that causes the computer to execute.

7.3. Firmware. The combination of a hardware device and computer data resident as read-only software. Changes to firmware will be controlled as a software or hardware change depending on the characteristics of the change. If the firmware can be changed without being physically removed, the change will be documented and processed as a software change. If the firmware must be removed from the physical location to be changed, then it will be documented as a hardware change.

7.4. Connectivity Medium. The means to transfer digital and analog data. Communications medium changes are categorized as changes to modems, communications multiplexers, cryptographic equipment, or mode of transmission.

7.5. User Baselined Database.

8. CSCCSN CCB. The CSCCSN CCB acts as the certification authority for technical solutions. The approval authority to implement a certified change resides in the CSRB.

8.1. The membership of the CSCCSN CCB is as follows:

8.1.1. Chairperson. The CSCCSN CCM is the chairperson of CSCCSN CCB. The chairperson will schedule meetings and prepare and distribute the board minutes.

8.1.2. Members. Permanent primary and alternate members will be appointed in writing. Members are responsible for assuring each proposed CI change on the agenda has been reviewed and evaluated to their satisfaction, and making a recommendation to the chairperson to certify or not certify a requested change and establish a priority. Permanent Members. The CSCCSN CCB permanent membership will include representatives from the following organizations: HQ AFSPC/SCO HQ AFSPC/SCX HQ AFSPC/SCN USSPC/J6OC NORAD/J3CR 21 CS/LGGC 721 CS/CXR DISA Field Office (Non-voting) Associate Members. Associate membership of the CSCCSN CCB is open to representatives of any interested organization.

8.2. Meetings. The CSCCSN CCB will conduct business by formal quarterly board meetings. If there are vital issues to be acted on prior to the meeting, the chairperson will schedule an additional meeting.

9. Unit Level Control. Configuration control of each switch is the responsibility of the CSCCSN Communication-Computer Security Officer (CCSO) for each switch. CCSO, primary and alternate, will be appointed in writing by the respective commander. Copies of appointment letters will be forwarded to CSCCSN CCM.

9.1. The 21st CS is the CCSO for the switches supporting NORAD/USSPC (Building 1470) and AFSPC (Building 1).

9.2. The 721 CS is the CCSO for the CMASN switches.

10. CCM Responsibilities. The CSCCSN CCM, AFSPC/SCOSV, is responsible for the overall network configuration management of the CSCCSN. The configuration management responsibilities include configuration control, configuration identification, configuration auditing, and status accounting. The CSCCSN CCM is the single point of contact within the Peterson Complex for the DRSN.

10.1. After a certified change request has been approved by the CSRB, the CCM will oversee the implementation of the requested change. The change should occur within the timeline requested by the user or recommended by the CSCCSN CCB. The milestone actions for the type of CI change are as follows:

10.1.1. Software change. The following actions are required: Proprietary Software Release Document. Full description of software (provided by the vendor) to be affected by the change. Provided to the CSCCSN CCB for review during the staffing process. A technical assessment with recommendations and expected impacts will then be provided to the CSRB. Test Bed and Evaluation Report. Demonstrates, under conditions as realistic as possible, the system's operational effectiveness and operational suitability. The test bed switch will be determined by the CSCCSN CCB and depend upon the mission and test requirements at the time of each anticipated or announced software delivery. Version Installation Date. The actual date the software change is installed and certified operational. Operational Acceptance. After a minimum period (to be determined by the CCM and the affected CCSO), the responsible CCSO declares the software version acceptable for operational use. Upon operational acceptance, the software will be tracked as the new baseline on that switch. When the software release has been accepted at all affected switches, it will be tracked as bonded software.

10.1.2. Hardware. For implementation of Switch Hardware Changes, the following milestone actions are required: Installation Date. The CCM will coordinate an installation date with the responsible CCSO. The CCSO will ensure all corollary actions (i.e., facilities, maintenance support, utilities, vendor checkouts/diagnostics) are complete and/or available. Since hardware cannot normally be removed after installation, the date of this initial installation action constitutes the Installation Date. Operational Acceptance. The CCSO will notify the CCM when the change has acceptably met all test criteria. At this point the CCM will track the change as operationally accepted.


11. General. This chapter contains the procedures used for making configuration item changes to the CSCCSN, to include identification and origin of a proposed change, staffing and acting on proposed changes, and implementing approved changes.

12. Change Request Certification and Requirements Approval Authority. Only the responsible CCSO or the CSCCSN CCB can certify a proposed CI change.

12.1. Proposed changes will be submitted on a CSRD, AF Form 3215. The flow for validation, technical solution and approval will follow normal CSRD procedures. The CSCCSN CCB will be accomplished as part of the technical review.

12.2. The CCSO may certify and implement certain categories and types of change requests without review by the CSCCSN CCB. These are defined as:

12.2.1. Changes affecting station line, call detail recording, and lists, operational traffic measurement features, and other call processing functions. Specifically: Top Secret/Secret Line Button changes. Assignment of phone number within block of numbers allocated to the switch. Hotlines within the switch. Preset conferences within one switch (except OPS Loop extensions outside the CMC). Allow Multiple Line Phones (MLPs) access to STU-IIIs on local switch. Allow MLPs access to Local switches specific interfaces (MACA, BMEWS, JCSAN, MRVCS, TSP, and SSSVN).

12.2.2. A courtesy copy of all CSRDs associated with secure voice requirements will be provided to the CCM.

12.3. The following database changes must always be forwarded to the Configuration Control Manager/CSCCSN CCB for consolidation and recommended approval/disapproval before forwarding to DISA/UTV for final consideration:

12.3.1. Maximum Calling Area (MCA) changes.

12.3.2. Multiple switch preset conferences.

12.3.3. Assignment of MCAs that allow access to the DRSN.

12.3.4. Assignment of MCAs that allow access to trunks or crypto assets on other switches in the network.

12.3.5. Digital Validation (DIGVAL).

12.3.6. Assignment of Security Access Level (SAL) other than SAL-2.

12.3.7. All Maximum Precedence Authorized (MPA) higher than Priority.

13. Special Security Office (SSO) Certification and Requirements Approval Authority. The SSO is the cognizant security office responsible for ensuring the Air Force and Defense Intelligence Agency (DIA) Sensitive Compartmentive Information (SCI) accreditation of the CSCCSN remains valid. SSO written concurrence is required on all proposed CI changes involving changes when the telephone instrument is equipped with an SCI high or low access. The CMASN and Building 1470 switches fall under control of the USSPC SSO. The Building 1 switch is under the control of the AFSPC SSO.

14. Board Decisions. The CSCCSN CCB Chairperson makes a decision on the agenda items, based on the assessments of the members and advisors. For each agenda item, the chairperson will resolve the items as follows:

14.1. Approve. If the change and all corollary changes are within the CCM's scope of responsibility, then the chairperson has approval authority.

14.2. Recommend Approval. If the total change is not within the CCMs cope of responsibility, the Chairperson may recommend approval to the Comm CCSB.

14.3. Disapprove with Comment. The minutes will reflect the chairperson's rationale for disapproval.

14.4. Defer with Comment. If additional staffing or evaluation is required, the item may be deferred until the next board. The minutes will include the chairperson's rationale for deferral.

14.5. Withdraw with Comment. The originator may withdraw the action item. The minutes will reflect the rationale for withdrawing the item.

14.6. Cancel. Used when a proposed change is removed due to the sundown clause. The sundown clause cancels any item not scheduled for implementation after it has been open for two years.

15. Hardware Modifications. Actions that require a hardware modification will have an AF Form 1067 attached for forwarding to the AFSPC CCB Modification Ranking Process.

16. DRSN Changes. If a change operationally impacts the DRSN, the Request For Change (RFC) will be forwarded to DISA/UTV for further processing. Refer to DISA publication, "Defense RED Switch Network (DRSN) Configuration Management Guide".


17. General. This chapter contains the procedures used for maintaining configuration control of the CSCCSN on a daily basis. These procedures include frequent contact between the CSCCSN CCM and the Red/Black Switch database managers, monthly extraction of data from each of the Red/Black Switches, and comparisons of old versus new switch database.

18. Database Extraction. The database from each of the Red/Black Switches will be extracted on a monthly basis utilizing the AFSPC Database Management System. The data will be downloaded onto a 3 1/2" PC disk, and delivered to the CSCCSN CCM. The CCM will review the data for compliance with configuration control as set forth in this Instruction.

19. Old/New Comparison. The "Old/New Comparison" query of the Database Management System will be used by the CSCCSN CCM to ensure that proper configuration control guidelines are being adhered to.

20. Cable Plant Configuration Control. The configuration control of the cable plant for each of the Red/Black Switches is the continual responsibility of the O&M unit for the respective switch.

21. Switch Numbering Plan. The CSCCSN Red Switches are unique in that the three separate switches all use the same NNX code to interface the DRSN. Therefore the numbering scheme in each switch is dependent on the other two. Reference Attachment 2.

21.1. There are four basic types of numbers used within a switch:

21.1.1. Hotlines. These are five-digit numbers that are generated within a switch that will allow calls to be set up in a point-to-point manner.

21.1.2. Psuedos. These are five-digit numbers that are used internally within a switch for the processing of preset conferences. These numbers are assigned to boards created by software only.

21.1.3. Trunks. These are five-digit numbers that are used to interface a switch to the DRSN.

21.1.4. Subscriber Directory Numbers (SDNs). These are four-digit external numbers that are assigned to the individual users.

22. Instrument Button Scheme. To standardize the faceplate of the various telephone instruments (MLP, IST, CCP-40, SLP) used in the CSCCSN, the following standards have been established:

22.1. Color Code.

22.1.1. SCI HI - Red

22.1.2. SCI LOW - Yellow

22.1.3. TOP SECRET - Blue

22.1.4. WorldWide Secure Voice Conferencing System (WWSVCS) - Red/Yellow Stripe over Blue background

22.1.5. Unclassified - White

22.2. Button Breakdown.

22.2.1. SCI HI/LOW lines will be restricted to buttons 1-6. The CCSO can approve additional SCI lines on a case by case basis. If additional SCI lines are required, sequential buttons will be used following line button (L/B) 6.

22.2.2. Collateral lines will be restricted to the far left column/columns of buttons as needed.

22.2.3. Unclassified lines will be restricted to the far right column/columns of buttons as needed. If one button in a column is unclassified, then only unclassified lines will be assigned in that column.

22.2.4. Primary SDNs will be assigned as follows:


MLP L/B 12 L/B 48
IST L/B 10 L/B 40
CCP-40 L/B 8 L/B 40
SLP L/B 4 L/B 6

23. DRSN Directory. A worldwide DRSN telephone directory will be published and distributed to all users twice a year, in January and July. Local changes to the directory will be made by the applicable switch CCSO on the DISA electronic bulletin board directory. The CCM will extract the directory from the electronic bulletin board and publish it for all DRSN users in the Colorado Springs area.


24. Scope. This chapter applies to changes to the operational baseline of the Sensor Site Secure Voice Network (SSSVN). The configuration control of operational SSSVN sites is the responsibility of HQ AFSPC/SCO, with HQ AFSPC/SCOSV serving as the Colorado Springs Command and Control Switching Network (CSCCSN) Configuration Control Manager (CCM).

25. System Description. SSSVN is the primary secure communications for NORAD and US Space Command to/from sensor sites. This robust network integrates the secure voice requirements of Alternate Space at Dahlgren and Alternate Missile Warning at Offutt. Six voice trunks are provided at each sensor site. Four trunks route directly to CMASN, one trunk is dedicated for Missile Warning and is recorded at Cheyenne Mountain. The remaining trunks are in a trunk hunt group for use by Space, Testing, and other authorized users terminated on the Red Switch in CMAS. The SSSVN is not part of the Defense Red Switch Network (DRSN), but has obtained authorization to connect to the Red Switches. The sensor sites are restricted by software to only designated subscribers off the Red Switches in Cheyenne Mountain, Dahlgren, and Offutt.

26. Communication-Computer Security Officer (CCSO). The Site Commander will appoint an on-site individual as the CCSO. The on-site CCSO will be responsible for the configuration control and security of the SSSVN terminal equipment.

27. Configuration Control Process. Only the responsible on-site CCSO and the CSCCSN CCM can certify a proposed configuration change to the SSSVN.


The on-site CCSO may certify and implement certain types of changes to the SSSVN without review by the CSCCSN CCM. The following changes can be made on-site as long as they do not affect access to the network trunks -- telephone instrument installs, moves, and removals.

27.2. When a proposed change affects or changes access to the trunk from the site to the Red Switch at CMASN, approval must be gained from the CSCCSN CCM prior to implementation.

28. SSSVN Security. Since the SSSVN is directly connected to the CSCCSN Red Switch, certain security procedures must be adhered to.

28.1. Each SSSVN telephone instrument must be treated as a Secret-level terminal, as a STU-III with the key installed at all times.

28.2. The on-site CCSO must assure that access control to the SSSVN telephone instruments is limited to Secret-cleared personnel only.

29. Each site must complete an annual review of the SSSVN and provide a certification to the CSCCSN CCM. This review shall include a list of all telephones, their location, and office symbol. A statement that proper access control to the switch and all telephone instruments is maintained.

Director of Communications-Computer Systems

1. Command & Control Switch Network
2. Red Switch Numbering Plan


Hotlines 10,000 - 17,999

Psuedos 18,743 - 18,999

Trunks 19,000 - 19,999

SDNs Peterson Building 1470 2XXX
Peterson Building 1 3XXX

All Switches, US Only SCI 75XX-79XX

All Switches, US and Canadian SCI 70XX-74XX