Inactive

Request for Information (RFI): Hardware and Software Architecture recommendations for Cross Domain Solution (CDS) RFI Introduction: Cross Domain Solutions (CDS) are a key component to information domi... Request for Information (RFI): Hardware and Software Architecture recommendations for Cross Domain Solution (CDS) RFI Introduction: Cross Domain Solutions (CDS) are a key component to information dominance and Warfighter operations that provide the ability to access or transfer information between different security domains. Today, the Warfighter must share intelligence and command and control (C2) information with Joint forces, as well as Mission Partners. The CDS provides a controlled interface to manually or automatically enable and/or restrict the access or transfer of information between two or more security domains based on a predetermined security policy. The CDS is an integrated information assurance system composed of specialized software and hardware that is designed to enforce domain separation and typically include some form of content filtering, which is used to designate information that is unauthorized for transfer between security domains or levels of classification, such as between different military divisions, intelligence agencies, or other operations which critically depend on the timely sharing of potentially sensitive information. The timely exchange of Situational Awareness (SA), Command and Control (C2), Intelligence and Sensor data between various security domains is critical. A CDS capable of connecting to multiple security domains on a single hardware device will allow the Warfighter to transfer the data during mission operations. RFI Responses must address these requirements: The following requirements were identified as necessary to provide the Warfighter with interoperability between security domains. The CDS must meet current National Cross Domain Strategy Management Office (NCDSMO) Raise the Bar (RTB) requirements. The CDS must be on the NCDSMO CDS Baseline list. The CDS must include support for High Threat Networks and Defensive Cyberspace Operations per RTB for Enterprise and Tactical. The vendor must provide both Tactical and Enterprise software and hardware for the CDS as per RTB. The CDS must be both IPv4 and IPv6 compliant The vendor must provide CDS documentation for Phase 0-4 of the CDS Process for a Secret and Below (SABI). The proposed CDS must support up to 10 security domains. The CDS must allow for the data transfer of Structured data formats. Structured data formats refer to data organization methods where information is arranged in a predefined, consistent structure with clearly defined fields and relationships. Examples of structured data types are MIL-STD, XML, Motion Video, etc. The CDS must allow for the data transfer of Unstructured data formats. Unstructured data is information that doesn't have a defined format or organization. Examples of unstructured data types are Text files, Image files, Audio/Video files, Document Files, etc. Question Submissions: Questions regarding this RFI shall be submitted in writing by email NLT 25 October 2024 to virginia.a.pippen.civ@army.mil. The Government does not guarantee the ability to answer questions received after 25 October 2024. As questions are submitted, they will be collected and all questions will be answered at the same time, posted on SAM.gov by close of business on 8 November 2024. Submission Deadline and Contact Information: Responses shall be submitted electronically to virginia.a.pippen.civ@army.mil via DoD SAFE no later than noon (12 PM) EST on 27 November 2024. Submissions shall not exceed 10 pages, using no less than a 12-point Times New Roman font presented in a .docx /.pdf /or .ppt format. An additional, single, cover page may be submitted and it not included in the 10-page limit. PLEASE NOTE NO CLASSIFIED INFORMATION IS ALLOWED ON DOD SAFE Any files containing CUI, PII and/or PHI must be encrypted in accordance with DoD policy prior to uploading or by checking the Encrypt every file box in this form! Cyber.mil clarifies policies about transmitting CUI, PII and PHI Additional Discussions: The Government may choose to reach out to select respondents for additional discussions as a result of this RFI to obtain further information as part of the market research effort. Disclaimer: This RFI is issued solely for informational and planning purposes. This RFI is not a solicitation. This RFI is not to be considered a commitment by the Government to issue a solicitation or award a contract. Responses to this RFI are not proposals and cannot be accepted by the Government to form a binding contract. Federal Acquisition Regulation (FAR) clause 52.215-3, “Request for Information or Solicitation for Planning Purposes”, is incorporated by reference. The Government does not intend to reimburse respondents for any costs associated with the submissions of their responses to this RFI; respondents to this RFI are solely responsible for all expenses associated with responding. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in response to this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned. The Government will not be confirming receipt of submissions. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. Responses from this RFI will be used to formatively shape broad Army guidance for acquiring software solutions. Response content may be aggregated and anonymously published into summary documentation to facilitate such guidance. Any publications resulting from this RFI will be non-attributional. RFI respondents consent to their submissions being used for such purposes. Note: Ensure proprietary information and trade secrets are clearly marked on all materials. All submissions become Government property and will not be returned nor will receipt be confirmed.