Solicitation - N0040626Q0522_Redacted.pdf

Section A - Solicitation/Contract Form

Shore Power Jumper Cables for a

Additional Regulation or Supplemental Clauses Incorporated by Full Text

FLCPS SRF 001 FLCPS_SRF_NOTICE_TO_OFFERORS (Aug 2025)

This Solicitation is a SOLE SOURCE REQUIREMENT for OEM (JOKELL) Shore Power Jumper Cable Assemblies for a

1. : The Government anticipates awarding a firm, fixed price contract in accordance withNOTICE TO ALL OFFERORS RFO Part 12in response to quotes/proposals received in response to this solicitation. A firm, fixed price contract places the maximum risk and full responsibility for all costs and resulting profit or loss on the contractor, offerors are advised to consider these risks when pricing their quotes/proposals.

2. See block 8 on page 1 of the solicitation for the closing date and time.

3. The deadline for submission of questions regarding the solicitation's terms, conditions, specifications, and/or the statement of work (SOW) / performance work statement (PWS) is 1 day prior to the solicitation's closing date. Submit via email, to the Contracting Official 1 day prior to solicitation closing date:

Name: Jeremy Wells Email: Jeremy.a.wells.civ@us.navy.mil

4. FOR SOLE SOURCE -

The Government will evaluate the offeror's price for reasonableness and past performance as part of the responsibility determination.

5. "EXCEPTIONS: All quoters MUST note all exceptions from the solicitation's terms, conditions, specifications, and/or the statement of work / performance work statement, if any. It will be assumed that any quote without mention of any exceptions will take no exception from all specifications, terms and conditions, clauses, or provisions within the solicitation."

6. SINGLE AWARD FOR ALL ITEMS: Due to the interrelationship of supplies and/or services to be provided hereunder, the Government reserves the right to make a single award to the quoter whose quote is considered in the best interest of the government, price and other factors considered. Therefore, quoters who quote less than the entire effort specified herein may be determined to be unacceptable.

7. Submission of invoices will be via WAWF; see Clause 252.232-7006.

PLEASE PROVIDE:

YOUR NAME:

YOUR SAM REGISTERED CAGE CODE NUMBER:

YOUR E-MAIL ADDRESS:

YOUR PHONE NUMBER:

LIST YOUR COMPANY SIZE: LARGE OR SMALL

YOUR COMPANY MUST BE REGISTERED WITH **SAM** SYSTEM AWARD FOR MANAGEMENT IN ORDER TO

RECEIVE A GOVERNMENT AWARD

THIS IS ALWAYS A FREE SITE TO REGISTER; SEE FOLLOWING LINK: HTTPS://WWW.SAM.GOV

N0040626Q0522

Section B - Supplies or Services & Prices or Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

Shore Power Cable Jumper Assemblies

PR# N6275826PR05299

Commercial and Government Entity (CAGE) Code: 5V049 Manufacturer's Name: JOKELL Part Reference Number: SPC1525MOD Pricing Arrangement: Firm Fixed Price

20 Each

Section C - Description/Specifications/Statement of Work

Requirements Modified Shore Power Cable Jumper Assemblies

Additional Regulation or Supplemental Clauses Incorporated by Full Text

243-9400(1-92) SUPTXT243-9400(1-92) AUTHORIZED CHANGES ONLY BY THE

CONTRACTING OFFICER

(Jan 2024)

AUTHORIZED CHANGES ONLY BY THE CONTRACTING OFFICER

(a) Except as specified in paragraph (b) below, no order, statement, or conduct of Government personnel who visit the Contractor's facilities or in any other manner communicate with Contractor personnel during the performance of this contract shall constitute a change under the "Changes" clause of this contract.

(b) The Contractor shall not comply with any order, direction or request of Government personnel unless it is issued in writing and signed by the Contracting Officer, or is pursuant to specific authority otherwise included as a part of this contract.

(c) The Contracting Officer is the only person authorized to approve changes in any of the requirements of this contract and notwithstanding provisions contained elsewhere in this contract, the said authority remains solely with the Contracting Officer. In the event the Contractor effects any change at the direction of any person other than the Contracting Officer, the change will be considered to have been made without authority and no adjustment will be made in the contract price to cover any increase in charges incurred as a result thereof. The address and telephone number of the Contracting Officer is:

Section D - Packaging and Marking

Additional Regulation or Supplemental Clauses Incorporated by Full Text

FLCPS SRF 007 FLCPS_SRF_DELIVERY (Aug 2025)

