Current through November 30, 2024
Section 215.407-5-70 - Disclosure, maintenance, and review requirements(a)Definitions.(1)Acceptable estimating system is defined in the clause at 252.215-7002, Cost Estimating System Requirements.(2)Contractor means a business unit as defined in FAR 2.101.(3)Estimating system is as defined in the clause at 252.215-7002, Cost Estimating System Requirements.(4)Significant deficiency is defined in the clause at 252.215-7002, Cost Estimating System Requirements.(b)Applicability.(1) DoD policy is that all contractors have acceptable estimating systems that consistently produce well-supported proposals that are acceptable as a basis for negotiation of fair and reasonable prices.(2) A large business contractor is subject to estimating system disclosure, maintenance, and review requirements if-(i) In its preceding fiscal year, the contractor received DoD prime contracts or subcontracts totaling $50 million or more for which certified cost or pricing data were required; or(ii) In its preceding fiscal year, the contractor received DoD prime contracts or subcontracts totaling $10 million or more (but less than $50 million) for which certified cost or pricing data were required and the contracting officer, with concurrence or at the request of the ACO, determines it to be in the best interest of the Government (e.g., significant estimating problems are believed to exist or the contractor's sales are predominantly Government).(c)Policy.(1) The contracting officer shall- (i) Through use of the clause at 252.215-7002, Cost Estimating System Requirements, apply the disclosure, maintenance, and review requirements to large business contractors meeting the criteria in paragraph (b)(2)(i) of this section;(ii) Consider whether to apply the disclosure, maintenance, and review requirements to large business contractors under paragraph (b)(2)(ii) of this section; and(iii) Not apply the disclosure, maintenance, and review requirements to other than large business contractors.(2) The cognizant contracting officer, in consultation with the auditor, for contractors subject to paragraph (b)(2) of this section, shall- (i) Determine the acceptability of the disclosure and approve or disapprove the system: and(ii) Pursue correction of any deficiencies.(3) The auditor conducts estimating system reviews.(4) An acceptable system shall provide for the use of appropriate source data, utilize sound estimating techniques and good judgment, maintain a consistent approach, and adhere to established policies and procedures.(5) In evaluating the acceptability of a contractor's estimating system, the contracting officer, in consultation with the auditor, shall determine whether the contractor's estimating system complies with the system criteria for an acceptable estimating system as prescribed in the clause at 252.215-7002, Cost Estimating System Requirements.(d)Disposition of findings -(1)Reporting of findings. The auditor shall document findings and recommendations in a report to the contracting officer. If the auditor identifies any significant estimating system deficiencies, the report shall describe the deficiencies in sufficient detail to allow the contracting officer to understand the deficiencies.(2)Initial determination.(i) The contracting officer shall review all findings and recommendations and, if there are no significant deficiencies, shall promptly notify the contractor, in writing, that the contractor's estimating system is acceptable and approved; or(ii) If the contracting officer finds that there are one or more significant deficiencies (as defined in the clause at 252.215-7002, Cost Estimating System Requirements) due to the contractor's failure to meet one or more of the estimating system criteria in the clause at 252.215-7002, the contracting officer shall- (A) Promptly make an initial written determination on any significant deficiencies and notify the contractor, in writing, providing a description of each significant deficiency in sufficient detail to allow the contractor to understand the deficiency;(B) Request the contractor to respond in writing to the initial determination within 30 days; and(C) Promptly evaluate the contractor's responses to the initial determination, in consultation with the auditor or functional specialist, and make a final determination.(3)Final determination.(i) The contracting officer shall make a final determination and notify the contractor in writing that- (A) The contractor's estimating system is acceptable and approved, and no significant deficiencies remain, or(B) Significant deficiencies remain. The notice shall identify any remaining significant deficiencies, and indicate the adequacy of any proposed or completed corrective action. The contracting officer shall-(1) Request that the contractor, within 45 days of receipt of the final determination, either correct the deficiencies or submit an acceptable corrective action plan showing milestones and actions to eliminate the deficiencies;(2) Disapprove the system in accordance with the clause at 252.215-7002, Cost Estimating System Requirements; and(3) Withhold payments in accordance with the clause at 252.242-7005, Contractor Business Systems, if the clause is included in the contract.(ii) Follow the procedures relating to monitoring a contractor's corrective action and the correction of significant deficiencies in PGI 215.407-5-70(e).(e)System approval. The contracting officer shall promptly approve a previously disapproved estimating system and notify the contractor when the contracting officer determines that there are no remaining significant deficiencies.(f)Contracting officer notifications. The cognizant contracting officer shall promptly distribute copies of a determination to approve a system, disapprove a system and withhold payments, or approve a previously disapproved system and release withheld payments, to the auditor; payment office; affected contracting officers at the buying activities; and cognizant contracting officers in contract administration activities.63 FR 55040, Oct. 14, 1998, as amended at 67 FR 49252 , July 30, 2002; 71 FR 69495 , Dec. 1, 2006; 76 FR 28866 , May 18, 2011; 77 FR 11365 , Feb. 24, 2012; 77 FR 76940 , Dec. 31, 2012