You are here

FOD Retriever

Description:

OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Trusted AI and Autonomy; Integrated Network Systems-of-Systems OBJECTIVE: Develop and demonstrate weatherproof automated Foreign Object retrieval system that is linked to and electronically tethered to the LFOD (Laser Foreign Object Detection) truck by a secure network to eliminate the need for maintenance personnel to retrieve the geo-tagged Foreign Object. DESCRIPTION: An independent, follow-on industrial vacuum unit, 3-5 feet in width, that is linked to the LFOD system and will go to geo-tagged locations that the LFOD system has identified as FO source to retrieve, while eliminating human source. It should also have a scanning capability on the trailing edge to determine if the FO was removed. FOD deposits should be visible, easily accessible in a clear compartment to confirm FOD contents. Compartment should be large enough to fit a large quantity of hardware, tools and miscellaneous hard/soft FOD. It should have the ability to report failure to pick up FO to the LFOD system. This will require a secure connection to the LFOD vehicle to receive data inputs. The vacuum unit should be wirelessly tethered to the LFOD truck and have a warning system that can be installed on the truck to alert passengers if the tether is broken. Must be environmentally sealed/to operate outdoors and able to withstand ambient temperatures from -20F to 120F and winds up to 50 mph. It should operate on battery power for 3-5 hours before recharging and have an auto-docking capability when it is within _10_ feet of charging station. The unit should be able to travel at a maximum speed of 25 MPH and have 10k Pa (Pascal Pressure Units) of suction. Currently, the LFOD system requires 3 personnel dedicated daily for operations: a System Operator, Vehicle Operator and the third member (FOD Retriever) is required to get out of the vehicle to physically retrieve the FO, which makes the LFOD survey reach a total of 2 hours to clear all taxiways prior to daily flight operations. The quality of checks performed by Flightline workers is subject to any number of external factors affecting the outcome. One primary goal of the FOD Rhumba is to reduce the LFOD Survey time to one hour and eliminate a third person for FOD retrieval. PHASE I: A feasibility study that encompasses the following at a minimum Problem, Solution, Market, Competition, Team/Stakeholders, Financials, Milestones, Additional Information Address at least the following 1) Annual costs for foreign object damage in military aviation overall broken down by military branch and shown as percent of total military/branch/mission support budget 2) Identify current technology capable of meeting the topic objective 3) Identify if the current technology can retire/replace a current process or technology 4) Identify ways where human lead FOD checks can go wrong, and where technological capabilities are greater than current method used by military 5) Identify security concerns and mitigations 6) Cost overview for both initial purchase, sustainment, and scaling up-to and including use across the Department of the Air Force. 7) Warrantee and service information 8) Solution impacts to cost, quality or speed versus the current method 9) Overview of the technological components to make the solution work 10) Procedural changes needed to make solution work 11) Include a visual of potential solutions complete with descriptors 12) Policy changes needed to make solution work, if any 13) Feasibility for an app component 14) Any discretionary information that may be valuable when choosing a solution proposal This is a Direct to Phase II Topic. PHASE II: Develop, integrate, install, test, and demonstrate a prototype system to meet topic objective. This demonstration should focus specifically on: 1) Present overview of the technological components to make the solution work 2) Present annual costs for foreign object damage in military aviation overall broken down by military branch and shown as percent of total military/branch/mission support budget 3) Present a visual depiction of the solutions complete with descriptors 4) Modify current technology capable to meet the topic objective 5) Address security concerns and mitigations actions 6) Provide cost overview for both initial purchase, sustainment, and scaling up-to and including use across the Department of the Air Force. 7) Present warranty and service information 8) Identify any policy changes that would stand in the way of utilizing this capability 9) Real world phase one solution application to a client Air Force base taxiway 10) Testing the scalability of solution 11) Data generation analysis - provide insight to FOD trends 12) Solution/system upgrades based on client Air Force base feedback 13) Provide/cooperate with 3rd party integration for Foreign Object (FO) Rumba Project 14) Beyond government facility priority, integration into civilian airports would be the next step in applicability/usage. 15) Capabilities/issues identified but not address in previous phase can be resolved, added or remove as needed 16) Any discretionary information that may be valuable when choosing a solution proposal" PHASE III DUAL USE APPLICATIONS: Seek to develop non-military applications for technologies developed during or used by this project. Provide ongoing support to military stakeholders. Capabilities/issues identified but not address in previous phase can be resolved, added or remove as needed. This capability will have applications on military taxi-ways/flight lines in which commercial and private airports could utilize in the same fashion. In addition, it could be modified for use in supply warehousing (if adapted to follow forklifts with LFOD systems or other manned/autonomous vehicles). Fully operational capability requires ability to seamlessly integrate onto the Air Force Information Networks (AFIN) for network transport and Air Forces Network (AFNET) for software utilization. The system will utilize these networks for software application usage (both for on premises and remote access as necessary), security practices and procedures, and data transport requirements. Prior to inclusion on Air Force Installation Base Enclaves, all hardware components must comply with DoD Unified Capabilities Requirements (UCR), and be listed on the Department of Defense Information Network (DoDIN) Approved Products List (APL). All software components must adhere to UCR and be certified per the Air Force Evaluated Products List (EPL). In the event components are not currently authorized, authorization will be completed with support of government sponsorship prior to capability delivery to enable immediate operational usage. Request solution use current common criteria certified components when/where possible. REFERENCES: 1. DAFI 21-101; 2. lakenheathi21-102 KEYWORDS: Foreign Object Debris; Damage; Aircraft Engines; Taxiway Crossing; FOD, Pebble; Flightline
US Flag An Official Website of the United States Government