C2BMC Follow-on RFI_Final.pdf

Request for Information:

Missile Defense Agency (MDA) Command and Control, Battle Management, and Communications (C2BMC) Capability

General Information:

Document Type: Request for Information RFI Number: MDA21BCRFI01 Original Posted Date: TBD Original Response Date: TBD Current Posted Date: TBD Current Response Date: TBD Classification Code: D -- Information technology services, including telecommunications services Set Asides: Full and Open NAICS Code: 541715 –Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology)

1. Background:

The Missile Defense Agency (MDA) is responsible for developing an integrated Missile Defense System (MDS), integrating land, sea, air, and space-based assets to defend the United States, deployed forces, and friends and allies from missile attacks. The MDA is further responsible for delivering MDS capability with 24/7/365 support across multiple combatant commands and national leadership for strategic, regional, and operational levels. As the integrating element, Command and Control, Battle Management, and Communications (C2BMC) is at the core of the MDS. It is a vital operational system that enables the U.S. President, Secretary of Defense and Combatant Commanders at strategic, regional and operational levels to systematically plan MDS operations, to collectively see the battle develop, and to dynamically manage designated networked sensors and weapons systems to achieve global and regional mission objectives.

C2BMC is required to support a layered missile defense capability that enables an integrated response to threats of all ranges in all phases of flight to include ballistic missiles with complex countermeasures, hypersonic glide vehicles, and subsonic, supersonic and hypersonic highly maneuverable cruise missiles. It is an integral part of all system ground and flight tests, which verify and exercise all current and future MDS capabilities.

2. Description:

The images below provide an overview of the Missile Defense System and the Command and Control, Battle Management and Communications mission:

Today’s Layered Active Missile Defense System

C2BMC Mission

2a. Request for Information (RFI) In accordance with Defense Federal Acquisition Regulation Supplement PGI 206.302-1 this Request for Information is being conducted by the MDA to gauge industry's interest in developing efficient, effective and innovative approaches to deliver an advanced, state of the art C2BMC capability. The C2BMC Program is responsible for delivering reliable, continuous support to the Warfighter, including new innovative capabilities. Each C2BMC release delivered to the Warfighter includes the required software, hardware, network connectivity, fielding, training, cyber resiliency and logistics support for an operational capability. The current C2BMC Element provides: (1) the communications links and connectivity between MDS elements, command centers, other national sensors and data sources, as well as select allied sensors and/or systems; (2) a battle management function that supports engagement planning and coordination to optimize MDS effectiveness and efficiency; (3) control and data management of MDS sensors, to include accepting threat track data from multiple sensors and correlating them into a single system track; (4) real-time situational awareness of the MDS battle as it unfolds;

(5) an advanced planning capability which enables Warfighters to utilize MDS assets across the globe to counter various threat scenarios; and (6) a training system supporting homeland and regional defense.

Historically, C2BMC has been developed and matured in a series of spiral cycles, adding new functionality in each epoch supporting primarily ballistic missile defense. In recent years, the adversary has quickly developed more complex advanced threats, to include hypersonic glide vehicles, supersonic, subsonic and hypersonic highly maneuverable cruise missiles. This drives the need for C2BMC to evolve more quickly to maintain superiority against advanced threats against the homeland and regional mission areas. As C2BMC is central to the MDS, it must have the ability to creatively develop, mature, integrate and test new technologies quickly and reliably to provide a state of the art defense system. As the integrating element of the MDS, C2BMC must also respond to evolution in sensors and weapons systems of the overall system.

As other elements of the MDS make changes or upgrades, the C2BMC program must adjust accordingly to maintain critical integrated end-to-end capability. This includes all aspects of the systems engineering process including system design, algorithm software development, model development and utilization, integration, test, assessment, verification and validation, training, fielding, operations and sustainment support. The resulting system must include a strong cyber security posture and overall system resiliency. The MDA is interested in responses presenting ideas, concepts and approaches that address the need for more rapid, creative technical evolution of capability while maintaining C2BMC’s role as the reliable, integrating element of the MDS.

The C2BMC program office has a requirement to design, develop, test, and field new capabilities to support the MDA commitments to the Warfighter. Additionally, there is a requirement to sustain/maintain the current and future fielded capabilities. Paragraph 2b below identifies the major C2BMC system components/functions that comprise the C2BMC system. Potential approaches to satisfy these requirements could be:

a) develop and integrate new capabilities into the MDS;

b) develop portions of the capability and integrate the entire overall C2BMC release, including portions from other vendors;

c) focus on providing development of some capabilities for C2BMC, with another vendor integrating those capabilities into the overall C2BMC release.

The C2BMC deliverables include, but are not limited to, software modules and associated data products, integration with the C2BMC hardware and software architecture, periodic technology refresh of supporting hardware, threat models and scenarios, upgraded MDS planner, new/upgraded external interfaces, trainer upgrades and documentation, system test plans, procedures, documentation and logistics support planning.

2b. Major Area Descriptions:

2b-1. Software/Digital Development: This technology area includes the development, integration, and testing of C2BMC software with all additional hardware and external software required to achieve an integrated increment capability. Testing includes both element-level and system-level testing with the whole of the MDS. System testing includes flight tests, digital predictive analysis, Hardware in the Loop (HWIL) Ground Tests (GTs), distributed GTs, and HWIL cybersecurity testing.

The MDA seeks to modernize how we design, develop, deliver, operate, and sustain our systems. An integrated digital approach across disciplines to support lifecycle engineering is in the planning stages. Models and Simulations will be implemented as a continuum across the Systems Engineering "V" as the authoritative sources of engineering data. Software Development activities also include designing and implementing an efficient cybersecurity infrastructure that includes anti-tamper mechanisms and protects Critical Program Information.

Furthermore, as the agency seeks to move to a cloud-based development environment to improve and accelerate secure movement of developed software to operational fielding.

C2BMC is interested in concepts and approaches to quickly develop, test, integrate, and validate new capabilities into a modular, extensible system securely and reliably in a responsive manner without incurring unacceptable risk.

To field new system capability, Objective Evidence must be brought through the MDA test processes and to its corporate boards. Objective Evidence is obtained from developmental testing, integration testing with other MDA assets, MDA HWIL GTs, MDA flight tests and overall system test exercises to ensure a strong cyber posture. A developmental test environment of C2BMC software with all additional hardware and external software is required to achieve a secure, resilient integrated increment capability as described above. The integration and support of new C2BMC capability into the MDA system test processes for these tests is required. An integrated assessment of these data into Objective Evidence along with the associated capabilities and limitations of the new C2BMC product will be needed to satisfy the MDA corporate board processes.

2b-2. Development Cadence: The C2BMC program currently utilizes agile development processes, employing a Modular Open Systems Approach, producing the hardware, algorithms, software, network connectivity, and fielded support required to provide a system-wide, integrated missile defense capability. As C2BMC products mature, they are engineered and integrated into fielded releases. The current expected timeframe from requirements identification to develop a release is 24-36 months, which is nominally followed by a period of qualification testing (system ground and flight testing). Historically, multiple releases are in staggered stages of development at all times. Typically, new/improved capabilities have been delivered on a 24 month cycle. Delivered releases enable progressively increased abilities to better plan missile defense, view the battle unfold on common situational awareness displays, remotely manage sensors worldwide, process track data to discern the threat and associated flight path, forward threat engagement information to weapons systems and perform integrated battle management utilizing a global-grid communications network to defeat an adversary's attack. This includes continued evolution of a multi-layer integrated battle management capability to efficiently manage available sensor and weapons systems from detection and acquisition through sensor – shooter pairing, engagement de-confliction and fire control. Current weapons system include Ground Based Missile Defense, Terminal High Altitude Area Defense (THAAD), Patriot, and Aegis Ballistic Missile Defense (Aegis BMD) with additional systems expected as capability is extended to new or existing assets and additional threat types. As C2BMC seeks to evolve capabilities for an effective layered missile defense at a more rapid pace, there is a need to balance faster evolution and fielding with maintaining the overall MDS system operation with MDS sensor and weapon systems that may develop on a different development cycle. The C2BMC architecture of the future must be designed to accept enhanced capabilities as they are integrated into the MDS to achieve full interoperability with other elements (internal and external to the MDA), integrate the MDS into the national military command structure, and be interoperable in coalition environments. C2BMC will manage the sharing of information with allied sensors and/or systems. An example of this could be a future layered homeland defense system that requires multi-layer integrated battle management to incorporate and coordinate additional weapon systems with the GMD system to provide multiple engagement opportunities against threats to the homeland.

The overall MDS capabilities are broken into numbered Increments that are coordinated to synchronize the related efforts among MDS elements for an integrated system capability.

Increment content is maintained in an approved Phased Implementation Plan (PIP). Current planned capability for Increments 9 and 10 are as follows.

Planned Increment 9: Includes the deployment of C2BMC to integrate, coordinate, and enhance operations in support of missile defense capabilities for Sea-Based X-Band (SBX) forward-based discrimination and Ground-Based Midcourse Defense system use of advanced discrimination supporting intercept. This increment also expands interfaces with the space assets that make up the Overhead Persistent Infrared (OPIR) Enterprise, thus providing improved capability against additional Intermediate Range Missile (IRM) threats. C2BMC will continue to play a vital role providing a layered, coordinated active defense against all types of missile threats, and to provide missile defense situational awareness to the Combatant Commanders.

Planned Increment 10: Includes initial long-term content for additional sensors providing features for improved track correlation and interceptor threat correlation. Additional strategic threats are added to the system capability along with the ability to assess intercept success with additional sensor data. As part of Enhanced IRM Defenses in Europe, deployment of a future generation interceptor is anticipated at multiple Aegis Ashore sites and at sea to provide enhanced protection from IRMs. Additional MDS improvements during this phase include expanded coordination of missile defense fire control systems and improvements to radar discrimination. The future generation interceptor will provide an early intercept capability against Medium Range Missiles (MRMs) and IRMs and provide an additional layer for a more enhanced homeland defense. Advanced discrimination technologies will also be deployed during this phase, including Ground-Based Midcourse Defense use of fused data from the entire network of MDS sensors to improve homeland defense.

2b-3. C2BMC Networked Capabilities: The C2BMC System, through the MDS Communications Network, links together the external sensors and weapons of independent elements into a layered missile defense system such that the whole is far more capable and robust than the sum of its parts, thus increasing the footprint of the MDS with greater performance and defensive coverage against current and future ballistic and non-ballistic hypersonic, maneuvering and cruise missile threats. The C2BMC System enables the MDS to manage complex threats -- near simultaneous enemy missile shots aimed at theater, regional, or homeland assets.

The MDS Communications Network Program provides a robust, end-to-end, high availability operational communications network (COMNET) that allows cross-element communication through the MDS (i.e., connectivity that quickly and unambiguously shares information across the global MDS). The COMNET provides network solutions to improve interoperability, security, and collaboration with both internal and external MDS subsystems/elements. Fundamentally, it enables the National Command Authority and the commanders at the strategic, regional, and tactical levels to optimally engage threats at any range, in any phase of flight, at any time. The systems, linked through C2BMC, include PATRIOT, THAAD, Aegis BMD, Ground-Based Midcourse Defense; and sensors such as the Army/Navy/Transportable Surveillance-2 (AN/TPY-

2) radar, SBX radar, Space-Based Infrared Radar System (SBIRS), BMDS OPIR Architecture (BOA), Cobra Dane, Upgraded Early Warning Radars (UEWRs), Long Range Discrimination Radar (LRDR), and other non-traditional sensors. This sharing of information is performed securely with special emphasis on preventing cyber-attack via a MDS Network Operations and Security Center (NOSC). The C2BMC Command Center (CCC) provides daily operations, managing and executing all operations, system administration, system/network monitoring, cyber defense and maintenance activities for all C2BMC operational, test, and training equipment at associated sites. Effective networking management and operations relies on the ability to manage, coordinate, and integrate a wide variety of equipment platforms; interfaces with other DoD and allied communications systems; existing/evolving information standards and capabilities, and adherence to DoD Risk Management Framework (RMF). Defense Information Systems Agency (DISA) services are also highly leveraged in providing worldwide communications.

2b-4. Cybersecurity: The MDA's C2BMC Cyber-resiliency program identifies cyber requirements in early development from current threat intelligence, complies with applicable statutes, regulations, DoD and MDA Issuances, implements the Risk Management Framework (NIST 800 series guidance), and conducts software assurance and cyber-resiliency testing throughout development, capability testing, ground tests and continuous persistent cyber operations monitoring. C2BMC maintains an innovative cyber resiliency focus integrated into system protection planning, engineering, analysis, testing, financial management, sustainment and disposal. The C2BMC cyber-resiliency program is focused on the ability to Identify, Protect, Detect, Respond, and Recover from potential cyber-attacks via the MDS NOSC with a near real-time feedback loop to the development and test environment responsible teams, as well as the Information System Security Manager team. All identified potential vulnerabilities are risk assessed, prioritized, and plan of action and milestones documented through risk acceptance, mitigation, or closure in the MDA Enterprise Mission Assurance Support Service.

2b-5. Planner: The C2BMC Planner functionality is increasingly dependent on reliable understanding of existing missile defense assets and resources as well as potential future changes. Knowledge of both allied and adversary capability together forms a foundational, data-driven basis for battle plans, which influence battle management and engagement outcome. Frequently evolving threat data requires an adaptive approach to MDS planning as well as an ability to adapt to regular advancements in missile defense assets. A C2BMC planner needs to stay relevant to these advancements and look ahead to plan for future advancements as well as provide flexibility to dynamically modify and validate defense designs while operating in a coalition environment. This includes, but is not limited to defense design creation, editing, import, analysis and optimization. It also implies an ability to integrate with the C2BMC suite, provide an intuitive interface and workflow that minimize training and expertise.

2b-6. Training Support: The MDS Continuous Test, Training, and Operations (CTTO) capability safely separates test, evaluation, and training venues from real-world activities, and allows injection of high-fidelity simulations to run realistic scenarios on operational equipment and networks. CTTO is planned to eventually be a capability encompassing all elements of the MDS.

Part of the training solution for CTTO is Distributed Training System (DTS). The DTS addresses Combatant Commander high priority requirements to maintain their operational capability, participate in exercises, train, and rehearse mission scenarios while the system is in an operational state or “on alert.” DTS provides the capability to conduct distributed, medium and high fidelity, and end-to-end strategic and operational training for missile defense operations that incorporates missile warning activity in any or all of the MDS elements. The architecture allows for scalable training of the MDS over the operational architecture and allows operators to train where they fight. Scalable training can vary from individual missile defense assets, to regional MDS capabilities, to the full MDS global community.

2b-7. Program Protection, Defense Exportability and Anti-Tamper: The C2BMC System must protect any embedded Critical Program Information (CPI) and be designed to enable exportability to foreign partners without modification. Provide innovative systems security engineering (SSE) solutions that protect CPI and enable system exportability in accordance with applicable laws, regulations, policies, and procedures. Solutions can include, but are not limited to, hardware, software, and processes.

2b-8. Operations, Maintenance and Sustainment: Prospective vendors must have the capability to efficiently and effectively operate, maintain and sustain the currently globally deployed C2BMC system while minimizing total ownership costs for current and future versions. The system will continue to support and interface with a variety of globally distributed sensors and communications elements hosted in a variety of facilities. The focus is to increase supportability and reduce hardware and software lifecycle costs of current and future variants in a technology environment that faces rapid turnover and requires increasing cyber resilience. Operations and maintenance support must be maintained for C2BMC operational, test, and training systems at all C2BMC locations.

3. Responses:

The intended outcome of this synopsis is to determine if interested sources capable of satisfying the Agency’s requirements exist; specifically the capability to design, develop, test, and field new capabilities to support MDA commitments to the Warfighter as well as to maintain/sustain the current and future fielded capabilities. Paragraph 2b above identifies the major C2BMC system components/functions that comprise the C2BMC system.

The MDA is interested in responses outlining new and creative ideas for the development and integration of state of the art technology to advance C2BMC while maintaining the operational integrity of the deployed system with minimal risk at all times. New technologies should include an assessment of the current Technology Readiness Level (TRL)/Algorithm Readiness Level (ARL), as required as a part of the C2BMC MDS program element (MDA/BC). As a guide, reference the BC Algorithm Readiness Process (see section 9).

Respondents may provide information in some or all of the areas identified in section 2b.

above, such as:

a) approaches to develop and integrate new capabilities into the MDS;

