DRAFT_PWS FTAMS 20260209.docx
DOCX document 56 KB Posted
- Solicitation number
- RFI-FTAMS-001
About this file
This is a Performance Work Statement (PWS) for Flying Training Analysis Modeling and Support (FTAMS) dated February 9, 2026, issued by the Air Education and Training Command (AETC). The contractor must develop and sustain a comprehensive, web-based analytical tool with a probabilistic modeling capability to forecast the impact of resourcing and requirement decisions across AETC's flying training enterprise. The system must analyze Undergraduate Pilot Training (UPT), Pilot Instructor Training (PIT), Euro-NATO Joint Jet Pilot Training (ENJJPT), Fighter Bomber Fundamentals (FBF), Combat Systems Operator (CSO), and Formal Training Unit (FTU) operations. The tool requires secure cloud access via CAC authentication, dashboards displaying analysis results, and the ability to perform "what-if" analyses accounting for resources (aircraft, instructor manning, simulators), syllabus composition, operational factors (utilization rates, mission capable rates, attrition), and lifecycle transitions (fleet divestiture, new aircraft delivery). The system must integrate aircraft maintenance data, support asset lifecycle management, and interface with the Department of the Air Force Data Fabric Envision platform to automatically pull pilot training and maintenance data and push analytical results.
The contractor shall provide development, maintenance, sustainment, configuration, user training, documentation, and helpdesk support with defined service level agreements including modifications within ten business days, study scenario analysis within one business day, incorporation of government data within two business days, and customer support responses within four business hours during normal business hours (Monday-Friday, 8:00 AM–5:00 PM CST). Additional responsibilities include sustaining the ENJJPT Management Database, supporting Special Operations Forces training analysis, conducting monthly analyses reporting, providing user manual updates, participating in weekly status reviews, and supporting AETC's annual Programmed Flying Training (PFT) and Program Objective Memorandum (POM) processes. The primary place of performance is the contractor's facility in Addison, Texas, with estimated travel to JBSA Randolph, Laughlin AFB, Sheppard AFB, Vance AFB, Columbus AFB, and Kirtland AFB. The work is unclassified; no security clearances are required, but contractor personnel must comply with DFARS 252.204-7012 safeguarding requirements, NIST SP 800-171 security controls for Controlled Unclassified Information, OSHA standards, and DoD safety protocols. The contractor must submit a Quality Control Plan prior to award and report direct labor hours and costs via SAM by October 31 of each fiscal year.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Performance Work Statement (PWS) Flying Training Analysis Modeling and Support
09 Feb 2026
1. DESCRIPTION OF SERVICES.
This Performance Work Statement (PWS) defines the requirement for a contractor-provided analytical capability to support the Air Education and Training Command (AETC). AETC requires an analytical tool and associated services to model and analyze its flying training enterprise. The Air Education and Training Command A9 Division (AETC/A9) is responsible for providing Headquarters (HQ) Air Education and Training Command (AETC) and 19th Air Force (19 AF) with aircrew training program analyses. 19 AF is responsible for executing operational-level command and control of all formal aircrew flying training missions within AETC and providing Airmen with a 5th generation, cross-domain, warrior mindset to sustain the United States Air Forces combat capability. HQ AETC and 19AF have a requirement to utilize an analytical tool to forecast the impact of resourcing and requirement decisions across AETC’s Flying Training enterprise.
The required solution shall be a probabilistic model that accounts for process variance within AETC’s Undergraduate Pilot Training (UPT), Pilot Instructor Training (PIT), Euro-NATO Joint Jet Pilot Training (ENJJPT), Fighter Bomber Fundamentals (FBF), Combat Systems Operator (CSO), and Formal Training Unit (FTU) operations. The solution must be tailorable to both Undergraduate and Graduate user levels and requirements. The solution must be accessible from a secure cloud environment via CAC authentication, providing users the capability to perform pilot training analyses from an internet browser. The solution shall include a dashboard that displays the results of analyses in a variety of charts, providing the user with the ability to quickly visualize and understand the results. The tool shall allow process owners the ability to integrate potential ranges of all factors that influence the Flying Training pipeline capacity.
In addition to the AETC requirement, the Office of the Under Secretary of the Air Force for Installations, Environment, and Operational Energy (SAF-IE) has the need to evaluate flying training fuel consumption metrics and energy savings plans and programs. SAF-IE will use the provided analytical capability to determine and evaluate fuel consumption data for FTU missions under operational control by AETC and 19AF.
2. SCOPE.
The scope of this PWS is to provide and sustain a comprehensive analytical tool, to include a web-based interface, and to provide pilot training pipeline studies and analyses using this tool. This capability must include integrated modules for analyzing aircraft maintenance data and performing asset lifecycle management analysis. The Contractor shall provide all development, maintenance, sustainment, configuration, user training, documentation, and helpdesk support for the provided system.
The system must provide AETC with a high-fidelity representation of AETC’s UPT, PIT, ENJJPT, FBF, CSO, and government- selected FTU operations at each of their respective training locations, and each respective pilot training syllabi, operating current Mission Design Series (MDS) aircraft training systems.
The system shall be used to conduct “what-if” analyses across multiple dimensions and forecast the outcomes of specific study scenarios, such as the number of sorties and/or graduates realized, before resources are expended. Analyses must be able to account for a variety of inputs, including but not limited to:
· Resources: Aircraft inventories and availability, instructor manning (including instructor-to-student ratios), simulator inventories, maintenance manning, and facility/airspace availability (runways, ranges, etc.).
· Syllabus & Production: Training syllabi composition and duration, student production requirements, class loading schedules, and student attrition rates.
· Operational Factors: Aircraft utilization (UTE) rates, Mission Capable (MC) rates, sortie attrition rates, unplanned events (e.g., fleet groundings, weather, pandemics), and maintenance profiles.
· Lifecycle & Transition: Fleet divestiture profiles, new aircraft delivery schedules (e.g., T-7A transition), and subcomponent availability.
Specific study scenarios can include, but are not limited to, the effects of grounding an aircraft fleet, a comparison of legacy and future UPT constructs, or an examination of strategic basing decisions plans. In addition to performing analyses with the provided analytical tool, the contractor shall work with the 19AF and AETC staffs to support and sustain the generation of Programmed Flying Training (PFT) and the Command’s Program Objective Memorandum (POM) input to the USAF budget using the model's capabilities. The Contractor shall provide a system capable of supporting analysis of T-6A, T-38C, and T-7A maintenance data.
3. REQUIRED SUPPORT CAPABILITIES.
The Contractor shall provide an integrated analytical system that meets the requirements outlined in this PWS. This system must provide a holistic view of aircraft maintenance data, its impact on aircraft availability, and the resulting effects on training production forecasts. This capability shall include, but is not limited to, the following asset management and resource planning functions:
| • | Optimized maintenance scheduling |
| • | Forecasted aircraft turnaround times |
| • | Modification planning and tracking |
| • | Predicted life expectancy of assets |
| • | Optimized distribution of assets across operating locations |
| • | Utilization tracking and analysis |
To ensure the system accurately represents real-world AETC flying training operations, the Contractor shall provide all necessary support to develop, maintain, sustain, and configure the integrated system architecture as required by AETC and 19AF. This includes collecting data, modeling and analyzing study scenarios, reporting results, supporting the analysis of T-38C subcomponent availability, and tracking T-6A fleet health to provide accurate Aircraft Availability (AA) estimates. The Contractor is required to be able to access the Department of the Air Force (DAF) Data Fabric, to include the Envision platform. At a minimum, the Contractor will be required to automatically pull pilot training and maintenance data from Envision for the creation of baseline inputs, and be required to push analytical results into Envision, including tables, charts, and dashboards. If the Government requests the capability, the Contractor will be required to port the analytical tool into Envision.The Contractor shall:
a. Modify the integrated system architecture as required by AETC. Make modifications within ten (10) business days after a request is made and deliver all related files and documentation to AETC/A9 and 19 AF via e-mail or compact disk (CD) within ten (10) business days after completion.
b. Conduct study scenario analysis using the integrated system within one (1) business day after AETC’s request. Provide all input and result files to AETC/A9 and 19 AF via e-mail within one (1) business day upon completion of a study.
c. Incorporate Government-provided data into the integrated system baseline scenarios and provide them to the Contracting Officer’s Representative (COR) within two (2) business days after receipt.
d. Provide training to Government personnel for the operation of the integrated system as required, responding to requests via telephone or e-mail within one (1) business day.
e. Provide the Government with updated Users’ Manuals for the operation of the integrated system within ten (10) business days after a model modification release.
f. Review the status of analyses and system modifications with AETC via telecom weekly or as pre-coordinated with AETC/A9 and 19 AF.
g. Maintain the ability of the system to provide full undergraduate flying training resourcing and programming capability. Begin modification of any related modules within one (1) business day after AETC’s request.
h. Provide a monthly report summarizing all analyses performed in the prior month to AETC/A9 on the first working Monday of every month.
i. Provide analyses of capacity factors affecting pilot training production by the ENJJPT program at Sheppard AFB, TX, beginning analysis within one (1) business day of a request.
j. Sustain the ENJJPT Management Database (EMD), providing support as needed within one (1) business day.
k. Analyze capacity factors impacting Special Operations Forces (SOF)/Personal Recovery (PR) training production and other FTUs as required, beginning analysis within one (1) business day of a request.
l. Work with wing Operations Analysts at the FTUs to align aircrew instructor requirements and capabilities to support programmed student training flow and required training events.
m. Work with 19AF and AETC staffs to fully support AETC’s mission and annual PFT and POM processes, updating the integrated system accordingly.
n. Provide feedback to AETC/A9 and 19 AF on written reports and presentations to ensure a study’s assumptions were accurately represented within the integrated system, within one (1) business day after receipt.
o. Provide support to, or design and develop new analytical models for, SAF-IE to evaluate productivity related to fuel consumption.
p. Provide user licenses for the web-based interface and any associated software as directed
q. Be available to answer Government inquiries during normal business hours (8:00 AM - 5:00 PM CST), responding via telephone or e-mail within four (4) business hours.
4. GOVERNMENT PROVIDED RESOURCES
4.1. The Government will provide the Contractor with data for the EDM baselines and specific “what-if” scenarios. This data includes, but is not limited to:
a. AETC training syllabi via e-mail as changes occur.
b. The previous month’s sortie attrition rates via e-mail by the 15th calendar day of the month.
c. Current instructor, aircraft, simulator, and student inventories (provided by various HQ AETC organizations).
d. Current AETC processes and staff coordination procedures used to develop annual PFT and POM programs of record.
4.2. If onsite personnel are required, the government shall provide contractor personnel with workspace, office furniture and supplies, computer resources, and telephones necessary to perform the task, commensurate with those provided government employees. DoD Common Access Card (CAC), (AFI 36-3026), used for contracts for more than six months and requirement exists for access to the government computer systems and software. CAC applications are accomplished by Trusted Agents via the Contractor Verification System (CVS). CACs shall be returned within seven business days of the end of the contract or separation of a Contractor employee.
4.3. The contractor shall have access to government regulations, specifications, standards, technical manuals, design documentation, and task documentation.
5. CONTRACTUAL REQUIREMENTS
5.1. Customer Support.
The Contractor shall provide the technical support as listed below via telephone and/or e-mail:
If EDM Online is not accessible or not functioning properly, the Contractor shall respond within four (4) hours after notification during normal work hours, which for the purpose of this contract shall be Monday – Friday (M-F) 8:00 A.M. – 5:00 P.M. CST. AETC does not expect the vendor to respond after normal duty hours. A fix shall be implemented within 3 business days after notification.
5.2. Non-Personal Services.
The Government shall neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor's responsibility to notify the Procuring Contracting Officer (PCO) immediately.
5.3. Place of Performance.
The primary place of performance shall be at the Contractor’s facility (Addison TX). Should the contractor approve telework for its employees, the telework shall be consistent with meeting mission needs. There shall be no additional cost to the Government. The contractor shall determine if an employee is eligible to participate in telework on either a regular or a situational basis.
Contractor employees who are eligible to telework must be fully trained on telework procedures including information technology and data security, and safety requirements consistent with DoWI 8500.01.
If a contractor employee requires access to Government furnished equipment (GFE), the GFE shall be used for official use and authorized purposes only. Family members and friends of employees are not authorized to use GFE and materials. GFE must be returned to the Government at the conclusion of the employee’s need for the equipment to perform his or duties on the contract, or at the Government’s request.
For elevated privileges, each contractor employee must fill out a DD Form 2875.
5.4. Normal Hours of Operation.
Normal hours of operation are Monday through Friday between 8:00 AM and 5:00 PM CST with the exception of Federal Holidays.
5.5. Travel
Travel to government facilities may be required. All travel requirements (including plans, agenda, itinerary, or dates) shall be pre-approved by the government (subject to local policy procedures) and conducted IAW the JTR. Travel shall be cost- reimbursable to the contractor. No profit shall be paid on travel. The table below contains estimates for the travel required for each year of the contract:
Estimated Travel
| Destination |
| No. of Trips |
| No. of Travelers |
| Days per Trip |
| JBSA Randolph |
| 5 |
| 2 |
| 3 |
| Laughlin AFB |
| 1 |
| 2 |
| 3 |
| Sheppard AFB |
| 1 |
| 2 |
| 3 |
| Vance AFB |
| 1 |
| 2 |
| 3 |
| Columbus AFB |
| 1 |
| 2 |
| 3 |
| Kirtland AFB |
| 2 |
| 2 |
| 3 |
5.6. Security
This effort shall be unclassified, and the Contractor personnel shall NOT have access to classified documents. No classified work shall be accomplished under this PWS and security clearances are not required. Performance under this PWS may generate USG proprietary data categorized as "Controlled Unclassified Information" (CUI) or protected under the Privacy Act of 1974. Contractor personnel, although recognized as Contractor employees and under the complete control of the Contractor, shall be required to comply with the directives and requirements of the base commander or authorized representative as to security standards and regulations applicable to the work site. Contractor personnel involved in civil crimes and/or other incidents of misconduct may be barred from the site. The Contractor shall inform the CO of any information they have relating to crimes. The Contractor shall comply with DFARS Clause 252.204-7012, 'Safeguarding Covered Defense Information and Cyber Incident Reporting,' which requires the implementation of NIST SP 800-171 security controls for all Covered Defense Information (CDI) processed, stored, or transmitted in the performance of this contract.
5.7. Safety
Contractor Compliance: The Contractor and its subcontractors shall comply with Public Law 91- 596 (Occupational Safety and Health Act (OSHA)) and the Environmental, Safety, and Occupational Health (ESOH) (DODD 4715.1E). These requirements shall be incorporated into the Contractor's safety and health program. The Department of Defense (DoD) participates in the OSHA Voluntary Protection Program (VPP). Contractor personnel performing services on a DoD installation shall participate in the local VPP. Information on the VPP is available at http://www.osha.gov/dcsp/vpp/index.html.
5.8. Mishap Notification and Investigation. The Contractor shall notify (via telephone) the cognizant contracting officer, the COR, and/or other applicable members within four (4) hours after all mishaps or incidents. The Government person notified by the Contractor shall in-turn notify the Safety office. Contractor notifications made after duty hours shall be reported to the appropriate installation Command Post. If requested by the cognizant contracting officer, the COR, and/or the cognizant program manager, the Contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records until released by the investigating safety office. If the Government investigates the mishap, the Contractor and the subcontractors shall cooperate fully and assist the Government personnel until the investigation is completed.
5.9. Data and Intellectual Property Rights. The Government’s rights in all deliverables, including but not limited to, software applications, source code, databases, software documentation, training materials, forms, modules, user guides, reports, meeting minutes and other materials and technical data shall be IAW the rights described in DFARS 252.227-7015 and DFARS 252.227-7020 which shall be incorporated by reference to this contract. The contractor shall seek review and approval from the contracting officer prior to using any proprietary solutions in any of the deliverables delivered under this contract.
6. QUALITY
This section describes the Quality Control components for this effort. The following sub-sections provide details of various considerations on this effort. Only the COR or the designated alternate COR has the authority to inspect, accept, or reject performance objectives.
6.1. The Contractor shall develop a Quality Control Plan (QCP) and maintain an effective quality control program to ensure services are performed in accordance with the contract and this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non- recurrence of defective services. The Contractor's QCP is the means by which to it ensures work complies with the requirement of the contract. Contractor's attention is directed to the contract’s clause entitled “Inspection of Services”. Contractor shall submit a Quality Control Plan (QCP) to the CO, for acceptance, prior to contract award. The QCP shall be submitted as part of the technical proposal for evaluation. Changes to the QCP during contract performance shall be submitted to the CO for acceptance no later than ten (10) calendar days prior to any changes being affected by the Contractor.
6.2. The Contractor's quality inspection documentation (i.e., metrics, reports, etc.) shall be made available to the COR monthly. The reports should provide information on the methods of inspection, what was inspected, discrepancies found, and actions taken to correct and preclude recurrence.
7. SERVICES SUMMARY.
| Performance Objective |
| PWS Paragraph |
| Performance Threshold |
| 1. Modify the integrated system architecture as required by AETC |
| 3.1.a |
| The Contractor shall make modifications to the model’s architecture within ten (10) business days after request is made, with no more than two (2) discrepancies allowed per quarter. |
| 2. Maintain full undergraduate flying training resourcing and programming capability, making any modifications as required, including support to the annual PFT and POM processes. |
| 3.1.g |
| The Contractor shall begin modifications within one (1) business day after AETC’s request and provide support within one (1) business day as needed, with no more than two (2) discrepancies allowed per quarter. |
| 3. Model and analyze AETC study scenarios, including UPT, ENJJPT, SOF/PR, and other FTUs. |
| 3,1,b |
| The Contractor shall begin conducting the study scenario analysis within one (1) business day after AETC’s request. No more than two (2) discrepancies allowed per quarter.. |
| 4. Provide all model input and result files related to AETC study scenarios.. |
| 3 |
| The Contractor shall provide all model input and result files to AETC/A9 and 19 AF via e-mail within one (1) business day after completing the study. No more than two (2) discrepancies allowed per quarter. |
| 5. Sustain the ENJJPT Management Database (EMD). |
| 3.1.k |
| The Contractor shall provide support within one (1) business day as needed. No more than two (2) discrepancies allowed per quarter. |
| 6. Update integrated system baseline inputs |
| 3.1.c |
| The Contractor shall incorporate data and provide updated baselines to the COR within two (2) business days after receipt. No more than two (2) discrepancies allowed per quarter. |
| 7. Provide training on the operation of the integrated system |
| 3.1.d |
| The Contractor shall respond to users' request for training via telephone or e-mail within one (1) business day after receipt of inquiry. No more than two (2) discrepancies allowed per quarter. |
| 8. Provide a monthly report on all analyses performed. |
| 3.1.i |
| The Contractor shall provide the report to AETC/A9 on the first working Monday of every month. No more than two (2) discrepancies allowed per quarter |
| 9. Provide updates of User’s Manuals. |
| 3.1.e. |
| The Contractor shall provide the manuals to AETC/A9 and 19 AF within ten (10) business days after model modification release. No more than two (2) discrepancies allowed per quarter |
| 10. Provide system status reviews. |
| 3.1.f |
| The Contractor shall review the status of analyses and modifications with AETC via telecom every Tuesday or as pre-coordinated |
| 11. Advise on written reports |
| 3.1.o |
| The Contractor shall provide feedback on AETC's written reports within one (1) business day after receipt. No more than two (2) discrepancies allowed per quarter. |
| 12. Provide customer support to users during normal business hours |
| 3.1.r |
| The Contractor shall respond to users via telephone or e-mail within four (4) business hours after receiving inquiries. No more than two (2) discrepancies allowed per quarter. |
8. PERFORMANCE OF SERVICES DURING CRISIS
IAW DoDI 1100.22, Policy and Procedures for determining Workforce Mix and DFARS 237.76, Continuation of Essential Contractor Services, unless otherwise directed by an authorized government representative, it is determined that services as identified in this PWS are NOT essential for performance during a crisis. In the event of an unforeseen natural or military crisis, i.e., hurricane, insurrection, etc., the contractor’s primary responsibility is to safeguard it personnel and secure any equipment.
9. CONTRACTOR MANPOWER REPORTING
The Contractor shall report all un-loaded direct labor hours and unburdened direct labor dollars required for performance of services provided under this contract. After the prime contractor has reported its data, subcontractors are required to report their information. The prime contractor has overall responsibility for ensuring subcontractors enter their respective data. The Contractor must completely fill in all required data fields.
The System for Award Management (SAM) secure data website (https://www.sam.gov) is the collection point for this information. Data for Air Force service requirements must be input at the SAM link at https://www.sam.gov.
9.1. Reporting inputs shall be for the direct labor executed during each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data for the FY shall be reported no later than 31 October of each calendar year. Notify the contracting officer via e-mail when all prime contractor and subcontractor input is complete.
9.2. Information from the secure web site is proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time shall any data be released to the public with the contractor name and contract number associated with the data.
File details come from the government source that posted it. Updated .