Attachment J-01 - IRES Contract SOO (A0005).docx

DOCX document 191 KB Posted

Attached to
MDA IT Operations & Engineering Solutions (MIOES) - CANCELED Federal contract opportunity
Solicitation number
HQ0857-MIOES-ZA
Issued by
DOD Missile Defense Agency

View the file

Other files for this federal contract opportunity

Other files attached to MDA IT Operations & Engineering Solutions (MIOES) - CANCELED, newest first.
File Type Posted
MIOES TO Phase-in Schedule (Preliminary).pptx PPTX presentation
MDA 5013.06 - Source Selection Procedures.pdf PDF
MIOES MDIOC Facility Operations and Sustainment PWS DRFP Inc3.pdf PDF
Attachment L-5 MIOES Question Matrix DRFP Inc3.xlsx XLSX spreadsheet
MIOES 1-on-1 Participant List and Topics.xlsx XLSX spreadsheet
MIOES DRFP Inc1 CONSOLIDATED QandAs.xlsx XLSX spreadsheet
MIOES Industry Day Overview and Instructions.docx DOCX document
Attachment L-3 OCI Analysis Disclosure Form DRFP Inc2.pdf PDF
MIOES LCAT Table DRFP Inc2.xlsx XLSX spreadsheet
MIOES Section M DRFP Inc2.docx DOCX document
MIOES Acquisition Strategy Summary - 14 June DRAFT RFP.pdf PDF
MIOES Industry Monthly CSSP - June.pptx PPTX presentation
MIOES Industry Monthly Chargeback Showback - May.pptx PPTX presentation
23F7300_PWS.pdf PDF
MIOES SE Overview (15 Feb 24).pptx PPTX presentation
22F8900_PWS.pdf PDF
23F3100_PWS.pdf PDF
23F8600_PWS.pdf PDF
22F8004_PWS.pdf PDF
22F8003_PWS.pdf PDF
23F4100_PWS.pdf PDF
MIOES Industry Monthly April 2024.pdf PDF
20230405-MIOES_Industry_Day_POC.xlsx XLSX spreadsheet
IRES_AttchJ-01_Encl1_HLO.docx DOCX document
20230103-MIOES_Industry_Day_POC.xlsx XLSX spreadsheet
20221110-MIOES_Industry_Day_POC.xlsx XLSX spreadsheet
Attachment J-03 - IRES Labor Category Descriptions.xlsx XLSX spreadsheet
Exhibit A - MDA Mandatory CDRLs.docx DOCX document
Exhibit B - IRES CDRLs.docx DOCX document
Attach L-06 - Client Authorization Letter.docx DOCX document
Attach L-11 - EITS SOO (A0005).docx DOCX document
Attach L-12 - FEO SOO (A0005).docx DOCX document
Attach L-16 - Cost Price WB 3 (A0003).xlsx XLSX spreadsheet
Section M (A0006).docx DOCX document
Attachment J-02 - IRES WBS and CSDR.pdf PDF
Attach L-02 - Team List.docx DOCX document
Attach L-05 - Consent Letter.docx DOCX document
Attach L-07 - PPQ (A0001).docx DOCX document
Attach L-14 - Cost Price WB 1 (A0001).xlsx XLSX spreadsheet
MIOES_Industry_Day_POC.xlsx XLSX spreadsheet
Sections A-K (A0007).pdf PDF
Attachment J-06 - PEIP.pdf PDF
Attachment J-07 - Compliance Documents List.docx DOCX document
Attach L-01 - Library Request Form v2.2.pdf PDF
Attach L-03 - OCI Disclosure Form v2.0 (Extended).pdf PDF
Attach L-04 - CDM.xlsx XLSX spreadsheet
Attach L-08 - Transition SOO (A0002).docx DOCX document
Attach L-09 - IRES TO Award-Modification Process.docx DOCX document
Attach L-13 - IRES ERI Data.xlsx XLSX spreadsheet
Attach L-15 - Cost Price WB 2 (A0001).xlsx XLSX spreadsheet
Show all 50

MDA IT Operations & Engineering Solutions (MIOES) - CANCELED has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Attachment J-01:

Integrated Research & Development for Enterprise Solutions (IRES) Contract Statement of Objectives (SOO)

H95001-15-R-0001-0005 Attachment J-01

Sep 1 2016 Change History

Document Versions
Date
Significant/Major Changes

Original

Sep 1, 2016 Table of Contents

1.0Mission1
1.1Missile Defense Agency (MDA) Mission1
1.2Integrated Research & Development for Enterprise Solutions (IRES) Mission1
2.0Purpose and Program Goals / Desired Attributes2
2.1Purpose2
2.2Program Goals / Desired Attributes2
3.0Scope3
3.1IRES Systems Engineering and Program Integration (SE&PI)3
3.2BMDS Mission Operations3
3.3BMDS Testing3
3.4Wargames and Exercises4
3.5Modeling and Simulation4
3.6Enterprise Communications and Information Technology Environment4
3.7Operation of Facility Infrastructure4
4.0Service Summary Items5
5.0Deliverables5
6.0Government Furnished Equipment/Government Furnished Information (GFE/GFI)5
7.0Special Requirements5
7.1Cost and Software Data Reporting (CSDR)5
7.2Supply Chain Risk Management (SCRM)6
7.3Cybersecurity6
7.4Property Management and Accountability6
7.5Network Access7
7.6Location and Hours of Work7
7.7Security7
7.7.2Operations Security10
7.8Program Protection10
8.0Applicable Directives/Regulations11
9.0Revisions and Updates11
Enclosure 1 – High Level Objectives and Capabilities Descriptions and Legacy Requirements11
Sep 1, 2016Page i
1.0Mission
1.1Missile Defense Agency (MDA) Mission

