FRA Enterprise Unmanned Aircraft Systems (UAS) Delivery Model Validation

Form / Attachment / Pricing Sheet

This document, "Attachment B – Technical Requirements," outlines the operational and data requirements for an anticipated Unmanned Aircraft System (UAS) platform. It is intended to guide vendors in providing Rough Order of Magnitude (ROM) pricing.

Section 1 – Operations (Minimum Operational Requirements):

• Platform Capabilities: VTOL, autonomous flight with obstacle avoidance, ruggedized design, max payload capacity, integrated parachute for emergency recovery.
• Flight Performance: Minimum 30-60 minutes endurance, up to 10 km operational range, suitable for open corridors/urban operations, rapid swap batteries.
• Payload/Sensors: Spare propellers, high-resolution optical camera (still imagery and 4K+ video), LiDAR/3D mapping, thermal imaging, stabilized gimbal, optional GNSS/other sensors, support for at least 6 GCPs.
• Data Management: Onboard encrypted storage, automated offload, live feed streaming.
• Safety/Compliance: FAA regulations (Part 107 or other), NDAA Sec. 848 (FY2020), Sec. 817 (FY2023), American Security Drone Act compliant, redundant systems (IMUS, GPS), remote pilot interface with geofencing and override.
• Operational Support: Compatible with secure transport, portable charging systems, workflow integration, software updates.
• Environmental/Field Considerations: Operational in rain, dust, moderate temperatures; designed for rapid deployment in rail-adjacent, emergency response, and difficult-to-access sites.

Operational Use Cases:

• Grade crossing inspection (weekly)
• ENS Inspection (weekly)
• Derailment investigation (as needed)
• Hazard material inspection (as needed)
• Incident response (as needed)
• Infrastructure assessment (as needed)
• Site distance reviews (as needed)
• Quiet Zone inspection (weekly)
• Trespassing detection (weekly)

Operational Locations: Public right-of-way, railroad property, remote rural/urban crossings, training environments, incident response locations.

Operational Assumptions:

• Low Utilization: 10-25 missions/week
• Medium Utilization: 25-75 missions/week
• High Utilization: 75-150 missions/week
• Estimated derailment response events: 25/year.

Section 2 – Data (Minimum Requirements):

• Data types: Standard aerial imagery, high-resolution photography, photogrammetry, thermal imagery, video capture.
• Data usage: Support FRA inspectors for safety inspections, investigations, site distance analysis, measurements, accident documentation, and compliance assessment.
• Data ownership: All imagery, metadata, and geospatial products are property of the Federal Government.
• Integration: Solutions should integrate with FRA enterprise data systems (geospatial, inspection, records management, analytics).
• Cybersecurity: Secure data transmission, FISMA-aligned architecture, continuous monitoring, 3-5 year data retention, integration capability with government systems.

This document details the specific technical capabilities, operational requirements, data collection needs, and compliance standards expected for the UAS platform. Vendors must address these requirements when preparing their proposals and ROM pricing to ensure their solution meets the government's needs for railroad infrastructure inspection and incident response.

Request for Information (RFI)

This RFI seeks information from qualified vendors regarding Unmanned Aircraft Systems (UAS) platforms, sensors, payload options, software solutions, data processing services, and overall system capabilities. The goal is to assess and identify various delivery models for UAS services to improve the safety, efficiency, and effectiveness of the Federal Railroad Administration's (FRA) inspection activities. This is for market research purposes only and does not constitute a solicitation or an indication of a future contract award.

• Potential enterprise delivery models for UAS capability

• Commercially available UAS platforms and services

• Acquisition planning and lifecycle cost modeling

• Most effective operational approach for a national FRA UAS capability

• Railroad grade crossing inspections

• Accident and derailment investigations

• Infrastructure and right-of-way assessments

• Safety situational awareness

• Site distance analysis and obstruction evaluation

• Trespassing detection and evaluation

The FRA is evaluating three primary delivery models for UAS capabilities:

• Government-Owned / Government-Operated (GOGO)

• Contractor-Owned / Contractor-Operated (COCO)

• Hybrid Model: Contractor-Owned, Government-Operated (COGO) Vendors are requested to provide input on advantages, limitations, and lifecycle cost implications for each model, and to recommend a preferred model using the provided ROM Pricing template (Attachment C).

• Response not to exceed 8 pages of text (excluding cover page, graphics, tables, diagrams, spreadsheets, and Attachment C).

• Prepared using Times New Roman 12-point font, 8.5 x 11-inch paper, 0.5" margins.

• Each page to identify respondent and page number.

• Cover page to include company name, business product/service line, CAGE code, UEI, contact info, NAICS codes, business size/type, and GWAC contract information if applicable.

• Responses should demonstrate capability, not just affirm it.

• Section 848 of the FY2020 National Defense Authorization Act (NDAA)

• Section 817 of the FY2023 NDAA, and the American Security Drone Act of 2023

• American Security Drone Act of 2023 (FY2024 NDAA, Title XVIII)

• FAR 52.240-1

• RFI Response Due Date/Time: April 8, 2026, 5 PM EST

• Email questions and responses to: kerianne.gallagher@dot.gov

• Include RFI #693JJ6FRAUAS and "FRA Enterprise UAS Delivery Model Validation" in the subject line.

Form / Attachment / Pricing Sheet

This document is a Rough Order of Magnitude (ROM) Pricing Template provided for market research to assess potential delivery models and associated ROMs for Unmanned Aircraft Systems (UAS) services for the Federal Railroad Administration (FRA). It is not a Request for Proposal (RFP).

• Instructions Sheet: Provides guidance on completing the template, emphasizing that it's for ROM pricing, not binding quotes. It requests alignment with specific delivery models (Government-Owned/Government-Operated, Contractor-Owned/Contractor-Operated, Hybrid) and asks vendors to detail cost differences, key cost drivers, and assumptions.
• Scope of Pricing: Requires ROM for flight operations across low, medium, and high utilization categories, covering assumed costs for Hardware, Sensor Package, Data Processing, Cloud Storage, Software Licensing, Maintenance/Support, Hardware Lifecycle, and Training.
• Delivery Model Alignment: Vendors should align ROMs with recommended models: GOGO, COCO, or Hybrid (COGO). ROMs for multiple models should be provided if feasible.
• Assumptions & Notes: Vendors must include key assumptions such as geographic coverage, mission frequency, equipment type, staffing, and data processing approach.
• Optional Inputs: May include cost drivers, scaling considerations, and pricing differences across environments.
• Pricing Template Sheet: A spreadsheet for vendors to input their ROM pricing based on utilization levels and delivery models.

This template is crucial for vendors to provide high-level cost estimates for potential UAS services based on different operational models and utilization rates. It helps the government compare approaches and associated costs. Bidders must use this template to submit their ROM pricing, clearly documenting all assumptions and cost drivers.