OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Trusted AI and Autonomy; Integrated Network Systems-of-Systems OBJECTIVE: Develop a mobile standalone asset management system capable of using a variation of sensors and devices to track any AF asset and report location and status on one system capable of feeding a Common Operating Picture (COP) (AGE, weapons, computer, medical equipment, etc.). DESCRIPTION: Air Force organizations/personnel require a flexible automated asset management capability in order to increase efficiency/effectiveness of asset tracking and reporting while reducing manpower requirements currently required to complete hands-on/visual inventories completed on end of shift, daily, weekly, and monthly time intervals. The asset management/tracking system should utilize various sensors/devices (RFID, Bluetooth, GPS, etc.) to enable the following: 1. Creation of geo-fenced locations (minimum 50 meter radius) for tracking larger equipment 2. Track items entering and exiting buildings/facilities through identified entrances and exits 3. Provide expandable capability to detect devices within a room of a building/facility utilizing hand-held device 4. Provide expandable capability to provide pinpoint location of an asset (not inside a geo-fenced location) if necessary The system needs to track and report on usage rates, repair cycles, status, historical records, and pinpoint locations of the asset to reduce manpower waste while providing the ability to deploy and track assets down to the last tactical mile. The tracking needs to be capable of operating as often as near-real time with options to report at longer intervals. The system needs to be capable of connecting with current Air Force asset tracking/reporting systems by pushing/pulling data to them on a set cycle using AFNET/AFIN and commercial connections. To meet the intent of the objective, the system needs to meet the following requirements using the topic objective and description: 1. The tracking system needs to be modular and deployable in a kit like system capable of quickly being attached to assets using a variety of sensors. 2. The kit needs to be MIL-STD-810G/hardened enough to withstand high and low temperatures, dirt, dust, sand, rain, snow, and ice. 3. The kit needs to be MIL-STD-810G/hardened enough to withstand drops, falls, and impacts. 4. The kit needs to be capable of receiving power from an outlet ranging from 110-240V and operating up to 8 hours on battery power. 5. The system must offer the ability to be powered via a battery source capable of meeting the MIL-STD-810G standard. 4. 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. 5. The sensor must be capable of adhering to multiple types of surfaces with adhesive capable of withstanding exposure to the elements and chemicals like jet fuel, hydraulic fluid, etc. 6. The system needs to operate separate from a network connection while track and report on usage rates, repair cycles, status, historical records, and pinpoint locations of the asset to reduce manpower waste while providing the ability to deploy and track assets down to the last tactical mile. 7. The tracking needs to be capable of operating as often as near-real time with options to report at longer intervals using a variation of sensors and devices (Bluetooth, RFID, GPS, etc.). 8. 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 PHASE I: Complete a feasibility study that should, at a minimum, complete the following: 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 technologies 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 current/emerging Air Force assets/systems. 5. Determine the necessary requirements for any technologies deemed incompatible with each other and make them compatible with 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. 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 civilian users 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, the system should be expandable enough to operate on a cloud based system capable of consuming, processing, and analyzing data from multiple systems as well as operating independently from the main system during transport but capable of reconnecting to the main system upon return. The system needs to be capable of connecting with current/emerging Air Force systems using a rest API to enable communications with other Air Force Systems and the capability to data dump into Air Force Systems using different formats as applicable. The system needs to be compatible with current Air Force systems, programs, and apps with the ability to evolve and connect to emerging Air Force systems, programs, and apps. 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 use current 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. DAFMAN 17-1301 KEYWORDS: AF Assets Tracking; Common Operating Picture (COP); Near-Real Time; Pinpoint Locations; Reporting
