Solicitation - N0018926QD231.pdf

WOMEN-OWNED SMALL

BUSINESS (WOSB)

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

1. REQUISITION NUMBER PAGE 1 OF

2. CONTRACT NUMBER 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODE17a. CONTRACTOR/

OFFEROR

CODE

FACILITY

CODE

CODE

TELEPHONE NUMBER

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

OFFER

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

BELOW IS CHECKED

REQUEST

FOR QUOTE

(RFQ)

INVITATION

FOR BID

(IFB)

REQUEST

FOR

PROPOSAL

(RFP)

SEE ADDENDUM

19.

ITEM NUMBER

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

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

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Government Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH

AND DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND

ON ANY ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS

SPECIFIED

29. AWARD OF CONTRACT: REFERENCE OFFER

DATED . . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

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

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 11/2021)

Prescribed by GSA - FAR (48 CFR) 53.212

10. THIS ACQUISITION IS UNRESTRICTED OR

NORTH AMERICAN

INDUSTRY CLASSIFICATION

STANDARD (NAICS):

SIZE STANDARD:

13a. THIS CONTRACT IS A

RATED ORDER UNDER

THE DEFENSE PRIORITIES

AND ALLOCATIONS

SYSTEM - DPAS (15 CFR 700)

SET ASIDE: % FOR:

11. DELIVERY FOR FREE ON

BOARD (FOB) DESTINATION

UNLESS BLOCK IS MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

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

AND 52.212-5 ARE ATTACHED. ADDENDA

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

8(A)

ECONOMICALLY

DISADVANTAGED

WOMEN-OWNED SMALL

BUSINESS (EDWOSB)

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

(SDVOSB)

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

NOTE: OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30.

Solicitation/Contract Form Continuation

Virtual Marine: Night Vision and Chart Plotting

N0018926QD231

Continuation of Supplies or Services and Prices/Costs

Additional Information/Notes

Item Supplies/Service Quantity Unit Unit Price Amount

Software License: Integrate a simulated night vision capability into the existing VR training environment to enhance low-light operational training scenarios.

Pricing Arrangement: Firm Fixed Price

1 Each

Software/ Hardware: Integrate a functional chart plotter capability into each simulator, aligned with operational systems currently used by NSW, to enhance navigation and mission realism.

Pricing Arrangement: Firm Fixed Price

2 Each

0003 New Database: Additional databases for navigation with Chart Plotter

Pricing Arrangement: Firm Fixed Price

2 Each

0004 New Scenarios: New Scenario package for new Database/ Chart Plotter

Pricing Arrangement: Firm Fixed Price

5 Each

0005 Scoping and Installation: Technical Support

Pricing Arrangement: Firm Fixed Price

1 Each

Continuation of Description Performance Work Statement (PWS)

Special Boat Training Command

Coastal Craft Simulator Upgrades: Night Vision and Chart Plotter Integration

1.0 BACKGROUND

The Special Boat Training Command (SBTC) command utilizes advanced Virtual Reality (VR) Small Boat Simulators to provide high-fidelity tactical, navigational, and operational training to Partner Force Students. SBTC currently operates two (2) deployed VR-Based Small Boat Simulators designed and manufactured by the Original Equipment Manufacturer (OEM), Virtual Marine. To meet expanding operational requirements and ensure students are prepared for complex, low-light environments, SBTC requires the integration of software-driven Night Vision capabilities and hardware-driven tactical Chart Plotter interfaces into these existing simulator units.

2.0 OBJECTIVE

The objective of this effort is to acquire comprehensive software, hardware-interfacing, database, and scenario integration package from Virtual Marine. This contract shall deliver and integrate simulated Night Vision emulation and a functional, physical Furuno Chart Plotter interface into both existing VR simulators, accompanied by the database expansion, custom scenario packages, and on-site installation support necessary to make the updated systems fully operational.

3.0 SCOPE

The Contractor shall provide all software licensing, system engineering, database development, scenario programming, physical hardware interface design, and on-site technical support required to upgrade the two (2) existing VR-Based Small Boat Simulators. The scope includes:

Night Vision (NVG) Emulation: Software integration of a monochromatic green/black low-light simulator overlay within the VR headset environment.

Chart Plotter Integration: Interface engineering to bridge the simulator telemetry with client-supplied physical Furuno radar and navigation hardware.

Database & Scenario Expansion: Custom databases and training scenarios explicitly tailored to validate and train operators on the integrated systems.

On-Site Technical Integration: Scoping, deployment, testing, calibration, and user-guidance delivery at SBTC, Stennis Space Center, MS.

4.0 REQUIREMENTS

4.1. Task 1: Night Vision Integration for VR-Based Small Boat Simulators

The Contractor shall develop and integrate a simulated night vision capability into the existing VR training environment to enhance low-light operational training.

- 4.1.1. Night Vision Visual Mode: Develop and implement a night vision visual mode directly within the simulator's VR headset rendering pipeline.

- 4.1.2. Monochromatic Overlay: Apply a monochromatic green/black visual overlay to replicate the general appearance of operational night vision devices.

- 4.1.3. Lighting and Contrast Tuning: Program and adjust scene lighting, contrast, and brightness parameters within the simulation engine to accurately mimic low-light and nighttime operational conditions.

- 4.1.4. Tactical Controls: Program and enable user-controlled activation/deactivation (toggle) of the night vision mode within active training scenarios.

- 4.1.5. Hardware Compatibility: Ensure full compatibility and seamless rendering performance across the existing simulator hardware and VR headsets currently deployed at NSW.

- 4.1.6. Technical Scope Boundary: The integration is strictly software-driven within the existing VR headset environment (visual emulation only); it does not require physical hardware-based Night Vision Goggles (NVGs), nor does it support infrared (IR) spectrum simulation or dynamic depth-based illumination.

4.2. Task 2: Chart Plotter Hardware and Software Integration

The Contractor shall develop, test, and integrate a functional chart plotter capability into each simulator, aligned with real-world Furuno systems utilized by SBTC, to enhance navigational realism.

- 4.2.1. Software Interface Development: Develop and compile the necessary software interfaces within the "MissionQuest" simulation engine to output live telemetry.

- 4.2.2. Hardware-to-Software Interfacing: Design, fabricate, and implement the hardware and software cabling/routing interfaces required to feed real-time simulator telemetry to external navigation units.

- 4.2.3. Furuno Hardware Integration: Interface the simulation output with physical Furuno hardware systems to replicate authentic, real-world maritime navigation workflows.

- 4.2.4. Telemetry Synchronization: Enable real-time, low-latency interaction between vessel movement inside the simulation (position, heading, speed) and the physical Furuno chart plotter display.

- 4.2.5. Dual Deployment: Deploy and configure the finalized dual-system chart plotter interface onto both existing SBTC simulators.

4.3. Task 3: Database and Scenario Package Development

The Contractor shall design and deliver expanded databases and tactical training environments to support the newly integrated systems.

- 4.3.1. Database Engineering: Develop two (2) new geographical/navigational databases optimized for use with the integrated physical Chart Plotter.

- 4.3.2. Scenario Development: Design and deliver a package of five (5) new, distinct tactical training scenarios (focusing on route planning, navigation, approach, and mission execution) that leverage the new databases and require active use of the Chart Plotter and Night Vision modes.

4.4. Task 4: On-Site Scoping, Technical Support, and Installation

The Contractor shall execute one (1) on-site technical support trip to SBTC facilities at Stennis Space Center, MS, to complete physical integration, calibration, and testing.

- 4.4.1. Physical Integration: Mount, wire, and physically integrate the required interface components to link the client-supplied Furuno units to both simulators.

- 4.4.2. Calibration & Validation: Perform comprehensive on-site testing and calibration to ensure telemetry accuracy and zero-latency display synchronization.

- 4.4.3. System Acceptance Testing: Conduct joint system validation with SBTC staff to confirm that all Night Vision and Chart Plotter functionalities meet operational stability and usability standards within the training environment.

5.0 DELIVERABLES

Deliverable Item PWS Ref

Delivery Timeline

Updated Simulator Software Package (Integrated Night Vision Visual Mode & Configuration Settings)

4.1

Delivery to SBTC upon completion of software phase ( milestone)Readiness to Ship

User Guidance Documentation Brief manual detailing NVG activation, options, and limitations)

4.1 Accompanying Software Delivery

Completed Chart Plotter Software/Hardware Interfaces Cabling, drivers, and integration interfaces for 2 units)

4.2 Delivered and installed during on-site integration trip

New Navigation Databases (Qty: 2) Configured for simulator and Chart Plotter compatibility)

4.3.1

Pre-loaded on upgraded software build

Custom Simulator Scenario Package (Qty: 5) Incorporating databases, NVG, and Furuno inputs

4.3.2 Pre-loaded on upgraded software build

On-Site Installation, Calibration, & Acceptance Test Report 4.4 Within ten (10) business days following completion of the on-site Stennis, MS integration trip

6.0 CONTRACTOR TRAVEL

Travel is authorized and required under this contract to support on-site system integration, physical hardware calibration, and validation testing at SBTC facilities.

Destination: SBTC, Stennis Space Center, MS.

Trips: The contract includes one (1) technical scoping and installation trip for qualified Virtual Marine engineering and technical support staff.

Compliance: All contractor travel shall be coordinated in advance with the SBTC Technical Point of Contact (TPOC) to secure necessary base and facility access credentials.

7.0 SAFETY

The Contractor shall comply with all local facility, hardware, and safety regulations while executing tasks on-site at SBTC. Standard safety protocols for working on active electrical/computing equipment, VR systems, and simulator platforms shall be strictly observed during installation and calibration procedures.

8.0 GOVERNMENT FURNISHED PROPERTY/EQUIPMENT/INFORMATION (GFP/GFE/GFI)

To facilitate the timely development and integration of these simulator upgrades, the Government will provide the following:

8.1. Simulator Access: Adequate, scheduled window of physical access to the two (2) deployed Virtual Marine VR-Based Small Boat Simulators at SBTC.

8.2. Furuno Hardware (GFE): Client-supplied Furuno radar/navigation units required by the Contractor for hardware interface testing, validation, and final on-site installation.

8.3. Charts and Technical Documentation (GFI): Required Electronic Navigation Charts (ENCs), along with proprietary physical/technical interface protocols or user manuals for the SBTC-configured Furuno systems, unless specifically authorized for contractor sourcing under optional pricing.

9.0 QUALITY CONTROL

The Contractor shall conduct rigorous internal software and hardware interface testing before shipping components or deploying code to the active SBTC simulator platforms. The Contractor's quality assurance program shall ensure:

Zero software regressions or degradation of performance to the core "MissionQuest" simulation software.

Proper frame rates are maintained inside the VR headsets when the monochromatic Night Vision overlay is actively toggled.

Electrical and telemetry signals between the simulator computer and the Furuno units conform to standard operating specifications of both respective systems.

10.0 PERIOD OF PERFORMANCE

The Period of Performance (PoP) shall commence immediately upon contract award and extend through system deployment, on-site calibration, and final government acceptance (160 days after award).

Milestone 1 (Contract Award): Kick-off, physical interface design, database design, and initial software development.

Milestone 2 (Readiness to Ship / Install): Final software compilation, database integration, scenario loading, physical cabling fabrication, and mobilization of technical team to SBTC for physical installation All work, including final on-site acceptance testing, shall be completed within the schedule mutually agreed upon during contract kick-off. Payment terms shall be NET 30 days.

Requirements The SBTC intends to procure software integration, licensing, and technical support

Continuation of Packaging and Marking

Continuation of Inspection and Acceptance

Overall Contract Inspection/Acceptance Locations

Inspection and Acceptance Location

Both Destination Instructions: Special Boat Training Command 2606 Lower Gainesville Road Stennis Space Center, MS. 39529

DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r. bawsel.ctr@socom.mil Telephone: 228-813-4050 (+ext 34323)

Inspection and Acceptance Location

Both Destination Instructions: Special Boat Training Command 2606 Lower Gainesville Road Stennis Space Center, MS. 39529

DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r. bawsel.ctr@socom.mil Telephone: 228-813-4050 (+ext 34323)

Inspection and Acceptance Location

Both Destination Instructions: Special Boat Training Command 2606 Lower Gainesville Road Stennis Space Center, MS. 39529

DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r. bawsel.ctr@socom.mil Telephone: 228-813-4050 (+ext 34323)

Inspection and Acceptance Location

Both Destination Instructions: Special Boat Training Command 2606 Lower Gainesville Road Stennis Space Center, MS. 39529

DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r. bawsel.ctr@socom.mil Telephone: 228-813-4050 (+ext 34323)

Inspection and Acceptance Location

Both Destination Instructions: Special Boat Training Command 2606 Lower Gainesville Road Stennis Space Center, MS. 39529

DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r. bawsel.ctr@socom.mil Telephone: 228-813-4050 (+ext 34323)

Continuation of Deliveries or Performance

Overall Contract Delivery Period

Contractor Destination

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

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

1 Each Ship To DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS

SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r.bawsel.ctr@socom.mil Telephone: 228-813-4323

FoB Details Contractor Destination

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

2 Each Ship To DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS

SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r.bawsel.ctr@socom.mil Telephone: 228-813-4323

FoB Details Contractor Destination

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

2 Each Ship To DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS

SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r.bawsel.ctr@socom.mil Telephone: 228-813-4323

FoB Details Contractor Destination

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

5 Each Ship To DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS

SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r.bawsel.ctr@socom.mil Telephone: 228-813-4323

FoB Details Contractor Destination

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

1 Each Ship To DoDAAC: N70076 CountryCode: USA

NAVSCIATTS CIV SUPPORT ACTY

2606 LOWER GAINSVILLE RD, STENNIS

SPACE CENTER MS 39529-5000

STENNIS SPACE CENTER, MS 39529-5000

UNITED STATES

Luke Bawsel, TPOC Email: luke.r.bawsel.ctr@socom.mil Telephone: 228-813-4323

FoB Details Contractor Destination

Continuation of Accounting and Appropriation Data

Contract Clauses

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

52.204-13 System for Award Management-Maintenance. (Deviation 2026-O0038) Feb 2026 52.203-19 Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements. Jan 2017 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.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-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.212-4 Terms and Conditions-Commercial Products and Commercial Services. (Deviation 2026- O0038)

Feb 2026

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

252.223-7008 Prohibition of Hexavalent Chromium. Jan 2023 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-7015 Notice of Authorized Disclosure of Information for Litigation Support. Jan 2023 252.232-7003 Electronic Submission of Payment Requests and Receiving Reports. Dec 2018 252.232-7010 Levies on Contract Payments. Dec 2006 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)

DFARS Clauses Incorporated by Full Text

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

WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)

(a) As used in this clause- Definitions.

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

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

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

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

(b) The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as 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 WAWF payment instructions.

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

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

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

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

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

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

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

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

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

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

WAWF 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) ____

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

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

(4) The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in 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.

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

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

(End of clause)

Addendum to 52.212-4, Contract Terms and Conditions - Commercial Products and Commercial Services

Contract Terms and Conditions Required To Implement Statutes or Executive Orders — Commercial Products and Commercial Services

Addendum to Contract Clauses

Contract Clauses

FAR Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

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

52.209-10 Prohibition on Contracting With Inverted Domestic Corporations. (Deviation 2026- O0038)

Feb 2026

52.232-39 Unenforceability of Unauthorized Obligations. Jun 2013

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.222-3 Convict Labor. (Deviation 2026-O0038) Feb 2026 52.240-91 Security Prohibitions and Exclusions. (Deviation 2026-O0038) Feb 2026

52.244-6 Subcontracts for Commercial Products and Commercial Services. (Deviation 2026- O0038)

Apr 2026

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

Apr 2026

DFARS Clauses Incorporated by Reference

Number Title Effective Date

Alternate/ Deviation

Variation Effective Date

252.223-7006 Prohibition on Storage, Treatment, and Disposal of Toxic or Hazardous Materials.

Sep 2014

252.225-7012 Preference for Certain Domestic Commodities. Apr 2022 252.225-7001 Buy American and Balance of Payments Program. Feb 2024 252.225-7002 Qualifying Country Sources as Subcontractors. Mar 2022

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

Jan 2023

252.211-7008 Use of Government-Assigned Serial Numbers. Sep 2010 252.225-7048 Export-Controlled Items. Jun 2013

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

Aug 2024 Deviation 2024-O0014 Aug 2024

252.244-7999 Subcontracts for Commercial Products or Commercial Services.

(DEVIATION 2026-O0015)

Feb 2026 Deviation 2026-O0015 Jan 2026

FAR Clauses Incorporated by Full Text

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 and 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 Federal Acquisition Regulation (48 CFR Chapter 1) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the clause.

(b) The use in this solicitation or contract of any (48 CFR ) clause with an authorized deviation is indicated by the addition of DFARS Chapter 1 "(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)

(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 deliverable attachment for exhibit line item number (fill in) , Unique Item Identifier Report for Embedded ____ Items, Contract Data Requirements List, DD Form 1423.

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

(End of clause)

Additional Regulation or Supplemental Clauses Incorporated by Full Text

203.1106-1(3-18) SUPTXT 203.1106-1 (3-18) NAVY USE OF ABILITYONE SUPPORT

CONTRACTOR - RELEASE OF OFFEROR INFORMATION

(Jan 2024)

NAVSUP FLC Norfolk may utilize contractor support through the AbilityOne Program, as needed, to perform contract closeout functions for this acquisition. Information, including business sensitive/confidential or proprietary data, that the offeror provides to the Government or information already in the possession of…