2026 01 30 80MSFC26R0002 Appendix B DRFP to RFP Change Log.pdf

PDF 5 MB Posted

Attached to
Final RFP Engineering Services and Science Capability Augmentation (ESSCA) II
Solicitation number
80MSFC26R0002
Issued by

About this file

This document is an appendix to a Request for Proposal (RFP) that delineates significant changes made between the draft solicitation posted on SAM.gov on September 30, 2025, and the final RFP. The changes resulted from industry and internal review comments and represent substantive modifications across multiple sections, though grammatical and typographical corrections are excluded from this summary. Key changes include: revision of mandatory language from "shall" to "must" throughout; updates to numerous FAR and NASA FAR Supplement clauses to align with the Revolutionary FAR Overhaul (RFO) and associated NASA Procurement Class Deviations; modification of contract line item (CLIN) unit descriptions from "Unit Each" to "Unit Job"; and extension of the funds availability date from September 30, 2026, to September 30, 2027. Additional notable modifications involve changes to subcontracting plan requirements, award fee evaluation periods, skills augmentation transition options, initial Approval for Contract Award (ACA) requirements for specific NASA contracts, mandatory training course specifications, and security-related clauses addressing cybersecurity and privacy role-based training requirements.

The RFP encompasses an Engineered Systems and Software for Control Applications II (ESSCA II) contract valued at contract level with both Cost-Plus-Award-Fee (CPAF) and Cost-Plus-Fixed-Fee (CPFF) ordering periods anticipated, covering Contract Years 1–4 and 5–8 respectively. Significant evaluation and proposal instruction changes address past performance content element groupings, subcontractor identification (shifted from "applicable" to "major" subcontractors), organizational management structure terminology (changed from "key personnel" to "vital positions"), Mission Suitability volume page limits (increased from 175 to 215 pages), cost volume submission requirements emphasizing contractor responsibility for formula accuracy, labor rate escalation provisions, and the addition of new Commercial Artificial Intelligence (AI) Risk and Impact Assessment (CAIRA) requirements per DRD 1839CD-006. Performance evaluation now references Attachment J-3 throughout contract life regardless of contract type, with particular emphasis on skills augmentation work assessment mechanisms and consideration of unmet Acceptable Performance Levels in award fee determination.

View the file

Other files

File Type Posted
2026 07 23__Amendment 00004 80MSFC26R0002 Amendment 00003 to Amendment 00004 Appendix C Change Log.pdf PDF
2026 07 23__Amendment 00004 80MSFC26R0002 SF30 and Continuation.pdf PDF
2026 07 06__Amendment 00004 80MSFC26R0002 Attachment L-1 Excel Pricing Model.xlsx XLSX spreadsheet
2026 07 23__Amendment 00004 80MSFC26R0002 Cover Letter with Appendix A.pdf PDF
2026 07 23__Amendment 00004 80MSFC26R0002 Sections J-M.docx DOCX document
2026 07 06__Amendment 00003 80MSFC26R0002 Cover Letter with Appendix A_B.pdf PDF
2026 07 06__Amendment 00003 80MSFC26R0002 ESSCA II RFP Sections A-I.pdf PDF
2026 07 06__Amendment 00003 80MSFC26R0002 Attachment L-1 Excel Pricing Model.xlsx XLSX spreadsheet
2026 07 06__Amendment 00003 80MSFC26R0002 SF30 and Continuation.pdf PDF
2026 07 06__Amendment 00003 80MSFC26R0002 Sections J-M Rev 1.docx DOCX document
80MSFC26R0002 ESSCA II RFP Amendment 00001 to Amendment 00003 Clause Provision Change Matrix.pdf PDF
2026 07 06__Amendment 00003 80MSFC26R0002 Amendment 00002 to Amendment 00003 Appendix C Change Log.pdf PDF
2026 02 27_Amendment 00002 80MSFC26R0002 SF30.pdf PDF
2026 02 27__80MSFC26R0002 Amendment 00002 ESSCA II Attachment L-1 Excel Pricing Model.xlsx XLSX spreadsheet
80MSFC26R0002 ESSCA II RFP to Amendment 00001 Clause and Provision Change Matrix.pdf PDF
2026 02 27__Amendment 00002 80MSFC26R0002 Sections J-M.docx DOCX document
2026 02 23__Amendment 00001 80MSFC26R0002 Appendix C RFP Questions and Responses.pdf PDF
2026 02 23_Amendment 00001 80MSFC26R0002 SF30_.pdf PDF
2026 02 23__Amendment 00001 80MSFC26R0002 Final RFP to Amendment 00001 Appendix D Change Log.pdf PDF
2026 02 23__Amendment 00001 80MSFC26R0002 Sections J-M.docx DOCX document
2026 02 23__Amendment 00001 80MSFC26R0002 ESSCA II RFP Sections A-I.pdf PDF
2026 02 09 80MSFC26R0002 ESSCA II Draft RFP to Final RFP Clause and Provision Change Matrix.pdf PDF
2026 01 30 80MSFC26R0002 Attachment J-12-A Installation Accountable Property List.xlsx XLSX spreadsheet
2026 01 30 80MSFC26R0002 ESSCA II Attachment L-1 Excel Pricing Model.xlsx XLSX spreadsheet
2026 01 30 80MSFC26R0002 ESSCA II Final Cover Letter and Sections J-M.docx DOCX document
2026 01 30 80MSFC26R0002 Appendix A DRFP Questions and Responses.pdf PDF
2026 01 30 80MSFC26R0002 ESSCA II RFP Sections A-I.pdf PDF
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

