Amendment 0003.pdf

PDF 4 MB Posted

Attached to
ELECTRICAL SWITCHING STATION NORTH, WATERVLIET ARSENAL, NEW YORK
Solicitation number
W912DS26RA015
Issued by

About this file

This is Amendment 0003 to the solicitation for the Watervliet Arsenal Electrical Switching Station North project (W912DS26RA015), issued by the U.S. Army Corps of Engineers, W2SD Endist New York, with an effective date of 18 May 2026. The proposal submission deadline remains 03 June 2026 at 2:00 P.M. EST.

The amendment incorporates three primary changes: addition of a Site Visit Sign-In Sheet and Site Visit Photos as required documentation; incorporation of DFARS Clause 252.204-7012 regarding Safeguarding Covered Defense Information and Cyber Incident Reporting; and incorporation of FAR Clause 52.222-90 addressing DEI Discrimination by Federal Contractors. CMMC Level 2 certification is not required for this contract. Bidders must acknowledge receipt of this amendment by the bid deadline through one of three methods: completing items 8 and 15 on the SF 1442, submitting a separate letter or electronic communication, or signing block 15. References to Niagara Framework hardware and JCI Metasys systems in the specifications and drawings are being removed, allowing bidders flexibility in selecting compliant building management systems. The amendment also addresses eleven bidder inquiries regarding CPARS submission, Key Personnel requirements, past performance documentation, volume submission format, small business utilization, and technical specifications. All terms and conditions of the original solicitation remain unchanged except as specifically modified by this amendment.

View the file

Other files

File Type Posted
Amendment 0016.pdf PDF
Amendment 0015.pdf PDF
Amendment 0015_23 09 00 and 23 09 23.02.pdf PDF
Amendment 0015_JA for Johnson Controls Inc Metasys.pdf PDF
Amendment 0015_Submittal REGISTER.pdf PDF
Amendment 0014.pdf PDF
Amendment 0013.pdf PDF
Amendment 0012.pdf PDF
Amendment 0011.pdf PDF
Amendment 0011_RFI Photos.pdf PDF
Amendment 0011_33 57 55.pdf PDF
Amendment 0010.pdf PDF
Amendment 0010_Pictures_Switches Nameplates.pdf PDF
Amendment 0009.pdf PDF
Amendment 0009_Photos.pdf PDF
Amendment 0008.pdf PDF
Amendment 0007.pdf PDF
Amendment 0007_Pictures.pdf PDF
Amendment 0007_Site Visit Photos Compressed.pdf PDF
Amendment 0006.pdf PDF
Amendment 0005.pdf PDF
Amendment 0004_01 14 00.pdf PDF
Amendment 0004.pdf PDF
Amendment 0004_C-001.pdf PDF
Amendment 0003_ Site Visit Photos.pdf PDF
Amendment 0003_Site Visit Sign In Sheet_06MAY2026.pdf PDF
Amendment 0002_G-101.pdf PDF
Amendment 0002.pdf PDF
Amendment 0002_01 14 00.pdf PDF
Amendment 0002_01 50 00.pdf PDF
Amendment 0001_JA - ESS North - North - Square D.pdf PDF
Amendment 0001.pdf PDF
Amendment 0001_ JA - ESS North - Fire Alarm.pdf PDF
Amendment 0001_ Spec 33 57 55.pdf PDF
Amendment 0001_ JA - ESS North - CAC-IDS.pdf PDF
Amendment 0001_ Dwg MS101.pdf PDF
Evaluation Factors.pdf PDF
Drawings.pdf PDF
Solicitation - W912DS26RA015.pdf PDF
Specifications.pdf PDF
Show all 40

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

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

The purpose of this Amendment 0003:Block 14 (Description of Amendment/Modification):

1) Proposals due date remains 03 June 2026 @ 2: 00 P.M. EST

2) Incorporate Site Visit Sign-In Sheet & Site Visit Photos.

3) Incorporate Clause 252.204-7012.

4) Incorporate Clause 52.222-90

5) Respond to Bidder Request for information. For information Only.

NOTE: Bidders must acknowledge receipt of this amendment by date specified in the bid (or as amended) by one of the following methods: In the space provided on the SF 1442, by separate letter, or by signing block 15 below. FAILURE TO ACKNOWLEDGE AMENDMENT BY DATE

SPECIFIED MAY RESULT IN REJECTION OF YOUR BID IN ACCORDANCE WITH THELATE

BID, LATE MODIFICATION OF BID, OR LATE WITHDRAWAL OF BID (FAR 14.304)

Section 01 00 00 - General Requirements

Miscellaneous text in this section has been modified to:

Watervliet Arsenal

Electrical Switching Station North

W912DS26RA015

Amendment 0003

AMENDMENT 0003 to DRAWINGS and SPECIFICATIONS for Watervliet Arsenal Electrical Switching Station North.

TO OFFERORS

The following changes shall be made to the drawings and specifications.

DRAWINGS

1. The following DRAWINGS have been REVISED but NOT REISSUED:

W912DS26RA0150003

- None

2. The following DRAWINGS have been REVISED and REISSUED:

- None

3. The following DRAWINGS have been ADDED:

- None

4. The following DRAWINGS have been DELETED:

- None

SPECIFICATIONS

1. The following SPECIFICATION SECTIONS have been ADDED and are provided in their entirety herein:

- None

2. The following SPECIFICATIONS SECTIONS have been DELETED in their entirety:

- None

3. The following SPECIFICATIONS SECTIONS have been REVISED and REISSUED:

- None

4. The following SPECIFICATIONS have been REVISED but NOT REISSUED:

- None

PROPOSER'S QUESTIONS AND GOVERNMENT REPLY

Questions that may be of general interest to all Offerors and/or the Government and that are not readily answered by the proceeding changes will appear below. These questions may have been paraphrased or altered to represent several questions regarding the same subject and/or simply revised to clarify and simplify the question(s). Questions and answers are issued to the Offerors "for information only" and do not revise the solicitation, plans or specifications.

BIDDER INQUIRY 04: Is CMMC Level 2 certification required for this project, and if it is when does the selected winner need to have this in place?

RESPONSE: No, CMMC Level 2 Certification is not required for this contract. Please refer to

DFARS 252.204-7012.

BIDDER INQUIRY 05: When CPARS are available, please confirm that CPARS can be included in the proposal in lieu of PPQs.

RESPONSE: Yes.

BIDDER INQUIRY 06: Where in the proposal should CPARS/PPQs be provided?

RESPONSE: Under Factor 1- Past Performance.

BIDDER INQUIRY 07: Attachment 5, Key Personnel Resume is included with the solicitation packet but is not referenced within the proposal requirements. Are there Key Personnel requirements that need to be responded to in the offeror's proposal? If so, what are the Key Personnel requirements? Where should the offeror provide their response to the Key Personnel requirements within their proposal, and will the page limitations be increased to allow for these additional requirements?

RESPONSE: Disregard Attachment 5 "Key Personnel".

BIDDER INQUIRY 08: For Section 5.1.2, Relevant Past Performance, will the government recognize relevant past performance of sister companies (subsidiaries with the same parent company who operate under a shared executive leadership structure and common business systems and established standard operating procedures) where the offeror demonstrates, in a document signed by authorized representatives of both the offeror and the sister company, that the sister company will have meaningful participation in contract performance?

RESPONSE: No, Please refer to 5.1.2, "If the firm has multiple divisions, limit the project examples to those performed by the division submitting the offer."

BIDDER INQUIRY 09: Should Volumes 1-3 be submitted as three separate PDFs?

RESPONSE: Submit three separate volumes.

BIDDER INQUIRY 10: (1)If the prime offeror is an SBA-certified small business, is the offeror still required to respond to Volume 2, Factor 4, Tab B regarding past utilization of small business concerns? (2) Additionally, does the response requirement change if one of the companies providing past performance examples in Volume 1 is an unrestricted business?

RESPONSE: (1) Offeror is still required to respond. (2) Response requirement does not change.

BIDDER INQUIRY 11: Spec sections 23 09 00 and 23 09 23.02 of the WVA Switching Station project spec. They state to use Niagara Framework hardware and software for scheduling, trending, and communication with a front end. Meanwhile, dwg M701 calls for installation of JCI Metasys system in the building. However, JCI Metasys is not mentioned in specs 230900, 230913, 230923.02, or 251010. Is a Niagara based system with Honeywell controllers acceptable for installation at the system facility in lieu of JCI?

RESPONSE: References to Niagara and JCI Metasys on the Drawings and in the Specs will be removed. Disregard these references, thank you.

-END-

252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting.

As prescribed in 204.7304 (c), use the following clause:

SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT REPORTING

(MAY 2024)

(a) Definitions. As used in this clause--

"Adequate security" means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

"Compromise" means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

"Contractor attributional/proprietary information" means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

"Controlled technical information" means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

"Covered contractor information system" means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

"Covered defense information" means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.

archives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is--

(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or

(2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract.

"Cyber incident" means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

"Forensic analysis" means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.

"Information system" means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

"Malicious software" means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

"Media" means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system.

''Operationally critical support'' means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

"Rapidly report" means within 72 hours of discovery of any cyber incident.

"Technical information" means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013 , Rights in Technical Data--Other Than Commercial Products and Commercial Services, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security on all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:

(1) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government, the following security requirements apply:

(i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010 , Cloud Computing Services, of this contract.

(ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.

(2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply:

(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, "Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations" (available via the internet at https://csrc.nist.gov/publications/sp800) in effect at the time the solicitation is issued or as authorized by the Contracting Officer.

(ii)(A) The Contractor shall implement NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.

(C) If the DoD CIO has previously adjudicated the contractor's requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.

(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/documents-templates/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.

(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, the Contractor shall--

(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor's network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor's ability to provide operationally critical support; and

(ii) Rapidly report cyber incidents to DoD at https://dibnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at https://dibnet.dod.mil.

(3) Medium assurance certificate requirement.In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see https://public.cyber.mil/eca/.

(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer.

Do not send the malicious software to the Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis.Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional /proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD.

Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD--

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or

(5) To a support services contractor ("recipient") that is directly supporting Government activities under a contract that includes the clause at 252.204-7009 , Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.

(j) Use and release of contractor attributional/proprietary information created by or for DoD.

Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall--

(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial products or commercial services, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and

(2) Require subcontractors to--

(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and

(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

(End of clause)

2.222-90 Addressing DEI Discrimination by Federal Contractors.

As prescribed in 22.2203, insert the following clause:

Addressing DEI Discrimination by Federal Contractors (Deviation DATE)

(a) Definitions. As used in this clause--

Program participation means membership or participation in, or access or admission to: training, mentoring, or leadership development programs; educational opportunities; clubs; associations; or similar opportunities that are sponsored or established by the contractor or subcontractor.

Racially discriminatory diversity, equity, and inclusion (DEI) activities means disparate treatment based on race or ethnicity in the recruitment, employment (e.g., hiring, promotions), contracting ( , vendor agreements), e.g.

program participation, or allocation or deployment of an entity's resources.

(b) In connection with the performance of work under this contract, the Contractor agrees as follows:

(1) The Contractor will not engage in any racially discriminatory DEI activities;

(2) The Contractor will furnish all information and reports, including providing access to books, records, and accounts, as required by the Contracting Officer, for purposes of ascertaining compliance with this clause;

(3) In the event of the Contractor's or a subcontractor's noncompliance with this clause, this contract may be canceled, terminated, or suspended in whole or in part, and the Contractor or subcontractor may be declared ineligible for further Government contracts;

(4) The Contractor will report any subcontractor's known or reasonably knowable conduct that may violate this clause to the Contracting Officer and take any appropriate remedial actions directed by the Contracting Officer;

and

(5) The Contractor will inform the Contracting Officer if a subcontractor sues the Contractor and the suit puts at issue, in any way, the validity of this clause.

(6) The Contractor recognizes that compliance with the requirements of this clause are material to the Government's payment decisions for purposes of 31 U.S.C. 3729(b)(4).

(c) The Contractor must include the substance of this clause, including this paragraph (c), in subcontracts at any tier, including those for commercial products and commercial services, except those where the place of delivery or performance is outside the United States.

(End of clause)

IDCode: J
Page: 1
Pages: 11
AmendNo: 0003
EffDate: 18 MAY 2026
ReqNo:
ProjNo: 26-9
IssCode: W912DS
AdmCode:
IssuedBy: W2SD ENDIST NEW YORK

KO CONTRACTING DIVISION, 26 FEDERAL PLAZA ROOM 16 300

NEW YORK, NY 10278-0004

UNITED STATES

ORLANDO NIEVES, EMAIL: ORLANDO.NIEVES@USACE.ARMY.MIL TELEPHONE: (917) 790-8078

AdminBy:

SCD: PAS:

ContractorNameAdd:
Code:
FacCode:
SolChg: 1
SolNo: W912DS26RA015
SolDate: 17 APR 2026
AwardChg: Off
AwardNo:
AwardDate:
Amended: 1
OffrExt: Off
OffrNoEx: 1
NoCopies: 1
ApprData: SEE SECTION G - CONTRACT ADMINISTRATION DATA
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 .