AWS_RPP_Official_QandA.pdf

PDF 8 KB Posted

Attached to
Request for Prototype Proposals (RPP) — Anesthesia Workstation System (AWS) Prototype
Solicitation number
W91CRB-26-AWSP
Issued by

About this file

This file is a Questions and Answers document for Request for Prototype Proposals (RPP) W91CRB-26-AWSP for the Anesthesia Workstation System (AWS) Prototype Project issued by the U.S. Army. The proposal submission deadline is 01 October 2026 at 16:00 Eastern Time. Respondents must request a DoD SAFE file transfer link and password from Roxanne Dalrymple, the Agreements Specialist, at roxanne.a.dalrymple.civ@army.mil. The anticipated award date is FY27 Q1, and the Government will use FY26 Defense Health Program RDT&E two-year funds for the prototype award. Prototype delivery is desired within 45-60 days after award; however, if minimal modifications such as a transport case are required, delivery may extend to 120-180 days after award.

The document addresses technical specifications and compliance requirements for the AWS prototype. Key clarifications include: electronic gas-supply pressure display is acceptable provided it has battery backup power (minimum 1 hour) and includes mechanical backup for manual ventilation during complete electrical power loss; a separate, compatible modular monitor (NIBP + ≥2 IBP) is acceptable instead of integrated monitoring; limited software modifications to optimize concentrator operation and FiO2 handling are considered minimal modifications and respondents retain resulting intellectual property; adjustment of inspired oxygen concentration via circle system rebreathing is acceptable in austere environments without compressed medical air sources; and compliance matrices may be submitted as separate appendices outside the seven-page Volume II page limit. The document also notes that MIL-STD-810H tailoring levels, RMF/ATO scope documentation, and specific environmental testing parameters remain under development and will be determined in coordination with testing and cybersecurity teams following award. A potential follow-on procurement of 180 AWS systems would utilize Procurement funding, with procurement anticipated to start in FY28.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Official Questions and Answers

Request for Prototype Proposals (RPP) W91CRB-26-AWSP Anesthesia Workstation System (AWS) Prototype Project

1. Can you please confirm the proposal submission due date? The RPP posting on sam.gov lists both 1-OCT and 8-OCT (both by 1600 Eastern).

The proposal submission due date is 01 October 2026 at 16:00 Eastern Time.

2. Who is the email point of contact to request a DoD SAFE file transfer link and password for proposal submissions?

To request a DoD SAFE file transfer link, please email the Agreements Specialist, Roxanne Dalrymple, at roxanne.a.dalrymple.civ@army.mil.

3. RPP Section 6.1 (A-003) and Section 6.2 state prototype unit delivery at 45–60 days after award, while the ADRL matrix (A-001) states 120–180 days after award. Which timeline is binding for proposal purposes, and will the Government amend the non-governing document?

The Government would like prototype delivery 45-60 days after award; however, if minimal modifications, such as a transport case, needs to be created, then 120-180 days after award is the latest the Government would like to accept the prototypes.

4. Section 5.2 lists Additional Performance Attributes numbered 1, 2, 3, 4, 6 and 7, with no APA

5. Was an attribute omitted in error?

The numbering was an oversight. There are no missing attributes and there should be 6 total.

5. Section 7.6 excludes compliance matrices from page limits, while Section 7.3 requires the CODS compliance matrix within Volume II. Please confirm if the compliance matrix may be submitted as a separate appendix that does not count against the seven-page Volume II limit.

The compliance matrix may be submitted as a separate appendix that does not count against the seven-page Volume II limit.

6. Appendix E must be included in Volume II. Does Appendix E count toward the Volume II page limit?

Appendices do not count towards page limits.

7. Section 2.0 identifies FY27 Defense Health Program RDT&E; two-year funds, while Section 9.2 identifies FY26 funds. Is the potential procurement of 180 follow-on AWS systems included in FY 26 funds? If not, where will the follow-on funding come from, and what is the timeline for procurement?

FY27 Q1 is the anticipated award date. We will use FY26 DHP RDT&E; funds for that award. The potential procurement would be with Procurement (PROC) funding which would be discussed during the potential follow-on award. Procurement is expected to start in FY28 and will be discussed in further detail upon successful prototype OTA.

8. If procurement of 180 follow-on AWS systems is initiated, what is the anticipated delivery schedule required to meet your needs?

Procurement is expected to start in FY28 and will be discussed upon successful prototype OTA.

9. Gas-supply pressure display (CODS-4): Is it acceptable that the gas-supply pressure is measured and displayed electronically rather than by a mechanical gauge?

Yes, this is acceptable. Measuring and displaying gas-supply pressure electronically (e.g., via digital pressure transducers and display screens) meets the intent of CODS-4.

However, in accordance with CODS-4 and CODS-6:

1. The electronic pressure monitoring capability must be supported by the system's battery backup power (minimum 1 hour per CODS-10); and

2. If electronic gas delivery or flow control is utilized, the system must retain a physical mechanical backup to ensure the clinician can verify gas flow and deliver manual ventilation during a complete loss of electrical power.

Respondents should describe their pressure display architecture and power-loss contingency mechanisms in Volume II (Technical Approach).

10. Monitoring (CODS-7): Confirm that a separate, compatible modular monitor (NIBP + ≥ 2 IBP) is acceptable instead of integrated monitoring.

A separate, compatible monitor is acceptable instead of integrated monitoring.

11. MIL-STD-810H — configuration: Are the five methods (501.7 / 502.7 / 506.6 / 514.8 / 516.8) to be run operating or non-operating (storage / transit)? Is a post-exposure functional check sufficient, or is operation during exposure required?

The testing and PM teams are still determining how to tailor the MIL-STD-810H testing. Testing is likely to include operating, storage, and transit scenarios.

12. SW modification & data rights: Would a limited software modification to optimise concentrator operation (FiO2 handling with an external O2 supply) still count as a minimal modification? And if the Respondent funds this modification itself, does the resulting IP / data rights remain Respondent property rather than becoming Government data?

Yes. A limited software or firmware modification to optimize fresh gas delivery, FiO2 handling, or alarm logic for operation with external oxygen concentrators is considered a 'minimal modification' under this RPP, provided it does not alter the baseline core clinical functionality or require a fundamental architectural redesign of the COTS/NDI system.

In accordance with Section 7.3 (Volume II), Section 7.4 (Volume III), and Section 7.5 (Volume IV), Respondents proposing such a modification must:

a. Clearly describe the technical nature of the software modification;

b. Provide an integrated milestone schedule showing how the modification, validation, and delivery will be achieved within the Government’s prototype testing window; and

c. Break out and identify the cost under CLIN 0007. If the modification is internally/privately funded by the Respondent, CLIN 0007 should be priced accordingly (e.g., $0.00 / Respondent-Funded).

Yes, the resulting intellectual property remains the property of the Respondent. Pursuant to Section 5.6 of the RPP, this is a commercial-derivative prototype effort, and the Government does not seek ownership of proprietary commercial hardware designs, algorithms, or software source code.

13. Mixer Type: Which mixer is desired? Mechanical Mixer (where there are traditional O2 + Air knobs) or Electronic Mixer (where the FG flow/mixture is set electronically?

The Government is not directing any desires outside of what is included in the RPP.

14. RMF / ATO scope: For a standalone, non-networked device, confirm the reduced RMF / MDERA scope and the expected documentation set.

The specific documentation required for RMF (to include a MDERA) will be discussed in coordination with the cybersecurity team following award.

15. Oxygen / concentrator operation: When supplied from an external Army O2 concentrator with no medical AIR available, is it acceptable that an FiO2 < 100 % is achieved only via (partial) rebreathing in the circle system?

Yes, this is acceptable. The Government recognizes that in austere ROC 3 operational environments where an external compressed medical air source is not available, adjustment of inspired oxygen concentration (FiO2) may rely on circle system rebreathing kinetics and fresh gas flow management.

Respondents should describe in Volume II (Technical Approach) their system's gas delivery mechanics, circuit architecture, and method for monitoring delivered FiO2 and agent concentration under single-gas (O2/concentrator-only) supply conditions.

16. MIL-STD-810H — tailoring levels: Please specify the temperature ranges, vibration levels, shock / drop heights, durations and the climatic category to be applied.

This is still being worked out with the testing and PM teams to determine how to tailor testing for a COTS device.

File details come from the government source that posted it. Updated .