Inactive

REQUEST FOR INFORMATION - AUTONOMOUS GROUND VEHICLE SYSTEMS 1. Background The testing and use of Autonomous Ground Vehicle Systems (AGVS) in and around airports has become more prevalent, both domesti... REQUEST FOR INFORMATION - AUTONOMOUS GROUND VEHICLE SYSTEMS 1. Background The testing and use of Autonomous Ground Vehicle Systems (AGVS) in and around airports has become more prevalent, both domestically and internationally. Increased demand for more efficient airport operations coupled with projected labor shortages has driven growing interest and testing of driverless technologies for a range of airport-related applications. These include but are not limited to self-driving jet bridges, aircraft tugs, baggage carts, de-icing, snow removal equipment, grass-cutting vehicles, employee buses, maintenance vehicles, and passenger shuttles. The Federal Aviation Administration (FAA) published two guidance documents (see attachments), which are designed to assist airport sponsors with testing AGVS: Part 139 CertAlert 24-02: Autonomous Ground Vehicle Systems (AGVS) Technology on Airports Emerging Entrants Bulletin 25-02, Testing and Demonstrating Autonomous Ground Vehicle Systems (AGVS) at Federally Obligated Airports The FAA’s Airport Technology Research and Development Branch has been tasked by the FAA Office of Airports Safety and Standards to conduct research to evaluate the operational needs, safety, and security risks associated with the use of AGVS on the movement areas, safety areas, and non-movement areas of an airport. 2. Purpose The FAA is seeking input from: • Designers and manufacturers of AGVS technology • Airport sponsors and stakeholders (end-users) that currently operate or are evaluating AGVS technology The responses received will be used to assess the state of technology and assist the FAA in directing research for the development of minimum standards and guidance for the AGVS design and operation within the airport environment. The information obtained will be used to keep pace with this emerging technology and to assess its potential impacts- such as on airport security, operational efficiency, and passenger experience—for future use at airports. Two appendices accompany this Request for Information (RFI): • Appendix A - AGVS Designers/Manufacturers • Appendix B - Airport Sponsor/Stakeholder Questions It is conceivable that every question in a respective survey may not apply to each respondent. Responding to this RFI is completely voluntary, and we are requesting that you only answer the questions relevant to your operations and within your comfort level. Even partial completion of the survey information is valuable to the FAA research effort. THIS IS NOT A REQUEST FOR PROPOSALS OR OFFERS. The FAA will not pay for any information received or costs incurred in preparing responses to this RFI. Any cost associated with responding is solely at the interested vendor's expense. HOW TO RESPOND TO THIS RFI Interested parties should submit their responses and any supplemental documents that the parties deem relevant to this research, electronically in either Microsoft Word or Portable Document Format (PDF). Please be aware that the FAA’s e-mail server restricts file size to 10 MB per email. If necessary, responses may be submitted across multiple e-mails. The following naming convention must be used: AGVS RFI RESPONSE: (Insert Company/Airport Name) Responses to this RFI must be received by the FAA no later than by 5:00 P.M. EST, Friday, September 26, 2025. Please include “AGVS RFI RESPONSE: (Insert Company/Airport Name)” in the subject line of your e-mail. All proprietary information must be clearly marked. The FAA will protect any proprietary or export-controlled information provided in your submission to the fullest extent allowed under the Freedom of Information Act and other applicable laws and regulations. Proprietary information must be clearly marked. ALL QUESTIONS MUST BE IN SUBMITTED IN WRITING VIA E-MAIL TO: Karen.C.Thorngren@faa.gov and Joseph.S.Szwec@faa.gov. Appendix A – AGVS Designers/Manufacturers Concept of Operations 1. What is the type or function of the vehicle (e.g., lawn maintenance, FOD detection/retrieval, perimeter security, baggage tow tractor, etc.)? Vehicle Components and Capabilities 1. Please describe your vehicle’s remote monitoring and control system. Can multiple vehicles be monitored and how many vehicles can one individual reasonably oversee? Is your monitoring and control system proprietary or is it an open-source standard? Does it easily integrate with other vendors’ monitoring and control systems or would your vehicle fleet be monitored independently of other OEMs? When are alerts/notifications sent to the remote monitor (e.g., lost link, reaching destination, etc.) 2. Please describe your object detection and obstacle avoidance technology and onboard sensors, wireless communication devices and how redundant navigation systems operate (e.g., LiDAR, radar, video, GPS, visual/thermal cameras, etc.). 3. What types of other sensors are used and what are their respective functions? Where are they positioned on the vehicle? 4. What safety elements are employed on the vehicle? Safety elements may include vehicle-based lighting/signage/markings; audible alarms (i.e., a horn) and commands (i.e., a speaker); manual shut-off switches. What is the rationale for selecting specific lighting/signage/marking? 5. What measures are in place to facilitate emergency shutoff? 5.1.1 External manual intervention mechanism (e.g., button) 5.1.2 Remote shutoff capability via a monitoring function on a tablet/command center Vehicle Communications 1. What wireless communication platform is required (e.g., 4G, 5G, Wi-Fi, etc.)? 2. How does the vehicle react during a lost link? 2.1 What vehicle safety options exist (e.g., immediately stopping, moving to the nearest predetermined location, independently determining the safest option in real-time)? Can the vehicle independently determine a safe place to stop in real-time? 2.2 What communication and alerts are possible in the event of a lost link? 3. What alerts are available in the event of an issue (with the communication link still intact) and how are those scenarios implemented or programmed into the AGVS operating rules? 4. What cyber-security measures are in place to ensure the vehicle is not interfered with? Vehicle Operations 1. How does the vehicle safely navigate in its operating area(s)? What is the level of accuracy of the vehicle when following predefined paths? How is this maintained (e.g., types of sensors, GPS, monitoring) and is there redundancy? What happens if the vehicle deviates from its pre-programmed path or the geo-fenced area? What does the vehicle do if one or more of these sensors is damaged or working improperly? 2. Describe the required base data or mapping that needs to be implemented to use your technology. 3. Can a vehicle learn to anticipate the movements of other ground service vehicles and aircraft when taxiing (i.e., similar to how a human would)? 4. At what distance can objects (e.g., vehicles, pedestrians, and aircraft) be detected and identified? Can the AGVS differentiate between different objects? 4.1 In the event that the AGVS gets struck or collides with an object, what does it do (e.g., stop, keep going, send an alert to remote monitor, etc.)? 5. How would the technology plan the vehicle’s route, adjust, and interact with legacy traffic (both aircraft, humans, other ground service equipment, etc.). This includes multiple-vehicle intersection management, parking/gate areas, airport service roads, etc. 6. If an AGVS is traveling on a service road/close proximity to aircraft, how will the AGVS know when to proceed on its route of travel to ensure it is not jet blasted? 7. How will the AGVS give way to emergency response vehicles? Will the AGVS know there is an emergency vehicle approaching? How will it react? Will it give the right way? 8. What operating limitations exist with your vehicle? For example, are there any meteorological (low visibility, precipitation, lightning) or temperature restrictions? 8.1 Do low temperatures greatly impact the operating duration of the AGVS? 9. Would any airport infrastructure changes be required? For example, does the airport/operator need to install additional sensors for navigation and communication (e.g., waypoint navigation beacon or local antennas)? 10. What maintenance is required and what is the frequency of the maintenance schedule to ensure that the vehicle is properly maintained (e.g., sensors are clear of dirt, dust, debris, etc.)? Does the vehicle indicate it is in need of maintenance or is it up to the facility to follow a predetermined schedule? Operations in Movement Areas and Safety Areas 1. How do you plan to address movement area operations? 1.1 For example, does your vehicle have the ability to receive and transmit complex ATC instructions? Can voice be supported or data communications? Appendix B – Airport Sponsor/Stakeholder Questions AGVS Overview 1. What types of vehicles/applications (e.g., lawnmowing, foreign object debris detection, baggage tow tractor, etc.) are your airport/stakeholders considering and what are your most likely use cases for these vehicle types in the short, medium, and long term? 2. Is your airport/stakeholder(s) conducting testing or planning to host a demonstration? 3. What is your airport’s/stakeholder’s future plans for integrating AGVS into day-to-day airport operations? 4. How is your airport and stakeholders preparing for the integration of AGVS? 5. What have you learned to date regarding the potential usage of AGVS in the airport environment.