Attachment_J-01_-_BMD_Systems_Engineering_PWS_2016-10-03_(track_changes).pdf

HQ0147-16-R-0009

Attachment J-01 BMD Systems Engineering

TEAMS Performance Work Statement BMD Systems Engineering 10August 03 October 2016

Revision 1

Amendment 0001

1. Top Level Functional Requirements/Scope

1.1 Purpose

To provide a highly integrated and effective Ballistic Missile Defense (BMD) capability to defend the homeland, regional interests, allies, and deployed forces against ballistic missile threats of all ranges and in all phases of flight.

This requirement is for the Engineering Directorate (MDA/DE) and covers geographically dispersed locations identified in this Performance Work Statement (PWS), i.e., the National Capital Region (NCR); Dahlgren, VA (DHL); Huntsville, AL (HSV); and Colorado Springs, CO (COS).

This effort includes BMD System (BMDS) architecture, system engineering, and engineering activities as shown in Figure 1.1, the Missile Defense Agency (MDA) System Engineering “V”. This effort complements engineering activities occurring within the “Element Design & Build” systems engineering phase. It includes the identification and definition of future capabilities not yet assigned to an MDA product office, planning for technology demonstrations and risk reduction tests, development of transition plans for future capabilities into product offices, and administrative and technical coordination of Special Access Programs (SAPs).

Figure 1.1: MDA System Engineering "V"

1.2 Organizational Description

a. The Engineering Directorate (MDA/DE) is responsible for technical design and development of the BMDS and supports its integration and assessment through the organization shown in Figure 1.2. This ensures unity of effort in the development of subsystems and architecture designs to deliver system-level capabilities.

Engineering Ops Mgt

(DEO)

Independent

Assessments / Knowledge Ctrs

(DEA)

Director for Engineering

DE

Chief Scientist

(DE/CS)

Technical Director

(DE/TD)

BMD System Integrator (DE/SI)

BMDS

Architect

DE/B

MDA Systems Engineer

DE/E

MDA Chief Engineer

DE/C

BMDS Warfighter Technical Interface

DE/W

M&S Program

DE/S

Technical Intelligence

DE/I

Architecture & Concepts

EBA

Future Enhancements

EBB

System Design & Specification

EED

System Flight Test Engineering

EEF

Baseline Controls

ECB

Assured Design

& Processes

ECD

Warfighter Interface

EWW

International

EWI

M&S Products

ESP

M&S Operations

ESO

Requirements

EII

Cyber Security

EIC

Counter-

Countermeasures

EBC

System Test & Performance

Analysis

EET

System

Verification

EEV

System Assessment

EEA

Integration

ECI

Industrial Manufacturing & Technology

ECM

Element Chief Engineers

M&S System Integration &

Execution

ESI

Threat Systems

EIT

Counter-

EIX

Security & Program

Protection

EIR

Special

Programs AA Aegis Ashore GM GMD BC C2BMC DVM Common Kill Vehicle EIS

Element System Engineers

AG Aegis Guided Missile

AW Aegis Weapon System

IP US-Israeli Coop SN

TC Tgts & Countermeasures SS

Sensors

STSS

Concept

DVL Sensor and Laser Tech

DVR Advanced Research Adv Concepts &

Tech Intel

Matrix Support

AX Aegis Sea-Based TH THAAD CE Exploration DVS Perf Assessment EIM

Terminal LTPO Lower Tier Proj Ofc GD Global Deployment

Figure 1.2: MDA Engineering (MDA/DE) Organization Chart

1) Director for Engineering (MDA/DE)

The Director for Engineering is the MDA Single Technical Authority and Engineering Functional Manager. This ensures unity of effort in the development of subsystems and architecture designs to deliver system-level capabilities. The Engineering Directorate (MDA/DE) provides system and product engineering technical support to the agency staff and program offices. This Directorate is responsible for the BMDS Technical Baseline (TBL), the Operational Capacity Baseline (OCB), and Test Baseline requirements. The Engineering Directorate also provides recommended technical responses and analyses for external inquiries such as Requests for Analysis (RFAs), Government Accountability Office (GAO) requests, Department of Defense (DoD) Inspector General (IG) inquiries, and Congressional

DE Organization As of: 22 June 2015 inquiries. In addition, the Engineering Directorate directs studies, analyses, assessments, and alternatives for technology reviews, baseline reporting, higher level information and reporting (e.g., Office of the Secretary of Defense (OSD) or DoD), operational analysis, and agency corporate decision-making.

2) Engineering Operations Management (MDA/DEO)

The Engineering Operations Management office manages personnel, business, contracts, and facilities and space allocation in support of the Engineering and Technical Intelligence functional areas. Primary responsibilities include managing Government and military personnel, business and financial operations, contracts, and facilities and space allocation; developing and promulgating MDA/DE policies and procedures; and coordinating the Federally Funded Research and Development Center (FFRDC) and University Affiliated Research Center (UARC) programs.

3) BMDS Architect (MDA/DE/B)

The BMDS Architect office defines, implements, and maintains a disciplined process that establishes BMDS Architecture support requirements and produces alternatives for satisfying those requirements. The BMDS Architect documents the Agency’s far-term (beyond the Five Year Defense Plan (FYDP)) technical needs, assesses technology concepts, and provides the roadmap for BMDS evolution. The BMDS Architect oversees the Integrated Air and Missile Defense (IAMD), discrimination, and counter-countermeasure programs; and executes MDA/DE special programs.

The Architecture and Concepts office (MDA/EBA) defines, implements, and maintains a disciplined process that enables a roadmap for BMDS evolution that results in alternative BMDS architectures defined as concept level functional and performance needs that guide programmatic decisions as well as technology development and experimentation for future BMDS Capabilities.

The Counter-Countermeasures office (MDA/EBC) executes all system-level engineering functions required to evolve missile defense capabilities for improving identification of lethal objects and mitigating countermeasures.

4) MDA Systems Engineer (MDA/DE/E)

The MDA Systems Engineer owns the systems engineering function and executes processes that produce the system-level engineering standards and technical documentation Program Directors (PDs) and Program Managers (PMs) need to develop the various elements and components of the BMDS. The MDA Systems Engineer develops and allocates requirements, including interface requirements that define the BMDS capability to be developed.

The System Assessment office (MDA/EEA) develops, documents, and executes the approach for assessing BMDS technical and operational capability by updating and maintaining the Integrated Master Assessment Plan (IMAP), which documents the MDA assessment planning process and the overarching BMDS assessment plan in support of incremental deliveries. MDA/EEA plans, executes, and documents BMDS assessments to support BMDS OCB decisions, BMD System capability and limitations determination decisions, and BMDS performance characterization.

The System Design and Specification (MDA/EED) office designs the integrated BMDS through a disciplined systems engineering process that creates the BMDS level requirements enabling development and detailed design of new BMD capabilities. The EED office defines BMDS technical content and conducts functional and performance trade studies and analyses including developing BMDS capability and system requirements; conducting Specialty Engineering design, analysis and trade studies to define MDA technical core standards; and identifying, assessing, and reporting BMDS High Altitude Exo-atmospheric Nuclear Survivability (HAENS), Nuclear, Biological, and Chemical Contamination Survivability (NBCCS) capability. The EED office manages the BMDS requirements traceability process to identify and resolve requirements disconnects and manage adherence to technical core standards.

The System Flight Test Engineering (MDA/EEF) office plans and supports execution of a flight test program that addresses BMDS requirements, demonstrates and measures the capability of the BMDS, and provides meaningful data to anchor system- and element-level models. The EEF office develops and manages test objectives, evaluation criteria, system test configurations, scenarios, flight test risks, and data requirements; and ensures test objectives are addressed during test execution and post-test evaluation.

The System Verification office (MDA/EEV) performs three primary tasks: Modeling and Simulation (M&S) systems engineering test requirements development; M&S Verification, Validation, and Accreditation (VV&A); and BMDS specification verification. The fundamental approach of the EEV Office is to improve accreditation of the M&S used to assess BMDS performance; ensure the BMDS accurately represents the BMDS specification design; and ensure consistent and traceable development of the design requirements for the M&S used to assess BMDS performance. M&S test requirements are documented in the M&S System Requirements Document (SRD) while data requirements are captured as system- and element-level Critical Engagement Conditions (CECs), Empirical Measurement Events (EMEs) and documented in the Test Resource Mission Planning Tool

(TRMP-T).

5) MDA Chief Engineer (MDA/DE/C)

The MDA Chief Engineer ensures sound and integrated engineering and manufacturing processes and products; thorough element engineering controls, management, and verification; independent test, analysis, and assessment of failed and high risk events and engineering efforts; and industrial and manufacturing readiness. The Chief Engineer coordinates, controls, and manages BMDS interface activities including definition, design, implementation, verification, traceability, interoperability, and issue resolution through the Interface Control Working Group (ICWG). The Chief Engineer leads Failure Review Boards (FRBs) when primary test objectives are not met, participates in the BMDS Discrepancy Report (BDR) process, and is responsible for execution of the Failure Review, Analysis, and Corrective Action System (FRACAS) to ensure performance shortfalls are identified and fixed prior to capability delivery. The Chief Engineer also participates in the test risk management process and is responsible for execution of the Mission Readiness Working Group (MRWG).

The Baseline Controls office (MDA/ECB) facilitates BMDS effectiveness and interoperability through control of the BMDS TBL and OCB as well as the orchestration of technical execution within and DE support to the BMDS change management process. MDA/ECB conducts BMDS integration planning, provides timely and effective support to program offices in their technical execution against the TBL and OCB and their related program objectives and plans, chairs the OCB Working Group (OWG), and ensures effective communication of BMDS engineering.

The Engineering Integration office (MDA/ECI) ensures rigorous element interfaces and interoperability processes, specifications, control and discrepancy resolution.

The ECI office administers the Interface Control Working Group (ICWG) and Interoperability Technical Analysis Group (ITAG), and provides expert review of evidence related to interfaces and interoperability presented in system and element requirements and design reviews. The ECI office establishes and maintains reliability as a complete and comprehensive core engineering competency, and administers the Joint Reliability and Maintainability Evaluation Team (JRMET) and Reliability, Availability and Maintainability Working Group (RAMWG). The ECI office also ensures consistent, thorough, and integrated risk and issues management, execution, and products through the Mission Readiness Working Group (MRWG), and Failure Review, Analysis and Corrective Action System (FRACAS).

6) BMDS Warfighter Technical Interface (MDA/DE/W)

The Warfighter Technical Interface office provides a single point of contact to the warfighter for all engineering and technical issues related to the BMDS, and is the MDA engineering representative in all warfighter forums including the Warfighter Involvement Process (WIP), Homeland Defense Architecture Working Group (HDAWG), and various international technical fora. DE/W works with the Combatant Commands (CCMDs) to define their BMDS mission capabilities, collaborates with the warfighter to assist in defining capabilities and limitations, and manages the development of the MDA achievable capabilities list based on warfighter prioritized capabilities list. DE/W works with the warfighter to define the technical components of RFAs and Requests for Information (RFIs), and provides oversight and review of all technical products going to external agency stakeholders.

DE/W also supports all engineering aspects of MDA international acquisition and international cooperative programs.

The International Engineering office (MDA/EWI) leads the collaborative engineering activity that enables both U.S. and foreign partners to understand the existing system capabilities, architectural performance and operational concepts while identifying potential opportunities for collaboration. The EWI office supports all engineering aspects of MDA International Acquisition Program development of new and/or refined U.S./Allied BMDS initiatives through MDA international cooperative programs. This office also leads the coordination with MDA International Affairs Directorate (MDA/DI) to ensure consistency of BMDS technical development and planning within MDA international activities.

7) Modeling and Simulation (M&S) Program (MDA/DE/S)

The MDA uses an integrated layered approach to develop a system level M&S architecture integrated with, and reflective of, the BMDS incorporating element level M&S. DE/S executes a single, integrated, and synchronized program to manage M&S development in support of the BMDS acquisition lifecycle. The system-level M&S incorporates element- and component-level M&S with a framework in order to provide a representation of the full BMDS system-of-systems behavior. Element-level M&S must accurately reflect its components and functionality with sufficient fidelity when operating separately. The system-level architecture integrates the elements’ M&S into one cohesive system. At the system level, each component M&S must demonstrate a different set of fidelity requirements to ensure interoperability.

The M&S Products office (MDA/ESP) oversees the acquisition of M&S frameworks, core truth models, new threat models and simulations, and other assigned models and simulations to include design, development, verification, system test, sustainment and spiral upgrades for models and simulations. ESP manages the M&S product testing program.

The M&S Operations office (MDA/ESO) provides M&S operations support to the Warfighter and MDA for designated products and applications for the purpose of supporting MDA’s M&S intended use categories of concept evaluation, developmental engineering, testing and verification, assessment, training, and operational support. ESO oversees the production and delivery of both event-based (Integrated Threat Package (ITP)) and development-based (Developmental Threat Package (DTP)) threat data.

The M&S Integration and Event Execution office (MDA/ESI) leads the integration, testing and verification of Hardware-in-The-Loop (HWIL) architectures and digital end-to-end simulations to support the agency’s ground and Flight Test program, and other event types that require HWIL and digital end-to-end simulation capabilities;

M&S integration for all HWIL events; and M&S integration for digital events.

8) Technical Intelligence Directorate (MDA/DE/I)

The DE/I Directorate provides intelligence, cybersecurity engineering, threat systems engineering, counterintelligence, and research, development and acquisition security services to protect the agency and BMDS technologies, facilities, information, and people from threats and the compromise of classified information.

The Threat Systems Engineering office (MDA/EIT) supports a collaborative MDA Engineering effort to develop, test, and field BMDS capabilities. MDA/EIT provides representations of adversary missile capabilities based on best available intelligence information and develops, coordinates, and baselines BMDS-level targets and countermeasures requirements to define target capabilities that support BMDS flight test objectives.

9) MDA Engineering Team - Industry (MET-I)

The system-level detailed requirements for systems engineering will be executed by the Advisory and Assistance Services (A&AS) (or TEAMS) contractors as part of the Missile Defense National Team (MDNT) construct known as the MET-I. The MET-I construct requires extensive collaboration and integration of products from several components, industry, UARCs, FFRDCs, Government, and A&AS teams.

A firewall has been established to prevent conflict of interest within the MET-I, protect proprietary information, and ensure the integrity of future competitions. The MET-I A&AS teams lead efforts inside and outside the firewall. Inside the firewall, the A&AS teams perform as an integral component of the collaborative MET-I with the major defense contractor team members. Outside the firewall, the A&AS teams assist MDA/DE with executing Government-assigned BMDS level analysis, preparing documentation, and conducting or participating in reviews. All MET-I personnel are required to sign a non-disclosure agreement, and the information infrastructure includes hardware protection and procedures to protect MET-I proprietary and sensitive information.

b. Advanced Technology Program Office (MDA/DV)

The Program Executive (PE) for Advanced Technology (MDA/DV) identifies innovative concepts and technological changes that can be applied across the BMDS to outpace the threat, improve system performance and reliability, reduce risk, lower life-cycle costs, and leverage technology investments of other DoD organizations, industry, and other Government agencies and international partners. The DV PE works closely with MDA/DE to plan, assess, and define future capabilities and with the programs to transition for product development.

c. Global Deployment Program Office (MDA/GD)

The Global Deployment Program Office conducts siting, site development, system deployment, weapon system integration, and the Host Nation coordination of assigned BMDS deployments. MDA/GD teams with and synchronizes the efforts of the MDA, foreign nations, DoD, CCMDs, service components, and construction agents to support successful deployment of BMDS capabilities. MDA/GD integrates MDA products and services through the Global Deployment Integration Task Force (GDITF), existing MDA processes, and Geographic Combatant Commander (GCC) relationships to deliver BMD capability.

d. Ground-Based Midcourse Defense Program Office (MDA/GM)

Ground-based Midcourse Defense (GM) is an element of the BMDS deployed in Alaska and California designed to defend the U.S. homeland against a limited attack of intermediate-to-intercontinental range ballistic missiles during the exo-atmospheric midcourse phase of flight. The GM system consists of fire control, interceptors, and associated communications and support assets. The GM ground system consists of the GM Fire Control (GFC), Test Exerciser (TEx), In-Flight Interceptor Communication Systems (IFICS) Data Terminal (IDT), GM Communications Network (GCN), External Systems Interface (ESI), launch support systems (including Command Launch Equipment (CLE)), and launch site components (including silo and missile field). The Ground Based Interceptor (GBI) system consists of boosters and Exo-Atmospheric Kill Vehicles (EKVs).