b) approaches to develop portions of the capability and integrate the entire overall C2BMC release, including portions from other vendors;

c) approaches focused on providing development of some capabilities for C2BMC, with another vendor integrating those capabilities into the overall C2BMC release.

This RFI is issued solely for market research – it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the MDA to establish a contract for any supply or service whatsoever. Further, the MDA is not seeking proposals nor will it accept proposals. The information provided may be used in developing an Acquisition Strategy, Statements of Work, Statements of Objectives, or Performance Work Statements.

Participation in future Agency transactions and procurement opportunities is not contingent upon responding to this RFI. It is the responsibility of the potential respondents to monitor this site for additional information pertaining to this requirement.

Responses must follow the following guidelines:

All responses are limited to no more than (20) twenty 8.5 inch X 11 inch pages using Times New Roman 12 pt font, with 1 inch margins on top, bottom and sides (11 inch X 17 inch foldouts shall be counted as two pages). Addendums may be added to meet the MDA's request for additional cost detail (2 pages - top level Rough Order of Magnitude (ROM) of the technical work described in submission to include, but limited to, all anticipated non-recurring engineering costs) (see b. below), answer the MDA's question regarding MDA furnished technical data, computer software, computer software documentation, programmatic or operational information (1 page) (see e. below), and recommendations for future contract construct (2 pages) (see f. below). These addendums will not count against the (20) twenty page RFI response limitation.

Responses must provide the following information:

a. The cover page should contain: Respondent’s profile to include respondent’s name and address, number of employees, annual revenue history, office locations, DUNs number, cage code, NAICS code, current business status (large or small), small business category (if applicable), applicable socioeconomic status, primary and one alternate point of contact, and telephone and email addresses. For all email correspondence, please use the following subject line: MDA21BCRFI01 Command and Control, Battle Management and Communications Capability.

b. Respondents should submit a Capability Statement with an explanation that supports why they should be considered a responsible source. Capability statements must include a feasible schedule with the plan demonstrating the ability to deliver capabilities by the current planned Increment 9 fielding timeline of December 2025. For planning purposes, the anticipated timeline for this effort to begin is 1QFY2023.

c. Description of the respondent's recommended approach to transition work from the current C2BMC capability to ensure successful delivery of future capabilities and increments.

d. If the respondent is recommending parts of the C2BMC Capability program for separate development, provide the respondent’s strategy to seamlessly integrate the developed part with the other subsystems/components with minimal schedule, cost, and performance risk.

e. Specifically what government furnished technical data, computer software, computer software documentation, programmatic or operational information is necessary to perform the requirement?

f. A recommended contract construct for this effort. This includes, but is not limited to, number of contracts (recommended breakout of work), contract type, and incentive and fee structures.

Include the rationale for each recommendation.

g. A prime small business contractor responding to this RFI should include past experience in managing subcontractors on similar requirements and, if applicable, include subcontractor or teaming partners’ experience applicable to requirements specified in this RFI.

Small businesses planning teaming arrangements to meet the support requirements listed above should articulate the portions of work that the prime small business intends to perform as well as articulate the portions that subcontractors or teaming partners (if applicable) will perform. Responses should include business size and business socio-economic category of all subcontractors or teaming partners identified to perform work associated with the NAICS for this RFI.

4. Marking:

Proprietary information is neither sought nor desired by the MDA. If proprietary information is submitted, it must clearly be marked "proprietary" on every sheet containing such information and the proprietary information must be segregated to the maximum extent practicable from other portions of the response (e.g., paragraph markings, image markings, or use an attachment or exhibit). Respondents are responsible for adequately marking proprietary information contained in their response. Do not send any classified information.

The Freedom of Information Act (FOIA) and its amendments have resulted in an increasing number of requests from outside the Government for copies of contract qualifications and proposals submitted to federal agencies. If a respondent’s submissions contain information that he/she believes should be withheld from such requestors under FOIA on the grounds that they contain “trade secrets and commercial or financial information” [5 USC§552(b)(4)], the respondent should mark its submissions in the following manner:

The following notice should be placed on the title page: “Some parts of this document, as identified on individual pages, are considered by the respondent to be privileged or confidential trade secrets or commercial or financial information not subject to mandatory disclosure under the Freedom of Information Act. Material considered privileged or confidential on such grounds is contained on page(s) [enter page number(s)].” Each individual item considered privileged or confidential under FOIA should be marked with the following notice: “The data or information is considered by the submitter to be confidential or privileged, and is not subject to mandatory disclosure under the Freedom of Information Act.”

5. Response Submissions:

Packages shall be submitted electronically to the Contracting Officer in Microsoft Word Format or Portable Document Format (PDF) at the following address: Latoya.Pryor@mda.mil. All responses to this announcement must be received by close-of-business TBD. Submitted information will not be returned to the interested party. The MDA may not acknowledge receipt of responses to this RFI. If a receipt is desired, potential sources should submit statements electronically and select "read receipt request" from electronic mail options.

Communications with the MDA with regard to this RFI will be permitted only electronically to the Contracting Officer during the RFI response period, ending TBD. It is anticipated that all information submitted will be unclassified. If it is necessary to submit classified information, please contact the Contracting Officer for submittal instructions.

6. Response Review:

The MDA intends to use Government personnel and third party, non-government (i.e., contractor) support personnel as subject matter experts in the review of responses received, including the review of any marked or unmarked proprietary information provided. Appropriate nondisclosure agreements will be executed between the third party, non-government support personnel and the MDA. As a general policy, contractors, which provide advisory and assistance services to the Agency, particularly in the engineering, acquisition support, and quality functional areas, cannot develop or support the development of the Agency’s procurement efforts. This separation of contractual responsibilities is critical to ensuring the Agency obtains independent and objective advice.

Submission of a response under this RFI constitutes a grant of authority by the respondent to the MDA to allow access to Federal personnel and these third party individuals to any content of the submission that may constitute material within the ambit of the Trade Secrets Act, 18 U.S.C. 1905.

Respondents will not be notified of the results of any review of this RFI; however, the Contracting Officer may request clarification of submissions.

7. Compensation:

Participation in this effort is voluntary with no cost or obligation to be incurred by the MDA. All costs associated with responding to this RFI will be solely at the respondent’s expense. No funds have been authorized, appropriated, or received for this contemplated effort.

8. Security Clearance:

The highest level of personnel and facility security classifications for this effort will be Secret.

9. List of Documents Available Upon Request:

Government Furnished Information (GFI) is restricted for use for this RFI only and may be classified SECRET. Dissemination of information is limited and intended to assist a respondent in providing a response to this request. In order to receive the classified GFI, the respondent requires the ability to receive or view the information. A respondent may request GFI via SIPR, if available. If a respondent wishes to receive a digital copy of the documentation, a facility security clearance of no less than SECRET to include SECRET safe guarding will need to be provided. All requests must be submitted to the Contracting Officer, Latoya Pryor at Latoya.Pryor@mda.mil using the Document Access Agreement/Request form, Annex 4.

1. Ballistic Missile Defense System (BMDS) Security Classification Guide (SCG), Change 1 dated May 26, 2017; (U)Secret Appendix

2. Missile Defense Agency Assurance Provisions (MAP) MDA-QS-001-MAP-Rev C Dated 1 October 2019

3. Missile Defense Agency Parts, Materials, and Processes Mission Assurance Plan (PMAP) MDA-QS-003-PMAP-REV B Dated 2 March 2012

4. BC Algorithm Readiness Process, dated 25 October 2017

5. Adversary Data Package Version 19.0, (U)Secret Document

6. MDA Phased Implementation Plan (PIP)

7. C2BMC Top Level Architecture

8. C2BMC Operational Concept Description, (U)Secret Document

All technical data, computer software, computer software documentation, and programmatic and operational information provided by the MDA is in an "as is" condition without any warranty as to its accuracy, completeness, or adequacy. The respondent shall use this technical data at its own risk. The MDA assumes no responsibility for such data/documentation nor will the MDA have any liability should such data/documentation prove to be inaccurate, incomplete, or otherwise defective.

Contracting Office Address:

Redstone Arsenal, Alabama 35898 United States

Place of Performance:

Redstone Arsenal, Alabama 35898 United States

Primary Point of Contact:

Latoya Pryor Contracting Officer, C2BMC Latoya.Pryor@mda.mil Phone: 256.450.2831

Opportunity History

HQ0147-11-R-0012