FT3 Production Follow-On Request for Proposal Memo_17 Nov 26.pdf
PDF 2 MB Posted
- Solicitation number
- FA821426RB004
About this file
This is a Request for Proposal (RFP) memorandum from the Department of the Air Force, Air Force Nuclear Weapons Center, ICBM Systems Directorate, dated 17 November 2026, soliciting proposals from The Boeing Company for the production and delivery of 25 Minuteman III Flight Test, Telemetry, and Termination (FT3) flight test kits. The contract period of performance extends up to 7 years, beginning in October 2027 or upon contract award. Boeing must provide just-in-time deliveries (120 days prior to need) to Vandenberg Space Force Base, California, to support Air Force Global Strike Command's Minuteman III Operational Test Launch program through 2040. The proposal submission deadline is 17 May 2027. Boeing shall propose a schedule for subtier vendor delivery of component end items to Boeing Guidance Repair Center in Heath, Ohio, including flight test kit assembly and storage prior to shipment to Vandenberg.
The RFP requires Boeing to submit certified cost or pricing data and supporting attachments in accordance with RFO 15.408-2, Table 15-1, including a Cost Analysis Report, separate cost volume, technical volume addressing production approach, and draft production schedule. Boeing must complete the Proposal Adequacy Checklist (PAC) DEVIATION 2026-O0048 and address specific cost proposal requirements including breakout by Government Fiscal Year and Calendar Year, consolidated bill of materials in Excel format, cost estimating relationships, historical actual costs incurred data from prior three years, commercial item determinations, and an electronic cost model with active formulas in Excel that is editable by the Government. The proposal must address overtime estimates with detailed supporting documentation, assist audit requests, subcontractor data rights assertions, and pricing for all subcontract commercial items. Boeing shall also populate the Government Rights in Data form identifying all subtier vendor data rights and submit it during negotiations.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 3. FT3 Production Follow-On CDRL Package 4 Nov 2026.docx | DOCX document | |
| 5. Solicitation - FA821426RB004 Rev 17 Nov 2026.pdf | ||
| 1. FT3 PWS_Production Follow-On Final_17 Nov 26.pdf | ||
| 4. FT3 Production Follow-On CLIN Structure.xlsx | XLSX spreadsheet | |
| 4. FT3 Production Follow-On CLIN Structure_Draft May 26.xlsx | XLSX spreadsheet | |
| 6. AFNWC-NIMS OPSEC Addendum.docx | DOCX document | |
| 2. FT3 Production Follow-On GRID.docx | DOCX document | |
| 3. FT3 Production Follow-On CDRL Package 24 Apr 2026.docx | DOCX document | |
| FT3 Production Follow-On Request for Proposal Memo_updated 7 July 26.docx | DOCX document | |
| 5. Solicitation - FA821426RB004.pdf | ||
| 1. FT3 PWS_Production Follow-On_1 Jun 26v1.docx | DOCX document | |
| 7. FT3_VSFB_locations for shipping Attachment.xlsx | XLSX spreadsheet |
Show all 12
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
Never Doubted, Always Feared
DEPARTMENT OF THE AIR FORCE
AIR FORCE NUCLEAR WEAPONS CENTER
ICBM SYSTEMS DIRECTORATE
HILL AIR FORCE BASE UTAH
17 November 2026
MEMORANDUM FOR The Boeing Company Attn: Ms. Stacy Wagner 6006 Wardleigh Road Hill AFB UT 84056-5837
FROM: AFNWC/NIKM (Mr. Bradley Vargo) 6014 Dogwood Avenue, Bldg.
1258 Hill AFB UT 84056
SUBJECT: Request for Proposal (RFP) for Minuteman III Flight Test, Telemetry, and Termination (FT3) Flight Test Kits Procurement
1. The FT3 Program is requesting The Boeing Company provide a proposal to produce 25 flight test kits. This contract award will allow for production of FT3 flight test kits to support Air Force Global Strike Command (AFGSC) Minuteman III (MMIII) Operational Test Launch (OTL) Program through 2040 in accordance with the attached FT3 Performance Work Statement (PWS) dated 1 June 2026. The contract period of performance (PoP) is for up to 7 years, starting in October 2027 or upon contract award. Boeing should provide pricing for the production and delivery of 25 flight test kits. Please provide the RFP in accordance with the attached Clauses and Provisions, PWS dated 17 November 2026, and Contract Data Requirements List (CDRL) dated 4 November 2026. Packaging and shipping should be proposed in accordance with Boeing Document D2-29691 FT3 Transportation Plan.
2. The Government requires just-in-time (120 days prior) flight test kit deliveries to Vandenberg Space Force Base (VSFB), California, to coincide with the AFGSC MMIII OTL 5-year schedule. Boeing should propose a schedule for subtier vendor delivery of component end items to Boeing Guidance Repair Center (BGRC) in Heath, Ohio, to include flight test kit assembly and plan for storage at BGRC prior to required shipment to VSFB.
3. The Government has attached a draft CLIN structure for review and discussion to ensure flexibility and guarantee execution as expected.
4. The Government requests that Boeing populate the attached Government Rights in Data (GRID) to include all subtier vendors exertion of data rights, and plan to submit to the Government at negotiations.
5. The Government requests Boeing to review and provide comments/actions for the CDRL package.
6. Attached is the Proposal Adequacy Checklist (PAC) along with preparation guidelines. Boeing shall prepare and submit a Cost Analysis Report (CAR) and pricing data. Pricing shall be delivered in accordance with RFO 15.408-2, Table 15-1. Additionally, Boeing should provide the following: a separate cost volume; technical volume which includes approach for production requirements; and draft schedule for production.
a. Proposal Adequacy and Structure.
1) In response to this RFP, Boeing shall prepare and submit certified cost or pricing data and supporting attachments in accordance with Table 15-1 of RFO 15.408-2. Further, Boeing shall (1) utilize the R- DFARS 252.215-7993, Proposal Adequacy Checklist (PAC) DEVIATION 2026-O0048 (attached to this RFP letter), in pre-submission proposal quality reviews, and (2) furnish the completed checklist as part of its proposal submission.
a) If Boeing believes overtime (OT) is necessary to perform the contract requirements, the Contractor must discretely estimate any anticipated OT over the life the contract to the extent the OT can be estimated with reasonable certainty and the request must contain the information required by paragraph (b) of RFO 52.222-2, Payment for Overtime Premiums pursuant to RFO 22.103(b).
b) The proposed OT estimates shall include adequate documentation and support, e.g., OT labor rates shall be identified separate from straight/regular labor hour rates, overtime premiums (OTP), shift premiums, and/or multishift costs shall be visible in the estimates; OT calculations/formulas shall be explained; descriptions of tasks anticipated to require OTP, shift premiums, and/or multishift costs will be provided along with associated justifications to explain why these extra costs are necessary to execute the requirements.
c) Basing proposed OT estimates on rates only such as the application of blended rates and referencing the Boeing/DCMA OTP Memorandum of Agreement (MOA) is not acceptable because the rates do not afford the Government adequate visibility into the estimated OTP, shift premiums, and/or multishift costs and the OTP MOA is not applicable to estimating, negotiating, or approving OT.
2) The responsibility for providing a well-prepared and fully supported cost proposal lies solely with Boeing. The basis and rationale for all proposed costs shall be provided as part of the proposal so that the Contracting Officer (CO) has the information necessary to evaluate the reasonableness of the proposed price.
3) If Boeing is unsure as to whether a checklist item is required in support of the proposal, or how to adequately comply with a checklist item, Boeing shall contact the CO as soon as possible after receipt of the RFP, but in any case, prior to proposal submittal, to resolve the questions.
4) Noncompliance with the R-DFARS Proposal Adequacy Checklist and the additional requirements of this provision will require immediate correction. However, completion of the checklist does not relieve Boeing from the responsibility to comply with all applicable regulations and any special requirements of the solicitation.
5) Boeing is encouraged to flow down this provision to subcontractors/affiliates required to submit certified cost or pricing data in support of this RFP.
a. Boeing is advised that the CO may find costs associated with revision/rework of inadequate cost proposals unreasonable and will consider the nature and extent of any proposal inadequacies when assessing/negotiating profit.
b. To preclude delays in negotiations and contract award, the completed PAC submitted with the proposal shall provide a clear explanation for any checklist items not included in the proposal, particularly items not provided based on any of the five exceptions found at RFO15.403-2(b).
c. Cost Proposal Requirements. In addition to the requirements identified in the R-DFARS PAC, the following also apply to the cost proposal submitted in response to this RFP.
6) Breakout by Year. If the proposal includes more than one CLIN, the proposal shall include a breakout of CLIN prices by cost element by Contractor Fiscal Year (CFY). At the CO’s direction, the breakout by year shall also be provided by:
_X_ Government Fiscal Year (GFY) _X_ Calendar Year (CY)
The proposal shall define the timeframe of the Contractor Fiscal Year (for example, January – December).
7) If the proposal includes more than one CLIN/subCLIN, recurring/non-recurring costs shall be identified for each CLIN/subCLIN.
8) If the proposal includes material costs, the proposal shall include a consolidated bill of materials (CBOM) at the total contract level in an electronic, sortable format (Excel spreadsheet).
a) When the amounts proposed in the CBOM include application of escalation, the proposal shall identify the base value, the escalation rate(s) used, and the escalation amount associated with each item escalated.
b) When the proposed amount is based on historical data which has been adjusted (for example, for differences in quantity), the CBOM shall clearly identify the adjustments made to the historical data and the reason for each adjustment.
9) All costs proposed on the basis of Cost Estimating Relationships (CER) shall be fully supported.
The proposal shall identify the basis for the proposed rate, shall identify the base to which the rate is applied, and shall clearly demonstrate the calculation of proposed costs based on CERs.
10) For any costs incurred prior to proposal submission, the proposal shall identify actual hours, and cost incurred as well as hours/costs to complete and the time phasing associated with these hours/costs. This information/data shall be provided in a time-phased cost element summary format.
11) Submission of Historical Actual Costs Incurred. Boeing shall provide with its proposal historical Actual Costs Incurred (ACI) data for any similar efforts within the past 3 years.
a) The contractor shall provide the following information for these prior acquisitions:
(1) contract number (including modification number if applicable) or other identifier;
(2) contract type;
(3) contract quantity;
(4) contract price; and
(5) actual cost incurred, including a breakout of actuals as recurring/non-recurring costs. If performance is not complete on any of the specified contract actions, provide an estimate to complete and the basis for that estimate.
b) The contractor shall also request that its major sole source subcontractors provide the information listed in the above paragraphs (a) (1) through (5) on prior contracts for items the prime is purchasing from the subcontractors for this effort. If a subcontractor’s information on prior actuals is not included in the prime’s proposal, the proposal should identify status and anticipated receipt date(s). If the subcontractor deems the information proprietary, the subcontractor may submit the information directly to the CO.
12) The proposal shall identify those actions where assist audits have been requested by the prime or sub-tier contractors and identify the request date and scheduled receipt date for those audits. The need for assist, audits resulting from proprietary data rights assertions at any tier shall be identified to the Contracting Officer as soon as Boeing becomes aware of the need. Government performance of assist audits does not relieve Boeing of the responsibility to accomplish and provide its price/cost analysis of the subcontracts.
13) Commercial item considerations:
a) Boeing proposal shall provide support for any subcontractor Commercial Item Determinations (CID), addressing, at a minimum, the following:
(1) A description of the supplies or services;
(2) Specific identification of the type of commercial item claim (RFO 2.101 ), and the basis on which the item meets the definition; and
(3) For modified commercial items (commercial product sub-definition (3)), classification of the modification(s) with supporting rationale as either:
(a) Of a type customarily available in the commercial marketplace (FAR 2.101 commercial product sub-definition (3)(i)); or
(b) A minor modification of a type not customarily available in the commercial marketplace made to meet Federal Government requirements (FAR 2.101 commercial product sub-definition (3)(ii)).
Note that per RFO 15.403-2(c)(3)(iii)(B), modifications that meet the definition of minor modifications of a type not customarily available in the commercial marketplace as defined in RFO 2.101, paragraph (3)(ii) of the commercial product definition, will require the submission of certified cost and pricing data when the total price of all such modifications exceeds the greater of the threshold for certified cost or pricing data (R-DFARS 215.403-3)
b) For proposed subcontract commercial items “of a type”, or “evolved” or modified (RFO 2.101 commercial product sub-definitions (1) through (3)), the offeror shall provide a technical description of the differences between the proposed item and the comparison item and thoroughly address the cost differences between the proposed item and the comparison item.
c) The proposal shall include, or Boeing shall make available, data other than certified cost or pricing data to establish price reasonableness of the proposed subcontract commercial item (to include any modifications not subject to the requirement to submit certified cost or pricing data) by supplying:
14) Information/data related to competition, if competition is Boeing’s basis for asserting the reasonableness of the proposed subcontract price.
15) Information/data related to prices (sales data, market price assessments, etc.). Note that subcontractors may submit sales data directly to the CO if the subcontractor deems the data proprietary.
16) The prime contractor’s or higher tier subcontractor’s price analysis/price reasonableness determination for the commercial subcontract in accordance with RFO 15.404-8(a).
17) Cost information/data (cost element breakdown and supporting documentation not subject to certification in accordance with RFO 15.403-4). Instances where cost information may be required include but are not limited to commercial items offered but never actually sold to the public, “of a type” commercial items, or when sales data is limited and/or not recent and/or not for the same/similar quantities.
NOTE: The preferred method of establishing the price reasonableness of commercial items is to obtain commercial sales data. It is recognized that other methods, such as market price assessment data or evaluation of cost data not subject to certification, are also acceptable when prior sales data cannot be obtained. Sales data shall (1) demonstrate sales to the general public; (2) be current; and (3) where possible, be in like quantities.
Items sold to state, local or foreign governments, or items sold with applications only to state, local, or foreign government or US Government end items are not considered to be sales to the general public unless the proposed commercial item meets the RFO 2.101 commercial product definition sub-definition (8).
18) Submission of electronic cost model. The proposal submission shall include an electronic cost model with active formulas demonstrating the mathematical calculation of the proposed cost (in Excel). The electronic cost model shall include build-up by year of cost in total and by CLIN/subCLIN, consistent with the yearly breakout required by paragraph (d)(1) of this provision, or as directed by the Contracting Officer. If applicable, the electronic cost model shall link each Work Breakdown Structure (WBS) to the applicable CLINs. The electronic cost model shall roll up to an annual and total program summary by cost element. All information supporting each CLIN should be visible and verifiable in the electronic cost model. The formulas included in the electronic cost model shall not be locked, and the model shall be made editable by the Government.
7. Please provide your proposal, in accordance with the requirements specified in the attached FT3 PWS. In accordance with DAFFARS MP5332.7, Contract Funding: Notice to Offeror(s)/Supplier(s); Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an offeror for any costs. The proposal is due by COB on 17 May 2027. If you have any questions or concerns, please contact Mr. Bradley Vargo at 801-775-3700. If additional information is required, Mr. Vargo can be reached by calling 801-775-3700 or through e-mail at bradley.vargo.1@us.af.mil or myself at torrey.boggs.2@us.af.mil.
TORREY W. BOGGS, NH-03, USAF
Contracting Officer
7 Attachments:
1. FT3 Performance Work Statement (PWS) with Appendices
2. FT3 Government Rights in Data (GRID)
3. FT3 CDRL Instructions and Master Listing
4. FT3 CLIN Structure
5. Clauses Proposed
6. AFNWC-NIMS OPSEC Addendum
7. Shipping Instructions mailto:bradley.vargo.1@us.af.mil mailto:torrey.boggs.2@us.af.mil
FT3 Production Follow-On Performance Work Statement – 17 November 2026
PERFORMANCE WORK STATEMENT
for
FLIGHT TEST, TELEMETRY, AND
TERMINATION (FT3) PROGRAM
OPERATIONS AND SUPPORT PHASE
FT3 Production Follow-On
17 November 2026
AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)
INTERCONTINENTAL BALLISTIC MISSILE (ICBMSD)
SYSTEMS DIRECTORATE (AFNWC/NI)
MMIII Systems Program Office (AFNWC/NIM)
Guidance Branch (AFNWC/NIMG)
Hill Air Force Base, Utah
Distribution Statement A:
Distribution authorized to Department of War and U.S. DoD contractors only (public release), 8 April 26. Other requests must be referred to MMIII SPO (AFNWC/NIM), 6014 Dogwood Ave, Hill AFB UT 84056.
Table of Contents
1 SECTION I. DESCRIPTION OF SERVICES/SCOPE
1.1 Introduction
1.2 Description of Services
1.3 Scope and Period of Performance
2 SECTION II. PRODUCTION DESCRIPTION OF TASKS
2.1 Flight Test Kit Production
2.1.1 Program Objectives
2.1.2 Contract Objectives
2.1.3 Aerospace Vehicle Equipment Integration, Assembly, Test and Checkout
2.1.4 Parts Management Working Group and Parts, Materials, and Processes (PMP) Management Plan
2.1.5 Production Readiness Review and Audits
2.1.6 Manufacturing Practices and Materiel Fielding
2.1.7 Packaging, Handling, Storage and Transportation (PHS&T)
2.1.8 Program Management
3 SECTION III. GENERAL REQUIREMENTS
3.1 Contractor Travel
3.2 Scientific Technical Information (STINFO) and Controlled Unclassified Information (CUI)
3.3 Applicable Documents
3.4 Base or Area Badges for Access to Government Facilities
3.5 Common Access Card (CAC)
3.6 Continuation of Mission-Essential Services During a Crisis
3.7 Mission-Essential Contractor Services Plan
3.8 Days and Hours of Operation
3.9 Conservation of Utilities
3.10 Standards of Conduct
3.11 Identification of Contractor Personnel
3.12 Direct and Immediate Removal of Contractor Personnel
3.13 Qualified Workforce
APPENDIX A: ACRONYMS
APPENDIX B. REFERENCE DOCUMENTS
APPENDIX C: CONTRACT DATA REQUIREMENTS LISTING (CDRL)
APPENDIX D. SPACE LAUNCH DELTA 30 SAFETY OFFICE
1 SECTION I. DESCRIPTION OF SERVICES/SCOPE
1.1 Introduction
The flight test kit consists of the Flight Destruct System (FDS) and an Integrated Instrumentation System (IIS), and is expected to meet Space Launch Delta (SLD) 30 Range Safety and Air Force Global Strike Command (AFGSC) requirements and resolve obsolescence concerns. Flight test kit replenishment spares are necessary to sustain future Operational Test Launches (OTL). The OTLs are critical to validating the continued accuracy and reliability of the Minuteman (MM) III Intercontinental Ballistic Missile (ICBM) Weapons System and providing valuable data to ensure a safe, secure, and effective nuclear deterrent. The FT3 flight test kit is expected to perform the same function as the existing flight test kits and comply with Range Commanders Council (RCC) 319, Flight Termination Systems Commonality Standard, and RCC-324, Global Positioning and Inertial Measurements Range Safety Tracking Systems’ Commonality Standard as tailored for the FT3 Program.
1.2 Description of Services
The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to produce flight test kits to include flight spares to support OTLs except for those items specified in the FT3 Government Furnished Property (GFP) Listing as defined in this Performance Work Statement (PWS). The contractor shall perform to the standards in this contract.
1.3 Scope and Period of Performance
The Government estimates an overall contract period of performance (PoP) of up to 7 years (October 2027 to September 2034) for the base contract to buy 25 flight test kits. The Production CLINs include 001 Materials, Build, Assemble; 002 Data; 003 Travel; 004 Requalification.
2 SECTION II. Production Description of Tasks
2.1 Flight Test Kit Production
2.1.1 Program Objectives
2.1.1.1 As part of the FT3 Program Production Follow-On Contract (Operations & Support Phase), the contractor shall manufacture, produce and deliver, using FT3 approved technical data, specifications and drawings for 25 flight test kit replenishment spares.
2.1.1.1.1 The contractor shall review and analyze acceptance test data to determine if there are adverse trends.
2.1.1.2 The contractor shall implement corrective action with Government approval to resolve findings, negative trends, deficiencies, and nonconformities as identified.
2.1.2 Contract Objectives
2.1.2.1 The Government expects delivery of the first production flight test kit (spare) at Vandenberg Space Force Base (VSFB) in August 2032 to support launch GT 275 in November 2032. Once acceptance testing has been performed and the assets have been accepted by the Government, Range verification checks will be required prior to final configuration for flight, as outlined in the FT3 tailored versions of RCC 319-14 and RCC 324-11.
2.1.2.2 The contractor shall provide a delivery schedule upon contract award, detailing activities/tasks planned to deliver flight test kits 120 calendar days prior to scheduled OTLs per the current AFGSC MMIII OTL 5-year schedule.
2.1.2.3 The FT3 Production contractor will procure parts and materials to produce 25 FT3 flight test kits with expected delivery to VSFB 120 calendar days prior to OTL.
2.1.2.4 The contractor shall ensure timely and accurate delivery of all data deliverables IAW contract requirements and shall ensure data is marked with the appropriate STINFO (i.e., Distribution Statement, Export Control Warning statement, and Destruction Notice), Controlled Unclassified Information (CUI) and classification markings.
2.1.3 Aerospace Vehicle Equipment Integration, Assembly, Test and Checkout
2.1.3.1 The contractor shall procure all equipment, parts and materials required to support production for 25 flight test kits prior to contract PoP end.
2.1.3.2 The contractor shall assemble, check out and test flight test kits, then ship kits to VSFB just-in-time (120 days prior to flight for the primary and 90 days prior to flight for the spare) for acceptance testing and certification for flight by I-LAB personnel. These actions will pertain to the first five (5) flight test kits produced provided this requirement does not extend beyond the contract PoP. [CDRL A064, DI-QCIC-81891, Acceptance Test Reports]
2.1.3.3 For the remaining 20 IIS subkits, the contractor shall assemble, check out and conduct acceptance testing at Boeing-Heath for sell-off once IIS and FDS components are received from the manufacturers [CDRL A064, DI-QCIC-81891, Acceptance Test Reports (ATR)]. Upon completion of acceptance testing, the IIS and completed set of FDS components will be stored at Heath in appropriate shipping containers. The IIS will be stored on a Test and Transportation (TAT) or equivalent storage fixture. FDS components will be stored in an I-lab or Missile Processing Facility (MPF) crate ready for shipment. Shipment of these kits is determined by the
AFGSC MMIII OTL 5-year schedule. Flight test kits stored beyond the Production Follow-On contract POP end will be billed to the sustainment contract.
2.1.3.4 For the Ordnance subkit, the contractor shall direct shipment from the manufacturer to the VSFB Munitions Facility.
2.1.3.5 The contractor shall manage parts inventory and supply chain risk, including the procurement of spare components, to ensure zero schedule slippage due to component failures or anomalies.
2.1.3.6 The contractor shall provide management and engineering support to ensure test activities meet latest FT3 tailored revision of RCC-319-14(T), RCC-324-11(T), and AFSPCMAN 91-710, and coordinated with Range Safety accordingly.
2.1.3.7 The contractor shall provide management and engineering support to ensure qualification and acceptance test activities meet the latest version of DODI 5000.89_DAFI 99- 103, Capabilities-Based Test and Evaluation criteria and the latest version of MMIII Systems Program Office HB 99-1110, Test and Evaluation and are coordinated with MMIII Program Office accordingly.
2.1.3.8 The contractor shall provide engineering support for resolution of system/subsystem Acceptance Test Procedure (ATP) failures and anomalies.
2.1.3.9 The contractor shall conduct Materiel Defect Reporting using standard Air Force ICBM maintenance reporting processes IAW TO 00-35D-54, USAF Deficiency Reporting, Investigation, and Resolution.
2.1.3.10 The contractor shall ensure that any materiel defects identified during flight test kit acceptance testing are reported to the FT3 Program Manager. The Government will assess the defect and determine the appropriate corrective action.
2.1.3.11 The contractor shall notify the Government within the timeframe specified in the latest RCC 319-14(T) for all acceptance test failures.
2.1.3.12 The contractor shall notify the Government within the timeframe specified in the latest RCC 324-11(T) for all acceptance test failures.
2.1.3.13 The contractor shall provide a full failure analysis IAW latest FT3 tailored revision of RCC 319-14(T) for any flight safety component which does not meet all of its Acceptance Test criteria. [CDRL A059.1, DI-MISC-80508B/T, Technical Report - Studies/Services - Failure/Anomaly Resolution Report]
2.1.3.14 The contractor shall provide a full failure analysis IAW latest FT3 tailored revision of RCC 324-11(T) for any range tracking component which does not meet all of its Acceptance Test criteria. [CDRL A059.1, DI-MISC-80508B/T, Technical Report - Studies/Services - Failure/Anomaly Resolution Report]
2.1.3.15 The contractor shall implement Engineering Change Orders (ECO)/Engineering Change Proposals (ECP) as directed to include associated drawings updates, and Specification Change Notices (SCN) if any are required during contract execution. [CDRL A027, DI-SESS- 81000F/T, Product Engineering Design Data and Associated Lists and CDRL A030, DI-SESS- 80643E, Specification Change Notice (SCN)]
2.1.3.16 The contractor shall deliver Missile Guidance Set (MGS) (AN/DSW-23) assemblies in the modified flight test configuration to VSFB 120 calendar days in advance of the scheduled OTL flight. NOTE: All MGS assemblies will be furnished by United States Air Force (USAF) for contractor modification. MGS assemblies delivered beyond contract PoP end will be delivered under the Sustainment contract.
2.1.3.17 The contractor shall, for the first five flight test kits, modify an MGS (AN/DSW-23) with a new port hole while at Boeing Guidance Repair Center (BGRC) at Heath, Ohio, per drawing 25-94970 and using procedure 21-62947 to mount the antenna onto the MGS. For flight test kits stored beyond PoP end, modification of the MGS and the mounting of the antenna will be billed to the sustainment contract.
2.1.3.18 The contractor shall report actual measured weight for all flight test kit components at the ATP level. [CDRL A064, DI-QCIC-81891, Acceptance Test Reports]
2.1.3.19 The contractor shall deliver this list of weights to include the final IIS subkit weight to the Government as part of the delivery package of each flight test kit before launch. (This will not be included as a CDRL-Mass Properties Report) [CDRL A064, DI-QCIC-81891, Acceptance Test Reports]
2.1.3.20 The contractor shall test, troubleshoot, and certify the IIS for the first five flight test kits for flight, using the Minuteman Integrated Instrumentation System (IIS) Test Station (MITS) installed in the Integrated Laboratory (ILAB) at VSFB.
2.1.3.21 When executing ECOs, the contractor shall conduct T&E activities for potential flight test kit redesign and requalification to include test integration, scheduling and conduct (execution), simulated environment testing, necessary requirement updates, and revise test requirements and test plan development IAW Minuteman III Systems Program Office HB 99- 1110, Test and Evaluation. [CDRL A059.2, Technical Report - Study/Services (Verification Analysis Report); CDRL A060, DI-NDTI-80566, Test Plan; CDRL A061, DI-NDTI-80603, Test Procedure;
CDRL A062, DI-NDTI-80809, Test/Inspection Report; CDRL A064, DI-QCIC-81891, Acceptance Test Reports].
2.1.3.21.1 The contractor shall execute Class I and II changes as follows: Class I changes shall be performed under the GuSSC 2.0 Sustainment Contract, Appendix H using MMIII SPO-HB- 63-1101, Technical Review Board (TRB) as a reference. Class II changes for Production shall be performed under the Production Contract using MMIIISD-HB-99-1108 as a reference. Class determination must be done IAW 62-CMP Rev A, Appendix A.
2.1.3.22 The contractor shall provide safety assessments when there are changes to safety hazards IAW CDRL A067, DI-SAFT-80102, Safety Assessment Report (SAR).
2.1.3.23 The contractor shall update the Failure Mode Effects and Criticality Analysis (FMECA) Report when the design is changed, new failure modes are identified or if required by Government. [CDRL A102, DI-SESS-81495, Failure Mode Effects and Criticality Analysis (FMECA) Report]
2.1.4 Parts Management Working Group and Parts, Materials, and Processes (PMP) Management Plan
2.1.4.1 The contractor shall use the latest revision of the D2-28994-1 Parts, Materials, and Processes (PMP) Management Plan for requirements and guidance when procuring parts during production.
2.1.4.2 The contractor shall support the PMP Control Board to coordinate any obsolescence mitigation, parts, materials, process concerns or changes.
2.1.4.3 The contractor shall archive lot conformance data (screening and testing at piece-part level) and make available upon request for the duration of the service life of the deployed product.
2.1.4.4 The contractor shall ensure that each supplier of mission critical hardware performs the applicable incoming tests and inspections of parts and materials and meets the requirements of the procurement specification. For categories I and II, the contractor shall develop and maintain a database that captures all relevant data for received parts to include date code, purchase order requirements, and certificate of conformance data for the life of the program. The incoming inspection and testing of parts and materials shall be conducted IAW with the supplier’s approved PMP Management Plan.
2.1.4.5 The contractor shall perform assessments of subcontractor PMP implementation as required to verify compliance with PMP management and control practices as defined in the approved critical supplier’s hardware PMP plan.
2.1.4.6 The contractor shall conduct a failure analysis, in addition to PMP Management Plan requirements, when directed by the Government.
2.1.4.7 The contractor shall purchase piece part quantities sufficient to mitigate the potential of continual lot screening and requalification. This is necessary to reduce costs associated with screening and qualification of new lot date code piece parts as required per the RCC 319-14 (T) Appendix B and the FT3 Parts Management Plan.
2.1.5 Production Readiness Review and Audits
The contractor shall hold a Production Readiness Review (PRR) if necessary due to changes to the production line to ensure that the system design is ready for production, and the supplier has accomplished adequate production planning for entering Full Rate Production (FRP). The PRR shall be conducted IAW IEEE 15288.2, IEEE Standard for Technical Reviews and Audits on Defense Programs to review the specified technical data products and meet the exit criteria stated within. [CDRL A002, DI-ADMN-81249C; Meeting Agenda; CDRL A003, DI- MGMT-81605, Briefing Material; CDRL A004, DI-ADMN-81250C, Meeting Minutes]
2.1.6 Manufacturing Practices and Materiel Fielding
2.1.6.1 The contractor shall update the Manufacturing and Producibility Plan for full rate production with updated Manufacturing Bill of Materials; production and acceptance plan, and definition of responsibilities during production; and delivery plan. This plan shall include specific manufacturing and handling procedures required to maintain program protection IAW the D2-28817-1 Guidance Subsystem Support Contract (GuSSC) Program Protection Implementation Plan (PPIP) which is delivered on the GuSSC 2.0 Appendix H. FT3 Requirements contract. [CDRL A009, DI-MGMT-81889, Manufacturing Plan]
2.1.6.2 The contractor shall ensure flight test kit support equipment (GFE) is functioning in support of production. The GFE listing is maintained as part of the Guidance Subsystems Support Contract 2.0 Appendix H. FT3 Requirements and is updated annually.
2.1.6.3 The contractor shall monitor in-process hardware to include electronic components and assemblies for compliance with MIL-STD-1568, Materials and Processes for Corrosion Prevention and Control in Aerospace Weapons Systems, Society of Automotive Engineers (SAE); AS12500, Corrosion Prevention and Deterioration Control in Electronic Components and
Assemblies, AFNWC/NM-HB-21-1100, Corrosion Program and the D2-28991-1 FT3 Corrosion Prevention & Control (CPC) Plan during the various stages of manufacture. Final specifications will continue to be documented on drawings and any required Engineering Orders updates. Any production line corrosion or contamination problems that occur or may occur shall be reported to the FT3 program and the CPC representative. The problem will be reviewed and corrective action implemented. If there are any changes, the CPC Plan will need to be updated as required as part of the sustainment contract. (see MIL-STD-2073-1, Standard Practice for Military Packaging)
2.1.6.4 The contractor shall have an Integrated Product Team (IPT) managing all aspects of its subsystem/component product manufacturing and operational support activities. The contractor's supplier management will work with each IPT through the assigned responsible engineer and the procurement agent to include representatives from other appropriate disciplines to assist in defining supplier requirements for system safety, quality assurance, logistics support, reliability and maintainability, and other specialty disciplines, as required.
2.1.6.5 In compliance with the clause entitled “Inspection of Services,” 52.246-3 and 52.246-4, the contractor shall establish a complete Quality Control Program to ensure the requirements of this contract are provided as specified IAW the clause. The contractor shall institute quality assurance processes IAW D2-28843-1 Quality Assurance Program Plan (QAPP) to ensure quality of documentation, testing, analyses, and hardware during the manufacturing of systems/subsystems.
2.1.6.6 The contractor shall perform quality product evaluation audits during fabrication, assembly and installation activities. These audits may be in conjunction with first article inspection activities. Ensuring production process surveillance processes provide the surveillance requirements and methodology to verify compliance with processes, procedures, work instructions, and other requirements. Internal audits should be performed IAW processes as identified in the FT3 QAPP which establish requirements and responsibilities for implementing and maintaining an internal audit program that evaluates the Quality Management System (QMS), applicable contract requirements, conformity, effectiveness, and efficiency.
2.1.6.7 The contractor shall ensure all products provided to the Government are compliant with MIL-STD-130, Identification Marking of U.S. Military Property and Technical Manual 00- 25-260, Asset Marking and Tracking Item Unique Identification (IUID) Marking Procedures.
2.1.7 Packaging, Handling, Storage and Transportation (PHS&T)
2.1.7.1 The contractor shall coordinate the plan for assembly, kitting and delivery timeline for flight test kits (subkits) prior to contract award with final delivery schedule confirmed within 120 calendar days post contract award.
2.1.7.2 The contractor shall coordinate flight test kit (subkits) delivery with the MMIII Systems Program Office and the 377 TEG/576 FLTS.
2.1.7.3 The contractor shall ship subkits (first five flight test kits or up until PoP ends) IAW D2-29691-1, FT3 Transportation Plan, appropriate Air Force and Military Standard PHS&T requirements to VSFB from BGRC. (MIL-STD-2073-1E, Standard Practice for Military Packaging Requirements)
2.1.7.4 The contractor shall kit FDS assemblies, Electronic Safe and Arm Devices (ESAD) to include the Conduit Support System, at the BGRC, Heath OH, using fiberboard containers and placed in a wooden crate per MIL-STD-2073-1, Method 54.
2.1.7.5 The contractor shall handle electrostatic discharge sensitive (DS) parts of the flight test kit per MIL-STD-1686, Class 2.
2.1.8 Program Management
The contractor shall perform program management of the production of the flight test kits.
Program management includes the resources necessary to manage, direct, and control all efforts contributing to the production of the flight test kits. The contractor shall conduct bi-weekly leadership tag-ups which include development and distribution of briefings. The tag-ups shall include production status, detailing material buys, lot acceptance testing, requalification effort schedule and status, component build and shipment specifics. [A003, DI-MGMT-81605, Briefing Material]
2.1.8.1 Subcontract Management
2.1.8.1.1 The contractor shall manage all aspects of subcontract oversight. The contractor shall provide a bi-weekly performance update to the Government. Subcontractor Deliverable Requirement Lists (SDRL) shall be planned appropriately to support Government reporting requirements. [CDRL A008.1, DI-MGMT-81911, Work Management Plan (Subcontractor Management Plan)]
2.1.8.1.2 The contractor shall identify all subcontractors and develop subcontract management plans to include use of Small Business minority set asides such as Service Disabled Veteran- Owned Small Business (SDVOSB) and HubZone. The Subcontractor Management Plan must include small business goals, and detailed explanations for any standard goals that are not met.
[CDRL A008.2, DI-MGMT-81911, Work Management Plan (Small Business Subcontractor Report)]
2.1.8.2 Risk Management
2.1.8.2.1 The contractor shall manage the program risk IAW the D2-28801-1 Contractor’s Risk Management Plan.
2.1.8.2.2 The contractor shall identify, track, report, and present risks as part of the Risks, Issues, and Opportunities (RIO) Board.
2.1.8.2.3 The contractor shall provide standardized risk assessment and management functions, utilizing techniques which easily interface with the Government’s current risk management process. Program Management Reviews.
2.1.8.2.4 The contractor shall mitigate supply chain risk as referenced in Boeing’s delivered Supply Chain Risk Management (SCRM) Plan (delivered as part of the FT3 Sustainment contract modification) to ensure piece-parts, circuit boards, components, repair parts, etc., do not incorporate counterfeit parts, malicious code, or any other elements that would allow adversaries to gain unauthorized access to data, alter data, interrupt communications, or otherwise disrupt operations.
2.1.8.3 Cost and Software Data Reporting (CSDR)
2.1.8.3.1 The contractor shall systematically collect and report to Cost Assessment Data Enterprise (CADE) and the United States Government (USG) the actual contract costs and technical information based on the Office of the Secretary of War (OSW) Deputy Director Cost Analysis (DDCA)-approved CSDR plan (Attachment 1) in accordance with (IAW) the CSDR Manual, DoDM 5000.04.
2.1.8.3.2 The CSDR requirements are outlined per Attachment 1, CSDR Plan (DD Form 2794).
Inclusive in the plan is the information required by Cost Working Integrated Product Team (CWIPT) for the respective prime and subcontractors, i.e., schedule for report submission, and specific information as to format, address to send the information, and other pertinent facts.
2.1.8.3.3 The contractor shall submit electronically CDRL A231, DI-FNCL-82162, Cost and Hour Report (FlexFile); CDRL A238, DI-MGMT-82164, Quantity Data Report; CDRL A237, DI-MGMT-82165, Technical Data Report; and CDRL A235, DI-FNCL-81765C, Contractor Business Data Report (CBDR). The required form and file type for each CSDR is specified in its Data Item Description (DID).
2.1.8.3.4 The contractor data submitters must register through the CADE website (http://cade.osd.mil) and possess a DoD-approved External Certification Authorities (ECA) digital certificate or DoD-issued Common Access Card (CAC) to obtain a CADE Portal account and be authorized to upload CSDR content. Users can obtain access by submitting user information about themselves and their organizations to the CADE Portal and requesting a CSDR submitter user role.
2.1.8.3.5 The contractor shall flow down CSDR requirements contained in their prime contracts to all subcontractors who meet the reporting thresholds specified in DoDI 5000.73, or as required by the CWIPT. This includes subcontractors to electronically report directly to the CADE Portal using the CSDR Submit-Review System.
2.1.8.3.6 CSDR Readiness Review: A CSDR Readiness Review Meeting will be held 60 calendar days after contract award to include a discussion of the CSDR process that satisfies the guidelines contained in the DoDM 5000.04 and the requirements in the approved CSDR Plan and related Resource Distribution Table.
2.1.8.4 Requalification Effort
The contractor shall prepare and submit a Contract Funds Status Report (CFSR) to provide the Government with visibility into the flow of funds, track actual and projected expenditures, and accurately forecast future funding requirements. CFSR tracking and reporting requirements are tailored to apply exclusively to CLIN 004 Requalification. All Firm-Fixed-Price (FFP) CLINs are explicitly exempt from CFSR tracking and reporting requirements, and the Contractor shall ensure FFP costs are not co-mingled in the CFSR data. [A018, DI-MGMT-81468, Contract Funds Status Report (CFSR)]
3 SECTION III. General Requirements
3.1 Contractor Travel
The contractor shall perform travel in support of this effort, as required on a Cost Reimbursable No Fee (CRNF) CLIN basis.
3.1.1 Travel Expenses
The contractor shall ensure all contractor travel is in accordance with RFO 31.205-46 and the DoD Joint Travel Regulation (JTR) for all costs, airfares, per diem, allowances, and reimbursement of travel expenses. First class air travel is not authorized. Travel costs will be considered reasonable and allowable only to the extent that they do not exceed the maximum per diem rates in effect at the time of the travel. The Government reserves the right to disallow unreasonable travel. The contractor shall bill all travel expenses as a separate line item on all invoices. Labor costs are not allowed under the Travel Contract Line Item Number (CLIN); the Travel CLIN will be a cost reimbursement with no fee.
3.2 Scientific Technical Information (STINFO) and Controlled Unclassified Information
(CUI)
Department of Defense Instruction (DoDI) 5230.24, Distribution Statements on Technical Documents, Enclosure 4, Table 5, identifies six (6) authorized distribution statements for Scientific Technical Information (STINFO). The contractor shall mark all scientific technical data, regardless of media or form, with the appropriate STINFO markings (i.e., distribution statement, export control warning [when applicable], and destruction notice) as specified on the DD Form 1423-1, Contract Data Requirements List (CDRL).
For written or printed material, the STINFO markings shall appear in full text on the front cover/title page as specified in the CDRL. Distribution statements shall include all applicable “reasons” based on the contents of the document. The “date of determination” within each distribution statement shall reflect the date of the document, unless otherwise agreed to upon contract award. The Controlling DoD Office (CDO) will review all technical data (e.g., technical reports, test reports, final summaries, and briefings) prior to finalization to ensure the correct STINFO markings are applied to all scientific/technical documents. A distribution statement designation is distinct from, and in addition to, a security classification marking applied in accordance with (IAW) DoD Manual (DoDM) 5200.01, Volume 2, DoD Information Security Program: Marking of Information.
Controlled Unclassified Information (CUI) markings shall be applied to all applicable scientific, technical information documents IAW DoDI 5200.48_DAFI 16-1403, Controlled Unclassified Information (CUI). Utilize the Critical Information Indicators List when categorizing CUI data as AFI10-701, Operation Security (OPSEC) is applicable. The STINFO information (i.e., Distribution statement, Export Control Warning [when applicable] and destruction notice) will be fully spelled out, and will be placed above the CUI Designation Indicator box. The CUI box only lists the “Distribution Statement line and letter. Place “Controlled Unclassified Information” (do not abbreviate) in the header and footer of each page. NOTE: If the information does not fall within law, regulation, or government policy then the information is not CUI. IAW DFARS 252.204-7008, Compliance with Safeguarding Covered Defense Information Controls and 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting.
3.3 Applicable Documents
Compliance and reference documents related to specifications, standards, handbooks, regulations, instructions and tables applicable to the work required in the performance of this contract are listed in APPENDIX B: Reference Documents. If vendors are knowledgeable of critical documents or requirements not listed in this PWS, it is expected they inform the Government to ensure adequate coverage. The contractor shall use the latest version of compliance documents.
3.4 Base or Area Badges for Access to Government Facilities
The Government Program Manager will assist contractor personnel to obtain and process the necessary DoD forms for base or area badges for access to Government facilities and property.
The contractor shall have limited access to Government facilities, and must coordinate access and usage dates and times with the Government Program Manager at least 15 working days prior to the access date. The contractor shall protect Government property to prevent damage during the period of time the property is in the possession of the contractor. The contractor shall report promptly to the Contracting Officer (CO) all available facts relating to each instance of damage to Government property. The contractor shall not be in a Government facility without a Government supervisor present. Control of the facilities shall remain with the Government.
3.5 Common Access Card (CAC)
When a CAC is required in support of this effort and the Security Clearance level is UNCLASSIFIED, the following instructions apply. Note – The CAC approval process may take up to 4 weeks to complete and contractors are urged to consider these instructions before award (i.e., when preparing a proposal in response to an RFP) and prior to changing contractor personnel after award. The contractor shall have encryption capabilities in place to send and receive secure encrypted emails.
In accordance with Hill AFB Instruction 36-812, Issue of Common Access Cards to Contractors (Contractor Verification System), paragraph 6.1.5 the contractor "Must have favorable or higher adjudication based on a National Agency Check with Inquiries (NACI) or higher investigation."
In accordance with AFSSI 8522, Communications and Information, Chapter 3, Access to Information Systems and Networks, states:
3.5.1.1 Favorable Background Investigation. CSAs, in coordination with the security manager, will verify proper security clearance and background investigation checks, NACI, Single Scope Background Investigation) are submitted prior to granting a network user access to the AF-GIG.
Upon successful completion of initial Information Awareness training and verification of favorable background check, the user is authorized use of the network and is granted access to authorized network resources.
Refer to DAF Part 42, Common Access Cards (CAC) for Contractor Personnel, under the basic contract(s) for additional instructions and procedures that apply to obtain and manage CACs under individual task orders. One of the provisions of this clause is that the contractor shall provide a listing of personnel who require a CAC to the Contracting Officer. For purposes of individual task orders, in addition to the Contracting Officer, the contractor shall also submit the listing to the Program Manager and Contracting Officer Representative (COR).
3.6 Continuation of Mission-Essential Services During a Crisis
Designation of Services as Mission-Essential: The Functional Commander (FC) or civilian equivalent has determined certain services under this contract/order are mission-essential and will continue in the event of a crisis. The designation of services as mission-essential will not apply to an entire contract, but will apply only to services specifically identified as mission-essential by the FC or civilian equivalent. The mission-essential services under this contract/order include sustainment activities as required to support the OTL mission.
3.7 Mission-Essential Contractor Services Plan
The contractor shall submit a plan describing procedures for continuing performance of mission-essential services during a crisis. The contractor shall identify provisions for ensuring required personnel and resources are available to support continuity of operations for up to 30 calendar days or until normal operations can be resumed. The contractor shall submit any revision to the plan for approval prior to implementation. The contractor shall activate the plan only if authorized by the Government Contracting Officer acting under the direction of the FC or civilian equivalent.
3.8 Days and Hours of Operation
When work is performed at the Government’s location, the contractor shall perform the services during workdays Monday through Friday between the hours of 6:00 am and 6:00 pm, excluding Federal Holidays, local or national emergencies, administrative closings, or similar government directed facility closings. The days and hours of operation may be changed with prior approval from the government program manager and contracting officer. The days and hours of operation, (i.e., alternate work schedule) will be evaluated by the Government on an individual basis, depending upon the type and estimated duration of work activities and workload.
At all times, the contractor shall maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the government facility is not closed for the above reasons and when hiring contractor personnel, the contractor shall ensure…
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 .