Inactive

Amendment 2 : Adds the "Questions and Answers" document for access to frequently asked questions in response to the RFI. Amendment 1: Removes the requirement for "Document Access Agreement/Request for... Amendment 2 : Adds the "Questions and Answers" document for access to frequently asked questions in response to the RFI. Amendment 1: Removes the requirement for "Document Access Agreement/Request form, Annex 4" from the first paragrapgh in Section 9. THIS IS A REQUEST FOR INFORMATION (RFI) ONLY: This RFI is issued solely for information and planning purposes, 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 Government to a contract for any supply or service, whatsoever. Further, MDA is NOT seeking proposals at this time and will NOT accept unsolicited proposals as part of this RFI. Responders are advised that the Government will NOT pay for any information or administrative costs incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the interested party's expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. If a solicitation is released, it will by synopsized on the beta.SAM.gov website. It is the responsibility of the potential Offerors to monitor the referenced site for additional information pertaining to this requirement. ------------------------------------------------------------------------------- In accordance with Defense Federal Acquisition Regulation Supplement PGI 206.302-1 this Request for Information (RFI) is being conducted by 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 MDA commitments to the Warfighter. Additionally, there is a requirement to sustain and maintain the current and future fielded capabilities. Paragraph 2b of the attachment, C2BMC Follow-on RFI_Final, 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; and, 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.