Solicitation - FA461326Q0019.pdf

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30. 1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NUMBER 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER 5. SOLICITATION NUMBER

FA461326Q0019

6. SOLICITATION ISSUE DATE

31 Aug 2026

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

KYLE HARRIS

b. TELEPHONE NUMBER (no collect calls) 3077732181

8. OFFER DUE DATE/

LOCAL TIME

10 Sep 2026

11:00 AM

9. ISSUED BY CODE: FA4613

FA4613 90 CONS PK

CP 307 773 3888, 7505 BARNES LOOP BLDG 208

FE WARREN AFB, WY 82005-2860

UNITED STATES

KYLE HARRIS, Email: kyle.harris.23@us.af.mil Telephone: 3077732181 Liezel McIntyre, Email: liezel.mcintyre@us.af.mil Telephone: (307) 773-3411

10. THIS ACQUISITION IS UNRESTRICTED OR SET ASIDE: % FOR: 100

SMALL BUSINESS WOMEN-OWNED SMALL

BUSINESS (WOSB)

NORTH AMERICAN

INDUSTRY

CLASSIFICATION

STANDARD (NAICS):

314910

HUBZONE SMALL

BUSINESS

ECONOMICALLY

DISADVANTAGED WOMEN-

OWNED SMALL BUSINESS

(EDWOSB)

SIZE STANDARD:

SERVICE-DISABLED

VETERAN-OWNED SMALL

BUSINESS (SDVOSB)

8(A)

11. DELIVERY FOR FREE ON

BOARD (FOB) DESTINATION

UNLESS BLOCK IS MARKED

SEE SCHEDULE

12. DISCOUNT TERMS 13a.THIS CONTRACT IS A

RATED ORDER UNDER

THE DEFENSE PRIORITIES

AND ALLOCATIONS

SYSTEM-DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

REQUEST FOR

QUOTE (RFQ)

INVITATION

FOR BID (IFB)

REQUEST FOR

PROPOSAL (RFP)

15. DELIVER TO CODE:

See Schedule

16. ADMINISTERED BY CODE:

17a. CONTRACTOR/

OFFERER

CODE FACILITY

CODE:

TELEPHONE NUMBER

18a. PAYMENT WILL BE MADE BY CODE:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED SEE ADDENDUM

19.

ITEM NUMBER

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT

PRICE

24.

AMOUNT

See Schedule (Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA

See Section G - Contract Administration Data

26. TOTAL AWARD AMOUNT (For Government Use Only)

27a. SOLICITATION INCORPORATES BY REFERENCE (FEDERAL ACQUISITION REGULATION) FAR 52.212-1, 52.212-4. FAR

52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

ARE ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN COPIES TO

ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DELIVER ALL ITEMS SET FORTH

OR OTHERWISE IDENTIFIED ABOVE AND ON ANY ADDITIONAL SHEETS SUBJECT TO THE

TERMS AND CONDITIONS SPECIFIED

29. AWARD OF CONTRACT: REFERENCE OFFER DATED . YOUR

OFFER ON SOLICITATION (BLOCK 5), INCLUDING ANY ADDITIONS OR

CHANGES WHICH ARE SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS: See Schedule

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (Type or print)

31c. DATE SIGNED

COMPUTER GENERATED STANDARD FORM 1449 (REV. 11/2021)

PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212

Solicitation/Contract Form PKAB Emergency Beddown and Readiness Training Equipment (Commodity)

Emergency Beddown and Readiness Training Equipment.

Product Service Code: 8340

FA461326Q0019

Supplies or Services & Prices or Costs Additional Information/Notes

Item Supplies / Services Quantity Unit Unit Price Amount

Shelter System / Deployable Tents

Product Service Code: 8340 Item UID Required: Yes Program Code: A90 Pricing Arrangement: Firm Fixed Price

10 Each

Power Distribution

Product Service Code: 8340 Item UID Required: Yes Program Code: A90 Pricing Arrangement: Firm Fixed Price

10 Each

Light Assembly Kits

Product Service Code: 8340 Item UID Required: Yes Program Code: A90 Pricing Arrangement: Firm Fixed Price

10 Each

Skid Mounted Diesel Generator

Product Service Code: 8340 Item UID Required: Yes Program Code: A90 Pricing Arrangement: Firm Fixed Price

2 Each

Shipping and Onsite Training Installation/Operation for 1 Fully Operational Shelter System

Product Service Code: 8340 Program Code: A90 Pricing Arrangement: Firm Fixed Price

1 Each

Description/Specifications/Statement of Work

Requirements This requirement is for the purchase of Prime BEEF Readiness Equipment for 90 CES.

Packaging and Marking

Inspection and Acceptance Overall Contract Inspection/Acceptance Locations

Inspection and Acceptance Location

Both Destination Instructions: See Contract Terms and Conditions for Inspection and Acceptance criteria.

DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

MSgt Charles Wheeler Email: charles.wheeler.18@us.af.mil Telephone: 3077734350

Destination Instructions: See Contract Terms and Conditions for Inspection and Acceptance criteria.

DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

MSgt Charles Wheeler Email: charles.wheeler.18@us.af.mil

Destination Instructions: See Contract Terms and Conditions for Inspection and Acceptance criteria.

DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

MSgt Charles Wheeler Email: charles.wheeler.18@us.af.mil

Destination Instructions: See Contract Terms and Conditions for Inspection and Acceptance criteria.

DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

MSgt Charles Wheeler

Email: charles.wheeler.18@us.af.mil

Destination Instructions: See Contract Terms and Conditions for Inspection and Acceptance criteria.

DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

MSgt Charles Wheeler Email: charles.wheeler.18@us.af.mil Telephone: 3077734350

Deliveries or Performance

Line Item Delivery Schedule Quantity Address and POC Special Handling/Notes

Delivery Schedule From date of lead time event to delivery 150 Calendar Days Date of Award Receipt

10 Each Place of Performance DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

FoB Details Contractor Destination

Delivery Schedule From date of lead time event to delivery 150 Calendar Days Date of Award Receipt

10 Each Place of Performance DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

FoB Details Contractor Destination

Delivery Schedule From date of lead time event to delivery 150 Calendar Days Date of Award Receipt

10 Each Place of Performance DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

FoB Details Contractor Destination

Delivery Schedule From date of lead time event to delivery 150 Calendar Days Date of Award Receipt

2 Each Place of Performance DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

FoB Details Contractor Destination

Delivery Schedule From date of lead time event to delivery 150 Calendar Days Date of Award Receipt

1 Each Place of Performance DoDAAC: F1Y3DA CountryCode: USA

90 CES

AF BPN NO MILSBILLS PROCESSES, 300 VESLE DR

FE WARREN AFB, WY 82005-2782

UNITED STATES

FoB Details Contractor Destination

Contract Administration Data

DFARS Clauses Incorporated by Reference

Number Title Effective Date Alternate/ Deviation

Variation Effective Date

252.232-7003 Electronic Submission of Payment Requests and Receiving Reports. Dec 2018

DFARS Clauses Incorporated by Full Text

252.232-7006 Wide Area WorkFlow Payment Instructions. (Jan 2023)

WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)

(a) As used in this clause- Definitions.

"Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization.

"Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

"Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system.

"Payment request" and "receiving report" are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(b) The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Electronic invoicing.

Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) To access WAWF, the Contractor shall- WAWF access.

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

(d) The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before WAWF training.

submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the WAWF home page at https://wawf.eb.mil/

(e) Document submissions may be via web entry, Electronic Data Interchange, or File Transfer Protocol. WAWF methods of document submission.

(f) The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF for this contract WAWF payment instructions.

or task or delivery order:

(1) The Contractor shall submit payment requests using the following document type(s): Document type.

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items-

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.

(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.

(Contracting Officer: Insert either "Invoice 2in1" or the applicable invoice and receiving report document type(s) for fixed price line items for services.)

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial financing, submit a commercial financing request.

(2) ) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF "combo" document type to create some combinations of invoice and receiving report in one step.]

(3) The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment Document routing.

requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF

Pay Official DoDAAC F87700

Issue By DoDAAC FA4613

Admin DoDAAC FA4613

Inspect By DoDAAC F1Y3DA

Ship To Code F1Y3DA

Ship From Code N/A

Mark For Code N/A

Service Approver (DoDAAC) N/A

Service Acceptor (DoDAAC) FA4613

Accept at Other DoDAAC N/A

LPO DoDAAC N/A

DCAA Auditor DoDAAC N/A

Other DoDAAC(s) N/A

(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert "See Schedule" or "Not applicable.")

(**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

(4) The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the Payment request.

payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F. Receiving report.

(g) WAWF point of contact.

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

kyle.harris.23@us.af.mil;liezel.mcintyre@us.af.mil

(Contracting Officer: Insert applicable information or "Not applicable.")

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

(End of clause)

Special Contract Requirements

Contract Clauses 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)

252.211-7003 Item Unique Identification and Valuation.

As prescribed in 211.274-5 (a), use the following clause:

ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023)

(a) Definitions. As used in this clause-- "Automatic identification device" means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

"Concatenated unique item identifier" means--

(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or

(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code;

enterprise identifier; original part, lot, or batch number; and serial number within the original part, lot, or batch number.

"Data matrix" means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200 (ECC200) specification found within International Standards Organization (ISO)/International Electrotechnical Commission

(IEC) 16022.

"Data qualifier" means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.

"DoD recognized unique identification equivalent" means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html .

"DoD item unique identification" means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, o batch number; and the serial number.

"Enterprise" means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items.

"Enterprise identifier" means a code that is uniquely assigned to an enterprise by an issuing agency.

"Government's unit acquisition cost" means--

(1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery;

(2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery; and

(3) For items produced under a time-and-materials contract, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery.

"Issuing agency" means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/ IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459.

"Issuing agency code" means a code that designates the registration (or controlling) authority for the enterprise identifier.

"Item" means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts.

"Lot or batch number" means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions.

"Machine-readable" means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards.

"Original part number" means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface.

"Parent item" means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent.

"Serial number within the enterprise identifier" means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise.

"Serial number within the part, lot, or batch number" means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment.

"Serialization within the enterprise identifier" means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier.

"Serialization within the part, lot, or batch number" means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier.

"Type designation" means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and chaes thereto.

"Unique item identifier" means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent.

"Unique item identifier type" means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html .

(b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item.

(c) Unique item identifier.

(1) The Contractor shall provide a unique item identifier for the following:

(i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items:

Contract Line, Subline, or Exhibit Line Item Number Item Description

(ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table:

Contract Line, Subline, or Exhibit Line Item Number Item Description

(If items are identified in the Schedule, insert "See Schedule" in this table.)

(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number ____.

(iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number ____.

(v) Any item not included in (i), (ii), (iii), or (iv) for which the contractor creates and marks a unique item identifier for traceability.

(2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor.

(3) The unique item identifier component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology - International symbology specification - Data matrix; ECC200 data matrix specification.

(4) Data syntax and semantics of unique item identifiers. The Contractor shall ensure that--

(i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the Contractor:

(A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology - EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology

- EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and

(ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology - Transfer Syntax for High Capacity Automatic Data Capture Media.

(5) Unique item identifier.

(i) The Contractor shall--

(A) Determine whether to--

(1) Serialize within the enterprise identifier;

(2) Serialize within the part, lot, or batch number; or

(3) Use a DoD recognized unique identification equivalent (e.g. Vehicle Identification Number); and

(B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in MIL- STD-130, Identification Marking of U.S. Military Property, latest version;

(C) Label shipments, storage containers and packages that contain uniquely identified items in accordance with the requirements of MIL-STD-129, Military Marking for Shipment and Storage, latest version; and

(D) Verify that the marks on items and labels on shipments, storage containers, and packages are machine readable and conform to the applicable standards. The contractor shall use an automatic identification technology device for this verification that has been programmed to the requirements of Appendix A, MIL-STD-130, latest version.

(ii) The issuing agency code--

(A) Shall not be placed on the item; and

(B) Shall be derived from the data qualifier for the enterprise identifier.

(d) For each item that requires item unique identification under paragraph (c)(1)(i), (ii), or (iv) of this clause or when item unique identification is provided under paragraph

(c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, as part of the Material Inspection and Receiving Report, the following information:

(1) Unique item identifier.

(2) Unique item identifier type.

(3) Issuing agency code (if concatenated unique item identifier is used).

(4) Enterprise identifier (if concatenated unique item identifier is used).

(5) Original part number (if there is serialization within the original part number).

(6) Lot or batch number (if there is serialization within the lot or batch number).

(7) Current part number (optional and only if not the same as the original part number).

(8) Current part number effective date (optional and only if current part number is used).

(9) Serial number (if concatenated unique item identifier is used).

(10) Government's unit acquisition cost.

(11) Unit of measure.

(12) Type designation of the item as specified in the contract schedule, if any.

(13) Whether the item is an item of Special Tooling or Special Test Equipment.

(14) Whether the item is covered by a warranty.

(e) For embedded subassemblies, components, and parts that require DoD item unique identification under paragraph (c)(1)(iii) of this clause or when item unique identification is provided under paragraph (c)(1)(v), the Contractor shall report as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the following information:

(1) Unique item identifier of the parent item under paragraph (c)(1) of this clause that contains the embedded subassembly, component, or part.

(2) Unique item identifier of the embedded subassembly, component, or part.

(3) Unique item identifier type.**

(4) Issuing agency code (if concatenated unique item identifier is used).**

(5) Enterprise identifier (if concatenated unique item identifier is used).**

(6) Original part number (if there is serialization within the original part number).**

(7) Lot or batch number (if there is serialization within the lot or batch number).**

(8) Current part number (optional and only if not the same as the original part number).**

(9) Current part number effective date (optional and only if current part number is used).**

(10) Serial number (if concatenated unique item identifier is used).**

(11) Description.

** Once per item.

(f) The Contractor shall submit the information required by paragraphs (d) and (e) of this clause as follows:

(1) End items shall be reported using the receiving report capability in Wide Area WorkFlow (WAWF) in accordance with the clause at 252.232-7003. If WAWF is not required by this contract, and the contractor is not using WAWF, follow the procedures at http://dodprocurementtoolbox.com/site/uidregistry/.

(2) Embedded items shall be reported by one of the following methods--

(i) Use of the embedded items capability in WAWF;

(ii) Direct data submission to the IUID Registry following the procedures and formats at http://dodprocurementtoolbox.com/site/uidregistry/; or

(iii) Via WAWF as a deliverable attachment for exhibit line item number (fill in) ___, Unique Item Identifier Report for Embedded Items, Contract Data Requirements List, DD Form 1423.

(g) Subcontracts. If the Contractor acquires by subcontract any item(s) for which item unique identification is required in accordance with paragraph (c)(1) of this clause, the Contractor shall include this clause, including this paragraph (g), in the applicable subcontract(s), including subcontracts for commercial products or commercial services.

(End of clause)

FAR Clauses Incorporated by Reference

Number Title Effective Date Alternate/ Deviation

Variation Effective Date

52.203-3 Gratuities. Apr 1984 52.203-6 Restrictions on Subcontractor Sales to the Government. Jun 2020 52.203-6 Restrictions on Subcontractor Sales to the Government. (Alternate I) Jun 2020 Alternate I Nov 2021 52.203-19 Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements. Jan 2017 52.204-13 System for Award Management-Maintenance. (Deviation 2026-O0038) Feb 2026 52.209-6 Protecting the Government's Interest When Subcontracting With Contractors Debarred, Suspended, Proposed for Debarment, or Voluntarily Excluded. (Deviation 2026-O0038) Feb 2026

52.209-10 Prohibition on Contracting With Inverted Domestic Corporations. (Deviation 2026-O0038) Feb 2026 52.212-4 Terms and Conditions-Commercial Products and Commercial Services. (Deviation 2026-O0038) Feb 2026 52.219-6 Notice of Total Small Business Set-Aside. (Deviation 2026-O0038) Feb 2026 52.219-8 Utilization of Small Business Concerns. (Deviation 2026-O0038) Feb 2026 52.219-33 Nonmanufacturer Rule. (Deviation 2026-O0038) Feb 2026 52.222-3 Convict Labor. (Deviation 2026-O0038) Feb 2026 52.222-19 Child Labor-Cooperation with Authorities and Remedies. (Deviation 2026-O0038) Mar 2026 52.222-35 Equal Opportunity for Veterans. (Deviation 2026-O0038) Feb 2026 52.222-36 Equal Opportunity for Workers with Disabilities. (Deviation 2026-O0038) Feb 2026

52.222-37 Employment Reports on Veterans. (Deviation 2026-O0038) Feb 2026 52.222-40 Notification of Employee Rights Under the National Labor Relations Act. (Deviation 2026-O0038) Feb 2026 52.222-50 Combating Trafficking in Persons. (Deviation 2026-O0038) Feb 2026 52.222-90 Addressing DEI Discrimination by Federal Contractors. (Deviation 2026-O0040, Revision 1) Apr 2026 52.223-23 Sustainable Products. (Deviation 2026-O0038) Feb 2026 52.226-8 Encouraging Contractor Policies to Ban Text Messaging While Driving. May 2024 52.229-12 Tax on Certain Foreign Procurements. (Deviation 2026-O0038) Feb 2026 52.232-33 Payment by Electronic Funds Transfer-System for Award Management. Oct 2018 52.232-40 Providing Accelerated Payments to Small Business Subcontractors. Mar 2023 52.233-3 Protest after Award. (Deviation 2026-O0038) Feb 2026 52.233-4 Applicable Law for Breach of Contract Claim. (Deviation 2026-O0038) Feb 2026 52.240-91 Security Prohibitions and Exclusions. (Deviation 2026-O0038) Feb 2026 52.244-6 Subcontracts for Commercial Products and Commercial Services. (Deviation 2026-O0038) Apr 2026

DFARS Clauses Incorporated by Reference

Number Title Effective Date Alternate/ Deviation

Variation Effective Date

252.203-7000 Requirements Relating to Compensation of Former DoD Officials. Sep 2011 252.203-7002 Requirement to Inform Employees of Whistleblower Rights. Dec 2022 252.204-7018 Prohibition on the Acquisition of Covered Defense Telecommunications Equipment or Services. Jan 2023 252.223-7008 Prohibition of Hexavalent Chromium. Jan 2023 252.225-7001 Buy American and Balance of Payments Program. Feb 2024 252.225-7002 Qualifying Country Sources as Subcontractors. Mar 2022 252.225-7012 Preference for Certain Domestic Commodities. Apr 2022 252.225-7056 Prohibition Regarding Business Operations with the Maduro Regime. Jan 2023 252.225-7060 Prohibition on Certain Procurements from the Xinjiang Uyghur Autonomous Region. Jun 2023 252.226-7001 Utilization of Indian Organizations, Indian-Owned Economic Enterprises, and Native Hawaiian Small

Business Concerns.

Jan 2023

252.232-7010 Levies on Contract Payments. Dec 2006 252.243-7002 Requests for Equitable Adjustment. Dec 2022 252.246-7008 Sources of Electronic Parts. Jan 2023 252.247-7023 Transportation of Supplies by Sea. Oct 2024

FAR Clauses Incorporated by Full Text

52.219-14 Limitations on Subcontracting. (Deviation 2026-O0038) (Feb 2026)

Limitations on Subcontracting (Feb 2026) (Deviation 2026-O0038)

(a) This clause does not apply to the unrestricted portion of a partial set-aside.

(b) Definition. Similarly situated entity, as used in this clause, means a first-tier subcontractor, including an independent contractor, that-

(1) Has the same small business program status as that which qualified the prime contractor for the award (e.g., for a small business set-aside contract, any small business concern, without regard to its socioeconomic status); and

(2) Is considered small for the size standard under the North American Industry Classification System (NAICS) code the prime contractor assigned to the subcontract.

(c) Applicability. This clause applies only to-

(1) Contracts that have been set aside for any of the small business concerns identified in 19.000(a)(3);

(2) Part or parts of a multiple-award contract that have been set aside for any of the small business concerns identified in 19.000(a)(3);

(3) Contracts that have been awarded on a sole-source basis in accordance with sections 19.105, 19.106, 19.107, and 19.108;

(4) Orders expected to exceed the simplified acquisition threshold and that are set aside for small business concerns under multiple-award contracts, as described in 8.4 and 16.5;

(5) Orders, regardless of dollar value, that are set aside in accordance with sections 19.105, 19.106, 19.107, and 19.108 under multiple-award contracts, as described in

8.4 and 16.5; and

(6) Contracts using the HUBZone price evaluation preference to award to a HUBZone small business concern unless the concern waived the evaluation preference.

(d) Independent contractors. An independent contractor shall be considered a subcontractor.

(e) By submission of an offer and execution of a contract, the Contractor agrees that in performance of a contract assigned a North American Industry Classification System (NAICS) code for-

(1) Services (except construction), it will not pay more than 50 percent of the amount paid by the Government for contract performance to subcontractors that are not similarly situated entities. Any work that a similarly situated entity further subcontracts will count towards the prime contractor's 50 percent subcontract amount that cannot be exceeded. When a contract includes both services and supplies, the 50 percent limitation shall apply only to the service portion of the contract;

(2) Supplies (other than procurement from a nonmanufacturer of such supplies), it will not pay more than 50 percent of the amount paid by the Government for contract performance, excluding the cost of materials, to subcontractors that are not similarly situated entities. Any work that a similarly situated entity further subcontracts will count towards the prime contractor's 50 percent subcontract amount that cannot be exceeded.