Attachment_3_QASP_SOS_HAF_A3S_Revised_5-12-15.doc

Quality Assurance Surveillance Plan

Attachment 3

12 May 2015

Headquarters Air Force, Directorate of Space Operations (HAF/A3S)

Space Operations Support (SOS)

FA7014-15-R-5011

Quality Assurance Surveillance Plan

COMPLIANCE WITH THIS DOCUMENT IS MANDATORY

OPR: HAF/A3S

Reviewed by: HAF/A3S

CHRISTOPHER A. SOLEE

COL SCOTT T. MCLEAN

Contracting Officer Representative

Division Chief, Space Operations

Reviewed by: AFDW/PK Accepted by: AFDW/PK

MICHAEL V. LEE

MELISSA S. TAMAYO

Quality Assurance Program Coordinator Contracting Officer

Pages: 16

TABLE OF CONTENTS

1.0

SCOPE

1.1 Purpose

1.2 Application

1.3 General Policies

2.0

MANAGEMENT LOCATIONS AND KEY PERSONNEL

2.1 OASIS SB Management Locations

2.2 OASIS SB Management Team

2.3 Contractor Key Personnel

3.0

CONTRACT SURVEILLANCE

3.1 Surveillance Methods

3.2 Surveillance Documents

3.3 Assessing Performance

4.0

WIDE AREA WORK FLOW (WAWF)

4.1 Validating Receiving Reports

4.2 Certifying Receiving Reports

4.3 Rejecting Receiving Reports

5.0

CONTRACTING OFFICER REPRESENTATIVE (COR) FOLDER

TABLES

Deliverables

Services Summary

Monthly Performance Rating Definitions

COR Folder Tabs and Contents

ATTACHMENTS

Corrective Action Request (CAR) Template

1.0 SCOPE. The Quality Assurance Surveillance Plan (QASP) is applicable to personnel performing contract surveillance audits in accordance with (IAW) Federal Acquisition Regulation (FAR) Part 46, Quality Assurance; Department of Defense FAR Supplement (DFARS) Subpart and PGI 201.602-2 , Contracting Officer Responsibilities; Air Force FAR Supplement (AFFARS) Mandatory Procedures (MP) 5346-103, Contracting Office Responsibilities, The Quality Assurance Program; Air Force Instruction (AFI) 63-501, Air Force Acquisition Quality Program; and organizational policy. It is designed to provide the Contracting Officer Representative (COR) a systematic surveillance method for each service identified in the Performance Work Statement (PWS) for each Task Order (TO). The owning Functional Director (FD) and COR develop the methods for administering and evaluating TOs issued under the One Acquisition Solution for Integrated Services (OASIS) Small Business Indefinite Delivery/Indefinite Quantity (IDIQ) contract vehicle. The Quality Assurance Program Coordinator (QAPC) and Program Manager (PM) or Contracting Manager (CM), will review these methods, which are then accepted or rejected by the Contracting Officer (CO).

1.1 Purpose. This document defines the surveillance policy, procedures, and associated methods used by CORs for planning, preparing, performing, analyzing, and reporting Contractor performance. This QASP provides a systematic surveillance method to evaluate the services received from the Contractor, and NOT to address the details of how the Contractor accomplishes the work. It provides the detailed process for a continuous oversight process:

· What will be monitored

· How monitoring will take place

· Who will conduct the monitoring

· How monitoring efforts and results will be documented

1.2 Application. This QASP is used by all parties involved with assessing Contractor performance under the TO and is for the use of FDs, CORs and CO. The Contractor may receive a courtesy copy of the QASP in order to facilitate open communication. However, the QASP is not considered as part of the contract. The Contractor is responsible for implementing and delivering performance that meets contract standards using its Quality Control Plan. The QASP is a living document and provides the structure for the Government’s surveillance of the Contractor’s performance to assure that it meets contract standards. It is the Government’s responsibility to be objective, fair and consistent in evaluating contractor performance. Bottom line, the QASP should ensure early identification and resolution of performance issues to minimize impact on mission performance.

1.3 General Policies. Four basic policies serve as the foundation for this Quality Assurance (QA) program: (1) Always coordinate contract actions with the Contracting Officer and QAPC; (2) Foster a teamwork atmosphere between the Contractor and all Government personnel; (3) Emphasize, wherever possible, re-performance, rather than withholding of funds if a Contractor discrepancy is discovered; and (4) Ensure the Contractor’s task order level Quality Control Plan (QCP)/Management Plan, if applicable, is compliant with contractual requirements and capable of identifying/correcting non-conformances and addressed in the deliverables.

2.0 MANAGEMENT LOCATIONS AND KEY PERSONNEL.

2.1 Air Force District of Washington (AFDW)/Strategic Sourcing Division (PKS). The address for the TO Contracting Management is:

1500 West Perimeter Rd (Jones Bldg.), Suite 2720 Joint Base Andrews, MD 20762

2.2 Contracting Management Team.

2.2.1 Contracting Officer. CO duties are detailed in FAR subpart 1.602-2. The CO is the only Government agent authorized to award or modify contracts; therefore, the CO is the only person authorized to contractually obligate the Government. The CO is also the individual who will sign any notifications to Contractors regarding performance issues and accepts Government surveillance methods utilized for each TO. The CO approves/appoints all CORs assigned by the Functional Director/Functional Commander.

The CO can be reached at DSN: 612-6138 or Commercial: 240-612-6138.

2.2.2 Contract Manager (CM) The CM is the Government agent within the contracting office who performs day-to-day administration of the contract. The CM/CA may also be the CO if the person has a warrant.

The CM can be reached at DSN: 612-2996 or Commercial: 240-612-2996.

2.2.3 Program Manager (PM). The PM assists customers with requirements development and definition, PWS modifications, deficiency resolution, and portfolio management.

The PM can be reached at DSN: 612- 6201 or Commercial: 240-612-6201.

2.2.4 Quality Assurance Program Coordinator (QAPC). The QAPC assists the CO and QAM in managing the overall QA program and supports customers in developing and adhering to TO-specific QASPs.

The QAPC can be reached at DSN: 612-6205 or Commercial: 240-612-6205

2.2.5 COR Management: COR Management is the Functional Director/Commander and COR Supervisor (both roles may be performed by one individual). COR Management ensures continuous contract monitoring by a qualified COR and submits COR nomination packages to the CO. Receives contract specific training by the QAPC.

2.2.5.1 The Functional Commander/Functional Director (FC/FD). The FC/FD identifies mission essential services, reviews contract performance documentation submitted by the COR on a regular basis to ensure performance is compatible with contract mission objectives.

2.2.5.2 The COR Supervisor ensures personnel are properly trained and technically qualified to perform COR duties, have no personal conflict of interest, and COR responsibilities are assessed on performance report. The COR Supervisor can be reached at DSN 614-1964 or Commercial 703-614-1964.

2.2.6 Contracting Officer Representative (COR). The COR is ultimately responsible for implementing all QA matters and procedures. COR(s) should be at a level where other duties don’t prevent proper oversight of Contractor performance. The COR must maintain both technical competency and evaluation proficiency in Contractor surveillance procedures. The COR must also have enough knowledge of Contractor activities to properly review and disposition monthly invoices. The COR cannot assume duties until assigned by the requiring agency (FC/FD), completed COR required training (CO/QAPC and CO led training), and appointed by the CO.

2.3 Contractor Key Personnel.

2.3.1 Program Manager. The Contractor’s Program Manager is responsible for the overall execution of the task order. This individual will serve as the focal point for the CM/CO and/or PM assigned to the TO and may interface with the customer, as needed.

2.3.2 Project/Task Lead. The Project/Task Lead is responsible for technical or quality control oversight; this individual may be the Project Manager.

