RFP 357835_Drone Services - QA.pdf

PDF 93 KB Posted

Attached to
Autonomous Drone Program - Drone Services
Solicitation number
357835-MTC
Issued by

About this file

This document is an amendment to a Request for Proposals (RFP) for drone services issued by the Department of Energy's Fermi National Accelerator Laboratory. The RFP seeks proposals to provide all-weather, 24/7 drone infrastructure supporting situational awareness, security, site inspections, and contingency response services.

Key details include:

  • Proposals are due by August 30, 2024 at 12:00 PM CST, with early submittals accepted.
  • The contract can be grown into, with the agency understanding that full autonomy may not be achievable by the initial deployment. Components that transmit or store data are of primary concern.
  • There are no restrictions on page length or formatting for the proposal response, which should clearly reference the solicitation requirements.
  • The agency will provide comments on early proposal submissions to ensure completeness, but no extensions will be granted for corrections.
  • The agency has specified required drone capabilities (e.g. RGB 4K, infrared, LIDAR) rather than weight limits, preferring longer flight times with lighter payloads.
  • The current security camera system uses IP-based networking and the agency has separate server infrastructure for retaining video and sensor data.

View the file

Other files

Show all 13

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

Amendment to RFP 357835 – Drone Services August 15, 2025

Questions and Answers

1. Question: Do we have to be able to operate at 100% of the 'must have tasks' IAW Attachment "C" at the beginning of the contract, or can we 'grow' into some of those tasks; are you looking for a complete solution from the beginning of the contract?

Discussion: We understand the five-phase approach as written in the Statement of work. We believe we would be quickly ready to move to phase three at the very start as we currently operate aspects of phase one and two for other projects. (Clearly there are steps in phases one and two that require interaction with FNAL like drone selection, specific spectrum management etc.)

For example, our infrastructure is operational today, however our hangar doors (protection) are not completely constructed. We know they will be required for winter weather, but it boils down to whether we have to have those hangar doors 100% by October, by the start and without Fermi funds, or we are able install our devices at the beginning of the contract and can then assemble hangar doors once complete?

Another example is concerning autonomy. True hands-free operations (100%) does not exist as of yet. No one has mastered the specific robotics. We are working with a national research lab to assist in closing that gap, else they would not take on this task and believe we will get there soon. Is this an inhibitor as I doubt we will be there by the end of August or even October date?

Answer: Yes, the contract can be grown into. It should be made clear what parts cannot be done at initial deployment. We want to make sure the company chosen is aware that full autonomy is an desired end state.

2. Question: When it comes to DoD and BLUE UAS, is FNAL looking for 100% US made components, or are you specifically looking at those components that concern date, computing, transmitting, and control (flight controllers), i.e. share any form of a digital spectrum?

Discussion: We understand as the lead submitting the response to the RFP are responsible to ensure DFARS (CMMC) compliance for all partners (clients) who provide technology for our solution. I ask, and not a show stopper, but many drones for example use struts, motors, payload mounts and props that are not US made. We can limit drone selection, but would be good to clarify as we would then include producing our own 'mechanical and structural parts' as part of our response.

Answer: So long the UAS is on the DOD BLUE list, that certification is all we are looking for. Components that transmit or store data are of most concern if the UAS is not on the approved lists for US government use.

3. Question: Format for submission. We understand all attachments must be filled out completely and submitted back to you by 30 August 2024. Attachment "B" provides the template. Is there a limit to size, number of pages, font required by FNAL?

Discussion: I imagine Attachment "C" will grow significantly with written responses for example.

Sketches and explanations will also expand with multiple courses of action as we do not know required flight / loiter times as well as what drone flight characteristics we have. We will keep it concise, but want the selection panel to understand we know what we are talking about while not explaining every possibility in detail.

Answer: There is no restriction on size. In responding to the solicitation, references to direct specifications/requirements should be clear.

4. Question: Will Fermilab provide comments to RFP (only for completeness or perceived error/ item missing) if the RFP is submitted early (for example by 15 August 2024)?

Answer: Yes. This can be communicated for early submittals. No extensions will be granted for corrections.

5. Question: Is there any weight estimate of packages etc that Fermilab would see transporting by drone? (Time of flight expected as well. Weight, flight time, weather, number of drone delivery / docking stations all related to the answer. We have weights for optical payloads although those will adjust based on optical combinations. This helps us in determining drone platforms to recommend and pricing estimates).

Answer: Instead of specifying a weight, we specified the capability (IE RGB 4K, Infrared, FLIR and LIDAR etc.) Longer flight times with lighter payloads are preferred meeting the capability requirements.

6. Question: Is the current Axis Camera based system transmitted via internet protocol or other frequency band, or is it all hard wired (ether, cable)?

Answer: IP based with commodity WIFI and IP based ethernet (majority), minor use of cellular.

7. Question: Does the Security Department have their own server stacks the retain on all video / sensor / human created inputs (badging for example)? If so, is that data siloed from other data, information from FNAL operations?

Answer: SEMD retains all the data and has separate server racks for the video capability. SEMD partners with our CIO/IT division on some aspects of the architecture (authentication, networking, etc.).

8. Question: Operating system for Fermilab? (Specific to the Security Department).

Answer: Windows is the preferred OS for Security.

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