MDA_Directive_8315.03_Modeling_and_Simulation_Program_Dec2015.pdf

MISSILE DEFENSE AGENCY

MODELING AND SIMULATION PROGRAM

MDA DIRECTIVE 8315.03

December 21, 2015

Office of Primary Responsibility: Director for Engineering (DE)

MDA 8315.03, December 2015

TABLE OF CONTENTS

PURPOSE

APPLICABILITY AND SCOPE

POLICY

RESPONSIBILITIES

Director for Engineering (DE) Director for Modeling and Simulation Program (DE/S) MDA Systems Engineer (DE/E) MDA Chief Engineer (DE/C) Director for Technical Intelligence (DE/I) Director for Test (DT) Program Executive of Advanced Technology (DV) MDA Element/Component Program Managers (PMs) Director for Operations

EFFECTIVE DATE

ENCLOSURE, REFERENCES

GLOSSARY

Acronyms Definitions

FIGURES

1. M&S Enterprise

2. M&S Enterprise Management

DEPARTMENT OF DEFENSE

MISSILE DEFENSE AGENCY

5700 18th STREET

FORT BELVOIR, VIRGINIA 22060-5573

DE 8315.03

SUBJECT: Modeling and Simulation Program

References: See Enclosure

1. PURPOSE. This directive describes Missile Defense Agency (MDA) policy for managing the modeling and simulation (M&S) enterprise. This directive implements References (a) through (c) and supersedes MDA Directives 8315.01 and 8315.02 (References (d) and (e)).

2. APPLICABILITY AND SCOPE

a. This directive applies to staff in MDA directorates, elements, and components of the Ballistic Missile Defense System (BMDS), and staff in all other MDA organizations that fund, develop, support, and/or use BMDS models, simulations, or the associated data supplied by them. Additionally, this directive applies to MDA organizations that fund external development of non-MDA element M&S.

b. The M&S enterprise is composed of all resources, assets, and processes necessary to simulate the BMDS for all categories of intended uses spanning all phases of the systems engineering process (see Figure 1). The M&S enterprise includes all element/component models and drivers; framework, threat, and core truth models (CTMs); and the infrastructure, hardware, and facilities necessary to design, develop, integrate, and employ all M&S products.

Management of the M&S enterprise will be conducted as a single, synchronized program supporting multiple intended uses and venues such as performance assessment, training/exercise capabilities, concept analysis, international engagement, and representations required for element development. Within the M&S enterprise, there are two primary categories of M&S products:

system-level M&S and element/component-level M&S.

(1) Management of system-level M&S will be centralized within the Agency and delegated to the Director for Engineering (DE) to ensure timely delivery of credible, integrated BMDS simulations.

(2) Management of element/component M&S will be delegated to the program executive (PE)/program manager (PM)-level where the program expertise of the represented element system resides.

(3) In cases where element/component-level M&S supports system-level products, those element/component-level M&S applications will be subject to joint DE and PE/PM commitments to schedule and funding for implementing allocated system-level requirements.

These commitments will be aggregated into a top-level program plan and baselined by the

Integration Synchronization Group (ISG)/Program Control Board (PCB). Element PEs and PMs will continue to manage, budget, plan, develop, and employ these simulations. However, the system-level commitments will be jointly tracked and reviewed by DE and the PE/PMs. Any change to the baselined system-level commitments will be adjudicated in accordance with ISG/PCB change management procedures.

Figure 1. M&S Enterprise

c. The M&S enterprise supports BMDS development, fielding, and operations, and produces assessment data reflecting the behavior and capabilities/limitations of the BMDS.

MDA routinely uses M&S to formulate evolutionary plans; guide investment strategies; develop system specifications; integrate and test the BMDS; verify and assess M&S performance;

support tactics, techniques, and procedures (TTP) development; and train operators. Accredited M&S expands the overall BMDS testing envelope to a variety of engagement conditions beyond those that can be achieved with flight tests. Verification and validation (V&V) data requirements will be identified during the BMDS test planning process to ensure M&S validation is achieved and kept current.

(1) Vision. To provide fully accredited M&S for all intended uses.

(2) Mission. To develop, integrate, verify, validate, and employ accredited M&S to meet the needs of the Agency and stakeholders, and to guide and enable technology development to advance state-of-the-art M&S.

M&S Policy

• Synchronization of Agency M&S

• Integrated baseline management

• M&S SE processes

• M&S system‐level design

• VV&A strategy

Element/Component M&S

• M&S development, VV&A (Element/Component simulations)

