The Department of the Air Force Kessel Run Flight Operations Program Management Office (PMO) is soliciting White Papers for the Aerospace Readiness Enterprise System (ARES) prototype. ARES is a next-generation, cloud-based enterprise solution to unify aircrew scheduling, standardization and evaluation (stan/eval), and training management, replacing Patriot Excalibur (PEX), Puckboard, and G/TIMS. The RFWP outlines a five-step competitive acquisition process for Other Transaction (OT) Agreements, aiming to award up to four prototype OTAs. These prototypes will be developed within 90 days in the Air Force's Operational Enterprise Architecture (OpsEA) Salesforce environment. A challenge-based “bakeoff” competition will follow to select a single prototype for a follow-on Production OT Agreement without further competition. The total obligated amount for the prototype completion is $500,000, with deliverables including transition documentation and plans for data segregation and release. The RFWP also details administrative procedures, terms of agreement, data rights, funding, and cybersecurity requirements.

The Department of the Air Force (DAF) is launching the Aerospace Readiness Enterprise System (ARES) prototype project to modernize and unify its fragmented aircrew readiness management systems. This initiative, conducted under a prototype Other Transaction Agreement (OTA), seeks to integrate scheduling, training, and standardization/evaluation (stan/eval) functions into a single, secure, cloud-based platform leveraging the OpsEA Salesforce environment. The DAF aims to address current challenges such as manual processes, limited data interoperability, and outdated technical architectures. Key objectives include modernizing readiness management, optimizing resource allocation through AI/ML, enhancing decision-making with predictive analytics, improving user experience, and integrating ARES into the broader DAF BATTLE NETWORK. The prototype must demonstrate operational suitability, scalability, and cybersecurity compliance (NIST SP 800-171 at IL-4 with a path to IL-6). A successful prototype may lead to a follow-on production OTA to fully deploy the ARES solution across the DAF.

Attachment 2: ARES Offeror OT Agreement Eligibility Form outlines the requirements for offerors to certify their eligibility for a prototype project under 10 U.S.C. § 4022(d). The form is crucial for participation in the Aerospace Readiness Enterprise System (ARES) prototype and production phases, with the Agreements Officer making the final determination. Offerors must provide detailed information including legal name, SAM UEI, CAGE Code, address, and point of contact. Eligibility paths include significant participation by a Nontraditional Defense Contractor (NDC), participation by Small Businesses or NDCs, or cost-sharing of at least one-third of the total project cost. The document also requires NDCs to self-certify their status and provides definitions for NDC and "Significant Extent." Failure to complete the form may render a proposal ineligible.

The ARES Bidder Response Template provides instructions for offerors to comprehensively address mandatory and high-priority requirements for the ARES project. The template, an Excel file, requires detailed responses in specific columns (H, I, J, K, L) within TAB 1. Offerors must describe their solution approach (minimum 100 words for mandatory/high priority), differentiate their solution, and assess implementation risks, including technical, integration, and schedule risks, along with mitigation strategies. Compliance levels range from "Full Compliance" to "Non-Compliant." The document outlines numerous functional requirements across Training Management, Stan/Eval, and Scheduling, as well as non-functional requirements for System Design, Security, Interfaces, Performance, Resilience, and Extensibility. Key submission requirements include completing all columns, providing specific and detailed responses with verifiable evidence, and flagging unaddressable requirements. The purpose is to enable the Government to thoroughly evaluate proposed solutions for the ARES project.

The Aerospace Readiness Enterprise System (ARES) is the Department of Air Force's (DAF) next-generation enterprise solution, aiming to replace legacy systems like Patriot Excalibur (PEX), Puckboard, and Graduate/Training Integration Management System (G/TIMS). ARES will provide a unified, cloud-based platform for scheduling, standardization and evaluation (Stan/Eval), and training management for Mobility Air Forces (MAF), Combat Air Forces (CAF), Air Education and Training Command (AETC), and United States Space Force (USSF) operations. The system is designed to be scalable, modular, and integrated, centralizing these functions into a single digital ecosystem while complying with DAF policies. It will support over 149,000 users and be initially deployed at Impact Level 4 (IL-4) with a pathway to IL-6. Key functional requirements include comprehensive training management, Stan/Eval capabilities, and advanced scheduling features. Non-functional requirements cover technical architecture, security (IL-4 to IL-6 roadmap, Zero Trust), system interfaces with other DoD systems (ARTEMIS, MilPDS), scalability, resilience, and extensibility for future joint and coalition partners. Prototype deliverables include plans for IL-4 to IL-6 transition, data segregation, and DDIL/mobile access, with success measured by technical feasibility, functional adequacy, user acceptance, scalability, integration, security compliance, and extensibility.

The Department of the Air Force's Air Force Life Cycle Management Center (AFLCMC/C3C) is issuing a Documentation Request and Disclaimer Form for Solicitation FA873026RB001, concerning the Aerospace Readiness Enterprise System (ARES) under an Other Transaction Authority (OTA). This document outlines the terms for contractors to receive Controlled Unclassified Information (CUI) to aid in responding to the solicitation. Contractors must guarantee that the information will be used solely for the stated purpose, destroyed upon completion, and not published, sold, transferred, or used for foreign governments or contracts. The form requires the contractor's representative to bind their company to these rules, providing contact and company details, including CAGE Code and mailing address, along with an authorized signature and date.

DD Form 2345, the Militarily Critical Technical Data Agreement, is crucial for entities seeking access to unclassified military technical data from the U.S. or Canadian governments. This form, required for the Joint Certification Program, outlines the certification process for contractors, universities, or individuals. Applicants must provide detailed entity information, CAGE codes, and designate data custodians, specifying their citizenship/residency. A key section requires a detailed description of relevant business activities to justify the need for technical data, including prime/sub-contractor status, NAICS/FSC codes, and registration with relevant trade control programs. The agreement mandates adherence to U.S. and Canadian export control laws, ensuring data is not disseminated unlawfully and is used for legitimate government contract bidding or performance. It also prohibits access by debarred or ineligible individuals. Authorized representatives must certify the accuracy of all information, acknowledging penalties for false statements. The form includes sections for official approval, certification numbers, and expiration dates, emphasizing strict compliance with regulations like U.S. DoDD 5230.25 and Canada's TDCR to maintain certification.