1449 Solicitation.pdf

SEE ADDENDUM

(No Collect Calls)

N0017824RC619 20-Jun-2024

b. TELEPHONE NUMBER

540-500-9320

8. OFFER DUE DATE/LOCAL TIME

12:00 PM 25 Jun 2024

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

N001789. ISSUED BY

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

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

DREW NICKELS

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

0 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

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

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

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

NSWCDD 1

DREW NICKELS/0232 17632 DAHLGREN ROAD

DAHLGREN VA 22448

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS AX

13b. RATING

DX-A7

CODE15. DELIVER TO CODE N00178 16. ADMINISTERED BY

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

NAVAL SURFACE WARFARE CENTER

RECEIVING OFFICER

6220 TISDALE ROAD BLDG 125 STE 159

DAHLGREN VA 22448-5114

TEL: (540) 653-7306 FAX:

FAX:

TEL: 540-500-9320 SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$47,000,000

NAICS:

513210

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF63

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

N0017824RC619

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Lot

GS-I178T64GOS-LIN-IA

FFP

INTEGRITY-178 tuMP w/GuestOS support for an INTEL processor. Product Line Development License. A Royalty–Free Site-Wide license to use INTEGRITY-178 tuMP 64 Bit for a specific INTEL processor, at a single site, for the development and support of the NSWC TBD Product Line.

1 Lot = Qty. 2.

In accordance with the attached Statement of Work.

FOB: Destination

MFR PART NR: GS-I178T64GOS-LIN-IA

PSC CD: DA10

NET AMT

0002 1 Lot

@GS-I178T64GOS-LIN-IA

FFP

Annual technical support and software maintenance for CLIN 0001.

In accordance with the attached Statement of Work.

FOB: Destination

MFR PART NR: @GS-I178T64GOS-LIN-IA

PSC CD: DA01

0003 1 Lot

GS-I178T-IPF64-LIN-IA

FFP

IPFLITE Product Line Development License for INTEGRITY-178 tuMP/INTEL 64 Bit. A Royalty-free Site-Wide license to use IPFLITE for INTEGRITY-178 tuMP (a safety-critical UDP/IP network stack with Multicast and TFTP support) operating on for a specific INTEL processor, at a single site, for the development and support of the NSWC TBD Product Line.

1 Lot = Qty.2.

In accordance with the attached Statement of Work.

FOB: Destination

MFR PART NR: GS-I178T-IPF64-LIN-IA

0004 1 Lot

@GS-I178T-IPF64-LIN-IA

FFP

Annual technical support and software maintenance for CLIN 0003.

In accordance with the attached Statement of Work.

FOB: Destination

MFR PART NR: @GS-I178T-IPF64-LIN-IA

0005 1 Lot

G-MC-X86-IR-PRM

FFP

MULTI Software Development Environment for INTEGRITY-178 Intel targets.

Includes Intel x86 C/C++ cross compiler, RTserv remote debug server (for serial/ethernet debugging) and MPserv remote debug server (for JTAG/BDM Probe debugging).

PC Linux host floating license.

1 Lot = Qty. 4.

In accordance with the attached Statement of Work.

FOB: Destination

MFR PART NR: G-MC-X86-IR-PRM

0006 1 Lot

@G-MC-X86-IR-PRM

FFP

Annual technical support and software maintenance for CLIN 0005.

In accordance with the attached Statement of Work.

FOB: Destination

MFR PART NR: @G-MC-X86-IR-PRM

0007 1 Lot

GS-3TRN-SRV-UNS

FFP

Green Hills Software’s On-site Training Services to be provided at customer location. Three (3) day Training course includes training for the INTEGRITY-178 tuMP RTOS and MULTI Software Development. Includes all materials for up to 12 students. Includes instructor travel and living expenses.

1 Lot = Qty. 1.

In accordance with the attached Statement of Work.

FOB: Destination

MFR PART NR: GS-3TRN-SRV-UNS

PSC CD: U099

0008 1 Each GH Prototype Software Development Kit

FFP

Consists of Dual Kontron Tiger Lake Computers and Green Hills Software GS-

I178T64-BSP-IA

The Kontron Computer will consist of COM Express Computer on Module (COMe-cTL6) containing a 1.8 Ghz Intel Tiger Lake Core i7-1185GRE with 16 GB DDR4, 32 GB DDR4 SODIMM, Carrier Board, Power Supply, Keyboard and Mouse. The software for the Kontron Computer will consist of Green Hills Software’s GS-I178T64-BSP-IA Board Support Package (BSP) for the INTEGRITY-178 tuMP 64-Bit OS operating on Kontron Computer COMe-cTL6.

Includes BSP source code.

The INTEGRITY-178 tuMP Board Support Packages (BSP) for the Kontron Tiger Lake Computer will include support for the following hardware functionality:

• Onboard Xeon SOC Ethernet device driver

• Serial/UART device driver

• USB Mouse and Keyboard device drivers Customer has the No-Fee option to convert the Prototype Software Development Kit for the Kontron computer to a Prototype Software Development Kit for Tyan’s Tempest CX S7136 Processor Board (S7136GM2NRE-2T) that contains a Dual Intel Xeon 4th generation scalable processors with support for up to 32 cores on each 4th Gen Xeon multicore processor. Customer would be responsible for providing The Tempest System. A BSP for the Tempest CX S7136 Processor Board BSP would be included (Source Code included) with support for the same hardware functionality as for the Kontron computer:

• Onboard Xeon SOC Ethernet device driver

• Serial/UART device driver

• USB Mouse and Keyboard device drivers In accordance with the attached Statement of Work.

NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

FOB: Destination MFR PART NR: GH Prototype Software Development Kit

PSC CD: 7H20

0009 1 Lot

GS-I178T64-BSP-IA

FFP

Green Hills Software’s Board Support Package (BSP) for INTEGRITY-178 tuMP 64-Bit OS operating on Trenton Systems’ BAM8300 Processor Board containing Dual Intel Xeon 4th generation scalable processors with support for up to 32 cores on each 4th Gen Xeon multicore processor. Includes BSP source code.

The INTEGRITY-178 tuMP Board Support Packages (BSP) for the TBD platform containing an Intel Xeon Scalable processor will include support for the following hardware functionality:

• Onboard Xeon SOC Ethernet device driver

• Serial/UART device driver

• USB Mouse and Keyboard device drivers In accordance with the attached Statement of Work.

FOB: Destination

MFR PART NR: GS-I178T64-BSP-IA

Section C - Descriptions and Specifications

STATEMENT OF WORK

1.0 BACKGROUND

The Naval Surface Warfare Center, Dahlgren Division (NSWCDD) requires consulting and support services for INTEGRITY-178 tuMP RTOS Software, manufactured by Green Hills Software.

2.0 APPLICABLE DOCUMENTS

2.1 Original Equipment Manufacturer (OEM) Specifications.

3.0 REQUIREMENTS

3.1 The Contractor shall provide a quantity of two (2) each INTEGRITY-178 tuMP with guestOS support for INTEL processor Product Line Development License, part number GS- I178T64GOS-LIN-IA, and IPFLITE Product Line Development License for INTEGRITY-178 tuMP, part number GS-I178T-IPF64-LIN-IA, and a quantity of four (4) each Multi Software Development Environment for INTEGRITY-178 Intel targets, part number G-MC-X86-IR-PRM.

3.2 The Contractor shall provide one year of technical support for the INTEGRITY-178 tuMP license to include the following:

3.2.1 The Contractor shall provide technical support to assist in installation of INTEGRITY- 178 tuMP on applicable hardware.

3.2.2 The Contractor shall support technical questions for the product via phone calls and email as needed within the 12-month contract period.

3.3 The Contractor shall provide one year of technical support for the IPFLITE Product Line Development License to include the following:

3.3.1 The Contractor shall provide technical support to assist in installation of IPFLITE Product Line Development License on applicable hardware.

3.3.2 The Contractor shall support technical questions for the product via phone calls and email as needed within the 12-month contract period.

3.4 The Contractor shall provide one year of technical support for the MULTI Software Development Environment to include the following:

3.4.1 The Contractor shall provide technical support to assist in installation of MULTI Software Development Environment on applicable hardware.