• Framework, threat, core truth models (CTMs)

• Communication

System‐Level M&S

• M&S system‐level integration and verification

• BMDS integrated simulations

(supports performance assessments, Element integration, training)

• BMDS‐level simulations (supports Wargames, exercises, concept analysis, experimentation)

• Infrastructure • Resources

(3) Attributes and Goals of the M&S Enterprise

(a) Address all categories of intended uses within MDA to include concept analysis and trade studies, wargames and experimentation, element and component integration, system performance assessment, flight and ground test prediction and analysis, and Warfighter/operator training and exercises.

(b) Supply data of sufficient quality, quantity, and timeliness to meet intended uses.

(c) Develop a comprehensive suite of cost-effective, modular, composable, scalable, and extensible M&S tools that use a common framework, common test control, consistent truth, and standardized interfaces for system-level end-to-end hardware-in-the-loop and digital simulations.

(d) Achieve verification, validation, and accreditation (VV&A) of all enterprise models, simulations, and federations for their applicable intended uses to establish model-user confidence.

(e) Provide an enterprise that is adaptive and responsive to changes driven by BMDS development, changing real-world threat capabilities, fiscal realities, and technology evolution opportunities.

d. The M&S enterprise management approach varies between system-level and element-only M&S. Figure 2 summarizes these organizational lines of responsibility that are further explained in Section 4 of this directive. MDA Instruction 8315.04-INS (Reference (f)) discusses cost, schedule, and performance management of integrated system-level M&S. MDA Instruction 8315.05-INS (Reference (g)) describes VV&A activities required across all areas of the M&S enterprise. MDA Instruction 8315.06-INS (Reference (h)) describes systems engineering (SE) processes that support the integration of system-level M&S.

e. Integrated management of system-level M&S is applied to system-level end-to-end hardware-in-the-loop and digital simulations to include the element/component models developed and provided as applications supporting those products. For these system-level products, centralized cost, schedule, performance, and risk management through joint DE and PE/PM commitments to meet cost, schedule, and performance of system-level capabilities is necessary to ensure the following objectives are met:

(1) Achievement of a product delivery within cost and schedule constraints.

(2) Employ rigorous SE processes to develop, allocate, track, and monitor system-level

M&S requirements resulting in a credible system-level product.

(3) Develop and sustain M&S system-level testing events through the design, scenario generation, and integration processes.

(4) Verify, validate, and accredit M&S for system-level intended uses.

(5) Conduct M&S operations and support, including maintenance, system integration, and test/event execution support for multiple intended uses.

Figure 2. M&S Enterprise Management

f. For all other M&S not within the system-level management practice, management responsibility is delegated to the PE/PM with budget authority for the item being represented.

However, this standalone and other MDA M&S category of products is still within the M&S enterprise, and the PE/FM has the following responsibilities to ensure program synchronization and efficiency across the MDA M&S program.

(1) Report M&S funding levels as required to support Agency budgeting activities as well as execution year M&S reporting.

(2) Employ modeling approaches that are consistent with other related Agency M&S products to improve the consistency of results for areas where similar BMDS technical capabilities and functions are modeled within MDA M&S.

(3) Employ existing models and components to both improve consistency of results across the enterprise as well as avoiding duplication of effort and increased costs.

(4) Conduct VV&A of M&S in accordance with Reference (g).

3. POLICY. It is MDA policy that:

a. All M&S in MDA will be managed to ensure consistent, accurate results, and efficient application of Agency resources in serving all categories of M&S intended uses.

b. BMDS element developers and functional organizations will manage, design, develop, deliver, accredit, and operate representations of their systems and components that fall within their budget authority. This ensures accurate M&S representations for both standalone element intended uses and integrated, system-level representations. Prior to any new or modified model development, the element/functional organization will present the requirement, program plan, and budget to the ISG/PCB for approval.

c. All system-level M&S will be designed, developed, accredited, and operated as an integrated program. System-level M&S consists of integrated BMDS representations composed of multiple element/component models and/or drivers, unless a system-level composition will be used by a single element/component for internal testing, training, and/or analysis. System-level M&S is subject to internal processes and rigor similar to those used in the development, testing, and fielding of the BMDS. These processes include using the BMDS baselines for approval and configuration management change control of compliance documents governing integrated development, using the SE processes and design review structure to support VV&A. Finally, these processes include using regular program reviews to manage cost, schedule, and performance.

