Solicitation Amendment N4008525R26390001 SF 30.pdf

PDF 787 KB Posted

Attached to
N4008525R2639 DESIGN-BID-BUILD P-222: MQ-25 AIRCRAFT LAYDOWN FACILITIES, NAVAL STATION NORFOLK, NORFOLK, VA
Solicitation number
N4008525R2639
Issued by

About this file

This document is Amendment 0001 to Solicitation N4008525R2639, issued by NAVFACSYSCOM MID-ATLANTIC on 5 February 2026. The amendment extends the deadline for receipt of offers and incorporates two primary changes to the solicitation requirements.

The amendment revises DFARS Clause 252.204-7021 (Contractor Compliance with the Cybersecurity Maturity Model Certification Level Requirements) and adds DFARS Provision 252.204-7025 (Notice of Cybersecurity Maturity Model Certification Level Requirements). The key requirement is that contractors must maintain a current Cybersecurity Maturity Model Certification (CMMC) Level 2 (Self) status for all information systems that will process, store, or transmit Federal Contract Information (FCI) or Controlled Unclassified Information (CUI) during contract performance. Contractors must have current CMMC status in the Supplier Performance Risk System (SPRS) and maintain annual affirmations of continuous compliance. If a contractor holds Conditional CMMC status, it must close out a valid plan of action and milestones to achieve Final status. The amendment also addresses subcontractor CMMC requirements, requiring subcontractors to maintain appropriate CMMC levels based on 32 CFR 170.23 flowdown requirements. Additionally, the amendment provides responses to four pre-proposal inquiries (PPIs), including confirmation that CMMC Level 2 (Self) is the minimum required level (reduced from a previously proposed Level 2 C3PAO requirement), that CSP documents will not be redacted, and that the project has been determined exempt from Project Labor Agreement requirements.

View the file

Other files

File Type Posted
Attachment G Individual Small Business Subcontracting Plan.docx DOCX document
Attachment F Small Business Participation Commitment.docx DOCX document
JA ML2650 25R2639 P222 ILDFA Redacted.pdf PDF
Solicitation Amendment N4008525R26390008 SF 30.pdf PDF
K3237099 LP-48 HazMat Report 3.5.26 - signed.pdf PDF
01 31 23.13 20.pdf PDF
Amendment 0007 Continuation Sheet.pdf PDF
Solicitation Amendment N4008525R26390007 SF 30.pdf PDF
REGISTER.pdf PDF
TABLE OF CONTENTS.pdf PDF
13 49 20.00 10.pdf PDF
Solicitation Amendment N4008525R26390006 SF 30.pdf PDF
P222_1737012_01 91 00.15 22.pdf PDF
Crane - LP48 1-DATA SHEET.pdf PDF
P222_1737012_Geotech Report.pdf PDF
P222_1737012_28 31 76.pdf PDF
Attachment H - Price Proposal Form_rev1.pdf PDF
P222_1737012_Drawings_volume II_Rev 001_SIGNED.pdf PDF
Solicitation Amendment N4008525R26390005 SF 30.pdf PDF
P222_1737012_04 20 00.pdf PDF
Amendment 0005 Continuation Sheet.pdf PDF
P222_1737012_32 13 13.06.pdf PDF
P222_1737012_09 29 00.pdf PDF
P222_1737012_07 60 00.pdf PDF
FY26 Naval Station Norfolk Utility Costs.pdf PDF
P222_1737012_07 21 13.pdf PDF
P222_1737012_REGISTER.pdf PDF
P222_1737012_Drawings_volume I_Rev 001_SIGNED.pdf PDF
P222_1737012_13 34 20.pdf PDF
Crane - LP48 2-DATA SHEET.pdf PDF
Solicitation Amendment N4008525R26390004 SF 30.pdf PDF
JA ML2623 25R2639 P222 ASSA Abloy Redacted.pdf PDF
JA ML2624 25R2639 P222 SRG RF Shielding Redacted.pdf PDF
26R2639 P222 Site Visit Log.pdf PDF
Solicitation Amendment N4008525R26390003 SF 30.pdf PDF
Solicitation Amendment N4008525R26390002 SF 30.pdf PDF
Attachment B - PIEE Vendor Access Instructions.pdf PDF
1737012_dwg 02of02_P222.pdf PDF
Attachment M - P222 Site Visit Map.pdf PDF
1737012_spec 01of04_P222.pdf PDF
1737012_dwg 01of02_P222.pdf PDF
Attachment C- Construction Experience Project Data.docx DOCX document
Attachment D- Past Performance Questionnaire.docx DOCX document
Attachment H - Price Proposal Form.pdf PDF
Attachment E- Historical Small Business Utilization.docx DOCX document
Attachment G- Individual Small Business Subcontracting Plan.docx DOCX document
1737012_spec 04of04_P222.pdf PDF
Attachment F- Small Business Participation Commitment.docx DOCX document
Attachment L - JA ML-26-01 P222 MQ25 Hangar Brand Name or Equal Finishes_Reda.pdf PDF
1737012_spec 03of04_P222.pdf PDF
Show 40 more

Latest 50 of 56 listed here. See the rest on GovTribe.

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

R

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

16C. DATE SIGNED

Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE PAGE OF PAGES

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6) CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBE

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

Created On:

05 Feb 2026, 21:42 PM Greenwich Mean Time

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

Section 00 30 00 - Available Information

Miscellaneous text in this section has been added to:

Amendment 0001

This amendment is issued to incorporate the following:

1. Incorporate revised DFARS Clause and incorporate applicable DFARS Provision

2. Provide responses to Pre-proposal Inquiries (PPIs) (attached separately)

1. DFARS Clause 252.204-7021 Contractor Compliance with the Cybersecurity Maturity Model Certification Level Requirements (revised below) and DFARS Provision 252.204-7025 Notice of Cybersecurity Maturity Model Certification Level Requirements (added below)

2. Provide responses to Pre-proposal Inquiries (PPIs) (attached separately)

Section 00 70 00 - Conditions of the Contract

Additional Information/Notes

The following clauses were added:

DFARS Clauses Incorporated by Full Text

252.204-7025 Notice of Cybersecurity Maturity Model Certification Level Requirements. (Nov 2025)

NOTICE OF CYBERSECURITY MATURITY MODEL CERTIFICATION LEVEL REQUIREMENTS (NOV 2025)

(a) . As used in this provision, "controlled unclassified information (CUI)," "current," "Cybersecurity Maturity Model Certification Definitions (CMMC) status," "Cybersecurity Maturity Model Certification unique identifier (CMMC UID)," "Federal contract information (FCI)", and "plan of action and milestones" have the meaning given in the Defense Federal Acquisition Regulation Supplement 252.204-7021, Contractor Compliance With the Cybersecurity Maturity Model Certification Level Requirements, clause of this solicitation.

(b)(1) . The CMMC level required by this solicitation is: . This Cybersecurity Maturity Model Certification (CMMC) level CMMC Level 2 (Self) CMMC level, or higher (see 32 CFR part 170), is required prior to award for each contractor information system that will process, store, or transmit Federal contract information (FCI) or controlled unclassified information (CUI) during performance of the contract.

(2) The Offeror will not be eligible for award of a contract, task order, or delivery order resulting from this solicitation if the Offeror does not have, for each of the contractor information systems that will process, store, or transmit FCI or CUI and that will be used in performance of a contract resulting from this solicitation-

(i) The current CMMC status entered in the Supplier Performance Risk System (SPRS) ( ) at the CMMC level required https://piee.eb.mil by paragraph (b)(1) of this provision; and

(ii) A current affirmation of continuous compliance with the security requirements identified at 32 CFR part 170 in SPRS.

N4008525R26390001

(c) . If the Offeror has a CMMC Status of Conditional, the Offeror shall successfully close out a valid plan of Plan of action and milestones action and milestones (32 CFR 170.21) to achieve a CMMC Status of Final.

(d) . The Offeror shall provide, in the proposal, the CMMC unique identifier(s) (CMMC UIDs) issued by SPRS for CMMC unique identifiers each contractor information system that will process, store, or transmit FCI or CUI during performance of a contract, task order, or delivery order resulting from this solicitation. The Offeror also shall update the list when new CMMC UIDs are generated in SPRS. The CMMC UIDs are provided in SPRS after the Offeror enters the results of self-assessment(s) for each such information system.

(End of provision)

The following clauses were modified:

252.204-7021Contractor Compliance with the Cybersecurity Maturity Model Certification Level Requirements.

Nov 2025 hereby reads as follows:

CONTRACTOR COMPLIANCE WITH THE CYBERSECURITY MATURITY MODEL CERTIFICATION LEVEL REQUIREMENTS (NOV 2025)

(a) . As used in this clause- Definitions

"Controlled unclassified information" means information the Government creates or possesses, or information an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Governmentwide policy requires or permits an agency to handle using safeguarding or dissemination controls (32 CFR 2002.4(h)).

"Current" means-

(1) With regard to Conditional Cybersecurity Maturity Model Certification (CMMC) Status-

(i) Not older than 180 days for Conditional Level 2 (Self) assessments and Conditional Level 2 (certified third-party assessment organization (C3PAO)) assessments, with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Conditional CMMC Status date (see 32 CFR

170.16 and 170.17); and

(B) A corresponding affirmation of continuous compliance by an affirming official (see 32 CFR 170.4); and

(ii) Not older than 180 days for Conditional Level 3 (Defense Industrial Base Cybersecurity Assessment Center (DIBCAC)) assessments, with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Conditional CMMC Status date (see 32 CFR 170.18); and

(B) A corresponding affirmation of continuous compliance by an affirming official;

(2) With regard to Final CMMC Status-

(i) Not older than 1 year for Final Level 1 (Self), with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Final CMMC Status date (see 32 CFR 170.15);

and

(B) A corresponding affirmation of continuous compliance, not older than 1 year, by an affirming official;

(ii) Not older than 3 years for Final Level 2 (Self) assessments and Final Level 2 (C3PAO) assessments, with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Final CMMC Status date (see 32 CFR 170.16 and 170.17); and

(B) A corresponding affirmation of continuous compliance, not older than 1 year, by an affirming official; and

(iii) Not older than 3 years for Final Level 3 (DIBCAC) assessments, with-

(A) No changes in compliance with the requirements at 32 CFR part 170 since the Final CMMC Status date (see 32 CFR 170.18);

and

(B) A corresponding affirmation of continuous compliance, not older than 1 year, by an affirming official; and

(3) With regard to affirmation of continuous compliance (32 CFR 170.22), not older than 1 year with no changes in compliance with the requirements at 32 CFR part 170.

"Cybersecurity Maturity Model Certification (CMMC) status" means the result of meeting or exceeding the minimum required score for the corresponding assessment. The potential statuses are as follows:

(1) Final Level 1 (Self).

(2) Conditional Level 2 (Self).

(3) Final Level 2 (Self).

(4) Conditional Level 2 (C3PAO).

(5) Final Level 2 (C3PAO).

(6) Conditional Level 3 (DIBCAC).

(7) Final Level 3 (DIBCAC).

"Cybersecurity Maturity Model Certification unique identifier (CMMC UID)" means 10 alpha-numeric characters assigned to each CMMC assessment and reflected in the Supplier Performance Risk System (SPRS) for each contractor information system.

"Federal contract information (FCI)" means information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government. It does not include information provided by the Government to the public, such as on public websites, or simple transactional information, such as information necessary to process payments.

"Plan of action and milestones" means a document that identifies tasks to be accomplished. It details resources required to accomplish the elements of the plan, any milestones in meeting the tasks, and scheduled completion dates for the milestones, as defined in National Institute of Standards and Technology Special Publication 800-115 (32 CFR 170.21).

(b) . The Cybersecurity Maturity Model Certification (CMMC) is a framework for assessing a contractor's compliance with Framework applicable information security protections (see 32 CFR part 170).

(c) . The CMMC assessments will not duplicate efforts from any other comparable DoD assessment, except for rare circumstances Duplication when a reassessment may be necessary, for example, when there are indications of issues with cybersecurity and/or compliance with CMMC requirements.

(d) . The Contractor shall- Requirements

(1)(i) Have and maintain for the duration of the contract a current CMMC status at the following CMMC level, or higher: CMMC Level 2 (Self) for all information systems used in performance of the contract, task order, or delivery order that process, store, or transmit FCI or CUI; and

(ii) Consult 32 CFR 170.23 related to the flowdown of the CMMC requirements, and flow down the correct CMMC level to subcontracts and other contractual instruments;

(2) Only process, store, or transmit FCI or CUI on contractor information systems that have a CMMC status at the CMMC level required in paragraph (d)(1) of this clause, or higher;

(3) Complete on an annual basis, and maintain as current, an affirmation, by the affirming official (see 32 CFR 170.4), of continuous compliance with the requirements associated with the CMMC level required in paragraph (d)(1) of this clause in the Supplier Performance Risk System (SPRS) ( ) for each CMMC UID applicable to each of the contractor information systems that process, store, or transmit FCI https://piee.eb.mil or CUI and that are used in performance of the contract;

(4) Ensure all subcontractors and suppliers complete prior to subcontract award, and maintain on an annual basis, an affirmation, by the affirming official (see 32 CFR 170.4), of continuous compliance with the requirements associated with the CMMC level required for the subcontract or other contractual instrument for each of the subcontractor information systems that process, store, or transmit FCI or CUI and that are used in performance of the subcontract; and

(5) If the Contractor has a CMMC Status of Conditional, successfully close out a valid plan of action and milestones (32 CFR 170.21) to achieve a CMMC Status of Final.

(e) . The Contractor shall- Reporting

(1) Submit to the Contracting Officer-

(i) The CMMC UID(s) issued by SPRS for contractor information systems that will process, store, or transmit FCI or CUI during performance of the contract; and

(ii) Any changes in the CMMC UIDs generated in SPRS throughout the life of the contract, task order, or delivery order, if applicable;

(2) Enter into SPRS the results of a current self-assessment for each CMMC UID, not covered by a C3PAO assessment or DIBCAC assessment, applicable to each of the contractor information systems that process, store, or transmit FCI or CUI and that are used in performance of the contract; and

(3) Complete in SPRS on an annual basis and maintain as current an affirmation of continuous compliance by the affirming official (see 32 CFR 170.4) for each self-assessment, C3PAO assessment, or DIBCAC assessment required under the contract in SPRS.

(f) . The Contractor shall- Subcontracts

(1) Insert the substance of this clause, including this paragraph (f) and excluding paragraph (e)(1), in subcontracts and other contractual instruments, including those for the acquisition of commercial products or commercial services, excluding commercially available off-the-shelf items, if the subcontract or other contractual instrument will contain a requirement to process, store, or transmit FCI or CUI; and

(2) Prior to awarding a subcontract or other contractual instrument, ensure that the subcontractor has a current CMMC certificate or current CMMC status at the CMMC level that is appropriate for the information that is being flowed down to the subcontractor based on the requirements at

32 CFR 170.23.

(End of clause)

2. Pre- proposal Inquiry Responses

PPI

Page Section Paragraph Question Response

51 of

Project Solicitation

N/A

Per the project solicitation, DFAR 252.204-7021 (Contractor Compliance with the Cybersecurity Maturity Model Certification Level Requirements) is included. Page 51 of 65 states, the Contractor is required to have and maintain a CMMC status of Level 2 (C3PAO) or higher. 32 CFR

170.23 requires the correct CMMC level to flow down to subcontractors.

Per CFR 170.23, if a subcontractor will process, store, or transmit CUI in performance of the subcontract and the associated prime contract has a requirement for a CMMC status of Level 2 (C3PAO), then the CMMC status of Level 2 (C3PAO) is the minimum requirement for the subcontractor.

It is our understanding from surveying the market on other Government projects requiring CMMC, that there are minimal subcontractors in which obtain a Status of Level 2 (Self), let alone a Level 2 (C3PAO) Status. It is recommended the Government reevaluate the CMMC Status Level required for this project. Due to the lack of availability in the subcontracting market, and the ability to comply with this DFAR, any status greater than Level 2 (Self) will result in the inability to bid this project.

Concur with recommended required Level:

CMMC Level 2 (Self) is sufficient.

DFAR Clause 252.204-7021:

Contractor Compliance with the Cybersecurity Maturity Model Certification Level Requirements has been edited (Please see Amendment 0001).

7 of

It appears the only documents which contain CUI information are the CSP files. Is it possible to redact information from the CSPs to eliminate CUI information? By doing this, the CMMC Level Status required per DFAR 252.204-7021 could be reduced to a Level 1 (Self) as there would be only FCI (and not CUI). This will allow for a more adequate

CMMC Level 2 (Self) will be the minimum level allowed, therefore the CSP will not be redacted. Please see solicitation on instructions on how to capacity of subcontractors to pursue, propose on and support this Project.

request CSP documents.

As of February 4, 2022, Executive Order 14063 was signed and requires federal construction projects valued at $35 million or more to use Project Labor Agreements (PLAs). In review of the project solicitation, it does not appear FAR 52.222-33 and/or 52.222- 34 are included which requires Project Labor Agreements. Please confirm this project has been evaluated and determined to be exempt from the use of a PLA.

Confirmed, this project has been evaluated and has been determined to be exempt from the use of a

PLA.

IDCode: J
Page: 1
Pages: 5
AmendNo: 0001
EffDate: 05 Feb 2026
ReqNo: See Continuation Sheet
ProjNo: 1737012
IssCode: N40085
AdmCode:
IssuedBy: NAVFACSYSCOM MID-ATLANTIC

9324 VIRGINIA AVENUE, NORFOLK VA 23511-0395

NORFOLK, VA 23511-0395

UNITED STATES

CATHARINE Keeling, Email: catharine.a.keeling.civ@us.navy.mil Telephone: 757-341-0150 AdminBy:

SCD: PAS:

ContractorNameAdd:
Code:
FacCode:
SolChg: 1
SolNo: N4008525R2639
SolDate: 26 Jan 2026
AwardChg: Off
AwardNo:
AwardDate:
Amended: 1
OffrExt: Off
OffrNoEx: 1
NoCopies: 1
ApprData: See Section 00 70 00 - Conditions of the Contract
ChgeOrd: Off
ChgeOrder:
Modify: Off
SuppAgre: Off
SuppAuth:
ModOthr: Off
OthrSpec:
NoReq: Off
Require: Off
Copies:
Descript: See Schedule
ContNameTitle:
CoNameTitle:
ContDate:
CODate:

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