MS_T2D_SRD_Version_4.2_Aug2015.pdf

MISSILE DEFENSE AGENCY

SYSTEMS ENGINEERING DIRECTORATE (MDA/DE/E)

BALLISTIC MISSILE DEFENSE SYSTEM (BMDS)

Modeling and Simulation (M&S) System Requirements Document (SRD)

Tier 2 Digital (T2D)

24 August 2015

Prepared by:

MDA System Verification (MDA/EEV)

Von Braun IV Redstone Arsenal, Huntsville, AL 35898

WARNING – This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or Executive Order 12470. Violators of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

The views, opinions, and findings contained in this report are those of the author(s) and should not be construed as an official Department of Defense position, policy, or decision, unless so designated by other official documentation.

Distribution authorized to U.S. Government agencies and their contractors due to this publication containing technical or operational information for official Government use only, effective 1 Oct 2010. Other requests for this document shall be referred to the Office of the Secretary of Defense, Missile Defense Agency, ATTN: Contracting Officer, 7100 Defense Pentagon, MDA/DAC, Washington, DC 20301-7100 or higher DoD authority.

DESTRUCTION NOTICE – For classified documents, follow the procedures in DoD 5220.22-M, Industrial Security Manual Section 11-19 or DoD 5200.1-R, Information Security Program Regulation, Chapter IX. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

This document contains information EXEMPT FROM MANDATORY DISCLOSURE under the Freedom of Information Act (5 U.S.C. Section 552).

Exemption 3 applies: "Authority to Withhold From Public Disclosure Certain Technical Data, 10 U.S.C. 130 and DoD Directive 5230.25 (references

(k) and (l))."

UNCLASSIFIED//FOR OFFICIAL USE ONLY

UNCLASSIFIED//FOR OFFICIAL USE ONLY

THIS PAGE LEFT BLANK INTENTIONALLY

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

Initial Release Version 4

Modeling and Simulation (M&S) System Requirements Document (SRI)) Tier 2 Digital (T2D)

UNCLASSIFIED//FOU0

August 2015

M&S System Requirements Document Tier 2 Digital

August 2015

Submitted by:

KATHY ELVIDGE

MDA/DE Director, System Verification

Approved by:

KEITH L. ENGL DER

Director for Engin ering

M&S SRD T2D

Page 3 a 285 UNCLASSIFIED//FOUO

REVISION/CHANGE RECORD

Change Record - Page 1 of 1

Date AuthorizationDescription

Pages

AffectedSRD Version

10/9/2014 MDA/EEVVersion 0, Initial release for review for submittal to EEV

Leadership

AllM&S SRD T2D Version 0 (initial release)

11/13/2014 MDA/EEVVersion 1, Initial release for E-Tasker for community review AllMDA/EEV

2/11/2015 MDA/EEVChanged SRD T2D in accordance with (IAW) with all EEV adjudication of Accepted and Modified Administrative

Comments found in SRD T2D Comments (20150210).xlsx

Multiple

Pages/Sections of SRD and

Appendicies

MDA/EEV

2/12/2015 MDA/EEVChanged SRD T2D IAW with all EEV adjudication of

Accepted Substantive Comments found in SRD T2D Comments

(20150210).xlsx

Multiple

Pages/Sections of SRD and

Appendicies

MDA/EEV

2/13/2015 MDA/EEVRemoved "It is desired that the …." from requirements and made them "shall" statements.

Multiple

Pages/Sections of SRD and

Appendicies

MDA/EEV

2/13/2015 MDA/EEVChanged SRD T2D IAW with all EEV adjudication of

Accepted Substantive Comments found in SRD T2D Comments

(20150210).xlsx (continued from 12 Feb)

Multiple

Pages/Sections of SRD and

Appendicies

MDA/EEV

2/13/2015 MDA/EEVRemoved "support the computation of …." from requirements. See

"reword support computation of verbiage.doc" in the EEV Drop folder for specific requirements affected.

Multiple

Pages/Sections of SRD and

Appendicies

MDA/EEV

3/4/2015 MDA/EEVChanged SRD T2D IAW with all subsequent comments received following the release of EEV adjudicated comments on

20 Feb 2015.

Multiple

Pages/Sections of SRD and

Appendicies

MDA/EEV

4/1/2015 MDA/EEVModified document to align requirements, SCM, and Table E changes.

MultipleMDA/EEV

4/6/2015 MDA/EEVVersion 2 of Initial Release for MSEWG vote. DocumentMDA/EEV

5/29/2015 MDA/EEVVersion 3 of Initial Release for signature. DocumentMDA/EEV

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

7/09/2015 MDA/EEVVersion 3 dated 9 Jul 2015 updated with administrative changes, including changing D4 reference to Increment 5

DocumentMDA/EEV

8/21/2015

MDA/EEV

Version 4 updated with administrative changes, removal of PAA Phase 3, Increment 5 references based on Pre-ISG direction

DocumentMDA/EEV

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

Initial Release Version 4

8/24/2015 MDA/EEVVersion 4.1 updated with table of contents to reflect correct page numbering

DocumentMDA/EEV

09/02/2015 MDA/EEVVersion 4.2 updated with signature page DocumentMDA/EEV

TABLE OF CONTENTS

1.0 SCOPE 12

1.1 Introduction 12

1.2 System Definition 13

1.2.1 M&S Enterprise 13

1.2.2 BMDS Simulation Conceptual Model 14

1.2.3 M&S System 15

1.3 BMDS M&S System Description 15

1.3.1 BMD System Functions 15

1.3.1.1 Pre-Mission Planning

1.3.1.2 Sensor Acquisition

1.3.1.3 Sensor Tracking

1.3.1.4 Sensor Discrimination and Classification

1.3.1.5 Battle Manager Tracking and Discrimination

1.3.1.6 Battle Manager Engagement Planning

1.3.1.7 Interceptor Launch and Flyout

1.3.1.8 Interceptor Guidance, Navigation and Control

1.3.1.9 Interceptor Acquisition, Tracking and Discrimination

1.3.1.10 Lethal Intercept

1.3.1.11 Communications / Interoperability

1.3.1.12 System to Maintain Situational Awareness

1.3.1.13 Other Assessment Objectives 22

1.3.2 Truth 22

1.3.3 Communications 26

1.3.4 Threat 26

1.3.5 Simulation Support Infrastructure 27

1.4 Approach for SRD Updates 27

1.5 M&S Overlay to the BMDS Technical Requirements 28

2.0 APPLICABLE DOCUMENTS 29

3.0 REQUIREMENTS 30

3.1 Architecture Description 30

3.1.1 Red Force 30

3.1.2 Blue Force 30

3.2 M&S System Level Requirements 30

3.2.1 M&S System Functions 31

3.2.1.1 Pre-Mission Planning 31

3.2.1.2 Sensor Acquisition 31

Tables of Contents / Figures / Appendices – Page 1 of 7

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

3.2.1.3 Sensor Tracking 31

3.2.1.4 Sensor Discrimination and Classification 31

3.2.1.5 Battle Manager Tracking and Discrimination 31

3.2.1.6 Battle Manager Engagement Planning 31

3.2.1.7 Interceptor Launch and Flyout 31

3.2.1.8 Interceptor Guidance, Navigation and Control 31

3.2.1.9 Interceptor Acquisition, Tracking and Discrimination 31

3.2.1.10 Lethal Intercept 31

3.2.2 Truth 31

3.2.2.1 Signatures 31

3.2.2.2 Environment 32

3.2.2.3 Truth Interactions 32

3.2.2.4 Lethality 32

3.2.3 Communications 32

3.2.3.1 Network Architecture 32

3.2.3.2 Nodes 32

3.2.3.3 Links 32

3.2.3.4 Information Exchange 32

3.2.3.5 Truth Interaction 32

3.2.3.6 Communications Services 33

3.2.4 Threat 33

3.2.4.1 Ballistic Missile 33

3.2.4.2 Aircraft - N/A 33

3.2.4.3 Cruise Missiles 33

3.2.5 Simulation Support Infrastructure 33

3.2.5.1 Pre-Mission Planning

3.2.5.2 M&S Deployment and Installation

3.2.5.3 Mission Execution

3.2.5.4 M&S Post-mission

3.2.5.5 M&S Interoperability

3.2.5.6 M&S Management 34

3.3 Design and Considerations 35

3.4 Documentation 35

3.5 Logistics 35

3.6 Personnel and Training 35

3.6.1 Personnel 35

3.6.2 Training 35

3.7 Constituent Characteristics 36

3.7.1 Element / Component 36

Tables of Contents / Figures / Appendices – Page 2 of 7

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

3.7.1.1 Aegis BMD

3.7.1.2 C2BMC

3.7.1.3 External Weapon Systems – Excluded for T2D Venue

3.7.1.4 Ground-based Midcourse Defense (GMD)

3.7.1.5 Overhead Sensors

3.7.1.5.1 Space-Based Infrared System (SBIRS)/Overhead Future Sensors (OFS)

3.7.1.6 Overhead Sensor Ground Stations

3.7.1.6.1 BMDS Overhead Persistent Infrared Architecture (BOA)

3.7.1.6.2 Mission Control Station (MCS)

3.7.1.7 Patriot

3.7.1.8 Standalone Radars

3.7.1.8.1 AN/TPY-2 (FBM)

3.7.1.8.2 COBRA DANE

3.7.1.8.3 SBX

3.7.1.8.4 UEWR

3.7.1.9 THAAD 57

3.7.2 Truth 60

3.7.2.1 Signatures 60

3.7.2.2 Environments 65

3.7.2.3 Truth Interactions 70

3.7.2.4 Lethality 78

3.7.3 Communication 82

3.7.3.1 Network Architecture 82

3.7.3.2 Nodes 82

3.7.3.3 Links 86

3.7.3.4 Information Exchange 88

3.7.3.5 Communications Truth Interaction - Excluded for T2D Test Venue 90

3.7.3.6 Communications Services 90

3.7.4 Threat 92

3.7.4.1 Ballistic Missile 92

3.7.4.2 Aircraft - N/A 96

3.7.4.3 Cruise Missiles 96

3.7.5 Simulation Support Infrastructure 98

3.7.5.1 M&S Pre-Mission Planning 98

3.7.5.2 M&S Deployment and Installation 101

3.7.5.3 M&S Mission Execution 102

3.7.5.4 M&S Post-mission 107

3.7.5.5 M&S Interoperability 108

3.7.5.6 M&S Management 108

Tables of Contents / Figures / Appendices – Page 3 of 7

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

3.8 Precedence 111

4.0 M&S SYSTEM-LEVEL VERIFICATION 112

4.1 Verification Methods 112

4.1.1 Test 112

4.1.2 Analysis 114

4.1.3 Demonstration 115

4.1.4 Examination 115

4.2 Integrated BMDS M&S Requirements 116

4.3 System Verification Process 117

Tables of Contents / Figures / Appendices – Page 4 of 7

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

TABLE OF FIGURES

Figure 1 - BMD System - Increment 5 Architecture

Figure 2 - M&S Enterprise

Figure 3 - BMD System Functions

Figure 4 - CTM Taxonomy Tailored for T2D

Figure 5 - Communications Representation Requirements Development Approach

Figure 6 - Threat Requirement Development Approach

Figure 7 - M&S Infrastructure Conceptualization

Figure 8 - M&S System Engineering Development Process

Figure 9 - M&S Rain in a Test Scenario

Figure 10 - Example Rain Attenuation Verification by Test

Figure 11 - Example RCS Verification by Analysis Results

Figure 12 - Aegis BMD Provide Sensor Track Report Demonstration Test Case

Figure 13 - Integrated BMD System M&S Requirements Flow

Figure 14 - BMD System M&S Requirements Verification Process 117

Tables of Contents / Figures / Appendices – Page 5 of 7

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

TABLE OF APPENDICES

Appendix A 121

Table A.1: Measures for Pre-Mission Planning

Table A.2: Measures for Sensor Acquisition

Table A.3: Measures for Sensor Tracking

Table A.4: Measures for Sensor Discrimination and Classification

Table A.5: Measures for Battle Manager Tracking and Discrimination

Table A.6: Measures for Battle Manager Engagement Planning

Table A.7: Measures for Interceptor Launch and Flyout

Table A.8: Measures for Interceptor Guidance, Navigation and Control

Table A.9: Measures for Interceptor Acquisition, Tracking and Discrimination

Table A.10: Measures for Lethal Intercept

Table A.11: Measures for Communications/Interoperability

Table A.12: Measures for System to Maintain Situational Awareness 134

Appendix B 135

135 Table B.1: Environment Initialization Parameters

Appendix C 136

137 Table C.1: Tactical Messages

Appendix D 139

Table D.1: Section 3.2 System Requirements Allocation

Table D.2: Section 3.7 Constituent Function Allocation

Table D.3: Section 3.7.2 Truth Allocation

Table D.4: Section 3.7.3 Communications Allocation

Table D.5: Section 3.7.4 Threat Allocation

Table D.6: Section 3.7.5 Simulation Support Allocation 211

Appendix E 225

226 Table E.1: AN/SPY-1 Truth Touch Points

Table E.2: Aegis BMD SM-3/KV/KW Truth Touch Points 230

Tables of Contents / Figures / Appendices – Page 6 of 7

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

Table E.3: GMD GBI/KV/KW Truth Touch Points

Table E.4: SBIRS/OFS Truth Touch Points

Table E.5: PATRIOT Truth Touch Points

Table E.6: PATRIOT PAC-3/Pre-PAC-3/KV/KW Truth Touch Points

Table E.7: AN/TPY-2 (FBM) Truth Touch Points

Table E.8: COBRA DANE Truth Touch Points

Table E.9: SBX Truth Touch Points

Table E.10: UEWR Truth Touch Points

Table E.11: AN/TPY-2 (TM) Truth Touch Points

Table E.12: THAAD Interceptor/KV/KW Truth Touch Points 264

Appendix F 268

268 Table F.1: Attribute Summary Table

Appendix G 273

273 Table G.1: Variable Parameters

Appendix H 278

278 Table H.1: Acronyms

Appendix I (Classified) 1

Table I.1: Classified M&S Representation Required for Tier 2 Digital

Table I.2: Threat Systems (Unclassified)

Table I.3: Classified SRD References

Table I.4 : Classified Variable Parameters 4

Tables of Contents / Figures / Appendices – Page 7 of 7

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

1.0 SCOPE

1.1 Introduction

The Modeling and Simulation (M&S) Tier 2 Digital (T2D) System Requirements Document (SRD), hereafter referred to as the SRD T2D, provides a top-level set of system-level M&S requirements for the Missile Defense Agency (MDA) T2D venue. The SRD T2D focuses on development of system-level requirements for an end-to-end M&S architecture, based on the technical content for Increment 5.

M&S requirements within this SRD will not change tactical element/component specifications or requirements. The objective of this SRD is to translate high-level stakeholder needs, measures and existing M&S limitations into a set of M&S system-level requirements for the T2D intended use, in alignment with the BMDS Simulation Conceptual Model (SCM), as discussed in paragraph 1.2.2.

The T2D venue will be a timely, relevant, dependable, stable and reusable digital BMDS representation developed through a disciplined systems engineering process. The T2D venue enables assessment of the performance, capabilities and limitations of the BMDS as well BMDS capability deliveries (including individual Element contributions).

The stakeholder assessment needs allocated to this intended use drive required BMDS architecture and system-level requirements captured in this document. The detailed design to implement these requirements must continue to incorporate stakeholder needs to ensure the development of M&S that can achieve accreditation. The BMDS Operational Test Agency (OTA) Accreditation Plan describes the criteria necessary to achieve BMDS OTA Accreditation. The two primary BMDS Assessment intended uses in the T2D venue are to conduct BMDS Performance Assessment and may support BMDS requirements verification. The T2D venue supports characterization of the BMDS in a number of ways. First, it enables the identification of BMDS performance trends that transcend Ground Test (GT) objectives. Second, it provides a statistically relevant replica set sufficient to make broad statements of capability and to characterize BMDS limitations and other implications pertinent to warfighters across the operational mission space. Third, it enables system sensitivities to be characterized through the test of conditions that degrade behavior even if no immediate failure occurred. Fourth, it enables characterization of the BMDS's conformance to its technical performance specifications through BMD System Specification (SS) verification.

The M&S SRD defines the objective set of system-level M&S requirements, as well as the regression capabilities required within the M&S system to support assessment of the Increment 5 functionality.

The stakeholder assessment needs and derived requirements contained in the M&S SRD T2D were developed without considering the limitations of constrained resources. M&S Enterprise Management activities will prioritize development and implementation of these requirements based on funding and schedule constraints.

The T2D SCM Objectives Phase, described later in this document (paragraph 1.3.5), defined a set of threshold attributes required to meet the assessment objectives of the T2D venue. In defining these attributes, analysis of SCM objectives determined that specific T2D functionality is required. Table F.1:

Attribute Summary Table, lists the complete set of attributes, organized by T2D Attribute category.

Section 1 - Page 1 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

August 2015

M&S SRD T2D

1.2 System Definition

The BMDS is a joint, integrated, multi-layered and globally deployed system-of-systems delivered to defend the United States, deployed forces, allies and friends against ballistic missiles of all ranges by engaging them in all phases of flight: boost, ascent, midcourse and terminal (Figure 1 – BMD System –

Increment 5 Architecture, below). Modeling the BMDS at the enterprise level requires an infrastructure to act as the backbone (i.e., simulation support infrastructure) for the individual component models to include the elements, threats, environments and communications. The SRD T2D is specifically tailored to document the requirements needed to assess Increment 5 functionality in T2D venue. The SRD T2D addresses interface requirements to support the inclusion of External Weapon Systems and

Interoperability Support in the T2D venue, but does not allocate requirements to those elements.

1.2.1 M&S Enterprise

Figure 1– BMD System – Increment 5 Architecture

The M&S enterprise is managed as a single, synchronized program supporting multiple venues to include all-digital (e.g., T2D), hardware-in-the-loop (HWIL), and warfighter training/exercises.

The M&S enterprise is comprised of all resources, assets and processes necessary to simulate the BMDS to include element/component models and drivers, as well as the necessary infrastructure, hardware and facilities. Additionally, the M&S enterprise enables BMD system planning, enables

Section 1 - Page 2 of 17

The traceability of these threshold attributes is captured in requirements and reflected in the traceability documented in Appendix D allocation matrices. In addition, objective attributes for a non-real-time all-digital architecture are documented in the SRD and mapped to requirements in Table F.1: Attribute Summary Table.

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

assessment criteria translation into test plans and scenario development, and supports the analysis of data collected from a defined venue. The M&S SRDs for GT and T2D primarily address the BMDS behavior (element M&S products) and the supporting simulation components (M&S simulation support infrastructure, threat, truth and communications) necessary to simulate the BMDS. The M&S SRDs do not explicitly address the enterprise products and/or processes that are outside the M&S System proper;

however, all are depicted in Figure 2. The “Plan Event” step notionally includes activities such as the

Planning Exercise (PLANEX) or products like the Test Case Description Document (TCDD) shown in Figure 2 – M&S Enterprise below. This is part of the M&S enterprise but not addressed in the M&S

SRDs. Similarly, the “Analyze Data” step is also outside the scope of the M&S SRDs, and Enterprise products / processes / organizations like the Missile Defense Data Center (MDDC) and Joint Analysis

Team (JAT) do not have allocated requirements. While there are no allocated requirements identified, there are implied requirements for MDDC and JAT to prepare for the increase in data quantities that the

T2D will produce. Increased data handling, data / product storage and analysis capabilities will be required by the increasingly more robust BMDS M&S Enterprise.

Figure 2 – M&S Enterprise

1.2.2 BMDS Simulation Conceptual Model

MDA’s System Verification Directorate (MDA/EEV) is executing an enterprise-level M&S System

Engineering (SE) process to develop and manage the M&S System requirements that govern the translation of the physical BMDS into a virtual M&S representation per intended use. The goal of this process is to establish defendable and traceable system-level M&S requirements that serve as the basis for the initial product delivery and incremental updates for the elements, M&S simulation support infrastructure, threat, communication and core truth. The SCM serves as the cornerstone of the MDA/EEV SE process. The SCM process is a collaborative effort among MDA/EEV, MDA/DES, the element Project Offices (PO), the assessment community, end-user clients, simulation developers and subject matter experts.

Section 1 - Page 3 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

FOR OFFICIAL USE ONLY

FOR OFFICIAL USE ONLY

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

The SCM process provides an approach for specifying the essential BMDS system behavior and supporting simulation infrastructure necessary to meet the needs for an M&S intended use as applied to the T2D venue. This process yields a conceptual description of the virtual BMDS, and the resulting artifacts form the basis of the SRD T2D development.

1.2.3 M&S System

The M&S System, as characterized in the BMDS conceptual model, represents the behavior of the physical BMDS via modeling and simulation. The M&S System supporting T2D is an integrated architecture comprised of simulations of BMDS Elements, threat, truth stimuli and communications as well as simulation support infrastructure.

1.3 BMDS M&S System Description

1.3.1 BMDS System Functions

The BMDS System Functions are a construct for analyzing the operation of the BMDS system versus ballistic threats from Pre-Mission Planning through Lethal Intercept. These functions were originally developed by the BMDS Capability Assessment (BCA) team to support assessment of the BMDS. The

System Functions have been adopted by the SCM team, the Integrated Master Assessment Plan (IMAP) team, and the BMDS Operational Test Agency (OTA) to ensure a common starting point for both

BMDS Assessment and M&S requirements development. Figure 3 – BMDS System Functions illustrates the BMDS System Functions from Pre-Mission planning through Lethal Intercept. For completeness of the system functions, operational assessment objectives also address both

Communications / Interoperability and System to Maintain Situational Awareness. These two

“additional functions,” defined later in sections 1.3.1.11 and 1.3.1.12, include a description of where they are addressed in this SRD.

Figure 3 - BMDS System Functions

Section 1 - Page 4 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

1.3.1.01 Pre-Mission Planning

Pre-Mission Planning refers to the ability of the BMDS warfighter to configure Blue Force (BF) assets and develop deployment strategies prior to a battle. The resultant Blue Force Laydown is the basis for test case development and scenario execution. The Pre-Mission Planning effort is primarily conducted as part of the test campaign PLANEX where the warfighter (typically) will run their planners. The sub-functions are described below:

- Develop an Effective Defense Design: To develop the defense design, warfighters / planners consider Ballistic Missile Operating Areas (BMOA), Prioritized Defended Asset Lists (PDAL), Defended Areas (DA), Weapons Release Authority (WRA), Rules of Engagement (ROE), Keep Out Zones (KOZ), Intercept Control Volumes (ICV), shot doctrine, pre-planned responses, interceptor inventories and intelligence regarding Red Force Concepts of Operation (CONOPS), capabilities and intentions.

-- Develop a Communication Architecture: To develop the communication architecture, warfighters/planners consider network designs, including their relative reliabilities and latencies. The resultant Operations Task Link (OPTASKLINK) documents the data link plans for the given mission.

-- Threat Acquisition Strategies: To develop coordinated threat acquisition strategies (e.g., settings and Tactics, Techniques and Procedures (TTPs) for search fences cues), warfighters / planners consider intelligence regarding Red Force launch capabilities, as well as Blue Force deployment details such as sensor Mission Profiles, available search plans in each Mission Profile and the number and location of potential cueing sources.

-- Discrimination Strategies: To develop threat discrimination strategies (e.g., whether to use auto-or tasked-discrimination), the warfighters/planners consider intelligence regarding Red Force CONOPS, threat types, numbers and locations, as well as likely Blue Force shooter engagement timelines.

- Element-level Defense Plans: Elements use the defense design, communication architecture, threat acquisition strategies and discrimination strategies to develop element level defense plans. These plans include all the element specific settings (e.g., mission profiles) needed to support the specified mission.

-- Element-level Threat Acquisition Strategies: Element-level warfighters / planners consider intelligence regarding Red Force launch capabilities, as well as Blue Force deployment details such as sensor Mission Profiles, available search plans in each Mission Profile and the number and location of potential cueing sources when developing coordinated threat acquisition strategies (e.g., settings and TTPs for search fences and cues).

-- Element-level Discrimination Strategies: Element-level warfighters / planners consider intelligence regarding Red Force CONOPS, threat types, numbers and locations, as well as likely Blue Force shooter engagement timelines when developing threat discrimination strategies (e.g., whether to use auto- or tasked-discrimination).

Section 1 - Page 5 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

- Acquire Targets (autonomous): Autonomous acquisition can be accomplished using active sensors (e.g., radar) or passive sensors (e.g., infrared imaging). BMDS radars that perform autonomous acquisition include Army Navy Surface Ship Surveillance Radar-1 (AN/SPY-1), Army Navy Transportable Surveillance Radar - 2 (AN/TPY-2 (Terminal Mode (TM) and Forward-Based Mode (FBM))), Army Navy Multifunction Phased Array Radar-53/65 (AN/MPQ 53/65), Upgraded Early Warning Radar (UEWR) and COBRA DANE (CD). Overhead Persistent Infrared (OPIR) systems include overhead assets (Space-Based Infrared System (SBIRS) and other classified OPIR systems) and ground processing assets (Mission Control System (MCS)).

- Construct Search Regions: Search regions for ground radars are constructed based on (1) fixed search fences defined pre-mission (e.g., default search plan), (2) tasked search fences (e.g., Focused Search Plans (FSP)), (3) externally-tasked or self-tasked precision cues (PC) and/or (4) self-tasked local Reentry Vehicle (RV) search. For OPIR sensors, search regions are based on two basic modes of operation: (1) scanning or (2) staring.

- Schedule Resources/Service Volume: Resources required for acquisition must be scheduled and managed with competing tasks (e.g., Tracking vs. Discrimination).

- Task Sensors to Acquire Targets: Sensor tasking for acquisition refers to the ability of BMDS battle managers to issue acquisition tasking using PCs, boost phase cues (BPCs), FSPs or cued search on remote tracks. For example: Command and Control Battle Management and Communications (C2BMC) issues PCs, BPCs or FSPs to increase the probability of AN/TPY-2 acquisition relative to its default search fence. PCs are used when an eligible source reports a track on a complex not currently reported by

AN/TPY-2.

-- The PC, sent by C2BMC (based on the track from the eligible source), is centered on the propagated track state, and its volume is commensurate with the reported track covariance and inflated to account for propagation uncertainty. The PC volume changes over time to match the propagated cueing track state and covariance. BPCs use similar logic, but they account for the increased uncertainty associated with propagating tracks on boosting threats. Although the warfighter has the option of basing PCs on OPIR data, they typically use FSPs to cue AN/TPY-2 with OPIR data in theaters where threats are expected to fly through the default search fence quickly, or where PC-eligible sources are deployed behind the radar. Unlike PCs (which are relatively small and move over time), FSPs are large fixed volumes chosen specifically for a threat reported by OPIR. Ground-based Midcourse Defense (GMD) Fire Control (GFC) is responsible for cueing some sensors for acquisition. This is particularly critical for the Sea-Based X-Band (SBX) radar, which has a small beam and a very low probability of acquisition without a cue. Weapons systems on Link-16 (e.g., Aegis BMD, Terminal High-Altitude Air Defense (THAAD), Patriot (includes Patriot Advanced Capability - 3 (PAC-3) and Pre-PAC-3) independently perform cued search on remote tracks (e.g., from other Aegis BMD, THAAD, or Patriot units or from C2BMC via the Air Defense System Integrator (ADSI)). Unlike PCs and FSPs, where a central node (C2BMC) has inputs from multiple sources and determines that there is a system benefit from explicitly cueing a particular sensor, this form of cued search is totally decentralized. Each type of weapon system has its own algorithm for cueing on remote tracks, and these do not include logic to gauge the system level benefit of doing so.

- Acquire Targets (cued): Cued acquisition refers to the ability of BMDS sensors to detect objects and distinguish true objects from false ones based on a tasking.

Section 1 - Page 6 of 17

1.3.1.02 Sensor Acquisition

Acquisition refers to the process by which the BMDS detects objects and distinguishes true objects from false ones. The sub-functions are described below:

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

- Report Initial Track: Initial track reporting takes place when an object is acquired. OPIR provides Boost Phase Reports (BPR) (containing launch point estimate, time, missile type) and Boost State Estimate Reports (BSER) (containing estimated burn-out position and velocity vector with full covariance). Radars reporting directly to C2BMC or GFC typically report track states and covariances at pre-defined regular intervals. Radars reporting via Link-16 only report on a subset of their tracks when they are able to achieve reporting responsibility (R2). The subset reports do not always include covariances.

1.3.1.03 Sensor Tracking

Tracking refers to the process by which the BMDS maintains tracks and develops, aggregates and reports trajectory information. The sub-functions are described below:

- Determine Track Tasking: Sensor tasking for Tracking refers to the ability of BMDS battle managers to direct constrained sensor resources so that fire-control-quality tracks on high-priority threats are available in time to support the shooters. For example, C2BMC issues track management commands to AN/TPY-2.

These commands set the priority (low, medium or high) that AN/TPY-2 assigns to each track in its resource scheduler. Lethal threats influencing the PDAL are tasked to high priority, and tracks that are benign or fail to impact the PDAL are tasked to low priority. The intent is to get the best possible accuracy on high priority tracks and forward them to Link-16 for theater/regional shooters or to GFC for strategic defense. GFC exerts greater control in its tracking tasks to SBX. Rather than simply setting track priority, it specifies the track accuracy required at a particular time to support its Ground-based Interceptors (GBI).

- Initiate Tracks: Track initiation is the process by which unassociated measurements are combined to create new tracks. Logic is often included at this step to mitigate the effects of false alarms (e.g., through requiring tracks to receive m measurement updates in n attempts before they reach ‘firm’ status).

- Manage Tracks: Some BMDS sensors use track management to clean up their track pictures by merging tracks that appear to be redundant, deleting (dropping) tracks due to loss or exiting Field of Regard (FOR).

Tracks are maintained through persistent scheduling, transmit, receive, detection processing, detection correlation and track/detection fusion (filtering). The scope of this step varies across sensors in the BMDS.

- Provide Track Updates: Provide track updates refers to the ability of BMDS sensors to provide track information to the battle managers for subsequent reporting.

- Report Track Update: Track reporting takes place throughout the life of a track but varies substantially from sensor to sensor. OPIR provides BPRs (containing launch point estimate, time, missile type) and BSERs (containing estimated burn out position and velocity vector with full covariance). Radars reporting directly to C2BMC or GFC typically report track states and covariances at pre-defined regular intervals.

Radars reporting via Link- 16 only report on a subset of their tracks when they are able to achieve R2 and their reports do not always include covariances.

Section 1 - Page 7 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

1.3.1.04 Sensor Discrimination and Classification

Discrimination and classification refers to the process by which the BMDS determines which object(s) among a group of objects (debris, countermeasures, etc.) is lethal. The C2BMC and/or sensor typically characterize the objects (lethal and non-lethal) in the threat complex using algorithms. Details of the discrimination techniques are classified. The sub-functions are described below:

- Perform Discrimination Tasking: Discrimination tasking involves commanding a sensor to extract target features used to determine if the object is a threat by a certain time. A second form of sensor tasking for discrimination is in the hit/kill assessment. This involves commanding a sensor to search an area before and after intercept to determine whether an intercept occurred and whether the intercept neutralized the lethal object. Hit assessment is typically easier and can be based on a comparison of the pre- and post- intercept scenes. Kill assessment is more difficult, since it requires accurate tracking of the lethal object (and possibly its remains) before, during and after the intercept.

- Provide Discrimination Results: The results of discrimination are reported by the sensor based on the tasking. During discrimination assessment, the collected information is compared to thresholds that distinguish objects assumed to be lethal from those that are assumed to be non-lethal.

- Report Track Update: During track update reporting for discrimination, information regarding the classification, missile type or lethality of the object is reported.

1.3.1.05 Battle Manager Tracking and Discrimination

Battle Manager Tracking and Discrimination refers to the tracking and discrimination synthesis process by which BMDS battle managers collect, process and manage sensor tracking and discrimination data and develop and display composite trajectory and track identification information. The sub-functions are described below:

- Collect and Condition Data from Sensors: Both C2BMC and GFC begin by collecting incoming source tracks and conditioning them to account for neglected residual biases. Wild point editing also occurs at this point to prune out any source track reports that appear to be corrupted.

- Correlate and Fuse Data from Sensors: Both C2BMC and GFC correlate source tracks together and fuse the results to create system tracks. Their algorithms differ substantially, but the goal is to produce a single system track per object in track. When fusion of multiple source tracks occurs, a discrimination answer from one of the contributing source tracks is selected to represent the system track. System track launch point estimates (LPE) and impact point predictions (IPP) are also estimated at this time.

- Aggregate System-level Tracks received from Sensors: C2BMC associates its system tracks into launch families and selects a representative track for each; these families inform subsequent sensor resource management, track forwarding and situational awareness displays. GFC combines its system tracks into targeting clusters, which inform GBI engagements.

- Evaluate Lethality for System-Level Tracks: Aggregated tracks are evaluated for lethality.

- Track Forwarding and Down Select: Tracks are down-selected based on their lethality evaluation and forwarded between BMDS battle managers for use in engagement planning.

Section 1 - Page 8 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

- Report Track Update: During battle management tracking and discrimination, information on the system-level tracks is reported.

1.3.1.06 Battle Manager Engagement Planning

Engagement planning refers to the process by which BMDS battle managers plan and otherwise manage engagements using BMDS interceptors. The sub-functions are described below:

- Compute Battle Space: BMDS battle managers compute battle space for each potential engagement.

- Perform Debris Mitigation: BMDS battle managers task sensor to perform debris mitigation, and the sensor performs mitigation.

- Perform Automated Engagement Coordination (AEC): AEC messages are exchanged between BMDS battle managers to coordinate potential engagements.

- Select Targets: BMDS battle managers select targets from the objects being tracked.

- Allocate Weapons: Interceptors are allocated by weapon system and launch site depending on a variety of factors including battle space, weapon inventory, Rules of Engagement and AEC.

- Compute Firing Solutions: Firing solutions are computed and information is provided to interceptor launch equipment.

- Provide In-Flight Updates: Information is typically communicated between the battle managers and interceptors while the latter is in flight.

- Provide Interceptor Status: Battle Managers typically receive inflight status updates, and engagement plans are updated as necessary.

1.3.1.07 Interceptor Launch and Flyout

Interceptor launch and flyout refers to the process by which the BMDS launches the interceptor and deploys the Kill Vehicle (KV)/Kinetic Weapon (KW) to a specific insertion point. The sub-functions are described below:

- Launch Command: The interceptor receives a launch command.

- Launch Interceptors: The interceptor executes a launch sequence based on the launch command.

- Boost and Stage Interceptors: During boost and stage phases of flight, the interceptor systems (propulsion and guidance, navigation and control) fly out and boost and stage (if applicable) to reach the KV/KW deployment point.

- KV/KW Separation: During KV/KW separation, the KV/KW separates from the booster at the insertion point.

- Report Engagement Status: The interceptors report engagements status to the battle managers.

Section 1 - Page 9 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

1.3.1.08 Interceptor Guidance, Navigation and Control

Interceptor Divert and Attitude Control Systems (DACS) refer to the interceptor systems that employ a process by which the KV/KW maintains a stable attitude and diverts from the original insertion point to a point on a trajectory that will lead to a successful intercept. Sub-functions are described below:

- Communicate with Interceptor: In-flight target updates are communicated from the battle manager to the interceptor or KV/KW that provide information regarding the target. The updated information is used to provide a more accurate predicted intercept point and to refine the commands to the KV/KW

DACS.

- Compute Needed Diverts: Computation of the guidance solution is based on information derived from the KV/KW and target states.

- Execute Commanded Diverts: Executing the guidance commands includes the guidance commands for exo-atmospheric and endo-atmospheric engagements.

- Compute Needed Attitude Adjustments: Attitude adjustments are computed to maintain desired pointing and roll orientation throughout the engagement.

- Execute Needed Attitude Adjustments: Attitude adjustments are executed to maintain desired pointing and roll orientation throughout the engagement.

- Report Flyout Status: The interceptor flyout status is reported to the battle manager.

- Report Engagement Status: The interceptor engagement status is reported by the battle manager.

1.3.1.09 Interceptor Acquisition, Tracking and Discrimination

Interceptor acquisition, tracking and discrimination refers to the ability of BMDS interceptors to search for, track and identify target objects. Sub-functions are listed below:

- Handover (event): The KV/KW extracts target update information from the inflight updates to be used in acquiring targets and executes handover.

- Acquire Threat Objects: The KV/KW positions the sensor and searches for detections in its field of view.

- Track Threat Objects: KV/KW tracking involves track initiation, smoothing and management.

- Discriminate Threat Objects: KV/KW discrimination refers to the process by which the KV/KW selects an object for targeting. The KV/KW is provided a target object map, and it collects information about all tracked objects for use during discrimination.

1.3.1.10 Lethal Intercept

Intercept refers to the process by which the KV/KW selects an aim point on the targeted object, guides to that point and inflicts physical damage on the intercepted object. When the intercepted object is the RV (commonly referred to as the lethal object) and KV/KW inflicts sufficient damage to negate the payload, the intercept is a lethal intercept. Sub-functions are listed below:

Section 1 - Page 10 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

- Select the Aim point: The KV/KW selects an aim point on the targeted object.

- Transition to Terminal: The KV/KW transitions into Terminal Mode and conducts a series of diverts to intercept the selected object as close to the aim point as achievable.

- Intercept: Intercept refers to the physical contact between the KV/KW and targeted object. The difference between the aim point and the hitpoint is the miss distance. For intercepts of the lethal object the details of the engagement are used to determine whether lethal damage is inflicted. These conditions include miss distance, hit point, closing velocity, strike angle, type of target, etc.

- Task Sensors to Perform Kill Assessments: Battle Managers task sensor to perform Kill Assessment.

- Perform Hit/Kill Assessment: The Hit/Kill Assessment sub-function is associated with the battle manager interpreting data from the intercept to determine if an intercept was achieved and whether that intercept effectively negated the lethal object. This function supports potential re-engagement decisions.

1.3.1.11 Communications / Interoperability

Communications / Interoperability effectiveness in supporting essential mission functions, including data communications, will be assessed. Data communications attributes of interest include capacity, robustness, timeliness and accuracy of the data communications architecture to assess the sufficiency to support the overall mission effectiveness. Section 3.7.3 Communication of this SRD addresses the link types, node behaviors, and rule sets required for the communications architecture for the defined venue.

Section 3.7.5.5 M&S Interoperability of the SRD addresses the interface and data requirements for the defined venue. Measures defined in Table A.11: Measures for Communication / Interoperability are for data communications and interoperability (AO1.11 and AO4.1, as defined in the OTA OAP) only.

There are no measures for voice communications allocated for the T2D venue.

1.3.1.12 System to Maintain Situational Awareness

Situational awareness, as presented to the warfighter, will be assessed for sufficieny in supporting BMD operations. This includes the ability to qualitatively assess the degree to which system-level effectiveness is influenced by the accuracy and consistency of the overall mission picture presented to the warfighters. The requirements for the test infrastructure to inform the warfighters include SIPRChat, voice communications and displays. There are currently no measures allocated to Situational Awareness (AO1.12) for the T2D venue.

1.3.1.13 Other Assessment Objectives

Other assessment objectives include Suitability (AO2.X) and Survivability (AO3.X). There are currently no measures allocated from these assessment objectives for the T2D venue.

1.3.2 Truth

The 2012 MDA Modeling and Simulation Corrective Action Plan (CAP) defined the need for the development of requirements for common and consistent representation of the truth. In coordination with the element POs, the DE/S Core Truth Model group developed the Core Truth Models (CTM) Taxonomy as part of the SCM, to include a database of corresponding definitions and descriptions.

Leveraging the physics-based CTM Taxonomy, MDA/EEV defined a requirements-focused version

Section 1 - Page 11 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

to frame the development of truth requirements in this M&S SRD. This version of the CTM Taxonomy, shown below in Figure 4 – CTM Taxonomy Tailored for T2D, was coordinated through the Modeling and Simulation Engineering Working Group (MSEWG). The tailored taxonomy identifies the components of truth stimuli required across the BMDS architecture to represent Signatures, Environments, Truth Interactions and Lethality.

The SCM team consulted with all elements to determine the truth touch points; that is, the locations in the M&S System functional architecture in which BMDS functions influence or are influenced by environments, signatures or lethality. The truth touch points are being included in the functional allocation for clarity of the truth interaction to be consumed by the elements when performing specific BMDS functions. This document captures the results of these discussions. If the truth component has an effect on element performance, it is allocated to that element. The BMDS Element M&S Representations will utilize the CTM signature models to ensure common and consistent signatures.

Note: for the T2D venue, those CTM components that are not required to support assessment objectives are “greyed out.”

Section 1 - Page 12 of 17

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD) Tier 2 Digital (T2D) August 2015

M&S SRD T2D

CORE Truth Models

(CTM)

(E) Environments

(TI)

Truth Interactions

S1 Plume

EO/IR

S2 Hardbody

EO/IR

S3 Nearbody

EO/IR

S5 Hardbody

RF/RCS

S6 Nearbody

RF/RCS

S4 Plume

RF/RCS

S1.2 High Altitude

(Rarefied)

S1.1 Low Altitude (Continuum)

S3.1 Plumeshine

S3.2 Separation

Debris

S3.3 Chuff/Fuel

Debris

S3.4 Wake

S3.5 Intercept

Flash

S3.6 Post-Intercept

Debris

S3.7 Fuel Venting

S4.1 Low Altitude (Continuum)

S4.2 High Altitude

(Rarefied)

S5.2 Counter-measures

S5.3 Resident

Space Objects (RSOs)

S5.1 Hardbody

S6.1 Multiple Point

S6.2 Enhanced RCS due to Plume/

Hardbody Coupling

S6.3 RF Coupling

Between Closely Spaced

Objects

S6.4 Separation

Debris

S6.5 Chuff Fuel

S6.6 Wake

S6.7 Intercept Flash

S6.8 Post-Intercept

Debris

E1 Earth

Reference

E2 Atmosphere

E3 Solar

E4 Space

E1.1 Date & Time of

Day

E1.2 Gravity

E1.3 Terrain

E1.4 Albedo

E1.5 Sea State

E1.6 Earthshine

E1.7 Geomagnetic

Field

E2.1 Atmospheric

Profile

E2.2 Surface

Observations

E2.3 Airborne

Particulates

E2.4 Precipitation

E2.5 Tropospheric/

Boundary Layer Winds

E2.6 Clouds

E2.7 Cloudshine

E2.9 Atmospheric Constituents

E2.14 Aurora

E2.15 Ionospheric State

E2.16 Sky Noise

E4.2 Celestial Bodies

E4.3 Plasma/

Radiation

E4.1 Moonshine

E4.4 Galactic Noise

S2.2 Countermeasu res

S2.3 Resident

Space Objects (RSOs)

S2.1 Hardbody

TI 1.1

Terrestrial

Background Effects

TI 1.4

Cloud

Background Effects

TI 1.5

Cloudshine

Effects

TI 1.6

Skyshine Effects

TI 1.7

Moonshine

Effects

TI 1.2

Earthshine

Effects

TI 1.3

Atmospheric Attenuation/

Emission

TI

EO/IR

Propagation

TI 1.8

Sunshine Effects

TI 1.11

Celestial

Background Effects

TI 1.12

Aurora Effects

TI 1.13

Attenuation/

Scattering Due to Chuff

TI 1.9

Earth Limb Background

Effects

TI 1.10

Nuclear High Altitude Burst

Effects

TI 2.1

Ice/Freezing Rain Effects

On Radar

TI 2.4

Multipath

Effects

TI 2.5

Blowing Sand/

Dust Effects

TI 2.6

Clear Air

Attenuation/ Absorption

TI 2.7

Tropospheric Scintillation

TI 2.2

Ground/Sea

Clutter Effects on Radar

TI 2.3

RF Lens Loss

TI 2.8

Tropospheric

Refraction

TI 2.9

Tropospheric

Ducting

TI 3

Aerodynamic Propagation

TI 2

RF

Propagation

TI 2.10

Hydrometeor ological Losses

TI 2.13

Ionospheric Range Delay

TI 2.14

Aurora Effects

TI 2.15

Solar Noise

Effects

TI 2.16

Nuclear High Altitude Burst

Effects

TI 2.11

Ionospheric Scintillation

TI 2.12

Ionospheric Loss

TI 2.17

Attenuation/

Scattering Due to Chuff

TI 3.2

Aerothermal

Demise

TI 3.1

Aerodynamic/

Body Interactions

(S) Signatures At source

E2.10 Middle

Atmospheric Winds

E2.11 Skyshine

E2.12 Upper

Atmospheric Density

E2.13 Thermospheric/

High Altitude Winds

TI 2.18

Sky Noise

(L) Lethality

L1 End Game Lethality

L2 Post-Intercept

Debris

L3 Consequences of

Engagement

L1.1 Unitary

Chemical Payload

Response

L1.4 HE Sub Payload

Response

L1.5 HE Nuclear & Rad Payload

Response

L1.2 Unitary HE

Payload Response

L1.3 Chemical

Biological Sub Payload

L2.1 Physical

Characteristics

L2.4

RF

Characteristics

L2.5

EO/IR

Characteristics

L2.2 Dynamic

Characteristics

L2.3 Aerodynamic

Characteristics

L3.4 Hazard Area Assessments

L0.1 KV Physical

Characteristics

L0.2 KV Engagement

Conditions

L0.3 Target Physical Characteristics

L0 End Game Geometry

L0.4 Target

Engagement Conditions

E3.4 Solar Noise

E3.1 Sunshine

E3.2 Solar Wind

E3.3 Solar Storm

Figure 4 - Core Truth Taxonomy Tailored T2D

Excluded for the Intended use of BMDS Performance Assessment in the T2D Venue

Section 1 - Page 13 of 17

E2.8 Fog

UNCLASSIFIED//FOUO

UNCLASSIFIED//FOUO

Modeling and Simulation (M&S) System Requirements Document (SRD)…