Aerospace Readiness Enterprise System (ARES)

Solicitation / RFP / RFQ

This Request for White Papers (RFWP) is a multi-step open project announcement for the Aerospace Readiness Enterprise System (ARES) prototype. ARES is a next-generation, cloud-based enterprise solution for the Department of the Air Force that unifies aircrew scheduling, standardization and evaluation (stan/eval), and training management. It aims to replace legacy systems and enhance operational readiness and lethality.

• The initial step requires submission of White Papers.

• The acquisition process involves five steps, with potential for a follow-on Production OT Agreement.

• Prototypes will be built in the Air Force Operational Enterprise Architecture (OpsEA) Salesforce environment.

• Deliverables for the prototype phase include Transition Out Documentation, IL4 to IL6 Plan, Data Segregation Plan, DDIL Plan, and Release Documentation.

• This is a competitive Other Transaction (OT) acquisition.

• Up to four (4) prototype OT Agreements may be awarded.

• The total obligated amount for the ARES Prototype ALIN (0001) is $500,000.00.

• Period of Performance for each prototype OT Agreement is 120 days (90 for development, 30 for test and evaluation).

• A single follow-on Production OT Agreement may be awarded without further competition.

• White Papers are due by January 9, 2026.

• Evaluation is a multi-step process including White Paper evaluation, prototype development, and a prototype bake-off.

• Key evaluation criteria for White Papers include OT Eligibility, Mandatory Threshold Requirements Compliance, SOO Alignment, Organizational Structure, Systems Engineering Approach, and Program Management Approach.

• Open to traditional and non-traditional defense contractors.

• Offerors must be registered in the System for Award Management (SAM) and have a Unique Entity Identifier (UEI).

• No costs incurred in the development and negotiation of proposals are recoverable from the Government.

• Information classified as "Proprietary", "Confidential", "CUI", "Secret", or "Top Secret" shall not be submitted.

• A Bidder's Library will be available for supplementary information.

Form / Attachment / Pricing Sheet

This document, "Attachment 4: ARES Consolidated Requirements Document (CRD)", outlines the functional and non-functional technical requirements for the Aerospace Readiness Enterprise System (ARES). ARES is a next-generation enterprise solution for the Department of Air Force (DAF) aimed at unifying and modernizing aircrew scheduling, standardization and evaluation (stan/eval), and training management.

• System Overview: Details the purpose of ARES to replace legacy systems (PEX, Puckboard, G/TIMS) with a unified, cloud-based platform.
• Desired End State: A scalable, modular, integrated system centralizing training, stan/eval, and flight/resource scheduling.
• Functional Requirements: Covers Training Management, Standardization and Evaluation (Stan/Eval) Management, and Scheduling capabilities, detailing specific functions like syllabus management, qualification tracking, event scheduling, and personnel management.
• Technical Requirements (Non-Functional): Addresses system design, architecture, security, performance, scalability, resilience, and extensibility.
• Prototype-Specific Deliverables: Outlines deliverables for the ARES prototype phase, including roadmaps, plans, and the prototype release.
• Success Criteria: Defines metrics for successful ARES prototype deployment, including technical feasibility, functional adequacy, user acceptance, scalability, integration, security compliance, and extensibility.
• Key Performance Indicators (KPIs): Lists metrics for measuring ARES performance and effectiveness, such as schedule creation time, user training time, and system response time.

This document is crucial for potential bidders as it defines the comprehensive requirements for the ARES system. It details the scope of work, technical specifications, and performance expectations, which are essential for understanding the system's capabilities and for developing accurate proposals or solutions. Bidders can use this document to assess their ability to meet the government's needs and to identify specific areas where their offerings align with the ARES program objectives.

Form / Attachment / Pricing Sheet

This document is the DD Form 2345, "Militarily Critical Technical Data Agreement," used in conjunction with the Joint Certification Program (JCP). It is required for entities or individuals seeking to receive or access militarily critical technical data. The form certifies that the applicant understands and agrees to comply with U.S. and Canadian export control laws and regulations regarding the dissemination of such data.

• Submission Type: Applicants must indicate if this is an INITIAL submission, REVISION, or RENEWAL.
• Entity/Individual Data: Requires the name and address of the entity or individual, along with their CAGE code.
• Data Custodian Information: Details for primary and alternate custodians responsible for managing the technical data, including name, title, telephone, and email.
• Business Activity Description: A description of the applicant's relevant business activities, including their role as a prime or sub-contractor, the type of equipment/material/service they provide, and whether it relates to the USML or CCL.
• Certifications: The applicant certifies their understanding and compliance with export control laws, their eligibility to receive the data, and that they are not debarred or suspended from government contracts.
• Representative Certification: An authorized representative must certify the accuracy of the information provided.
• Certification Action & Official Use: Sections for the Joint Certification Program Office (JCPO) and DOD officials to approve the certification, assign a number, and set an expiration date.

Bidders who need to access or receive militarily critical technical data to bid on or perform a contract will need to complete and submit this form to obtain certification. This certification is a prerequisite for receiving such data, ensuring compliance with export control regulations. The form outlines the specific information and certifications required to demonstrate eligibility.

Form / Attachment / Pricing Sheet

This document is a bidder response template (Excel file) designed to capture offerors' proposed solutions for the ARES opportunity. It requires bidders to detail how their solution addresses mandatory and high-priority requirements, explain their differentiation, assess implementation risks, and state their compliance level.

• Instructions Sheet: Provides guidance on completing the template, defining requirement priorities (Mandatory - Red/Pink, High - Orange), and specifying required content for bidder solution approach (min. 100 words), differentiation, and risk assessment.
• TAB 1 Sheet: Contains a detailed list of requirements (Functional and Non-Functional) with columns for bidders to fill in their Solution Approach, Evidence/References, Differentiation Statement, Implementation Risk Assessment, and Compliance Level.
• Mandatory Requirements: Bidders must address all MANDATORY requirements without exception. These include specific items under System Design (Platform Hosting, Cloud Services, CI/CD Pipeline, Quality Management, Access Control, Accessibility, Security Classification, Intrusion Detection, Encryption, API Standards, System Integration, Legacy System Support, User Capacity) and Scheduling (Event Scheduling, Availability Verification, Calendar Views, Event Management, Flying vs Non-Flying, Personnel Data Integration, Platform Hosting, CI/CD Pipeline, User Capacity).
• High Priority Requirements: Bidders must also address all HIGH priority requirements.
• Compliance Levels: Offerors must select from: Full Compliance, Threshold Met, Partial Compliance, Planned Capability, or Non-Compliant.

This template is critical for bidders to structure and submit their technical proposals. It dictates the format and content required for demonstrating how their proposed solution meets the government's needs for the ARES opportunity. Failure to complete all required columns for mandatory and high-priority requirements may impact evaluation.

Form / Attachment / Pricing Sheet

This form is required for offerors to certify and support verification of their qualification to enter into a transaction for a prototype project under 10 U.S.C. § 4022(d). Failure to submit a completed form may render a proposal ineligible for award. The Government will verify self-certified Nontraditional Defense Contractor (NDC) status and may request additional documentation.

• Offeror Information: Legal name, SAM UEI, CAGE Code, Address, Point of Contact.
• Eligibility Path(s): Offerors must select at least one path: participation by an NDC, all significant participants are Small Businesses or NDCs, or offeror white paper includes significant cost-sharing.
• Team Composition: Workshare matrix detailing participants' tasks, level of effort, and deliverables.
• NDC Self-Certification: Details for entities claiming NDC status, including basis of certification and prior DoD contract history.
• Small Business Status: Information for primes relying on Small Business status, including NAICS codes and SAM representation.
• Certifications & Acknowledgements: Offeror certifies the accuracy of provided information and acknowledges the Agreements Officer's final eligibility determination.
• Optional Supporting Documentation Checklist: Lists required supporting documents such as NDC self-certifications, SAM small business evidence, cost share documentation, and workshare matrices.

This form is critical for determining eligibility for the opportunity. Bidders must accurately complete all applicable sections, provide required documentation for NDC and Small Business status, and clearly define their eligibility path and team composition. The Agreements Officer will make the final determination on eligibility.

Statement of Objectives (SOO)

This Statement of Objectives (SOO) aims to award prototype projects for the design, integration, configuration, and demonstration of the Aerospace Readiness Enterprise System (ARES) capability. ARES will leverage the Salesforce Operational Enterprise Architecture (OpsEA) platform to unify aircrew scheduling, training, and readiness management across the Department of Air Force (DAF), with scalability to non-aircrew personnel. The prototype will validate the operational suitability, scalability, and cybersecurity of the OpsEA/Salesforce environment.

This SOO covers the development, configuration, integration, testing, and engineering support for an initial ARES prototype on the OpsEA Salesforce platform. It emphasizes leveraging platform-native capabilities like workflow automation, analytics, AI, and API extensibility. The effort will use a Challenge-Based Acquisition (ChBA) approach with iterative demonstrations and user feedback.

• Modernize Readiness Management: Consolidate legacy capabilities into a single, cloud-based system for DDIL environments.

• Optimize Resource Allocation: Automate and optimize aircrew scheduling using AI and ML.

• Enhance Decision-Making: Provide predictive analytics and a shared situational awareness picture.

• Improve User Experience: Deliver an intuitive, mobile-accessible interface.

• Integrate into DAF BATTLE NETWORK: Ensure seamless interoperability within the DAF C3BM digital ecosystem.

• Technical Architecture: Develop to DoD IL-4 security requirements with a path to IL-6, using a DevSecOps pipeline.

• Accessibility: Implement RBAC and ICAM for access control, supporting mobile access.

• Scheduling: Provide comprehensive scheduling for up to 160 sorties per day per squadron, with role-tailored calendar views and AI-enhanced optimization.

• Syllabus and Training Management: Deliver end-to-end syllabus management and training progress tracking.

• Standardization & Evaluation (STAN/EVAL): Streamline stan/eval processes for routine qualifications.

• Waiver and GO/NO-GO Management: Enable end-to-end waiver management.

• Personnel, Accessions, and Pipeline Management: Enhance training class and pipeline management.

• Reporting, Analytics, and Intelligence: Elevate ARES to a strategic command and control platform with predictive insights.

• The prototype will have an anticipated 3-month performance period, with a maximum of 30 days for follow-on testing and transition.

• The performance period begins upon contractor access to the OpsEA/Salesforce development environment.

• Offerors must complete mandatory OpsEA/Salesforce sandbox training.

• The solution must comply with NIST SP 800-171 security requirements.

• A follow-on production Other Transaction Agreement (OTA) is anticipated upon successful prototype completion.

• The prototype will be awarded as a fixed-price Other Transaction Agreement (OTA).

Form / Attachment / Pricing Sheet

This document is a "Documentation Request and Disclaimer Form" required for the "Other Transaction Authority (OTA) for Solicitation: FA873026RB001 Aerospace Readiness Enterprise System (ARES)". It outlines the terms and conditions under which information obtained from the AFLCMC/C3C Program Office will be used by the contractor.

• Purpose of Information Use: For assisting the contractor in responding to Government requirements for the specified solicitation.
• Restrictions: Information received will not be used for purposes other than stated, will be destroyed upon completion of work, and will not be published or offered for sale.
• Distribution Limitations: Information containing Controlled Unclassified Information (CUI) is authorized for distribution only to U.S. Government agencies and U.S. Government contractors.
• Foreign Use Prohibition: Information is intended for U.S. domestic use only and will not be made available to foreign governments.
• Authorization: Requires the signature of an individual authorized to bind the company.
• Required Fields: Name of Individual, Title/Position, Phone, Email Address, Authorized Signature & Date, Company/Firm Name, CAGE Code, Mailing Address, City, State, Zip Code.

Bidders must complete and submit this form as part of their response to the solicitation. It signifies their understanding and agreement to the terms regarding the use, distribution, and protection of government-provided documentation and information.