3.0 CONTRACT SURVEILLANCE. The COR function is responsible for a wide range of surveillance requirements that effectively measure and evaluate Contractor performance. The Contractor, not the Government, is responsible for task management and Quality Control (QC) actions to meet the terms of the contract. However, the Government will not rely solely on the Contractor’s quality program and will have a method to oversee the contracting process. The Government does this through the QASP and can inspect or test all services called for by the contract, to the extent practicable, at all times and places, during the term of the contract. The COR contribution is comprised of professional, non-adversarial relationships, which include positive and open communications with the CO, PM, QAPC, and the Contractor. The foundation of this relationship is built upon regular, objective, fair, and consistent COR evaluations of Contractor performance against contract requirements, and the ability to discuss inspection results, trends, and items of mutual interest with the Contractor. The COR uses the methods in this QASP and the PWS to achieve this goal.

3.1 Surveillance Methods. Three primary methods of surveillance will be used under this TO: one hundred percent inspection, periodic audits and customer complaints. Other methods of surveillance must be fully documented and approved by the CO and QAPC before implementation. Information obtained from these activities may be used by the FD/FC to ascertain whether or not Contractor performance is compatible with contract and mission objectives and by the CO for actions relating to the Contractor. One Hundred Percent Inspection. This method will be used for Contractor submissions, products, and deliverables (tangible items). CORs will use the One Hundred Percent Inspection method to evaluate all reports delivered under paragraph 3.2. The COR, with assistance from the FD and CO if necessary, accepts or rejects these products based on the criteria and performance standards as outlined in the Services Summary. The COR also documents all results of inspections actions, and subsequent Contractor re-performance taskings, if applicable.

3.1.1 Periodic Audit. This type of surveillance consists of evaluating products/services not surveilled via one hundred percent inspection or by customer survey, and is implemented at a pre-defined frequency. An example of periodic audit is performing monthly inspections of class training conducted by the Contractor or weekly inspection of a Contractor’s process in developing training manuals.

3.1.2 Customer Survey or Customer Complaint. Although usually not a primary method, this is a valuable supplement to other, more systematic methods of surveillance. For example, in a case where random sampling indicates unsatisfactory service, customer complaints can be used as substantiating evidence. In certain situations, where customers complain consistently when the quality of performance is poor (e.g., dining facilities, custodial services), customer surveys and customer complaints may be a primary surveillance method, and customer satisfaction an appropriate performance standard. In all cases, complaints will be documented, preferably on a standard form. All customer complaints will be forwarded to the COR. Information obtained from customer complaint activities may be used by the CO for actions relating to the Contractor.

3.2 Surveillance Documents.

3.2.1 Deliverables. All deliverables will be reviewed for timeliness, accuracy and format. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last work day prior to the due date.

Table 1

3.2.2 Services Summary. The Services Summary is a list of critical tasks that must be performed by the Contractor, the performance threshold, and the method of surveillance the COR will use to validate/inspect these tasks. Inspection of each task will be documented in the COR folder.

Services Summary Table 2

a) Qualified personnel are on the job at TO start unless previously negotiated by the CO and

b) The mission is not impacted due to position vacancies or personnel qualifications

· 100% inspection. At TO Start, COR verifies personnel present; reports filled positions/vacancies to CM and QAPC

· COR provides status in the first COR report occurring after TO start and in the first COR report occurring after any TO start when issued. Updated in CMS Monthly QA Report

a) Vacancies are filled with qualified personnel within 14 business days of vacancy, unless approved in writing by the COR and

b) There is no mission impact due to position vacancies or unqualified personnel

· Upon personnel departure, COR tracks and reports vacancy to CM

· If vacancies exceed 14 days or impact mission, COR reports non-conformance to CM and QAPC

· Monthly, COR updates vacancy in CMS Monthly QA Report

a)There are zero late submissions for annual tasks AND b)There is no more than one late monthly status report per year

· Monthly, COR performs review of deliverables list (table 1) and validates delivery conformance with Government OPR.

· If delivery is unacceptable, COR reports non-conformance to CM and QAPC

a) 98% of deliverable requirements are met and received on time.

b) Critical information is accurate.

· Monthly, COR performs review of deliverables list (table 1) and validates delivery conformance with Government OPR.

· If delivery is unacceptable, COR reports non-conformance to CM and QAPC

· Monthly, COR updates submittal of deliverables under CMS Monthly QA Report

· If violations and Compromises occur, COR reports non-conformance to CM and QAPC

· Monthly, COR updates compliance in CMS

3.2.3 Surveillance Checklist (Attachment 2). The COR is responsible for developing standard procedures for Surveillance Checklists and may request QAPC assistance; the Surveillance Checklist serves as the guideline for all inspections. As a minimum, the Surveillance Checklist will include the items in the Services Summary and Deliverables Tables. The COR may also add other inspection activities/surveillance items to the Surveillance Checklist, with applicable PWS references, and obtain permission from the QAPC. These items may fluctuate throughout the course of the contract based on customer needs, identified risks, or issues related to Contractor performance. The COR will document all inspections conducted using the Surveillance Checklist and maintain them in the COR folder.

3.2.4 Contractor’s Quality Control Plan (QCP). A Contractor's internal actions, in the form of a QCP, are usually written to satisfy task order requirements for written procedures or to provide direction on how Contractor employees are to perform. Any deviations will be treated as deficiencies/non-conformances and handled IAW paragraph 3.3.3. The COR will review the QCP IAW requirements of the solicitation and subsequent awarded task order. The COR will forward any deficiencies/non-conformances to the QAPC and CM/CO for appropriate action.

3.3 Assessing Performance. CORs must document Contractor performance on each contract, as well as the scope and purpose of any inspections. Documentation will be maintained in the COR’s monthly log. CORs will also assess and rate Contractor performance as it relates to contract requirements. Performance Assessment may take the form of notes in the monthly log, assessment results from the Surveillance Checklist, Non-conformance notifications, quarterly Performance Assessment Reports (PAR) and annual Contract Performance Assessment Reports (CPAR). Each builds on the other and provides a thorough documented history of Contractor performance.

3.3.1 Monthly Logs. The COR shall maintain a monthly log documenting Contractor performance for each month during the performance of the contract. These months should follow the period of performance of the contract. The monthly log should document both good and less than desirable performance issues, concerns, highlights or non-conformances and can be used to document any correspondence with the Contractor. This log serves as the basis for any formal documentation of non-conformances or deficiencies and provides the backbone for formal reports on Contractor performance, such as the quarterly PAR or annual CPARs. The log also provides continuity should COR duties shift in the course of contract performance.

3.3.2 Inspections. The COR may perform inspection/surveillance at any time during contract performance IAW FAR 52.212-4. The COR will retain all audit and inspection documentation until contract closeout, unless otherwise approved by the CO.

3.3.3 Non-conformances and Deficiencies. Audit or Inspection results that fall below contractual standards shall be identified as non-conformances or deficiencies. The COR will notify the contactor IAW para 3.3.3.2 and document all non-conformances in the monthly log, referencing the specific PWS/TO requirement that the Contractor did not meet, document the name of the individual contacted, and date and time of notification. If the Contractor fails to take corrective actions in a reasonable time-frame, the COR will notify the CM/CO and QAPC for further actions.

3.3.3.1 Types of Non-conformance.

3.3.3.1.1 Minor Non-conformance: A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. A minor non-conformance normally does not increase risk to the Government.

3.3.3.1.2 Major Non-conformance: A major non-conformance is a non-conformance that adversely impacts mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. A major non-conformance also increases risk to the Government. An example of increasing risk would be significant number of recurring non-conformances, which indicates inadequate preventive measures or actions, thus lowering the Government’s confidence that quality services will be provided on time and at cost.

3.3.3.2 Non-conformance Notification. If a deficiency is found during inspection of the Contractor’s performance, the COR will determine the type of notification based on the category of the non-conformance (see Table 3) and pursue non-conformance resolution per paragraph 3.4.

TABLE 3 – NON-CONFORMANCE NOTIFICATIONS.

Minor

Corrective Action Request (CAR)

3.3.3.2.1 Corrective Action Requests (CAR) (see Attachment 1). As shown in Table 3, a CAR provides written notification from the Government to the Contractor of minor and major non-conformances. The COR will recommend to the CM/CO and QAPC that a CAR be issued when the situation first occurs. If a CAR is deemed necessary, the QAPC will assist the primary COR in filling out the CAR. The draft CAR will be routed NLT ten duty days after the event to the CO for review and signature with a suspense date for the Contractor’s reply. The CO is the only person who has the authority to issue a CAR to the Contractor. If the Contractor fails to respond by the specified due date, the COR will notify the CO/QAPC for action and annotate the Contractor’s non-responsiveness in the quarterly PAR. If the Contractor fails to resolve the issue as documented in the CAR, the COR should elevate the issue to CO. Corrective/preventive actions initiated and/or completed by the Contractor will be verified by CORs on the scheduled inspection and documented accordingly. The COR will provide a final, signed copy to the CM/CO and QAPC.

3.3.3.2.2 To satisfactorily close-out a CAR, the following criteria must be met: the Contractor must meet the suspense; the corrective action must have already begun; and the Contractor's actions must correct the deficiency and if applicable, be within specified standards.

3.3.3.2.3 If the corrective action is deemed UNSATISFACTORY by the FD and COR, annotate the CAR accordingly and forward it to the CO with a brief explanation, including an estimate of the Government's loss due to the deficient performance. The estimate may account for loss or destruction of property, supplies, or equipment, and hours lost to re-perform the task. If the task cannot be re-performed, indicate the number of hours it ordinarily would have taken to do the task.

3.3.3.2.1 The COR will maintain a non-conformance log documenting all CARs. The log will include the date sent to the Contractor, issue, due date for response and actual response date. If a detailed response is required, include a link to the response and include the response in the applicable COR folder tab.

3.3.4 Monthly Services Summary Reporting – CORs will perform services summary inspections (table 2) and update in CMS monthly.

3.3.5 Quarterly Performance Assessment Report (PAR) (Attachment 3). The COR will accomplish quarterly PARs documenting Contractor performance for the preceding quarterly performance period. This is a critical document giving the CO performance oversight on all services and ensures all products during the quarterly period were provided to the Government IAW all contract and TO requirements. The QAPC will notify/suspense the COR for providing information on the Contractor’s performance. The COR will provide the both QAPC and FD a copy of the completed report.

Quarterly PAR Evaluation Categories. The quarterly PAR will also provide a brief summary of Contractor performance covering, as applicable, the categories in Table 4 below.

TABLE 4 – PERFORMANCE ASSESSMENT REPORT (PAR) EVALUATION CATEGORIES

3.3.5.1 Performance Rating Definitions. The COR rates each of the quarterly PAR categories, as applicable, based on the Contractor’s actual performance during the reporting period (see Table 5 below). These ratings can also be used for inputs to the monthly log and serve as a basis for CPARs. Ratings will not be arbitrary or reflect an emotional assessment of the Contractor’s performance. Any ratings other than ‘Meets Standards’ must be appropriately justified. For instance, if the COR rates the Contractor’s performance as ‘Exceeds Standards,’ the COR must show what PWS was exceeded and how that benefitted the Government.

TABLE 5 – MONTHLY PERFORMANCE RATING DEFINITIONS

or

Specific question is not applicable for evaluated period.

3.3.6 Annual Contract Performance Assessment Reporting System (CPARS) The Contractor Performance Assessment Reporting System (CPARS) http://www.cpars.csd.disa.mil/cparsmain.htm ) is the Department of Defense (DoD) Enterprise Solution for collection of Contractor Past Performance Information (PPI) as required by the Federal Acquisition Regulation (FAR). CPARS is a web-enabled application that collects and manages a library of automated Contractor report cards. An annual CPAR will be written on all OASIS IDIQ contracts and all OASIS task orders that exceed $1M total contract value. The Program Manager on the IDIQ contracts will be designated as the Assessing Official Representative in CPARS; the written assessment in CPARS will begin annually from the start date of the contract and forwarded to the Contract Manager within 60 days of the contract start date anniversary. The COR will provide the OASIS PM objective evidence from previous quarterly PARS, monthly Services Summary, inspection logs, 1st/2nd notices, CARS, and correspondence letters for CPARs assessment. A CPARS quality checklist is available at the following link. http://www.cpars.csd.disa.mil/cparsfiles/pdfs/CPARSQualityChecklist.pdf.

4.0 WIDE AREA WORK FLOW (WAWF). The COR will accept or reject all Receiving Reports submitted by the Contractor in WAWF within 7 days of submittal by the Contractor.

To access the receiving report, log into WAWF, select the Government, Acceptor, Acceptance Folder tab; then type in the contract and delivery order (task order) number. The Shipment Number column in WAWF is the Receiving Report number.

4.1 Validating Receiving Reports. The COR will review and validate all WAWF receiving reports (Shipment Number in WAWF) ensuring that:

· The Contractor submitted a combination invoice/receiving report

· The report reflects the correct contract and TO number

· Beginning and ending dates being billed are stated and accurate

· The correct CLIN(s) is(are) charged for billing period

· A description of the services is provided (Firm Fixed Price, Labor Hour, Travel, Materials

· The correct amount is charged, to include applicable handling rates

· Invoiced travel was pre-approved

· Back-up documentation is attached that includes a Contractor invoice with current and cumulative hours (for FFP LOE contracts) and amounts, as applicable

· A breakout of any other charges, as agreed to by the CO or required by the TO, is attached in WAWF or has been provided to the COR

4.2 Certifying and Accepting Receiving Reports.

4.2.1 Certification of services is ALWAYS performed by the appointed COR. After validation of services is performed by the COR per paragraph 4.1 above, the COR will select the “CQA” (Contract Quality Assurance) button to verify that the invoice was accurate, this step will normally select the Acceptance: button also. If anyone other than the COR (typically the Resource Advisor (RA)) is accepting services for the task order, the COR MUST certify in writing to the acceptor that services have been inspected/validated, the acceptor must then state in the comments block (under Misc. Info tab) that the COR has reviewed, validated and certified services/invoices. In all cases, the COR will retain documentation (electronic or hard copy) showing COR validation and certification, as well as final acceptance of Contractor invoices.

4.2.2 COR Expenditure Log. After certification of an invoice in WAWF, the Primary COR will update the expenditure log documenting/tracking certified invoice expenditures against funds allocated on the contract against each CLIN. The QAPC will provide a template, if requested. Funding belongs to the organization where the COR resides; the COR expenditure log allows the COR to ensure that funds are available for the work performed, to include travel and materials.

4.3 Rejecting Receiving Reports. If a receiving report is rejected in WAWF, the COR will go to the Miscellaneous Info tab to complete the comments block as follows:

· List details regarding all unsatisfactory services or incorrect invoice information

AND

· Instruct the Contractor to contact DFAS to have the invoice rejected back to the Contractor; this will allow the Contractor to make the same correction on both the receiving report and invoice, since combination invoices/receiving reports are required

4.4 The rejecter will then return to the Header tab and click the “Reject to Initiator” block. Anyone other than the COR may reject receiving reports in WAWF, but only when services/invoices have been reviewed and rejected by the COR in writing per the paragraph above. After rejecting the receiving report, e-mail the CM/CO the contract number, receiving report number, and reason for rejection.

5.0 COR FOLDER. The Primary COR will establish and maintain a COR folder for each task order; an electronic version of the folder may be kept, however, must be maintained in an area where both alternate CORs and FC/FD will have access to it. The COR folder must contain the tabs and contents outlined below in Table 5. ALL surveillance records are considered FOR OFFICIAL USE ONLY documents, and must be marked and safeguarded as such. Documentation is kept for the life of the contract and provides necessary continuity should COR duties transition during the course of the contract. The FD/FC and COR will receive instructions from the CO on disposition or archival procedures upon contract completion.

TABLE 6 – COR FOLDER TABS & CONTENTS

CORRECTIVE ACTION REPORT (CAR)

(If more space is needed, use reverse and identify by number)

1. CONTRACTOR

2. CONTRACT NUMBER

3. TYPE OF SERVICES

4. FUNCTIONAL AREA

5. SUSPENSE DATE

6. CONTROL NUMBER

7. DEFICIENCY MAJOR MINOR

FINDING:

FINDING IMPACT:

Please respond with a written corrective action plan that details the corrective action of the cited deficiency, the cause of the deficiency, and actions taken to prevent recurrence by Suspense Date in Block 5. If date was not entered in Block 5, the contractor is not required to provide a response.

8. QUALITY ASSURANCE PERSONNEL (COR)

TYPED NAME AND GRADE

SIGNATURE AND DATE

9. ISSUING AUTHORITY

TYPED NAME AND GRADE

SIGNATURE AND DATE

10. COR RESPONSE TO CONTRACTOR CORRECTIVE ACTION AND ACTION TAKEN TO PREVENT RECURRENCE

11. COR DETERMINATION

ACCEPTED REJECTED

12. CLOSE DATE

Measure

a) Qualified personnel are on the job at TO start unless previously negotiated by the CO

