<?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.604"
            ditaarch:DITAArchVersion="1.2"
            class="- topic/topic concept/concept ">
      <title class="- topic/title ">
         <ph props="autonumber" class="- topic/ph ">204.604</ph> Responsibilities.</title>
      <conbody class="- topic/body  concept/conbody ">
         <p id="PxNPMz" outputclass="List2" class="- topic/p ">(1) The process
for reporting contract actions to FPDS should, where possible, be
automated by incorporating it into contract writing systems.</p>
         <p id="HePzCJ" outputclass="List2" class="- topic/p ">(2) Data in FPDS is stored
indefinitely and is electronically retrievable. Therefore, the contracting
officer may reference the contract action report (CAR) approval
date in the associated Government contract file instead of including
a paper copy of the electronically submitted CAR in the file. Such
reference satisfies contract file documentation requirements of
FAR 4.803(a).</p>
         <p id="KmKfXA" outputclass="List2" class="- topic/p ">(3) By December 15th of each
year, the chief acquisition officer of each DoD component required
to report its contract actions shall submit to the Principal Director, Defense Pricing and Contracting,
its annual certification and data validation results for the preceding
fiscal year in accordance with the DoD Data Improvement Plan requirements
at
               <xref href="https://www.acq.osd.mil/asda/dpc/ce/cap/index.html"
                  format="html"
                  scope="external"
                  class="- topic/xref ">https://www.acq.osd.mil/asda/dpc/ce/cap/index.html</xref>
   .
The Principal Director,
Defense Pricing
and Contracting, will submit a consolidated DoD annual certification
to the Office of Management and Budget by January 5th of each year.</p>
      </conbody>
   </concept>
</dita>
