<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE dita
  PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
<dita xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/"
      ditaarch:DITAArchVersion="1.2"
      domains="(topic task)                            (topic concept)                            (topic concept glossentry)                            (topic concept glossgroup)                            (topic reference)                            (topic troubleshooting++task) (topic task)                            (topic abbrev-d)                            a(props deliveryTarget)                            (topic equation-d)                            (topic hazard-d)                            (topic hi-d)                            (topic indexing-d)                            (topic markup-d)                            (topic mathml-d)                            (topic pr-d)                            (topic relmgmt-d)                            (topic sw-d)                            (topic svg-d)                            (topic ui-d)                            (topic ut-d)                            (topic markup-d xml-d)                            (topic task strictTaskbody-c)   ">
   <concept id="id2064F0S0NXF"
            outputclass="3"
            ditaarch:DITAArchVersion="1.2"
            class="- topic/topic concept/concept ">
      <title class="- topic/title ">
         <ph props="autonumber" class="- topic/ph ">F-301</ph> Preparation instructions.</title>
      <conbody class="- topic/body  concept/conbody ">
         <p outputclass="List1" class="- topic/p ">(a) General.</p>
         <p outputclass="List2" class="- topic/p ">(1) Preparation instructions and training for the WAWF RR are available at https://wawftraining.eb.mil. The instructions on preparing a WAWF RR are part of the Vendor Training section.</p>
         <p outputclass="List2" class="- topic/p ">(2) Prime contractors can direct subcontractors to prepare and submit documents in WAWF by giving their subcontractors access to WAWF via the creation of a Commercial and Government Entity (CAGE) extension to the prime CAGE.</p>
         <p outputclass="List2" class="- topic/p ">(3) If the contract is in Electronic Data Access (EDA) (DoD’s contract repository), then the WAWF system will automatically populate all available and applicable contract data.</p>
         <p outputclass="List3" class="- topic/p ">(i) When source acceptance is required, WAWF will populate the “Inspect By” with the “Admin by” Department of Defense Activity Address Code (DoDAAC). The vendor shall change the DoDAAC if Government Source Inspection (GSI) is performed at other than the “Admin By.”</p>
         <p outputclass="List3" class="- topic/p ">(ii) Any fields that have been pre-filled may be changed.</p>
         <p outputclass="List3" class="- topic/p ">(iii) WAWF will also verify that CAGE codes are valid and active in the System for Award Management (SAM), and that DoDAACs and Military Assistance Program Address Codes (MAPACs) are valid in Defense Automatic Addressing System (DAAS).</p>
         <p outputclass="List2" class="- topic/p ">(4) WAWF will populate the address information for CAGE codes, DODAACs, and MAPACs from SAM and DAAS. These sites are the DoD definitive sources for address information. Any fields that have been pre-filled may be changed or additional information added.</p>
         <p outputclass="List2" class="- topic/p ">(5) Do not include classified information in WAWF.</p>
         <p outputclass="List1" class="- topic/p ">(b) Completion instructions.</p>
         <p outputclass="List2" class="- topic/p ">(1) CONTRACT NO/DELIVERY ORDER NO.</p>
         <p outputclass="List3" class="- topic/p ">(i) For stand-alone contracts, enter the 13-position alpha-numeric basic Procurement Instrument Identifier (PIID) of the contract. For task and delivery orders numbered in accordance with FAR 4.1603 and DFARS <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-204.1603"
                  href="204.1603.dita#DFARS_204.1603">204.1603</xref>, enter the 13-character order number. The contract or agreement number under which the order was placed may be omitted from the WAWF RR. Alternatively, the contractor may choose to enter the contract number on the WAWF RR in addition to the 13-character order number. If the order has only a four-position alpha-numeric call or order serial number, enter both the 13-position basic contract PIID and the four-position order number.</p>
         <p outputclass="List2" class="- topic/p ">(ii) Except as indicated in paragraph (b)(1)(iii) of this appendix, do not enter supplementary numbers used in conjunction with basic PIIDs to identify—</p>
         <p outputclass="List4" class="- topic/p ">(A) Modifications of contracts and agreements;</p>
         <p outputclass="List4" class="- topic/p ">(B) Modifications to calls or orders; or</p>
         <p outputclass="List4" class="- topic/p ">(C) Document numbers representing contracts written between contractors.</p>
         <p outputclass="List3" class="- topic/p ">(iii) When shipping instructions are furnished and shipment is made before receipt of the confirming contract modification (SF 30, Amendment of Solicitation/Modification of Contract), enter a comment in the Misc. Info Tab to this effect. This will appear in the Comments section of the printed WAWF RR.</p>
         <p outputclass="List2" class="- topic/p ">(2) SHIPMENT NO.</p>
         <p outputclass="List3" class="- topic/p ">(i) The shipment number format requires first three data positions to be alpha, fourth position alpha-numeric and last three positions numeric, e.g., DFAR001 or DAR0001. Any document used as a packing list must include the shipment number information.</p>
         <p outputclass="List4" class="- topic/p ">(A) The prime contractor shall control and assign the shipment number prefix. The shipment number shall consist of three alphabetic characters for each “Shipped From” address. The shipment number prefix shall be different for each “Shipped From” address and shall remain constant throughout the life of the contract. The prime contractor may assign separate prefixes when shipments are made from different locations within a facility identified by one “Shipped From” address.</p>
         <p outputclass="List4" class="- topic/p ">(B) Number the first shipment 0001 for shipments made under the contract or contract and order number from each “Shipped From” address, or shipping location within the “Shipped From” address. Consecutively number all subsequent shipments with the identical shipment number prefix. While shipments should be created sequentially they can be released and accepted out of sequence.</p>
         <p outputclass="List6" class="- topic/p ">(1) Use alpha-numeric serial numbers when more than 9,999 numbers are required. Serially assign alpha-numeric numbers with the alpha in the first position (the letters I and O shall not be used) followed by the three-position numeric serial number. Use the following alpha-numeric sequence:</p>
         <table frame="all" colsep="0" rowsep="0" class="- topic/table ">
            <tgroup cols="1"
                    colsep="0"
                    rowsep="0"
                    outputclass="Table"
                    class="- topic/tgroup ">
               <colspec colnum="1"
                        colname="1"
                        colwidth="100*"
                        colsep="0"
                        class="- topic/colspec "
                        rowheader="headers"/>
               <tbody class="- topic/tbody ">
                  <row rowsep="0" class="- topic/row ">
                     <entry colname="1" class="- topic/entry ">
                        <p class="- topic/p ">A000 through A999 (10,000 through 10,999)</p>
                        <p class="- topic/p ">B000 through B999 (11,000 through 11,999)</p>
                        <p class="- topic/p ">Z000 through Z999 (34,000 through 34,999)</p>
                     </entry>
                  </row>
               </tbody>
            </tgroup>
         </table>
         <p outputclass="List6" class="- topic/p ">(2) When this series is completely used, the shipment number prefix will have to be changed when the series is completely used. WAWF will not allow duplicate shipment numbers to be created against a contract or contract and delivery order.</p>
         <p outputclass="List2" class="- topic/p ">(ii) Reassign the shipment number of the initial shipment where a “Replacement Shipment” is involved (see paragraph (b)(16)(iv)(F) of this appendix).</p>
         <p outputclass="List3" class="- topic/p ">(iii) The prime contractor shall control deliveries and on the final shipment of the contract shall end the shipment number with a “Z.” Where the final shipment is from other than the prime contractor's plant, the prime contractor may elect either to—</p>
         <p outputclass="List4" class="- topic/p ">(A) Direct the subcontractor making the final shipment to end that shipment number with a “Z”; or</p>
         <p outputclass="List4" class="- topic/p ">(B) Upon determination that all subcontractors have completed their shipments, to correct the DD Form 250 (see F-304) covering the final shipment made from the prime contractor's plant by addition of a “Z” to that shipment number.</p>
         <p outputclass="List3" class="- topic/p ">(iv) Contractors follow the procedures in F-305 to use commercial invoices.</p>
         <p outputclass="List2" class="- topic/p ">(3) DATE SHIPPED. Enter the date the shipment is released to the carrier or the date the services are completed. If the shipment will be released after the date of contract quality assurance and/or acceptance, enter the estimated date of release. When the date is estimated, enter an “E” or select an "E" from the drop down menu in the “Estimated” block after the date. Do not delay submission of the WAWF RR for lack of entry of the actual shipping date. Correction of the WAWF RR is not required to show the actual shipping date (see F-303). Once the document is submitted the shipment date cannot be changed.</p>
         <p outputclass="List2" class="- topic/p ">(4) B/L TCN. When applicable, enter—</p>
         <p outputclass="List3" class="- topic/p ">(i) The commercial or Government bill of lading number after “B/L;” WAWF provides the capability to separately and correctly identify the Government Bill of Lading (GBL) from a Commercial Bill of Lading (CBL). An authorized user will select whether the entered bill of lading number is either a GBL number or a CBL number.</p>
         <p outputclass="List3" class="- topic/p ">(ii) The transportation control number must be a 17 alpha/numeric digit min/max field, and WAWF provides the capability to enter two secondary transportation tracking numbers.</p>
         <p outputclass="List2" class="- topic/p ">(5) LINE HAUL MODE. Select the Line Haul Mode of Shipment code from a drop down menu in WAWF.</p>
         <p outputclass="List2" class="- topic/p ">(6) INSPECTION AND ACCEPTANCE POINT. Enter an “S” for Origin or “D” for Destination. In addition to “S” and “D,” WAWF allows acceptance at Other (O). For purposes of conforming to contract, "O" is equivalent to "D". In WAWF, destination acceptance is performed by the “Ship to” DODAAC organization and “Other” permits the acceptance of destination documents at a location other than the “Ship to.” The goods or services will be shipped to one location and the paperwork will be routed to another location for the actual acceptance.</p>
         <p outputclass="List2" class="- topic/p ">(7) PRIME CONTRACTOR/CODE. Enter the prime CAGE code to which the contract was awarded.</p>
         <p outputclass="List2" class="- topic/p ">(8) ADMINISTERED BY/CODE. Enter the DoDAAC code of the contract administration office cited in the contract.</p>
         <p outputclass="List2" class="- topic/p ">(9) SHIPPED FROM/CODE</p>
         <p outputclass="List3" class="- topic/p ">(i) Enter the CAGE or DoDAAC code of the “Shipped From” location. If it is the same as the CAGE code leave blank.</p>
         <p outputclass="List3" class="- topic/p ">(ii) For performance of services line items which do not require delivery of items upon completion of services, enter the code of the location at which the services were performed. As mentioned in (i) above, if identical to the prime CAGE code leave blank.</p>
         <p outputclass="List2" class="- topic/p ">(10) FOB. Enter an “S” for Origin or “D” for Destination as specified in the contract. Enter an alphabetic “O” if the “FOB” point cited in the contract is other than origin or destination.</p>
         <p outputclass="List2" class="- topic/p ">(11) PAYMENT WILL BE MADE BY/CODE. Enter the DoDAAC code of the payment office cited in the contract.</p>
         <p outputclass="List2" class="- topic/p ">(12) SHIPPED TO/CODE. Enter the DoDAAC, MAPAC, or CAGE code from the contract or shipping instructions.</p>
         <p id="i1004433" outputclass="List2" class="- topic/p ">(13) MARKED FOR/CODE. <?FM MARKER [Cross-Ref] OLE_LINK2?><?FM MARKER [Cross-Ref] OLE_LINK1?>Enter the code from the contract or shipping instructions. Only valid DoDAACs, MAPACs, or CAGE codes can be entered. Vendors should use the WAWF “Mark for Rep” and “Mark for Secondary” fields for textual marking information specified in the contract. Enter the three-character project code when provided in the contract or shipping instructions.</p>
         <p outputclass="List2" class="- topic/p ">(14) ITEM NO. Enter the item number used in the contract. Use a valid 4 or 6 character line item number under the Uniform Contract Line Item Numbering System (see 204.71). Line item numbers with 6 characters with numbers in the final two positions are not deliverable or billable.</p>
         <p outputclass="List2" class="- topic/p ">(15) STOCK/PART NUMBER/DESCRIPTION.</p>
         <p outputclass="List3" class="- topic/p ">(i) Enter the following for each line item:</p>
         <p outputclass="List4" class="- topic/p ">(A) The national stock number (NSN) or noncatalog number. If the contract contains NSNs as well as other identification (e.g. part numbers) the contractor should place the NSN information in the Stock Part Number field and the remaining numbers in the line item description field. The data entered in the NSN field must reflect the NSN of the material item being shipped and should be a valid NSN, 13 positions in length. In the "Type" drop-down field, select the corresponding type for the data entered. If no National Stock Number (NSN) or other valid "Type" is available, the word "NONE" may be entered for the Stock/Part Number, with a corresponding "Type" of any value other than NSN selected from the drop-down box.</p>
         <p outputclass="List4" class="- topic/p ">(B) In the description field, if required by the contract for control purposes, enter: the make, model, serial number, lot, batch, hazard indicator, or similar description.</p>
         <p outputclass="List4" class="- topic/p ">(C) The Military Standard Requisitioning and Issue Procedures (MILSTRIP) must be placed on the MILSTRIP Tab, not in the line item description field. Enter the MILSTRIP data for each CLIN when MILSTRIP data is identified in the contract.</p>
         <p outputclass="List3" class="- topic/p ">(ii) For service line items, select SV for “SERVICE” in the type field followed by as short a description as is possible in the description field. Some examples of service line items are maintenance, repair, alteration, rehabilitation, engineering, research, development, training, and testing.</p>
         <p outputclass="List4" class="- topic/p ">(A) For WAWF RRRs, the “Ship To” code is the DoDAAC, MAPAC, or CAGE code from the contract or shipping instructions.</p>
         <p outputclass="List4" class="- topic/p ">(B) For service line items not using a WAWF RRR, the “Ship To” code and the “Unit” shall be filled out. The “Ship To” code is the destination Service Acceptor Code for WAWF. If source inspected and accepted, enter the service performance location as the “Ship To” code.</p>
         <p outputclass="List3" class="- topic/p ">(iii) For all contracts administered by the Defense Contract Management Agency, with the exception of fast pay procedures, enter the gross weight of the shipment.</p>
         <p outputclass="List3" class="- topic/p ">(iv) In the description field enter the following as appropriate (entries may be extended through Block 20).</p>
         <p outputclass="List4" class="- topic/p ">(A) Enter in capital letters any special handling instructions/limits for material environmental control, such as temperature, humidity, aging, freezing, shock, etc.</p>
         <p outputclass="List4" class="- topic/p ">(B) When a shipment is chargeable to Navy appropriation 17X4911, enter the appropriation, bureau control number (BCN), and authorization accounting activity (AAA) number (e.g., 17X4911-14003-104).</p>
         <p outputclass="List4" class="- topic/p ">(C) When the Navy transaction type code (TC), “2T” or “7T” is included in the appropriation data, enter “TC 2T” or “TC 7T.”</p>
         <p outputclass="List4" class="- topic/p ">(D) When an NSN is required by but not cited in a contract and has not been furnished by the Government, the contractor may make shipment without the NSN at the direction of the contracting officer. Enter the authority for such shipment.</p>
         <p outputclass="List4" class="- topic/p ">(E) When Government furnished property (GFP) is included with or incorporated into the line item, enter the letters “GFP.”</p>
         <p outputclass="List4" class="- topic/p ">(F) On shipments of Government furnished aeronautical equipment (GFAE) under Air Force contracts, enter the assignment AERNO control number, e.g., “AERNO 60-6354.”</p>
         <p outputclass="List4" class="- topic/p ">(G) For items shipped with missing components, enter and complete the following:</p>
         <table frame="all" colsep="0" rowsep="0" class="- topic/table ">
            <tgroup cols="1"
                    colsep="0"
                    rowsep="0"
                    outputclass="Table"
                    class="- topic/tgroup ">
               <colspec colnum="1"
                        colname="1"
                        colwidth="100*"
                        colsep="0"
                        class="- topic/colspec "
                        rowheader="headers"/>
               <tbody class="- topic/tbody ">
                  <row rowsep="0" class="- topic/row ">
                     <entry colname="1" class="- topic/entry ">
                        <p class="- topic/p ">“Item(s) shipped short of the following component(s): NSN or comparable identification ________________, Quantity __________, Estimated Value ___________, Authority ______________________________________”</p>
                     </entry>
                  </row>
               </tbody>
            </tgroup>
         </table>
         <p outputclass="List4" class="- topic/p ">(H) When shipment is made of components which were short on a prior shipment, enter and complete the following:</p>
         <table frame="all" colsep="0" rowsep="0" class="- topic/table ">
            <tgroup cols="1"
                    colsep="0"
                    rowsep="0"
                    outputclass="Table"
                    class="- topic/tgroup ">
               <colspec colnum="1"
                        colname="1"
                        colwidth="100*"
                        colsep="0"
                        class="- topic/colspec "
                        rowheader="headers"/>
               <tbody class="- topic/tbody ">
                  <row rowsep="0" class="- topic/row ">
                     <entry colname="1" class="- topic/entry ">
                        <p class="- topic/p ">“These components were listed as shortages on shipment number _____________, date shipped __________________”</p>
                     </entry>
                  </row>
               </tbody>
            </tgroup>
         </table>
         <p outputclass="List4" class="- topic/p ">(I) When shipments involve drums, cylinders, reels, containers, skids, etc., designated as returnable under contract provisions, enter and complete the following:</p>
         <table frame="all" colsep="0" rowsep="0" class="- topic/table ">
            <tgroup cols="1"
                    colsep="0"
                    rowsep="0"
                    outputclass="Table"
                    class="- topic/tgroup ">
               <colspec colnum="1"
                        colname="1"
                        colwidth="100*"
                        colsep="0"
                        class="- topic/colspec "
                        rowheader="headers"/>
               <tbody class="- topic/tbody ">
                  <row rowsep="0" class="- topic/row ">
                     <entry colname="1" class="- topic/entry ">
                        <p class="- topic/p ">“Return to_______________________, Quantity ___________, Item ______________, Ownership (Government/contractor).”</p>
                     </entry>
                  </row>
               </tbody>
            </tgroup>
         </table>
         <p outputclass="List4" class="- topic/p ">(J) Enter the total number of shipping containers, the type of containers, and the container number(s) assigned for the shipment.</p>
         <p outputclass="List4" class="- topic/p ">(K) On foreign military sales (FMS) shipments, enter the special markings, and FMS case identifier from the contract. Also enter the gross weight.</p>
         <p outputclass="List4" class="- topic/p ">(L) When test/evaluation results are a condition of acceptance and are not available prior to shipment, the following note shall be entered if the shipment is approved by the contracting officer:</p>
         <table frame="all" colsep="0" rowsep="0" class="- topic/table ">
            <tgroup cols="1"
                    colsep="0"
                    rowsep="0"
                    outputclass="Table"
                    class="- topic/tgroup ">
               <colspec colnum="1"
                        colname="1"
                        colwidth="100*"
                        colsep="0"
                        class="- topic/colspec "
                        rowheader="headers"/>
               <tbody class="- topic/tbody ">
                  <row rowsep="0" class="- topic/row ">
                     <entry colname="1" class="- topic/entry ">
                        <p class="- topic/p ">“Note: Acceptance and payment are contingent upon receipt of approved test/evaluation results.”</p>
                     </entry>
                  </row>
               </tbody>
            </tgroup>
         </table>
         <p outputclass="List4" class="- topic/p ">The contracting officer will advise—</p>
         <p outputclass="List6" class="- topic/p ">(1) The consignee of the results (approval/disapproval); and</p>
         <p outputclass="List6" class="- topic/p ">(2) The contractor to withhold invoicing pending attachment of the approved test/evaluation results.</p>
         <p outputclass="List4" class="- topic/p ">(M) For clothing and textile contracts containing a bailment clause, enter the words “GFP UNIT VALUE.”</p>
         <p outputclass="List4" class="- topic/p ">(N) When the initial unit incorporating an approved value engineering change proposal (VECP) is shipped, enter the following statement:</p>
         <table frame="all" colsep="0" rowsep="0" class="- topic/table ">
            <tgroup cols="1"
                    colsep="0"
                    rowsep="0"
                    outputclass="Table"
                    class="- topic/tgroup ">
               <colspec colnum="1"
                        colname="1"
                        colwidth="100*"
                        colsep="0"
                        class="- topic/colspec "
                        rowheader="headers"/>
               <tbody class="- topic/tbody ">
                  <row rowsep="0" class="- topic/row ">
                     <entry colname="1" class="- topic/entry ">
                        <p class="- topic/p ">This is the initial unit delivered which incorporates VECP</p>
                     </entry>
                  </row>
                  <row rowsep="0" class="- topic/row ">
                     <entry colname="1" class="- topic/entry ">
                        <p class="- topic/p ">No. _____________________, Contract Modification</p>
                     </entry>
                  </row>
                  <row rowsep="0" class="- topic/row ">
                     <entry colname="1" class="- topic/entry ">
                        <p class="- topic/p ">No. _____________________, dated ______________________</p>
                     </entry>
                  </row>
               </tbody>
            </tgroup>
         </table>
         <p outputclass="List2" class="- topic/p ">(16) QUANTITY SHIPPED/RECEIVED.</p>
         <p outputclass="List3" class="- topic/p ">(i) Enter the quantity shipped, using the unit of measure in the contract for payment. When a second unit of measure is used for purposes other than payment, enter the appropriate quantity in the description field.</p>
         <p outputclass="List3" class="- topic/p ">(ii) On the final shipment of a line item of a contract containing a clause permitting a variation of quantity and an underrun condition exists, the prime contractor shall choose the Ship Advice Code “Z”. Where the final shipment is from other than the prime contractor's plant and an underrun condition exists, the prime contractor may elect to direct the subcontractor making the final shipment to choose the Ship Advice Code “Z”;</p>
         <p outputclass="List3" class="- topic/p ">(iii) When the Government is performing destination acceptance the acceptor should enter actual quantity received in apparent good condition in the “Qty. Accepted” field of the Acceptor Line Item Tab.</p>
         <p outputclass="List2" class="- topic/p ">(17) UNIT OF MEASURE. Enter the abbreviation of the unit measure as indicated in the contract for payment. Where a second unit of measure is indicated in the contract for purposes other than payment or used for shipping purposes, enter the second unit of measure in the description field. Authorized abbreviations are listed in MIL-STD-129, Marking for Shipping and Storage and in the WAWF Unit of Measure Table Link. For example, LB for pound, SH for sheet.</p>
         <p outputclass="List2" class="- topic/p ">(18) UNIT PRICE. When using the WAWF RRR, the unit price is the price of the repair, overhaul, or maintenance service from the contract.</p>
         <p outputclass="List3" class="- topic/p ">(i) The contractor may, at its option, enter unit prices on the WAWF RR, except when the contract has IUID requirements and the receiving report is being processed in WAWF, the unit price must represent the acquisition cost that will be recorded in the IUID registry. Therefore, in such cases, the unit price is required. See DFARS <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-252.211-7003"
                  href="252.211-7003.dita#DFARS_252.211-7003">252.211-7003</xref>, Item Unique Identification and Valuation.</p>
         <p outputclass="List3" class="- topic/p ">(ii) The Contractor shall enter unit prices for each item of property fabricated or acquired for the Government and delivered to a contractor as Government furnished property (GFP). Get the unit price from Section B of the contract. If the unit price is not available, use an estimate. The estimated price should be the contractor's estimate of what the items cost the Government. When the price is estimated, enter</p>
         <p outputclass="List3" class="- topic/p ">“Estimated Unit Price” in the description field. When delivering GFP via WAWF to another contractor, WAWF will initiate a property transfer if the vendor who is initiating the WAWF RR is also registered as a vendor property shipper in WAWF and the vendor receiving the property is also a vendor property receiver in WAWF.</p>
         <p outputclass="List3" class="- topic/p ">(iii) For clothing and textile contracts containing a bailment clause, enter the cited Government furnished property unit value as “GFP UNIT VALUE” in the description field.</p>
         <p outputclass="List3" class="- topic/p ">(iv) For all copies of DD Forms 250 for FMS shipments, enter actual prices, if available. If actual prices are not available, use estimated prices. When the price is estimated, enter an “E” after the price.</p>
         <p outputclass="List2" class="- topic/p ">(19) AMOUNT. WAWF will calculate and populate the amount by multiplying the unit price times the quantity.</p>
         <p outputclass="List2" class="- topic/p ">(20) CONTRACT QUALITY ASSURANCE (CQA).</p>
         <p outputclass="List3" class="- topic/p ">(i) The words “conform to contract” contained in the text above the signature block in the WAWF RR Header Tab relate to quality and to the quantity of the items on the report. Enter notes taking exception in Misc. Info Tab comment field or on attached supporting documents with an appropriate block cross-reference.</p>
         <p outputclass="List3" class="- topic/p ">(ii) When a shipment is authorized under an alternative release procedure, contractors will execute the alternative release procedure in WAWF by including the appropriate indicator in the electronic transaction rather than through inclusion or attachment of the text of the certificate. The alternative release procedure only provides for release of shipment; Government acceptance must still be indicated by a Government official’s signature on the WAWF RR.</p>
         <p outputclass="List3" class="- topic/p ">(iii) When contract terms provide for use of Certificate of Conformance and shipment is made under these terms, contractors will execute Certificates in WAWF by including the appropriate indicator in the electronic transaction rather than through inclusion or attachment of the text of the certificate. Government acceptance must still be indicated by a Government official’s signature on the WAWF RR.</p>
         <p outputclass="List3" class="- topic/p ">(iv) ORIGIN.</p>
         <p outputclass="List4" class="- topic/p ">(A) The authorized Government representative must:—</p>
         <p outputclass="List6" class="- topic/p ">(1) Place an “X” in the appropriate CQA and/or acceptance box(es) to show origin CQA and/or acceptance; and</p>
         <p outputclass="List6" class="- topic/p ">(2) Sign and date.</p>
         <p outputclass="List6" class="- topic/p ">WAWF will enter the typed, stamped, or printed name, title, email address, and commercial telephone number.</p>
         <p outputclass="List4" class="- topic/p ">(B) When fast pay procedures apply, the contractor or subcontractor shall select “FAST PAY” when creating the WAWF RR. When CQA is required, the authorized Government representative shall execute the block as required by paragraph (A).</p>
         <p outputclass="List3" class="- topic/p ">(v) DESTINATION. When CQA and acceptance or acceptance is at destination, the authorized Government representative must—</p>
         <p outputclass="List4" class="- topic/p ">(A) Place an “X” in the appropriate box(es); and</p>
         <p outputclass="List4" class="- topic/p ">(B) Sign and date.</p>
         <p outputclass="List4" class="- topic/p ">WAWF will enter the typed, stamped, or printed name, title, email address, and commercial telephone number.</p>
         <p outputclass="List2" class="- topic/p ">(21) CONTRACTOR USE ONLY. MISC. INFO. Self explanatory.</p>
      </conbody>
   </concept>
</dita>
