CD System Requirements Document (SRD).pdf

CUI/SP-CTI//SP-EXPT

Strategic Warning and Surveillance Systems

(SW&SS)

Acquisition Delta

SYSTEM REQUIREMENTS DOCUMENT (SRD)

COBRA DANE Radar (AN/FPS-108)

3 October 2024 Version 2.0.0

Prepared by:

COBRA DANE Radar Division (SSC/SZQC) Peterson SFB, Colorado

OPR: SSC/SZQC

Phone: DSN 692-9390; Commercial (719) 554-9390

This document contains information that is EXEMPT FROM MANDATORY DISCLOSURE under the Freedom of Information Act.

Exemptions b (2) and b (3) apply.

WARNING—This document contains technical data and /or technology whose export or disclosure to non-U.S. Persons, wherever located, is restricted by the International Traffic in Arms Regulations (ITAR) (22 C.F.R. Section 120-130) or the Export Administration Regulations (EAR) (15 C.F.R. Section 730-774). This document CANNOT be exported (e.g., provided to a supplier outside of the United States) or disclosed to a non-U.S. Person, wherever located, until a final jurisdiction and classification determination has been completed and required U.S. Government approvals have been obtained. Violations are subject to severe criminal penalties.

DESTRUCTION NOTICE—For classified documents, destroy in accordance with DoD 5200.01 and AFI16-404. For unclassified documents, destroy by any method that will prevent disclosure of the contents or reproduction of the document.

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only, Critical Technical Information (CTI), Export Controlled, 3 October 2024. Other requests for this document must be referred to SSC/SZQC at 1050 E. Stewart Ave. Peterson SFB, CO 80914.

Controlled By: SSC Controlled By: SZQC CUI Category: CTI, Export Controlled Distribution Statement: D

THIS PAGE IS INTENTIONALLY BLANK

iii

REVISION HISTORY

Change Version Date

AFLCMC/HBQC Initial Look 0.8.2 29 Jun 2015 AFLCMC/HBQC Initial Look Updates AFLCMC/HBQC Updates AFSPC and MDA Action Officer Updates AFLCMC/HBQE/I/R Updates AFSPC & MDA 3-ltr Review; Signatures Replaced AFTAC SCG with AFSPC SCDG SSC/SZQC Rewrite Initial Update

0.9.4 0.9.5 0.9.6 0.9.7 1.0.0 1.0.1 2.0.0

24 Jul 2015 08 Sep 2015 30 Oct 2015 10 Nov 2015 04 Dec 2015 25 Apr 2016 03 Oct 2024 iv

APPROVED BY

Prepared By:

Beth Blakney (2015 Editions), MITRE Phil Chorman (2015, 2024 Editions), Riverside Research Institute Dave Eherenman (2015 Editions), MITRE Stanley Toenjes (2016 Edition), ETASS David Dirksen (2024 Edition), Riverside Research Institute v

Table of Contents

1 SCOPE 1

1.1 System Identification

1.2 System Overview

1.3 Document Overview

2 APPLICABLE DOCUMENTS

2.1 General

2.2 Government Documents

2.2.1 Specifications, Standards, and Handbooks

2.2.2 Other Government Documents, Drawings and Publications

2.3 Non-Government Publications

2.4 Order of Precedence

2.5 Military Standards (MIL-STD)

3 SYSTEM REQUIREMENTS

3.1 System Definition

3.2 States and Modes

3.2.1 COBRA DANE System States

3.2.2 Mode Transitions

3.2.3 Mode Descriptions

3.2.4 Correlation Between Modes and System Functions

3.3 Functional Requirements

3.3.1 Functional Missile Defense Mission Requirements

3.3.2 Functional Space Surveillance Mission Requirements

3.3.3 Retained Functional Intelligence Mission Requirements

3.3.4 Deactivated Early Warning Mission Requirements

3.3.5 Functional Cross Mission Requirements

3.3.6 Functional System Requirements

3.4 System External Interface Requirements

3.4.1 Interface Identification and Diagrams

3.4.2 Interface Requirements

3.4.3 Spectrum Management

3.5 System Internal Interface Requirements

3.5.1 Interface Identification and Diagrams

vi

3.5.2 Interface Requirements

3.6 System Internal Data Requirements

3.7 Adaptation Requirements

3.8 Safety Requirements

3.8.1 Safety

3.8.2 Personnel and Equipment Safety

3.8.3 System Safety

3.8.4 Flammable and Arc-Resistant Materials

3.8.5 Electrical Overload protection

3.8.6 Shock protection

3.8.7 Radiation Hazards

3.8.8 Hazardous Materials

3.9 Security and Privacy Requirements

3.9.1 Physical Security Modifications

3.9.2 System Security

3.9.3 Information System Security

3.9.4 Computer Security

3.9.5 Access Control

3.9.6 Identification and Authentication

3.9.7 Audit

3.9.8 Integrity

3.9.9 Authorization and Authentication

3.9.10 Positive Control

3.10 System Environment and Survivability Requirements

3.10.1 Environmental Conditions

3.10.2 Ice Load and Wind

3.10.3 Positioning, Navigation, and Timing Standard

3.10.4 Electrostatic Discharge from Human Source

3.10.5 Electromagnetic Interference

3.10.6 Pressure

3.11 Computer Resource Requirements

3.11.1 Computer Hardware Requirements

3.11.2 Computer Hardware Resource Utilization Requirements

3.11.3 Computer Software Requirements

vii

3.11.4 Computer Communication Requirements

3.12 System Quality Factors

3.12.1 Human Performance/Human Engineering

3.12.2 Mean Time Between Critical Failure (MTBCF)

3.12.3 Reliability

3.12.4 Maintainability

3.12.5 Availability

3.13 Design and Construction Constraints

3.13.1 Open Technology/Modular Open Systems Approach (MOSA)

3.13.2 Electromagnetic Radiation

3.13.3 Interchangeability

3.13.4 Seismic Hold Down Rails

3.13.5 New CD Design

3.14 Personnel Requirements

3.15 Training Requirements

3.16 Logistics Requirements

3.16.1 Transportability

3.17 Packaging Requirements

3.18 Statutory, Regulatory, and Certification Requirements

3.18.1 Statutory Requirements

3.18.2 Regulatory Requirements

3.18.3 Certification Requirements

3.19 Demilitarization and Disposal

4 VERIFICATION PROVISIONS

4.1 Verification methods

4.1.1 Inspection

4.1.2 Demonstration

4.1.3 Analysis

4.1.4 Test

4.1.5 Certification

4.2 Verification Matrix

4.2.1 Contractors Responsibility

4.2.2 USG Responsibility

5 REQUIREMENTS TRACEABILITY

viii

5.1 Traceability to Capability Document or System Specification

5.2 Traceability to Subsystems Requirements

Appendix A Acronyms

Appendix B Classified Tables, Figures, and SAPs ix

List of Figures Figure 1.2-1 COBRA DANE Block Diagram Legacy (Top) and Future (Bottom) Figure 1.2-2 COBRA DANE Radar Figure 3.2-1 CD System States and Modes Figure 3.2-2 CD Missions and Mission Transitions Figure 3.5-1 COBRA DANE Functional Diagram with Data Interface Interconnections.

Legacy (top), Modernized (Bottom) x

List of Tables Table 1.2-1 Array Characteristics Table 1.2-2 L-Band Frequency Characteristics Table 1.2-3 Transmitter Characteristics Table 3.2-1 CD Missions, Modes, and States Relationships Table 3.2-2 Radar Energy Management Priorities Normal Mode Table 3.2-3 Function and Mode Relationships Table 3.3-1 Object Characteristics Table 3.3-2 Tracking Performance Table 3.3-3 Object Classification Requirements Table 3.3-4 COBRA DANE Future Threat Complex (CDFTC) Table 3.3-5 Scenarios 1 and 2 State Vectors* Table 3.3-6 Scenarios 1 and 2 State Vectors (Continued) Table 3.3-7 Scenarios 1 and 2 State Vectors (Continued) Table 3.3-8 Scenario 1 Data Collection Profile Table 3.3-9 Scenario 2 Data Collection Profile Table 3.3-10 Scenario 3 Events and State Vectors Table 3.3-11 Scenario 3 Radar Cross Section Table 3.3-12 Scenario 3 Radar Collection Profile Table 3.3-13 Scenario 4 Events and State Vectors Table 3.3-14 Scenario 4 Data Collection Profile Table 3.3-15 Scenario 4 Data Collection Priorities Table 3.3-16 Scenario 5 Events and State Vectors1 Table 3.3-17 Scenario 5 Data Collection Profile Table 3.3-18 Scenario 5 Data Collection Priorities Table 3.3-19 Scenario 6 Data Collection Profile Table 3.3-20 IRV Characteristics Table 3.3-21. Sensor Operations Table 3.3-22. Number of Concurrent Pulse Trains Table 5.1-1 Source Document Traceability and Verification Matrix Table 5.2-1 IA Controls

1 SCOPE

1.1 System Identification

This System Requirements Document (SRD) establishes requirements for the co-primary Ground-Based Midcourse Defense (GMD) mission and Space Domain Awareness (SDA) mission operational requirements for the COBRA DANE AN/FPS-108 (Army-Navy Fixed, Radar, Search) Radar System located at Eareckson Air Station, Shemya Island, Alaska. The functional and performance requirements contained herein reflect a combination of requirements established for the COBRA System Modernization (CDSM) program, and the COBRA DANE Upgrade (CDU) program which added Missile Defense mission support capabilities. As such, these requirements may not reflect the as delivered system baseline performance levels of all installed equipment.

1.2 System Overview

COBRA DANE supports two co-equal mission areas for the United States Space Command (USSPACECOM), Missile Defense and Space Domain Awareness (SDA). COBRA DANE supports the Missile Defense mission by providing midcourse coverage for the Missile Defense System. COBRA DANE detects Intercontinental Ballistic Missiles (ICBMs) and Sea-Launched Ballistic Missiles (SLBMs), classifies reentry vehicles (RVs) and other missile complex objects, provides real-time information to the Ground-Based Midcourse Defense (GMD) Fire Control/Communications (GFC/C), and provides tracking of threat ballistic missiles with sufficient accuracy to commit the launch of Ground Based Interceptors (GBIs), and update the target tracks to the interceptor while the interceptor is in flight.

COBRA DANE also supports the SDA Custody and Safety of Flight missions by detecting, tracking, correlating, and characterizing man-made Resident Space Objects (RSOs), primarily in the Low-Earth Orbit (LEO) regime, including space debris and early observation of Non- Cooperative Launches (formerly known as New Foreign Launches (NFL’s)). It operates as part of the Space Surveillance Network (SSN) and provides metric observation data to its command-and-control nodes. Additionally, COBRA DANE supports the National Space Defense Center’s (NSDC) Protect and Defend mission by performing High-Rate Revisit (HRR) observations to maintain custody of high interest RSOs and High Value Asset (HVA) Clearing via its ability to track Closely Spaced Objects (CSOs).

COBRA DANE also supports the Space Measurement and Signature Intelligence (MASINT) mission (formerly known as Space Object Identification (SOI)), by providing narrowband radar signature data of man-made RSOs in the LEO regime. The collected signature data is analyzed to determine satellite characteristics such as size, shape, motion, and orientation. Space MASINT information is used to ascertain the mission and operational status of various payloads and aids in forecasting maneuvers or deorbits.

The Missile Defense mission takes precedence in the event the Combatant Commander declares an immediate emergency based on an imminent threat of ballistic missile attack on the US and its allies.

The COBRA DANE Radar was originally developed by Raytheon in the mid-1970s, was modernized in the early-1990s by Raytheon under the COBRA DANE System Modernization (CDSM) program and was upgraded in the early-2000s by Raytheon under the COBRA DANE Upgrade (CDU) program. The CDSM program replaced many of the back-end radar subsystems and established its current baseline system configuration and performance.

The CDU program modified the operational software and other software items and added Battle Management Command, Control and Communications (BMC3) Communications Processing Equipment (BCPE) for the Missile Defense (MD) mission, which established its current Missile Defense baseline system configuration and performance. Note that where BMC3 is referenced in this document, GFC/C is synonymous. The current and future COBRA DANE System Block Diagrams are shown in Figure 1.2-1.

Time Standard Unit

Digital Signal Processing Receiver Exciter (DPSREX)

Transmit Beam Forming Network

Transmitter Group

A R R A Y

Receive Beam Forming Network

Mission Computer HCI

Cluster

Mission Computer HCI

Cluster

BCPE

CFE

COM

Equip

CSEIOC

Console

SOSC Console (Maintenance)

IOC Console (Operations)

IOC

Console

(Tactical)

GFE

Communications

Equipment

Post Mission Support

Terminals

Beam Steering

Unit

BCPE – BMC3 Communications Processing Equipment CFE – Contractor Furnished Equipment CSE – CDU Support Equipment GFE – Government Furnished Equipment HCI – Hyperconverged Infrastructure IOC – Intelligence Operations Center SOSC – System Operation and Status Console

Figure 1.2-1 COBRA DANE Block Diagram Legacy (Top) and Future (Bottom)

Figure 1.2-2 shows the COBRA DANE Radar.

Figure 1.2-2 COBRA DANE Radar

The system capabilities are listed in Table 1.2-1 through Table 1.2-3 below, and in Table B-2 in the SRD Classified Appendix B.

Table 1.2-1 Array Characteristics Diameter 94.5 feet

Gain 47.7 decibel

Polarization CD074

Coverage:

Normal (Cone Half Angle [CHA]) 60° CHA

Extended (Below 30° Elev.) +/- 68° azimuth

Elements:

Total 34,768

Active 15,360

Illumination (Sum - TX/RX) CD075

Illumination (Difference - RX) CD076

Subarrays 96

Table 1.2-2 L-Band Frequency Characteristics Narrowband 1215-1250 MHz

Wideband 1175-1375 MHz

Table 1.2-3 Transmitter Characteristics Number/Type 96 Traveling Wave Tubes (TWTs)

Peak Power 15.3 Megawatts (MW)

Average Power 0.92 MW

1.3 Document Overview

This SRD describes the technical requirements for which the System was designed and which the Operations, Maintenance and Sustainment (OM&S) contractor will be responsible for observing and adhering to during the period of performance (PoP) for the contract. The document is divided into the following sections:

Scope – Identifies the system to be addressed by the document and provides an executive summary of the purpose and mission for the system.

Applicable Documents – List of the documents referenced within the SRD.

System Requirements – Identifies the requirements describing the system as built. If there are no requirements for a given subsection, the paragraph for the subsection will state such. If a given requirement fits into more than one subsection, the requirement will be stated once and referenced from the other paragraphs.

Verification Provisions – This section is not used as there is no anticipation of verifying all the requirements contained herein.

Requirements Traceability – Maps the requirements contained within this document to the Capability Description Document or associated higher level specification.

Appendix A – Acronyms

Appendix B – Classified Requirements. The classified requirement values are in a table in the classified Appendix B, identified with a prefix CD, SYS, MD, SS, or IN. Unclassified references to these values use the form CD001, SYS002, etc.

THIS PAGE IS INTENTIONALLY BLANK

2 APPLICABLE DOCUMENTS

2.1 General

Documents listed in this section are specified in Section 3 of this SRD. This section does not include documents cited in other sections of this specification or recommended for additional information or as examples. While every effort has been made to ensure the completeness of this list, contractors are cautioned that they should meet all specified requirements of the documents cited in Sections 3 of this specification, whether or not they are listed. The following specifications, standards, and handbooks form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract. The documents, tables, and current Software feature set requirements have been merged and deconflicted in this document to accurately reflect the state of the system.

2.2 Government Documents

2.2.1 Specifications, Standards, and Handbooks

1. 31P6-2FPS108-xx, COBRA DANE Radar Series of Technical Manuals (TMs)/Technical

Orders (TOs)

2. System Specification Volume I for the Modernized COBRA DANE AN/FPS-108 System (CDSM A Spec), (SS-CDSM0001C), 7 Mar 1990

3. System Specification Volume II for the Modernized COBRA DANE AN/FPS-108 System, (SS-CDSM0001C), 28 Aug 1989, Revised 7 Mar 1990

4. Missile Defense Agency (MDA) Ballistic Missile Defense System (BMDS) COBRA DANE Element Specification Version 1.0 SN-CD-ES-1.0-20150805, 5 Aug 2015

5. MDA COBRA DANE Element Specification Change Notice (SCN) Object Classification (OC) SCN-CD-0001, 21 Dec 2017

6. MDA System Specification Version 23.2 N-2471-11.1, Oct 6, 2023

7. MDA System Description Document Version 23.2 S-1275-45.0, July 26, 2023

8. Interface Control Document for COBRA DANE System Modernization (CDSM) Radar Subsystem (CDSM ICD), (G526783), Rev B, 6 Apr 1994

9. Interface Design Document for the COBRA DANE System Modernization (CGG526712), 1 Oct 1992

10. Interface Requirements Specification for the COBRA DANE System Modernization (CGG490461, 1 Feb 1991

11. General Interface Control Document Communications COBRA DANE System Modernization Program, Rev A, 2 May 1992

12. COBRA DANE Upgrade (CDU) Test Article Capabilities Document (TACD), (H312407), Revision H, 8 Dec 2010

13. Ground-Based Midcourse Defense COBRA DANE Upgrade (CDU) BCPE Internal Interface Control Document (ICD) (CDU/BCPE ICD), (H328828), Rev B, 29 Mar 2004

14. Ground-Based Midcourse Defense COBRA DANE Upgrade (CDU) Interface Control Document (ICD) (GMD ICD), (H313775), Rev A, 5 May 2005

15. CDVA10000ICD01 - CD Virtual Address Extension-Replacement (VAX-R) BCPE Interface Control Document (ICD), Rev A

16. CDVA10000SYD01 - System Design Document (SDD) for the COBRA DANE VAX-R ADPE, Rev A

17. CDVA11000SRS01 - CD VAX-R Operating System Augmentation (OSA) Software Requirements Specification (SRS), Rev A

18. CDVA12000SRS01 - CD VAX-R Mission (MSN) Software Requirements Specification, Rev A

19. CDVA13000SRS01 - CD VAX-R Simulation (SIM) Software Requirements Specification, Rev

20. CDVA14000SRS01 - CD VAX-R Operational Support Software (OSS) Software Requirements Specification, Rev

2.2.2 Other Government Documents, Drawings and Publications

1. Headquarters, Space Operations Command (HQ SpOC) COBRA DANE Security

Classification Guide (SCG), 6 Feb 2024

2. Ballistic Missile Defense (BMD) Radars Security Classification Guide, 22 Jul 2013

3. United States Strategic Command Security Classification Guide for Space Surveillance Operations (SSOps), 15 Oct 2014

4. Air Force Manual (AFMAN) 36-2100, “Military Utilization and Classification.” 7 April

5. Code of Federal Regulations (CFR) Title 21, Chapter I, Subchapter J

6. Combat Delta 2 Space Domain Awareness Operating Instruction (SDA OI)

7. Committee on National Security Systems Advisory Memorandum (CNSSAM) TEMPEST/01-13, RED/BLACK Installation Guidance, 17 January 2014

8. Department of Defense (DoD) Manual 4140.01, Volume 11, “DoD Supply Chain Materiel Management Procedures: Inventory Accountability and Special Management and Handling” Change 4, November 4, 2022

9. DoD Manual 5200.1, Volume 1, “DoD Information Security Program: Overview, Classification, and Declassification” 24 Feb 2012, Change 2, 28 Jul 2020

10. DoD Manual 5200.01. Volume 2, “DoD Information Security Program: Marking of Information” 24 Feb 2012, Change 4, 28 Jul 2020

11. DoD Manual 5200.01 Volume 3, “DoD Information Security Program: Protection of Classified Information” 24 Feb 2012, Change 3, 28 Jul 2020

12. DoD Instruction 8500.01, "Cybersecurity,” 14 Mar 2014

13. National Geospatial-Intelligence Agency (NGA) Standardization Document, NGA.STND.0036_1.0.0_WGS84, Department of Defense World Geodetic System 1984, Version 1.0.0, 2014-07-08

14. National Telecommunications and Information Administration (NTIA), Manual of Regulations and Procedures for Federal Radio Frequency (RF) Management, Jan 2021

15. National Institute of Science and Technology (NIST) Special Publication 800-53 Revision 4, “Security and Privacy Controls for Federal Information Systems and Organizations”, Dec 2014

16. Unified Facilities Criteria (UFC) 3-301-01 Structural Engineering, 1 Oct 2019

2.3 Non-Government Publications

The following documents form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

1. Interface Design Description Ground-Based Midcourse Defense Fire Control/Communications and COBRA DANE Upgrade, (D742-14204-2), Rev D, 8 April 2008, The Boeing Company, Huntsville, AL 35824-3001

2. D742-14213-1, 04 Test Bed Interface Design Description for Embedded Test and COBRA DANE Upgrade, D742-14213-1, The Boeing Company, Anaheim, California 92803-3105.

3. Generic Requirements (GR)-63-CORE Issue Number 05, Network Equipment-Building System (NEBS) Requirements: Physical Protection, Dec 2017

4. International Electrotechnical Commission (IEC)-61000-4-2 Edition 2.0, Electromagnetic Compatibility (EMC) - Testing and Measurement Techniques - Electrostatic Discharge Immunity Test, 2008

5. International Organization for Standardization (ISO) 14119:2013(en) Safety of machinery

— Interlocking devices associated with guards — Principles for design and selection, 2013-10.

6. Initial Block Threat Database Version 5.1 Compact Disk (CD), dated 21 Dec 2001, The Boeing Company, Anaheim, California 92803-3105.

7. Radar Cross Section (RCS) Data Addendum to Initial Block and Block 1 Increment 1 Databases, 9 Aug 2002

2.4 Order of Precedence

Unless otherwise noted herein or in the contract, in the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

2.5 Military Standards (MIL-STD)

All references to MIL-STDs or related products such as Details and Handbooks referred to the version that was in effect at the time the requirement was written. Future changes to the system, (e.g., obsolete parts replacement) or spares replenishment will use the current MIL-STD, Detail, or Handbook version, as referenced within this SRD.

1. Military Handbook (MIL-HDBK)-454C, General Guidelines for Electronic Equipment, 21 Sept 2021

2. MIL-STD-461G, Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment, 11 Dec 2015

3. Military Detail (MIL-DTL)-14072G, Finishes for Ground Based Electronic Equipment, 17 May 2021

4. MIL-STD-1366E, Department of Defense: Interface Standard for Transportability Criteria, 31 Oct 2006

5. MIL-STD-1472H, Department of Defense Design Criteria Standard: Human Engineering, 15 Sep 2020

6. MIL-STD-2073-1E (Change 4), Department of Defense Standard Practice for Military Packaging, 22 Apr 2019

7. MIL-STD-464D, Department of Defense Interface Standard: Electromagnetic Environmental Effects, Requirements for Systems, 24 Dec 2020

8. MIL-STD-810H (Change 1), Department of Defense Test Method Standard:

Environmental Engineering Considerations and Laboratory Tests, 18 May 2022

3 SYSTEM REQUIREMENTS

3.1 System Definition

The CD System shall (001) include:

a. The radar subsystems, to include:

1. Antenna Array Subsystem,

2. Transmitter Group Subsystem,

3. Digital Signal Processor and Receiver Exciter (DPSREX) Subsystem,

b. Mission Computer Subsystem,

c. Battle Management Command, Control and Communications (BMC3) Communications Processing Equipment (BCPE),

d. CDU Support Equipment (CSE) consisting of software maintenance workstations,

e. Communication Interface and Support Subsystem, and

f. Technical Facility Subsystem.

See Figure 1.2-1for a block diagram of the above listed equipment.

3.2 States and Modes

3.2.1 COBRA DANE System States

As used in the SRD, a State is defined as a high-level control condition or status used to govern software and radar system behavior. As used in the SRD, a Mode is a low-level software control condition or status used within a State to govern software and radar system behavior.

The CD System shall (002) consist of a set of distinct System States within which the System Modes, as specified in 3.2.2, are defined.

These System States are 1) the Startup State (where ADPE components initialize and begin interaction with each other), 2) the Standby State (ADPE components initialized for running the CD software), and 3) the Operational State (ADPE components connect, initialize, and command radar and external communication interfaces for mission operation) and are depicted in Figure 3.2-1.

Figure 3.2-1 CD System States and Modes

3.2.1.1 GMD System States

Ground-Based Midcourse Defense (GMD) Fire Control/Communications (GFC/C) uses two GMD System States as shown in Table 3.2-1 right hand column:

• Normal State

• Alert State: GMD Sensor Tasks (Cued Search Acquisition Tasks and Track/Classification Tasks) are accepted and performed only in this State.

Table 3.2-1 CD Missions, Modes, and States Relationships

Active Mission SDA Mission Active?

Applicable Modes

CD States GMD System States

Missile Defense Yes Surveillance Operational1 Normal/Alert No Missile Defense Normal/Alert

Space Domain Awareness

Yes Normal Normal Yes Surveillance Normal/Alert

Intelligence Yes Normal Normal No Intelligence Normal

1Or Simulated Operational State. Either of these States is entered from CD Standby State. CD Standby State is entered at the completion of start-up sequence.

The CD mission software will enter the GMD System State as commanded by GFC/C, if the CD System is able to comply. The CD mission software may perform a Mode transition in response to GMD System State changes, as shown in Figure 3.2-2.

3.2.2 Mode Transitions

The CD System shall (002B) communicate with GFC/C to report status and receive GFC/C messages.

If GFC/C changes the GMD System State to the Alert State, the CD System shall (002C) switch to Surveillance or Missile Defense in support of the Missile Defense Mission if able to comply.

The transitions between Modes in the Operational State (and Simulated Operational State) for the CD System are illustrated in Figure 3.2-2. On entry to Missile Defense Mission, if no missile object is in track, then the Mode is Surveillance, otherwise the Mode is Missile Defense. On entry to Intelligence Mission the Mode is Normal.

Figure 3.2-2 CD Missions and Mission Transitions

The CD System shall (002D) track and categorize objects acquired in support of all missions.

When an object is detected, if it is non-Earth impacting, then the System shall (014) carry out the appropriate Space Surveillance functions as indicated in 3.3.2.3

If the object is predicted to be Earth- impacting, it is categorized as a missile.

When an object has been categorized as a missile, the CD System shall (002E) determine its Threat Characteristic.

The Threat Characteristic of missile objects is defined as follows:

• Threat: A missile's predicted earth impact point is within a Threat Defended Area and its current range to CD is < CD007.

• Test Threat: A missile's predicted earth impact point is within a Test Threat Defended Area and its current range to CD is < CD007.

• Non-Threat: A missile not satisfying the above cases (i.e., a missile’s predicted earth impact point is outside of all Threat and Test Threat Defended Areas or its current range to CD is > CD007).

Any tracked object categorized as a missile object by the CD System shall (002F) trigger an automatic switch to either Intelligence Mode or Missile Defense Mode.

The switch is determined as follows:

• Missile Defense Mode is entered when either:

o Any Threat's range to CD is< CD008; OR o All objects impacting a Threat Defended Area are Threats (i.e., have current ranges < CD007)

• Intelligence Mode is entered when the inverse of the above conditions applies, i.e.:

o All Threats' ranges to CD are> CD008; AND o Any objects impacting a Threat Defended Area are Non-Threats

The CD System shall (003) transition between Normal, Intelligence, Surveillance and Missile Defense Modes in no greater than MD01 time units.

Automatic and Manual Operation The CD System shall (004) initialize operation through manual actions which establish operational Modes as in 3.2.1 for subsequent automatic control of CD System operation.

The CD System manual functions shall (005) minimize manual interventions during target acquisition, data collection; switching between various operating Modes.

The CD System message processing (except transmission of the System Report message or selection of data to be transmitted to the users) shall (006) be limited to remedial or override actions only, including the drop of use of System resources on any given object.

3.2.3 Mode Descriptions

3.2.3.1 System Modes

The CD System’s ADPE and radar sub-systems shall (007) operate in the Modes defined in the following paragraphs, illustrated in Figure 3.2-1, CD system States and Modes:

Computer Ready Mode In the Computer Ready Mode, the mission computer is operational, and the mission software is loaded and ready for operator interaction.

Transition from Computer Ready to System Standby in the CD System shall (007B) be accomplished in no greater than ten seconds.

System Standby Mode In the System Standby Mode, the communication channels are enabled, and radar subsystem components are pre-heated.

Transition from System Standby to System Operation in the CD System shall (007C) be accomplished in no greater than 1.5 minutes.

System Ready In the System Ready Mode, the mission software is ready to begin executing real-time Satellite Data, Mission Planning, and Search Detection-tasks, upon transition into Operational Mode.

3.2.3.2 Operating Modes

The CD System shall (007D) have four (4) Operating Modes in the Operational- or Simulated Operational-State, as illustrated in Figure 3.2-2, CD Missions and Mission Transitions:

• Normal Mode,

• Intelligence Mode,

• Surveillance Mode, and

• Missile Defense Mode.

Within the limits of available radar resources, the CD System in the Surveillance Mode shall

(008) perform Missile Defense search and Space Surveillance operations, including satellite-based radar calibration.

Within the limits of available radar resources, the CD System in the Missile Defense Mode shall

(009) perform Missile Defense search; GFC/C-requested cued search, track and object classification tasks, and Intelligence data collection.

Normal Mode Normal Mode may be entered manually, i.e., when commanded by the operator, at the end of the startup sequence from Standby State. It is, as its name implies, the Mode in which CD normally operates.

Normal Mode performs:

• Continuous search of the three-dimensional (3-D) spaces defined by a set of active Search Fences,

• Space Surveillance operations to search for and acquire data on Earth Satellite Vehicles (ESV),

• Satellite-based radar calibration operations to calibrate radar performance.

In the Normal Mode, the CD System shall (010) utilize fence searches based on specific Missile Defense and/or Space Surveillance Mission requirements and precedence.

The CD System shall (011) also conduct Space Surveillance functions described in paragraph 3.3.2.

The CD System shall (012) be able to change the allocation of radar resources between these missions (see Table 3.2-2).

Table 3.2-2 Radar Energy Management Priorities Normal Mode

Priority Task/Action

1. Track unknown object to determine if Earth-impacting

2. Erect Intelligence Surveillance fences

3. Erect special Space Surveillance fences

4. Space Surveillance, significant unknown non-impacting object and high-priority known ESV

5. Space Surveillance, non-significant unknown non-impacting object and low-priority known ESV

6. Enhance search fences

The Normal Mode of operation of the CD System shall (016) consist of Space and Missile Surveillance, categorization of detected objects per paragraph 3.3.6, and if sufficient resources are available, Space Surveillance tasking in accordance with (IAW) the tasking described in paragraph 3.3.2and its subparagraphs.

The CD System shall (017) format and transmit messages in support of Space Surveillance functions.

During Normal Mode operation, the CD System shall (018) properly format per paragraph 3.3.3 and its subparagraphs and transmit to the end-users on a non-interfering basis, data acquired from a previous Intelligence Mission.

Priorities of Normal Mode functions are shown in Table 3.2-2.

Upon re-initiation of Normal Mode operation following an Operating Mode transition, the CD System shall (019) transition IAW paragraph 3.3.6.3

In Normal Mode, the CD System shall (021) allow searches added by the operator and be limited only by radar resources.

The CD System shall (022) utilize the full fence suite using no more than 90 percent (%) of the radar resources.

The CD System shall (022A) inactivate all previously active Search Fences (if any) and activate a set of preselected Normal Search Fences upon entry to Normal Mode.

The CD System shall (022B) allow the user to activate and inactivate all Search Fences of appropriate range (according to the active scheduling interval template as described in Section 3.3).

Each Search Fence is designed to consume a predictable amount of radar energy.

The CD System shall (022C) allow the user to define and edit the control parameters of inactive Search Fences.

The control parameters include probability of detection; target object cross-section; target object elevation rate; and fence range, azimuth, and elevation extent.

The CD system shall (022D) update all new objects at a 2 Hertz (Hz) track rate for 15 seconds.

Surveillance Mode The CD System shall (648) allow the user to enter Surveillance Mode at the end of the startup sequence from Standby State.

The CD System shall (649) allow the user to control the horizon search for missile objects as part of Missile Defense operation by performing continuous search of the three-dimensional (3- D) spaces defined by a set of active Search Fences.

Operation in this Mode is similar to Normal Mode, but the preselected Search Fences will be described using furnished threat information.

The CD System shall (650) activate all preselected Missile Defense Search Fences and inactivate all active Search Fences upon entry to Surveillance Mode at system startup or from Normal Mode.

The CD System shall (651) retain the search Fences active in Missile Defense Modes and not replace them with any preselected Missile Defense Search Fences on transition from Missile Defense Mode to Surveillance Mode.

The CD System shall (652) allow the user to activate or inactivate all Search Fences of appropriate range (according to the active scheduling interval template as described in Section 3.2) at any time.

The CD System shall (653) allow the user to define and edit the control parameters of inactive Search Fences when in Surveillance Mode.

The CD System shall (654) carry out Space Domain Awareness (formerly Space Surveillance) operations and satellite calibrations.

Missile Defense Mode The Missile Defense Mode supports Missile Defense autonomous acquisition, object tracking, typing, and object classification. In this Mode, CD performs GFC/C cued search, tracking and object classification taskings within the limits of available radar resources.

The CD System shall (655) shall be able to enter Missile Defense Mode from Surveillance, Normal, or Intelligence Modes.

When starting in Surveillance Mode, the sequence of events for autonomous acquisition is similar to Normal Mode.

The CD System shall (656) make a periodic check to determine if the object is an aircraft, balloon, meteor, or clutter (ABMC) as shown in Figure B-1 in the SRD Classified Appendix B.

If any of these conditions is true, the object is dropped.

After CD070 time units, the CD System shall (657) categorize the object as a missile if it is earth impacting.

If it is a missile, the Threat Characteristic is determined.

The CD System shall (658) transition to Missile Defense Mode from any other Mode upon any missile event.

The CD System shall (659) enter Missile Defense Mode if CD is in the GMD Alert State and a Cued Search Acquisition Task is received.

The CD System shall (660) inactivate all active Search Fences and activate all preselected Missile Defense Search Fences upon entry to Missile Defense Mode from any legacy Mode (Normal or Intelligence).

The CD System shall (661) retain the active Search Fences and not replace them with preselected Missile Defense Search Fences upon transition from Surveillance Mode to Missile Defense Mode.

The CD System shall (662) allow the user to activate and inactivate all Search Fences at any time when in Missile Defense Mode.

By selecting what Search Fences to activate, the operator controls radar energy consumption.

The CD System shall (663) allow the user to define and edit the control parameters of inactive Search Fences.

The CD System shall (664) use the Intelligence Mode Long Term Planner (LTP) in Missile Defense Mode to schedule all GFC/C tasks and determine whether the tasks can be performed within the GFC/C-specified deadline.

The CD System shall (665) perform Missile Defense Mode profile-controlled Intelligence data collection operations on missile objects at a lower priority than tracking of threat objects.

In Missile Defense Mode the Profile selection logic is similar to that in Intelligence Mode.

The CD System shall (666) select Reference Object based on the Threat Missile objects, then Test Threat Missile objects then Non-Threat Missile objects.

In the Missile Defense Mode, the CD System shall (020) be capable of recording Intelligence data, based on mission profiles.

The inherent Missile Defense Mode data collection capability is identical to the Intelligence Mode capability, but radar activity priorities may allocate fewer radar resources to data collection in Missile Defense Mode.

3.2.4 Correlation Between Modes and System Functions

Unless otherwise stated, these System Functions apply to the modes as specified below:

Table 3.2-3 Function and Mode Relationships System Functions Operating Modes

General Operating Functions (3.2.1) Normal

Intelligence

Normal Mode Functions (3.2.1) Normal

Intelligence Mode Functions (3.3.3) Intelligence

Space Surveillance Functions (3.3.2) Normal

Surveillance

Missile Defense Functions (3.3.1) Surveillance

Missile Defense

System Support Functions (3.3.5) (Except for offline diagnostics)

Normal

Intelligence

Surveillance

Missile Defense

3.3 Functional Requirements

Reduced Duty Operation CD is capable of operating with reduced duty factor templates only in Normal and Intelligence Modes. The available reduced duty factor templates include quarter duty (1.5% duty) and half duty (3.0% duty). Like full duty, these duty factors use either the 33 milliseconds (msec) or 25 msec scheduling interval when in Normal Mode. Quarter duty is also available in the 100 msec scheduling interval when in Normal Mode or Intelligence Mode (called "Quarter Duty Special").

Quarter Duty Special allows the operator to modify and activate fences with ranges > CD007 for the purpose of Intelligence data collection at extended ranges. This extended range capability drives the range criteria of Threat objects when transitioning to Missile Defense Mode (see Figure 3.2-2). When operating with the reduced duty factor templates, transitions to other Modes (Surveillance and Missile Defense) cause the system to automatically employ the full duty factor template. At this point the operator may no longer modify or activate extended range fences.

Changing from quarter duty to full duty, including the response latency takes CD069 time units.

3.3.1 Functional Missile Defense Mission Requirements

Missile Defense Mission Missile Defense is a contingency mission whose functionality is enabled whenever a threatening impacting object has been detected, by GFC/C message, by operator command, or by autonomous detection.

The CD System shall (667) support Missile Defense autonomous acquisition by set of preselected and predefined horizon Search Fences.

These Missile Defense Search Fences may be activated or inactivated by the operator when Missile Defense Mission is active.

The CD System shall (667B) support mission profile-controlled Intelligence data collection on all missile objects exactly as performed in Intelligence Mode while in the Missile Defense Mode, but its priority for radar occupancy is lower than Missile Defense functions.

By deactivating search fences, radar occupancy is made available to Intelligence data collection.

The CD System shall (667C) communicate with GFC/C about all threat missile objects or test threat missile objects in all Modes except Intelligence and any impacting objects correlated with a cued search task.

The CD System shall (667D) perform GFC/C-directed cued search, track, and object classification tasks, and provide missile track and object classification data to GFC/C within the limits of available radar resources.

The CD System shall (667E) report to GFC/C all missile objects, regardless of threat characteristic, correlated with a cued search task.

The CD System shall (667F) report all acquired threat and test-threat missile objects to the GFC/C while not in Intelligence Mode.

The CD System shall (667G) report tracks periodically to GFC/C with reporting continuing for each missile object until it leaves the CD field of view.

For tracking and Intelligence data collection purposes, the CD System shall (667H) assign test-threat missile objects with a priority of a threat, when no threats are in track, and the priority of a non-threat when a threat is in track.

The CD System shall (667I) allow the use a real-world Target of Opportunity (TOO), e.g., a foreign missile test flight, for testing Missile Defense as well as Intelligence data gathering.

Disabling some Missile Defense search fences will increase the likelihood that radar energy will be available for Intelligence data collection.

The CD System shall (667J) allow a TOO object to be characterized as a Test Threat missile object and therefore be treated as a Threat missile object and be reported to GFC/C as in a Missile Defense operation.

The CD System shall (667K) perform the Space Domain Awareness Mission, including satellite-based radar calibration while in in the Missile Defense Mission, except during cued search and Intelligence data collection operations.

The CD System shall (667L) allow manual Missile Defense Mission entry and exit under command from the operator.

The CD System shall (667M) automatically enter Missile Defense Mission from any legacy mission, upon receipt of a valid System State Change message from GFC/C requesting a change to Alert State.

3.3.1.1 Timelines

The CD System’s basic system timelines are illustrated in Figure B-1 and Figure B-2 in the SRD Classified Appendix.

The CD System shall (668) perform Object Categorization for each object in track, within CD070 time units of track initiation.

Categorization identifies objects as satellites or missiles.

The CD System shall (668B) further divide missile objects into: Threat, Test Threat, Non- Threat.

The CD System shall (668C) begin Missile Defense object classification at start of the track.

Note that object typing is part of the Intelligence Mode process, which executes in parallel with the Missile Defense Object Classification process but is otherwise independent of it.

Figures B-3 through B-6 in the SRD Classified Appendix B expand the basic timelines to support Missile Defense operation, including GFC/C-commanded and autonomous behavior.

In all the figures the small boxes on the timelines represent the Computer Software Component (CSC) or task that performs the listed functions, e.g., the Typing and Planning. This is the existing Intelligence Mode software architecture. In Intelligence Mode, Intelligence (INT) CSC runs every 10 seconds. In CD Missile Defense Mode, this same CSC will be used but its execution interval may differ (noted as 'N' seconds in the figures). Figure B-3 in the Classified Appendix B illustrates that there may be a delay of up to N seconds before the process recognizes the existence of a new track. This behavior is expected and will satisfy the Missile Defense requirements for object classification.

3.3.1.2 Track Accuracy

The CD Track capabilities are as follows:

a. Within the sensor operations specified in Table 3.3-20 and for objects with the characteristics identified in Table 3.3-1, the CD System shall (023) provide the tracking performance identified in Table 3.3-2.

The Probability of Track Reporting is defined as the probability that the object of interest, or an object that would be within CD020 km (kilometers) of the reentry vehicle (RV) when predicted ahead to the Maximum Predict-ahead time given in Table 3.3-2, is in track at the assessment time and subsequently reported to GFC/C.

b. The CD System shall (023B) report its tracks as specified in the Interface Design Description (IDD) D742-14204-2, of the date of issue shown in Section 2.2.

Table 3.3-1 Object Characteristics

Object Type CD025 CD030

Minimum Mean Object Radar Cross Section (RCS)1

CD026 CD031

Maximum Object Range CD027 CD032

Maximum Azimuth Angle Relative to a Vector Normal To The Center Of Each Array Face

CD028 CD033

Minimum Elevation Angle Relative to the Radar Horizon CD029 CD034

Note 1. Applies to the CD013 missile systems described in the C1 Threat Database identified in Section 2.2.

Table 3.3-2 Tracking Performance

Object Type

Minimum Track Time (seconds)

Maximum Predict-ahead

Time (seconds) Probability of Track Reporting

CD035 Spherical Error Probable (SEP)

Absolute Position Uncertainty Including all Corrections

Raid Type Raid Type

Medium Medium

CD025 or CD030 CD039 CD045 CD048 CD051

CD030 CD040 CD046 CD049 CD052

CD030 CD041 CD047 CD050 CD053

3.3.1.3 Mean Time Between False Track Messages

The CD System shall (024B) use existing logic to prevent false track messaging.

This is defined as have no more than CD003A autonomous tracks per year due to "false events" and no more than CD003B autonomous tracks per year due to "non-missile events."

A "false event" is defined as one generated by a sensor system hardware or software malfunction or internal receiver noise. A "non-missile event" is defined as one generated by environmental conditions (aurora, radar ducting, aircraft, clutter, etc.) external to the sensor system.

The CD System shall (024) report no more than CD003C false tracks per every 100 tracks reported over a twelve-hour period, for report times greater than or equal to 60 seconds after track initiation, for any of the object densities and raid sizes described in Table 3.3-3.

For the purposes of this requirement, a false track is a false event or non-missile event.

3.3.1.4 Covariance Fidelity

At the initial assessment time (CD039 for medium raid type) and for the object of interest identified in Table 3.3-2, the ensemble average of the Sigma position reported to GFC/C by the CD System shall (025) be within CD064 of the true position error.

At the initial assessment time (CD039 for medium raid type) and for the object of interest identified in Table 3.3-2, the ensemble average of the Sigma velocity reported to GFC/C by the CD System shall (026) be within CD065 of the true velocity error.

3.3.1.5 Classification Performance

The CD System shall (027D) designate objects as threat or test threat in any Mode except Intelligence Mode, and be reported to GFC/C.

The CD System shall (027C) report any impacting objects correlated with a cued search task to

GFC/C.

The CD System shall (027E) perform Object Classification for all missile objects designated for reporting to GFC/C.

Within the sensor operations specified in Table 3.3-20 and for objects with the characteristics identified in Table 3.3-1, the CD shall (027) achieve the object classification performance indicated in Table 3.3-3, where the Probability of Correct Classification is defined as the probability that at least one object that is within CD020 of the RV when predicted to the Maximum Predict-ahead time, is declared as threatening.

The Probability of Incorrect Classification is defined as the probability that at least one object that is within CD020 of the RV when predicted to the Maximum Predict-ahead time, is declared as threatening.

Table 3.3-3 Object Classification Requirements

CD Raid Type Minimum Track Time (sec)

Probability of Correct Classification (%)

Probability of Incorrect Classification (%)

Medium CD040 CD061 CD063

3.3.1.6 Missile Defense Time Scales

The CD System shall (027A) be synchronized to Universal Time Coordinated (UTC) via the Global Positioning System (GPS).

Time is the independent variable in the equations of motion and as such time tags are construed to be error free. Errors in CD time tags associated with track messages are manifest as errors in position.

The CD System time tag shall (027B) be of sufficient accuracy that track accuracy requirements are met when the effects of timing errors are included.

3.3.1.7 Missile Defense Coordinate System

The CD System shall (027F) send and receive all state vectors in DoD World Geodetic System (WGS)-84 coordinates, using the units and conventions specified in the Interface Design Description Ground-Based Midcourse Defense Fire Control/Communications and COBRA DANE Upgrade, (D742-14204-2), Rev D, 8 April 2008.

In evaluation of CD performance requirements in this Capabilities document, DoD WGS-84 coordinate system, specified in National Geospatial-Intelligence Agency (NGA) Standardization Document, NGA.STND.0036_1.0.0_WGS84, Department of Defense World Geodetic System 1984, Version 1.0.0, 2014-07-08 is used where applicable, unless otherwise stated.

3.3.1.8 Missile Defense Defended Area

In System Specification-CDSM0001, the Continental United States (CONUS) is defined by the area on the surface of the earth inside an ordered set of five two-dimensional (latitude-longitude) geodetic coordinates, joined by great circles, defined as System Adjustable Parameters (SAPs).

In the CD System, the Missile Defense Defended Areas shall (028B) be comprised of at least one Threat Defended and zero or greater Test Threat Defended Areas.

The CD System shall (028C) use the Active Threat Defended Area(s) instead of the CONUS for all Modes of system operation.

The CD system shall (028D) use the Active Test Threat Defended Areas in Missile Defense Mission only.

The CD System shall (028) be capable of defining Defended Areas by one to ninety-nine ordered sets of two-dimensional coordinates in latitude and longitude (West longitude and North latitude are positive.)

The CD System shall (029) provide the operator with the capability to activate or de-activate Defended Areas while in Normal or Surveillance Modes, or in Standby State, with the total number of active Defended Areas never exceed CD071.

Each Defended Area will have an associated identifier to distinguish Threat Defended versus Test Threat Defended Areas.

The CD System shall (029B) define each Defended Area as a polygon.

A predicted impact point is said…