e. Targets and Countermeasures Program Office (MDA/TC)

The Targets and Countermeasures Program Office (MDA/TC) provides threat-representative, capability-based targets to support layered BMDS testing. Based on systems engineering assessments of realistic threat scenarios, the TC program acquires and launches BMDS targets with representative payloads to test, verify, and validate BMDS performance.

f. Sensors Program Office (MDA/SN)

The Sensors Program Office (MDA/SN) develops, tests, acquires, deploys, and sustains BMDS Radars including Long Range Discrimination Radar (LRDR), Army/Navy Transportable Radar Surveillance and Control Model-2 Radar (AN/TPY-2), Sea-Based X-Band Radar (SBX), Upgraded Early Warning Radars (UEWR), and COBRA DANE Radar (CD). MDA/SN activities include the acquisition of new radar systems; radar systems engineering and requirements development; radar hardware/software engineering; radar sustainment engineering; radar test planning, analysis, and performance assessment; radar tracking and discrimination improvements; and radar modeling and simulation capability development.

g. Terminal High Altitude Area Defense (THAAD) Project Office (MDA/TH)

THAAD is an Element of the BMDS providing both endo- and exo-atmospheric terminal phase interceptor capabilities to protect the U.S. homeland, forward deployed forces, friends, and Allies against short-to-medium range ballistic missiles. The THAAD system features a transportable capability (via C-17 aircraft) that enhances the ability of CCMDs to wage theater wars by providing flexible sensor and weapons coverage of defended areas.

1.3 Systems Engineering Forums

This effort requires participation in or assistance with the multiple system engineering forums including:

− Assessment Integrated Product Team (AIPT) − Director’s Program Review (DPR) − Blue Force Working Group (BFWG) − BMDS Data Analysis Working Group (BDAWG) − BMDS Requirements Working Group (BRWG) − Core Standards Working Group (CSWG) − Failure Review, Analysis, and Corrective Action System (FRACAS) − Infrastructure Working Group (IWG) − Interface Control Working Group (ICWG) − Interoperability Technical Analysis Group (ITAG) − BMDS Joint Reliability and Maintainability Evaluation Team (JRMET) − Mission Readiness Working Group (MRWG) − Operational Capacity Baseline (OCB) Working Group (OWG) − Planning Exercises (PLANEX) − Risk Management Working Group (RMWG) − System Engineering and Integration Council (SEIC) − Target Requirements Working Group (TRWG) − Test Baseline Working Group (TBWG) − Test Objectives Working Group (TOWG) − Test Resources Quarterly Review (TRQR) − Threat Systems Working Group (TSWG) − Verification Working Group (VWG)

The frequency of stated working group meetings, relationships to other organizations or groups, and structure are defined in working group charters. Required activities associated with this effort are identified in Section 3.

1.4 MDA Boards and Reviews

BMDS capabilities are matured using an incremental development process as described in the BMDS Systems Engineering Plan (SEP). The BMDS technical review strategy uses a decision process where integrated BMDS-level technical reviews follow capabilities compliance direction, per MDA Program Change Board (PCB) approval, to ensure coordinated implementation of capabilities across the BMDS. In accordance with (IAW) MDA Manual 3500.01-M, Ballistic Missile Defense System Change Management Process, the PCB and the Integration and Synchronization Group (ISG) are the two bodies that have decision authority for BMDS changes. The PCB approves changes to the six BMDS baselines IAW MDA Instruction 5010.20-INS, Boards and Reviews. This effort includes requirements for systems engineering studies, analyses, and presentations for MDA boards and reviews; which include, but are not limited to, the Acquisition Strategy Panel and/or Board (ASP/ASB), Executive Management Board (EMB), ISG, and PCB.

2. Data Rights

The contractor shall comply with Government data rights IAW the Defense Federal Acquisition Regulations Supplement (DFARS), as identified below in the PWS and incorporated in the contract:

All Technical Data (TD) and Computer Software (CS), algorithms and related models, (see DFARS 252.227-7013 and 252.227-7014) to be produced or developed under this contract shall be delivered to the Government with unlimited data rights. The TD and models shall be delivered to the contracting officer in its entirety at any point during the Period of Performance (PoP) of this contract upon written request of the contracting officer or by the end of the contract. The TD and models are to be developed with only Government funds.

Do not use open source computer software unless prior written approval is received from the contracting officer. All copyrights for updated and newly developed TD and models will be assigned to the Government (see DFARS 252.227-7020, incorporated herein).

3. Performance Objectives and Detailed Requirements

Table 3.1 below is the Performance Objectives Index outlining the objectives to be performed IAW this PWS. The Performance Objectives (POs) align with the MDA Systems Engineering “V” shown in Figure 1.1. Required products for each objective shown in Table

3.1 are included.

Performance Objective Index Location

1. Performance Objective #1: BMDS Planning and Architecture Development Dahlgren, VA (DHL);

National Capitol Region (NCR);

Huntsville, AL (HSV)

2. Performance Objective #2: BMDS Technology Development NCR; HSV

3. Performance Objective #3: BMDS Design and Technical Baseline Establishment NCR; HSV

4. Performance Objective #4: BMDS Test and Verification NCR; HSV

5. Performance Objective #5: BMDS Capability and Architecture Assessment NCR; HSV

6. Performance Objective #6: BMDS Delivery NCR; HSV

7. Performance Objective #7: Product Office Systems Engineering NCR; HSV

8. Performance Objective #8: Engineering Functional Management Colorado Springs, CO (COS);

