B08.03 W913T2Q0031- Amendment 0001.pdf

W81EWF51263624

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to clarify the extent of the requirements as detailed in Performance Work Statement (PWS) Section C, and extend the solicitation closing date.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 6

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

16C. DATE SIGNED

BY 06-Oct-2025

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street , County, State and Zip Code) X W9132T25Q0031

X 9B. DATED (SEE ITEM 11)

30-Jul-2025

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offer 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 telegram 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 telegram or letter, provided each telegram or letter 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 NO. AS DESCRIBED IN ITEM 14.

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

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, 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.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

06-Oct-2025

CODE

ERDC CONTRACTING OFFICE

CHAMPAIGN OFFICE

P O BOX 9005

CHAMPAIGN IL 61826-9005

W9132T 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W9132T25Q0031

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 15-Aug-2025 11:59 AM to 23-Oct-2025 11:59 AM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

Support to the Controls System Test Laboratory (CSTL)

1. INTRODUCTION: ERDC has several ongoing and upcoming research projects which have a need to evaluate

Facility Related Control Systems (FRCS) and their interaction with the growing number of installation microgrids in an operational laboratory environment.

Department of Defense (DoD) installations have a growing number of control systems. There is potential for the coordination or integration of these systems to greatly improve situational awareness and operational management. Many technologies claim to provide part or all of this capability. Testing these devices in a functional network architecture will highlight any compatibility issues and/or cybersecurity concerns with other existing devices and equipment. Testing this capability in an integrated environment is important because it would highlight issues prior to deployment.

ERDC-CERL recently stood up the Control System Test Lab (CSTL) to address the FRCS testing gap, but additional system components are needed to provide the full range of testing services required to meet new and emerging Army control system requirements and goals. In line with this, CERL is using the CSTL to perform testing to support a demonstration project evaluating Managed BACnet. The contract is for the installation and integration of components into the CSTL. Activities beyond those required to install and integrate components into the CSTL as indicated are not within the scope of this contract. Activities outside the scope of this contract include cybersecurity engineering/configuration, cybersecurity testing, and functional product testing. There are no cybersecurity requirements associated with this contract.

2. OBJECTIVE: Support the execution of a project by supporting the installation, configuration, and integration of new technologies into the CSTL for future use by ERDC-CERL.

3. MAJOR REQUIREMENTS: In order to accomplish the above objective, the Contractor must complete the following tasks:

a. Task 1. New Equipment Installation Support.

Provide support for the installation, configuration, and integration of new technologies into the Control System Test Lab by completing the following:

i. Participate in three (3) major install/integration sessions lasting one (1) week each, by serving as expert controls technicians in the CSLT for the installation and configuration of BACnet and BACnet SC technologies and integration of these technologies to the CSTL font-ends. The number of devices to be installed and integrated is estimated to be 24 and will not exceed 30.

ii. At the conclusion of each integration session, provide a brief written summary (maximum 5 pages) of the devices integrated, the front-end to which they are integrated, the network address(es) of the devices, and any issues encountered integrating those components.

b. Task 2. Configuration and Integration Troubleshooting Support.

Following the integration and configuration described in Task 1, ERDC CERL will begin using and reconfiguring as needed the new components and integrating additional components. Provide support for the reconfiguration and integration by completing the following:

i. Participate in eight (8) minor integration/troubleshooting sessions lasting up to four (4) hours each. Each session may be the integration of a single components or troubleshooting multiple components that are on a common front-end. The purpose of each session will be determined by the needs of the project at the time the sessions occur.

ii. At the conclusion of each session, provide a maximum one (1) page written summary detailing the objective of the session and the outcome.

4. GOVERNMENT-FURNISHED SUPPORT/INFORMATION/PROPERTY:

Access to the physical CSTL building must be coordinated with ERDC-CERL. All technologies to be installed and integrated, relevant documentation, and necessary software tools will be provided by ERDC-CERL.

5. CONTRACTING OFFICER’S REPRESENTATIVE (COR): The ERDC CERL COR for this contract will be appointed in accordance with DFARS 252.201-7000, and a copy of the designation letter will be provided to the Contractor. Although other Government personnel may clarify technical points or supply relevant information to the Contractor regarding this contract, only a Contracting Officer has the authority to revise any requirements in these specifications, including those resulting from verbal clarification. Only a warranted Contracting Officer (either a Procuring Contracting Officer (PCO), or an Administrative Contracting Officer (ACO)), acting within their delegated limits, has the authority to issue modifications or otherwise change the terms and conditions of this contract. If an individual other than the Contracting Officer attempts to make changes to the terms and conditions of this contract, you shall not proceed with the change and shall immediately notify the Contracting Officer.

