This is a combined synopsis/solicitation for commercial items prepared in accordance with Federal Acquisition Regulation (FAR) Subpart 12.6, as supplemented with additional information included in this notice. The Naval Surface Warfare Center Carderock Division (NSWCCD) intends to solicit only one source under the authority of FAR Part 13.106-1(b) the Contracting Officer has determined that circumstances of the contract action deem only one source reasonably available. The Government intends to solicit with Gexcon, Inc. for Gexcon X- Suite Software.

The provisions and clauses included and/or incorporated in this solicitation document are those in effect through the Federal Acquisition Circular. This RFQ incorporates all provisions and clauses in effect through Federal Acquisition Circular FAC 2026-01 and the Defense Federal Acquisition Regulation Supplement (DFARS) DPN 20260702. SEE ATTACHED SOLICITATION FOR

CLAUSES AND PROVISIONS.

Interested parties may identify their interest to this requirement by submitting a capabilities statement no later than the response due date. This notice is NOT a request for competitive quotes. However, all capabilities statements received by the above deadline will be considered by the Government. A determination by the Government not to compete this proposed purchase order based upon responses to this notice is solely within the discretion of the Government. Information received will normally be considered solely for the purpose of determining whether to conduct a competitive procurement. All responses shall include price(s), FOB point, a point of contact, name and phone number, GSA contract number (if applicable), business size, and payment terms. Each response must clearly indicate the capability of the quoter to meet all specifications and requirements.

Responses to this notice are due on or before 10:00 AM ET on Thursday, 27 August 2026 by email to tracy.l.mcdonough2.civ@us.navy.mil

Point of Contact for this notice is Tracy McDonough at tracy.l.mcdonough2.civ@us.navy.mil

Section A - Solicitation/Contract Form

Gexcon X-Suite Software

N0016726Q1153

Section B - Supplies or Services & Prices or Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

Gexcon X-Suite Software Suite in accordance with the requirement specifications.

Manufacturer's Name: Gexcon Pricing Arrangement: Firm Fixed Price

1 Each

Section C - Description/Specifications/Statement of Work

REQUIREMENT SPECIFICATIONS

Gexcon X-Suite Software

1.0 DESCRIPTION OF SERVICES/INTRODUCTION:

The Naval Surface Warfare Center Carderock Division (NSWCCD) Code 612, Fire Protection Group (FPG), requires a contract to procure the GEXCON Inc. X-Suite software. The software suite will enable FPG to accurately assess the risk and consequence of various shipboard fire and explosion hazards. The procurement of this assessment tool will directly support recurring requests from both the Fire Protection Systems and Damage and Fire Recoverability Technical Warrant Holders at NAVSEA 05P5 to characterize the threat associated with emerging shipboard fire hazards (i.e., lithium batteries).

2.0 BACKGROUND:

To date, FPG has supported fire and explosion hazard assessments using empirical data sets and first-order approximations. These analytical approaches generally result in extremely conservative outcomes and provide very little fidelity which can slow and/or prevent informed decisions from being made by NAVSEA customers. The procurement of the X-suite software will enable FPG to better resolve shipboard fire and explosion hazards and enable stakeholders to more efficiently and accurately assess risk and consequence from a much more informed posture.

3.0 OBJECTIVE:

The objective is to procure a software tool which, when coupled with shipboard space geometries and fire/combustible gas release scenarios, enables advanced analytics based on code integration. This procurement is to improve the analytical capability of NSWCCD FPG in the area of hazard, consequence, and risk assessment as it relates to shipboard fires and explosion casualties. The acquisition of the GEXCON X-suite analytical tool will satisfy this objective and will enable FPG to not only support existing customers with an increased level of technical rigor but will also expand the customer base which FPG can support in the future.

4.0 MINIMUM SPECIFICATIONS FOR GEXCON X-SUITE ANALYTICAL TOOL

4.1 The contractor shall provide the software suite to include the ability to:

4.1.1 Integrate both risk and consequence considerations into a common user portfolio

4.1.2 Enable high-throughput computations for the following computational fluid dynamics simulations:

4.1.2.1 Combustible and toxic gas dispersion

4.1.2.2 Pool and jet fires

4.1.2.3 Vapor cloud explosions

4.1.2.4 Scheil-Gulliver solidification

4.1.2.5 Material property models

4.1.3 Leverage a Porosity Distributed Resistance (PDR) approach, to allow for the modeling of complex shipboard structures without resolving every obstruction within the model mesh.

4.1.4 Allow users to perform parallel computations

4.1.5 Use object-oriented approach to accelerate calculations and enable composition modifications as the simulation progresses using application programming interface (API)

4.1.6 Possess graphical user interface (GUI) in both pre- and post-processing tools

4.1.7 Enable parametric study of integral model parameters to inform risk assessments

4.1.8 Include example datasets for user training and validation/verification studies

4.2 The contractor shall provide three (3) virtual training days for the EFFECTS&RISK CURVES for 3 users.

4.3 The contractor shall provide licensing that can be locally-hosted on NSWCCD IT infrastructure.

5.0 APPLICABLE DOCUMENTS:

NAVSEA 5100.12-M, "System Safety Engineering (SSE) Manual," January 2014.

MIL-STD-882E, "Department of Defense Standard Practice System Safety," September 2023.

NAVSEA INST 9310.1C, "Naval Lithium Battery Safety Program," August 2015.

6.0 PERIOD OF PERFORMANCE:

Dates for virtual training will be coordinated after award.

7.0 SECURITY REQUIREMENTS:

Unclassified

Requirements Gexcon X-Suite Software

Additional Regulation or Supplemental Clauses Incorporated by Full Text

C-204-H001 USE OF NAVY SUPPORT CONTRACTORS FOR OFFICIAL CONTRACT FILES (Oct 2018)

(a) NAVSEA may use a file room management support contractor, hereinafter referred to as "the support contractor", to manage its file room, in which all official contract files, including the official file supporting this procurement, are retained. These official files may contain information that is considered a trade secret, proprietary, business sensitive or otherwise protected pursuant to law or regulation, hereinafter referred to as "protected information". File room management services consist of any of the following: secretarial or clerical support; data entry; document reproduction, scanning, imaging, or destruction; operation, management, or maintenance of paper-based or electronic mail rooms, file rooms, or libraries; and supervision in connection with functions listed herein.

(b) The cognizant Contracting Officer will ensure that any NAVSEA contract under which these file room management services are acquired will contain a requirement that:

(1) The support contractor not disclose any information;

(2) Individual employees are to be instructed by the support contractor regarding the sensitivity of the official contract files;

(3) The support contractor performing these services be barred from providing any other supplies and/or services, or competing to do so, to NAVSEA for the period of performance of its contract and for an additional three years thereafter unless otherwise provided by law or regulation; and,

(4) In addition to any other rights the contractor may have, it is a third party beneficiary who has the right of direct action against the support contractor, or any person to whom the support contractor has released or disclosed protected information, for the unauthorized duplication, release, or disclosure of such protected information.

(c) Execution of this contract by the contractor is considered consent to NAVSEA's permitting access to any information, irrespective of restrictive markings or the nature of the information submitted, by its file room management support contractor for the limited purpose of executing its file room support contract responsibilities.

(d) NAVSEA may, without further notice, enter into contracts with other contractors for these services. Contractors should enter into separate non-disclosure agreements with the file room contractor. Contact the Procuring Contracting Officer for contractor specifics. However, any such agreement will not be considered a prerequisite before information submitted is stored in the file room or otherwise encumber the government.

(End of Text)

C-211-H018 APPROVAL BY THE GOVERNMENT (NAVSEA) (JAN 2019) (Jan 2019)

Approval by the Government as required under this contract and applicable specifications shall not relieve the Contractor of its obligation to comply with the specifications and with all other requirements of the contract, nor shall it impose upon the Government any liability it would not have had in the absence of such approval.

(End of Text)

Section D - Packaging and Marking

Section E - Inspection and Acceptance

Overall Contract Inspection/Acceptance Locations

Inspection and Acceptance Location

Both Destination Instructions: Please contact the POC upon delivery for inspection and acceptance

DoDAAC: N00167 CountryCode: USA

NSWC CARDEROCK

CARDEROCK DIVISION, 9500 MACARTHUR BOULEVARD

BETHESDA, MD 20817-5700

UNITED STATES

TBD, TBD

Email: TBD Telephone: TBD

Section F - Deliveries or Performance

Overall Contract Delivery Period

Contractor Destination

Line Item Delivery Schedule Quantity Address and POC

Delivery Requested By Delivery Date 30 Sep 2026

1 Each Ship To DoDAAC: N00167 CountryCode: USA

NSWC CARDEROCK

CARDEROCK DIVISION BLDG 143, 9500 MACARTHUR BOULEVARD

BETHESDA, MD 20817-5700

UNITED STATES

TBD, TPOC