(1) System-level M&S will be governed in accordance with an M&S baseline and with ISG/PCB change management procedures. The M&S baseline will be maintained as a distinct part of the BMDS Technical Baseline to include M&S compliance documents and other artifacts deemed necessary to effectively manage system-level M&S. Formal change control of the M&S baseline will be managed through existing board structures for the BMDS Technical Baseline, in accordance with Reference (f).

(2) SE processes are used to collect system-level M&S stakeholder needs, develop and allocate M&S requirements, and monitor/track the progress made toward fulfilling the M&S requirements.

(3) Execution of the system-level M&S program will be managed through program reviews. These reviews will consist of lower-level element/component reviews, supporting a summary execution review that spans all system-level M&S. These reviews will track execution of requirements and associated risks, resources, scheduled capability delivery, VV&A and plans, and other programmatic details. These reviews will ensure that all funding obligations, investment priorities, and de-obligations affecting the development, delivery, and VV&A of system-level M&S are consistent with Agency goals for the M&S enterprise.

d. All Agency system-level M&S will use a common framework, standardized interfaces, and consistent truth.

e. All elements/component representations for system-level M&S supporting BMDS fielding decisions will be delivered and accredited within a schedule supporting the integration, test, data reduction, and analysis necessary to inform the fielding decisions. Elements seeking to use system-level M&S to provide evidentiary data to support a fielding decision should use an M&S development and acquisition strategy that delivers necessary M&S representations of element/ component capabilities in time to support evaluation and test of their tactical software.

f. M&S developers will seek to use contractual approaches that are flexible and responsive to support the dynamic nature of M&S enterprise products. These approaches include elimination of proprietary data and proprietary source code from future M&S procurement actions.

g. Models, simulations, and associated data used to support MDA processes, products, and decisions will be accredited for each intended use in accordance with Reference (g).

4. RESPONSIBILITIES

a. The Director for Engineering (DE) will:

(1) Function as the single technical authority in accordance with MDA Directive 5000.05 (Reference (i)), responsible for the overall oversight of the M&S enterprise.

(2) Have final approval authority over all funding obligations, investment priorities, and de-obligations affecting the development and delivery of system-level M&S required to support events and analysis in accordance with MDA Memorandum, “Ballistic Missile Defense System Model and Simulation Program Investments” (Reference (j)).

(3) Act as the BMDS M&S accreditation authority for MDA.

(4) Inform the Director on M&S program status.

(5) Advocate for the M&S enterprise budget and manage resource allocation of system-level M&S capability providers across the Agency.

(6) Provide test requirements to the Integrated Master Test Plan (IMTP) planning process to ensure the necessary referent data is collected from flight and ground testing to support VV&A of system-level M&S.

(7) Act as M&S baseline owner for all additions, deletions, or modifications to the compliance documents and other artifacts on the M&S baseline.

b. Under the authority, direction, and control of the DE, the Director for Modeling and Simulation Program (DE/S) will:

(1) For system-level M&S, conduct advanced M&S planning, and implement Agency M&S governance policy into standards of practice. Support M&S SE, lead M&S systems design activities, coordinate element/component development activities, and conduct cross-Agency M&S integration. Support and/or conduct Agency M&S events, and deliver integrated M&S capabilities.

(2) Provide DE cognizance and assist in synchronizing all MDA M&S in support of the budgeting process. For system-level M&S, plan, prioritize, assess, document, and report according to Reference (f).

(3) Provide integrated management of system-level M&S cost, schedule, performance, and risk to meet allocated M&S requirements and stakeholder needs following the processes in Reference (f).

(4) For system-level M&S, conduct regular program reviews with each M&S element/ component by intended use in accordance with Reference (f). These reviews will track element/ component M&S progress in achieving system-level M&S requirements and derived element/ component cost, schedule, and performance commitments.

(5) Conduct and manage system-level M&S integration. Support test event execution activities.

(6) Conduct system-level M&S verification and analysis of system-level M&S verification test data to support VV&A activities. This includes conducting system post-flight reconstructions.

(7) At the M&S system-level, develop program content, resource, and schedule-related artifacts for the M&S baseline as required by the M&S baseline owner. Coordinate necessary additions, deletions, or modifications to these artifacts through the ISG/ PCB.

(8) Function as a component-model developer for framework, threat M&S, and CTM M&S, as well as stand-alone BMDS simulations and non-MDA elements. In this capacity, DE/S is subject to the items in paragraph 3.c.(3) of this directive.

c. Under the authority, direction, and control of the DE, the MDA Systems Engineer (DE/E) will:

(1) With stakeholders, establish stakeholder M&S needs.

(2) Implement an M&S SE process for requirements development in accordance with Reference (h). Develop and allocate M&S requirements for system-level M&S and coordinate necessary additions, deletions, or modifications to system-level requirements documents on the M&S baseline through the ISG/PCB process.

(3) Track M&S requirements’ progress. Conduct M&S VV&A for all intended uses in accordance with Reference (g).

(4) Establish and implement a system-level M&S VV&A process that results in accredited M&S for all intended uses across MDA in accordance with Reference (g).

(5) Define, in coordination with each element/component, the referent data needed for M&S VV&A efforts. Support Agency flight and ground test planning activities to help allocate data needs to tests. Track the collection progress over time and by test event.

(6) Plan System Post Flight Reconstruction activities to validate system-level M&S and analyze and assess System Post Flight Reconstruction results to support system-level VV&A.

d. Under the authority, direction, and control of the DE, the MDA Chief Engineer (DE/C) will support DE/S and element/component representatives regarding M&S baseline artifacts that will be presented to MDA decision boards (e.g., System Engineering and Integration Council, ISG, PCB).

e. Under the authority, direction and control of the DE, the Director for Technical Intelligence (DE/I) will:

(1) Levy threat modeling requirements upon all threat M&S used to enable system-level simulation employment, coordinating with DE/E.

(2) Verify and validate threat M&S and resultant threat data products.

f. The Director for Test (DT) will:

(1) Collaborate in developing and testing system-level M&S with DE/S and DE/E.

(2) Provide and synchronize test resources to support M&S development, verification, and validation as defined in the IMTP and in accordance with MDA Instruction 3000.07-INS (Reference (k)).

(3) Direct and manage test event execution support for ground and flight test events.

Coordinate with DE/S on M&S integration supporting test event execution.

(4) Direct and manage execution support for exercises, wargaming, and demonstrations.

Coordinate with DE/S on M&S modifications and enhancements supporting event execution.

g. The Program Executive for Advanced Technology (DV) will:

(1) Design, develop, integrate, test, maintain, and operate M&S supporting the research and technology activities that reside within their program authority for all intended uses.

(2) Support DE’s M&S enterprise-level budgeting and planning.

(3) Coordinate M&S-related technology development, including Small Business Innovative Research topics and small business technology transfers. Work with DE to improve overall Agency M&S capabilities and ensure transition of M&S capabilities corresponding to new BMDS elements, components, or capabilities for their representation within integrated BMDS representations.

(4) Function as the M&S accreditation authority for all representations of emerging BMDS capabilities residing within their program authority.

h. MDA Element/Component Program Managers (PMs) will:

(1) Manage, fund, design, develop, integrate, test, and maintain the element/component representations of BMDS capabilities residing within their program authority for all of the M&S intended uses.

(2) Conduct M&S program reviews supporting DE system-level M&S management, in accordance with Reference (f).

(3) Collaborate in developing, integrating, testing, verifying, analyzing, and executing system-level M&S activities containing element/component representations.

(4) Ensure element/component M&S V&V evidence meets element/system-level intended uses. Ensure timely delivery of M&S representations and the associated V&V evidence.

(5) Support M&S enterprise budgeting and planning.

(6) Ensure M&S baseline and products are placed on contract and are traceable to element and enterprise requirements. Coordinate necessary additions, deletions, or modifications to these artifacts through the ISG/PCB process in accordance with Reference (f).

(7) Function as the element-level M&S accreditation authority for representations of BMDS capabilities residing within their program authority. Conduct element/component-level M&S V&V. Support system-level M&S VV&A in accordance with Reference (g).

i. The Director for Operations (DO) will:

(1) During planning, programming, budgeting, and execution process ensure M&S resource requirements are identified by PE/PMs and consolidated for DE verification

(2) Work in conjunction with DE to ensure M&S requirements are identified in budget justification documents.

(3) In conjunction with DE, review year of execution expenditures on M&S efforts.

5. EFFECTIVE DATE. This directive is effective immediately.

J. D. SYRING

Vice Admiral, USN Director

Enclosure:

References Glossary

13 ENCLOSURE

ENCLOSURE

REFERENCES

(a) DoD Directive 5000.59, “DoD Modeling and Simulation (M&S) Management,”

August 8, 2007

(b) DoD Instruction 5000.61, “DoD Modeling and Simulation (M&S) Verification, Validation, and Accreditation (VV&A),” December 9, 2009

