Missile Defense Agency

Transcription

1 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 Location: MDA-BC Reference Number: BC Responses Due by close of business DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited Approved for Public Release nn16-mda-nnnn (dd mm yyyy8567 (10 February 2016) 1

2 1.0 GENERAL INFORMATION These RFI srequests For Information (RFIs) 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 United States Government (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. bdd [Package] System Block Diagram [System Block Diagram] Gulf Cooperation Council (GCC) Ballistic Missile Early Warning System (BMEWS) Block Definition Diagram NOTIONAL Surveillance and Tracking Sensors {1..n} + Early Warning Radar(s) + Satellite + Unmanned Aerial System (UAS) Data Message Exchanges Task Commands Threat Track Data Health and Status Strategic Analysis and Coordination Center (SACC) {1} «Operating Mode» + Ready - Standby() + Active - Operational() + Active - Training/Exercise() + Active - Maintenance() «Command and Control» + Threat Analysis() + Sensor Planning() + Sensor Management() + Multi-Sensor Track Reporting() + Object Lethality Discrimination() + Situational Awareness Display() «Network Communications» + Network Management() + Secure Data Transport() «Operator Training» + Training Support System() notes GCC Regional Ballistic Missile Defense Command, Control, and Communications (C3) Host Country Cross Domain Solution {1} Threat Track Data GCC Cross Domain Solutions {6} Data Message Exchanges Sensor Cues Launch Point Estimate Impact Point Prediction System Health and Status Multi-Sensor Correlated Threat Data Object-to-Launch Event Association USA Cross Domain Solution {1} Data Message Exchanges Task Requests Threat Track Data Health and Status Radar Host Country AOC/ADOC {1} GCC Member State's Air Operations Centers (AOCs) and Air Defense Operations Centers (ADOCs) {6} + Bahrain + Kuwait + Oman + Qatar + Saudi Arabia + United Arab Emirates USA Ballistic Missile Defense System (BMDS) {1} GCC Member State's National Assets Organic Radar {0..n} THAAD Weapon System {0..n} PATRIOT Weapon System {0..n} Organic Weapon System {0..n} The C3 System provides common situational awareness information and sensor data to the GCC Member State AOC/ADOCs. The individual AOC/ADOCs may use the BMEWS sensor data for cueing and weapon engagements with their organic national assets. 2

3 Figure 1 BMEWS Block Definition Diagram 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. ibd [Package] SACC Internal Block Diagram [SACC Internal Block Diagram] Gulf Cooperation Council (GCC) Strategic Analysis and Coordination Center (SACC) Internal Block Diagram SACC Mission Processing String A NOTIONAL «interface» Sensor Interface(s) {1..n} + Early Warning Radar(s) + Satellite + Unmanned Aerial System (UAS) Initialization Health and Status Tasking Commands Sensor Management Initialize Sensor Operating Mode Monitor Sensor Health and Status Manage Sensor Tasks & Resources System Operating Mode Threat Analysis and Sensor Planning «interface» GCC Member State AOCs/ADOCs Interface(s) {6} + Bahrain + Kuwait + Oman + Qatar + Saudi Arabia + United Arab Emitates GCC Member State Organic Radar Source Track Reports Source Track Reports Boost (9-state) Ballistic (6-state) Source Track Data Conditioning Multi-Sensor Track Correlation Sensor Track Processing Launch Event Association Launch Point Estimate BMEWS Correlated Track Reports BMEWS Operator Workstation «datastore» Source Tracks «datastore» Correlated Tracks Impact Point Prediction BMEWS Track Reporting «datastore» Threat Launch Family Associations Sensor Management and Common Situation Awareness Data SACC Mission Processing String B Redundant processing strings with failover capabilities for continuous mission operations Figure 2 SACC Internal Block Diagram 3

4 Formatted: Font: Not Bold, Font color: Text 1 Formatted: Heading 1, Left 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-attacksembedded Operator training. 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 external GCC Member State data interfaces. 2.5 The C3 System shall manage and/or control multiple GCC sensors including satellites, IR Early Warning Radars, Satellites, and Unmanned Aerial Systems (UAS, and EWR.). Sensor management includes initialization,; operating mode selection,; RF exclusion zones; health &, status, and resource utilization monitoring,; pre-planned autonomous and precision cued surveillance search volumes; threat tracking and object lethality discrimination tasking. 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 The C3 System shall report BMEWS correlated tracks to the GCC Member State AOCs/ADOCs including the launch point estimate, threat typing, boost/ballistic state vector with covariance data (if available), launch family association, object lethality discrimination results and impact point prediction. 4

5 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 The C3 System shall provide Operator Workstation(s) for GCC Sensor Management, Common Situational Awareness, BMEWS operational status and capability displays The C3 System shall provide Role Based Access Controls to ensure only authorized Operators can modify the BMEWS System configuration The C3 System shall provide dual redundant processing strings with failover capabilities for continuous 24/7 mission operations The C3 System shall provide secure, redundant, and cyber-protected communications circuits for data transport between the following: Sensors and the SACC Sensor and the respective Host Nation 2.15 SACC and the GCC Member State AOCs/ADOCs. SACC and the US Ballistic Missile Defense System (BMDS) 2.16 The C3 System shall provide an interface to exchange information with the USA s Ballistic Missile Defense System (BMDS).US BMDS The C3 System shall employ a Modular Open System Approach (MOSA) for the hardware and software component design The C3 System processing strings shall be capable of Concurrent Operational, Training/Exercise, and Maintenance operating modes with safety isolation between real-world and test/exercise data The C3 System shall implement the Information Technology Risk Management Framework to ensure information assurance and provide security measures to protect against nation-state cyber-attacks The C3 System shall determine and report the lethal object (i.e., warhead or reentry vehicle) for each threat The C3 System shall be capable of operating in the natural and induced environments of the GCC region The C3 System shall implement techniques to limit unintentional transfer of critical technology through reverse engineering. Formatted: Indent: Left: 1.25", Hanging: 0.25" 5

6 3.0 RESPONSES 3.1 Instructions for Submissions: Respondents to this RFI are invited to prepare and submit, no later than February 1629, 2016, the following: Executive Summary (not to exceed 5 pages or slides) that includes Descriptive Data: Company Name Point of Contact Address Telephone and Fax Numbers Address DUNS (Data Universal Number System) Number CAGECommercial and Government Entity (CAGE) Code and/or Tax ID Number Business Size Standard and applicable NAICS (North American Industry Classification System) codes, and socio-economic category 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) White Paper (not to exceed 30 pages): The white paper on the C3 Architecture will address the capabilities and requirements contained in section The Respondents shall provide Random Order of Magnitude (ROM) costs and milestones for the proposed C3 architecture or identified existing systems. Examples of C3 sub-systems for the requested ROM data include threat Analysis and Sensor Planning, Sensor Management, Sensor Track Processing, BMEWS Operator Workstation, BMEWS Network Communications, System Control and Management (Computing Infrastructure). Formatted: Outline numbered + Level: 3 + Alignment: Left + Aligned at: 1.46" + Indent at: 1.96" Formatted: Bullets and Numbering Formatted: Outline numbered + Level: 4 + Alignment: Left + Aligned at: 2.19" + Indent at: 2.69" Formatted: Outline numbered + Level: 3 + Alignment: Left + Aligned at: 1.46" + Indent at: 1.96" Formatted: Space After: 6 pt, Line spacing: single, Outline numbered + Level: 3 + Alignment: Left + Aligned at: 1.46" + Indent at: 1.96" 6

7 3.2 Responses to this RFI should be submitted via to 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 locationii Presentation Center which will include a presentation/discussion at the classified (SECRET) level. [THIS EVENT HAS BEEN HELD] 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). s for the reservation will be accepted at BMEWStask@mda.mil. Please title your request BMEWS Industry Day and include the following information: Company Name Point of Contact Full names of all attendees Address Telephone and Fax Numbers Address DUNS (Data Universal Number System) Number CAGE Code and/or Tax ID Number Attendance at the Industry Day is not a requirement to submit a response to this RFI 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 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 DSSDefense Security Service (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. Formatted: Outline numbered + Level: 2 + Alignment: Left + Aligned at: 0.73" + Indent at: 1.06" Formatted: Outline numbered + Level: 2 + Alignment: Left + Aligned at: 0.73" + Indent at: 1.06" Formatted: Indent: Left: 0.75", Outline numbered + Level: 3 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 1.46" + Indent at: 1.96" Formatted: Indent: Left: 1.25", Outline numbered + Level: 5 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 2.92" + Indent at: 3.67" Formatted: Indent: Left: 0.75", Outline numbered + Level: 3 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 1.46" + Indent at: 1.96" Formatted: Outline numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 3 + Alignment: Left + Aligned at: 0" + Indent at: 0.33" Formatted: Bullets and Numbering 7

8 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 exfed Ex packages may be sent to the physical address provided. Alternatively, identify a classified 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 CLASSIFIED MAILING INSTRUCTIONS DoD Manual Volume 3 (Enclosure 4) and DoD M (NISPOM) (Section 4) establish procedures for mailing classified information. Formatted: Space Before: 0 pt, Line spacing: single Formatted: Space After: 0 pt, Line spacing: single When transferring classified information, it shall be enclosed in two opaque, sealed envelopes, wrappings, or containers, durable enough to properly protect the material from accidental exposure and facilitate detection of tampering. (1) Prepare envelop/package, and securely seal classified material in ways that minimize risk of accidental exposure or undetected deliberate compromise. To minimize the risk of exposure of 8

9 classified information, package documents so that classified material is not in direct contact with the inner envelope or container (e.g., fold so classified material faces together). (2) Show the address of the receiving activity, the address of the sender, the highest classification of the contents on the inner envelope or container. The inner envelope may have an attention to line with a person s name. (3) Do not place a classification marking or any other unusual marks on the outer envelope or container that might invite special attention to the fact that the contents are classified. (4) Sender will include a transmittal receipt form which will be placed inside the package -- no classified information should be contained on the transmittal receipt. (5) MDA will return this transmittal receipt form to sender to validate receipt of classified data. (6) Address all classified envelopes or containers consistent with the Labeling Examples shown below. Sender must display complete return address on both inner and outer packages. Outer Label Inner Label Missile Defense Agency Missile Defense Agency/BC Attn: Document Control Attn: Mike Kennedy/Shirlee Madeloff Bldg: 5224, Martin Road Bldg: 5224, Martin Road Redstone Arsenal, AL Redstone Arsenal, AL CLASSIFIED MAIL US Postal Service (USPS) Registered Mail, USPS Express Overnight Mail and Federal Express Overnight Mail are acceptable for delivery to the MDA facilities in Huntsville, Alabama IMPORTANT: If any portion of the RFI response is classified, please submit the entire response as one classified package. Additionally, please ensure the RFI response is provided in a digital format, hard copies are optional. Once classified package is mailed, notify the government by via BMEWSTask@mda.mil with mail method, tracking number, and name & contact data of organization's person responsible for mailing the package QUESTIONS All unclassified questions related to this RFI should be provided via to BMEWStask@mda.mil. Contracting Office Address: Missile Defense Agency, MDA-DACK Building 5224 Martin Rd, Redstone Arsenal, AL, 35898, UNITED STATES Point of Contact: Shirlee Madeloff, Procuring Contracting Officer, C2BMC Contracts 9