Email: TBD Telephone: TBD

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.247-34 F.o.b. Destination. Jan 1991

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.

Invoice and Receiving Report (COMBO) Destination/Destination (D/D)

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

Invoice and Receiving Report (COMBO) Destination/Destination (D/D)

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

Issue By DoDAAC N00167

Admin DoDAAC N00167

Inspect By DoDAAC N00167

Ship To Code N00167

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 points of contact.

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

Ademola Oriowo at 301-503-0809 or by email ademola.m.oriowo.civ@us.navy.mil

Or the NAVSEA Helpdesk at WAWFHQ@navy.mil

You may also contact the below SAP Coordinator:

Sheila Riggs sheila.b.riggs.civ@us.navy.mil

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

(End of clause)

Additional Regulation or Supplemental Clauses Incorporated by Full Text

G-232-H005 SUPPLEMENTAL INSTRUCTIONS REGARDING INVOICING (NAVSEA) (JAN

2019)

(Jan 2019)

(a) For other than firm fixed priced contract line item numbers (CLINs), the Contractor agrees to segregate costs incurred under this contract/task order (TO), as applicable, at the lowest level of performance, either at the sub line item number (SLIN) or CLIN level, rather than at the total contract/TO level, and to submit invoices reflecting costs incurred at that level. Supporting documentation in Wide Area Workflow (WAWF) for invoices shall include summaries of work charged during the period covered as well as overall cumulative summaries by individual labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost break down of other direct costs (ODCs), materials, and travel, by technical instruction (TI), SLIN, or CLIN level. For other than firm fixed price subcontracts, subcontractors are also required to provide labor categories, rates, and hours (both straight time and overtime) invoiced; as well as, a cost breakdown of ODCs, materials, and travel invoiced. Supporting documentation may be encrypted before submission to the prime contractor for WAWF invoice submittal. Subcontractors may email encryption code information directly to the Contracting Officer and Contracting Officer Representative (COR). Shouldthe subcontractor lack encryption capability, the subcontractor may also email detailed supporting cost information directly to the Contracting Officer and COR; or other method as agreed to by the Contracting Officer.

(b) Contractors submitting payment requests and receiving reports to WAWF using either Electronic Data Interchange (EDI) or Secure File Transfer Protocol (SFTP) shall separately send an email notification to the COR and Contracting Officer on the same date they submit the invoice in WAWF. No payments shall be due if the contractor does not provide the COR and Contracting Officer email notification as required herein.

N0016726Q1153 mailto:ademola.m.oriowo.civ@us.navy.mil mailto:WAWFHQ@navy.mil

(End of Text)

G-232-H002 H002 PAYMENT INSTRUCTIONS (NAVSEA) (FEB 2024) (Feb 2024)

Payment office allocation methods can be found in the table at DFARS PGI 204.7108(b)(2) (https://www.acq.osd.mil/dpap /dars/pgi/pgi_htm/current/PGI204_71.htm#payment_instructions).

(End of text)

G-242-H002 HOURS OF OPERATION AND HOLIDAY SCHEDULE (NAVSEA) (JUL 2021) (Jul 2021)

(a) The policy of this activity is to schedule periods of reduced operations or shutdown during holiday periods. Deliveries will not be accepted on Saturdays, Sundays or Holidays except as specifically requested by the Technical Point of Contact. All goods or services attempted to be delivered on a Saturday, Sunday or Holiday without specific instructions from the Contracting Officer or his duly appointed representative will be returned to the contractor at the contractor’s expense with no cost or liability to the U.S. Government.

(b) The federal Government observes public Holidays that have been established under 5 U.S.C. 6103. The actual date of observance for each of the holidays, for a specific calendar year, may be obtained from the OPM website at OPM.GOV or by using the following direct link: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/.

(c) Delayed Opening, Early Dismissal and Closure of Government Facilities. When a Government facility has a delayed opening, is closed or Federal employees are dismissed early (due to severe weather, security threat, security exercise, or a facility related problem) that prevents personnel from working, onsite contractor personnel regularly assigned to work at that facility shall follow the same reporting and/or departure directions given to Government personnel. The contractor shall not direct charge to the contract for such time off, but shall follow parent company policies regarding taking leave (administrative or other). Non-essential contractor personnel, who are not required to remain at or report to the facility, shall follow their parent company policy regarding whether they should go/stay home or report to another company facility. Subsequent to an early dismissal, delayed opening, or during periods of inclement weather, onsite contractors should monitor the OPM website as well as radio and television announcements before departing for work to determine if the facility is closed or operating on a delayed arrival basis.

(d) When Federal employees are excused from work due to a holiday or a special event (that is unrelated to severe weather, a security threat, or a facility related problem), on site contractors shall continue working established work hours or take leave in accordance with parent company policy. Those contractor employees who take leave shall not direct charge the non-working hours to the contract. Contractors are responsible for predetermining and disclosing their charging practices for early dismissal, delayed openings, or closings in accordance with the FAR, applicable cost accounting standards, and the company's established policy and procedures. Contractors shall follow their disclosed charging practices during the contract period of performance, and shall not follow any verbal directions to the contrary. The Contracting Officer will make the determination of cost allowability for time lost due to facility closure in accordance with FAR, applicable Cost Accounting Standards, and the Contractor's established accounting policy and procedures.

(e) If you intend to visit the Contracts Office, it is advised that you call for an appointment at least 24 hours in advance.

(f) The hours of operation are as follows:

AREA FROM TO

West Bethesda, MD 0800 1400

(g) All deliveries to the Receiving Officer or Technical Point of Contact to the , shall be made Monday through address as identified in Box 15 Friday from to , local time. Deliveries will not be accepted after . No deliveries will be accepted on federal government holidays.0800 1400 1400

(End of Text)

G-242-H001 - GOVERNMENT CONTRACTADMINISTRATION POINTS-OF-CONTACT AND

RESPONSIBILITIES (NAVSEA) (OCT 2023)

(Oct 2023)

N0016726Q1153 https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/ https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays

(a) The Government reserves the right to administratively substitute any of the points of contact listed below at any time.

(b) The contracting officer is the only person authorized to change this contract or orders issued thereunder. The Contractor shall not comply with any order, direction or request of Government personnel - that would constitute a change - unless it is issued in writing and signed by the Contracting Officer or is pursuant to specific authority otherwise included as part of this contract. If, in the opinion of the contractor, an effort outside the existing scope of this contract is requested, the contractor shall promptly comply with the Notification of Changes clause of this contract.

(c) The points of contact are as follows:

(i) The Procuring Contracting Officer (PCO) is:

The Procuring Contracting Officer (PCO) is:

Name: Kristen Duhaime

Address: 904 Corporate Lane, Chesapeake, VA 23220

Phone: (301) 219-7629

E-mail: kristen.m.duhaime.civ@us.navy.mil

The Contract Specialist is:

Name: Tracy McDonough Phone: (757) 288-6854 E-mail: tracy.l.mcdonough2.civ@us.navy.mil

(d) The Technical Point of Contact (TPOC) is the contracting officer's representative for technical matters when a COR is not appointed. The TPOC is responsible for technical issues of contract administration, such as providing all items of Government Furnished Information (GFI), Government Furnished Material (GFM) and Government Furnished Equipment (GFE) if specified in the contract as well as the inspection and acceptance of all contract deliverables.

The Technical Point of Contact (TPOC) is:

Name: [ * ] Address: [ *Street ] [ *City, State, Zip ] Phone: (Area Code) xxx- [xxxx] E-mail: [ * ]

[ * ] To be completed at contract award

(End of Text)

G-242-W001 CONTRACT ADMINISTRATION FUNCTIONS (NAVSEA) (OCT 2018) (Oct 2018)

(a) In accordance with FAR 42.302(a) all functions listed are delegated to the ACO except the following items to be retained by the PCO:

N/A

(b) In accordance with FAR 42.302(b), the following additional functions are delegated to the ACO:

N/A

(End of Text)

N0016726Q1153 mailto:kristen.m.duhaime.civ@us.navy.mil mailto:tracy.l.mcdonough2.civ@us.navy.mil

Section H - Special Contract Requirements

Section I - Contract Clauses

SOFTWARE LANGUAGE

No terms will be incorporated into any price quote and/or order accepted by the Government unless otherwise agreed to by all parties in writing. Any and all terms and conditions contained in any price quote and/or order that violate any Federal laws, statutes, and regulations, including but not limited to, the Federal Acquisition Regulation (FAR) and Defense Federal Acquisition Regulation Supplement (DFARS) are void and will have no effect. The applicable Federal laws, statutes, and regulations, including, but not limited to, the FAR and DFARS will govern instead.

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.203-12 Limitation on Payments to Influence Certain Federal Transactions. Jun 2020 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-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-50 Combating Trafficking in Persons. (Deviation 2026-O0038) Feb 2026 52.222-54 Employment Eligibility Verification. (Deviation 2026-O0038) Feb 2026

52.222-90 Addressing DEI Discrimination by Federal Contractors. (Deviation 2026-O0040, Revision 1)

Apr 2026

52.226-8 Encouraging Contractor Policies to Ban Text Messaging While Driving. May 2024 52.232-33 Payment by Electronic Funds Transfer-System for Award Management. Oct 2018 52.232-39 Unenforceability of Unauthorized Obligations. Jun 2013 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-7004 Antiterrorism Awareness Training for Contractors. Jan 2023

252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting

(DEVIATION 2026-O0025)

May 2024 Deviation 2026-O0025 Jun 2026

252.204-7015 Notice of Authorized Disclosure of Information for Litigation Support. Jan 2023

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

Jan 2023

252.204-7022 Expediting Contract Closeout. May 2021

252.209-7004 Subcontracting with Firms that are Owned or Controlled by the Government of a Country that is a State Sponsor of Terrorism.

May 2019

252.223-7008 Prohibition of Hexavalent Chromium. Jan 2023 252.225-7012 Preference for Certain Domestic Commodities. Apr 2022 252.225-7048 Export-Controlled Items. Jun 2013 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-7061 Restriction on the Acquisition of Personal Protective Equipment and Certain Other Items from Non-Allied Foreign Nations.

Jan 2023

252.225-7972 Prohibition on the Procurement of Foreign-Made Unmanned Aircraft Systems. (DEVIATION 2024-O0014)

Aug 2024 Deviation 2024-O0014 Aug 2024

252.232-7010 Levies on Contract Payments. Dec 2006 252.237-7010 Prohibition on Interrogation of Detainees by Contractor Personnel. Jan 2023 252.239-7010 Cloud Computing Services. Jan 2023 252.239-7018 Supply Chain Risk. Dec 2022

252.240-7007 Prohibitions Relating to Chinese Military Companies. (DEVIATION 2026- O0025)

Jun 2026 Deviation 2026-O0025 Jun 2026

252.240-7997 NIST SP 800-171 DoD Assessment Requirements. (DEVIATION 2026- O0025)

Feb 2026 Deviation 2026-O0025 Feb 2026

252.244-7999 Subcontracts for Commercial Products or Commercial Services.

(DEVIATION 2026-O0015)

Feb 2026 Deviation 2026-O0015 Jan 2026

252.247-7023 Transportation of Supplies by Sea. Oct 2024

FAR Clauses Incorporated by Full Text

52.219-28 Postaward Small Business Program Rerepresentation. (Deviation 2026-O0038) (Feb 2026)

POSTAWARD SMALL BUSINESS PROGRAM REREPRESENTATION (FEB 2026) (DEVIATION 2026-O0038)

(a) . As used in this clause-Definitions

Long-term contract means a contract of more than five years in duration, including options. However, the term does not include contracts that exceed five years in duration because the period of performance has been extended for a cumulative period not to exceed six months under the clause at 52.217-8, Option to Extend Services, or other appropriate authority.

Small business concern-

(1) Means a concern, including its affiliates, that is independently owned and operated, not dominant in its field of operation, and qualified as a small business under the criteria in 13 CFR part 121 and the size standard in paragraph (c) of this clause.

(2) , as used in this definition, means business concerns, one of whom directly or indirectly controls or has the power to control the others, Affiliates or a third party or parties control or have the power to control the others. In determining whether affiliation exists, consideration is given to all appropriate factors including common ownership, common management, and contractual relationships. SBA determines affiliation based on the factors set forth at 13 CFR 121.103.

(b) If the Contractor represented that it was a small business concern, a small disadvantaged business concern, or a joint venture that was any of the small business concerns identified in 19.000(a)(3) prior to award of this contract, the Contractor shall rerepresent its size and socioeconomic status according to paragraph (e) of this clause or, if applicable, paragraph (g) of this clause, upon occurrence of any of the following:

(1) Within 30 days after execution of a novation agreement or within 30 days after modification of the contract to include this clause, if the novation agreement was executed prior to inclusion of this clause in the contract.

(2) Within 30 days after a merger or acquisition that does not require a novation or within 30 days after modification of the contract to include this clause, if the merger or acquisition occurred prior to inclusion of this clause in the contract.

(3) For long-term contracts-

(i) Within 60 to 120 days prior to the end of the fifth year of the contract; and

(ii) Within 60 to 120 days prior to the date specified in the contract for exercising any option thereafter.

(c) The Contractor shall rerepresent its size status in accordance with the size standard in effect at the time of this rerepresentation that corresponds to the North American Industry Classification System (NAICS) code(s) assigned to this contract. The small business size standard corresponding to this NAICS code(s) can be found at https://www.sba.gov/document/support--table-size-standards.

(d) The small business size standard for a Contractor providing an end item that it does not manufacture, process, or produce itself, for a contract other than a construction or service contract, is 500 employees, or 150 employees for information technology value-added resellers under NAICS code 541519, if the acquisition-

(1) Was set aside for small business and has a value above the simplified acquisition threshold;

(2) Used the HUBZone price evaluation preference regardless of dollar value, unless the Contractor waived the price evaluation preference; or

(3) Was an 8(a), HUBZone, service-disabled veteran-owned, economically disadvantaged women-owned, or women-owned small business set-aside or sole-source award regardless of dollar value.

(e) Except as provided in paragraph (g) of this clause, the Contractor shall make the representation(s) required by paragraph (b) of this clause by validating or updating all its representations in the Representations and Certifications section of the System for Award Management (SAM) and its other data in SAM, as necessary, to ensure that they reflect the Contractor's current status. The Contractor shall notify the contracting officer in writing within the timeframes specified in paragraph (b) of this clause, that the data have been validated or updated, and provide the date of the validation or update.

(f) If the Contractor represented that it was other than a small business concern prior to award of this contract, the Contractor may, but is not required to, take the actions required by paragraphs (e) or (g) of this clause.

(g) If the Contractor does not have representations and certifications in SAM, or does not have a representation in SAM for the NAICS code applicable to this contract, the Contractor is required to complete the following rerepresentation and submit it to the contracting office, along with the contract number and the date on which the rerepresentation was completed:

(1) The Contractor represents that it is, is not a small business concern under NAICS Code assigned to contract number.____ ____

(2) [ .] The Contractor represents Complete only if the Contractor represented itself as a small business concern in paragraph (g)(1) of this clause that it is, is not, a small disadvantaged business concern as defined in .13 CFR 124.1001

(3) . The Contractor represents that it is, is not a Women-owned small business (WOSB) joint venture eligible under the WOSB Program joint venture that complies with the requirements of 13 CFR 127.506(a) through (c). [ The Contractor shall enter the name and unique entity ____ identifier of each party to the joint venture: __.]

(4) . The Contractor represents that it is, is not a joint Economically disadvantaged women-owned small business (EDWOSB) joint venture venture that complies with the requirements of 13 CFR 127.506(a) through (c). [ The Contractor shall enter the name and unique entity identifier ____ of each party to the joint venture: __ .]

(5) . The Contractor represents that it Service-disabled veteran-owned small business (SDVOSB) joint venture eligible under the SDVOSB Program is, is not an SDVOSB joint venture eligible under the SDVOSB Program that complies with the requirements of 13 CFR 128.402. [ The ____ Contractor shall enter the name and unique entity identifier of each party to the joint venture: __.]

(6) [ ] The HUBZone joint venture eligible under the HUBZone Program. Complete only if the offeror is a HUBZone small business concern.

offeror represents, as part of its offer, that It is, is not a HUBZone joint venture that complies with the requirements of 13 CFR 126.616(a) through (c). [ The Contractor shall enter the name and unique entity identifier of each party to the joint venture: .] Each HUBZone small business ____ concern participating in the HUBZone joint venture must be certified as a HUBZone concern. [ Contractor to sign and date and insert authorized ____ signer's name and title.]

(End of clause)

52.252-2 Clauses Incorporated by Reference. (Tailored) (Feb 1998)

Clauses Incorporated By Reference (Feb 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52 https://www.acq.osd.mil/dpap/dars/dfars_far_overhaul_class_deviations.html

(End of clause)

52.252-6 Authorized Deviations in Clauses. (Tailored) (Nov 2020)

Authorized Deviations in Clauses (Nov 2020)

(a) The use in this solicitation or contract of any clause with an authorized deviation is Federal Acquisition Regulation (48 CFR Chapter 1) indicated by the addition of "(DEVIATION)" after the date of the clause.

(b) The use in this solicitation or contract of any clause with an authorized Defense Federal Acquisition Regulation (48 CFR Chapter 2) deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation.

(End of clause)

DFARS Clauses Incorporated by Full Text

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

ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023)

N0016726Q1153 https://www.acquisition.gov/far-overhaul/far-part-deviation-guide/far-overhaul-part-52 https://www.acq.osd.mil/dpap/dars/dfars_far_overhaul_class_deviations.html

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