You are here

New Integrated ATC


OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Trusted AI and Autonomy; Integrated Network Systems-of-Systems OBJECTIVE: Develop a Military spec/hardened automatic tool control (ATC) toolbox that runs off a remote located network approved computer or virtual machine (VM) and incorporates a user interface screen, multi-factor authentication, tool tracking, tool wear, tool home recognition, Foreign Object (FO) scans, and AI to do predictive tool replacement that runs off a centrally located service approved computer. DESCRIPTION: Technicians currently rely on manual checkouts and check-ins for tools and equipment requiring human interaction to input data by hand. Additionally, inspections and tool replacement uses human interaction to identify, predict, and order tools. Human error is high, resulting in an overabundance of tools with low replacement rates and not enough spares for tools with high breakage rates. Additionally, individual tool locations within the same organization are operated under separate systems that do not allow integration with other programs. Furthermore, none of the current ATC toolboxes are capable of operating on the current AFIFNET and they cannot track, identify, and determine tool location internally or externally to the tool box. Technicians spend several hours a day checking tool boxes in and out, inspecting, and replacing tools, wasting valuable time that could have been spent inspecting and repairing aircraft. Personnel need a solution that harnesses current technology to reduce time spent in lines, removes human error, and monitors requirements to keep toolboxes completely functional and ready for use. To meet the intent of the objective, the system needs to meet the following requirements: 1. The ATC needs to be MIL-STD-810G/hardened enough to withstand high and low temperatures, dirt, dust, sand, rain, snow, and ice. 2. The ATC needs to be MIL-STD-810G/hardened enough to withstand drops, falls, and impacts. 3. The toolbox must meet requirements to obtain a HERO certification with max ""Safe Separation Distance"" of 10 ft for UNSAFE from the AF safety center. 4. The ATC needs the ability to use a remote located AFIFNET computer or VM capable with a user interface screen and multi-factor authentication on the toolbox. 5. The ATC needs the ability to track and notify technicians on tool locations, wear/condition status of the tool, identify correct placement of tools and notify when a tool is missing, and locate/identify FO within the toolbox. 6. The AI system needs to conduct predictive tool replacement that operates on a centrally located service approved computer, capable of communicating with all ATCs. 7. The ATC must remain mobile. 8. The ATC needs to be capable of receiving power from an outlet ranging from 110-240V with the ability to operate from batteries for 8 hours prior to needing a recharge or battery swap. 9. The batteries must be easy to swap and capable of recharging within the ATC or on dedicated charging stations. 10. The ATC needs to offer wired and wireless connectivity to AFIFNET and Commercial systems and capable of connecting to closed intranet systems operating on NIPR or lower levels. 11. The ATC needs expansion capability to receive new types of tools and compatible with toolbox expansion from other companies and systems to include a REST API for pushing data to future authoritative data repositories and reporting systems. 12. Develop an example of how the ATC could be used in a commercial and military environment for vehicle maintenance and airports. PHASE I: Complete a feasibility study that should, at a minimum, complete the following using the topic objective and description; 1. Clearly identify who the prime (and additional) potential AF end user(s) is and articulate how they would use your solution(s) (i.e., the one who is most likely to be an early adopter, first user, and initial transition partner). 2. Identify current technology capable of meeting the topic objective that follows all NDAA, DISA, DoD, and Air Force policies, rules, regulations, and laws. 3. If the technology does not exist, determine what needs to be developed to meet the topic objective. 4. Determine if the technology is compatible with required current/emerging Air Force/Commercial assets/systems used within the topic objective. 5. Determine the necessary requirements for any technologies deemed incompatible with each other and current/emerging Air Force assets. 6. Identify if an ATO is required and the necessary stakeholders to ensure implementation across the Air Force. 7. Deeply explore the problem or benefit area(s), which are to be addressed by the solution(s) - specifically focusing on how this solution will impact the end user of the solution. 8. Define clear objectives and measurable key results for a potential trial of the proposed solution with the identified Air Force end user(s). 8. Describe how the solution will need to be implemented across the Air Force. 10. Determine cost of installation, upkeep, and upgrade for the identified technology. 11. Provide a rated scale of feasibility on the identified technology based upon the first five items in this list. 12. Describe technology related development that is required to successfully field the solution. The funds obligated on the resulting Phase I awards are to be used for the sole purpose of conducting a thorough feasibility study using mathematical models, scientific experiments, laboratory studies, commercial research and interviews. PHASE II: Develop, integrate, install, test, and demonstrate a prototype system determined to be the most feasible solution during the Phase I feasibility study. This demonstration should focus specifically on; 1. Evaluating the proposed solution against the objectives and measurable key results as defined in the Phase I feasibility study. 2. Implement countermeasures for issues and identify the necessary evolution of the prototype to foster its eventual transition into a working commercial/warfighter solution. 3. Describing in detail how the solution can be scaled to be adopted widely (i.e. how can it be modified for scale). The solution should detail a rapid deployment and sustainment plan based upon lessons learned from the prototype capable of installing the technology at other Air force installations broken down by continent (i.e. separate plans for bases in Europe, CONUS, the Pacific, etc.). 4. Develop a clear transition path for the proposed solution that takes into account input from all affected stakeholders including but not limited to: end users, engineering, sustainment, contracting, finance, legal, and cyber security. 5. Specific details about how the solution can integrate with other current and potential future solutions. 6. How the solution can be sustainable (i.e. supportability). 7. Clearly identify other specific DoD or governmental customers who want to use the solution. 8. Capabilities/issues identified but not address in previous phase can be resolved, added or remove as needed 9. Verify validity of the developed example for using the ATC in commercial and military vehicle maintenance and airport environments. PHASE III DUAL USE APPLICATIONS: The contractor will pursue commercialization of the various technologies developed in Phase II for transitioning expanded mission capability to a broad range of potential government and commercial users in traditional and alternate mission applications. Direct access with end users and government customers will be provided with opportunities to receive Phase III awards for providing the government additional research & development, or direct procurement of products and services developed in coordination with the program. Additionally, implement commercial applications, marketing, and sales based upon the developed example in Phase II while maintaining government purchasing availability. Additionally, fully operational capability requires seamless integration 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), 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 utilize current DISA APL common criteria certified components when/where possible. Capabilities/issues identified but not address in previous phase can be resolved, added or remove as needed. REFERENCES: 1. AFI 21-101; 2. AFMAN 91-203; 3. Technical Manual 32-1-101 KEYWORDS: Automatic Tool Control; Artificial Intelligence; Identify; Predict; Tool Tracking; Tool Wear; Tool Home Recognition; Foreign Object (FO) Scans; Wired and Wireless Connectivity
US Flag An Official Website of the United States Government