PREPARATION FOR DELIVERY (COMMERCIALLY PACKAGED ITEMS)

(a) Preservation, packaging, and packing shall be in accordance with ASTM-D-3951 (most current edition), "Standard for Commercial Packing." The unit pack quantity that applies to items under this contract is "Industry Standard".

(b) Prohibited Packing Materials. The use of asbestos, excelsior, loose fill polystyrene, newspaper or shredded paper (all types including waxed paper, computer paper and similar hydroscopic or non-neutral material) is prohibited.

(c) Non-Manufactured Wood Packing. All non-manufactured wood utilized in wood pallets and wood containers shall be heat treated to a minimum core temperature of 56 degrees centigrade for 30 minutes and certified by an accredited agency recognized by the American Lumber Standards Committee (ALSC). Refer to https://www.aphis.usda.gov/aphis/ourfocus/planthealth/import-information/wood-packaging-material for wood packing policy, enforcement regulations and accredited agencies. Non-coniferous (hardwood) and manufactured wood, such as particleboard and plywood, are exempt from this requirement.

(d) Manufactured wood, such as particleboard and plywood, are exempt from this requirement.

(e) Packing must be sufficient to ensure safe delivery to the final destination without the need for additional repackaging or repair.

(f) All materials shall be packed to withstand multiple modes of transport (truck, rail, sea, or air) and handling by forklifts or cranes.

(g) Heavy items must be crated or skid-mounted to distribute weight evenly and ensure lifting point are accessible and marked.

(h) Packages must be stable, not exceed safe stacking limits, and be secured against movement in transit.

MARKING OF SHIPMENTS (COMMERCIALLY PACKAGED ITEMS)

(i) Marking shall be in accordance with ASTM-D-3951 (most current edition) and with the information set forth in paragraph (ii) below. Unless specified elsewhere in this contract/order, bar coding is not required.

(ii) All unit and exterior containers/packs shall, as a minimum, be marked as follows:

1. National stock number (NSN), when available, or Federal stock number (FSN), when NSN is not available, or part number when neither NSN or FSN are available.

2. Noun nomenclature cited on contract or order.

3. Quantity and unit of issue.

4. Contract, or order number.

5. From:_______________________________________________ (Contractor's Name) (Address)

6. To: (See delivery address on page 3-4 or in Section F)

(iii) Markings may be applied by any means which provide legibility.

TRACEABLE FREIGHT

The Contractor shall assume all responsibility for shipment to the specified destination. Shipment must be via a fully traceable commercial freight method. Traceable freight means that the shipment is registered upon shipment with an identifying number. The number is for location of the shipment at any point in transit, including final destination, and verifies shipment arrival at the specified destination. If a shipping method does not provide traceability as defined above, it shall not be used.

PROOF OF DELIVERY

If United Parcel Service (UPS) or Federal Express services are used for transportation, each package must have a unique package identification number. The Government will not consider the manifest as proof of delivery unless each package can be uniquely identified. Acceptance will occur only after the Government can verify actual receipt of the contract items--packaged, marked and labeled as required elsewhere in this contract.

Section E - Inspection and Acceptance

Overall Contract Inspection/Acceptance Locations

Section F - Deliveries or Performance

Overall Contract Delivery Period

Government Origin (Shipping Point)

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

Additional Regulation or Supplemental Clauses Incorporated by Full Text

FLCPS SRF 006 FLCPS_SRF_SHIPPING (Aug 2025)

I. INTRODUCTION

For this FOB Origin procurement, the Government will arrange for transportation and pay all associated transportation costs through the NAVSUP WSS Shipment Processing (SP) office (aka NAVSUP GLS, NAVSUP LOC or NOLSC). NAVSUP WSS will process shipments of materials from within the United States to CONUS (Continental United States)/OCONUS (Outside Continental United States) consignees with delivery terms Free On-Board (FOB) Origin.

Contractors/vendors shall complete the Naval Supply Systems Command automated Ready-to-Ship (RTS) web form by accessing the link provided below in Section II. By completing the form on line, the NAVSUP WSS at Norfolk, VA will receive an email of the shipment request immediately and will act on it as soon as possible during their normal working hours of 7:30 AM to 6:00 PM Eastern Time Monday through Friday. In response, NAVSUP WSS will provide MANDATORY USE shipping labels to the contractor/vendor. The contractor/vendor will arrange for shipment with the NAVSUP WSS designated carrier IMMEDIATELY upon receipt of the shipping labels. If the NAVSUP WSS provided shipping labels are not used, the contractor/vendor will experience delays and additional work to reconcile the transportation payment under the NAVSUP WSS tracking number and possible additional costs not covered under the contract or NAVSUP WSS Transportation. If the contractor/vendor turns an ordered vehicle away and a vehicle furnished not used charge is incurred the contractor/vendor is responsible for payment. If the contractor/vendor detains the vehicle and incurs a detention charge the contractor/vendor is responsible for payment. International small parcel shipment documents are invalid after five business days. If the vendor incurs any extra costs with the carrier outside of the CBL/GBL it is the vendors responsibility for payment.

NAVSUP WSS does not accept hazardous or explosive shipments.

CONTRACTORS/VENDORS ARE NOT AUTHORIZED TO ARRANGE FOR TRANSPORTATION OR PAY TRANSPORTATION

COSTS FOR

SHIPMENT OF FOB ORIGIN PROCUREMENT.

II. PROCEDURES FOR CONTRACTORS TO REQUEST READY-TO-SHIP (RTS) NOTICES

When the cargo is ready for shipment, the contractor/vendor will submit their shipping request to NAVSUP WSS using the following procedures:

Click on the link at https://mynavsup-public.nag.navy.mil/public/ops$mailer.ready_to_ship_form to open the NAVSUP WSS RTS Web Form. The contractor/vendor is required to fill in all data fields marked with a red asterisk under the headings "Vendor Information" and "Package Information."

The fields not marked with a red asterisk and the heading "Additional Notes" are optional fields to be filled in at the contractor's/vendor's discretion.

Click on the blue question mark at the right of each data field to access "On-line Data Element Help" which explains the data required in that field. If shipping labels are being requested for multiple packages, enter the data for the first package under "Package Information" then click the "Store Pkg Info" button. Repeat this procedure for each package. When all data has been entered on the electronic form, click the "Submit" button.

Container Shipments: containers take longer to book and arrange for loading. If you can provide reliable dimensions and weight estimates for the cargo, send the initial shipping request THREE WEEKS before your requested container load date.

If you have any questions regarding the web form, contact NAVSUP WSS Transportation directly at (757) 443-5449 or usn.norfolk.

navsupwssnorf.

mbx.navsup-nfmgt1@us.navy.mil

NOTE: Incomplete or missing information will significantly delay the process of arranging transportation.

III. CONTRACTING OFFICER SHALL PROVIDE THE FOLLOWING INFORMATION:

*Information provided at time of Award.

Contract Number: ____________________________________ Transportation Control Number (TCN): __________________ Transportation Priority (TP): ___________________________ Required Delivery Date (RDD): _________________________ Transportation Account Code (TAC): ____________________ Destination DODAAC: ________________________________

**SASEBO - MAKE SURE YOU ARE USING TCN (FIRST 5 DIGITS) & DODAAC N45598

IV. NAVSUP WSS CONTACT INFORMATION

NOTE: The preferred method of contact is through email. Phone numbers are provided only for emergencies.

For Assistance Email (preferred): navsup_nfmgt.fct@navy.mil Fax: (757) 443-5517 Phone: (757) 443-5449 Business Hours: M-F 7:00 AM to 3:30 PM ET.

Section G - 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. (Tailored) (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 Electronic invoicing.

authorized by Defense 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 WAWF training.

Training Site before 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 WAWF methods of document submission.

Protocol.

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

WAWF for this contract 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.

_COMBO___

(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.

N/A

(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.

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

when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF

Pay Official DoDAAC

Issue By DoDAAC

Admin DoDAAC

Inspect By DoDAAC

Ship To Code

Ship From Code

Mark For Code

Service Approver (DoDAAC)

Service Acceptor (DoDAAC)

Accept at Other DoDAAC

LPO DoDAAC

DCAA Auditor DoDAAC

Other DoDAAC(s)

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

accordance with the 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.

Additional Regulation or Supplemental Clauses Incorporated by Full Text

FLCPS_C230_WAWF FLCPS_C230_WAWF (Apr 2026)

MSC SPECIFIC WIDE AREA WORKFLOW (WAWF) INSTRUCTIONS (AUG 2012)

The information contained in this instruction is supplemental to DFARS 252.232-7006. The information contained in the table in DFARS 252.232- 7006 is for WAWF purposes only. Information included in DFARS 252.232-7006 and this WAWF instruction apply only to WAWF Invoicing and WAWF Receiving Reports. Contradictory information elsewhere in this contract, e.g. Ship to DoDAAC, shall be followed per the terms and conditions of the contract.

When entering the invoice into WAWF, the Contractor shall fill in the DoDAAC fields or DoDAAC extensions exactly as shown in the table in DFARS 252.232-7006. Fields that should not be filled in when entering the invoice into WAWF will be indicated with the direction, "Leave Blank."

In some situations, the WAWF system will pre-populate the "Pay DoDAAC," "Admin By DoDAAC" and "Issue By DoDAAC." The Contractor shall verify that those DoDAAC automatically entered by the WAWF system match the information in the table in DFARS 252.232-7006. If these DoDAACs do not match, then the Contractor shall correct the field(s).

If Receiving Reports are required, ensure that the "Inspection" and "Acceptance" defaults of "destination" for both fields are not changed in the WAWF online interface.

The CLINs on the WAWF invoice shall be entered exactly as set forth in the contract document including CLIN number (e.g. 0001), Quantity (may be adjusted for actual quantity or dollar value delivered and invoiced), and Unit Price (e.g. $1.00). The dollar amounts on each CLIN or SubCLIN on the WAWF invoice shall reflect final performance values, but in no instance can the dollar amount for each CLIN or SubCLIN exceed what is specified in the contract document. The Contractor shall bill to the lowest level, e.g., the SubCLIN level. The Quantity and Unit of Measure fields must be filled out exactly as indicated in the CLINs and SubCLINs to reduce the possibility of the invoice being delayed or rejected during processing.

Before closing out of an invoice session in WAWF, but after submitting the document or documents, the Contractor will be given the option to send additional email notifications by clicking on the "Send More Email Notifications" link that appears on the page. The Contractor shall click on this link and add the Technical Point of Contact's (TPOC) or Contracting Officer's Representative's (COR) email address in the first email address block and add any other additional email addresses desired in the following blocks. This additional notification to the Government is important to ensure the acceptor/receiver is aware that the invoice documents have been submitted into the WAWF system.

Section H - Special Contract Requirements

Section I - Contract Clauses

252.225-7962 Threat Mitigation Support to Operations. (DEVIATION 2026-O0051)

VENDOR THREAT MITIGATION SUPPORT TO OPERATIONS

(JUN 2026) (DEVIATION 2026-O0051)

(a) Definitions. As used in this clause-- "Covered activities" means activities in which a covered person or entity is--

(1) Engaging in acts of violence against personnel of the United States or its partners and allies;

(2) Providing financing, logistics, training, or intelligence to a person or entity engaging in acts of violence against personnel of the United States or its partners and allies;

(3) Engaging in foreign intelligence activities against the United States or its partners and allies;

(4) Engaging in transnational organized crime or criminal activities; or

(5) Engaging in other activities that present a direct or indirect risk to United States or partner and allied missions and forces.

"Covered contract" means a contract that is performed outside the United States, including its outlying areas.

"Covered person or entity" means any person, corporation, company, limited liability company, limited partnership, business trust, business association, or other similar entity outside of the United States or any foreign reporting company in accordance with 31 U.S.C. 5336(a)(11)(A)(ii) that is responding to a covered solicitation or performing work on a covered contract.

"Covered procurement action" means an action taken by a head of contracting activity to--

(1) Exclude a person or commercial entity from an award with or without an existing contract;

(2) Terminate a contract for default or cause; or

(3) Void, in whole or in part, a contract.

(b) Authority. This clause implements section 841 of the National Defense Authorization Act (NDAA) for Fiscal Year (FY) 2015 (Pub. L. 113-291) and section 823 of the NDAA for FY 2024 (Pub. L. 118-31). Sections 841 and 823 provide the Government the authority to mitigate and prevent covered activities by taking covered procurement actions.

(c) Compliance.

(1) The Contractor and its personnel must be familiar with and comply with--

(i) Vendor Threat Mitigation (VTM) policies, including but not limited to the Department of Defense Directive 3000.16, Vendor Threat Mitigation;

and

(ii) The VTM program established by the respective combatant command, including the orders, directives, and instructions issued by the Combatant Commander relating to VTM support to operations.

(2) The Contractor and its personnel must not engage in covered activities.

(3) The Contractor must exercise due diligence to mitigate covered activities from occurring under this contract and all subcontracts. Due diligence includes but is not limited to--

(i) Checking the list of prohibited or restricted sources in the System for Award Management (SAM) at www.sam.gov prior to subcontract award and at least monthly thereafter to ensure subcontractor eligibility;

(ii) Terminating or voiding, in whole or in part, any subcontract with a person or entity listed in SAM as a prohibited or restricted source pursuant to section 841 of the NDAA for FY 2015 and section 823 of the NDAA for FY 2024, unless the Contracting Officer provides to the Contractor written approval to continue the subcontract; and

(iii) Leveraging all available resources and tools to mitigate engagement in covered activities.

(4) The Contractor must notify the Contracting Officer immediately upon a finding of covered activities taking place under this contract.

(d) Subcontracts. The Contractor must include the substance of this clause, including this paragraph (d), in subcontracts, including subcontracts for commercial products and commercial services, that will be performed outside the United States and its outlying areas.

(End of clause)

252.225-7975 Additional Access to Contractor and Subcontractor Records. (DEVIATION 2026-O0051) ADDITIONAL ACCESS TO CONTRACTOR AND SUBCONTRACTOR RECORDS (JUN 2026) (DEVIATION 2026-O0051)

(a) Authority. As authorized by sections 841 and 842 of the National Defense Authorization Act (NDAA) for Fiscal Year (FY) 2015 and section 823 of the NDAA for FY 2024, and in addition to any other existing examination-of-records authority, the Government is authorized to examine any records of the Contractor and its subcontractors to the extent necessary to support the Vendor Threat Mitigation Programs established by combatant commanders.

(b) Subcontracts. The Contractor must include the substance of this clause, including this paragraph (b), in subcontracts, including subcontracts for commercial products and commercial services, that will be performed outside the United States and its outlying areas.

(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-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.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-36 Equal Opportunity for Workers with Disabilities. (Deviation 2026-O0038) Feb 2026 52.222-50 Combating Trafficking in Persons. (Deviation 2026-O0038) Feb 2026 52.226-8 Encouraging Contractor Policies to Ban Text Messaging While Driving. May 2024 52.232-29 Terms for Financing of Purchases of Commercial Products and Commercial Services. Nov 2021 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.240-93 Basic Safeguarding of Covered Contractor Information Systems. (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-7009 Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.

Jan 2023

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

252.204-7018 Prohibition on the Acquisition of Covered Defense Telecommunications Equipment or Services.

Jan 2023

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.225-7962 Vendor Threat Mitigation Support to Operations. (DEVIATION 2026-O0051) Jun 2026 Deviation 2026-O0051 Jun 2026

252.225-7975 Additional Access to Contractor and Subcontractor Records. (DEVIATION 2026-O0051)

Jun 2026 Deviation 2026-O0051 Jun 2026

252.232-7010 Levies on Contract Payments. Dec 2006

252.244-7999 Subcontracts for Commercial Products or Commercial Services.

(DEVIATION 2026-O0015)

Feb 2026 Deviation 2026-O0015 Jan 2026

252.246-7003 Notification of Potential Safety Issues. Jan 2023 252.247-7023 Transportation of Supplies by Sea. Oct 2024 252.247-7028 Application for U.S. Government Shipping Documentation/ Instructions. Jun 2012

DFARS Clauses Incorporated by Full Text

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

(Nov 2025)

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

(a) . As used in this clause- Definitions

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

"Current" means-

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

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

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

170.16 and 170.17); and

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

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

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

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

(2) With regard to Final CMMC Status-

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

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

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

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

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

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

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

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

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

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

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

(1) Final Level 1 (Self).

(2) Conditional Level 2 (Self).

(3) Final Level 2 (Self).

(4) Conditional Level 2 (C3PAO).

(5) Final Level 2 (C3PAO).

(6) Conditional Level 3 (DIBCAC).

(7) Final Level 3 (DIBCAC).

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

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

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

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

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

(d) . The Contractor shall- Requirements

(1)(i) Have and maintain for the duration of the contract a current CMMC status at the following CMMC level, or higher:

for all information Contracting Officer insert: CMMC Level 1 (Self); CMMC Level 2 (Self); CMMC Level 2 (C3PAO); or CMMC Level 3 (DIBCAC) systems used in performance of the contract, task order, or delivery order that process, store, or transmit FCI or CUI; and

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

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

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

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

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

(e) . The Contractor shall- Reporting

(1) Submit to the Contracting Officer-

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

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

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

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

(f) . The Contractor shall- Subcontracts

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

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

(End of clause)

252.211-7003 Item Unique Identification and Valuation. (Jan 2023)

ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023)

(a) . As used in this clause- Definitions

"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, or 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 changes 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) The Contractor shall ensure that- Data syntax and semantics of unique item identifiers.

(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-

Serialize within the enterprise identifier; (1)

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

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

(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…