The Kessel Run Flight Operations (Flight Ops) Aerospace Readiness Enterprise System (ARES) is seeking offerors for a prototyping phase. Submissions, limited to ten pages, must address compliance with 10 U.S.C. § 4022, teaming structure, proposed prototype solution, quality management system, and qualifications for the OpsEA Salesforce development sandbox. The prototype must be hosted on the OpsEA platform, built at the IL-4 level, and avoid IL-6 restricted cloud services. It must also feature auditability, IDS integration, access control, and support training syllabus management and event scheduling. Evaluation criteria prioritize compliance, technical approach, and demonstration of capability, with cost/price and past performance not being factors. Deliverables during the prototyping phase include an IL-4 to IL-6 roadmap, data segregation plan, DDIL plan, and release documentation. Questions from industry are due by October 31, 2025.

This document outlines the Kessel Run Flight Operations (Flight Ops) Aerospace Readiness Enterprise System (ARES) "Entry to Prototype Phase – Instruction to Offerors." It details the requirements for vendors to submit written proposals to enter the ARES prototyping phase. Proposals must be in PDF format, not exceed ten pages, and adhere to specific formatting guidelines. Key evaluation criteria include compliance with 10 U.S.C. § 4022, proposed teaming structure, prototype solution against defined threshold requirements, quality management system, and compliance with minimum qualifications for working within the OpsEA Salesforce development sandbox. The document specifies technical, accessibility, syllabus management, and scheduling threshold requirements for the prototype. Evaluation methodology focuses on compliance, lowest risk, and greatest capability, excluding cost/price and past performance. It also details minimum developer requirements for Salesforce sandbox access, including SDK knowledge checks and Salesforce certifications. Finally, it lists prototype phase data deliverables, such as IL-4 to IL-6 Roadmap, Data Segregation Plan, DDIL Plan, and Release Documentation, and provides a deadline for industry questions.

The Air Force's ARES Prototype Requirements document outlines the development of the Aerospace Readiness Enterprise System (ARES), an enterprise solution for scheduling, standardization and evaluation (stan/eval), and training management. This prototype aims to replace legacy systems like PEX, Puckboard, and G/TIMS. The prototype must be completed within 90 days of contract award and will be evaluated based on threshold (pass/fail) and objective criteria. Key threshold requirements include hosting on the Operations Enterprise Architecture (OpsEA) platform, IL-4 level build with a path to IL-6, auditability, CI/CD DevSecOps hardened pipeline compliance, intrusion detection integration, and access control. Functionally, the prototype must support syllabus management, event scheduling (assigning individuals, verifying availability, creating/editing events), and routine qualification tracking. Additionally, the prototype needs to demonstrate extensibility and scalability for future DAF-wide, Joint, and Allied use cases through a roadmap, data segregation plan, and a whitepaper on DDIL/mobile access. Objective criteria cover enhanced accessibility (mobile, notifications), advanced syllabus management, extensive scheduling capabilities (AI-enhanced, conflict resolution), comprehensive stan/eval functions, waiver management, training class management, pipeline tracking, continuation training, detailed reporting and analysis, documentation, safety automation, go/no-go verification, and a robust personnel manager.