NCR; HSV

9. Performance Objective #9: Modeling and Simulation COS; NCR; HSV

10. Performance Objective #10: Foreign Military Sales Weapon Systems Support NCR; HSV

Table 3.1: Performance Objectives

3.1 Performance Objective #1: BMDS Planning and Architecture Development

The stakeholders for this PO are DE/B, EBA, EBC, DVR, GD, and TH.

Task Details: The contractor shall assist in the analysis and development of requirements for integrated air and missile defense, and assist with development of an integrated BMDS architecture roadmap to describe future BMDS capabilities. BMDS architecture analysis and development includes planning, conducting trade studies, and evaluating alternatives, future concepts, and advanced technology development. The current and planned BMDS architectures consider prioritized capability requirements for the BMDS and technologies to address the requirements.

• Key Products (as required): Engineering End-of-Week Status (EBA, EBC, DVR);

Weekly Activity Reports (EBA, EBC, DVR, TH)

a. Assist with development of an integrated BMDS architecture roadmap that describes future BMDS capabilities, and accounts for the integration of IAMD with the BMDS.

[Stakeholders: DE/B, EBA, DVR, TH]

• Key Products (as required): Engineering End-of-Week Status (EBA, EBC, DVR);

Weekly Activity Reports (EBA, EBC, DVR, TH); BMD System Strategic Architecture Roadmap (EBA)

1) Conduct BMDS analysis planning, threat to capability gap analysis, concept alternatives trade studies, advanced technology development prioritization, and initial requirements development. [Stakeholders: DE/B, EBA]

2) Generate, identify, define, develop, and analyze new and/or modified sensor, weapon

(air-, land-, and sea-based), and Command and Control, Battle Management, and Communications (C2BMC) system concepts to develop BMD System Integrated Architectures to close gaps and shortfalls in baseline integrated BMDS capabilities against evolving adversary capabilities. [Stakeholders: DE/B, EBA]

• Key Products (as required): BMD System Architecture Briefings (DE/B);

Architecture Analysis Parameters, Briefings, and Engineering Reports (DE/B)

3) Define and document new and/or modified system concept technical details for key subsystem or component performance parameters within the integrated BMDS architecture. [Stakeholder: DE/B]

4) Assist with developing performance requirements for integration of Gun-Based

Defense Systems (GBDS) with the BMDS, and support GBDS technical discussions and meetings.

[Stakeholder: DE/B]

• Key Products (as required): Initial Requirements Document (DE/B)

b. Analyze and document the basis for technical performance parameter selections for higher-level integrated BMDS architecture analysis. [Stakeholders: DE/B, EBA]

• Key Products (as required): Architecture Analysis Parameters, Briefings, and

Engineering Reports (DE/B)

c. Conduct analyses, report results, and document findings of joint studies for the Engineering Directorate (MDA/DE) and external partners (e.g., Homeland Defense BMDS Analysis jointly executed with the Joint Staff). [Stakeholders: DE/B, EBA]

• Key Products (as required): DE-Directed Trade Study Analyses, Briefings, Reports, and Memorandums (DE/B)

1) Support Special Program for Missile Defeat (SPMD) architecture development, concepts and analyses, and test CONOPS and utilization. Provide systems engineering support including definition and analyses of system-level requirements, capability, system analyses, integration and interfaces, system assessment, CCMD interface, models and simulation, and technology investment recommendations.

[Stakeholder: EBA]

• Key Product(s): Analyses (EBA); Assessments (EBA); Concept and Functional

Description Updates (EBA); Plans (EBA); Roadmaps (EBA); Briefings / Briefing Materials (EBA); White Papers (EBA); Test Plans (EBA); Test Objectives (EBA); Test Requirements (EBA)

d. Evaluate, identify, assess, and document impacts to program baselines for system-level architectural changes. [Stakeholders: EBA, GD]

• Key Products (as required): System Level Architectural Change Assessments (GD)

1) Independently analyze BMDS programs and conduct Technical Interchange Meetings

(TIMs) with external offices, organizations, departments, and other agencies, including the Joint Functional Component Command - Integrated Missile Defense (JFCC-IMD), Operational Test Agency (OTA), Missile and Space Intelligence Center (MSIC), and National Air and Space Intelligence Center (NASIC). [Stakeholder:

DE/B]

e. Define alternative architectures, analyze their effectiveness, recommend improvements, and document results. [Stakeholders: DE/B, EBA]

• Key Products (as required): Architecture Effectiveness & Alternatives White Paper

(DE/B)

1) Assist in planning, structuring, executing, documenting, and reporting studies and analyses of alternatives for future BMDS concepts and capabilities. [Stakeholders:

DE/B, EBA]

2) Support analysis and definition of future BMDS performance gaps. [Stakeholders:

DE/B, EBA]

3) Assess BMDS technical performance for operationally realistic theater regional threats. [Stakeholder: EBA]

f. Develop and update Initial Requirements Documents (IRDs) based on gap analyses, concept assessment, trade studies, alternative studies, and technology development activities. [Stakeholders: EBA, DVR]

• Key Products (as required): IRDs (EBA, DVR)

1) Conduct analyses and comparative trade studies for BMDS Architecture Roadmap and IRD development. Conducting rapid architectural level BMDS performance analysis may require the WILMA modeling suite of tools, which consists of the WILMA models and simulation suites and a supporting team of WILMA analysts and developers provided by the Government. Access to the WILMA model will be granted through designated Government computers. [Stakeholders: EBA, DVR]

• Key Products (as required): Technology Assessments (DVR)

2) Collaborate with the operational community, including the JFCC-IMD, U.S. Strategic

Command (USSTRATCOM), Joint Integrated Air and Missile Defense Organization (JIAMDO), and U.S. Northern Command (USNORTHCOM) to identify operational capability needs and develop Concepts of Operations (CONOPS) and associated Configuration Definition Documents (CDDs) for the BMD component of IAMD. [Stakeholder: DE/B]

• Key Products (as required): Briefings, Reports, and Memorandums (DE/B)

3) Collaborate with the operational community, including JIAMDO, USSTRATCOM, and other unified combatant commands as appropriate to identify operational capability needs for IAMD. This effort shall include the development of key products such as the IAMD roadmap, CONOPS, capabilities and benefits assessments, gap analyses, and development of other operational requirements documents as required.

[Stakeholder: DE/B]

• Key Products (as required): Briefings, Reports, and Memorandums (DE/B)

g. Identify and recommend changes to functional and performance requirements for integration of IAMD with the BMDS. [Stakeholders: DE/B, TH]

• Key Products (as required): Element Specification Change Reports (TH)

1) Assess potential changes to current BMDS requirements to accommodate integration of the BMDS into IAMD. This effort will require analyses and comparative trade studies, and will support development of products including IAMD system architecture, recommended changes to BMDS functional requirements, IAMD roadmap, capability gap analyses, and other trade studies as required. [Stakeholder:

DE/B]

2) Prepare plans, analyses, assessments, schedules, papers, metrics, guides, minutes, synopses, reports, and briefings for integration of BMDS elements into IAMD.

[Stakeholder: TH]

• Key Products (as required): Weekly Activity Reports (TH)

3) Participate in working groups, Integrated Product Teams (IPTs), meetings, reviews, panels, boards, and conferences for integration of BMDS elements into IAMD.

• Key Products (as required): Weekly Activity Reports (TH)

4) Conduct and/or review and assess system engineering trades analyses utilizing models and simulations to determine and document performance levels to support follow-on performance requirements activities to update BMDS TBL documentation for specifying integration of IAMD with the BMDS. [Stakeholder: DE/B]

5) Analyze BMDS program characteristics and features, such as content and format of track messages, sensor tasking, and communications protocols for integration into the emerging IAMD architecture. [Stakeholders: DE/B, TH]

6) Conduct independent studies, identify architecture solutions, and recommend BMDS architecture modifications for IAMD requirements. [Stakeholder: DE/B]

7) Modify and/or update MDA or other agency documentation and/or artifacts, including the BMDS Achievable Capabilities List (ACL) and BMD Report (BMDR) for integration of IAMD with the BMDS. [Stakeholders: EBA, TH]

h. Participate in program and technical efforts, including technology demonstrations, risk reduction tests, and transition planning for future capabilities and emerging technologies not assigned to an MDA product office. [Stakeholders: DE/B, DVR]

• Key Products (as required): Future Capabilities Transition Plans (DVR)

1) Prepare technology transfer plans for technologies transitioning to BMDS programs.

[Stakeholder: DVR]

• Key Products (as required): Technology Transfer Plan (DVR)

2) Prepare an events calendar, including technology transition timelines and related activities from other directorates and programs for future capability programs.

• Key Product (as required): Event Calendar (DVR)

3) Monitor program operations for issues in technology development, report activity progress toward completion, and adjudicate issues for future capability programs.

• Key Products (as required): Information and Decision Briefings (DVR)

4) Analyze capability gaps, support resource planning with BMDS programs, and prepare resource planning meeting minutes and/or synopses for advanced technology efforts. [Stakeholder: DVR]

• Key Products (as required): Gap Analysis Summary Advanced Technology

(DVR); Meeting Synopsis (DVR)

5) Recommend Integrated Experiments Campaign Requirements Document and Configuration Management Plan improvements for technical adequacy and completeness, and develop risk management and risk mitigation plans. [Stakeholder:

DVR]

• Key Products (as required): Integrated Experiments Campaign Requirements

Document(s) Recommendations (DVR); Configuration Management Plan Recommendations (DVR); Risk Management Plan (DVR); Risk Mitigation Plan

(DVR)

6) Participate in research venues and related meetings, prepare meeting minutes or synopses, evaluate relevance and value to BMD systems, and recommend responses to inquiries and information briefings for emerging technology and research.

• Key Products (as required): Meeting Synopses (DVR)

7) Review planning documents for compliance with concept documentation, issue resolution, and assessments of technology development test events. [Stakeholder:

DVR]

• Key Product (as required): Requirements Management Plan and Schedule (DVR)

8) Prepare agendas, briefings, and minutes and/or synopses for future capability engineering reviews, milestone decision meetings, and baseline reviews of technology development programs. [Stakeholders: EBA, EBC, DVR]

• Key Products (as required): Program Executive Review Monthly Assessment

Data (DVR); Program Executive Review Quarterly Assessment Data (EBA, EBC); Meeting Agendas and Minutes (EBA, EBC, DVR); Meeting Synopses (DVR); Briefings / Briefing Materials (EBA, EBC, DVR)

9) Translate technical analyses, data, and descriptions into graphic formats compatible with Government software programs, and edit Microsoft PowerPoint and specialized space system graphics for program overview briefings. [Stakeholder: DVR]

• Key Products (as required): Program Overview Briefing Updates (DVR)

10) Prepare white papers with findings for ASP and/or ASB engineering reviews.

• Key Products (as required): ASP White Paper (DVR); ASB White Papers (DVR)

11) Recommend assessment metrics and summarize findings for technical trends assessments. [Stakeholder: DVR]

• Key Products (as required): Technical Assessment Metrics Recommendations

(DVR); Technical Insight Summary (DVR)

12) Coordinate with the Technical Intelligence Directorate (MDA/DE/I) to document engineering assessment findings and update the Advanced Technology Security Classification Guide (SCG) for BMDS protection systems designed to deny access, define elements of critical technologies program information, and prevent inadvertent disclosure of leading edge technology to foreign interests. [Stakeholder: DVR]

• Key Products (as required): Security Classification Guide Updates (DVR)

i. Assist with program and technical efforts for SAPs. [Stakeholders: DE/B, EBA, EBC,

1) Obtain required clearances for personnel assigned to SAPs. [Stakeholders: DE/B, EBA, EBC, DVR]

2) Analyze, assess, and assist in the execution of MDA SAPs integrated with the BMDS architecture for overall contributions to BMDS capabilities. [Stakeholder: EBA]

3) Analyze, assess, and assist in the production of SAP information, which contributes to the development of IAMD capability increments, concepts, and performance requirements. [Stakeholders: DE/B, EBA]

4) Prepare technical data, coordinate products, and secure approval for internal Agency and external SAP reports, briefings, and associated documentation. [Stakeholders:

EBA, EBC, DVR]

• Key Products (as required): Reports (DVR, EBC); Briefings / Briefing Materials

(EBA, EBC, DVR)

5) Prepare SAP presentations for Agency panels and boards. [Stakeholders: EBA, EBC,

• Key Products (as required): Reports (DVR); Briefings / Briefing Materials (EBC, DVR)

6) Prepare SAP technical data, information, and recommendations for responses to OSD Oversight Committee and Congressional inquiries. [Stakeholders: EBA, EBC, DVR]

• Key Products (as required): Reports (EBC, DVR); Briefings / Briefing Materials

7) Plan and monitor SAP Information Technology (IT) equipment implementation and access for program intent. [Stakeholder: DE/B]

j. Participate in technical reviews; assess BMDS adversary capabilities, conceptual countermeasures, risk assessments, and mitigation approaches; and plan, schedule, and conduct meetings for the BMDS countermeasures mitigation program. [Stakeholders:

DE/B, EBC]

• Key Products (as required): Risk Assessments and Reports (EBC)

1) Prepare plans, analyses, assessments, schedules, papers, metrics, guides, minutes, synopsis, reports, and briefings for the BMDS countermeasures mitigation program.

[Stakeholder: EBC]

• Key Products (as required): Monthly Project Quad Charts (EBC)

2) Participate in working groups, IPTs, meetings, reviews, panels, boards, and conferences for the BMDS countermeasures mitigation program. [Stakeholder: EBC]

• Key Products (as required): Meeting Synopses (EBC)

3) Draft SAP working papers for the BMDS countermeasures mitigation program.

[Stakeholders: DE/B, EBC]

• Key Products (as required): SAP Working Papers (EBC)

4) Coordinate with the Acquisition Directorate (MDA/DA) and MDA Elements to prepare acquisition documents, create artifacts, and execute technical content for the BMDS countermeasures mitigation program. [Stakeholders: DE/B, EBC]

• Key Products (as required): Acquisition Documents and Artifacts (EBC)

5) Develop, update, and execute SAP plans, operational procedures, classification guides, and other implementing guides for the BMDS countermeasures mitigation program. [Stakeholders: DE/B, EBC]

• Key Products (as required): Security Classification Guide Updates (EBC)

6) Participate in SAP security classification and technology protection panels for the

BMDS countermeasures mitigation program. [Stakeholders: DE/B, EBC]

• Key Products (as required): Panel Synopses (EBC)

7) Identify critical program information, leading technology, and the application of general security guidelines for specific technologies. [Stakeholders: DE/B, EBC]

• Key Products (as required): Briefing Materials (EBC)

8) Facilitate element integration and engineering of the BMDS countermeasures mitigation program for BMDS enhancement. Personnel must be eligible for required SAP accesses. [Stakeholder: DE/B]

9) Develop conceptual descriptions of adversary capabilities and countermeasure concepts, and review proposed BMDS architectures for the BMDS countermeasures mitigation program. [Stakeholder: DE/B]

10) Develop technical plans and description documents for countermeasure mitigation, advanced discrimination concepts, and integration engineering activities.

11) Recommend countermeasure mitigations for MDA security classification and technology protection panels. [Stakeholder: DE/B]

12) Recommend written responses for classification policy change proposals.

13) Review and edit communications to support senior leadership; support staffing actions and coordination for e-taskers, working groups, and special requests; and provide staffing process controls to ensure deadlines are met. [Stakeholders: DE/B, EBC]

• Key Products (as required): Briefings (EBC); Staff Packages (EBC)

k. Identify integration and interface issues and propose and review potential solutions for

Plan Phase technical reviews and analyses, including trade studies. [Stakeholders: DE/B, EBA, DVR]

• Key Products (as required): Special Study / Trade Study Analysis Reports or

Briefings (DVR) synopses, reports, and briefings. [Stakeholder: EBA] conferences. [Stakeholder: EBA]

3) Monitor E-Taskers, liaise with E-Tasker managers and staff, and prepare weekly staff meeting charts and activity reports for accomplishments, activities status, and program status. [Stakeholders: DE/B, EBA]

4) Prepare schedules and briefings, and develop agendas for meetings including IAMD.

[Stakeholder: EBA]

• Key Products (as required): Briefings, Reports, and Memorandums (EBA)

