Questions And Answers_RFI 311111-MTC.xlsx
XLSX spreadsheet 12 KB Posted
- Attached to
- Autonomous Drone Program - Drone Services
- Solicitation number
- 357835-MTC
About this file
This document contains questions and answers related to a Request for Information (RFI) for an Autonomous Drone Program at the Fermi National Accelerator Laboratory (FNAL). The RFI is seeking to establish a comprehensive drone program to enhance security and operational capabilities, including situational awareness, inspection, contingency response, and logistics support. Key points from the questions and answers include:
- FNAL is seeking a hands-free, 24/7 multi-mission drone platform that can integrate with their existing security systems and provide a suite of sensor capabilities (e.g. LIDAR, EO/IR, laser designation).
- FNAL is looking for autonomous operation, live video feed, package/supply delivery, auto recharge, and seamless integration with their security systems.
- FNAL is considering maintenance and technical support requirements, with a desire for quick response times and on-site support as needed.
- The associated federal contract opportunity involves a future solicitation for an Autonomous Drone Program, with an anticipated release date of May 16, 2024. The program aims to acquire an autonomous, multi-platform/multi-sensor integrated system to support FNAL's security and operational needs.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Pre-Solicitation 357835-MTC Autonomous Drone Program - Drone Services_Amendment 1 .pdf | ||
| Questions and Responses RFP 357835-MTC Drone Services .xlsx | XLSX spreadsheet | |
| DRAFT_Drone Services SOW.pdf |
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
Sheet1 Question No. Document Name Section No. Page No. Contractor Question FRA Response SOW or RFP Changes Made
| 1 | Sources Sought | RFI | 2 | It would be helpful to know if particular types of vendors are not acceptable (e.g. US sourced). Has FNAL fully defined the SOW? The SOW is adequate, but it would be more helpful to know if FNAL will provide customized sensor package or expect the vendor to provide unique sensor solution based on data requirements. . | Q1: Overall the RFI did not specify in detail the system we desire for FNAL. We kept it high level: hands free, 24/7, multi-mission platform that can handle packages and a suite (TBD) of payloads - all integrate into the AXIS camera system we have as well as our C2/Situational Awareness (other sensors) on the site. |
| None | |||||
| 2 | Sources Sought | RFI | 2 | Additionally, roughly clarifying the scale of “package/supply delivery” requirement will improve the quality of responses | Q2: What should be in the PWS: |
- 24/7
- hands free
- drones at the ready - live in device
- integrated with security systems on installation
| - all weather (depending on the drones we select - we would not select all the same) | None | ||||||
| 3 | Sources Sought | RFI | 2 | Rough expectations on the required responsiveness (i.e. max time to drone to area of interest) and density (i.e. how many drone responses at any given time) will help with project costing. | Q3: We will make final determination of the type of sensor capabilities knowing that there is a big stratification of how precise we need them to be and their relationship to cost. LIDAR, EO/IR, Laser desg / Radiation / Gases / speaker system etc. Those costs come when we make decision on which ones we want to have and in what density. Given options, FNAL can discuss flight/station time, lift capability, weather min/max, etc. | None | |
| 4 | Sources Sought | RFI | 2 | General expectations for the maintenance responsibilities and desired reliability of the drones and docking appliance will be necessary to scope the project (i.e will this be contractor maintained or will this be government maintained) | Q4: Maintenance as part of the program - renegotiated when project complete end go into lifecycle. That being said, based on experience, company proximity to Fermilab makes a difference. The installation team that will be working with these requirements over the phases may be on-call as needed, and should likely have just about any maintenance or repair issues sorted within a 24 hour window. There is likely a need for boots on the ground techs to provide routine or emergency technical support within one hour, 24/7/365. | None | |
| 5 | |||||||
| 6 | |||||||
| 7 | |||||||
| 8 | |||||||
| 9 | |||||||
| 10 |
File details come from the government source that posted it. Updated .