To develop and deliver a layered Ballistic Missile Defense System (BMDS) to defend the United States, its deployed forces, allies, and friends from missile defense attacks of all ranges in all phases of flight.

MDA works with the Combatant Commanders to ensure development of a robust BMDS technology and development program that addresses the challenges of an ever-evolving threat. MDA is also steadily increasing international cooperation by supporting mutual security interests in missile defense.

The MDA is committed to maximizing the mission assurance and cost effectiveness of our management and operations through continuous process improvement.

1.2 Integrated Research & Development for Enterprise Solutions (IRES) Mission The IRES contract provides integrated solutions supporting concurrent test, training, and operations (CTTO) within the Missile Defense Integration and Operations Center (MDIOC) mission execution platform and enterprise communications and information technology (IT) environment.

In order to achieve the objectives of the MDA in developing, testing, and fielding the BMDS, the Agency must be able to provide integration of multiple disparate capabilities while simultaneously synchronizing unrelated requirements across a broad spectrum of stakeholders all vying for the same shared resources. The contract must provide MDA the agility, optimized solutions, and synchronization of technical capabilities to rapidly respond to real-world threats and emerging BMDS technologies supported within the CTTO environment hosted in the MDIOC. The contract solutions and execution must address the following:

· Deconfliction of concurrent events and critical assets, maintaining positive configuration control, and rapid resource reprioritization are fundamental to mission success.

· The contractor’s ability to synchronize capabilities, schedules, and priorities across the program is a key risk mitigation measure for integration and execution of events that support national defense.

· Integration of work activities across BMDS Mission Operations, BMDS Testing, Wargames and Exercises, Modeling and Simulation, Enterprise Communications and IT Environment, and Operation of Facility Infrastructure ensures integrity of event architectures and standardizes delivery of technical capabilities.

To enable stakeholders to achieve MDA mission by providing an agile, multi-purpose, capabilities-based contract to execute the following High Level Objectives (HLOs):

· IRES Systems Engineering and Program Integration

· BMDS Mission Operations

· BMDS Testing

· Wargames and Exercises

· Modeling and Simulation

· Enterprise Communications and Information Technology Environment

· Operation of Facility Infrastructure

2.0Purpose and Program Goals / Desired Attributes
2.1Purpose

The purpose of this Statement of Objectives (SOO) is to provide the procurement framework and focus all parties on implementation of a performance-based contract execution for delivery of quality products and services.

2.2 Program Goals / Desired Attributes

· Performance excellence achieved by an integrated approach to developing solutions that result in delivery of ever-improving value to customers and stakeholders in accordance with Federal and DoD directives.

· Best in breed performance resulting in efficiencies, adoption and incorporation of industry best practices, and enhanced products, services or throughput.

· Solutions to stakeholder requirements that leverage initiatives and standards that result in reduced costs and/or enhance the product/service lifecycle.

· Efficiencies across customers and stakeholders are sought and achieved through analysis, innovation, and the sharing of information and knowledge.

· Workforce capacity is understood and optimized for effective performance.

· Compliant, efficient and transparent property control process(es).

· Ability to account for work performed under each high level objective, each product/project, as well as the business base (e.g., small business, SDB, WOSB, VOSB) performing the work.

· A high performing organization that cultivates an engaged workforce and systematically pursues ever-higher levels of overall organizational and individual performance.

· Integrated, aligned processes.

· Innovation is systematically incorporated into standard operating procedures resulting in tangible benefits to the government.

· Rapid implementation of new technologies and capabilities without introduction of risk(s) that cannot be mitigated.

· Performance measures or indicators that are tied to customer requirements.

3.0 Scope

IRES is an MDA-wide contract vehicle designed to enable the MDA mission; task orders issued under the contract will be directly or logically connected to the MDA mission and will be executed under the high level objectives identified below. (Reference Enclosure 1, “IRES High Level Objectives and Capabilities Descriptions and Legacy Requirements,” for additional details and historical information related to the IRES HLOs and capabilities. The content of this document is not intended to limit the scope of the IRES contract nor is it a guarantee of future requirements that will be fulfilled under the IRES contract.)

Although it is very difficult to forecast all CTTO activities or predict how missile defense will evolve, this contract must be capable of adapting to and supporting evolving and new CTTO requirements, missile defense elements, and missions executed by or through the MDIOC and the enterprise communications and IT environment.

3.1 IRES Systems Engineering and Program Integration (SE&PI)

Successful realization of a single IRES HLO cannot be achieved without thorough systems integration, program integration, and alignment (both schedule and priorities) with the other HLOs. The IRES SE&PI HLO provides de-confliction of critical assets, positive configuration control of test environments, and rapid reprioritization of resources. This HLO is essential to simultaneously and efficiently executing multiple stakeholder requirements that span multiple HLOs in a dynamic test, training, and operational environment. Develops, manages, and maintains Department of Defense Architecture Framework (DoDAF) data used in a Federal and Department of Defense (FEA, DODEA) compliant architectural repository for the IRES contract; renders multiple views of the capabilities delivered under the contract which guides the development of solutions that will meet customer requirements; integrates technical artifacts from disparate MDA contract activities into the Enterprise repository as necessary to satisfy holistic views of the enterprise environment.

3.2 BMDS Mission Operations

The MDIOC is host to numerous BMDS operational missions, operational test assets, and developmental and prototype systems. BMDS Mission Operations ensures visibility and awareness of the multiple operational readiness postures, delivers warfighter mission support, and provides satellite operations in support of BMDS testing. In addition, BMDS Mission Operations is responsible for Advanced Research activities and the development of prototype systems destined for fielding and maintenance in the operational BMDS architecture.

3.3 BMDS Testing

BMDS Testing is a continuous, evolutionary process that encompasses both developmental and operational activities to demonstrate the effectiveness, suitability, and survivability of the BMDS. BMDS Testing develops secure test architectures that integrate multiple enclaves and disparate test resources across the enterprise communications and IT environment in accordance with test event requirements to enable testing of the BMDS and its elements while ensuring appropriate cyber security protections are enabled for the protection of all test elements.

3.4 Wargames and Exercises

MDA requires the capability to engineer, integrate, and execute wargames and exercises to demonstrate current and future BMDS capabilities. Wargames and exercises are comprised of a wide range of activities from tabletop seminars to fully interactive, distributed wargames to multi-stakeholder, Combatant Commands (CCMD) sponsored exercises. Delivery of wargames and exercises originates from the MDIOC platform and leverages the enterprise communications and IT environment to connect participants and distribute data around the globe.

3.5 Modeling and Simulation

MDA requires a modeling and simulation capability to develop, deliver, and support MDA models and simulations with functionality as described in requirements specification. Models and simulations are integrated into BMDS Test architectures in a cooperative mission focused manner to ensure test architecture specifications are met. The M&S program supports (1) BMD system concept evaluation, (2) engineering development of the BMD system and its components, (3) BMD system verification and valuation, (4) credible assessment of system-level effectiveness and functionality, (5) warfighter/operator training, and (6) real-world operational analysis.

3.6 Enterprise Communications and Information Technology Environment MDA’s Enterprise Communications and IT Environment HLO is the integrating and enabling platform that (in conjunction with SE&PI processes) ensures the coordination and secure cyber operation of multiple network and technology enclaves servicing the MDA RDT&E and associated operational mission environments across MDA. The Enterprise Communications and IT Environment HLO provides critical communications and infrastructure used in the integration of BMDS elements in the development and fielding of BMDS capabilities. The Enterprise Communications and IT Environment HLO also provides the MDA administrative and general services IT environment necessary to conduct MDA business functions through the operations, maintenance, and sustainment of collaboration services, networks, cloud computing infrastructure, computer network defense, communications gateways, end user productivity hardware/software, and mobile devices.

3.7 Operation of Facility Infrastructure

The Operation of Facility Infrastructure HLO encompasses the people, processes, tools, and infrastructure necessary to support mission-critical BMDS and RDT&E operations within the MDIOC. This HLO provides rapid facility modifications (testbed/lab builds) to support MDA mission activities at the MDIOC and ensures the facility is operated, maintained, and sustained in a coordinated and synchronized manner to reduce impact and risk to operational and RDT&E missions.

4.0 Service Summary Items

Service Summary Items (SSIs) will be specified in individual task orders. In accordance with the IRES Performance Evaluation and Incentive Plan, SSIs 1 through 4 are common [required] on all task orders and will be assessed at the contract level (i.e., all task orders will receive the same rating – one fail all fail model).

SSI 5 (through n) [Technical Performance] will capture the specific task order Service Summary Items deemed essential to successful execution of the task order.

SSI #
Title
Weight / QPIs
SSI 1
Integration
10% / 10 QPIs
SSI 2
Small Business Utilization
5% / 5 QPIs
SSI 3
Customer Satisfaction
5% / 5 QPIs
SSI 4
CDRL / Proposal Timeliness
5% / 5 QPIs
SSI 5
Technical Performance
No greater than 75%

5.0 Deliverables

The Contract Data Requirements List (CDRLs) is provided in Exhibit A – MDA Mandatory CDRLs and Exhibit B – IRES CDRLs. Individual task orders will order/tailor CDRLs, as appropriate, to fulfill requirements.

6.0 Government Furnished Equipment/Government Furnished Information (GFE/GFI) Workforce working in government facilities will be provided:

· Office Furnishings: desk, chair, table/conference table, bookcase, file space, visitor chairs.

· Hardware/Software: contemporary office automation tools, personal computers with Microsoft Office Suite, common use access of printers (black and white and color), access to classified DoD network resources, as required, common use access of workstations on the ULAN and CLAN, common use access of email, common use access of the internet for professional use only.

· Communications: telephones, common use access to fax machines, and voice mail.

Specific GFE/GFI necessary for accomplishment of requirements will be identified under the task order(s).

7.0Special Requirements
7.1Cost and Software Data Reporting (CSDR)

The contractor shall systematically collect and report actual contract costs to provide DoD cost analysts with needed data to estimate future costs. Contractor reports shall be prepared in accordance with the instructions contained in the most recently approved versions of DI-FNCL-81565, DI-FNCL-81566, DI-FNCL-81567, and DI-FNCL-81765.

7.2 Supply Chain Risk Management (SCRM)

SCRM will be established to protect supplies purchased for or part of solutions developed to support MDA in accordance with DoD 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN). In accordance with DoD 5200.44, identify the risks to the supply chain and the risk management strategies they will employ to counter those risks, identify critical components and subcomponents in their system design and describe how they will ensure visibility into the supply chain and to ensure the integrity of those critical components and subcomponents. Processes will be established to verify critical function components received from suppliers are free from malicious code, counterfeit parts or unauthorized product substitution (e.g., seals, inspection, secure shipping, testing, etc.) in accordance with “NSA Guidance for Addressing Malicious Code Risk” dated 10 September 2006. Processes shall also address the appropriate controls to ensure their subcontractor’s plans comply with supply chain risk management requirements in accordance with DoD 5200.44 and Software Assurance Countermeasures in Program Protection Planning dated March 2014.