3.4.2 The Contractor shall support technical questions for the product via phone calls and email as needed within the 12-month contract period.

3.5 The Contractor shall provide Training for INTEGRITY-178 tuMP in the following areas:

3.5.1 MULTI overview and components.

3.5.2 INTEGRITY-178 overview, concepts, and device drivers.

3.6 The Contractor shall provide a prototype software development kit for a Dual Kontron Tiger Lake.

3.6.1 The Kontron Computer shall consist of COM Express computer on Module containing a

1.8 GHz Intel Tiger Lake Core i7-1185GRE with 16 GB DDR 4, 32 GB DDR4 SODIMM, Carrier Board, Power Supply, Keyboard and Mouse.

3.7 The Contractor shall provide a board support package (BSP), part number GS-I178T64- BSP-IA, for INTEGRITY-178 tuMP 64-bit operating system for the Trenton Systems BAM8300 Processor Board containing Dual Intel Xeon 4th generation scalable processors.

3.8 The Contractor shall coordinate with the TPOC identified below to complete this work.

4.0 GOVERNMENT-FURNISHED PROPERTY/MATERIAL/INFORMATION

(GFP/GFM/GFI)

4.1 The Government will provide access to the NSWCDD and the required areas with escorts to complete this work.

4.2 The Government shall provide access via local system administrators to the INTEGRITY-178 tuMP RTOS software.

5.0 SECURITY

5.1 All work under this SOW is Unclassified with escorts provided to the secure Open Storage Secret (OSS) facility.

6.0 TRAVEL

The Contractor will be required to travel in performance of this contract. The number of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements and shall be coordinated with the technical point of contact. All travel shall be conducted in accordance with the Federal Travel Regulations (FTR). The following travel is anticipated: one (1) personnel for three (3) days to the NSWCDD located in Dahlgren, Virginia.

7.0 TECHNICAL POINT OF CONTACT

Provided upon award.

CLAUSES INCORPORATED BY FULL TEXT

C-212-W001 CONTRACT TERMS AND CONDITIONS - COMMERCIAL ITEMS ADDENDUM TO 52.212-4

(NAVSEA) (OCT 2018)

(o) Warranty -- append the following to paragraph (o):

The contractor shall extend to the Government the full coverage of any standard commercial warranty normally offered in a similar commercial sale at no additional cost to the Government. Acceptance of the standard commercial warranty does not waive the Government's rights under the "Inspection" clause nor does it limit the

Government's rights with regard to the other terms and conditions of this contract. In the event of a conflict, the terms and conditions of the contract shall take precedence over the standard commercial warranty. The standard commercial warranty period shall begin upon final acceptance of the applicable material and/or services listed in the Schedule.

The contractor shall provide a copy of its standard commercial warranty (if applicable) with its offer. The warranty covers a period of months. (Offeror is to insert number.)

The following information is hereby appended to the clause:

(w) Data Rights. The Government shall have data rights to all data generated under this contract or order in accordance with DFARS 252.227-7015.

(x) Ordering. The agency authorized to place delivery orders against this contract is: [Add ordering activity name].

Delivery orders will be placed against this contract, by the Government, using the SF 1449.

(End of text)

C-212-W002 COMMERCIAL SUPPLIER AGREEMENTS (NAVSEA) (MAR 2019)

(a) Commercial Supplier Agreement means End User License Agreement (EULA), Terms of Service (TOS), or similar legal instrument or agreement.

(b) Any Commercial Supplier Agreement must be provided in full text as part of a quote or offer without hyperlinks.

(c) The contract/order Schedule and Federal Acquisition Regulation (FAR) 52.212-4, Contract Terms and Conditions—Commercial Items, shall take precedence over any conflicting provisions in a Commercial Supplier Agreement.

(d) If any requirement in the Commercial Supplier Agreement conflicts with Federal law or regulations (see FAR 12.212(a)), the following shall apply:

(i) Any such requirement is unenforceable against the Government.

(ii) Neither the Government nor any Government authorized end user shall be deemed to have agreed to such requirement by virtue of it appearing in the Commercial Supplier Agreement. If the Commercial Supplier Agreement is invoked through an “I agree” click box or other comparable mechanism (e.g., “click-wrap” or “browse-wrap” agreements), execution does not bind the Government or any Government authorized end user to such requirement.

(iii) Any such requirement is deemed to be stricken from the Commercial Supplier Agreement.

(e) Automatic renewals. License Agreements will expire at end of the term identified in the Purchase Order/Contract. Automatic renewals are not permitted and any such provision is void.

(f) Changes to the Commercial Supplier Agreement. Unilateral changes of the Commercial Supplier Agreement are impermissible and any requirement authorizing such changes is unenforceable. Changes must be in writing and executed by both parties to be effective.

(g) Third Part License (Embedded Software).

(i) The Contractor agrees that it has obtained all necessary licenses for the Government for any third party materials (including without limitation all Open Source licenses) provided within the product.

(ii) Contractor agrees that it complies with and shall continue to comply with all of its obligations under Third Party Licenses (including without limitation all Open Source licenses) associated with any third party materials provided within each product.

(iii) To the extent that the Government’s use of the software products licensed herein is in compliance with the Contractor’s Commercial Supplier Agreement, the Government’s use will also be in compliance with any Third Party Licenses.

(h) Audits. In lieu of any audit provisions in the Commercial Supplier Agreement, the Government agrees that, no more than once every twelve (12) months or within a reasonable time after a transfer, the Contractor shall, upon reasonable notice, have the right to require that the Government conduct an internal audit to ascertain and verify the number of licenses in use and to verify that the Government’s use of the product is in conformity with this Agreement. The Government is not required to use any tools provided by the Contractor to conduct the audit and shall not be required to pay for any tools provided by the Contractor to conduct the audit. The results of any such audit shall be kept confidential.

If verification discloses that the Government’s use is not in conformity with this Agreement, the Government agrees to resolve any noncompliance by either removing or correcting the unlicensed installation and use of the software identified by the audit as not in conformity with this Agreement.

(i) Confidentiality. Commercial Supplier Agreements’ terms and the final contract pricing may not be deemed confidential. Other marked confidential information will be appropriately guarded.

(j) Assignment. The Government shall have the right, without the prior written consent of the Contractor or its authorized resellers, to assign, reassign, or transfer software licenses among Government employees or the Government’s rights in the Contractor’s product to any governmental organization that is managed, operated, or controlled by the Government.

Such authorization includes sublicensing, and assignment or transfer among or between authorized users. In the event authorized users are reorganized or restructured such that their responsibilities and operations are transferred to another government agency, the agency shall have the right to assign the affected program licenses to a successor agency. The licensed agency and the successor agency agree to be bound to the Commercial Supplier Agreement as modified. The transferee shall be bound by the license metrics and limitations in this license. Government shall complete any documentation required by the Contractor to facilitate the transfer of this license, and continuation of support shall be the responsibility of the transferee.

For the avoidance of doubt, any assignment or transfer of licenses of the Contractor’s products is also subject to all other terms of the Commercial Supplier Agreement, as well as the Contractor’s policies governing product dependencies and version compatibility. Reassignment does not require that the license be under maintenance or support in order to execute a transfer.

(k) Litigation. Any requirement insisting that the commercial supplier or licensor control any litigation arising from the government’s use of the contractor’s supplies or services is deleted and unenforceable.

(l) Equitable Remedies. Equitable remedies, injunctive relief, and binding arbitration requirements shall not be enforced unless explicitly authorized by agency guidance or statute.

(m) Venue. Any claim or dispute shall be resolved under the Contract Disputes Act and FAR 52.233-1. The forum for resolution of disputes and applicable statutes of limitation shall be governed by federal law.

(n) Applicable law. In accordance with FAR 52.233-4, United States law shall apply to resolve any claim of breach of this contract and such actions shall be handled in the applicable Federal court of jurisdiction.

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government 0002 Destination Government Destination Government 0003 Destination Government Destination Government 0004 Destination Government Destination Government 0005 Destination Government Destination Government 0006 Destination Government Destination Government 0007 Destination Government Destination Government 0008 Destination Government Destination Government 0009 Destination Government Destination Government

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 31-JUL-2024 1 NAVAL SURFACE WARFARE CENTER

RECEIVING OFFICER

6220 TISDALE ROAD BLDG 125 STE 159

DAHLGREN VA 22448-5114

(540) 653-7306 FOB: Destination

N00178

0002 31-JUL-2024 1 (SAME AS PREVIOUS LOCATION)

0003 31-JUL-2024 1 (SAME AS PREVIOUS LOCATION)

0004 31-JUL-2024 1 (SAME AS PREVIOUS LOCATION)

0005 31-JUL-2024 1 (SAME AS PREVIOUS LOCATION)

0006 31-JUL-2024 1 (SAME AS PREVIOUS LOCATION)

0007 31-JUL-2024 1 (SAME AS PREVIOUS LOCATION)

0008 31-JUL-2024 1 (SAME AS PREVIOUS LOCATION)

0009 31-JUL-2024 1 (SAME AS PREVIOUS LOCATION)

CLAUSES INCORPORATED BY REFERENCE

52.247-34 F.O.B. Destination NOV 1991

RECEIVING HOURS OF OPERATION

All deliveries to the Receiving Officer, Dahlgren Division, Naval Surface Warfare Center, Dahlgren, VA shall be made Monday through Friday from 7:00 a.m. to 2:30 p.m., local time.

Deliveries will not be accepted after 2:30 p.m. No deliveries will be made on government holidays.

NOTICE REGARDING LATE DELIVERY

In the event the contractor anticipates or encounters difficulty in complying with the contract delivery schedule or date, he/she shall immediately notify, in writing, the Contracting Officer and the cognizant Contract Administration Services Office, if assigned. The notice shall give the pertinent details; however, such notice shall not be construed as a waiver by the Government of any contract delivery schedule, or of any rights or remedies provided by law or under this contract.

Section G - Contract Administration Data

252.232-7003 Electronic Submission of Payment Requests and Receiving

Reports

DEC 2018

G-232-H002 PAYMENT INSTRUCTIONS (NAVSEA) (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-232-H005 SUPPLEMENTAL INSTRUCTIONS REGARDING INVOICING (NAVSEA) (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 breakdown 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). Should the 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.

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023)

(a) Definitions. As used in this clause—

“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) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232- 7003, Electronic Submission of Payment Requests and Receiving Reports.

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

(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) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice 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) WAWF methods of document submission. Document submissions may be via web entry, Electronic Data Interchange, or File Transfer Protocol.

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

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

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

Invoice2in1 Inspection Location: Destination Acceptance Location: Destination

(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) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in 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) P ayment req uest. T he Contractor shall ensure a payment req uest includes documentation appropriate to the type of payment req uest in accordance w ith the payment clause, contract financing clause, or

Federal Acq uisition Regulation 5 2.216 -7 , Allow able Cost and P ayment, as applicable.

(5 ) Receiving report. T he Contractor shall ensure a receiving report meets the req uirements of DFARS

Appendix F.

(g) W AW F point of contact.

P rovided upon aw ard.

(1) T he Contractor may obtain clarification regarding invoicing in W AW F from the follow ing contracting activity’s W AW F point of contact.

NSWCD_02_WAWF_AD.fct@navy.mil

(Contracting Officer: Insert applicable information or “Not applicable.”)

(2) Contact the W AW F helpdesk at 8 6 6 -6 18 -5 9 8 8 , if assistance is needed.

(E nd of clause)

FINAL INVOICING INSTRUCTIONS

***Please note, when invoicing be sure to mark the last invoice in the WAWF system as "FINAL" so that the invoice is properly closed out once payment has been processed;

unless a partial shipment has been authorized. If partial shipment has been authorized, partial payment invoices should not be marked as “FINAL”. All items of each CLIN must be delivered/received prior to marking the invoice as “FINAL”.***

Section I - Contract Clauses

52.232-18 AVAILABILITY OF FUNDS (APR 1984)

Funds are not presently available for this contract. The Government's obligation under this contract is contingent upon the availability of appropriated funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise until funds are made available to the Contracting Officer for this contract and until the Contractor receives notice of such availability, to be confirmed in writing by the Contracting Officer.

(End of clause)

252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023)

(a) Definitions. As used in this clause-

Automatic identification device means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

Concatenated unique item identifier means--

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

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

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

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

(IEC) 16022.

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

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

DoD item unique identification means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, 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 No. Item description See Schedule.

(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 No. 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 paragraphs (c)(1)(i), (ii), (iii), or

(iv) of this clause for which the contractor creates and marks a unique item identifier for traceability.

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

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

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

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

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

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

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

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

(5) Unique item identifier.

(i) The Contractor shall--

(A) Determine whether to--

(1) Serialize within the enterprise identifier;

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

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

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

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

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

(ii) The issuing agency code--

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

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

(d) For each item that requires item unique identification under paragraph (c)(1)(i), (ii), or (iv) of this clause or when item unique identification is provided under paragraph (c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, as part of the Material Inspection and Receiving Report, the following information:

(1) Unique item identifier.

(2) Unique item identifier type.

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

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

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

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

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

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

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

(10) Government's unit acquisition cost.

(11) Unit of measure.

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

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

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

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

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

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

(3) Unique item identifier type.**

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

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

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

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

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

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

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

(11) Description.

** Once per item.

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

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

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

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

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

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

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

52.243-1 Alt II Changes--Fixed-Price (Aug 1987) - Alternate II APR 1984 52.203-16 Preventing Personal Conflicts of Interest JUN 2020 52.204-13 System for Award Management Maintenance OCT 2018 52.204-18 Commercial and Government Entity Code Maintenance AUG 2020 52.204-19 Incorporation by Reference of Representations and

Certifications.

DEC 2014

52.211-15 Defense Priority And Allocation Requirements APR 2008 52.212-4 Contract Terms and Conditions--Commercial Products and

Commercial Services

NOV 2023

52.229-11 Tax on Certain Foreign Procurements--Notice and Representation

JUN 2020

52.232-39 Unenforceability of Unauthorized Obligations JUN 2013 52.233-1 Disputes MAY 2014 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-7000 Disclosure Of Information OCT 2016 252.204-7003 Control Of Government Personnel Work Product APR 1992 252.204-7004 Antiterrorism Awareness Training for Contractors JAN 2023 252.204-7009 Limitations on the Use or Disclosure of Third-Party

Contractor Reported Cyber Incident Information

JAN 2023

252.204-7012 (Dev) Safeguarding Covered Defense Information and Cyber Incident Reporting (DEVIATION 2024-O0013)

MAY 2024

252.204-7015 Notice of Authorized Disclosure of Information for Litigation Support

JAN 2023

252.225-7001 Alt I Buy American and Balance of Payments Program (FEB 2024) Alternate I

FEB 2024

252.225-7012 Preference For Certain Domestic Commodities APR 2022 252.225-7048 Export-Controlled Items JUN 2013 252.225-7052 Restriction on the Acquisition of Certain Magnets, Tantalum, and Tungsten.

JAN 2023

252.232-7010 Levies on Contract Payments DEC 2006 252.239-7010 Cloud Computing Services JAN 2023 252.239-7018 Supply Chain Risk DEC 2022 252.243-7001 Pricing Of Contract Modifications DEC 1991 252.246-7007 Contractor Counterfeit Electronic Part Detection and

Avoidance System

JAN 2023

252.246-7008 Sources of Electronic Parts JAN 2023 252.247-7023 Transportation of Supplies by Sea JAN 2023

52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION SYSTEMS (NOV 2021)

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

Covered contractor information system means an information system that is owned or operated by a contractor that processes, stores, or transmits Federal contract information.

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

Information means any communication or representation of knowledge such as facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audiovisual (Committee on National Security Systems Instruction (CNSSI) 4009).

Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information (44 U.S.C. 3502).

Safeguarding means measures or controls that are prescribed to protect information systems.

(b) Safeguarding requirements and procedures.

(1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls:

(i) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).

(ii) Limit information system access to the types of transactions and functions that authorized users are permitted to execute.

(iii) Verify and control/limit connections to and use of external information systems.

(iv) Control information posted or processed on publicly accessible information systems.

(v) Identify information system users, processes acting on behalf of users, or devices.

(vi) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.

(vii) Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.

(viii) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.

(ix) Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices.

(x) Monitor, control, and protect organizational communications (i.e., information transmitted or received by…