<?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_216.104-70"
            outputclass="4"
            ditaarch:DITAArchVersion="1.3"
            class="- topic/topic concept/concept ">
      <title class="- topic/title ">
         <ph props="autonumber" class="- topic/ph ">PGI 216.104-70</ph> Research and development.</title>
      <conbody class="- topic/body  concept/conbody ">
         <p outputclass="List2" class="- topic/p ">(1) <i class="+ topic/ph hi-d/i ">General</i>. There are several categories of research and development (R&amp;D) contracts: research, exploratory development, advanced development, engineering development, and operational systems development (see DFARS <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-235.001"
                  href="235.001.dita#DFARS_235.001">235.001</xref> for definitions). Each category has a primary technical or functional objective. Different parts of a project may fit several categories. The contract type must fit the work required, not just the classification of the overall program.</p>
         <p outputclass="List2" class="- topic/p ">(2) <i class="+ topic/ph hi-d/i ">Research and exploratory development</i>.</p>
         <p outputclass="List3" class="- topic/p ">(i) Price is not necessarily the primary factor in determining the contract type.</p>
         <p outputclass="List3" class="- topic/p ">(ii) The nature of the work to be performed will usually result in a cost-plus award fee, cost-plus fixed fee term, cost-no-fee, or cost-sharing contract.</p>
         <p outputclass="List3" class="- topic/p ">(iii) If the Government and the contractor can identify and agree upon the level of contractor effort required, the contracting officer may select a firm fixed-price level-of-effort contract, except see DFARS <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-235.006"
                  href="235.006.dita#DFARS_235.006">235.006</xref>.</p>
         <p outputclass="List3" class="- topic/p ">(iv) If the Government and the contractor agree that an incentive arrangement is desirable and capable of being evaluated after completion of the work, the contracting officer may use an incentive type contract.</p>
         <p outputclass="List2" class="- topic/p ">(3) <i class="+ topic/ph hi-d/i ">Advanced development</i>.</p>
         <p outputclass="List3" class="- topic/p ">(i) The nature of the work to be performed often results in a cost-plus fixed fee completion type contract.</p>
         <p outputclass="List3" class="- topic/p ">(ii) Contracting officers may select incentive contracts if—</p>
         <p outputclass="List4" class="- topic/p ">(A) Realistic and measurable targets are identified; and</p>
         <p outputclass="List4" class="- topic/p ">(B) Achievement of those targets is predictable with a reasonable degree of accuracy.</p>
         <p outputclass="List3" class="- topic/p ">(iii) Contracting officers should not use contracts with only cost incentives where—</p>
         <p outputclass="List4" class="- topic/p ">(A) There will be a large number of major technical changes; or</p>
         <p outputclass="List4" class="- topic/p ">(B) Actions beyond the control of the contractor may influence the contractor's achievement of cost targets.</p>
         <p outputclass="List2" class="- topic/p ">(4) Engineering development and operational systems development.</p>
         <p outputclass="List3" class="- topic/p ">(i) When selecting contract types, also consider—</p>
         <p outputclass="List4" class="- topic/p ">(A) The degree to which the project is clearly defined, which in turn affects the contractor's ability to provide accurate cost estimates;</p>
         <p outputclass="List4" class="- topic/p ">(B) The need for effort that will overlap that of earlier stages;</p>
         <p outputclass="List4" class="- topic/p ">(C) The need for firm technical direction by the Government; and</p>
         <p outputclass="List4" class="- topic/p ">(D) The degree of configuration control the Government will exercise.</p>
         <p outputclass="List3" class="- topic/p ">(ii) For development efforts, particularly for major defense systems, the preferred contract type is cost reimbursement.</p>
         <p outputclass="List3" class="- topic/p ">(iii) Contracting officers should use fixed-price type contracts when risk has been reduced to the extent that realistic pricing can occur; e.g., when a program has reached the final stages of development and technical risks are minimal, except see DFARS <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-235.006"
                  href="235.006.dita#DFARS_235.006">235.006</xref>.</p>
      </conbody>
   </concept>
</dita>