7.3 Cybersecurity

It is the Government’s objective for the contractor to:

· Identify, manage, verify, and validate Cybersecurity requirements in the same manner as all other program requirements;

· Integrate Cybersecurity considerations into program systems engineering and design processes, including risk management, SCRM;

· Provide support, source data, and analysis required to support the Government in obtaining system authorization in accordance with DoD Instruction 8510.01, Risk Management Framework;

· Provide Cybersecurity measures to secure, safeguard and protect controlled unclassified information from unauthorized access, disclosure, incident or compromise provided by or generated for the Government that transits or resides on any non-Government information technology system (prime and all sub-contractors);

· Integrate and support robust Cybersecurity testing in the Integrated Master Test Plan;

· Provide support, analysis of the MDA Cybersecurity insider threat program, computer network defense support program, and RMF efforts within the supported programs.

7.4 Property Management and Accountability

Accountability will be established and maintained for all property purchased, leased, developed, currently in development, or otherwise acquired by MDA for the asset’s entire lifecycle, from receipt to disposal.

7.5 Network Access

In accordance with DoDD 8140.01 and its interim implementation manual, DoD 8570.01-M, any individual requiring access to government information technology systems must complete Information Assurance Awareness training. In addition to the IA baseline training requirement for access, any personnel requiring privileged access must obtain appropriate Computing Environment (CE) certifications for the operating system(s) and/or security related tools/devices they support or operate. Compliance with the guidelines established in DoD 8570.01-M is mandatory irrespective of the Task Order on which the work is performed. Personnel performing IA functions on national security systems must also meet the Committee on National Security Systems training requirements. As reflected in DoD 8570.01-M paragraph C2.3.12, all personnel holding an approved IA baseline certification in fulfillment of the requirements of the Manual must release their certification information to the Department of Defense through the Defense Workforce Certification Application (DWCA): https://www.dmdc.osd.mil/appj/dwc/index.jsp

7.6 Location and Hours of Work

Specific workforce location constraints will be identified in task orders issued under the contract.

Altered work hours and workweeks may be necessary to support requirements scheduled during off-hours. Note: BMDS Test and Exercise support may require portions of the workforce schedule and/or place of performance to be realigned for the duration of the test and or exercise.

Weather or security closures of government facilities will be handled in accordance with the contractor's DCAA-approved accounting procedures and policies.

7.7 Security

All personnel must be in possession of at least an interim Secret security clearance to have unescorted access to areas within an MDA/Government facilities where performance is authorized (any location funded by and under the security cognizance of MDA is considered an MDA facility). Some work may require a Top Secret, Sensitive Compartmented Information, Special Access Program or Special Access Required clearances.

DD Forms 254: Overarching security requirements and Contractor access to classified information shall be as specified in the basic DD Form 254, which will be further identified in the DD Form 254 for each task order, as required. All contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable National Agency Check (NAC).

Access to the following Host Installations and Restricted areas may be required to execute the task orders issued under this contract:

7.7.1 Predominate MDA Facilities

Schriever AFB, CO and MDIOC (Primary work location).

Access to Schriever AFB (SAFB) is strictly controlled; to access the installation requires a sponsorship by a person assigned/employed on the installation for personnel who do not possess some form of current federal government issued identification. The MDIOC is located within a USAF restricted area on SAFB, contractor employees require at a minimum a National Agency Check Investigation (NACI) and a Visit Authorization Request (VAR) for issuance of a temporary or permanent badge that allows unescorted access to the restricted area. Contractors operating as visitor groups only may be issued a permanent badge for unescorted access if contract performance exceeds 90 consecutive days. The Commander may grant individuals access to the Restricted Area after the following has been completed: 1) the contractor completes the Standard Form (SF) 85P and it is submitted to Office of Personnel Management (OPM) for a National Agency Check Investigation (NACI); 2) a check of the Defense Clearance and Investigation Index (DCII) reveals no relevant, significant information which might preclude unescorted access; and 3) a check of the appropriate local records has been accomplished. Since access to the MDIOC is controlled, it is important to understand the potential impacts to the contractor(s) ability to accommodate/respond to requirement fluctuations (e.g., surge support, competing/overlapping schedules, etc.); this potential impact must be considered in all proposed solutions.

Redstone Arsenal, AL and MDA Controlled Space(s).

Access to Redstone Arsenal is strictly controlled; to access the post requires a sponsorship by a person assigned/employed on the post for personnel who do not possess some form of current federal government issued identification. MDA facilities are controlled areas and require a MDA-issued badge to gain unescorted entrance to any of the facilities. Unescorted access is granted to cleared MDA personnel and contractors and to other persons who, in the course of official business, have a current security clearance on file, a need to conduct MDA business, and having a need to know. Contract personnel are issued badges through COR and Security Managers. Contact MDA Security Operations Center for information and procedures pertaining to MDA controlled space(s).

Fort Greely, AK and Missile Defense Complex Restricted Area.