l. Assist with program and technical efforts for advanced research. [Stakeholder: DVR] synopses, reports, and briefings to assist the Advanced Technology Program Executive develop a technology transfer plan to transition technologies to BMDS programs that aligns emerging technology research with element system engineering requirements. Assist MDA/DE/I with engineering assessments of the BMDS protection systems, which are designed to deny access to defined elements of critical technologies program information and to prevent inadvertent disclosure of leading edge technology to foreign interests. [Stakeholder: DVR] conferences to support emerging technologies from research venues to respond to inquiries and information briefings, perform independent evaluation of relevancy and value to BMD systems, perform gap analyses, and support MDA Directorates in planning resources to support the advanced technology programs. [Stakeholder:

DVR]

• Key Products (as required): Technology Assessments for Broad Agency

Announcements (BAAs) (DVR); White Papers (DVR); Purchase Request (PR) Approval Documents (DVR)

3) Assist the Advanced Research office identify technology needs from MDA organizations. [Stakeholder: DVR]

• Key Products (as required): Technology Assessments for BAAs (DVR); White

Papers (DVR); PR Approval Documents (DVR)

4) Participate in advanced research with accredited domestic and foreign universities;

prepare briefings, reports, program plans, and test plans; prepare meeting minutes and/or synopses and action items; and track actions to closure for technologies, including fiber lasers, Electro-Optic (EO)/Infrared (IR) sensors, materials, simulation tools, rocket motors, and propellants. [Stakeholder: DVR]

• Key Products (as required): Domestic/International University Research Program

Review Summary (DVR); Meeting Synopsis (DVR); Reports (DVR); Briefings / Briefing Materials (DVR)

5) Identify and document MDA technology needs; participate in meetings and conferences; and research and review technical papers and articles on relevant technologies and state-of-the-art technical areas for advanced research. [Stakeholder:

DVR]

• Key Product (as required): Advanced Research to Identify Technology Needs

Summary (DVR)

6) Develop and maintain internal and external Government contacts for emerging technology knowledge advancement in each technical area, including radar systems, lasers and EO systems, active/passive IR sensor systems, computer science signal and data processing, mathematics probability and decision theory, physics, chemistry and materials, mechanical and aerospace engineering, battle management/command and control. [Stakeholder: DVR]

7) Prepare an annual briefing and coordinate with technology researchers and MDA offices for advanced research. [Stakeholder: DVR]

• Key Products (as required): Technology Researchers Coordination Review

Summary (DVR); Briefings / Briefing Materials (DVR); Draft Memo for Record

8) Prepare Memorandums for Record (MFRs) and present oral reports for technology researchers’ coordination sessions and contacts with other sources. [Stakeholder:

DVR]

• Key Products (as required): Briefings / Briefing Materials (DVR); Draft Memo for Record (DVR)

9) Investigate areas for synergy between different projects and recommend the best return on investment for agency partnerships. [Stakeholder: DVR]

• Key Product (as required): Technology Researchers Coordination Review

10) Participate in technology meetings, recommend improvements, prepare staff-level briefings, prepare reports, and monitor compliance with technical requirements for Advanced Research programs. [Stakeholder: DVR]

11) Define, draft, review, update, coordinate, monitor, and evaluate technology transfer and product or element transition plans; coordinate transfer plan updates and secure approval; and identify and define technology maturity requirements for transition to product development at Technology Readiness Level (TRL) defined by policy.

[Stakeholder: DVR]

12) Monitor threat, system, and program architecture and policy for impacts to Computer Network Defense and IA. [Stakeholder: DVR]

13) Develop Information System Security Engineering (ISSE) requirements and update program requirements for identified vulnerabilities. [Stakeholder: DVR]

m. Recommend project guidelines and identify project product requirements for program offices and MDA technical areas of interest. [Stakeholder: DVR]

1) Assist with test plan and project schedule reviews and prepare technology relevance and maturity documents for special interest projects including specific technology projects. [Stakeholder: DVR]

• Key Products (as required): Reports (DVR)

2) Prepare and present briefings, and identify and maintain internal agency contacts for special interest projects. [Stakeholder: DVR]

• Key Products (as required): Briefings / Briefing Materials (DVR)

3) Evaluate technology development and compliance with requirements, identify and propose project changes, and document results in a MFR for funded special interest

• Key Products (as required): Draft Memo for Record (DVR)

4) Prepare, coordinate, and secure approval of briefings; and update the overview briefing for special interest projects. [Stakeholder: DVR]

• Key Products (as required): Briefings / Briefing Materials (DVR)

5) Prepare status reports and provide inputs to tasking responses for special interest

• Key Products (as required): Status Reports (DVR)

n. Conduct analysis to assess planned capabilities against the Warfighter's Prioritized

Capabilities Lists (PCLs) in order to develop the ACL and support description of its content in appropriate warfighter and other user community forums. [Stakeholder: EBA]

• Key Products (as required): Achievable Capabilities List (EBA); ACL Briefings

(EBA)

1) Participate in operational and user community studies, related studies, war games, exercises, training, concepts of operations, and reviews; analyze feedback; provide recommendations; and coordinate and secure approval for the ACL. [Stakeholder:

EBA]

2) Analyze user-community feedback and recommend solutions for issues identified with the ACL. [Stakeholder: EBA]

3) Participate in, and prepare agendas, white papers, MFRs and briefings for operational and user community-focused meetings, IPTs, and reviews. [Stakeholder: EBA]

• Key Products (as required): White Papers (EBA); Draft Memo for Record (EBA)

o. Assist with technical and export control reviews for technology project papers and briefings, technical papers and articles submitted for publication approval and public release of information. [Stakeholder: DVR]

• Key Products (as required): Technical and Export Control Reviews and Written

Assessments (DVR)

1) Assist with technical and export…