W51AA126RA002 Amendment 0002.pdf

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 NUMBER

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

Section I - Contract Clauses

Additional Information/Notes

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

W51AA126RA0020002

(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 Framework assessing a contractor's compliance with applicable information security protections (see 32 CFR part 170).

(c) . The CMMC assessments will not duplicate efforts from any other Duplication comparable DoD assessment, except for rare circumstances 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: for all information systems used in CMMC Level 2 (Self) 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 https://piee.eb.mil of the contractor information systems that process, store, or transmit FCI 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)

Section L - Instructions, Conditions, & Notices to Offerors or Quoters

Miscellaneous text in this section has been modified to:

L.1.0 PROPOSAL SUBMISSION REQUIREMENTS

L.1.1 General Instructions: These instructions prescribe the format and describe the approach for the development and presentation of proposal data. They are designed to ensure the submission of necessary information for a comprehensive evaluation. Offerors must carefully review this section. To receive full consideration, the information furnished must be factual, accurate, and complete. Failure to furnish a complete proposal may result in the proposal being unacceptable and eliminated from consideration. All solicitation amendments must be acknowledged in accordance with FAR Provision 52.215- 1, Instructions to Offerors - Competitive Acquisition.

L.1.2 Submission Method and Deadline:

Electronic proposals must be submitted via email to Justin Marino and Brian Souter at justin.m.marino2.civ@army.mil and brian.j.souter.

civ@army.mil. No hardcopy proposals will be accepted.

The Government is not responsible for proposals that are delayed or not delivered due to technical issues. Offerors should plan ahead and begin transmission early to ensure successful delivery. The official time of receipt is the date/time stamp on the email notification sent by the offeror.

The entire proposal is due by the date and time specified for receipt of proposals in Block 13 of the SF 1442.

L.1.3 Proposal Validity: The Offeror shall indicate that their proposal remains valid for a minimum of 120 days and shall not contain classified data /information.

L.1.4 Point of Contact: The Contracting Officer (KO) and contract specialist are the sole points of contact for this acquisition. Technical personnel are not authorized to receive or discuss information regarding the solicitation.

Discussions of any kind with technical personnel prior to award is prohibited.

Address any questions or concerns you may have to the KO and contract specialist. Written requests for clarification may be sent to the KO and contract specialist at the addresses or email addresses located in paragraph (B)(1) above. Debriefings. The KO will promptly notify Offerors of any decision to exclude them from the competitive range (is the down select the competitive range), whereupon they may request and receive a debriefing in accordance

W51AA126RA0020002

mailto:justin.m.marino2.civ@army.mil with FAR 15.505. The KO will notify unsuccessful Offerors in accordance with FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

Discrepancies. If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror must immediately notify the KO and contract specialist in writing with supporting rationale.

L.1.5 Receipt of Submissions: For the purposes of establishing whether a proposal submission is considered timely, the Government will be following the regulations under FAR 15.208(b)(i). Do not assume that electronic communication is instantaneous. It can take several minutes or even hours in some cases. The electronic proposal submittal contents shall conform to the details of the solicitation and subsequent amendments. Each volume of the proposal shall be submitted electronically as detailed above.

L.2.0 PROPOSAL FILES AND FORMATTING

L.2.1 File Format and Naming:

Files shall be uploaded in PDF format unless otherwise instructed. The submission shall be clearly indexed and logically assembled.

Offerors shall include a "File Description" for each file uploaded.

The first page of the electronic proposal shall clearly identify the offeror's name, the RFP number, and the RFP title.

L.2.2 Page and Font Formatting:

Proposals shall be prepared on standard 8.5 x 11-inch pages. Charts and tables may be landscaped but must fit on an 8.5 x 11-inch page.

A standard, 12-point minimum font size applies for paragraphs. Arial or Times New Roman fonts are required.

Tables and illustrations may use a reduced font size, no less than 8-point.

Each paragraph should be single-spaced and separated by at least one blank line.

Margins shall be at least 1-inch on all sides.

L.2.3 Volume and Page Limits: The following volumes shall be submitted as separate files. Pages that exceed the required page limitations will be removed and not evaluated.

Vol um e

Title Digital Copies

Maximum Pages

I Technical 1 50

II Past Performance 1 15

III Solicitation, Offer and Award Documents, and Certifications / Representations

1 No page limit

L.2.4 Introductory Page: Provide a one-page introduction that includes your CAGE Code, Unique Entity Identification (UEI) Number, points of contact, authorized negotiators, contact phone numbers, and email addresses. Also, state your business socioeconomic status (e.g., small business, woman-owned small business, etc.). This page does not count toward the page limits.

L.3.0 PROPOSAL CONTENT REQUIREMENTS

All information shall be confined to the appropriate volume. Each volume shall consist of a Table of Contents, a Summary Section containing a brief abstract, and the Narrative discussion.

L.3.1 VOLUME I - TECHNICAL

The Technical volume shall be organized into the following sections:

L.3.1.1 Section 1 - Subfactor 1: Bonding Capacity Provide verification of a single project bonding threshold of at least $5,000,000 and an aggregate bonding threshold of at least $30,000,000.

This verification shall be a signed letter from your chosen surety.

The surety company must be listed on the U.S. Department of the Treasury's list of certified companies (Circular 570).

Provide contact information for the surety for verification purposes.

L.3.1.2 Section 2 - Subfactor 2: Safety Program Technical Approach to Safety: Provide a narrative describing how the company's education and training program aligns with OSHA Standards for each role within the organizational structure. Provide examples of required training, such as OSHA 10, OSHA 30, and Confined Spaces.

Submit TCR data for the five (5) Total Recordable Incident Rate (TCR):

previous complete calendar years: CY2021, CY2022, CY2023, CY2024, and CY2025. Do not provide an average. If no TCR data exists for any year, you must affirmatively state so and provide a detailed explanation.

For any year where the TCR is 2.5 or higher, provide a detailed and reasonable explanation that includes corrective actions taken.

Submit Days Away, Restricted, or Transferred (DART) Rate DART Rate:

data for the five (5) previous complete calendar years: CY2021, CY2022, CY2023, CY2024, and CY2025. Do not provide an average. If no DART Rate data exists for any year, you must affirmatively state so and provide a detailed explanation.<font style="font-size: 1rem;"> For any year where the DART Rate is above 1.0, provide a detailed and reasonable explanation that includes corrective actions taken.

L.3.1.3 Section 3 - Subfactor 3: Quality Control (QC) Quality Control Approach: Provide a description of the company's internal quality control structure and processes.

Duties, Responsibilities and Authorities of QC Personnel: Describe the duties, responsibilities, and authorities of QC personnel. Provide the procedures used for tracking construction deficiencies from identification through acceptable corrective action, including verification procedures.

L.3.2 VOLUME II - PAST PERFORMANCE

This volume shall contain information on three (3) recent and relevant contracts for the prime offeror under Federal, State, Local Government or commercial contracts for the same or similar services as compared to the NAICS 236220.

Recency is defined as a contract awarded and completed within the five (5) years prior to the issue date of this RFP.

Relevancy is defined as services performed as the prime contractor under NAICS code 236220 with a total contract value of $350,000 or greater.

This volume shall be organized into the following sections:

L.3.2.1 Section 1 - Contract Descriptions: For each of the three contracts, provide the following details:

Contractor/Subcontractor place of performance, CAGE Code, and UEI Number. If work was as a subcontractor, provide prime contractor details and POC.

Government contracting activity, address, and Procuring Contracting Officer contact information.

Government technical representative/COR contact information.

Government contract administration activity and Administrative Contracting Officer contact information.

Contract Number (and Delivery Order numbers if applicable).

Contract Type.

Awarded price/cost and final/projected final price/cost.

Original and final/projected delivery schedule (start and completion dates).

L.3.2.2 Section 2 - Performance Narrative:

Provide a specific narrative for each contract describing the objectives achieved and how the effort is relevant to this RFP's requirements.

If a contract did not meet its original schedule or technical requirements, explain the reasons and the corrective actions taken. Address all schedule revisions, Cure Notices, or Show Cause Letters.

Provide data on all manufacturing warranty returns, delineating the cause and nature of any failures.

L.3.2.3 Past Performance Questionnaire (PPQ):

For each of the three contracts, the offeror must send a PPQ to the client's POCs for completion.

The offeror shall complete Part I of the PPQ and email it to the technical representatives for that contract, instructing them to complete Part II and email the fully completed PPQ directly to justin.m.marino2.civ@army.mil and brian.j.souter.civ@army.mil by the proposal due date.

The offeror must also email a list of all POCs who were sent a questionnaire to the same email addresses by the proposal due date.

L.3.3 VOLUME III - SOLICITATION, OFFER AND AWARD DOCUMENTS AND

CERTIFICATIONS/REPRESENTATIONS

L.3.3.1 Section A - Standard Form 1442 (SF 1442): An authorized official of the firm must sign the SF 1442. All amendments must be acknowledged on the form.

L.3.3.2 Section K - Representations, Certifications, and Other Statements:

Ensure all fillable provisions are completed. If the offeror's representations and certifications in the System for Award Management (SAM) are current, only provisions not included in SAM need to be completed and submitted.

L.3.3.3 Joint Venture Requirements: Parties proposing as a joint venture must submit an executed copy of the joint venture agreement. The joint venture must be registered in SAM and meet applicable size standards. All questions regarding Joint Ventures should be directed to the Small Business Administration (SBA).

L.3.4 Use of Artificial Intelligence (AI) tools in Proposal Evaluation

L.3.4.1 Use of AI tools in Support of Evaluations: The Government may employ AI as a tool to assist in the analysis and review of offeror proposals. AI tools may be used to support tasks such as summarizing proposal content, identifying compliance with request for task order proposal / solicitation requirements, and highlighting areas of potential strength, weakness, or risk.

L.3.4.2 Maintaining Inherently Governmental Functions: Notwithstanding the use of AI tools to support the evaluation process, all final evaluation judgements, including the assignment or assessment of adjectival ratings, best value determinations, and source selection decisions, will be made exclusively by duly appointed Government personnel. The Government retains sole responsibility for all inherently governmental functions and will not delegate decision making authority to any AI tool.

L.3.4.3 Offeror Confidentiality and Data Protection: The AI tools utilized by the Government will be employed in a manner consistent with applicable regulations that govern the protection of proprietary and source selection sensitive information. The AI tool will be an output-only system. Any generated report data is not saved. No proposal data will be transmitted to or processed by external, non-Government systems without appropriate safeguards and authorizations in place.

The following clauses were modified:

252.204-7025Notice of Cybersecurity Maturity Model Certification Level Requirements.Nov 2025 hereby reads as follows:

NOTICE OF CYBERSECURITY MATURITY MODEL CERTIFICATION LEVEL

REQUIREMENTS (NOV 2025)

(a) . As used in this provision, "controlled unclassified information (CUI)," Definitions "current," "Cybersecurity Maturity Model Certification (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 Cybersecurity Maturity Model Certification (CMMC) level by this solicitation is: . This CMMC level, or higher (see 32 CFR part 170), CMMC Level 2 (Self) 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 by paragraph (b)(1) of this provision; https://piee.eb.mil and

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

(c) . If the Offeror has a CMMC Status of Conditional, the Plan of action and milestones Offeror shall successfully close out a valid plan of 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 CMMC unique identifiers identifier(s) (CMMC UIDs) issued by SPRS for 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)

TOBYHANNA ARMY DEPOT, 11 HAP ARNOLD BLVD

TOBYHANNA, PA 18466-0000

UNITED STATES

JUSTIN MARINO, EMAIL: JUSTIN.M.MARINO2.CIV@ARMY.MIL TELEPHONE: 5706157106

AdminBy:

SCD: PAS: