<?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/"
      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)   "
      ditaarch:DITAArchVersion="1.3">
   <concept id="DFARS_PGI_225.7301"
            outputclass="3"
            ditaarch:DITAArchVersion="1.3"
            class="- topic/topic concept/concept ">
      <title class="- topic/title ">
         <ph props="autonumber" class="- topic/ph ">PGI 225.7301</ph> General.</title>
      <conbody class="- topic/body  concept/conbody ">
         <p outputclass="List1" class="- topic/p ">(c)(i) Separately identify known FMS requirements and the FMS customer in solicitations.</p>
         <p outputclass="List3" class="- topic/p ">(ii) For economies of scale and efficiency, combine U.S. and FMS requirements under the same contract whenever possible. It is not in the taxpayer’s interest to concurrently use mixed contract types for the same or similar items.</p>
         <p outputclass="List3" class="- topic/p ">(iii) Clearly identify contracts for known FMS requirements by the case identifier code in section B of the Schedule.</p>
         <p outputclass="List3" class="- topic/p ">(iv) Ensure that the FMS LOA terms and conditions are incorporated into the signed contract.</p>
         <p outputclass="List3" class="- topic/p ">(v) Ensure that the shipping terms for any contract for FMS materiel are stated as free on board (f.o.b.) origin.</p>
         <p outputclass="List3" class="- topic/p ">(vi) For Pseudo LOAs, ensure that the period of performance in the contract is consistent with the period of availability of appropriated funds, as provided by the financial resource manager.</p>
         <p outputclass="List3" class="- topic/p ">(vii) Consistent with the Defense Transportation Regulations (DTR) 4500.9-R-Part II, Cargo Movement, http://www.transcom.mil/dtr/part-ii/, Appendix E, contracting officers shall ensure that contracts involving the acquisition and delivery of FMS materiel comply with the policies, procedures, packaging, labeling, and documentation requirements specified by the DTR.</p>
         <p outputclass="List3" class="- topic/p ">(viii) The Government representative responsible for acceptance shall ensure that the contractor prepares material inspection and receiving reports in compliance with—</p>
         <p outputclass="List4" class="- topic/p ">(A) Appendix F, F-301(b)(15)(iv)(K) for a Wide Area WorkFlow (WAWF) Receiving Report; or</p>
         <p outputclass="List4" class="- topic/p ">(B) F-401(b)(16)(iv)(L) for a paper DD Form 250, Material Inspection and Receiving Report, if an exception to the use of WAWF at <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-232.7003"
                  href="232.7003.dita#DFARS_232.7003">232.7003</xref> applies.</p>
         <p outputclass="List3" class="- topic/p ">(ix) Prior to contract award, contracting officers shall ensure that—</p>
         <p outputclass="List4" class="- topic/p ">(A) If a contracting officer’s representative is assigned, detailed point of contact information (email, phone number with international dialing protocols, and physical and mailing address) shall be clearly visible;</p>
         <p outputclass="List4" class="- topic/p ">(B) Unique country requirements are specified in the contract (i.e., additional documentation requirements for use in country customs clearance (Levy Exemption waiver));</p>
         <p outputclass="List4" class="- topic/p ">(C) Commodity-unique requirements are specified in the contract (i.e., responsibility for obtaining/paying for/affixing active Radio Frequency Identification tags and Transportation Control Number construction/usage); and</p>
         <p outputclass="List4" class="- topic/p ">(D) The FMS Transportation Accounting Code is stated in the contract.</p>
      </conbody>
   </concept>
</dita>
