<?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_204.7104-1"
            ditaarch:DITAArchVersion="1.3"
            class="- topic/topic concept/concept ">
      <title class="- topic/title ">
         <ph props="autonumber" class="- topic/ph ">204.7104-1</ph> Criteria for establishing.</title>
      <conbody class="- topic/body  concept/conbody ">
         <p class="- topic/p ">Contract subline items provide flexibility to further identify elements within a contract line item for tracking performance or simplifying administration.  There are only two kinds of subline items:  those which are informational in nature and those which consist of more than one item that requires separate identification.</p>
         <p outputclass="List1" class="- topic/p ">(a)  <i class="+ topic/ph hi-d/i ">Informational subline items.</i>
         </p>
         <p outputclass="List2" class="- topic/p ">(1)  This type of subline item identifies information that relates directly to the contract line item and is an integral part of it (e.g., parts of an assembly or parts of a kit).  These subline items shall not be scheduled separately for delivery, identified separately for shipment or performance, or priced separately for payment purposes.</p>
         <p outputclass="List2" class="- topic/p ">(2)  The informational subline item may include quantities, prices, or amounts, if necessary to satisfy management requirements.  However, these elements shall be included within the item description in the supplies/services column and enclosed in parentheses to prevent confusing them with quantities, prices, or amounts that have contractual significance.  Do not enter these elements in the quantity and price columns.</p>
         <p outputclass="List2" class="- topic/p ">(3)  Informational subline items shall be used to identify each accounting classification citation assigned to a single contract line item number when use of multiple citations is authorized (see 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="i1377536"
                  href="204.7103-1.dita#DFARS_204.7103-1">204.7103-1</xref>
            (a)(4)(ii)).</p>
         <p outputclass="List1" class="- topic/p ">(b) <i class="+ topic/ph hi-d/i "> Separately identified subline items</i>.</p>
         <p outputclass="List2" class="- topic/p ">(1)  Subline items will be used instead of contract line items to facilitate payment, delivery tracking, contract funds accounting, or other management purposes.  Such subline items shall be used when items bought under one contract line item number—</p>
         <p outputclass="List3" class="- topic/p ">(i)  Are to be paid for from more than one accounting classification.  A subline item shall be established for the quantity associated with the single accounting classification citation.  Establish a line item rather than a subline item if it is likely that a subline item may be assigned additional accounting classification citations at a later date.  Identify the funding as described in 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="i1377554"
                  href="204.7104-1.dita#DFARS_204.7104-1">204.7104-1</xref>
            (a)(3);</p>
         <p outputclass="List3" class="- topic/p ">(ii)  Are to be packaged in different sizes, each represented by its own NSN;</p>
         <p outputclass="List3" class="- topic/p ">(iii)  Have collateral costs, such as packaging costs, but those costs are not a part of the unit price of the contract line item;</p>
         <p outputclass="List3" class="- topic/p ">(iv)  Have different delivery dates or destinations or requisitions, or a combination of the three; or</p>
         <p outputclass="List3" class="- topic/p ">(v)  Identify parts of an assembly or kit which—</p>
         <p outputclass="List4" class="- topic/p ">(A)  Have to be separately identified at the time of shipment or performance; and</p>
         <p outputclass="List4" class="- topic/p ">(B)  Are separately priced.</p>
         <p outputclass="List2" class="- topic/p ">(2)  Each separately identified contract subline item shall have its own—</p>
         <p outputclass="List3" class="- topic/p ">(i)  Delivery schedule, period of performance, or completion date;</p>
         <p outputclass="List3" class="- topic/p ">(ii)  Unit price or single total price or amount (not separately priced (NSP) is acceptable as an entry for price or amount if the price is included in another subline item or a different contract line item).  This requirement does not apply—</p>
         <p outputclass="List4" class="- topic/p ">(A)  If the subline item was created 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 of the schedule and enclosed in parentheses; or</p>
         <p outputclass="List4" class="- topic/p ">(B)  In the case of indefinite delivery contracts described at 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="i1377536"
                  href="204.7103-1.dita#DFARS_204.7103-1">204.7103-1</xref>
            (a)(1)(vi).</p>
         <p outputclass="List3" class="- topic/p ">(iii)  Identification (e.g., NSN, item description, manufacturer's part number, scope of work, description of services).</p>
         <p outputclass="List2" class="- topic/p ">(3)  Unit prices and extended amounts.</p>
         <p outputclass="List3" class="- topic/p ">(i)  The unit price and total amount for all subline items may be entered at the contract line item number level if the unit price for the subline items is identical.  If there is any variation, the subline item unit prices shall be entered at the subline item level only.</p>
         <p outputclass="List3" class="- topic/p ">(ii)  The unit price and extended amounts may be entered at the subline items level.</p>
         <p outputclass="List3" class="- topic/p ">(iii)  The two methods in paragraphs (b)(3)(i) and (ii) of this section shall not be combined in a contract line item.</p>
         <p outputclass="List3" class="- topic/p ">(iv)  When the price for items not separately priced is included in the price of another contract line or subline item, it may be necessary to withhold payment on the priced contract line or subline item until the included line or subline items that are not separately priced have been delivered.  See the clause at 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="i1380912"
                  href="252.204-7002.dita#DFARS_252.204-7002">252.204-7002</xref>
            , Payment for Contract Line or Subline Items Not Separately Priced.</p>
      </conbody>
   </concept>
</dita>