Access to Fort Greely Army Garrison (FGA) is strictly controlled; contractor employees must have a local government sponsor and will be required to pass a National Crime Information Center (NCIC) Criminal Background Check review prior to unescorted entry. Contractor employees that possess an interim Secret security clearance at a minimum will not be required to submit an NCIC criminal background check. Procedures and information pertaining to access is available by contacting the Fort Greely Installation Visitor Control Center. Additionally, the Missile Defense Complex (MDC) is a designated restricted area on FGA. Contractor employees requiring unescorted entry to the MDC must have an approved Visit Authorization Request on file, possess an interim Secret security clearance at a minimum and have local government approval. Contact MDA/GMSG (Ground-based Midcourse Defense Operations Support at FGA) Security Manager at for additional information on FGA restricted/control area access requirements.

Vandenberg AFB, CA and Ground-based Midcourse Defense (GMD) Restricted Areas.

Access to Vandenberg AFB is strictly controlled; to access the installation requires a sponsorship by a person assigned/employed on the installation for personnel who do not possess some form of current federal government issued identification. Contact the Security Forces Visitor Control Office for procedures and information pertaining to installation access. Additionally, GMD has restricted areas on Vandenberg AFB. Contractor employees require a National Agency Check Investigation (NACI) at a minimum for unescorted access to the GMD restricted area(s). Contractors operating as visitor groups only (contract performance exceeding 90 consecutive days) may be issued a permanent badge for unescorted access to the GMD restricted areas. Commanders may grant individuals access to the Restricted Area after the following has been completed: 1) the contractor completes the Standard Form (SF) 85P and it is submitted to Office of Personnel Management (OPM) for a National Agency Check Investigation (NACI); 2) a check of the Defense Clearance and Investigation Index (DCII) reveals no relevant, significant information which might preclude unescorted access; and 3) a check of the appropriate local records has been accomplished. Since access to the GMD operational areas is restricted, it is important to understand the potential impacts to the contractor(s) ability to accommodate/respond to requirement fluctuations (e.g., surge support, competing/overlapping schedules, etc.); this potential impact must be considered in all proposed solutions. Contact Security Forces at 805-606-1853 for procedures and information pertaining to restricted area access.

Naval Support Facility-Dahlgren, VA and MDA Controlled Space(s).

Access to Dahlgren is strictly controlled; to access the installation requires a visit request sponsored by a person assigned/employed on the installation at the Pass & Identification (ID) center for personnel who do not possess some form of current federal government issued identification. A picture ID and vehicle registration are required prior to the issuance of guest badge and a temporary car pass from the Pass & ID center for installation access. Contact the Dahlgren Visitor Control Office for procedures and information pertaining to installation access. MDA facilities are controlled areas and require a MDA-issued badge to gain unescorted entrance to any of the facilities. Unescorted access is granted to cleared MDA personnel and contractors and to other persons who, in the course of official business, have a current security clearance on file, a need to conduct MDA business, and having a need to know. Contract personnel are issued badges through COR and Security Managers. Contact MDA for procedures and information.

Ft. Belvoir, VA and MDA Headquarters Command Center.

Access to Ft. Belvoir is strictly controlled; to access the post requires a sponsorship memorandum at the visitor center by a person assigned/employed at the MDA Headquarters Command Center for personnel who do not possess some form of current federal government issued identification. Contact the US Army Garrison, Ft. Belvoir visitor center for information and procedures pertaining to post access. MDA Headquarters Command Center (HQCC) is a controlled area facility and requires a MDA-issued badge to gain unescorted access. Unescorted access is granted to cleared MDA personnel and contractors and to other persons who, in the course of official business, have a current security clearance on file, a need to conduct MDA business, and having a need to know. Contract personnel are issued badges through COR and Security Managers. Contact MDA HQCC Security Operations Center for information and procedures pertaining to MDA controlled space(s).

Pacific Missile Range Facility and Aegis Facility Access.

Access to Pacific Missile Range Facility (PMRF) is controlled; to access the installation requires a sponsorship by a person assigned/employed on the installation for personnel who do not possess some form of current federal government issued identification. It is strongly recommended you contact the Security Pass & ID Office for procedures and information pertaining to installation access. Due to the geographical location of PMRF MDA contractors supporting missions at that location will require prior Government approval for travel due to limited supporting resources.

Outside the United States, Puerto Rico, U.S. possessions and trust territories.

Classified performance will occur at various MDA and/or other government locations as directed by the Performance Work Statement, Statement of Work, or Statement of Objectives. The contractor shall abide by government security requirements per NISPOM 6-105c. The cognizant security office at the performance location is MDA or the host installation.

7.7.2 Operations Security

The contractor is required to apply Operations Security (OPSEC) to enhance protection of classified and unclassified critical information pursuant to DoD Directive 5205.02, DoD OPSEC Program; DoD 5205.02-M, OPSEC Program Manual; National Security Decision Directive Number 298, National Operations Security Program; MDA Instruction 5205.02, OPSEC Program; and supplementary instructions. In addition to the above access requirements, there is also annual training in the following: Antiterrorism Awareness (Level 1) training, Operational Security, and other security related training specific to the above work areas.

7.8 Program Protection

Critical Program information (CPI) and Critical Technologies (CT), will be identified by MDA, and protected by the contractor to the standards articulated in DoDI 5200.39, Critical Program Information (CPI) Protection within the Department of Defense, July 16, 2008, Incorporating Change 1, December 28, 2010 and DoD Instruction 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN), November 5, 2012 and implemented by a Program Protection Plan developed in conjunction with the MDA program offices associated with the task orders.

8.0 Applicable Directives/Regulations

Directives/regulations that are applicable to all task orders are identified in Attachment J-07, Compliance Documents. Tailoring, as necessary, may be done at the task order level.