6. NON-PERSONAL SERVICES: The Government and the Contractor understand and agree that the services to be delivered under this contract by the Contractor to the Government are non-personal services and the parties recognize and agree that no employer-employee or master-servant relationship exists or will exist under the contract between the Government and the Contractor’s employees.

7. MEETINGS AND REVIEWS: The contractor shall attend the following:

a. General:

1. Unless otherwise indicated, all meetings will be held on-site.

2. Any virtual meetings must be conducted via a web meeting platform which enables screen sharing. Contractor may choose whether to provide the web meeting platform or to use the CERL provided platform (Teams).

3. Unless specific dates and times are provided, meetings must be scheduled in coordination with CERL to ensure they occur at a time which allows participation by the relevant Government personnel.

b. Kick Off Meeting (Virtual, 1 hour): The contractor must participate in a one-hour technical virtual orientation meeting within two (2) weeks of award. This will be a meeting to discuss general technical requirements of contract; including technical requirements, deliverables schedule, and contractor clarifications. Within one (1) week of the kick-off meeting, the contractor must submit written minutes from the meeting to the COR in a Microsoft Word (.docx) or Adobe pdf format.

c. Task-Specific Meetings (On-Site): Meetings will be scheduled by CERL in coordination with the contractor and other meeting attendees.

1. (Task 1) Three one-hour session coordination meetings, one per installation and integration session required in Task 1. These meetings will cover the devices and systems being worked on and the work to be performed and will take place during the first hour of each Task 1 session as defined in 3. a.

a. Task 1 – Session 1 Coordination Meeting

b. Task 1 – Session 2 Coordination Meeting

c. Task 1 – Session 3 Coordination Meeting

2. (Task 2) Up to eight thirty-minute session coordination meetings, one per integration/testing/troubleshooting session required in Task 2. These meetings will cover the devices and systems being worked on, the issue to be addressed, and the work to be performed and will take place during the first thirty minutes of each Task 2 session as defined in 3. b.

a. Task 2 – Session 1 Coordination Meeting

b. Task 2 – Session 2 Coordination Meeting

c. Task 2 – Session 3 Coordination Meeting

d. Task 2 – Session 4 Coordination Meeting

e. Task 2 – Session 5 Coordination Meeting

f. Task 2 – Session 6 Coordination Meeting

g. Task 2 – Session 7 Coordination Meeting

h. Task 2 – Session 8 Coordination Meeting

8. TRAVEL REQUIREMENTS: Travel from contractor offices to ERDC-CERL for eleven (11) on-site sessions (including the coordination meeting at the beginning of each session).

9. SUMMARYS/DELIVERABLES: Submit the following reports/deliverables to the ERDC-CERL COR, or to the required reporting system specified, within the time specified:

a. Kick-Off Meeting Minutes (Summary): Within one (1) week of the kick-off meeting, submit written minutes from the meeting to the COR in a Microsoft Word (.docx) or Adobe pdf format.

b. Technical Deliverables: Deliverables must be provided as indicated, in the formats shown in parenthesis after the deliverable name.

Deliverables for Base Tasks (Tasks 1 & 2)

iii. (Task 1) Installation and Integration Session Summaries: provide a written summary (maximum 5 pages) for each installation and integration session of the devices integrated, the front-end to which they are integrated, the network address(es) of the devices, and any issues encountered integrating those components. No specific summary format is required.

a. Task 1 – Session Summary 1 (.pdf or .docx)

b. Task 1 – Session Summary 2 (.pdf or .docx)

c. Task 1 – Session Summary 3 (.pdf or .docx)

ii. (Task 2) Integration/Testing/Troubleshooting Summaries: provide a written summary (maximum 1 page) for each integration/troubleshooting session summarizing the objectives of their respective session and the outcome of that session.

a. Task 2 – Session Summary 1 (.pdf or .docx)

b. Task 2 – Session Summary 2 (.pdf or .docx)

c. Task 2 – Session Summary 3 (.pdf or .docx)

d. Task 2 – Session Summary 4 (.pdf or .docx)

e. Task 2 – Session Summary 5 (.pdf or .docx)

f. Task 2 – Session Summary 6 (.pdf or .docx)

g. Task 2 – Session Summary 7 (.pdf or .docx)

h. Task 2 – Session Summary 8 (.pdf or .docx)

10. SCHEDULE: Approximated timeframes for the required sessions are shown in the table below. Session dates can be adjusted according to the associated project schedule and government and contractor availability.

Summary due dates will shift accordingly.

TASK 1 – Installation and Integration Sessions Task 1 – Session 1 January 2026 Task 1 – Session 1 Coordination Meeting conducted at the start of Session 1 Task 1 – Session Summary 1 due 4 weeks after Session 1 Task 1 – Session 2 February 2026 Task 1 – Session 2 Coordination Meeting conducted at the start of Session 2

Task 1 – Session Summary 2 due 4 weeks after Session 2 Task 1 – Session 3 March 2026 Task 1 – Session 3 Coordination Meeting conducted at the start of Session 3 Task 1 – Session Summary 3 due 4 weeks after Session 3

TASK 2 - Integration/Troubleshooting Sessions Task 2 – Session 1-8 approx. monthly from April-December 2026 Task 2 – Session 1-8 Coordination Meeting conducted at the start of respective Session Task 2 – Session Summary 1-8 due 2 weeks after respective Session

11. ANTI-TERRORISM/OPERATIONAL SECURITY

General security requirements and guidance: The security requirements described below apply to all contract personnel (including employees of the prime Contractor (“Contractor”) and all subcontractor employees) supporting the performance requirements of this contract. The Contractor is responsible for compliance with these security requirements. Questions regarding security matters shall be addressed to the designated Government representative (e.g., Contracting Officer Representative (COR), Requiring Activity (RA) representative, or Contracting Officer (if a COR or other RA representative is not appointed)). Contract personnel are critical to the overall security and safety of US Army Corps of Engineers (USACE) installations, facilities and activities, and security awareness training contributes to those efforts. The Department of Defense (DoD) and Army security training requirements specified below, if applicable, are performance requirements;

all applicable contract personnel shall complete initial training within 30 days of contract award or the date new contract personnel begin performance on the contract. Within five business days from the completion of training, the Contractor shall provide written documentation (e.g., email or memorandum) to the Government representative. The documentation shall include the names of contract personnel trained and which training they completed; the Contractor shall maintain training records as part of their contract files and be prepared to provide copies of training certificates to the Government representative. Contractor personnel and vehicles are subject to search when entering federal installations. Additionally, all contract personnel shall comply with Force Protection Condition (FPCON) measures, Random Antiterrorism Measures (commonly referred to as “RAMs”), and Health Protection Condition (HPCON) measures. The Contractor is responsible for meeting performance requirements during elevated FPCON and/or HPCON levels in accordance with applicable RA plans and procedures --this includes identifying mission essential and non-mission essential personnel. In addition to the changes otherwise authorized by the changes clause of this contract, should the FPCON or HPCON levels at any individual facility or installation change, the Government may implement security changes that affect contract personnel. The Contractor shall ensure all contract personnel are aware of their security responsibilities, including any site-specific requirements identified in local policies or procedures.

Physical security and access control requirements: All contract personnel requiring physical access to a federal installation or facility shall comply with the access control procedures of that location. Contract personnel requiring unescorted access to meet contract performance requirements on a DoD installation in the US shall be vetted by the installation/facility Provost Marshal/Directorate of Emergency Services/Security Office using the National Crime Information Center-Interstate Identification Index (commonly referred to as “NCIC-III”) and Terrorist Screening Database (commonly referred to as “TSDB”). Contract personnel shall comply with all personal identity verification requirements specified in installation/facility policies and procedures. Contract personnel who do not meet requirements for unescorted access to USACE facilities shall coordinate escorted access with the Government representative, as needed. Contract personnel who receive keys, access cards, or lock combinations that provide access to government-owned property shall comply with key and lock control procedures of the RA.

Pre-screen candidates using E-Verify Program: Contractors shall comply with the requirements set forth in FAR clause 52.222-54 Employment Eligibility Verification and FAR Subpart 22.18 in using the E-Verify Program at (https://www.e-verify.gov/) (website subject to change) to meet the contract employment eligibility requirements. Contractors are encouraged to cooperate with Federal and State agencies responsible for enforcing labor requirements to include eligibility for employment under United States immigration laws in accordance with FAR 22.102-1(i). An initial list of verified/eligible candidates shall be provided to the COR no later than three business days after the initial contract award. When contracts are with individuals, the individuals will be required to complete a Form I-9, Employment Eligibility Verification, and submit it to the Contracting Officer to become part of the official contract file.

12. PERIOD OF SERVICE: The period of performance for this contract will begin on the date of award and end 410 calendar days after award.

Performance Requirement Summary

(End of Summary of Changes)

Deliverable or Other item surveilled

Reference Number

Standards Maximum Allowable Degree of Deviation

Method of Surveillance

Remedy for Non- Conformance

Kick-Off Meeting Minutes (Summary)

PWS para 9.a

- Submitted by the required deadline

0% Review by

COR

Re-performance

Technical Deliverables

PWS para 9.b

- Submitted by the required deadline

- Summary contains the information required by the PWS (devices integrated, systems integrated to, and any issues encountered integrating those components)

0% Review by

COR

Re-performance