<?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_215.404-1"
            ditaarch:DITAArchVersion="1.3"
            class="- topic/topic concept/concept ">
      <title class="- topic/title ">
         <ph props="autonumber" class="- topic/ph ">215.404-1</ph> Proposal analysis techniques.</title>
      <conbody class="- topic/body  concept/conbody ">
         <p outputclass="List1" class="- topic/p ">(a)  <i class="+ topic/ph hi-d/i ">General</i>.</p>
         <p outputclass="List3" class="- topic/p ">(i)  Follow the procedures at PGI 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-PGI_PGI_215.404-1"
                  href="PGI_215.404-1.dita#DFARS_PGI_PGI_215.404-1"
                  xtrc="215.404-1">215.404-1</xref>
             for proposal analysis.</p>
         <p outputclass="List3" class="- topic/p ">(ii)  For spare parts or support equipment, perform an analysis of—</p>
         <p outputclass="List4" class="- topic/p ">(A)  Those line items where the proposed price exceeds by 25 percent or more the lowest price the Government has paid within the most recent 12-month period based on reasonably available data;</p>
         <p outputclass="List4" class="- topic/p ">(B)  Those line items where a comparison of the item description and the proposed price indicates a potential for overpricing;</p>
         <p outputclass="List4" class="- topic/p ">(C)  Significant high-dollar-value items.  If there are no obvious high-dollar-value items, include an analysis of a random sample of items; and</p>
         <p outputclass="List4" class="- topic/p ">(D)  A random sample of the remaining low-dollar value items.  Sample size may be determined by subjective judgment, e.g., experience with the offeror and the reliability of its estimating and accounting systems.</p>
         <p outputclass="List1" class="- topic/p ">(b)  <i class="+ topic/ph hi-d/i ">Price analysis for commercial and noncommercial items</i>.</p>
         <p outputclass="List3" class="- topic/p ">(i)  In the absence of adequate price competition in response to the solicitation, pricing based on market prices is the preferred method to establish a fair and reasonable price (see PGI 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-PGI_PGI_215.404-1"
                  href="PGI_215.404-1.dita#DFARS_PGI_PGI_215.404-1"
                  xtrc="215.404-1">215.404-1</xref>
            (b)(i)).</p>
         <p outputclass="List3" class="- topic/p ">(ii)  If the contracting officer determines that the information obtained through market research is insufficient to determine the reasonableness of price, the contracting officer shall consider information submitted by the offeror of recent purchase prices paid by the Government and commercial customers for the same or similar commercial items under comparable terms and conditions in establishing price reasonableness on a subsequent purchase if the contracting officer is satisfied that the prices previously paid remain a valid reference for comparison.  The contracting officer shall consider the totality of other relevant factors such as the time elapsed since the prior purchase and any differences in the quantities purchased (section 853 of the National Defense Authorization Act for Fiscal Year 2016 (Pub. L. 114-92)).</p>
         <p outputclass="List3" class="- topic/p ">(iii)  If the contracting officer determines that the offeror cannot provide sufficient information as described in paragraph (b)(ii) of this section to determine the reasonableness of price, the contracting officer should request the offeror to submit information on—</p>
         <p outputclass="List4" class="- topic/p ">(A)  Prices paid for the same or similar items sold under different terms and conditions;</p>
         <p outputclass="List4" class="- topic/p ">(B)  Prices paid for similar levels of work or effort on related products or services;</p>
         <p outputclass="List4" class="- topic/p ">(C)  Prices paid for alternative solutions or approaches; and</p>
         <p outputclass="List4" class="- topic/p ">(D)  Other relevant information that can serve as the basis for determining the reasonableness of price.</p>
         <p outputclass="List3" class="- topic/p ">(iv)  If the contracting officer determines that the pricing information submitted is not sufficient to determine the reasonableness of price, the contracting officer shall request other relevant information, to include cost data.  However, no cost data may be required in any case in which there are sufficient non-Government sales of the same item to establish reasonableness of price (section 831 of the National Defense Authorization Act for Fiscal Year 2013 (Pub. L. 112-239)).</p>
         <p outputclass="List3" class="- topic/p ">(v)  When evaluating pricing data, the contracting officer shall consider materially differing terms and conditions, quantities, and market and economic factors.  For similar items, the contracting officer shall also consider material differences between the similar item and the item being procured (see FAR 15.404-1(b)(2)(ii)(B) and PGI 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-PGI_PGI_215.404-1"
                  href="PGI_215.404-1.dita#DFARS_PGI_PGI_215.404-1"
                  xtrc="215.404-1">215.404-1</xref>
            (b)(v)).  Material differences are those that could reasonably be expected to influence the contracting officer’s determination of price reasonableness.  The contracting officer shall consider the following factors when evaluating the relevance of the information available:</p>
         <p outputclass="List4" class="- topic/p ">(A)  <i class="+ topic/ph hi-d/i ">Market prices</i>.</p>
         <p outputclass="List4" class="- topic/p ">(B)  <i class="+ topic/ph hi-d/i ">Age of data</i>.</p>
         <p outputclass="List6" class="- topic/p ">(<i class="+ topic/ph hi-d/i ">1</i>)  Whether data is too old to be relevant depends on the industry (e.g., rapidly evolving technologies), product maturity (e.g., stable), economic factors (e.g., new sellers in the marketplace), and various other considerations.</p>
         <p outputclass="List6" class="- topic/p ">(<i class="+ topic/ph hi-d/i ">2</i>)  A pending sale may be relevant if, in the judgement of the contracting officer, it is probable at the anticipated price, and the sale could reasonably be expected to materially influence the contracting officer’s determination of price reasonableness.  The contracting officer may consult with the cognizant administrative contracting officers (ACOs) as they may have information about pending sales.</p>
         <p outputclass="List4" class="- topic/p ">(C)  <i class="+ topic/ph hi-d/i ">Volume and completeness of transaction data</i>.  Data must include a sufficient number of transactions to represent the range of relevant sales to all types of customers.  The data must also include key information, such as date, quantity sold, part number, part nomenclature, sales price, and customer.  If the number of transactions is insufficient or the data is incomplete, the contracting officer shall request additional sales data to evaluate price reasonableness.  If the contractor cannot provide sufficient sales data, the contracting officer shall request other relevant information.</p>
         <p outputclass="List4" class="- topic/p ">(D)  <i class="+ topic/ph hi-d/i ">Nature of transactions</i>.  The nature of a sales transaction includes the information necessary to understand the transaction, such as terms and conditions, date, quantity sold, sale price, unique requirements, the type of customer (government, distributor, retail end-user, etc.), and related agreements.  It also includes warranties, key product technical specifications, maintenance agreements, and preferred customer rewards.</p>
         <p outputclass="List3" class="- topic/p ">(vi)  The contracting officer shall consider catalog prices to be reliable when they are regularly maintained and supported by relevant sales data (including any related discounts, refunds, rebates, offsets, or other adjustments).  The contracting officer may request that the offeror support differences between the proposed price(s), catalog price(s), and relevant sales data.</p>
         <p outputclass="List3" class="- topic/p ">(vii)  The contracting officer may consult with the DoD cadre of experts who are available to provide expert advice to the acquisition workforce in assisting with commercial item and price reasonableness determinations.  The DoD cadre of experts is identified at PGI 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-PGI_PGI_215.404-1"
                  href="PGI_215.404-1.dita#DFARS_PGI_PGI_215.404-1"
                  xtrc="215.404-1">215.404-1</xref>
            (b)(vii).</p>
         <p outputclass="List1" class="- topic/p ">(h)  <i class="+ topic/ph hi-d/i ">Review and justification of pass-through contracts</i>.  Follow the procedures at PGI 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-PGI_PGI_215.404-1"
                  href="PGI_215.404-1.dita#DFARS_PGI_PGI_215.404-1"
                  xtrc="215.404-1">215.404-1</xref>
            (h)(2) when considering alternative approaches or making the determination that the contracting approach selected is in the best interest of the Government, as required by FAR 15.404-1(h)(2).</p>
      </conbody>
   </concept>
</dita>