All documentation delivered under this contract must comply with Section 508 of the Rehabilitation Act of 1973, as amended. 29 U.S.C. § 794 (d), § 794d. Electronic and information technology Subpart D — Information, Documentation, and Support 1194.41 Information, documentation, and support. Authority: 29 U.S.C. 794d.

9.0 Revisions and Updates

This document will be reviewed annually to ensure the service summary items, desired outcomes and performance attributes are relevant and reflect the needs of the Agency.

Enclosure 1 – High Level Objectives and Capabilities Descriptions and Legacy Requirements

Sep 1, 2016 Page 11 image2.emf

Attachment J-01, Encl 1 - HLO Capabilities Descriptions and Legacy Requirements.docx

Attachment J-01, Enclosure 1

Integrated Research & Development for Enterprise Solutions

High Level Objectives and Capabilities Descriptions and Legacy Requirements

May 10, 2016

Attachment J-01, Enclosure 1

This page intentionally blank

Preface

This document is designed to convey the potential scope and breadth of the Integrated Research and Development for Enterprise Solutions (IRES) contract based on task orders issued under the legacy contract. The content of this document is not intended to limit the scope of the IRES contract nor is it a guarantee of future requirements that will be fulfilled under the IRES contract.

Attachment J1, Enclosure 1

Page i

Attachment J1, Enclosure 1

Page ii

Table of Contents

1.0 IRES High Level Objectives 1

2.0 IRES Systems Engineering and Program Integation 3

3.0 BMDS Mission Operations 3

3.1 Infrastructure Readiness Posture 4

3.2 Warfighter Mission Support 4

3.3 Satellite Operations 6

4.0 BMDS Testing 6

4.1 Flight Test Support 6

4.2 Ground Test Execution 7

4.3 Performance Assessment Execution 8

5.0 Wargames and Exercises 8

5.1 Wargame Execution 8

5.2 Exercise Execution 9

6.0 Modeling and Simulation 10

6.1 Models and Simulations – Development 10

6.2 Models and Simulations – Maintenance / Sustainment 10

7.0 Enterprise Communications and Information Technology Environment 11

7.1 Architect, Design, and Implement Secure Communications and IT Services 11

7.2 Manage, Operate, and Maintain IT Services 12

7.3 Manage and Maintain Secure IT Infrastructure 13

7.4 Customer Interface and Support Services 13

8.0 Operation of Facility Infrastructure 14

8.1 Operate and Maintain Common-use Facility Infrastructure 14

8.2 MDIOC Facility Repair / Alteration 15

FOR OFFICIAL USE ONLY Page 0

Page iv

1.0 IRES High Level Objectives

High Level Objectives are the overarching performance areas that characterize the major components of work to be performed under IRES. Each HLO contains capabilities that further refine / define potential performance areas.

IRES High Level Objectives are:

· IRES Systems Engineering and Program Integration

· BMDS Mission Operations

· BMDS Testing

· Wargames and Exercises

· Modeling and Simulation

· Enterprise Communications and IT Environment

· Operation of Facility Infrastructure

Exhibit 1 aligns active task orders under the current contract, the Joint National Integration Center (JNIC) Research and Development Contract (JRDC), to the IRES HLOs and capabilities described in this document. Task order documents can be found in the IRES bidders’ library.

EXHIBIT 1. ACTIVE JRDC TASK ORDERS ALIGNED TO IRES HLOs / CAPABILITIES

2.0 IRES Systems Engineering and Program Integation

Successful realization of a single IRES HLO cannot be achieved without thorough systems integration, program integration, and alignment (both schedule and priorities) with the other HLOs. The IRES SE&PI HLO provides de-confliction of critical assets, positive configuration control of test environments, and rapid reprioritization of resources. This HLO is essential to simultaneously and efficiently executing multiple stakeholder requirements that span multiple HLOs in a dynamic test, training, and operational environment. Develops, manages, and maintains Department of Defense Architecture Framework (DoDAF) data used in a Federal and Department of Defense (FEA, DODEA) compliant architectural repository for the IRES contract; renders multiple views of the capabilities delivered under the contract which guides the development of solutions that will meet customer requirements; integrates technical artifacts from disparate MDA contract activities into the Enterprise repository as necessary to satisfy holistic views of the enterprise environment.

Challenges:

a) De-confliction of concurrent events and critical assets, maintaining positive configuration control, and rapid resource reprioritization are fundamental to mission success.

b) The contractor’s ability to synchronize capabilities, schedules, and priorities across the program is a key risk mitigation measure for integration and execution of events that support national defense.

c) Integration of work activities across BMDS Mission Operations, BMDS Testing, Wargames and Exercises, Modeling and Simulation, Enterprise Communications and IT Environment, and Operation of Facility Infrastructure ensures integrity of event architectures and standardizes delivery of technical capabilities.

d) Development of DODAF-compliant end-to-end enterprise event architectures providing enough fidelity to effectively sustain and risk mitigate for the purpose of attaining mission assurance through the lifecycle of all systems involved.

3.0 BMDS Mission Operations

The MDIOC is host to numerous BMDS operational missions, operational test assets, and developmental and prototype systems. BMDS Mission Operations ensures visibility and awareness of the multiple operational readiness postures, delivers warfighter mission support, and provides satellite operations in support of BMDS testing. In addition, BMDS Mission Operations is responsible for Advanced Research activities and the development of prototype systems destined for fielding and maintenance in the operational BMDS architecture.

These missions must be maintained in a continuous state of operational readiness to support contingency operations in the execution of the BMDS mission.

· C2BMC is the integrating element of the BMDS providing missile defense planning, situational awareness, sensor management, engagement coordination, and global networks to create a layered missile defense.

