MODIFICATION
A -- Gulf Cooperation Council (GCC) Ballistic Missile Early Warning System (BMEWS) Command, Control, and Communications (C3) Architecture and System - Amendment 1
- Notice Date
- 2/11/2016
- Notice Type
- Modification/Amendment
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- Other Defense Agencies, Missile Defense Agency, MDA-DACK, Huntsville, Huntsville, Alabama, United States
- ZIP Code
- 00000
- Solicitation Number
- MDA16BCRFI03
- Archive Date
- 3/15/2016
- Point of Contact
- Shirlee R Madeloff, Phone: (256) 450-3166, Robert T. Duncan, Phone: (256) 450-3140
- E-Mail Address
-
shirlee.madeloff@mda.mil, Robert.Duncan@mda.mil
(shirlee.madeloff@mda.mil, Robert.Duncan@mda.mil)
- Small Business Set-Aside
- N/A
- Description
- This RFI has been revised since its original posting in November 2015. This document is the result of a comparison between the original RFI and the revised RFI (using track changes). **SEE ATTACHMENT AT BOTTOM OF NOTICE FOR CHANGES TO THIS RFI** Missile Defense Agency Gulf Cooperation Council (GCC) Ballistic Missile Early Warning System (BMEWS) Command, Control, and Communications (C3) Architecture and System Request for Information (Restricted to US Companies Only) Office: Missile Defense Agency DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited 1.0 GENERAL INFORMATION These RFI's are Restricted to US Companies Only. As a result of the May 2015 Camp David Summit, the United States Government (USG) agreed to "help conduct a study of a GCC (Gulf Cooperation Council) ballistic missile defense architecture and offered technical assistance in the development of a GCC-wide Ballistic Missile Early Warning System" (BMEWS). The USG is releasing three Requests for Information (RFIs) for Sensors; Command, Control, Communications (C3); and Cross Domain Solution (CDS). The Respondents may respond to one, two, or three RFIs. Responses to these RFIs will support the USG's recommendations to the GCC for development of a BMEWS. The Missile Defense Agency (MDA) Command, Control, Communications, Computers, Intelligence, Surveillance & Reconnaissance (C4ISR) Program Element is conducting market research to determine industry interest and capability for development of an C3 Architecture and System or identification of existing systems that could support the GCC BMEWS C3 architecture. The C3 System shall manage multiple sensors to detect, track, and discriminate ballistic missile (BM) events threatening the GCC Member States. GCC threat specifics are provided in a separate classified annex. In addition, the C3 System shall integrate with the six GCC Member State Air Operations Centers (AOCs) and Air Defense Operations Centers (ADOCs) to provide common situational awareness information and sensor data. The individual GCC Member State AOC/ADOCs may use the BMEWS sensor data for cueing and weapon engagements with organic National Assets in accordance with their command structure. Figure 1 as provided in the Attachment (BMEWS Block Definition Diagram) provides a BMEWS Block Definition Diagram including the C3 System providing additional capabilities beyond the sensors and GCC Member State Organic National Assets (sensors/weapons) operating autonomously. Figure 1 - BMEWS Block Definition Diagram (See Attachment) 2.0 C3 ARCHITECTURE CAPABILITIES AND REQUIREMENTS Figure 2 as provided in the Attachment (Strategic Analysis and Coordination Center (SACC) Internal Block Diagram) provides a notional internal block diagram for the SACC which is the primary location for conducting the BMEWS Operational Mission and C3 System's electronic equipment. The SACC operational role will be defined in a GCC BMEWS Concept of Operations to be developed in collaboration with the GCC Member States. Figure 2 - SACC Internal Block Diagram (See Attachment) The following defines the C3 System capabilities and requirements. 2.1 The C3 System shall manage the BMEWS including initialization, operating mode selection, health & status monitoring, redundant network communications, and security measures to protect against nation-state cyber-attacks. 2.2 The C3 System shall integrate with the GCC Member State AOCs/ADOCs to conduct mission threat analysis and sensor surveillance planning including: • Threat Assessment and Posture • Courses of Action (CoA) Development • Coordinate Sensor Surveillance Sectors • GCC Sensor Surveillance Plan Publication 2.3 The C3 System shall integrate the GCC BMEWS Cross Domain Solution (CDS) to ensure only releasable data is exchanged between the SACC and Member State AOC/ADOCs 2.4 The C3 System shall integrate the GCC BMEWS Sensors and data interfaces. 2.5 The C3 System shall manage multiple sensors including satellites, IR UAS, and EWR. Sensor management includes initialization, operating mode selection, health & status monitoring, pre-planned autonomous and cued surveillance search volumes. 2.6 The C3 System shall process sensor source track data including boost (9 state) and ballistic (6 state) source tracks with covariance data (if available) and maintain a sensor source track repository. 2.7 The C3 System shall perform multi-sensor track correlation to determine if the multiple source tracks represent the same ballistic missile threat and maintain a correlated track repository. 2.8 The C3 System shall associate objects from the same threat family to a specific launch event and maintain a launch family association repository. 2.9 The C3 System shall calculate a launch point estimate and impact point prediction for each threat trajectory. 2.10 The C3 System shall report BMEWS correlated tracks to the GCC Member State AOCs/ADOCs including the launch point estimate, boost/ballistic state vector with covariance data (if available), launch family association, and impact point prediction. 2.11 The C3 System shall report BMEWS tracks with sufficient accuracy and timeliness to support GCC Member State sensor and weapon system cueing and engagements. 2.12 The C3 System shall provide Operator Workstation(s) for GCC Sensor Management, Common Situational Awareness, BMEWS operational status and capability displays. 2.13 The C3 System shall provide Role Based Access Controls to ensure only authorized Operators can modify the BMEWS System configuration. 2.14 The C3 System shall provide dual redundant processing strings with failover capabilities for continuous mission operations. 2.15 The C3 System shall provide secure, redundant, and cyber-protected circuits for data transport between the Sensors - SACC and SACC - GCC Member State AOCs/ADOCs. 2.16 The C3 System shall provide an interface to exchange information with the USA's Ballistic Missile Defense System (BMDS). 2.17 The C3 System shall employ a Modular Open System Approach (MOSA) for the hardware and software component design. 3.0 RESPONSES 3.1 Instructions for Submissions: Respondents to this RFI are invited to prepare and submit, no later than February 14, 2016, the following: 3.1.1 Executive Summary (not to exceed 5 pages or slides) that includes 3.1.1.1 Descriptive Data: 3.1.1.1.1 Company Name 3.1.1.1.2 Point of Contact 3.1.1.1.3 Address 3.1.1.1.4 Telephone and Fax Numbers 3.1.1.1.5 Email Address 3.1.1.1.6 DUNS (Data Universal Number System) Number 3.1.1.1.7 CAGE Code and/or Tax ID Number 3.1.1.1.8 Business Size Standard and applicable NAICS (North American Industry Classification System) codes 3.1.1.2 Identify the Government Furnished Technical Information that is required in order to accomplish the execution of the GCC C3 Architecture description or supporting sensors and ROM costs identified in this RFI. List and describe this data (does not count toward page limit for Executive Summary). 3.1.2 White Paper (not to exceed 30 pages): The white paper on the C3 Architecture will address the capabilities and requirements contained in section 2. 3.1.3 The Respondents shall provide ROM costs and milestones for the proposed C3 architecture or identified existing systems. 3.2 Responses to this RFI should be submitted via e-mail to BMEWStask@mda.mil with the subject line notated as follows: BMEWS C3 RFI. 3.3 The Missile Defense Agency will host a BMEWS Industry Day on January 14, 2016 at 9 am CST at the Missile Defense Agency Von Braun III Auditorium, Huntsville, Alabama location which will include a presentation/discussion at the classified (SECRET) level. 3.3.1 Reservations for the Industry Day are required to attend and VARs must be submitted NLT 5 business days prior to the Industry Day (there will be no exceptions to this requirement). E-mails for the reservation will be accepted at BMEWStask@mda.mil. Please title your e-mail request "BMEWS Industry Day" and include the following information: 3.3.1.1.1 Company Name 3.3.1.1.2 Point of Contact 3.3.1.1.3 Full names of all attendees 3.3.1.1.4 Address 3.3.1.1.5 Telephone and Fax Numbers 3.3.1.1.6 Email Address 3.3.1.1.7 DUNS (Data Universal Number System) Number 3.3.1.1.8 CAGE Code and/or Tax ID Number 3.3.2 Attendance at the Industry Day is not a requirement to submit a response to this RFI. 4.0 CLASSIFIED THREAT DOCUMENTATION Access to classified threat documentation is being furnished with this RFI to provide additional background information to potential responders to facilitate a more informed response. A request made by a potential responder for this RFI's classified threat documentation must be submitted via email to BMEWStask@mda.mil with the subject line "Classified Threat Documentation Request". In order to receive this RFI's associated classified documentation, a requesting company must have a facility clearance of no less than "SECRET." All requests for the RFI classified attachment must be submitted in writing on company letterhead and the request must include the following information: 1.1 Verification of facility clearance level (either copy of DSS approval letter and/or company cage code). 1.2 Verification that the company has storage capability to the "SECRET" level. 1.3 Verification that the respondent understands that the data provided may NOT be duplicated and must be destroyed upon completion of RFI submission. 1.4 Physical Address where classified data should be sent along with responsible points of contact and phone numbers. Identify whether or not classified fed‐ex packages may be sent to the physical address provided. Alternatively, identify a classified email address to which the documents may be provided. 1.5 Verification of intention to respond to subject RFI, to validate the need to know. 5.0 REQUESTED INFORMATION 5.1 This announcement is published for informational purposes only. It does not constitute a solicitation or request for proposal and shall not be construed as a commitment by the Government. Any response will be treated as information only and shall not be used as a proposal. Replies will be separated from, and have no bearing on, evaluation of proposals submitted in response to any future formal Request for Proposal. Responses in any form are not offers and the Government is under no obligation to award a contract as a result of this announcement. The Government does not intend to pay for the information solicited and will not reimburse any costs associated with responding to this RFI. 5.2 Proprietary information is neither sought nor desired by the Government. If such 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., use an attachment or exhibit). Respondents are responsible for adequately marking propriety information contained in their response. The Government intends to use 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 non-disclosure agreements will be executed between the third party, non-Government support personnel and the Government. A submission of a response to this RFI constitutes the Respondent's acknowledgement and agreement that the information provided in the response, including any marked or unmarked proprietary or source selection information, may be disclosed to these third party, non-Government support personnel. Eligibility in participating in a future acquisition does not depend upon a response to this notice. 6.0 QUESTIONS All unclassified questions related to this RFI should be provided via email to BMEWStask@mda.mil. Contracting Office Address: Missile Defense Agency, MDA-DACB Building 5224 Martin Rd, Redstone Arsenal, AL, 35898, UNITED STATES Point of Contact: Shirlee Madeloff, Procuring Contracting Officer, C2BMC Contracts
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/c3a4f44c6df4892ef2a9f2020b1ca787)
- Record
- SN04017890-W 20160213/160211234449-c3a4f44c6df4892ef2a9f2020b1ca787 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |