Inactive

**Update: Submission date extended to 3 April 2023 along with POC updates. REQUEST FOR INFORMATION (RFI) Project Director Sensors-Aerial Intelligence (PD SAI) is seeking information from industry on s... **Update: Submission date extended to 3 April 2023 along with POC updates. REQUEST FOR INFORMATION (RFI) Project Director Sensors-Aerial Intelligence (PD SAI) is seeking information from industry on sensors that can satisfy MDSS HELIOS / HAP-DS requirements. THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY. THIS IS NOT A REQUEST FOR PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE AT THIS TIME. Overview/Purpose/Description of Procurement The Multi-Domain Sensing System (MDSS) is a family of capabilities intended to address Army deep sensing requirements by providing airborne sensors that support Multi-Domain Operations (MDO), including Large Scale Ground Combat Operations (LSGCO), and fill sensing gaps for Indicators and Warnings, Long-Range Precision Fire (LRPF) targeting and Situational Understanding. MDSS requirements focus on six capability areas: Platforms; Sensors; Integrated Intelligence, Fires, Electronic Warfare, Cyber and Mission Command; Processing, Exploitations, and Dissemination (PED); Data Transport; and Cyber and Electromagnetic Spectrum (EMS) Resiliency. The High-Altitude Extended-Range Long-Endurance Intelligence Observation System (HELIOS) is part of the overarching Army MDSS system of systems and will provide multiple sensing capabilities by developing and integrating sensor capabilities on different sized stratospheric platforms that, as a system will, comprise a survivable sensing suite in MDO. These will allow stand-off operations to detect, locate, identify, and track critical targets for the ground commander. High-Altitude Platform – Deep Sensing (HAP-DS) is the experimentation and demonstration phase for HELIOS. Presently, sensor priorities for HAP-DS are focused on Electronic Intelligence (ELINT), Communications Intelligence (COMINT), and Radio Detection and Ranging (RADAR). This RFI is specifically looking for information on ELINT, COMINT, and RADAR sensor technologies. This RFI is intended purely for market research purposes. The Government wishes to understand current operational state-of-the-art Intelligence, Surveillance, and Reconnaissance (ISR) sensor capabilities as outlined within this RFI. Additionally, the Government wishes to understand sensor capability maturity and interested parties’ abilities to execute either an anechoic/barometric chamber test or flight test in order to allow capability demonstration and maturity evaluation as compared to the performance requirements/desired capabilities listed in the HAP A-CDD and Deep Sensing Annex. Scope of Effort/Request In response to this RFI, PD SAI is seeking industry information on currently available/NDI solutions (TRL 6+) capable of addressing or capable of being upgraded/enhanced to address HAP-DS Sensor Requirements (Attachments 01-05) to validate industry defined capabilities, sensor maturity, and development risk. Development of timelines to upgrade or enhance existing sensors to address requirements ideally would not exceed a 36-month period and then lead to production. The intent of this RFI is to gather information on state-of-the art ELINT, COMINT, and/or RADAR sensor capabilities that can be integrated on a platform to meet the HAP-DS requirement. This is not a platform evaluation. The planned chamber/flight test is solely meant to evaluate sensor performance and limitations, not aircraft performance. The Government is particularly interested in Sensor Open Systems Architecture (SOSA) and Modular Open System Approach (MOSA) solutions that will provide standardized mounting, power, connections, software and electronic interfaces, and heating, ventilation, and cooling for High Altitude Platforms. Requested Information The Government requests that interested parties provide the following: White Paper Response Provide information on sensor performance/capabilities from the stratosphere and an assessment of technology and integration readiness levels of currently available or NDI solution for ELINT, COMINT, RADAR, or multi-capability sensor hardware in relation to the DS Annex and classified Appendix Requirements. This should include current sensor capabilities, planned/funded capability enhancements, and integration options. Specifically, explain how recommended sensor configuration will satisfy the Government requirements and objectives and/or suggest changes to the requirements based upon what is achievable given the state-of-the-art. Define sensor Size Weight and Power - Cooling (SWaP - C) alignment with the following assumptions regarding SWaP-C variations for the high-altitude platforms. Define scalability to meet various SWaP-C limitations as defined in Section 5.6 of Attachment 02 ((CUI) HAP A-CDD). Note: Submissions by sensor solution providers can assume platform providers will continue to advance technology that will allow for additional threshold power and payload capacity to the platforms as defined in Attachment 02 if desired. Any assumptions in the advances of SWaP capacity for balloons should not exceed the values as noted in Attachment 04 (RFI Supplement to the HAP A-CDD). Sensor provider power parameters/information desired by the Government: Peak power demand Sustained power demand Sensor’s ability to have power turned on/off in support of persistent and sustained stratospheric operations and still operate without significant delay Boot time Low power mode availability Show how proposed solution can be upgraded/enhanced to address deficiencies/deviations/gaps in meeting stated Government requirements and growth capability to meet emerging threats. Interested parties should propose engineering solutions with associated risk assessments (to include cost, schedule, and performance risk) for all deficiencies/deviations/gaps identified (ideally not to exceed a 36 month timeframe). Provide a summary matrix that addresses all sensor related desired characteristics as defined in Attachments 02-05. The summary matrix should include: Current sensor performance against desired characteristics or objectives and thresholds as detailed. Planned sensor performance against desired characteristics or thresholds and objectives with 36 months (three 12-month development cycles) of proposed upgrades to enhance sensor performance Summary of the upgrades proposed/required. As part of the matrix, please provide the following performance parameters as applicable to the proposed sensor(s), in addition to any of the desired characteristics and requirements in Attachments 02-05*: Overall frequency range Direction Finding (DF) /geolocation frequency range DF / geolocation approaches and accuracy Signal sets processed RF performance (bandwidth, sensitivity, dynamic range, resolution) Pulse and signal density processed Field of View (FOV) in Azimuth and elevation Method of dealing with signal separation and co-channel interference System architecture standards and configuration Antenna element and array designs SWAP-C Payload environmental specifications Previous HAP and airborne applications *Some of the parameters below may be included in Attachments 02-05 as well. Define current SOSA/MOSA standards sensor supports today and/or what SOSA/MOSA standards sensor could support with minimal Government investment. Additional information requested for currently available / NDI sensor proposed: Number of systems built and deployed System lead time and production rates First Article Test (FAT) Reports, Development Test (DT) Reports, Production Test Reports, Mil Std 810 (or Environmental Engineering Considerations and Laboratory Tests), Mil Std 461 Test Reports, etc. Independent test reports Current platforms sensor has been integrated on List of flight tested platforms and any reports Existing government customers Demo unit availability Interface Control Document (ICD) / Application Programming Interface (API) availability Second party plugs-ins or software development supported BIT, diagnostics and status monitoring Maintenance philosophy Security accreditation and features Cross cue and integration with other INTs System and LRU weights Blanking and Electronic Protection (EP) controls Operational Availability (AO), Mean Time Between Failure (MTBF) and Mean Time to Recovery, Repair, Respond, or Resolve (MTTR) data or predictions Provide information and solutions in support of DS data transport method requirements as defined in Attachment 03 (Section 5.7 (Data Transport) & 5.11 (Resilient Communications)). Data transport methodologies should support all ISR sensors as described in this document. The data transport equipment methodologies proposed should support the entire Mission Equipment Package (MEP) on both High Altitude Balloons (HABs) and/or Solar Fixed Wing (SFW) platforms. A single data transport method across methodologies and platforms is preferred, but not required. Provide projected cost estimates (Rough Orders of Magnitude (ROM)) for any sensor (this should include all sensor components required to operate sensor at altitude (power supply provided by platform)) and/or data transport methods proposed. Provide current sensor costs as applicable, any Non-Recurring Engineering (NRE) costs to develop sensors to close any technical gaps in requirements, end state per unit cost after 36-month development period to close deficiencies/deviations/gaps, and integration costs on HABs and SFW platforms. Document manufacturing capabilities for all sensors specifically discussing manufacturing facilities, line rates, and lead times. As noted in the introduction, the Government is interested in Industry’s ability to execute HAP-DS Phase 1 sensor performance verification via a chamber or flight test. Please provide the following. The actual testing itself is not part of the RFI response, but should be provided for informational purposes in support of the future release of the Phase 1 RFP: Provide information on availability and ability to provide a contractor owned sensor(s), as proposed in whitepaper response, in support of atmospheric and anechoic chamber testing. Interested parties should assume any chamber testing will occur at the Aberdeen Proving Ground, MD in FY25. Provide information on availability and ability to provide a contractor owned sensor(s), as proposed in whitepaper response, in support of stratospheric balloon flight testing. Interested parties should assume flight testing in FY25 flight testing, locations are TBD. Interested parties should also assume the Government will furnish the platform and gondola while the sensor provider will work with the platform provider for sensor integration. The USG will not be liable for any sensor(s) loss or damage during testing. White Paper Response Collaboration (Discussions) If the Government finds after White Paper responses there is a need for discussions and/or hardware demonstration, PM SAI representatives may meet with potential interested parties and/or request one-on-one sample hardware demonstrations. Such discussions are only intended to obtain further clarification of potential capability to meet the requirements and demonstration of product capabilities. INSTRUCTIONS FOR ACCESS TO MDSS HAP and HAP-DS TECHNICAL DOCUMENTATION: The Government is in the early phases (HAP-DS Experimentation and Demonstration) of the HELIOS program to include requirements development and definition. To support requirements definition, the Government is interested in assessing industry available ELINT, COMINT, and/or RADAR sensor solutions against Government defined desired characteristics and initial high-level sensor performance requirements. Therefore, the Government intends under this RFI to release initial MDSS requirements for industry consideration and feedback. Please note, current ELINT or COMINT or RADAR or ELINT/COMINT/RADAR is defined as a sensor that is capable of one or multiple of the defined ELINT, COMINT or RADAR capabilities. In order to be eligible to receive Controlled Unclassified Information (CUI) HAP-DS Technical Documentation, interested parties must supply: Proof of International Traffic in Arms Regulation (ITAR) compliance by submitting a copy of their Department of State, Defense Trade Controls Compliance (DTCC) registration statement with valid date (vendor may redact vendor registrant code). Sign/return a Non-Disclosure Agreement. Sign/return a Compliance Certification. Identify a Point of Contact (POC) for taking receipt of the Unclassified HAP-DS Technical Documentation (Name, NIPR Email, and Phone required). Once ITAR registration proof, signed NDA, signed Compliance Certification, and POC have been received/cleared, cleared POC will receive an email via DoD SAFE allowing them to download CUI HAP-DS Technical Documentation. Interested parties shall maintain all HAP-DS Technical Documentation in compliance with their signed Compliance Certification, DoDI 5220.22-M dated 1 May 2018 National Industrial Security Program Operating Manual, and DoDM 5200.01 dated 14 May 2019 DoD Information Security Program Marking of Information, and all document distribution statements. List of Unclassified HAP and DS Technical Documentation: Attachment 1: (CUI//SP-FEDCON) MDSS Initial Capabilities Document (ICD) (Secure Release) Attachment 2: (CUI//SP-FEDCON) High Altitude Platforms (HAP) A-CDD (Secure Release) Attachment 3: (CUI//SP-FEDCON) Deep Sensing Annex (Annex A) to the HAP A-CDD (Secure Release) Attachment 4: (CUI//SP-FEDCON) RFI Supplement to HAP A-CDD (Secure Release) In order to be eligible to receive Classified Deep Sensing Technical Documentation, interested parties must supply: Proof of International Traffic in Arms Regulation (ITAR) compliance by submitting a copy of their Department of State, Defense Trade Controls Compliance (DTCC) registration statement with valid date (vendor may redact vendor registrant code). Sign/return a Non-Disclosure Agreement. Sign/return a Compliance Certification. Fill out and return Request for Classified Information. Identify a cleared Point of Contact (POC) for taking receipt of the Classified DS Technical Documentation (Name, SIPR/JWICS Email, and Phone required). List of Classified DS Technical Documentation: Attachment 5: (S//NF) Appendix D – Sensor Performance Parameters for Deep Sensing Annex (Secure Release) Interested parties that complete steps 1-3 for CUI HAP-DS Technical Documentation, do not need to repeat these steps for Classified HAP-DS Technical Documentation access. Complete List of RFI Attachments The following attachments are provided to this RFI: Attachment 1: (CUI//SP-FEDCON) MDSS Initial Capabilities Document (ICD) (Secure Release) Attachment 2: (CUI//SP-FEDCON) High Altitude Platforms (HAP) A-CDD (Secure Release) Attachment 3: (CUI//SP-FEDCON) Deep Sensing Annex (Annex A) to the HAP A-CDD (Secure Release) Attachment 4: (CUI//SP-FEDCON) RFI Supplement to HAP A-CDD (Secure Release) Attachment 5: (S//NF) Appendix D –Sensor Performance Parameters for Deep Sensing Annex (Secure Release) Attachment 6: (CUI//SP-FEDCON) Non-Disclosure Agreement (Secure Release) Attachment 7: (CUI//SP-FEDCON) Compliance Certification (Secure Release) Attachment 8: (U) DoDI 5220.22-M (Public Release) Attachment 9: (U) DoDM 5200.01 (Public Release) Response Guidelines: Interested parties are requested to respond to this RFI with an Unclassified white paper. White paper submissions cannot exceed 25 pages, single spaced, 12-point type with at least one-inch margins on 8 1/2”x11” page size. The response should not exceed a 10 MB e-mail limit for all items associated with the RFI response. Responses must specifically describe the interested party’s capability to meet the requirements outlined in this RFI. Oral communications are not permissible. Sam.gov will be the sole repository for all information related to this RFI. Interested parties may also submit a Classified appendix/annex to the Unclassified white paper submission. Classified white paper annex/appendix submissions cannot exceed 10 pages, single spaced, 12-point type with at least one-inch margins on 8 1/2”x11” page size. The response should not exceed a 10 MB e-mail limit for all items associated with the Classified white paper appendix/annex RFI response. Interested parties shall contact Ms. Tianna Woods regarding classified submission instructions no later than 5 days prior to the submission deadline. Interested parties who wish to request access to any DS Technical Documentation shall do so in writing, (within 10 business days prior to the closing date), no later than Friday, 20 March 2023 at 1600 EST via email addressed as follows. The Government will provide the documentation within 2 business days of approved request. To: Thomas Trzeciak, thomas.f.trzeciak.civ@army.mil, 410.652.4407 Samantha Wallace, samantha.k.wallace2.ctr@army.mil, 443.417.4400 Interested parties who wish to respond to this RFI shall do so no later than Monday, 3 April 2023 at 1600 EST via the email addresses provided above. Questions/Disclaimers: The Government will not entertain and will not address any questions from Industry at this time. The Government will not reimburse companies for any costs associated with the submissions of their responses or the participation in demonstrations. Disclaimer: This RFI is not a RFP and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals, nor will any award be made as a result of this synopsis. All information contained in the RFI is preliminary as well as subject to modification and is in no way binding on the Government. FAR clause 52.215-3, “Request for Information or Solicitation for Planning Purposes”, is incorporated by reference in this RFI. The Government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on capabilities available. This RFI is issued solely for information and planning purposes. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all paper submissions become Government property and will not be returned nor will receipt be confirmed. 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.