2026 02 23__Amendment 00001 80MSFC26R0002 Final RFP to Amendment 00001 Appendix D Change Log.pdf
PDF 2 MB Posted
- Solicitation number
- 80MSFC26R0002
About this file
This document is Appendix C, a summary of changes between the final solicitation posted on January 30, 2026, and Amendment 00001 posted on February 2, 2026, for a federal contract opportunity. The changes resulted from industry comments and internal reviews and represent significant modifications to the Request for Proposal.
Key changes include: updating all contractual language from "shall" to "must"; updating numerous FAR and NASA FAR Supplement clauses in accordance with recent regulatory flight orders and procurement class deviations; creating fill-ins for Contract Line Item Number (CLIN) 0001 unit price and amount with "TBD" entries for other CLINs; adding clause 1852.232-77 Limitation of Funds (Fixed-Price); modifying CLIN 0001 Phase-in pricing from FFP/STBP to FFP/TBP; updating clause 52.246-11 Higher-Level Contract Quality Requirements to reference ISO 9001 and MSFC quality management standards; adding new FAR clauses including 52.215-15 Pension Adjustments, 52.215-18 Reversion of Plans for Postretirement Benefits, and 52.247-68 Report of Shipment; renaming the Information Technology Security Management Plan to Information System Security Plan; clarifying OCI Plan submission timing and requirements; modifying safety and security breach consequences; updating proposal page limitations and font requirements; adjusting benchmark direct labor rates; clarifying requirements for accounting system adequacy and FPRA/FPRP documentation; refining past performance submission instructions for joint ventures; and adding new sections on historical skill categories supporting classified work and incumbent WYE rates for engineering technicians.
View the file
Other files
Show all 27
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
6 E 16 52.246-11 52.246-11 Higher-Level Contract Quality Requirement. DEC 2014
(a) The Contractor shall comply with the higher-level quality standard(s) listed below.
Marshall Quality Management System Policy-Marshall Policy Directive
(MPD) 1280.1
(b) The Contractor shall include applicable requirements of the higher-level quality standard(s) listed in paragraph (a) of this clause and the requirement to flow down such standards, as applicable, to lower-tier subcontracts, in-
(1) Any subcontract for critical and complex items (see (b) and (c)); or 46.203
(2) When the technical requirements of a subcontract require-
(i) Control of such things as design, work operations, in-process control, testing, and inspection; or
(ii) Attention to such factors as organization, planning, work
52.246-11 Higher-Level Contract Quality Requirement. DEC 2014
(a) The Contractor shall comply with the higher-level quality standard(s) listed below.
Quality Management System Requirements, ISO 9001
MSFC Quality Management Policy, Marshall Policy Directive 1280.1
Marshall Quality Management System, Marshall Procedural Requirements 1280.10
(b) The Contractor shall include applicable requirements of the higher-level quality standard(s) listed in paragraph (a) of this clause and the requirement to flow down such standards, as applicable, to lower-tier subcontracts, in-
(1) Any subcontract for critical and complex items (see (b) and (c)); or 46.203
(2) When the technical requirements of a subcontract require-
(i) Control of such things as design, work
21 L L-22 Volume II – Cost Volume Instructions, a., 9.
N/A In accordance with FAR 16.301-3, Limitations, Offerors (to include Joint Ventures, if applicable) and major subcontractors must have an adequate accounting system for identifying and segregating costs prior to award of a cost reimbursement contract. Therefore, Cost volume(s) should be prepared in a manner consistent with each company's current adequate accounting system. Offerors and applicable subcontractors must provide the audit report number and date of approval for their accounting system. If a company's accounting system has not been approved, state “currently no approved accounting system” and prepare and submit a completed SF1408, Preaward Survey of Prospective Contractor- Accounting System (Attachment L- 11), as part of this volume. Cost volume(s) should be prepared with sufficient detail to allow direct and indirect rate verification and audit of selected costs by the cognizant audit office.
If an Offeror is relying on the accounting system adequacy of a Joint Venture team member, sister company, or any other affiliated
26 L L-37 Volume III – Past Performance Volume Instructions, (c)
Offerors which are joint ventures (JVs) should provide at least one of the six past performance referenced contracts required above in the name of the JV. If the JV is newly established and cannot provide past performance referenced contracts in the name of the JV, then past performance referenced contracts from individual partners of the JV should be submitted for consideration, not to exceed a combined total of six referenced contracts. One past performance referenced contract should be provided for the JV managing partner.
Offerors which are joint ventures (JVs) should provide at least one of the six past performance referenced contracts required above in the name of the JV. If the JV is newly established and cannot provide past performance referenced contracts in the name of the JV, then past performance referenced contracts from individual partners of the JV should be submitted for consideration, not to exceed a combined total of six referenced contracts. One past performance referenced contract should be provided for the JV managing partner.
References submitted for individual JV partners or Offerors for performance as part of an unpopulated JV must clearly describe the specific portion of the effort performed by that entity, independent of the overall JV’s performance. The narrative must identify, as applicable: the entity’s specific scope of work and functional responsibilities; percentage or relative share of work performed by that entity; key deliverables, outcomes, or performance results directly attributable to that entity; and, the entity’s management, technical, or
33 M M-7 If an Offeror is a new joint venture (JV) without a past performance record, past performance will be evaluated for each individual JV partner for which a referenced contract is submitted, in accordance with the relevancy thresholds established for the Offeror (see also 13 C.F.R. § 124.513(f)). Participation of an individual JV partner in another JV will be evaluated provided that the partner’s sole effort is clearly described and meets established relevancy criteria. When an Offeror submits a past performance reference for work performed as part of a JV, the offeror must clearly delineate the specific portion of the effort performed by that entity, independent of the overall JV performance. “Sole effort” in this context refers to the individual partner’s contribution, not the JV’s collective performance. The past performance submission should identify as applicable: the partner’s specific scope of work and functional responsibilities; the percentage or relative share of work performed by that partner; key deliverables, outcomes, or performance results directly attributable to that partner;
and, the partner’s management, technical, or operational control over
If an Offeror is a new joint venture (JV) without a past performance record, past performance will be evaluated for each individual JV partner for which a referenced contract is submitted, in accordance with the relevancy thresholds established for the Offeror (see also 13 C.F.R. § 124.513(f)).
Participation of an individual JV partner or Offerors for performance in another, unpopulated, JV will be evaluated provided that the entity’s effort meets established relevancy criteria. Quality of performance will be assessed based on the quality of the JV as a whole.
Participation of an individual JV partner or Offerors for performance as part of another, populated, JV will be evaluated provided the entity’s involvement constitutes a sufficient role in the populated JV for the Government to consider the entirety of the referenced populated JV performance in the evaluation. Quality of performance will be assessed based on the quality of the JV as a whole.
The Government may consider whether past performance references submitted either as unpopulated or
File details come from the government source that posted it. Updated .