Table of Contents
Click any column header below to sort by that column.
PGI Paragraph |
MAJCOM |
Paragraph Title |
AFMC |
Procedures |
|
AF |
Assignment of Contract Administration |
|
SMC |
Postaward Conference Arrangements |
(a) See the Contract Administration Tool to help determine whether to retain or delegate contract administration responsibilities to DCMA.
(a) Duties of the MAJCOM Contractor Performance Assessment Reporting System (CPARS) Agency Point of Contact (APOC) may include:
(1) Assistance to subordinate organization CPARS APOC (e.g. training, monitoring and policy implementation);
(2) Coordination and submittal of subordinate organization CPARS APOCs to the Navy CPARS Program Office;
(3) Provide metrics/information as requested by SAF/AQC; and
(4) Review and provide subordinate organization issues to the AF CPARS Focal Point and/or the CPARS Program Management Office (PMO).
(b) Program Executive Officers (PEOs), Center PZ organizations, and Air Force Research Laboratory (AFRL) are encouraged to assign a CPARS APOC who will perform duties outlined in the Guidance for CPARS, paragraph 3.4 for “Agency Point of Contact”.
(c) Assessing Officials (AOs) and Reviewing Officials (ROs) will normally be designated from within the command/activity/office/program that identifies the requirement and is in the best position to evaluate contractor performance. Contracting officers should be included in the evaluation process prior to forwarding the CPAR to the Contractor Representative.
(d) For AFMC system acquisitions, the AO is encouraged to always be the person who has overall responsibility for the acquisition of a system within the approved Acquisition Program Baseline. For programs under the PEO structure, the AO may be at least at the Division Chief or Branch Chief level. The designated RO should be at least one level above the AO. For PEO programs, the PEO will be given the option of acting as the RO. For AFRL, the Commander may delegate this authority to the Center Technology Director. For non-PEO programs, the AO should be at least at the Director level, or a Program Manager (PM) that is a direct report to the Director, consistent with the level at which the program is organized. The designated RO may be at least one level above the AO.
(e) For all other AFMC business sectors the AO should be the technical/functional person who has overall responsibility for, and/or has the most familiarity with the requirement/program/project/task or delivery order. The designated RO may be at least one level above the AO.
(f) Performance evaluations on classified and Special Access Programs (SAP) contracts are not exempt from past performance evaluations and are encouraged to be processed, distributed and maintained in accordance with program security requirements and with AFPD 16-14, Information Protection and AFI 31-401, Information Security Program Management. Classified and SAP CPARs will not be entered into the CPARS Automated Information System (AIS). Only in the case of classified CPARs should paper copies be used for evaluations. (Note: For AFMC, hard copies of SAP CPARs may be provided to HQ AFMC/XRJ.)
(g) Copies of SAP CPARs are encouraged to be marked in accordance with SAF/AO Security Pamphlet 1, Marking Guide for Special Access Required Material, dated November 1997, and written in accordance with National Industrial Security Program Operating Manual Supplement (NISPOM Sup) and the implementers of the NISPOM Supplement.
(a) The contracting officer should ensure conference participants include program personnel representing engineering, program control, production/manufacturing, data, test, software, systems & quality assurance, as appropriate. Whenever possible, preliminary meetings conducted by SMC contracting officers should include the administrative contracting officer assigned to the contract. In addition, weaknesses and risks identified during the evaluation process should be included in the agenda.