Army W56KGU-23-R-RTID questions responses.pdf

Questions/Clarifications for BAA number W56KGU-23-R-RTID “Cryogenic Magnetometer Integration”

Topic: GGA-02

Can the work be performed at a contractor location?

Yes. The contractor must have a valid network accreditation and implement appropriate security controls to protect the documentation, which is expected to be categorized as Controlled Unclassified Information (CUI), in accordance with relevant regulations and standards, such as the National Institute of Standards and Technology (NIST) Special Publication 800-171 and the Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012.

Are there any restrictions with respect to company size?

No restrictions if the company can meet the objectives of the project.

Are there any acquisition requirements for this BAA that favor one type of company over another?

No.

Is there another white paper or proposal opportunity associated with Topic # GGA-02, entitled “Novel RF Sensing Modalities such as Quantum for SIGINT”?

All opportunities are published on sam.gov when they are available.

Are there dimensional requirements for testing on the army platform?

The proof-of-concept iteration under this announcement will not impose strict dimensional requirements, allowing proposers to determine the optimal Size, Weight, and Power (SWaP) characteristics for their system to demonstrate capability. Proposals that showcase modular and scalable designs capable of being easily adapted for use in various platforms with minimal redesign or reconfiguration will be considered more competitive.

Is it expected that the prototype generated will move into acquisition if testing is successful?

A successful demonstration of the technology under this effort may lead to the transition of the design documentation to an Army Program of Record, potentially resulting in future production and fielding of the system, pending approval from the relevant Army acquisition authorities and successful completion of all necessary development, testing, and evaluation activities.

Are there any associated requirements for the acquisition model for example as distinct from a first prototype for testing?

The focus of this effort is demonstration of capability. Designs that would fit easily into the army acquisition model would make the capability more appealing to Army programs of record. For Reference the Army Acquisition Model is based on the DoD Acquisition Framework, which is outlined in DoD Instruction 5000.02.

The Army’s model is described in Army Regulation 70-1, “Army Acquisition Policy.”

Is there a determined temperature of operation?

Demonstrations will take place domestically, so the systems must be able to function during an Arizona summer or Montana winter (for example). The system must be able to be able to perform under outdoor conditions. MIL-STD 810 is the desired end state but it is not the intent of this project to meet the full temperature extremes or ruggedization requirements.

Are there SWAP requirements?

For the proof-of-concept iteration, proposers will have the flexibility to define their system's Size, Weight, and Power (SWaP) requirements, allowing them to optimize their design for demonstration of capability. Proposals that demonstrate platform-agnostic designs, capable of being easily integrated into multiple platforms with minimal modification, will be considered more desirable.

Is there value associated with logistical benefits such as reliability, and COTS/GOTS, and ease of operation etc.?

Yes. Designs that meet the required capabilities and are characterized by simplicity, ease of use, and minimal maintenance requirements will be more competitive for Army programs of record. Specifically, systems that can be operated and maintained by soldiers with basic training, without the need for specialized expertise or extensive technical knowledge, will be viewed as more desirable and sustainable for long-term fielding.

Will the sensor performance requirements e.g. noise floor and bandwidth be provided so that the design can be correspondent to the sensor performance?

Performance requirements will be provided at the appropriate classification.

While understanding the need to work in the CMOSS framework, are there requirements for the output of the pod with respect to what kind of systems it will be utilized with—is a generically applicable pod system more valuable than pod system designed for one specific application or system?

The RF output of the pod should be designed to be compatible with a wide range of Software Defined Radios (SDRs), enabling seamless integration with various systems that possess the necessary processing capabilities. A modular and adaptable design that can be easily interfaced with multiple SDR platforms, without requiring significant customization or modification, will be considered more valuable and desirable.

Is lack of security facility clearance a show-stopper for award or execution of a contract?

The work will be at the very minimum CUI. If a company does not have the ability to work or store technical data at that level it is a show-stopper. If there are components deemed to be higher classification than CUI the government will work with the performer to appropriately protect the sensitive information.

Is partnering with a company which has a cleared facility acceptable, or can work occur in a government facility when needed?

There are no restrictions on who performers can partner with. If you do not have pre-existing access to a government facility and wish to request access to one as part of this effort, lay out the purpose and requirements as part of the white paper.

Could or would this work require a company to get a facility clearance?

The work will be at the very minimum CUI. If there are components deemed to be higher classification than CUI the government will work with the performer to appropriately protect the sensitive information.