b) The mission is not impacted due to position vacancies or personnel qualifications

a) Vacancies are filled with qualified personnel within 14 business days of vacancy, unless approved in writing by the COR

b) There is no mission impact due to position vacancies or unqualified personnel

a)There are zero late submissions for annual tasks

AND

b)There are no more than one late monthly status report per year

a) 98% of deliverable requirements are met and received on time.

b) Critical information is accurate.

Attachment 3 - Quarterly Performance Assessment Report (PAR) Template:

MEMORANDUM FOR (Customer)

FROM: Mr. Michael Lee, QAPC, AFDW/PKS SUBJECT: Quarterly Performance Assessment Report (PAR), Contract FA7014-15-R-5011

1. This quarterly PAR addresses all activities in support of the Test Resources and Infrastructure Advisory and Assistance Services (A&AS) under the subject contract is for the period 1 Aug 2015 to 31 Jul 2018.

2. Functional Director: Col. Scott T. McLean, Division Chief, HAF/A3S, DSN 614-1964 or Commercial number: 703-614-1964

Contracting Officer Representative (COR): Mr. Christopher A. Solee, HAF/A3S, DSN 697-3529 or Commercial number: 703-697-3529

Alternate COR: TBD

3. Rating Summary: Rate each area as it applies to the reporting period.

(required for Exceeds and Below ratings)

Quality of Product or Services

Schedule

Cost Control

Business Relations

Management of Key Personnel

4. Performance Summary: Summarize performance as it applies to the reporting period. Address any items left open or unresolved from previous reporting period.

Any current or unresolved past issues with the Contractor (performance, personnel, etc.)?

If yes, nature of issue and how the Contractor management controlling and resolving issue(s)

Any CARs issued?

Provide date, notice type and how effectively the Contractor management controlled and resolved issue(s)

Any replacement of personnel or vacancies in staffing?

Provide inclusive dates of vacancies/replacement

Were current, accurate and complete invoices/billing provided?

Provide dates and reason for issue (costing information missing, labor hours incorrect, incorrect CLIN(s), etc.)

//signed//

(FD or COR)