(c) Deputy Undersecretary of Defense for Acquisition and Technology and Director, Operational Test and Evaluation Modeling and Simulation Guidance for the Acquisition Workforce, Version 1.01, September 2008

(d) MDA Directive 8315.01, “Modeling and Simulation (M&S) Verification, Validation and Accreditation (VV&A),” January 21, 2009, Incorporating Change 1, April 6, 2011 (hereby cancelled)

(e) MDA Directive 8315.02, “Modeling and Simulation Program,” January 13, 2009, Incorporating Change 1, April 6, 2011 (hereby cancelled)

(f) MDA Instruction 8315.04-INS, “Integrated Ballistic Missile Defense System Modeling and Simulation Management,” Month XX, YEAR

(g) MDA Instruction 8315.05-INS, “Ballistic Missile Defense System Modeling and Simulation Verification, Validation, and Accreditation,” Month XX, YEAR

(h) MDA Instruction 8315.06-INS, “Ballistic Missile Defense System Modeling and Simulation Systems Engineering,” Month XX, YEAR

(i) MDA Directive 5000.05, “Single Technical Authority,” September 25, 2013

(j) MDA Memorandum, “Ballistic Missile Defense System Model and Simulation Program

Investments,” November 1, 2010

(k) MDA Instruction 3000.07-INS, “Ballistic Missile Defense System Ground Test Concept of

Operations,” December 3, 2012, Administrative Change 1, March 4, 2013

14 GLOSSARY

GLOSSARY

PART I. ACRONYMS

BMDS Ballistic Missile Defense System

CTM core truth model

DE Director for Engineering

DE/C MDA Chief Engineer

DE/E MDA Systems Engineer

DE/I Director for Technical Intelligence

DE/S Director for Modeling and Simulation Program

DT Director for Test

DV Program Executive for Advanced Technology

IMTP Integrated Master Test Plan

ISG Integration Synchronization Group

M&S modeling and simulation

MDA Missile Defense Agency

PCB Program Control Board

PE program executive

PM program manager

SE systems engineering

TTP tactics, techniques, and procedures

V&V verification and validation

VV&A verification, validation, and accreditation

DO Director for Operations

PART II. DEFINITIONS

accreditation. Official certification that a model, simulation, or federation of M&Ss and its associated data are acceptable for use for a specific purpose.

composable. Provides ability to mix/match components (e.g., representations and CTMs) to allow assembling and deploying various configurations of the system to satisfy specific user needs/requirements (or intended uses).

consistent truth. For system-level M&S consisting of multiple element representations, the concept that allows for each element to generate truth data individually; however, such data is free from variation among the elements and does not contradict or violate scenario requirements

15 GLOSSARY

and simulation control constraints. Inherent in this concept is the requirement that evidence of consistency is readily available and provided by each participant.

core truth models (CTMs). Models supplied to provide consistency and effects for lethality, electro-optical/infrared, debris, radio frequency signatures, environments, and truth interactions.

extensible. Capable of expanding/enhancing the system with anticipated capabilities without having to make major changes to the system infrastructure (or capable of easily and quickly adding new participants, representations, and/or models).

framework. Component of a system-level simulation that promotes communication and coordination between the various M&S component models, typically including functions like common simulation control, common time management, and presentation of truth stimuli to each constituent model.

intended use. The problem to be addressed by the M&S, including the system or process being represented and the role it plays in the overall program. Sample categories of intended uses for MDA M&S include, but are not limited to:

Concept analysis and trade studies.

Wargaming and experimentation.

Element and component integration.

MDA M&S system integration and checkout.

Flight and ground test prediction and analysis.

Warfighter/operator training and exercises.

modeling and simulation (M&S) enterprise. A single, integrated, and synchronized program composed of all models and simulations used to simulate the BMDS, including element/ component models, framework, threat, and CTMs, as well as the people, resources, and infrastructure to develop and employ these models and simulations.

modular. System is designed using loosely coupled, cohesive components.

system-level modeling and simulation (M&S) (or representation). A representation of the BMDS that involves integration of two or more element representations, and where the intended use requires representation of integrated BMDS capabilities derived from two or more BMDS elements.

16 GLOSSARY

system performance assessment. Assessment of BMDS-level behavior to establish confidence that the BMDS can be effectively employed to execute its ballistic missile defense mission.

validation. Determining the degree to which a model, simulation, or federation of models and simulations, and their associated data, accurately represent the real world from the perspective of the intended use(s).

verification. Determining that a model, simulation, or federation of M&S implementations, and their associated data, accurately represent the developer’s conceptual description and specifications.