Attachment 4 - Questions and Answers.pdf

Questions and Answers

1. Technical Submission Requirements

• The solicitation mentions a "detailed narrative" for the technical evaluation but only asks for Attachment 3 in the Instructions to Offerors.

• Clarifications Requested:

1. Is a separate technical narrative/volume required in addition to Attachment 3?

• Answer: Yes, statement in solicitation: Offerors must provide a detailed narrative demonstrating how their proposed solution meets the exact specifications listed in the Salient Characteristics and addresses the following functional areas

2. If a technical narrative is required, are there any page limitations, formatting requirements (e.g., font size, margins, file format), or other restrictions?

• Answer: No limitations, see statement in solicitation: Offerors must provide a detailed narrative demonstrating how their proposed solution meets the exact specifications listed in the Salient Characteristics and addresses the following functional areas

3. If a technical narrative is not required, how will the Government evaluate technical acceptability under FAR 52.212-2?

• Answer: Technical Narrative is required.

2. Integration Costs

• The solicitation references integration with ADS-B, Counter-UAS, and related systems.

• Clarification Requested:

• Should offerors include all costs for integrating with Government-provided ADS-B, GCS, and cUAS systems in the quoted price, or will any non-recurring engineering (NRE) costs be handled under a separate contract?

• Answer: Yes, all costs should be included for integration mentioned in solicitation. NOTE – The Government is not providing ADS-B. Contractor is responsible for working with ADS-B vendor to integrate capability into DOMS.

3. Pricing Structure

• The RFQ requests a single fixed price for the Drone Operations Management System.

• Clarification Requested:

• Is this a one-time cost granting perpetual rights to use the system, or an annual recurring cost (e.g., license or SaaS subscription)?

• Answer: The Government would like a minimum of three years’ DOMS access & support. However, the GOVT is looking to industry to propose pricing models for their product.

4. Delivery / Period of Performance

• The RFQ specifies a 90-day delivery after receipt of order.

• Clarification Requested:

• For a SaaS/cloud solution, what constitutes “delivery” in this context?

Is it the initial setup, system deployment, or the start of service?

• Answer: The government needs the software accessible and able to support sUAS operations within 90 days.

5. Sustainment / Warranty

• Attachment 3 requests a "Warranty" description.

• Clarification Requested:

• For SaaS solutions, would a Service Level Agreement (SLA) be sufficient to meet this requirement instead of a traditional warranty?

• Answer: Yes

6. Contract Line Item Number (CLIN) Structure

• The RFQ currently includes only one CLIN (0001).

• Clarification Requested:

• Would the Government consider structuring CLINs to include a base setup cost plus separately priced option years for SaaS licensing, or must all costs be included in a single line item?

• Answer: A single fixed price is required however vendors are welcome to create a line-item breakdown.

7. Schedule / Extension Request

• The RFQ specifies deadlines of 4 September for questions and 12 September for quotes, but does not specify when Q&A responses will be posted.

• Clarifications Requested:

1. When will the Government release Q&A responses?

• Answer: 5 September 2025

2. Depending on the timing of the Q&A release, would the Government consider extending the quote due date by 1-2 weeks to give offerors sufficient time to incorporate the answers into their submissions?

• The amendment solicitation will extend the due date from offerors to 17 September 2025.

8. Past Performance

• Clarification Requested:

• Will past performance be considered in the evaluation alongside price and technical acceptability?

• Answer: No, past performance was not one of the evaluation factors listed.

9. General Information Requests

• Clarifications Requested:

1. What is the USAF's procurement timeline?

• Answer: The latest 30 September 2025

2. What is the USAF's desired implementation timeline?

• Answer: 90 days upon award

3. Has the USAF seen product demonstrations prior to issuing this RFQ? If so, which products or companies were involved?

• Answer: The Government has completed internal market research to identify potential vendors who meet the salient characteristics.

4. How many aircraft is the system expected to manage?

• Answer: JB CHS currently has 8 multi rotor and 1 fixed wing aircraft however this could grow exponentially at any point.

5. How many crewmembers is the system expected to manage?

• Answer: The JB CHS DOMS will need to be utilized by many users on the installation. JB CHS consists of 23,732 personnel

6. How many assets (excluding aircraft) will the system need to manage?

• Answer: All assets associated with the JB CHS sUAS Program Office that are needed to operate sUAS. Ie (batteries, props, sensors)

7. Can the USAF expand on its requirements for UTM capabilities? For instance, what constitutes a conflict and how is it resolved (e.g., scheduling vs. route conflict)?

• Answer: The Government expects industry to provide UTM capabilities based on industry standards ie. (ASTM)

8. Can the USAF elaborate on its expectations for the system's mission planning capabilities?

• Answer: The Government expects industry to provide its systems mission planning capabilities, and the USAF expects that the DOMS should support all mission types as governed by USAF policy and FAA regulations.

9. The pricing sheet has "Explosive Detection Kits" as a header — is this relevant?

• Answer: No that was an error on the Contracting Specialist’s end and will be corrected in the amendment of the solicitation.

10. Is the USAF seeking to outright purchase the system, rather than license it?

Would they be open to licensing software from a vendor?

• Answer: A single fixed price is required however vendors are welcome to create a line-item breakdown.

10. Technical Requirements / System Interfaces

• Clarifications Requested:

1. For “JB Counter-sUAS System interoperability,” which system/version is in scope, and what interfaces are expected? Will the Government provide API documentation or a test endpoint during evaluation/PoP?

• Answer: JB CHS uses multiple C-UAS systems and the GOVT expects the DOMS vendors technology to be adaptable in integration.

2. The Salient Characteristics mention "detection/communications that operate across jurisdictional boundaries." Which off-base stakeholders (e.g., CHS airport/TRACON, county LE) must be enabled on day one, and how many user seats/roles should the quote include?

• Answer: The Government expects industry as the SME to provide DOMS access/integration to all community mission partners that support JB CHS as an assigned unit or mutual aid partners. The application should support access to any operator or stakeholder that is operating withing the JB CHS AOR. Ie (USACE, BOEING, USMC, ARMY), and this should be able to roll out within 90 days upon award.

3. Is cloud hosting acceptable, and if so, is a specific impact level required (e.g., IL4/IL5), or only alignment with ISO 27001/SOC 2? Are there any FedRAMP requirements?

• Answer: ISO 27001/SOC 2 are required.

4. Will the Government provide network access (NIPR/VPN), or will on-prem installations be required? Are there any prerequisites for on-site work, such as base badging or security clearance?

• Answer: The DOMS solution can be hosted by the vendor but should be accessible via AFNET or commercial networks. Vendor may be required to make on-site visits if needed for integration/support however there is no on-site requirement from the GOVT. If on-site visits need to take place the GOVT will coordinate base access.