6 June 1995




This instruction gives guidance for establishing policies and assigns responsibilities for the 50th Space Wing (50 SW) Consolidated Operations Room (COR), and interfaces with the Operational Software Maintenance Complex (OSMC) and associated modules. It implements Air Force Policy Directives (AFPD) 33-1, Command, Control, Communications and Computer (C4) Systems; 33-2, C4 System Security; and 10-6, Mission Needs and Operational Requirements Use Agreements. It applies to all 50 SW subordinate units consolidated by the "Lights Out" project.

Certified by: 50 SW/CC (Col Simon P. Worden)
OPR: 50 OSS/OSPG (SMSgt Ingrid A. Hurley)
Pages: 6/Distribution: F

1. General Policies:

1.1. This instruction provides the initial guidance necessary to prepare for operations of the COR and interface with the OSMC and associated modules. The intent is to provide a high-level overview of the tasks to be performed and the information necessary to accomplish them. The information contained within this instruction provides some of the data necessary for the development of COR specific operating instructions.

1.2 The COR allows consolidated computer operations to be conducted from a remote centralized location. The seven units which are to be consolidated are the Satellite Operations Complex (SOC)-31A, SOC-31B, SOC-32 (Global Positioning System (GPS) Master Control Station (MCS)), SOC-33, SOC-34, Range Control Complex-Falcon (RCC-F), and the OSMC. Operator Control Consoles (OCC) located in the COR remotely control equipment in the respective computer rooms. The term common module refers to the seven units which are external to the COR.

2. References: The following technical documents may be referenced to provide recommended changes and conflicts to this instruction.

2.1. AFI 10-1101, Operations Security (OPSEC) Instructions.

2.2. AFI 33-112, Automatic Data Processing Equipment (ADPE) Management.

2.3. AFI 33-113, Telecommunications Centers and Data Processing Centers Management.

2.4. AFI 33-101, Command, Control, Communications, and Computer Systems Management Guidance and Responsibilities.

2.5. AFI 37-132, Air Force Privacy Act Program.

2.6. AFSSI 5102, Computer Security (COMPUSEC) for Operational Systems.

2.7. AFSSI5013, Password Management.

2.8. AFSSM 5006, Computer System Security Officer's/Network Security Officer's Guide.

2.9. DOD 5200,28 STD, Information Security Program Evaluation.

2.10. FAFB OPLAN 32-1, FAFBR 355-1, Disaster Preparedness, Administration, Training, Disaster Response Force and Disaster Preparedness Response Board.

2.11. 50 SW 56-1, Mainframe Computer Security.

3. Responsibilities:

3.1. Common Module Personnel:

3.1.1. Appoint a primary and alternate point of contact to function as the interface with COR management on issues such as Communications-Computer Systems (C-CS) downtime scheduling, training, module testing, and database installs, etc.

3.1.2. Operate and maintain Mission Unique Equipment (MUE), External Interface Unit (EIU), Link 1 Telemetry Processing System (L1TPS), Network Status and Scheduling Change Notification System (NSSCNS), Subordinate Display System, etc.

3.1.3. Retrieve printouts from printers located in their respective modules. Establish procedures for handling printed products.

3.1.4. Perform Communication Security (COMSEC) officer responsibilities within the modules to include Cryptographic KG resets and Programmable Read Only Memory (PROM) installs.

3.1.5. Perform emergency system shutdown procedures in coordination with COR computer operators.

3.1.6. Perform non-COR Computer Security Officer (CSO) duties.

3.1.7. Provide physical security of the computer room.

3.1.8. Provide access for COR personnel to the module and computer rooms.

3.1.9. Order supplies for the computer room.

3.1.10. Perform escort for janitorial services.

3.1.11. Provide SIP management.

3.1.12. Update Emergency Action Plans (EAP).

3.1.13. Provide small computer management.

3.1.14. Manage Automated Data Processing Equipment (ADPE) within the module.

3.1.15. Provide the COR with authorization lists for printed output and magnetic media.

3.2. OSMC (specific responsibilities):

3.2.1 Monitor module activities after duty hours.

3.2.2. Monitor copier.

3.2.3. Scheduling.

3.2.4. Changing Series/1 diskettes.

3.2.5. Connect Annex/Operational Readiness Trainer (ORT) to other MODs (testing and live).

3.2.6. Generate and maintain user ID's for all wing C-CS users.

3.3. COR Operations:

3.3.1. Perform duties and responsibilities consistent with developing operating instructions relative to: Temperature and humidity. Magnetic media controls. Information security. Magnetic storage librarian function. Off-site storage. Physical security. Shift activity and turnover logs. Power-up/power down procedures. Housekeeping. Maintenance of automatic data processing equipment. System initialization. Severe weather conditions. Product distribution. Customer education. Contingency and catastrophic failures. Status reporting. Procedures and analysis function. Duties and responsibilities of shift supervisor or leader. Configuration Management of COR equipment. Training.

3.3.2. COR Specific Operations: Provides mainframe support to four space operations squadrons and the 50th Logistics Support Squadron. Backup facility for print products of supported units (see above). Provides print products after duty hours, weekends, and holidays for OSMC customers. Ensure all tapes and cartridges are identified by the system security packages (RACF and CA-Top Secret). An on-line tape management system that provides real-time checking; i.e. the Tape Library Management System (TLMS) from Computer Associates, protects magnetic media so it is only permitted to be mounted on the system they are designed for. Tape conversion. Nine track drives will be available in the COR to meet specific requirements. Tape conversion (reel to cartridge) will primarily be done in the COR. For data pattern traffic generation (AUTODIN) purposes: Data will be recorded on tape cartridges. Conversion to nine track will be done upon customer request. The user is responsible for delivering products to the base communications center. The OSMC and SOC-34 will be used as back-ups for tape conversions.

4. General Guidance and Procedures:

4.1. Normal Operations:

4.1.1 During normal operations all computer operator functions will be accomplished from the COR. Communication between the COR and common modules will be done primarily by administrative point to point telephone. Secure communication is available via STU-III. Manning of the COR will be sufficient to complete assigned tasks.

4.1.2. Unscheduled outages, immediate computer support, and recovery actions will be accomplished under the direction of the module flight commander. In the OSMC these same actions will be directed by the on duty system shift supervisor. In the RCC, immediate recovery, unscheduled outages should be coordinated with Falcon Controllers (Mod 3/4). Information should be passed to scheduling shift supervisors (ASAP) after the fact to keep 22 SOPS/CC/DO informed. Recovery actions should not be delayed to pass information only.

4.1.3 All scheduled actions will be executed under the direction of the module flight commander, system shift supervisor (OSMC), and Falcon controllers (RCC) as appropriate. In room support by computer operations personnel will be coordinated with the unit POC.

4.1.4. System Maintenance Environmental conditions in the module computer room is remotely monitored. COR computer operators respond to module alarms in the computer rooms upon notification of exceeded environmental conditions. 50 LSS/SCOY provides in-room support for system maintenance. All system maintenance is coordinated in advance with the unit POC. System maintenance includes data base installs, module testing, and the testing and installation of automated scripts IAW the Logistic Support Plan for the Lights Out COR.

4.2. Contingency Operations:

4.2.1. In the event of an extended COR outage, computer operations can be accomplished within each module. One Operator Control Console (OCC) will be installed in each computer room to control the mainframe in case of a COR outage. Computer operators will be deployed to each module to perform operations until the COR is restored to normal operations.

4.2.2. Contingency operations commence within 8 - 10 minutes of any change that impacts the
capability to support the mission of the Satellite Operations Complexes (SOC) and/or the Range Control Complex-Falcon (RCC-F).

4.2.3. Deploying operators will take the tape media necessary to sustain module computer operations.

4.2.4. Contingency operations will be exercised on a quarterly basis.

4.3. System Security:

4.3.1 The COR processes Secret data in the System-High mode, with National Computer Security Center Class C2 functionality, at all times while in operation. This means that the COR is processing SECRET information at all times.

4.3.2. A password management program is established for the COR. The COR Computer Security Officer (CSO) creates, issues, and controls passwords for the COR system. The CSO is responsible for ensuring the basic criteria set forth in AFSSI 5013 are met. The Consolidated Operating Room CSO will coordinate with the OSMC Computer Security Officer and module Computer Security Officer's to establish user accounts on the individual module systems (for COR computer operators).

4.4. Training:

4.4.1. Formal: Initial contractor training consists of formal classes provided by the contractor. This training will be provided to both operator and maintenance personnel on a one-time basis only.

4.4.2. In-house Training: The contractor provides informal training to the computer operators during installation and checkout. Module personnel will be trained to perform all residual tasks prior to COR transfer. Those computer operators that are not able to attend the various formal training classes will be trained informally through On-the-Job Training and Instructional System Development. Training materials will be supplied to the Air Force (by the vendor) to be incorporated into the master COR training program. A training plan, IAW the Logistics Support Plan, will be developed to include the module equipment training necessary to sustain normal and contingency operations.

4.5. Configuration Management:

4.5.1. Installations and modifications to module systems will be handled IAW the Logistic Support Plan for the Lights Out COR.

4.5.2. COR configuration control will be the responsibility of 50 SCS. Any modifications to the COR will be controlled by 50 SCS and coordinated with the common module Modification Control Boards (MCB).

4.6. COR Maintenance: Maintenance activities are specified in the Logistics Support Plan for the Lights Out COR.