125 L L-36 Volume III – Past Performance Volume Instructions (d) (2)

Content - For Offerors, a referenced contract’s content relevancy will be determined based on how well the work performed aligns with the applicable elements of Attachment J-1, Performance Work Statement (PWS) (see PWS WYE Percentage Assignment Table below), and for subcontractors, how well the work performed aligns with the subcontractor’s proposed workshare, as indicated in the PWS WYE Percentage Assignment Table.

For the Offeror, referenced contract(s) shall demonstrate relevant experience in at least four of the 14 PWS elements identified in the PWS WYE Percentage Assignment Table [i.e., PWS Sections

2.0 (2.1, 2.4, 2.5, 2.6, and 2.10), 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 3.12, 4.0] to be considered relevant in content. For proposed subcontractor(s), relevancy will be determined relative to the content element(s) assigned to that subcontractor.

Content - For Offerors, a referenced contract’s content relevancy will be determined based on how well the work performed aligns with the applicable content elements in the Past Performance Content Element WYE Table, shown below. Content elements are groupings of varied Attachment J-1, Performance Work Statement elements and have been established for Past Performance evaluation purposes only.

For the Offeror, referenced contract(s) shall demonstrate relevant experience in at least two of the five content element groups identified in the Past Performance Content Element WYE Table to be considered relevant in content. An Offeror’s referenced contract can demonstrate relevant experience for any of the elements in a content element group to be considered relevant for the entire group.

For subcontractors, a referenced contract’s content relevancy will be determined based on how well the work performed in the referenced contract aligns with the subcontractor’s proposed workshare, as indicated in the PWS Element WYE Percentage Assignment Table. For proposed subcontractor(s), relevancy will be determined relative to the specific individual PWS elements assigned to that subcontractor.

154 M M-6 Factor III – Past Performance Volume Evaluation, (b)

In determining the overall relevancy of individual referenced contracts, each referenced contract will be evaluated in the order of size, content, and complexity. If a referenced contract is determined to be not relevant in either size, content, or complexity, it will be determined not relevant overall and will not be further evaluated. NASA reserves the right to evaluate past performance referenced contracts for subcontractors other than major subcontractors that have the potential to impact performance of the proposed contract. 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.

References for protégé members of any proposed mentor-protégé joint venture, HUBZone members of any HUBZone joint venture, and 8(a) participants of any 8(a) joint venture will be evaluated in accordance with the relevancy

In determining the overall relevancy of individual referenced contracts, each referenced contract will be evaluated in the order of size, content, and complexity. If a referenced contract is determined to be not relevant in either size, content, or complexity, it will be determined not relevant overall and will not be further evaluated. NASA reserves the right to evaluate past performance referenced contracts for subcontractors other than major subcontractors that have the potential to impact performance of the proposed contract. As part of its confidence level assessment, the Government will consider the past performance of other entities (e.g., parent, affiliate) where meaningful involvement is clearly described; however, the Government is not obligated to assess similar impact on the offeror’s ability to successfully perform the required effort as those references performed by the prime offeror. The Government may also consider other factors that contribute to overall confidence such as the breadth of relevant coverage across the applicable PWS elements and demonstrated relevant performance as a prime contractor. If an Offeror is a new joint venture (JV) without a past performance record, past performance thresholds established for proposed subcontractors (see 13 C.F.R. § 125.8(e), 13 C.F.R. § 126.616(f), and 13 C.F.R. § 124.513(f), respectively).

Parent or affiliate references for the Offeror will be held to the relevancy thresholds established for the Offeror.

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 populated 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 populated 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 its portion of the work. The Government will evaluate such past performance based on the relevance and quality of the proposing partner’s

File details come from the government source that posted it. Updated .