Addenda additional clauses.pdf

Addenda - List of Additional Clauses

52.204-7 System for Award Management

OCT

52.204-13 System for Award Management Maintenance

OCT

52.204-16 Commercial and Government Entity Code Reporting

JUL

52.204-18 Commercial and Government Entity Code Maintenance

JUL

52.204-21 Basic Safeguarding of Covered Contractor Information Systems

JUN

52.209-9 Updates of Publicly Available Information Regarding Responsibility Matters

OCT

52.212-3 Offeror Representations and Certifications— Commercial Items-- Alternate I

OCT

52.212-4 Contract Terms and Conditions— Commercial Items

OCT

52.232-40 Providing Accelerated Payments to Small Business Subcontractors

DEC

252.203-7000 Requirements Relating to Compensation of Former DoD Officials

SEP

252.203-7005 Representation Relating to Compensation of Former DoD Officials

NOV

252.204-7008 Compliance with Safeguarding Covered Defense Information Controls

OCT

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

MAY

252.204-7017 Prohibition on the Acquisition of Covered Defense Telecommunications Equipment or Services- Representation

DEC

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

DEC

252.211-7008 Use of Government- Assigned Serial Numbers

SEP

252.213-7000 Notice to Prospective Suppliers on Use of Supplier Performance Risk System in Past Performance Evaluations

SEP

252.215-7008 Only One Offer JUL

252.223-7008 Prohibition of Hexavalent Chromium

JUN

252.225-7012 Preference for Certain Domestic Commodities

DEC

252.225-7027 Restriction on Contingent Fees for Foreign Military Sales

APR

252.225-7052 Restriction on the Acquisition of Certain Magnets and Tungsten

APR

252.232-7010 Levies on Contract Payments

DEC

252.243-7002 Requests for Equitable Adjustment

DEC

252.244-7000 Subcontracts for Commercial Items

JUN

252.246-7008 Sources of Electronic Parts

MAY

52.219-3 Notice of HUBZone Set- Aside or Sole Source Award (DEVIATION 2019-O0003)

DEC

52.219-6 Notice of Total Small Business Set-Aside

(DEVIATION 2019-

O0003)

DEC

252.225-7979 Additional Access to Contractor and Subcontractor Records in the United States Central Command Theater of Operations

(DEVIATION 2018-

O0008)

DEC

252.225-7993 Prohibition on Providing Funds to the Enemy

(DEVIATION 2020-

O0001)

NOV

252.211-7003 Item Unique Identification and Valuation.

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

ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2016)

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

https://www.acquisition.gov/dfars/part-211-describing-agency-needs#211.274-6

“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 http://www.acq.osd.mil/dpap/pdi/uid/iuid_equivalents.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.

“ Lotor 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 https://www.acquisition.gov/dfars/iuid.html https://www.acquisition.gov/dfars/?Reg 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 http://www.acq.osd.mil/dpap/pdi/uid/uii_types.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 https://www.acquisition.gov/dfars/uii.html

Exhibit Line Item Number Item Description

__________TBD_________________________________________________________

(ii) Items for which the Government’s unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table:

Contract Line, Subline, or

Exhibit Line Item Number Item Description

________________TBD___________________________________________________

____________________TBD_______________________________________________

____________________________TBD_______________________________________

(If items are identified in the Schedule, insert “See Schedule in this table.)

(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number ____.

(iv) Any item of special tooling or special test equipment as defined in FAR

2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number ____.

(v) Any item not included in (i), (ii), (iii), or (iv) for which the contractor creates and marks a unique item identifier for traceability.

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

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

(4) 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 item unique identification under paragraph (c)(1)(iii) of this clause or when item unique identification is provided under paragraph (c)(1)(v), the Contractor shall report as part of the Material Inspection and Receiving

Report specified elsewhere in this contract, the following information:

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

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

(3) Unique item identifier type.**

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

(5) Enterpriseidentifier (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 https://www.acquisition.gov/dfars/252/dfars/part-232-contract-financing#252.232-7003 http://dodprocurementtoolbox.com/site/uidregistry/ http://dodprocurementtoolbox.com/site/uidregistry/

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

(End of clause)

252.211-7006 Passive Radio Frequency Identification.

As prescribed in 211.275-3, use the following clause:

PASSIVE RADIO FREQUENCY IDENTIFICATION (DEC 2019)

(a) Definitions. As used in this clause—

“Advance shipment notice” means an electronic notification used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as passive radio frequency identification (RFID) or item unique identification (IUID) information, order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment.

“Bulk commodities” means the following commodities, when shipped in rail tank cars, tanker trucks, trailers, other bulk wheeled conveyances, or pipelines:

(1) Sand.

(2) Gravel.

(3) Bulk liquids (water, chemicals, or petroleum products).

(4) Ready-mix concrete or similar construction materials.

(5) Coal or combustibles such as firewood.

(6) Agricultural products such as seeds, grains, or animal feed.

“Case” means either a MIL-STD-129 defined exterior container within a palletized unit load or a MIL- STD-129 defined individual shipping container.

“Electronic Product Code™ (EPC)” means an identification scheme for universally identifying physical objects via RFID tags and other means. The standardized EPC data consists of an EPC (or EPC identifier) that uniquely identifies an individual object, as well as an optional filter value when judged to be necessary to enable effective and efficient reading of the EPC tags. In addition to this standardized data, certain classes of EPC tags will allow user-defined data. The EPC Tag Data Standards will define the length and position of this data, without defining its content.

https://www.acquisition.gov/dfars/part-211-describing-agency-needs#211.275-3

“EPCglobal®” means a subscriber-driven organization comprised of industry leaders and organizations focused on creating global standards for the adoption of passive RFID technology.

“Exterior container” means a MIL-STD-129 defined container, bundle, or assembly that is sufficient by reason of material, design, and construction to protect unit packs and intermediate containers and their contents during shipment and storage. It can be a unit pack or a container with a combination of unit packs or intermediate containers. An exterior container may or may not be used as a shipping container.

“Palletized unit load” means a MIL-STD-129 defined quantity of items, packed or unpacked, arranged on a pallet in a specified manner and secured, strapped, or fastened on the pallet so that the whole palletized load is handled as a single unit. A palletized or skidded load is not considered to be a shipping container. A loaded 463L System pallet is not considered to be a palletized unit load. Refer to the Defense Transportation Regulation, DoD 4500.9-R, Part II, Chapter 203, for marking of 463L System pallets.

“Passive RFID tag” means a tag that reflects energy from the reader/interrogator or that receives and temporarily stores a small amount of energy from the reader/interrogator signal in order to generate the tag response. The only acceptable tags are EPC Class 1 passive RFID tags that meet the EPCglobal™ Class 1 Generation 2 standard.

“Radio frequency identification (RFID)” means an automatic identification and data capture technology comprising one or more reader/interrogators and one or more radio frequency transponders in which data transfer is achieved by means of suitably modulated inductive or radiating electromagnetic carriers.

“Shipping container” means a MIL-STD-129 defined exterior container that meets carrier regulations and is of sufficient strength, by reason of material, design, and construction, to be shipped safely without further packing (e.g., wooden boxes or crates, fiber and metal drums, and corrugated and solid fiberboard boxes).

(b)(1) Except as provided in paragraph (b)(2) of this clause, the Contractor shall affix passive RFID tags, at the case- and palletized-unit-load packaging levels, for shipments of items that—

(i) Are in any of the following classes of supply, as defined in DoD Manual 4140.01, Volume 6, DoD Supply Chain Materiel Management Procedures: Materiel Returns, Retention, and Disposition:

(A) Subclass of Class I – Packaged operational rations.

(B) Class II – Clothing, individual equipment, tentage, organizational tool kits, hand tools, and administrative and housekeeping supplies and equipment.

(C) Class IIIP – Packaged petroleum, lubricants, oils, preservatives, chemicals, and additives.

(D) Class IV – Construction and barrier materials.

(E) Class VI – Personal demand items (non-military sales items).

(F) Subclass of Class VIII – Medical materials (excluding pharmaceuticals, biologicals, and reagents – suppliers should limit the mixing of excluded and non-excluded materials).

(G) Class IX – Repair parts and components including kits, assemblies and subassemblies, reparable and consumable items required for maintenance support of all equipment, excluding medical-peculiar repair parts; and

(ii) Are being shipped to one of the locations listed at https://www.acq.osd.mil/log/sci/RFID_ship-to-locations.html or to—

(A) A location outside the contiguous United States when the shipment has been assigned Transportation Priority 1, or to—

(B) The following location(s) deemed necessary by the requiring activity:

Contract Line, Subline, or Exhibit Line Item Number

Location Name City State DoDAAC

TBD

TBD

TBD

(2) The following are excluded from the requirements of paragraph (b)(1) of this clause:

(i) Shipments of bulk commodities.

(ii) Shipments to locations other than Defense Distribution Depots when the contract includes the clause at FAR 52.213-1, Fast Payment Procedures.

(c) The Contractor shall—

(1) Ensure that the data encoded on each passive RFID tag are globally unique (i.e., the tag ID is never repeated across two or more RFID tags and conforms to the requirements in paragraph

(d) of this clause;

(2) Use passive tags that are readable; and

(3) Ensure that the passive tag is affixed at the appropriate location on the specific level of packaging, in accordance with MIL-STD-129 (Section 4.9.2) tag placement specifications.

(d) Data syntax and standards. The Contractor shall encode an approved RFID tag using the instructions provided in the EPC™ Tag Data Standards in effect at the time of contract award. The EPC™ Tag Data Standards are available at http://www.gs1.org/epc-rfid.

https://www.acquisition.gov/dfars/RFID.html http://www.gs1.org/epc-rfid

(1) If the Contractor is an EPCglobal™ subscriber and possesses a unique EPC™ company prefix, the Contractor may use any of the identifiers and encoding instructions described in the most recent EPC™ Tag Data Standards document to encode tags.

(2) If the Contractor chooses to employ the DoD identifier, the Contractor shall use its previously assigned Commercial and Government Entity (CAGE) code and shall encode the tags in accordance with the tag identifier details located in the DoD Suppliers' Passive RFID Information Guide at http://www.acq.osd.mil/log/sci/ait.html. If the Contractor uses a third-party packaging house to encode its tags, the CAGE code of the third-party packaging house is acceptable.

(3) Regardless of the selected encoding scheme, the Contractor with which the Department holds the contract is responsible for ensuring that the tag ID encoded on each passive RFID tag is globally unique, per the requirements in paragraph (c)(1).

(e) Advance shipment notice. The Contractor shall use Wide Area WorkFlow (WAWF), as required by DFARS 252.232-7003, Electronic Submission of Payment Requests, to electronically submit advance shipment notice(s) with the RFID tag ID(s) (specified in paragraph (d) of this clause) in advance of the shipment in accordance with the procedures at https://wawf.eb.mil/.

(End of clause)

252.232-7006 Wide Area WorkFlow Payment Instructions.

As prescribed in 232.7004(b), use the following clause:

WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (DEC 2018)

(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 http://www.acq.osd.mil/log/sci/ait.html https://www.acquisition.gov/dfars/252/dfars/part-232-contract-financing#252.232-7003 https://wawf.eb.mil/ https://www.acquisition.gov/dfars/part-232-contract-financing#232.7004 https://www.acquisition.gov/dfars/252/dfars/part-232-contract-financing#252.232-7003 https://www.acquisition.gov/dfars/252/dfars/part-232-contract-financing#252.232-7003 https://www.sam.gov/

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

__TBD_________________________________________________________

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

__TBD_________________________________________________________

(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 item financing, submit a commercial item financing request.

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

(f) [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.

https://wawf.eb.mil/ https://wawf.eb.mil/

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

__TBD_________________________________________________________

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

(End of clause)