Attachment 0015 - Consolidated Question and Answer Document.xlsx
XLSX spreadsheet 77 KB Posted
- Solicitation number
- W58RGZ-26-R-0026
About this file
This is a Consolidated Question and Answer (Q&A) Document for the Fort Rucker Aviation Maintenance (FRAM II) contract solicitation, addressing 110 industry questions submitted during the draft RFP phase. The document does not present new requirements but instead clarifies Government positions on questions raised by potential offerors regarding scope, workload data, pricing assumptions, and contract terms.
The Q&A confirms that the Government will not provide standardized workload assumptions, historical data baselines, or inclusion/exclusion matrices for pricing elements across the majority of questions posed. Instead, offerors are directed to develop their own technical, staffing, and pricing baselines based on PWS requirements and must clearly document all assumptions used in proposals. Key clarifications include: the Government will incorporate DFARS 252.228-7001 (Ground and Flight Risk Clause); the phase-in period will remain 60 days (16 November 2027–15 January 2028); MV-75 aircraft will be supported throughout the contract with maintenance assumptions estimated at 80% similarity to UH platforms and 20% to CH-47; UH-72A aircraft maintenance will continue for the full contract period; and the Government will not provide CBA information, seniority data, or MWO workload forecasts. Limited historical data was released for specific items including controlled exchanges (1,073–1,421 annually), ALSE/NVD quantities (2,946 vests, 654 devices), transient aircraft support (average 10 per year), local purchase requests (1,100 annually), and weekend flying frequency (average 19 events per year). The Government emphasized that any historical information provided is informational only and does not constitute a guarantee of future workload or bind the Government during contract execution.
View the file
Other files
Show all 36
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
Q&A
| Question Number | UCF Area | Attachment | Page Number | Paragraph Reference | Add Cross Reference | Discussion | Question | Government Response |
| 1 | A | N/A | 2 | A-1. | N/A | Anticipated Formal RFP Release | Will the government hold a Pre-proposal Conference and/or Industry Day for this RFP release? | No. |
| 2 | B | N/A | 3 | B-1 | For all CLIN Series XXX3 (UH-60M & UH-60A/L MEDEVAC Aircraft Maintenance) | Why is there no mention of HH-60M aircraft for MEDEVAC mission? This is a disconnect from Attachment 0003 | All references to UH-60A/L have been removed from the RFP. | |
| 3 | B | N/A | 3 | B-1, CLIN inclusions/exclusions | Att 0001 1.0-15.0 | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP does not clearly identify the scope boundaries for this pricing element. A Government clarification is needed so all offerors use the same inclusion/exclusion baseline and avoid post-award scope migration. Strategic alignment: A common data baseline supports the Army's broader data-centric decision-dominance direction by ensuring all offerors can price and solution from the same Government-held operational evidence. | Please provide an inclusion/exclusion matrix for each CLIN/SLIN identifying what labor, material, travel, subcontract, OEM/CLS, and Government-furnished support is included or excluded. If an inclusion/exclusion matrix is not issued, please identify which open-ended tasks are excluded from fixed-price bidding and require separate authorization. | The Government will not provide an inclusion / exclusion matrix. The Offeror should refer to Section B-1. CLIN to PWS Crosswalk. |
| 4 | B | N/A | 3 | B-1, CLIN to PWS Crosswalk | Att 0001 TOC pp. 3-4 | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP does not provide a complete Government crosswalk for this pricing element. This clarification is needed so all offerors price the same scope and no offeror relies on unwritten incumbent knowledge. Strategic alignment: A common data baseline supports the Army's broader data-centric decision-dominance direction by ensuring all offerors can price and solution from the same Government-held operational evidence. | Please provide a complete CLIN/SLIN-to-PWS mapping for every priced requirement, including which PWS paragraphs, attachments, CDRLs, and deliverables are included in each CLIN/SLIN. If the Government will not provide a crosswalk, please state that offerors may submit and rely on their own CLIN mapping without post-award interpretation risk. | The Government will not provide mapping details. Additionally, the Government will not accept any caveat that shifts the risk of requirement interpretation or pricing omissions from the Offeror to the Government. It is the Offeror’s responsibility to ensure their proposal and pricing structure fully account for all requirements, deliverables, and CDRLs as stated in the solicitation. |
| 5 | B | N/A | 3 | B-1, material/ ODC CLINs | Att 0001 2.7, 7.2, 15.1 | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP does not provide the historical or projected workload volume needed for all offerors to estimate this requirement on an equal basis. This is Government-held information or a Government estimating assumption needed to reduce incumbent-only informational advantage. Strategic alignment: Transaction-level parts, back-order, and inventory data supports AMCOM's stated use of AI-enabled tools for back-order management, environmental compliance, inventory tracking, shortage identification, and enterprise decision-making. | Please provide estimated annual quantities, ceilings, and/or historical actuals for each material, local-purchase, travel/TDY, commercial repair, subcontract, and other-direct-cost CLIN or cost element. If historical actuals are unavailable, please provide a Government pricing assumption set by contract year. | See Section L.3.2.5.2 which states "The Offeror shall utilize the following CNF CLIN prices: Material $200,000 per month; Services and Travel $700,000 per month; and Local Purchase $100,000 per month." As the Government is providing a plug number for each of these CNF CLINs, no other information is being provided. |
| 6 | B | N/A | 3 | B-1, MV-75 CLIN | Industry Day p. 8 | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP does not provide the historical or projected workload volume needed for all offerors to estimate this requirement on an equal basis. This is Government-held information or a Government estimating assumption needed to reduce incumbent-only informational advantage. Strategic alignment: MV-75 Cheyenne II planning data is necessary to buy down fielding and sustainment risk for a platform the Army describes as digitally enabled, modular, open-systems based, and engineered to evolve. | Please provide the MV-75 basis-of-estimate data by contract year, including aircraft quantities, stationing location(s), effective dates, annual flight hours, sorties, and launch windows. If MV-75 program data is not yet final, please provide the Government planning assumptions offerors are to use for pricing. | The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS. |
Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
The Offeror shall refer to the RFP, PWS, and Consolidated Question and Answer Document Fleet Size & Range and Flight Hours tabs.
7 B N/A 3 B-1, non-MDS support CLINs Att 0001 2.6-2.9, 11.0-15.0 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP does not provide the historical or projected workload volume needed for all offerors to estimate this requirement on an equal basis. This is Government-held information or a Government estimating assumption needed to reduce incumbent-only informational advantage. Strategic alignment: A common data baseline supports the Army's broader data-centric decision-dominance direction by ensuring all offerors can price and solution from the same Government-held operational evidence. Please provide estimated annual quantities, ceilings, and/or historical actuals for each non-MDS support CLIN covering management, logistics, facilities, reporting, and transition requirements. If historical actuals are unavailable, please provide the Government proposal assumptions for each CLIN and contract year. The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
Please see the below requested historical information based on the past three years: The average annual facility site visits that include Contractor participation is 30 visits with 80% involving 10 people or less.
The Government has addressed the other items in this inquiry elsewhere in this Q&A document. Offerors are encouraged to review the full set of responses for clarification on this topic. No further information will be provided.
| 8 | B | N/A | 3 | B-1, USAF support scope | Sources Sought 2.0; Industry Day p. 3 | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP identifies this support requirement without furnishing proposal-grade workload detail. A historical data release or common Government assumption is needed so all offerors can price this scope on the same footing. Strategic alignment: A common data baseline supports the Army's broader data-centric decision-dominance direction by ensuring all offerors can price and solution from the same Government-held operational evidence. | Please identify all USAF-supported aircraft MDS, quantities, assigned locations, flying-hour profile, required availability windows, and maintenance/logistics scope included in FRAM II pricing. If USAF support is only partially included, please identify the exact included and excluded scope. | This question is not in reference to an RFP document. |
| 9 | B | N/A | 3 | Fallback common assumptions - maintenance | All maintenance volume questions | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. If the Government elects not to release the underlying historical maintenance/readiness data, a standardized assumption set is needed to preserve a level playing field and enable predictive readiness modeling from a common baseline rather than incumbent-only operational knowledge. | If raw historical maintenance/readiness data is not released, will the Government provide a standardized proposal assumption set covering flight hours, launches, daily aircraft status, unscheduled maintenance events, corrective labor hours, repeat/recur rates, rejects, deferred discrepancies, rework, recovery burden, NMCS/NMCM/FMC/PMC trends, phase outcomes, ACR/IRAP activity, and parts latency by MDS/location/year? | The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS. |
Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
The Offeror shall refer to the PWS Attachment 0003 and Consolidated Question and Answer Document Flight Hours tabs. No further information will be provided.
10 B N/A 3 Fallback common assumptions - MV-75 / USAF Section B MV-75 / USAF support Offerors understand they are responsible for proposing their own technical, staffing, and management approach. If complete MV-75 or USAF workload data is unavailable, standardized assumptions are needed so all offerors price the same baseline and can propose progressive, data-enabled solutions without assuming privileged fielding or operational knowledge. If complete MV-75 Cheyenne II or USAF workload data is not available, will the Government issue a standardized basis-of-estimate assumption set by fleet, contract year, and location covering aircraft counts, flight hours, availability windows, maintenance concept, digital technical-data access, diagnostic-data access, support-equipment/tooling, facilities impacts, and support scope? The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
The Offeror shall refer to the PWS and Consolidated Question and Answer Document Fleet Size & Range and Flight Hours tabs. Section B does not reference the USAF. No further information will be provided.
11 B N/A 3 MV-75 support concept Industry Day p. 8; Section B MV-75 CLIN Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP identifies MV-75 Cheyenne II scope without furnishing proposal-grade fielding, maintenance concept, digital engineering, tooling/GSE, or technical-data assumptions. Because the Army has identified MV-75 Cheyenne II as a digitally enabled, modular open-systems platform, all offerors need the same Government baseline to buy down transition and sustainment risk and avoid post-award scope disputes. Please identify the MV-75 Cheyenne II maintenance and sustainment concept, including contractor-performed tasks, aircraft quantities by year/location, IOC/FOC or fielding schedule, OEM/CLS participation, GSE/tooling responsibilities, training requirements, facilities impacts, digital engineering data availability, technical-publication format, diagnostic-data interfaces, data rights, support-equipment baselines, and whether any Army Vantage-ready or AI-assisted maintenance data environment will be available to the contractor. If details are not final, please provide common proposal assumptions by contract year for all offerors. The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
The Offeror shall refer to the PWS and Consolidated Question and Answer Document Fleet Size & Range and Flight Hours tabs. As the MV-75 is still under development, the Government projects an approximate similarity of 80% to the UH platform and 20% to the CH-47 platform. The CH-47 similarity involves general mechanical and structural systems, whereas the UH similarity applies across all remaining aircraft systems. No further information will be provided.
12 B N/A 3 Open-ended recurring requirements Section B and PWS scope treatment Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP does not clearly identify the scope boundaries for this pricing element. A Government clarification is needed so all offerors use the same inclusion/exclusion baseline and avoid post-award scope migration. Strategic alignment: A common data baseline supports the Army's broader data-centric decision-dominance direction by ensuring all offerors can price and solution from the same Government-held operational evidence. For each open-ended recurring requirement lacking measurable volume, please state whether it is: (a) included in fixed-price CLIN pricing, (b) excluded from proposal pricing and Government-retained, or (c) separately directed/reimbursable only when authorized in writing. If not otherwise clarified, please confirm offerors may rely on their documented assumptions without post-award reinterpretation risk. The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The Offeror should refer to Section B-1. CLIN to PWS Crosswalk. The Government will not accept any caveat that shifts the risk of requirement interpretation or pricing omissions from the Offeror to the Government. It is the Offeror’s responsibility to ensure their proposal and pricing structure fully account for all requirements, deliverables, and CDRLs as stated in the solicitation.
| 13 | B | N/A | 3 | USAF pricing basis | Sources Sought 2.0 | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP identifies this support requirement without furnishing proposal-grade workload detail. A historical data release or common Government assumption is needed so all offerors can price this scope on the same footing. Strategic alignment: A common data baseline supports the Army's broader data-centric decision-dominance direction by ensuring all offerors can price and solution from the same Government-held operational evidence. | Please provide historical and projected USAF flight hours, launches, maintenance events, and support windows by supported USAF fleet and location. If USAF historical data is unavailable, please provide the Government proposal assumptions offerors are to use. | This question is not in reference to an RFP document. |
| 14 | B | N/A | 4 | B-1, Local Purchase / Other Direct Cost elements | Att 0001 2.7, 7.2 | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft package describes this logistics/property workload without furnishing the historical transaction burden behind it. Government-held actuals or common proposal assumptions are needed so all offerors estimate the same operational load. Strategic alignment: Transaction-level parts, back-order, and inventory data supports AMCOM's stated use of AI-enabled tools for back-order management, environmental compliance, inventory tracking, shortage identification, and enterprise decision-making. | Please provide historical annual counts, total dollars, and average approval cycle time for local-purchase requests, commercial repair buys, and non-stock material actions by support area. If historical data is unavailable, please provide Government pricing assumptions by year. | The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS. |
Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
The Offeror shall refer to RFP Section L.3.2.5.2. for total dollars. Please see the below requested historical information based on the past two years: Local Purchase Requests Annual counts - 1,100 purchase orders Services Annual counts - 245 purchase orders Average approval cycle for both varies based on priority.
| 15 | B | N/A | All | Section B | CLIN XXX4 | The solicitation provides a requirement for UH-72A Aircraft Maintenance throughout the duration of the 10 year period of performance. | Will the UH-72 Aircraft Maintenance requirements be revised in the final solicitation with award and transition of the Flight School Next Program? | The Government does not intend to do so at this time. |
| 16 | B | N/A | All | Section B | CLIN XXX5 | The solicitation provides a requirement for MV-75 Aircraft Maintenance? | The MV-75 platform is a new platform that has not fully completed production. Will the Government consider making this CLIN "To be negotiated" when the aircraft production is complete and maintenance data can be provided? | No. |
| 17 | B | N/A | All | Section B | CLIN XXX5 | The solicitation provides a requirement for MV-75 Aircraft Maintenance? | The MV-75 platform is a new platform that has not fully completed production. Will the Government consider establishing a fixed staffing level for all Offerors to propose a firm fixed price to level the evaluation and adjust based on final maintenance requirements? | No. |
| 18 | H | N/A | 129 | H-1 | Government intends to negotiate the rate adjustments to the applicable year and all remaining option years | H-1 referenced for incorporating CBA wage increases. Is the Government going to incorporate the CBAs into the RFP attachment documents? | No. | |
| 19 | I | N/A | 134 | Section I | 52.222-43 | FAR 52.222-43 is incorporated into the solicitation. | Is there an applicable collective bargaining agreement associated with this solicitation and will this be provided? | The Government will not provide any applicable bargaining agreements. |
| 20 | I | N/A | 134 | Section I | 52.222-43 | FAR 52.222-43 is incorporated into the solicitation. | Will the Government provide the seniority of the current workforce covered under the solicitation to provide Offerors the ability to propose adequate wages and benefits? | No. |
| 21 | I | N/A | All | Section I | 252.228-7001 | Section I does not include the Ground and Flight Risk Clause (252.228-7001) | Does the Government intend to incorporate the Ground and Flight Risk Clause (DFAR 252.228-7001)? | Yes, DFARS 252.228-7001 has been incorporated into the RFP. |
| 22 | J | 0001 | 2 | ACE discrepancy trends | Att 0001 2.6.2.9 | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft package imposes this quality, inspection, or review requirement without furnishing historical count and burden data. Government-held actuals or common proposal assumptions are needed to prevent incumbent-only pricing knowledge. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. Strategic alignment: Providing machine-readable technical, maintenance, and records data supports Army AI-Assisted Maintenance / Vantage-enabled workflows and allows offerors to propose digital maintenance tools without relying on incumbent-only system familiarity. | Please provide historical ACE discrepancy and trend files by MDS, location, and major system for FY23-FY25. If ACE files are not provided, please furnish a Government-prepared top-driver summary with counts and recurrence rates. | The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS. |
The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The requested data and records will not be provided.
| 23 | J | 0001 | 6 | 2.1 | Attachment 0014 | The PWS requires daily facility maintenance but does not clearly allocate routine support services, especially in co-use spaces. Risk: Misaligned assumptions for housekeeping and environmental services may create scope gaps and unplanned costs. | Are janitorial, trash removal, groundskeeping, and related environmental-compliance services Government-provided or contractor-provided, including in co-use facilities? | The Government is responsible for grass cutting and dumpster emptying. The Offeror shall refer to the PWS for all other referenced items. |
| 24 | J | 0001 | 9 | 2.2.2 | The Contractor shall accomplish approved MWO applications. | What is the historical annual workload estimate by MDS and anticipated MWO count? | The Government is not providing this information. | |
| 25 | J | 0001 | 10 | 2.2.3.2 | CH-47F and UH-60M Extended Range Fuel Systems (ERFS) | Will GOV provide current number of available ERFS and CEFS as well as estimated daily requirements? Are configurations considered separate in the DMP/MSMP calculations? | Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals. |
Please see the below requested historical information:
CH-47F ERFS: 25 EA to 35 EA UH-60M CEFS: 10 EA to 15 EA
No estimated daily requirements will be provided. DMP and MSMP will be calculated IAW the PWS and PWS Attachment 0002, Mission Performance Calculation.
| 26 | J | 0001 | 10 | 2.2.4 | Currently AMSS is not set up to use the Logistics Information System (LIS) ACN back shops module. | Is manual records keeping and processing acceptable if LIS is not available? If the contractor is required to use the ACN module at AMSS, will Government ensure AMSS is supported by ACN prior to FRAM II award? | The Offeror shall refer to PWS paragraph 2.2.12. regarding manual record keeping. The Offeror shall refer to PWS paragraph 2.7.4. regarding the use of the LIS systems ACN and/or GCCS-A at AMSS. | |
| 27 | J | 0001 | 11 | 2.2.6-2.2.7 | CDRL A011 / A016 | Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP does not provide the historical or projected workload volume needed for all offerors to estimate this requirement on an equal basis. This is Government-held information or a Government estimating assumption needed to reduce incumbent-only informational advantage. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. | Please provide the projected MWO, modification, transfer inspection, shipment preparation, and improvement-project workload by fleet and contract year. If forecasted counts are not established, please provide Government planning assumptions. | The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS. |
The requested data and records will not be provided.
| 28 | J | 0001 | 11 | 2.2.7 | The contractor shall issue and maintain removable aircraft data storage | Is the Contractor responsible for loading the data on the removable storage? If yes, will the Government supply the Amps Computer? Will the contractor require a TAC OPs officer? | The Contractor is not responsible for loading data on the removable storage devices using an AMPs computer. |
| 29 | J | 0001 | 11 | 2.2.7 | The Contractor shall install/load files and operational data for aircraft communication, maintenance, navigation, identification, and avionics systems. | Will the Government provide annual workload estimates? By MDS? What are the navigation / avionics devices? | Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals. |
The Offeror shall refer to the Consolidated Question and Answer Document Fleet Size & Range and Flight Hours tabs. No further information will be provided.
| 30 | J | 0001 | 11 | 2.2.8 | Reference anticipated fleet changes and aircraft divestiture. | What involvement will the FRAM II contractor have related to turn in of GFE / GFP related to aircraft fleet changes and divestiture of aircraft? | The Offeror shall refer to PWS paragraph 2.2.8., 14.0., 14.1., 14.2., and 14.3. |
| 31 | J | 0001 | 11 | 2.2.8 | Contractor shall ensure incoming Aircraft are placed in the school house fleet within 5 days of acceptance | What is definition of "acceptance" and is there a list of acceptance requirements? Is contractor simply performing serial number checks? Request clarity on acceptance criteria to satisfy 5 day requirement. | The term "acceptance" is not found in paragraph 2.2.8. |
| 32 | J | 0001 | 11 | 2.2.8 | Fleet Divestment and Integration | Will the USG provide historical and/or estimated MDS work load estimates? | Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals. |
The Offeror shall refer to the Consolidated Question and Answer Document Fleet Size & Range tab. No historical data will be provided.
| 33 | J | 0001 | 11 | 2.2.9 | Aircraft transfer criteria | Will the Government provide specific MDS aircraft transfer criteria that supports the 5 day induction into the AVCOE fleet? What consideration is given by the Government for transfer aircraft not inducted into the fleet within 5 days for conditions outside of the contractors control? | No. The Offeror shall refer to PWS paragraph 2.2.8. for instructions regarding extensions for aircraft induction. |
| 34 | J | 0001 | 11 | 2.2.9 | Aircraft Transfer Inspections and Shipment | Will Government provide annual workload estimates by MDS? How many transfers are anticipated per year? | Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals. |
The Offeror shall refer to the Consolidated Question and Answer Document Fleet Size & Range tab. No historical data will be provided.
35 J 0001 12 2.2.10 Controlled Exchange Will the USG provide historical and/or estimated MDS work load estimates for controlled exchanges? Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
Please see the below requested historical information:
Total number of controlled exchanges: For CY23: 1,073; CY24: 1,260; and CY25: 1,421.
No further information will be provided.
36 J 0001 12 2.2.8 / 2.2.9 Industry Day p. 8 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP does not provide the historical or projected workload volume needed for all offerors to estimate this requirement on an equal basis. This is Government-held information or a Government estimating assumption needed to reduce incumbent-only informational advantage. Strategic alignment: A common data baseline supports the Army's broader data-centric decision-dominance direction by ensuring all offerors can price and solution from the same Government-held operational evidence. Please provide planned dates and phasing assumptions for the UH-60M move to Hanchey, the AH-64E move to Lowe, and any related CPM redistribution. If dates are not established, please provide the Government assumptions bidders are to use. The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The requested data and records will not be provided.
37 J 0001 12 2.2.8, Fleet Divestment and Integration Industry Day p. 8 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP does not provide the historical or projected workload volume needed for all offerors to estimate this requirement on an equal basis. This is Government-held information or a Government estimating assumption needed to reduce incumbent-only informational advantage. Strategic alignment: A common data baseline supports the Army's broader data-centric decision-dominance direction by ensuring all offerors can price and solution from the same Government-held operational evidence. Please provide the year-by-year UH-72A divestment and FSN transition schedule by location, including aircraft counts, effective dates, and the residual FRAM II support requirement during overlap periods. If the schedule is not final, please provide the Government proposal assumptions. The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS.
The FRAM II Requirement contains yearly support for the UH-72A aircraft for the life of the contract.
| 38 | J | 0001 | 13 | 2.2.12.1 | Attachment 0004 | Torques and Documentation - this section needs better clarity. This should only apply to torquing tools not a measurement device. | AH-64 IETM does not have work packages. How does this apply to the AH-64 fleet? The AMAM referenced in Attachment 4 only requires to enter the Manual reference, not Work Packages. Is the requirement for every single calibrated item to be documented? Does this include calipers & dial indicators? Gen AMAM does not have this documentation as a requirement | The Government's requirement is defined in PWS paragraph 2.2.12.1. |
| 39 | J | 0001 | 14 | Phase-in data turnover | Att 0001 2.2.4; transition requirements | Offerors understand transition execution is part of the proposed approach. However, the content, format, completeness, and timing of Government-furnished historical records and system exports are Government-controlled assumptions that determine whether a new entrant can establish an accurate starting baseline. A machine-readable digital handoff supports data-centric sustainment, avoids paper-based conversion burden, and reduces post-award ambiguity. | Please provide the data and records the Government expects to furnish at phase-in, including historical ACN/logbook exports, aircraft configuration status, open work orders, deferred discrepancies, phase status, parts status, CDRL history, facility/property records, and any data dictionaries or schemas. Please state whether these will be provided as native/machine-readable exports or static reports. If not available, please provide common assumptions for transition data conversion and validation. | The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS. |
The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
At the time of Phase-In the Government will give the Contractor system read-only access to ACN.
40 J 0001 15 2.3.5 CLIN 0008 Aircraft recovery and monitor-personnel requirements are included, but the expected annual event volume and geographic scope are not defined. Risk: Underestimating recovery requirements could affect mission response and travel pricing. Will Government provide historical aircraft-recovery workload data and the expected geographic radius for recovery operations? Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
The Offeror shall refer to the Consolidated Question and Answer Document Aircraft PL Data tab. No further information will be provided.
41 J 0001 15 2.3.5.3 Aircraft Recovery Will the USG provide historical and / or estimated MDS recovery work load estimates? Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
The Offeror shall refer to the Consolidated Question and Answer Document Aircraft PL Data tab. No further information will be provided.
42 J 0001 16 2.3.5.2-2.3.6 Sources Sought 2.2.1 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft RFP identifies this support requirement without furnishing proposal-grade workload detail. A historical data release or common Government assumption is needed so all offerors can price this scope on the same footing. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. Please provide historical annual counts and average labor hours for precautionary landings, aircraft recovery events, and off-station support responses by location and fleet. If historical response data is unavailable, please provide standardized proposal assumptions. The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals.
The Offeror shall refer to the Consolidated Question and Answer Document Aircraft PL Data tab. No further information will be provided.
43 J 0001 16 Recovery dispatch history Sources Sought 2.2.1; Att 0001 2.3.6 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the Government requires or references these records and reports after award without furnishing the historical dataset to offerors. Historical extracts or a common Government summary baseline are needed so all bidders can estimate from the same factual record. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. Please provide historical off-station recovery dispatch data, including event counts, distance bands, response times, crew size, and duration. If raw recovery dispatch history is unavailable, please provide standardized proposal assumptions. The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS.
The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The requested data and records will not be provided.
| 44 | J | 0001 | 17 | 2.4 | Aircraft Coordination and scheduling | Is there a maximum number of hours that can be requested? What are the issue window hours? What are the aircraft configurations? Where are they found? | The Offeror shall refer to PWS paragraph 2.4. for aircraft issue times. The Offeror shall refer to AVCOE regulation 350-3 as referenced in Attachment 0004, Document Summary List (DSL), for aircraft configurations. The PWS does not limit the number of hours that can be requested. |
| 45 | J | 0001 | 18 | 2.4.1 | Monthly Projections | Will fleet size projections include Flight Hours by MDS? | No. |
| 46 | J | 0001 | 18 | 2.4.2 | Daily Mission Launch Requirements Sortie 3 update | Is there a maximum number or percentage of aircraft that can be added or removed from Sortie 3 at the 0900 update? How will Sortie 3 be updated? | The Offeror shall refer to PWS paragraph 2.4.2. regarding sortie updates. The PWS does not define a maximum number or percentage of aircraft that can be added or removed from Sortie 3. |
| 47 | J | 0001 | 19 | 2.4.4 | Weekend Flight Training | Will the Government please provide historical data for weekend flying frequency? What will be the notification process to the contractor for weekend flying requirements? | Any historical data, estimates, or supplementary information provided by the Government is for informational purposes only and does not constitute a guarantee of future workload or mission frequency. The Government will not be bound by this information during contract execution. Offerors must clearly document all assumptions used to develop their proposals. |
Please see the below requested historical information from the past four years:
Weekend flying frequency: Average 19 planned events
The Offeror shall refer to PWS paragraph 2.4.4. regarding the weekend/holiday flight training process.
48 J 0001 20 AOG / expedite maintenance Att 0001 2.3.1-2.3.5 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the Government requires or references these records and reports after award without furnishing the historical dataset to offerors. Historical extracts or a common Government summary baseline are needed so all bidders can estimate from the same factual record. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. Please provide historical annual counts and average labor hours for AOG, expedite, and rush-turn maintenance events by MDS and location. If history is not released, please provide a standard estimating assumption by MDS. The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS.
The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The requested data and records will not be provided.
49 J 0001 20 Corrective maintenance labor burden Att 0001 2.3.1-2.3.5 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the Government requires or references these records and reports after award without furnishing the historical dataset to offerors. Historical extracts or a common Government summary baseline are needed so all bidders can estimate from the same factual record. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. Please provide historical corrective-maintenance labor hours by MDS, tail number or fleet, system/fault category, and event severity for FY23-FY25, or the most recent 36 months available. If historical labor-hour data is not released, please provide Government common assumptions by MDS/year for corrective maintenance labor burden. The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS.
The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The requested data and records will not be provided.
50 J 0001 20 Deferred discrepancy backlog Att 0001 2.3.1-2.3.5 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the Government requires or references these records and reports after award without furnishing the historical dataset to offerors. Historical extracts or a common Government summary baseline are needed so all bidders can estimate from the same factual record. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. Please provide current and historical deferred discrepancy counts, aging bands, and monthly closure volumes by MDS and location. If backlog data is unavailable, please confirm offerors may rely on their own documented deferred-maintenance assumptions. The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS.
The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The requested data and records will not be provided.
51 J 0001 20 Native maintenance records Att 0001 2.5.4; historical forms Offerors understand they are responsible for proposing their own maintenance approach. However, native maintenance history, logbook transactions, technical-reference formats, and aircraft configuration data are Government/incumbent-held records needed to develop a data-driven maintenance plan and to support AI-assisted/manual interaction with technical documentation. Providing searchable, exportable records supports faster troubleshooting, reduced lapse time, and equal access to the operational evidence currently available to the incumbent. Please provide read-only native extracts of aircraft maintenance history, logbook transactions, aircraft configuration records, troubleshooting references, and technical manuals/IETMs where releasable, including field definitions and export formats. Please identify whether the data will be machine-readable, searchable, exportable, API-accessible, or compatible with Army AI-Assisted Maintenance/Vantage-enabled workflows. If not, please state the technical-publication and aircraft-record access limitations all offerors must assume. The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS.
The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The requested data and records will not be provided.
52 J 0001 20 Repeat/recur faults Att 0001 2.3.1-2.3.5 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the Government requires or references these records and reports after award without furnishing the historical dataset to offerors. Historical extracts or a common Government summary baseline are needed so all bidders can estimate from the same factual record. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. Please provide repeat/recur discrepancy rates by MDS, major system, and location for FY23-FY25, including top chronic fault categories. If repeat/recur history will not be released, please furnish a standardized chronic-fault assumption set. The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS.
The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The requested data and records will not be provided.
53 J 0001 20 Unscheduled maintenance history Att 0001 2.3.1-2.3.5 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the Government requires or references these records and reports after award without furnishing the historical dataset to offerors. Historical extracts or a common Government summary baseline are needed so all bidders can estimate from the same factual record. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. Please provide 36-60 months of historical unscheduled-maintenance event counts by MDS, tail number, location, shift, and event category, including corrective action category where available. If raw event history is not released, please provide a Government common assumption set by MDS/year covering event count, average labor hours, repeat/recur rate, and severity mix. The identified page number, paragraph reference, or additional cross reference details do not correlate to the PWS.
The Government is not providing standardized assumptions for this requirement. Offerors are responsible for developing their own technical and pricing baselines based on the requirements defined in the PWS.
The requested data and records will not be provided.
54 J 0001 21 IRAP workload Att 0001 2.6.2.4 Offerors understand they are responsible for proposing their own technical, staffing, and management approach. However, the draft package imposes this quality, inspection, or review requirement without furnishing historical count and burden data. Government-held actuals or common proposal assumptions are needed to prevent incumbent-only pricing knowledge. Strategic alignment: This request supports AMCOM's stated 2026 emphasis on using data analytics to predict sustainment challenges before they impact readiness and to move the requirement from reactive maintenance response toward predictive readiness planning. Please provide historical IRAP counts, approval/denial rates, cycle time, and labor-hour burden by MDS and location. If the Government elects not to provide historical IRAP actuals, please provide common proposal assumptions for IRAP incidence and burden.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .