SPE4A725D0384 AWD.pdf

AWARD/CONTRACT 1. THIS CONTRACT IS A RATED ORDER

UNDER DPAS (15 CFR 700)

RATING

5. ISSUED BY CODE 6. ADMINISTERED BY (If other than Item 5) CODE

15A. ITEM NO. 15B. SUPPLIES/SERVICES 15C. QUANTITY 15D. UNIT 15F. AMOUNT15E. UNIT PRICE

7. NAME AND ADDRESS OF CONTRACTOR (No., street, city, county, State and ZIP Code) 8. DELIVERY

FOB ORIGIN OTHER (See below)

(4 copies unless otherwise specified)

11. SHIP TO/MARK FOR CODE 12. PAYMENT WILL BE MADE BY CODE

13. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c) 41 U.S.C. 253(c)

14. ACCOUNTING AND APPROPRIATION DATA

16. TABLE OF CONTENTS

(X) SEC. DESCRIPTION PAGE(S)

PART I - THE SCHEDULE

A SOLICITATION/CONTRACT FORM

B SUPPLIES OR SERVICES AND PRICES/COSTS

C DESCRIPTION/SPECS./WORK STATEMENT

D PACKAGING AND MARKING

E INSPECTION AND ACCEPTANCE

F DELIVERIES OR PERFORMANCE

G CONTRACT ADMINISTRATION DATA

H SPECIAL CONTRACT REQUIREMENTS

CONTRACTING OFFICER WILL COMPLETE ITEM 17 OR 18 AS APPLICABLE

17. CONTRACTOR'S NEGOTIATED AGREEMENT (Contractor is required to sign this document and return copies to issuing office.) Contractor agrees to furnish and deliver all items or perform all the services set forth or otherwise identified above and on any continuation sheets for the consideration stated herein. The rights and obligations of the parties to this contract shall be subject to and governed by the following documents: (a) this award/contract, (b) the solicitation, if any, and (c) such provisions, representations, certifications, and specifications, as are attached or incorporated by reference herein. (Attachments are listed herein.)

18. SEALED-BID AWARD (Contractor is not required to sign this document.)

Your bid on Solicitation Number , , including the additions or changes made by you which additions or changes are set forth in full above, is hereby accepted as to the terms listed above and on any continuation sheets.

This award consummates the contract which consists of the following documents: (a) the Government's solicitation and your bid, and (b) this award/contract. No further contractual document is necessary. (Block 18 should be checked only when awarding a sealed-bid contract.)

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

PAGE(S)

PART II - CONTRACT CLAUSES

(X) SEC. DESCRIPTION

PART IV - REPRESENTATIONS AND INSTRUCTIONS

I CONTRACT CLAUSES

J LIST OF ATTACHMENTS

K REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF

OFFERORS

L INSTRS., CONDS., AND NOTICES TO OFFERORS

M EVALUATION FACTORS FOR AWARD

15G. TOTAL AMOUNT OF CONTRACT

19B. NAME OF CONTRACTOR

BY

AUTHORIZED FOR LOCAL REPRODUCTION STANDARD FORM 26 (REV. 5 /2011 )

20B. UNITED STATES OF AMERICA

BY

Previous edition is usable Prescribed by GSA - FAR (48 CFR) 53.214(a)

SPE4A7-25-D-0384

2. CONTRACT (Proc. Inst. Ident.) NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUEST/PROJECT NO.

7Z016CODE FACILITY CODE

Net 30 days

9. DISCOUNT FOR PROMPT PAYMENT

ITEM

$1,999,999.99

X 1

19A. NAME AND TITLE OF SIGNER (Type or Print)

19C. DATE SIGNED

20A. NAME OF CONTRACTING OFFICER

20C. DATE SIGNED

X

SEE SCHEDULE, DO NOT SHIP TO ADDRESS ON THIS PAGE

DEF FIN AND ACCOUNTING SVC

BSM

P O BOX 182317

COLUMBUS OH 43218-2317

USA

SL4701

X

1 SPE4A725R0623

( Signature of person authorized to sign) (Signature of Contracting Officer)

SPE4A7

DLA AVIATION

ASC SUPPLIER OPER AE AND AF DIV

6090 STRATHMORE ROAD

RICHMOND VA 23237

USA

Local Admin: Jeremy Prince PARFE09 Tel: 8042795994 Email: Jeremy.Prince@dla.mil

SPE4A1

DLA AVIATION

AVIATION SUPPLY CHAIN

6090 STRATHMORE ROAD

RICHMOND VA 23237

USA

Criticality: PAS : None

KAMPI COMPONENTS CO INC

88 CANAL RD

FAIRLESS HILLS PA 19030-4302

USA

See Schedule

10. SUBMIT INVOICES

TO THE

ADDRESS SHOWN IN

J PAGE 1 OF 17

MAXIMUM CONTRACT VALUE NTE

TO BE CITED ON EACH DELIVERY ORDER

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

CONTINUED ON NEXT PAGE

PAGE 2 OF 17 PAGES

SPE4A7-25-D-0384

This is a 5-year Long Term Indefinite Delivery Contract (IDC) with a 5-year Base effective date from 9/24/2025 to 9/23/2030. The total dollar value of this contract shall not exceed $1,999,999.99 for all delivery orders issued against it.

This contract is for a Base Period of 5 year with ZERO (0) Options.

The Guaranteed Minimum Quantity for this IQC is __15__ each. There is no guarantee that the Government will place any orders after the Guaranteed Minimum (GM) quantity has been met. This GM qty should be satisfied within the first year of the contract. If the GM qty has not been satisfied withing the first year, please contact the Basic Contract Administrator.

FOB DESTINATION, INSPECTION/ACCEPTANCE DESTINATION.

Dealer: Company Name (CAGE #) KAMPI COMPONENTS, Cage: 7Z016

Manufacturer: Company Name (CAGE #) ROBERTSON FUEL SYSTEMS, Cage: 1T765

Higher Level Quality Applies to Manufacturer Only (i.e., ISO 9001:2015, etc.). Dealer is not required to be Higher Level Certified.

PRICING IS AS FOLLOWS:

ESTIMATED ANNUAL QUANTITY UNIT PRICE (FOB DESTINATION)

YEAR 1 60 EACH $1,895.46 EACH

YEAR 2 60 EACH $2,028.16 EACH

YEAR 3 60 EACH $2,170.11 EACH

YEAR 4 60 EACH $2,321.99 EACH

YEAR 5 60 EACH $2,484.53 EACH

BASE YEAR ORDERING PERIODS (1-4)

GUARANTEED CONTRACT QUANTITY 15 BASE YEAR ONLY

MINIMUM DELIVERY ORDER QUANTITY 15 15

MAXIMUM DELIVERY ORDER QUANTITY 60 60

THE REQUIRED DELIVERY SCHEDULE IS 385 DAYS ARO. PARTIAL AND EARLY SHIPMENTS AT NO ADDITIONAL COST TO THE GOVERNMENT

ARE AUTHORIZED AND PREFERRED ON THIS CONTRACT.

TECH QUALITY and DLAD PROCUREMENT NOTES: http://www.dla.mil/HQ/Acquisition/Offers/eProcurement.aspx

The following procurement notes apply to solicitations and purchase orders as indicated below and may be found at the following: link: http://www.dla.mil/Aviation/Business/IndustryResources/DLAResourcesforSuppliers/DAANs.aspx

DAAN-11-01 Notification of Rejection of Award with Technical Data

DAAN-15-01 Evaluation and Award for Acquisitions Above the Simplified Acquisition Threshold

UNRESTRICTED

PAYMENT TERMS: NET 30

KAMPI COMPONENTS OFFER FOR SOLICITATION SPE4A725R0623 IS HEREBY INCORPORATED INTO THIS AWARD.

PAR SUBMISSIONS FOR THE BASIC LONG-TERM CONTRACTS (LTCs) VERSES DELIVERY ORDERS:

- FOR ANY ISSUES WITH THE BASIC CONTRACT, USE THE BASIC CONTRACT PIIN NUMBER WHEN SUBMITTING A PAR. BASIC CONTRACT

PIIN NUMBERS HAVE A “D” IN THE 9TH POSITION. EXAMPLE – SPE4A7-2#-D-XXXX.

**AFTER PAR SUBMISSION FOR THE BASIC, SEND A FOLLOW UP EMAIL TO THE INDIVIDUAL IDENTIFIED IN THE PAR TO ENSURE RECIEPT

OR ACKNOWLEDGEMENT OF THE PAR.**

- FOR ANY ISSUES WITH A DELIVERY ORDER, USE THE DELIVERY ORDER PIIN NUMBER WHEN SUBMITTING A PAR. DELIVERY ORDER PIIN

NUMBERS HAVE AN “F” IN THE 9TH POSITION. EXAMPLE –

SPE4A7-2#-F-XXXX.

*Email not suggested for Delivery Orders*

In the event that the Contractor experiences increases in supplier/manufacturer costs in the performance of delivery orders issued against this basic contract that are or could potentially be detrimental to the financial operations of the Contractor, the Government guarantees that a review and consideration for any price adjustment request will be conducted provided that the Contractor supplies the Government with appropriate supporting documentation for that price adjustment request. In the event that the Procuring Contracting Officer and Contractor cannot agree to the terms of the price adjustment request, the Contractor will be afforded the opportunity to either continue with the basic contract and any open orders as is or terminate the basic contract and any open orders at no cost to either party”.

PAGE 3 OF 17 PAGES

SPE4A7-25-D-0384

SECTION B

SUPPLIES/SERVICES: 2915-01-466-9676

ITEM DESCRIPTION:

<H> NOZZLE FUEL INJECTION</>

RP001: DLA PACKAGING REQUIREMENTS FOR PROCUREMENT

RD002, COVERED DEFENSE INFORMATION APPLIES

RA001: THIS DOCUMENT INCORPORATES TECHNICAL AND/OR QUALITY REQUIREMENTS

(IDENTIFIED BY AN 'R' OR AN 'I' NUMBER) SET FORTH IN FULL TEXT INTHE

DLA MASTER LIST OF TECHNICAL AND QUALITY REQUIREMENTS FOUND ON THEWEB

AT:

http://www.dla.mil/HQ/Acquisition/Offers/eProcurement.aspx

FOR SIMPLIFIED ACQUISITIONS, THE REVISION OF THE MASTER INEFFECT ON THE

SOLICITATION ISSUE DATE OR THE AWARD DATE CONTROLS. FOR LARGE

ACQUISITIONS, THE REVISION OF THE MASTER IN EFFECT ONTHE RFP ISSUE DATE

APPLIES UNLESS A SOLICITATION AMENDMENT INCORPORATES A FOLLOW-ON

REVISION, IN WHICH CASE THE AMENDMENT DATECONTROLS.

RQ001: TAILORED HIGHER LEVEL CONTRACT QUALITY REQUIREMENTS

(MANUFACTURERS AND NON-MANUFACTURERS)

RQ002: CONFIGURATION CHANGE MANAGEMENT - ENGINEERING CHANGE PROPOSAL

REQUEST FOR VARIANCE (DEVIATION OR WAIVER)

RQ011: REMOVAL OF GOVERNMENTIDENTIFICATION FROM NON-ACCEPTED SUPPLIES

<H>--</>

SAMPLING:

THE SAMPLING METHOD SHALL BE IN ACCORDANCE WITH MIL-STD-1916 ORASQ

H1331, TABLE 1 OR A COMPARABLE ZERO BASED SAMPLING PLAN UNLESS OTHERWISE

SPECIFIED BY THE CONTRACT. IF THE APPLICABLE DRAWING,SPECIFICATION,

STANDARD, OR QUALITY ASSURANCE PROVISION (QAP) SPECIFIES CRITICAL, MAJOR

AND/OR MINOR ATTRIBUTES, THEY SHALL BEASSIGNED VERIFICATION LEVELS OF

VII, IV AND II OR AQLS OF 0.1, 1.0 AND 4.0 RESPECTIVELY. UNSPECIFIED

ATTRIBUTES SHALL BE CONSIDEREDAS MAJOR UNLESS SAMPLING PLANS ARE

SPECIFIED IN APPLICABLE DOCUMENTS. FOR MIL-STD-1916, THE MANUFACTURER

MAY USE THE ATTRIBUTE ORVARIABLE INSPECTION METHOD AT THEIR OPTION OR

PER THE CONTRACT. MIL-STD-105/ASQ Z1.4 MAY BE USED TO SET SAMPLE LOT

SIZE, BUTACCEPTANCE WOULD BE ZERO NON-CONFORMANCES IN THE SAMPLE LOT

UNLESS OTHERWISE SPECIFIED IN THE CONTRACT.

ROBERTSON AVIATIONLLC

MIL-STD-130N(1) DATED 16 NOV 2012.

IDENTIFICATION MARKING OF U.S. MILITARY PROPERTY

DSCR DOES NOT CURRENTLY HAVE ANAPPROVED

TECHNICAL DATA PACKAGE AVAILABLE FOR THIS NSN.

DATA IS PROPRIETARY OR INSUFFICIENT FOR

COMPETITIVEPROCUREMENT.

CRITICAL APPLICATION ITEM

ROBERTSON FUEL SYSTEMS, L.L.C. 1T765 P/N HM020-931-11

DLA issues this document using the DoD authorized unit of issue, please refer to the following URL to determine the corresponding ANSI X12 unit of issue.

PAGE 4 OF 17 PAGES

SPE4A7-25-D-0384

SECTION B

SUPPLY/SERVICE: 2915-01-466-9676 CONT'D

https://www.dla.mil/Portals/104/Documents/DLMS/eApplications/LogDataAdmin/Unit_of_Issue_and_Purchase_Unit.xlsx

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT .

0001 2915-01-466-9676 EA $ $

NOZZLE,FUEL

INJECTI

PRICING TERMS: Firm Fixed Price

SUPPLIES/SERVICES: 2915-01-466-9676

Delivery CLIN Price (in days) .

0001 $

QTY VARIANCE: PLUS 0% MINUS 0%

INSPECTION POINT: DESTINATION

ACCEPTANCE POINT: DESTINATION

FOB: DESTINATION DELIVERY DATE:

FOB PAYMENT METHOD: CONTRACTOR

PREP FOR DELIVERY:

PKGING DATA - MIL-STD-2073-1E

QUP:001 PRES MTHD:41 CLNG/DRY:1 PRESV MAT:00

WRAP MAT:00 CUSH/DUNN MAT:NA CUSH/DUNNTHKNESS:C

UNIT CONT:E5 OPI:M

INTRMDTE CONT:E5 INTRMDTE CONT QTY:AAA

PACK CODE:U

MARKING SHALL BE IN ACCORDANCE WITHMIL-STD-129.

SPECIAL MARKING CODE:00 -00 No special marking

PALLETIZATION SHALL BE IN ACCORDANCE WITH RP001: DLA PACKAGING

REQUIREMENTS FOR PROCUREMENT

GOVT USE

External External External Customer RDD/

ITEM PR PRLI PR PRLI Material Need Ship Date .

0001 1000204033 0001 N/A N/A N/A N/A

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 5 OF 17 PAGES

SPE4A7-25-D-0384

SECTION A - SOLICITATION/CONTRACT FORM

52.204-16 COMMERCIAL AND GOVERNMENT ENTITY CODE REPORTING (AUG 2020) FAR

SECTION C - SPECIFICATIONS/SOW/SOO/ORD

C02 MANUFACTURING PHASE OUT OR DISCONTINUATION OF PRODUCTION, DIMINISHING SOURCES, AND OBSOLETE

MATERIALS OR COMPONENTS (DEC 2016)

SECTION E - INSPECTION AND ACCEPTANCE

52.246-2 INSPECTION OF SUPPLIES FIXED PRICE (AUG 1996) FAR

52.246-11 HIGHER-LEVEL CONTRACT QUALITY REQUIREMENT (DEC 2014) FAR

As prescribed in 46.311, insert the following clause:

(a) The Contractor shall comply with the higher-level quality standard(s) listed below.

Title Number Date Tailoring

ISO 9001:2015

[Contracting Officer insert the title, number, date, and tailoring (if any) of the higher-level quality standards.]

(b) The Contractor shall include applicable requirements of the higher-level quality standard(s) listed in paragraph (a) of this clause and the requirement to flow down such standards, as applicable, to lower-tier subcontracts, in-

(1) Any subcontract for critical and complex items (see 46.203(b) and (c)); or

(2) When the technical requirements of a subcontract require-

(i) Control of such things as design, work operations, in-process control, testing, and inspection; or

(ii) Attention to such factors as organization, planning, work instruction, documentation control, and advanced metrology.

(End of Clause)

E05 PRODUCT VERIFICATION TESTING (MAY 2020)

(1) Product verification testing (PVT) under this procurement note will only apply when the contracting officer specifically invokes it in writing. The contracting officer may invoke PVT at or after contract award. If the contracting officer invokes PVT at contract award, the contract will explicitly state this testing requirement. If the contracting officer invokes PVT after contract award, the contracting officer shall notify the contractor and the cognizant DCMA ACO. The Government will perform PVT testing at a Government-designated testing laboratory.

(2) The contractor shall not ship or deliver any material until it receives notification of the acceptable PVT results, unless the contracting officer directs it to do so in writing The Government will provide the PVT results to the contractor within 20 business days after receipt at the Government testing facility, unless the Government specifies otherwise in writing.

(3) The contractor shall provide and maintain an inspection system acceptable to the Government in accordance with FAR Clause 52.246-2 or 52.246-3; and maintain and make available all records evidencing those details if requested by the Government. When the Government finds evidence of risk associated with the contractor's sampling process, the Government may witness and evaluate the contractors sampling process. The contractor shall randomly select samples from the production lot(s), unless the contracting officer specifies otherwise in writing. The contractor shall ship the selected PVT samples with a copy of the system of record receiving report (i.e., WAWF, DD Form 250, or commercial shipping document) and the contractor's signed DD Form 1222.

The contractor shall prepare the shipping container(s) by marking the external packages in bold letters, “Product Verification Test Samples - Do Not Post to Stock," Contract Number [ ] and Lot/Item Number [ ]” adjacent to the MIL-STD-129 (latest revision) identification markings. The contractor shall use a hard copy of the system of record receiving report as a packing list, in accordance with DFARS Appendix F. The contractor shall mark the exterior of the shipping container in accordance with MIL-STD129 (latest revision), paragraph 5.11. The contractor shall send samples by traceable means (e.g., certified or registered mail, United Parcel Service, Federal Express). The contractor shall include the following in the interior package:

(a) Hard copies of the contract;

(b) Material certifications/process operation sheets; and

(c) Drawings used to manufacture the units and return shipping information.

(4) The Government will return samples that pass testing and are not destroyed during evaluation to the contractor at the Government's expense for the contractor to include as part of the total contract quantity to be delivered under the contract. The contractor and Government may agree to dispose of samples not destroyed when the cost of the item does not justify the shipping expense. If the Government does not return approved samples that pass testing to the contractor, the Government will consider those samples as part of the contract quantity for payment and delivery.

(5) If samples fail testing, the Government may reject the entire contract lot from which the contractor took the samples. The Government may, at its discretion, retain samples that fail testing without obligation to the contractor.

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 6 OF 17 PAGES

SPE4A7-25-D-0384

SECTION F - DELIVERIES OR PERFORMANCE (CONTINUED)

SECTION F - DELIVERIES OR PERFORMANCE

52.247-34 F.O.B. DESTINATION (JAN 1991) FAR

52.211-8 TIME OF DELIVERY (JUN 1997) FAR

As prescribed in 11.404(a)(2), insert the following clause:

(a) The Government requires delivery to be made according to the following schedule:

REQUIRED DELIVERY SCHEDULE

ITEM NO. QUANTITY WITHIN DAYS AFTER

DATE OF CONTRACT

0001 60 385

The Government will evaluate equally, as regards time of delivery, offers that propose delivery of each quantity within the applicable delivery period specified above. Offers that propose delivery that will not clearly fall within the applicable required delivery period specified above, will be considered nonresponsive and rejected. The Government reserves the right to award under either the required delivery schedule or the proposed delivery schedule, when an offeror offers an earlier delivery schedule than required above. If the offeror proposes no other delivery schedule, the required delivery schedule above will apply.

OFFEROR'S PROPOSED DELIVERY SCHEDULE

ITEM NO. QUANTITY WITHIN DAYS AFTER

DATE OF CONTRACT

(b) Attention is directed to the Contract Award provision of the solicitation that provides that a written award or acceptance of offer mailed, or otherwise furnished to the successful offeror, results in a binding contract. The Government will mail or otherwise furnish to the offeror an award or notice of award not later than the day award is dated. Therefore, the offeror should compute the time available for performance beginning with the actual date of award, rather than the date the written notice of award is received from the Contracting Officer through the ordinary mails. However, the Government will evaluate an offer that proposes delivery based on the Contractor's date of receipt of the contract or notice of award by adding (1) five calendar days for delivery of the award through the ordinary mails, or (2) one working day if the solicitation states that the contract or notice of award will be transmitted electronically. (The term “working day” excludes weekends and U.S. Federal holidays.) If, as so computed, the offered delivery date is later than the required delivery date, the offer will be considered nonresponsive and rejected.

(End of clause)

SECTION G - CONTRACT ADMINISTRATION DATA

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (PRE-FILLED) (JAN 2023) DFARS As prescribed in 232.7004 (b), use the following clause:

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

https://www.acquisition.gov/far/part-11 https://www.acquisition.gov/dfars/part-232-contract-financing https://www.sam.gov https://wawf.eb.mil/ https://wawf.eb.mil/ https://wawf.eb.mil/

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 7 OF 17 PAGES

SPE4A7-25-D-0384

SECTION G - CONTRACT ADMINISTRATION DATA (CONTINUED)

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

Invoice (stand-alone) and Receiving Report (stand-alone) or Invoice and Receiving Report (combination)

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

Pay Official DoDAAC See Block 12 (SF26), 15 (DD 1155), or 18a

(SF1449)

(If blank, see resulting award)

Issue By DoDAAC See Block 5 (SF26), 6 (DD 1155), or 9 (SF1449)

(If blank, see resulting award)

Admin DoDAAC See Block 6 (SF26), 7 (DD 1155), or 16 (SF1449)

(If blank, see resulting award)

Inspect By DoDAAC SEE SECTION B (If blank, see resulting award)

Ship To Code SEE SECTION B (If blank, see resulting award)

Ship From Code SEE SECTION B (If blank, see resulting award)

Mark For Code SEE SECTION B (If blank, see resulting award)

Service Approver (DoDAAC)

(If blank, see resulting award)

Service Acceptor (DoDAAC)

(If blank, see resulting award)

Accept at Other DoDAAC (If blank, see resulting award)

LPO DoDAAC (If blank, see resulting award)

DCAA Auditor DoDAAC (If blank, see resulting award)

Other DoDAAC(s) (If blank, see resulting award)

(* 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) Payment request. The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

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

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

See administer listed on page 1

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

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

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 8 OF 17 PAGES

SPE4A7-25-D-0384

SECTION G - CONTRACT ADMINISTRATION DATA (CONTINUED)

(End of Clause)

SECTION I - CONTRACT CLAUSES

52.203-19 PROHIBITION ON REQUIRING CERTAIN INTERNAL CONFIDENTIALITY AGREEMENTS OR STATEMENTS (JAN 2017)

FAR

52.204-14 SERVICE CONTRACT REPORTING REQUIREMENTS (OCT 2016) FAR

52.204-15 SERVICE CONTRACT REPORTING REQUIREMENTS FOR INDEFINITE-DELIVERY CONTRACTS (OCT 2016) FAR

52.204-18 COMMERCIAL AND GOVERNMENT ENTITY CODE MAINTENANCE (AUG 2020) FAR

52.204-19 INCORPORATION BY REFERENCE OF REPRESENTATIONS AND CERTIFICATIONS (DEC 2014) FAR

52.204-20 PREDECESSOR OF OFFEROR (AUG 2020) FAR

As prescribed in 4.1804(d), insert the following provision:

(a) Definitions. As used in this provision -- Commercial and Government Entity (CAGE) code means --

(1) An identifier assigned to entities located in the United States or its outlying areas by the Defense Logistics Agency (DLA) Commercial and Government Entity (CAGE) Branch to identify a commercial or government entity by unique location; or

(2) An identifier assigned by a member of the North Atlantic Treaty Organization (NATO) or by the NATO Support and Procurement Agency (NSPA) to entities located outside the United States and its outlying areas that the DLA Commercial and Government Entity (CAGE) Branch records and maintains in the CAGE master file. This type of code is known as a NATO CAGE (NCAGE) code.

Predecessor means an entity that is replaced by a successor and includes any predecessors of the predecessor.

Successor means an entity that has replaced a predecessor by acquiring the assets and carrying out the affairs of the predecessor under a new name (often through acquisition or merger). The term “successor” does not include new offices/divisions of the same company or a company that only changes its name.

The extent of the responsibility of the successor for the liabilities of the predecessor may vary, depending on State law and specific circumstances.

(b) The Offeror represents that it [ ] is or [ ] is not a successor to a predecessor that held a Federal contract or grant within the last three years.

(c) If the Offeror has indicated “is” in paragraph (b) of this provision, enter the following information for all predecessors that held a Federal contract or grant within the last three years (if more than one predecessor, list in reverse chronological order):

Predecessor CAGE code: (or mark “Unknown”).

Predecessor legal name: .

(Do not use a “doing business as” name).

252.204-7000 DISCLOSURE OF INFORMATION (OCT 2016) DFARS

252.204-7009 LIMITATIONS ON THE USE OR DISCLOSURE OF THIRD-PARTY CONTRACTOR REPORTED CYBER INCIDENT

INFORMATION (JAN 2023) DFARS

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT REPORTING (DEVIATION 2024-O0013)

(MAY 2024) DFARS

(a) Definitions. As used in this clause

Adequate security means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

Compromise means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

Contractor attributional/proprietary information means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

Controlled technical information means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

Covered contractor information system means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

Covered defense information means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI)

Registry at http://www.archives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, https://www.acquisition.gov/far/part-4 http://www.archives.gov/cui/registry/category-list.html

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 9 OF 17 PAGES

SPE4A7-25-D-0384

SECTION I - CONTRACT CLAUSES (CONTINUED)

regulations, and Governmentwide policies, and is --

(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or

(2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract.

Cyber incident means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

Forensic analysis means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.

Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

Malicious software means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

Media means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system.

Operationally critical support means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

Rapidly report means within 72 hours of discovery of any cyber incident.

Technical information means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data --Other Than Commercial Products and Commercial Services, regardless of whether or not the clause is incorporated in this solicitation or contract.

Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security on all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:

(1) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government, the following security requirements apply:

(i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract.

(ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.

(2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply:

(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations”, Revision 2 (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171).

(ii)(A) The Contractor shall implement NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.

(C) If the DoD CIO has previously adjudicated the contractor's requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.

(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) http://dx.doi.org/10.6028/NIST.SP.800-171 mailto:osd.dibcsia@mail.mil http://www.fedramp.gov/resources/documents/)

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 10 OF 17 PAGES

SPE4A7-25-D-0384

SECTION I - CONTRACT CLAUSES (CONTINUED)

and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.

(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, the Contractor shall --

(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor's network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor's ability to provide operationally critical support; and

(ii) Rapidly report cyber incidents to DoD at https://dibnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at https://dibnet.dod.mil.

(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see https://public.cyber.mil/eca/.

(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information equipment that is necessary to conduct a forensic analysis.

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/ proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD --

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or

(5) To a support services contractor (“recipient”) that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 11 OF 17 PAGES

SPE4A7-25-D-0384

SECTION I - CONTRACT CLAUSES (CONTINUED)

(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph

(i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall --

(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial products or commercial services, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and

(2) Require subcontractors to --

(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and

(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

252.204-7014 LIMITATIONS ON THE USE OR DISCLOSURE OF INFORMATION BY LITIGATION SUPPORT CONTRACTORS (JAN

2023) DFARS

252.204-7015 NOTICE OF AUTHORIZED DISCLOSURE OF INFORMATION FOR LITIGATION SUPPORT (JAN 2023) DFARS

52.211-15 DEFENSE PRIORITY AND ALLOCATION REQUIREMENTS (APR 2008) FAR

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

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

(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 https://www.acquisition.gov/dfars/part-211-describing-agency-needs https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 12 OF 17 PAGES

SPE4A7-25-D-0384

SECTION I - CONTRACT CLAUSES (CONTINUED)

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