· 100th MDB is the 24/7/365 operational center that conducts operational-level execution of the Ground-based Midcourse Defense (GMD) homeland defense mission.

· JFCC-IMD is U.S. Strategic Command’s (USSTRATCOM) lead organization for planning and synchronizing global missile defense.

· The Missile Defense Space Center (MDSC) provides a centralized, collaborative environment for on-orbit space operations to develop and integrate space sensor capabilities within the BMDS. Supported satellite constellations and space data feeds currently include: Space Tracking and Surveillance System (STSS) and the Enterprise Sensors Laboratory (ESL).

· MDA continually seeks opportunities for improving the BMDS through the experimentation, prototyping, and development of new capabilities leveraging terrestrial and space based data, which will hedge against future missile threat growth, provide early intercept capability, and increase raid handling of BMDS sensors.

These missions require support for their critical infrastructure resources, operational components and informational path flows that enable their warfighting function / capability.

3.1 Infrastructure Readiness Posture

The Infrastructure Readiness Posture capability provides the means to maintain a heightened level of responsiveness and the mission assurance rigor to ensure availability of operational BMD assets working in or through the MDIOC. This capability provides continuous MDIOC situational awareness and mission assurance support (24/7/365) as well as the ability to escalate health and status issues of critical infrastructure resources that directly support the operational BMDS assets. This capability requires increased responsiveness and mature, technical governance to enable full operation.

Challenges:

a) Rigorous configuration management and mission assurance governance / processes are essential to ensure the operational system is not impacted during routine maintenance and break / fix activities of unrelated systems.

b) Due to the criticality of maintaining an operational posture, incident (or break / fix) response time must be minimized.

3.2 Warfighter Mission Support

The Warfighter Mission Support capability assists the Warfighter in the accomplishment of their BMDS mission by the delivery of integrated proficiency training, continuity of operations (COOP) planning, contingency operations, development of automated situational awareness tools that provide real-time BMDS health and status information. Further, Warfighter Mission Support includes advanced concept research and the development of prototype capabilities intended to augment the operational BMDS architecture.

Proficiency training predominantly encompasses system support associated with the Missile Defense Space Warning Tool (MDST). The MDST provides a training opportunity to COCOMs, Military services, and other interested participants by providing Early Warning (EW) threat data over the operational Integrated Broadcast Service (IBS) broadcast.

Continuity of operations planning entails developing and maintaining documented, well defined, and process oriented transfer of mission capabilities to an alternate location (if required) to ensure continuous or near continuous BMDS Watch Officer operations.

Contingency operations is the ability to support the BMDS Warfighters as they transition from normal peacetime activities to a heightened state of alert based on real-world indications and warnings. The preparedness levels of the support infrastructure and resources will be elevated to a very rigorous posture that provides a more detailed analysis process for all maintenance activities and their potential impact, if any, to the resources identified as part of the operational system. It also provides updates on significant events affecting the operational status of the BMDS, assesses operations support status for updates to the Director, Deputy Director, and senior leaders, supports the RFA / RFI process, synchronizes support to Warfighters, and prepares briefings for senior leaders.

Automated tools provide real-time health and status situational awareness information regarding BMDS assets, which provides the Warfighter with information to make knowledgeable assessments pertaining to their respective mission area.

The Advanced Concept Research and Development capability includes systems engineering, design, test and verification, assessment, and delivery of products which add incremental, evolutionary, and/or revolutionary improvements to the BMDS. Development activities include fulfilling technical objectives and goals; demonstrating solutions for BMDS challenges; exploring alternative system design concepts; performing design trades to inform the selection and implementation of the best design; verifying product build and integration; delivery of interim and final products; assessing performance of the delivered products; and consideration of Warfighter feedback throughout the development cycle.

Two examples of advanced concepts that are currently being matured and implemented include the BMDS OPIR Architecture (BOA) and the Simultaneous Correlation of Unambiguous Tracks (SCOUT). The BOA capability will process sensor data from OPIR and other sensors to form tracking, estimation, and prediction solutions which are provided to C2BMC to support BMDS weapon engagements. Also provided are general system functions like data logging and record capabilities integrated within a hardware suite that complies with the installation host computing and security requirements. The SCOUT capability will process sensor data from multiple sources to provide information to C2BMC for discrimination decisions.

Challenges:

a) Development and maintenance of an effective COOP plan to capture operating contingencies that enable the Warfighter to perform at the same competence level as the primary facility.

b) Providing accurate and real-time reports on the readiness posture (health and status) of deployed (i.e., active) BMDS assets which allow the Warfighter to make informed decisions.

c) Providing integration and coordination for warfighter mission support that leverages shared resources (e.g., data and facilities) between multiple products (e.g., C2BMC and BOA) and hosts (e.g., MDIOC and SBIRS) while minimizing development and testing delays.

d) Accessing and utilizing legacy prototypes and products to decrease development cost and timelines.

e) Integrating element level products/modules into system-level architectures to support various events (e.g., ground test, flight test, and wargames and exercises) and operations.

3.3 Satellite Operations

The Satellite Operations Capability is centered on the MDSC, which is located in the MDIOC. The MDSC provides a unique environment to develop and mature space tracking and surveillance related capabilities that contribute to missile defense. The MDSC satellite operations capability provides systematic monitoring of space assets (e.g., Space Tracking and Surveillance System (STSS)) for the purpose of detecting, tracking, and characterizing objects. The MDSC also provides continuous threat updates to BMD elements that enhance overall weapons control solutions. This capability provides operation support to the STSS system.

Challenge:

