<?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="DFARS_204.7103-1"
            ditaarch:DITAArchVersion="1.2"
            class="- topic/topic concept/concept ">
      <title class="- topic/title ">
         <ph props="autonumber" class="- topic/ph ">204.7103-1</ph> Criteria for establishing.</title>
      <conbody class="- topic/body  concept/conbody ">
         <p class="- topic/p ">Contracts shall identify the items or services to be acquired as separate contract line items unless it is not feasible to do so.</p>
         <p outputclass="List1" class="- topic/p ">(a) Contract line items shall have all four of the following characteristics; however, there are exceptions within the characteristics, which may make establishing a separate contract line item appropriate even though one of the characteristics appears to be missing—</p>
         <p outputclass="List2" class="- topic/p ">(1) <i class="+ topic/ph hi-d/i ">Single unit price</i>. The item shall have a single unit price or a single total price, except—</p>
         <p outputclass="List3" class="- topic/p ">(i) If the item is not separately priced (NSP) but the price is included in the unit price of another contract line item, enter NSP instead of the unit price;</p>
         <p outputclass="List3" class="- topic/p ">(ii) When there are associated subline items, established for other than informational reasons, and those subline items are priced in accordance with 
               <xref href="204.7104.dita#DFARS_204.7104"
                  base="DFARS-204.7104"
                  outputclass="fm:ParaNumOnly"
                  class="- topic/xref ">204.7104</xref>
            ;</p>
         <p outputclass="List3" class="- topic/p ">(iii) When the items or services are being acquired on a cost-reimbursement contract;</p>
         <p outputclass="List3" class="- topic/p ">(iv) When the contract is for maintenance and repair services (e.g., a labor hour contract) and firm prices have been established for elements of the total price of an item but the actual number and quantity of the elements are not known until performance. The contracting officer may structure these contracts to reflect a firm or estimated total amount for each line item;</p>
         <p outputclass="List3" class="- topic/p ">(v) When the contract line item is established to refer to an exhibit or an attachment (if management needs dictate that a unit price be entered, the price shall be set forth in the item description block and enclosed in parentheses); or</p>
         <p outputclass="List3" class="- topic/p ">(vi) When the contract is an indefinite delivery type contract and provides that the price of an item shall be determined at the time a delivery order is placed and the price is influenced by such factors as the quantity ordered (e.g., 10-99 @ $1.00, 100-249 @ $.98, 250+ @ $.95), the destination, the FOB point, or the type of packaging required.</p>
         <p outputclass="List2" class="- topic/p ">(2) <i class="+ topic/ph hi-d/i ">Separately identifiable.</i> A contract line item must be identified separately from any other items or services on the contract.</p>
         <p outputclass="List3" class="- topic/p ">(i) Supplies are separately identifiable if they have no more than one—</p>
         <p outputclass="List4" class="- topic/p ">(A) National stock number (NSN);</p>
         <p outputclass="List4" class="- topic/p ">(B) Item description; or</p>
         <p outputclass="List4" class="- topic/p ">(C) Manufacturer's part number.</p>
         <p outputclass="List3" class="- topic/p ">(ii) Services are separately identifiable if they have no more than one—</p>
         <p outputclass="List4" class="- topic/p ">(A) Scope of work; or</p>
         <p outputclass="List4" class="- topic/p ">(B) Description of services.</p>
         <p outputclass="List3" class="- topic/p ">(iii) This requirement does not apply if there are associated subline items, established for other than informational reasons, and those subline items include the actual detailed identification in accordance with 
               <xref href="204.7104.dita#DFARS_204.7104"
                  base="DFARS-204.7104"
                  outputclass="fm:ParaNumOnly"
                  class="- topic/xref ">204.7104</xref>
            . Where this exception applies, use a general narrative description instead of the contract item description.</p>
         <p outputclass="List2" class="- topic/p ">(3) <i class="+ topic/ph hi-d/i ">Separate delivery schedule</i>. Each contract line item or service shall have its own delivery schedule, period of performance, or completion date expressly stated (“as required” constitutes an expressly stated delivery term).</p>
         <p outputclass="List3" class="- topic/p ">(i) The fact that there is more than one delivery date, destination, performance date, or performance point may be a determining factor in the decision as to whether to establish more than one contract line item.</p>
         <p outputclass="List3" class="- topic/p ">(ii) If a contract line item has more than one destination or delivery date, the contracting officer may create individual contract line items for the different destinations or delivery dates, or may specify the different delivery dates for the units by destination in the delivery schedule.</p>
         <p outputclass="List2" class="- topic/p ">(4) <i class="+ topic/ph hi-d/i ">Single accounting classification citation</i>.</p>
         <p outputclass="List3" class="- topic/p ">(i) Each contract line item shall reference a single accounting classification citation except as provided in paragraph (a)(4)(ii) of this subsection.</p>
         <p outputclass="List3" class="- topic/p ">(ii) The use of multiple accounting classification citations for a contract line item is authorized in the following situations:</p>
         <p outputclass="List4" class="- topic/p ">(A) A single, nonseverable deliverable to be paid for with R&amp;D or other funds properly incrementally obligated over several fiscal years in accordance with DoD policy;</p>
         <p outputclass="List4" class="- topic/p ">(B) A single, nonseverable deliverable to be paid for with different authorizations or appropriations, such as in the acquisition of a satellite or the modification of production tooling used to produce items being acquired by several activities; or</p>
         <p outputclass="List4" class="- topic/p ">(C) A modification to an existing contract line item for a nonseverable deliverable that results in the delivery of a modified item(s) where the item(s) and modification are to be paid for with different accounting classification citations.</p>
         <p outputclass="List3" class="- topic/p ">(iii) When the use of multiple accounting classification citations is authorized for a single contract line item, establish informational subline items for each accounting classification citation in accordance with 
               <xref href="204.7105.dita#DFARS_204.7105"
                  base="DFARS-204.7105"
                  outputclass="fm:ParaNumOnly"
                  class="- topic/xref ">204.7105</xref>
            .</p>
         <p outputclass="List1" class="- topic/p ">(b)  All subline items and exhibit line items under one contract line item shall be the same contract type as the contract line item.</p>
         <p outputclass="List1" class="- topic/p ">(c)  For a contract that contains a combination of fixed-price line items, time-and-materials/labor-hour line items, and/or cost-reimbursement line items, identify the contract type for each contract line item in Section B, Supplies or Services and Prices/Costs, to facilitate appropriate payment.</p>
         <p outputclass="List1" class="- topic/p ">(d)  Exhibits may be used as an alternative to putting a long list of contract line items in the schedule. If exhibits are used, create a contract line item citing the exhibit's identifier. See <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-204.7105"
                  href="204.7105.dita#DFARS_204.7105">204.7105</xref>.</p>
         <p outputclass="List1" class="- topic/p ">(e) If the contract involves a test model or a first article which must be approved, establish a separate contract line item or subline item for each item of supply or service which must be approved. If the test model or first article consists of a lot composed of a mixture of items, a single line item or subline item may be used for the lot.</p>
         <p outputclass="List1" class="- topic/p ">(f) If a supply or service involves ancillary functions, like packaging and handling, transportation, payment of state or local taxes, or use of reusable containers, and these functions are normally performed by the contractor and the contractor is normally entitled to reimbursement for performing these functions, do not establish a separate contract line item solely to account for these functions. However, do identify the functions in the contract schedule. If the offeror separately prices these functions, contracting officers may establish separate contract line items for the functions; however, the separate line items must conform to the requirements of paragraph (a) of this subsection.</p>
         <p outputclass="List1" class="- topic/p ">(g) Certain commercial items and initial provisioning spares for weapons systems are requested and subsequently solicited using units of measure such as kit, set, or lot. However, there are times when individual items within that kit, set, or lot are not grouped and delivered in a single shipment. This creates potential contract administration issues with inspection, acceptance, and payment. In such cases, solicitations should be structured to allow offerors to provide information about products that may not have been known to the Government prior to solicitation and propose an alternate line item structure as long as the alternate is consistent with the requirements of 204.71, which provides explicit guidance on the use of contract line items and subline items, and with PGI 
               <xref href="PGI_204.71.dita#i1495044"
                  base="i1495044"
                  outputclass="fm:ParaNumOnly"
                  class="- topic/xref ">204.71</xref>
            .</p>
      </conbody>
   </concept>
</dita>