a) Maintaining satellite system equipment and providing enhanced protection levels to ensure no system degradation or interruption impacts BMDS operations.

4.0 BMDS Testing

BMDS Testing is a continuous, evolutionary process that encompasses both developmental and operational activities to demonstrate the effectiveness, suitability, and survivability of the BMDS. BMDS Testing develops secure test architectures that integrate multiple enclaves and disparate test resources across the enterprise communications and IT environment in accordance with test event requirements to enable testing of the BMDS and its elements while ensuring appropriate cyber security protections are enabled for the protection of all test elements.

Based on historical data and projected budget profiles, this HLO is anticipated to be approximately 9% of the IRES acquisition.

4.1 Flight Test Support

The Flight Test Support capability examines assets in their operational configuration against an inventory of targets to assess readiness aspects of BMDS elements. Flight test activities involve hardware, software, and communications to support the preparation and execution; pre-mission test support and post-event analysis of BMDS element data collection events; and reporting on the performance of the flight test hardware, software, facilities, network monitoring, and procedures. Key characteristics for successful flight test integration include disciplined requirements coordination, precise event preparation, thorough event tracking and effectively capturing and incorporating lessons learned.

Historically, approximately eight flight tests have annually leveraged the JRDC.

Challenges:

a) Translation of flight test objectives and validated event architectures into mission assurance requirements that identify test resources to be provided heightened levels of mission assurance protection during the test period.

b) Obtaining event architecture Information Assurance (IA) accreditation is essential for prevention of a cyber-threat or leak of US information.

c) Availability, reliability and responsiveness of test resources, including subject matter experts, information systems, applications software, models and simulations, and communication networks for all test milestones (i.e., integration events, communication events, dress rehearsals, etc.).

d) Flight tests, which provide a venue to assess and validate BMDS operational architectures, are very expensive. Every opportunity to capitalize upon a test to gain data and knowledge to improve operations and further the BMDS capability must be exploited to the fullest extent possible.

4.2 Ground Test Execution

The Ground Test Execution capability includes the integration of element hardware-in-the-loop, high fidelity threat simulations with operational assets to test capabilities across a wide range of simulated threats, and operating environments that cannot be affordably replicated in flight tests.

Ground test activities involve managing and coordinating activities necessary to perform test events; architecting the test environment based on customer-defined test objectives; collecting, managing, and disseminating ground test data; and executing all phases (integration, dry runs, and runs for record) of ground tests. Key characteristics for successful ground test integration include disciplined requirements coordination, precise event preparation, thorough event tracking and effectively capturing and incorporating lessons learned.

Historically, approximately 12 ground tests have annually leveraged the JRDC.

Challenges:

a) Translation of ground test objectives and validated event architectures into mission assurance requirements that identify test resources to be provided heightened levels of mission assurance protection during the test period.

b) Obtaining event architecture IA accreditation is essential for prevention of a cyber-threat or leak of US information.

c) Availability, reliability, and responsiveness of test resources, including subject matter experts, information systems, applications software, modeling and simulations, and communication networks for all test milestones (i.e., integration events, communication events, dress rehearsals, etc.).

d) Ground tests provide a venue to assess and validate BMDS operational architectures. As such, a thorough understanding of BMDS capabilities, warfighter tactics, techniques, and procedures (TTP), is essential. Every opportunity to capitalize upon a test to gain data and knowledge to improve operations and further the BMDS capability must be exploited to the fullest extent possible.

4.3 Performance Assessment Execution

The Performance Assessment Execution capability provides digital / virtual predictive representations of BMDS elements and components. Performance Assessments are a cost-effective risk mitigation activity to collect data for characterization, verification and validation, and assessment prior to flight test execution. The assessment is a repeatable simulation environment thus allowing multiple assessments of system configuration, engagement conditions and target phenomena.

Performance Assessment activities involve managing and coordinating activities necessary to perform test events; architecting the test environment based on customer defined test objectives; collecting, managing, and disseminating test data; and executing all phases (integration, dry runs, and runs for record) of the assessment.

Historically, one performance assessment has been conducted biennially.

Challenges:

a) Translation of Performance Assessment objectives and validated event architectures into mission assurance requirements that identify test resources to be provided heightened levels of mission assurance protection during the test period.

b) Obtaining event architecture IA accreditation is essential for prevention of a cyber-threat or leak of US information.

5.0 Wargames and Exercises

MDA requires the capability to engineer, integrate, and execute wargames and exercises to demonstrate current and future BMDS capabilities. Wargames and exercises are comprised of a wide range of activities from tabletop seminars to fully interactive, distributed wargames to multi-stakeholder, CCMD sponsored exercises. Delivery of wargames and exercises originates from the MDIOC platform and leverages the enterprise communications and IT environment to connect participants and distribute data around the globe.

5.1 Wargame Execution

The Wargame Execution capability provides experimental opportunities for warfighter and engineering communities to examine defense designs based on near and far term research, development, and test and evaluation capabilities. Wargames may be in the form of table top briefings or fully interactive, geographically distributed, multi-player scenarios, and are based on military operations involving two or more opposing forces, using rules, data, and procedures designed to depict an actual or assumed real life situation. Essential to successful Wargame integration is a disciplined requirements coordination process, precise event preparation, thorough event tracking, and effectively capturing and incorporating lessons learned.

Table-top or limited participation Wargames have historically been conducted bi-monthly. Interactive Wargames historically have been conducted quarterly. Fully interactive, distributed, multi-player Wargames have historically been conducted bi-annually.

Challenges:

a) Translating Wargame…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .