QASP-GAP.docx
DOCX document 336 KB Posted
- Solicitation number
- 81214
About this file
This is a Quality Assurance Surveillance Plan (QASP) for a Gap Analysis contract supporting the Next-Generation Overhead Persistent Infrared (Next-Gen OPIR) program at the 402nd Software Engineering Group (SWEG), Warner Robins Air Logistics Complex, Robins Air Force Base, Georgia. The QASP, dated 28 October 2025 and prepared by Matthew Fialkowski, establishes the government's oversight procedures for monitoring contractor performance against contract requirements. The document defines roles and responsibilities for key personnel including the Program Manager (Angela Walker, AFMC 579 SWES/MXDPCD), Contracting Officer (Lasonia Anderson, AFSC/PZIMB), Contracting Officer's Representative (Matthew Fialkowski, AFSC/SWPC), and Quality Assurance Program Coordinator (Garry S. Navas, AFSC/SWPC). The contractor is responsible for performing gap analyses to determine organizational capability differentials and provide support at the SECRET classification level or below.
The surveillance matrix establishes fourteen performance elements tracked through monthly status reports and inspections. Key deliverables include eight Technical Interchange Meetings (TIMs) occurring every three weeks beginning three weeks after contract award, with specific meetings scheduled at intervals through week twenty-five addressing topics from introduction and workspace walkthrough through software development methodology, detailed design planning, tools selection, integration testing, and final review. Additional Contract Data Requirement Lists include Monthly Status Reports (CDRL A0003) due by the seventh calendar day of each month, Presentation Materials (CDRL A0001), and Meeting Minutes (CDRL A0002). The contractor must identify a Program Manager within five business days of contract award. The QASP utilizes performance rating criteria ranging from Exceptional to Unsatisfactory and establishes procedures for Corrective Action Reports (CARs) with thirty-day correction timelines and Performance Assessment Reports (PARs) for minor discrepancies requiring correction within ten days.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| PWS.docx | DOCX document | |
| Solicitation - FA857926R0005.pdf | ||
| CDRL A003.pdf | ||
| CDRL A002.pdf | ||
| CDRL A001.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Quality Assurance Surveillance Plan (QASP)
FOR
GAP Analysis
402nd Software Engineering Group (SWEG) Robins AFB, Georgia
28 OCT 2025
Prepared by:
Matthew Fialkowski
1. Vision The Next Generation Overhead Persistent Infrared (Next-Gen OPIR) program is intended to first augment, then replace, the Space Based Infrared System (SBIRS) program-of-record and will utilize two sets of satellites that provide worldwide initial warning of ballistic missile attacks on the United States using Infrared detection. Next-Gen OPIR GEO (NGG) satellites will have a Geosynchronous Earth Orbit with coverage around the equator. Lockheed Martin is the prime contractor for the NGG Space vehicles with Raytheon as a subcontractor for the satellites’ payload. Next-Gen OPIR Polar (NGP) will consist of satellites providing infrared coverage of the northern polar region. Northrop Grumman is prime for these satellites with Ball Aerospace providing their payloads..
2. Mission The Contractor shall perform Gap Analyses to determine the differential between where the SWEG organizations are and where they need to be to perform this workload. The PWS describes the performance objectives and standards expected of the contractor to provide information necessary for SWEG to produce the gap analysis documents. provide support with Next-Gen OPIR for workloads at or below the SECRET level to the 402d Software Engineering Group (SWEG)/578 Software Engineering Squadron (SWES), Warner Robins Air Logistics Complex (WR-ALC) at Robins Air Force Base (AFB), Georgia. The contractor shall provide all supervision, management, labor, tools, equipment, parts, materials, and transportation to Warner Robins, Georgia. as outlined in the PWS.
3. Purpose This Quality Assurance Surveillance Plan (QASP) is a government-developed document used to determine if the contractor’s performance meets the performance standards contained in the contract. The QASP establishes procedures on how this assessment/inspection process will be conducted. It provides the detailed process for a continuous oversight process:
· What will be monitored
· How monitoring will take place
· Who will be conduct the monitoring
· How monitoring efforts and results will be documented
The contractor is responsible for implementing and delivering performance that meets contract standards using its Quality Control Plan. The QASP 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.
The QASP is not part of the contract nor is it intended to duplicate the contractor’s quality control plan. This QASP is a living document. Flexibility in the QASP is required to allow for an increase or decrease in the level of surveillance necessary based on contractor performance.
The government may provide a copy of the QASP to the contractor to facilitate open communication. In addition, the QASP should recognize that unforeseen or uncontrollable circumstances might occur that are outside the control of the contractor.
Bottom line, the QASP should ensure early identification and resolution of performance issues to minimize impact on mission performance.
4. Authority Authority for issuance of this QASP is provided under Part 46 of the Federal Acquisition Regulation, Inspection of Services clauses, which provide for inspection, acceptance and documentation of the service called for in the contract or order. This acceptance is to be executed by the contracting officer or a duly authorized representative.
5. Roles and Responsibilities The following personnel shall oversee and coordinate surveillance activities.
Program/Project Manager (PM) – The PM provides program oversight. While the PM may serve as a direct conduit to provide Government guidance and feedback to the Contractor on technical matters, they are not empowered to make any contractual commitments or any contract changes on the government’s behalf.
Assigned PM: Angela Walker Organization or Agency: AFMC 579 SWES/MXDPCD Telephone: <enter number> 770-497-6777 Email: angela.walker.8@us.af.mil
Contracting Officer (CO) – The CO shall ensure performance of all necessary actions for effective contracting, ensure compliance with the contract terms, and shall safeguard the interests of the United States in the contractual relationship. The CO shall also ensure that the contractor receives impartial, fair, and equitable treatment under this contract. Determine the final assessment of the contractor’s performance.
Assigned CO: Lasonia Anderson Organization or Agency: AFSC/PZIMB Telephone: 770-468-9510 Email: lasonia.anderson@us.af.mil
Contracting Officer’s Representative (COR) - The COR is responsible for providing continuous technical oversight of the contractor’s performance. The COR will use the QASP to conduct the oversight/surveillance process. The COR shall use PIEE/SPM to accurately document the contractor’s actual performance. The purpose is to ensure that the contractor meets the performance standards contained in the contract. The COR is responsible for reporting early identification of performance problems to the CO. The COR is required to provide an annual performance assessment to the CO which will be used in documenting past performance. The QASP is the primary tool for documenting contractor performance. The COR is not empowered to make any contractual commitments or to authorize any contractual change on the Government’s behalf. Reviews performance prior to execution of options and assists in determining if contract as agreed upon met mission objectives. Documents past performance for input to the Contractor Performance Assessment Reporting System (CPARS).
Assigned COR: Matthew Fialkowski Organization or Agency: AFSC/SWPC Telephone: 801-586-4321 Email: matthew.fialkowski.2@us.af.mil
Contracting Officer’s Representatives Supervisor - Supervises and manages all assigned CORs. Oversees the COR self-nomination process in CORT Tools. The COR Supervisor ensures the COR is trained before performing any COR duties and supports the COR’s performance assessment activities, reviews COR documentation on a regular basis, and evaluates performance of COR duties as part of performance assessment throughout the period of the contract.
Assigned COR Supervisor: Adam Shepherd Organization or Agency: AFSC/SWPC Telephone: 801-586-2016 Email: adam.shepherd@us.af.mil
Lead Contracting Officer’s Representatives (LCOR) – The LCOR tracks monthly surveillance schedules, review all COR monthly status reports. Additionally, the LCOR maintains CAR data base, processes CARs for review, and collaborates with COR Supervisor, COR, and QAPC regarding contractor performance.
Assigned Lead COR: Garry S. Navas Organization or Agency: AFSC/SWPC Telephone: 801-777-4413 Email: Garry.Navas@us.af.mil
Acquisition Management Support Specialist (AMSS) - Serves as the primary SWEG customer representative familiar with the service requirements. AMSS will review contractor performance prior to execution of options. Periodically reviews contract specifications to determine if contract as written meets mission objectives. May provide input to the Contractor Performance Assessment Reporting System (CPARS). Leads multi-functional team contract management reviews.
Assigned AMSS: Gregory Hernandez Organization or Agency: AFSC/SWPA Telephone: 801-775-6701 Email: gregory.hernandez@us.af.mil
Quality Assurance Program Coordinator (QAPC) - The QAPC is appointed to integrate the quality contract requirements into the quality assurance program, act as the liaison between the contracting and functional organizations, and provide training and record keeping IAW MP 5346.103. Ensure consistent guidance is given to customers by QAPC and other functional areas, train CORs and COR management (e.g. COR Supervisor, Functional Commanders/Directors (FC/FD) on the contracting requirements associated with the quality assurance program. Assist, as required, with the evaluation of contractor Quality Control Plans and maintain a record of all COR and COR management training, including refresher training (e.g., QAPC, contracting officer, contract specialist, contract administrator, Defense Acquisition University, or commercial training provider).
Assigned QAPC: Garry S. Navas Organization or Agency: AFSC/SWPC Telephone: 801-777-4413 Email: Garry.Navas@us.af.mil
Contractor Representatives - The following employees of the contractor serve as the contractor’s Program Manager and Task Manager for this contract. (Complete this section after the contract award)
Program Manager - <upon award, enter name> Telephone: <enter number> Email: <enter address>
Task Manager - <upon award, enter name> Telephone: <enter number> Email: <enter address>
Other Key Contract Personnel – <upon award, enter name> Title: <enter number> Telephone: <enter number> Email: <enter address>
6. Performance Requirements and Method of Surveillance
6.1 Contract Surveillance
The goal of the QASP is to ensure that contractor performance is effectively monitored and documented. The COR’s contribution is their professional, non-adversarial relationships with the CO, PM and the Contractor, which enables positive, open and timely communications. The foundation of this relationship is built upon objective, fair, and consistent COR evaluations of contractor performance against contract requirements. The COR uses the methods contained in this QASP to ensure the contractor is in compliance with contract requirements. The COR function is responsible for a wide range of surveillance requirements that effectively measure and evaluate the contractor’s performance. Additionally, this QASP is based on the premise that the Contractor, not the government, is responsible for management and QC/QA actions to successfully meet the terms of the contract. Multi-functional Team Meetings – The Multi-functional team will manage the contract throughout the life of the contract. This team will form a partnership between the government and the contractor to ensure the best possible service is provided for the life of the contract. All performance assessment data will be reviewed at these meetings. If performance improvement is necessary, a plan of action will be created.
6.2 Surveillance Matrix
The Surveillance Matrix (Attachment 1) is the list of performance objectives and standards that must be performed by the contractor. This matrix details the method of surveillance the COR will use to validate and inspect these performance elements. Inspection of each element will be documented in the COR file.
Performance objectives define the desired outcomes. Performance Standards define the level of service required under the contract to successfully meet the performance objective. The inspection methodology defines how, when, and what will be assessed in measuring performance. The Government performs surveillance, using this QASP, to determine the quality of the contractor’s performance as it relates to the performance element standards. The Services Summary should be used to form the foundation of the COR’s inspection checklist.
6.3 Performance Rating Definitions
In evaluating the quality of contractor’s performance, the following performance ratings may be used.
Performance Rating Criteria
| Exceptional |
| Performance meets contractual requirements and exceeds many to the Government’s benefit. The contractual performance of the element or sub-element being assessed was accomplished with few minor problems for which corrective actions taken by the contractor was highly effective. |
| Very Good |
| Performance meets contractual requirements and exceeds some to the Government’s benefit. The contractual performance of the element or sub-element being assessed was accomplished with some minor problems for which corrective actions taken by the Contractor was effective. |
| Satisfactory |
| Performance meets contractual requirements. The contractual performance contains some minor problems for which corrective actions taken by the contractor were satisfactory. Performance meets contractual requirements. The contractual performance of the element or sub-element contains some minor problems for which corrective actions taken by the contractor appear or were satisfactory. |
| Marginal |
| Performance does not meet some contractual requirements. The contractual performance of the element or sub-element being assessed reflects a serious problem for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented. |
| Unsatisfactory |
| Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance of the element or sub-element contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective. |
6.4. Contract Performance Assessment Reporting System (CPARS)
If applicable, CPARs will be initiated annually, documenting contractor performance for this specific contract. More frequent updates may be made as required to document a significant improvement or degradation of the level of contract performance. The COR and Government Program Manager will serve as the Assessing Official Representative(s) and the SWEG Deputy Directors will serve as the Assessing Official for contracts over $1,000,000.00 aggregate.
7. Performance Reporting
7.1 Corrective Action Report (CAR)
CARs will be forwarded to the Lead COR (LCOR) for review and validation; after which the LCOR will forward the CAR to the CO for action (CC COR). A copy will be provided to the Contractor’s representative by the CO. CARs will be corrected within thirty (30) days depending on the complexity of the finding. The Contractor may be allowed up to six (6) months (maximum) to correct a CAR, at the discretion of the CO. The COR will ask the status of the CAR from the CO on a monthly basis. The COR will keep an electronic log of all CARs and will keep a hard copy of CARs in PIEE/SPM.
7.2 Performance Assessment Report (PAR)
PARs will be used to report ALL minor discrepancies. PARs will be generated by the COR. The COR will forward the PAR to the Contractor for corrective action. Contractors will be given ten (10) days to correct PARs unless they have requested an extension. If three (3) minor discrepancies are found, combine them and process a CAR. PARS will also be written to record Contractor successes.
7.3 Customer Complaint Form
The COR must furnish instructions to the customer receiving the contractor’s service. The customer must retain supporting evidence of complaint or feedback. After the COR validates feedback or complaint demonstrating contractor noncompliance, the COR will process a PAR or CAR. ALL Customer Complaint forms WILL BE VALIDTAED by the COR prior to notifying the contractor.
7.4 COR Monthly Surveillance Report
The COR shall use the “COR Monthly Surveillance Report” (see attached) template for their monthly “pre inspection” and for the end of month report using information from Section 7. This information will be submitted into CORTT IAW the required frequency and as directed by the CO.
7.4 Surveillance Matrix
7.4.1 Services Summary Items
| Inspection & PWS Paragraph |
| Performance Objective / Elements |
| Standards / AQL |
| Inspection |
| Calculation / Ratings |
| What |
| How/ Method |
| When/ Freq |
SS# 1
Para: 4
Technical Interchange Meetings (TIMs)
| The Contractor shall host a total of eight (8) Technical Interchange Meetings (TIMs) with the Government team, occurring at a frequency of every 3 weeks, to facilitate open communication, collaboration, and progress updates on the project. |
| Satisfactory when contractor conducts 8 TIMs IAW with Para 4. |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will verify TIMs deliverables as specified in PWS. |
M2
| ASREQ |
| Performance is acceptable when delivery timeline is met 90% of the time. |
SS# 2
Para: 4.1
TIM #1
| The contractor shall provide TIM #1: Introduction with Information Exchange. |
| Satisfactory when contractor provides TIM #1 IAW with Para 4 and 4.1 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will verify TIMs deliverables as specified in PWS. |
M2
| No later than three (3) weeks after contract award. |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS# 3
Para: 4.2
TIM #2
| The contractor shall provide TIM #2: Onsite Walkthrough of Workspace and Requirement Discussion. |
| Satisfactory when contractor provides TIM #2 IAW with Para 4 and 4.2 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will verify TIMs deliverables as specified in PWS. |
M2
| No later than six (6) weeks after contract award. |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS# 4
Para: 4.3
TIM #3
| The contractor shall provide TIM #3: Software Development Approach and Methodology. |
| Satisfactory when contractor provides TIM #3 IAW with Para 4.3 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will verify TIMs deliverables as specified in PWS. |
M2
| No later than nine (9) weeks after contract award. |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS# 5
Para: 4.4
TIM #4
| The contractor shall provide TIM #4: Detailed Design and Development Planning. |
| Satisfactory when contractor provides TIM #4 IAW with Para 4.4 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will verify TIMs deliverables as specified in PWS. |
M2
| No later than twelve (12) weeks after contract award. |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS# 6
Para: 4.5
TIM#5
| The contractor shall provide TIM #5: Software Development Environment and Tools. |
| Satisfactory when contractor provides TIM #4 IAW with Para 4.5 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will verify TIMs deliverables as specified in PWS. |
M2
| No later than fifteen (15) weeks after contract award. |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS #7
Para: 4.6
TIM#6
| The contractor shall provide TIM #6: Onsite Walkthrough and Integration and Testing Planning. |
| Satisfactory when contractor provides TIM #4 IAW with Para 4 and 4.6 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will verify TIMs deliverables as specified in PWS. |
M2
| No later than eighteen (18) weeks after contract award. |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS#8
Para: 7
TIM #7
| The contractor shall provide TIM #7: Finalize Software Development Plan. |
| Satisfactory when contractor provides TIM #4 IAW with Para 4.7 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will verify TIMs deliverables as specified in PWS. |
M2
| No later than twenty-one (21) weeks after contract award. |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS#9
Para: 8
TIM #8
| The contractor shall provide TIM #8: Final Review and Confirmation. |
| Satisfactory when contractor provides TIM #4 IAW with Para 4.8 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will verify TIMs deliverables as specified in PWS. |
M2
| No later than twenty-five (25) weeks after contract award. |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS#10
Para: 6.1.3
Monthly Status Report (MSR)
| The contractor shall provide a Monthly Status Report (CDRL A0003) |
| Satisfactory when contractor provides MSR (CDRL A0003) IAW with Para 6.1.3 |
| The COR and the Government Representatives will approve MSR prior to first submission. |
| The COR will review all MSRs to ensure requirements are met IAW PWS. |
M2 No later than the seventh (7th) calendar day of each month for previous months report.
Performance is acceptable when delivery timeline is met 90% of the time.
SS#11
Para: 4.1-4.8 and 6.1.4
Presentation Materials
| The contractor shall provide a Presentation Materials (CDRL A0001) |
| Satisfactory when contractor provides Presentation Materials (CDRL A0001) IAW with Para 6.1.4 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will review all MSRs to ensure requirements are met IAW PWS. |
M2
| ASREQ |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS#12
Para: 4.1-4.8 and 6.1.4
Meeting Minutes
| The contractor shall provide Meeting Minutes (CDRL A0002) |
| Satisfactory when contractor provides Meeting Minutes (CDRL A0002) IAW with Para 6.1.4 |
| The COR will ensure the contractor is complying with PWS with delivery of Contract Data Requirement Lists A001 and A002. |
| The COR will review all MSRs to ensure requirements are met IAW PWS. |
M2
| ASREQ |
| Performance is acceptable when delivery timeline is met 100% of the time. |
SS#13
Para: 9.1
Contractor Program Manager
| The contractor shall provide a Program Manager (PM). |
| Satisfactory when contractor provides PM IAW Para 9.1 |
| COR will verify Contractor PM. |
| COR and Government Representatives will contact Contractor PM. |
M2
| No later than five business (5) days after the contract award date. |
| Performance is acceptable when PM is identified within timelines. |
SS#14
Para 9.3
Intellectual Property
| The contractor shall permit the Government Limited Rights of the GAP Analysis. |
| Satisfactory when contractor permits Government access IAW PWS Para 9.3.1 and 9.3.2 |
| COR will verify that access is granted. |
| COR will ensure access with Government Representatives. |
| ASREQ |
| Performance is acceptable when all IP, including inventions, works, designs, developments, trade secrets, and other proprietary materials created, developed, or derived in connection with or as a result of this contract shall be the sole and exclusive property of the United States Government. |
| 7.4.2 | Non-Services Summary Items |
| (Applicable to all other requirements in the PWS not included in the Services Summary) |
| Non-SS# & PWS Paragraph |
| Performance Objective / Elements |
| Standards / AQL |
| Inspection |
| Calculation / Ratings |
| What |
| How/ Method |
| When/ Freq |
Inspection Methodologies:
M1: Periodic: Periodic surveillance/inspection is the type of surveillance that is based upon selecting samples for evaluation on other than 100% inspection or on a statistically random basis. Periodic surveillance can be accomplished, weekly, monthly or quarterly using a checklist method.
M2: Inspection of Reports: All reports shall be reviewed upon receipt. The reviewer will report any flaws in the document and categorize the flaws (Editorial, Format, and/or Substance).
M3: Technical Inspection: Surveillance/inspection is the type of surveillance that will be performed as specified on the project schedule by actually looking at the work being done.
M4: Non-Service Summary: All Non-SS items will be done on a random basis, at a 1/12 sampling IAW OO-ALC PMAP instructions, to ensure that all items are inspected during the year.
8. Trafficking in Person
8.1 IAW PGI 22.1703(4) the QASP should describe how the COR will monitor the contractors performance regarding compliance with FAR 52.222-50, Combat trafficking in persons.)
8.2 The Contractor shall comply with FAR 52.222-50, Combating Trafficking in Persons. Additional information about Trafficking in Persons can be found at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons below.
8.3 In accordance with the Defense Contingency COR Handbook section on Combating Trafficking in Persons, the COR must inform the PCO if the Contractor/subcontractor and/or Contractor/subcontractor personnel fail to comply with the requirements of FAR 52.222.50. The PCO must convey the information to DoD Combat Trafficking in Persons (CTIP) Law Enforcement and Support / Office of Under Secretary of Defense (OUSD) Personnel and Readiness (P&R) Defense Human Resources Activity (DHRA).
COR Monthly Surveillance Report
"The information herein is For Official Use Only (FOUO) which must be protected under the Privacy Act of 1974, as amended.”
| Contract #: |
| Contractor: |
| Order |
| COR(s): |
| POP: |
| Date: (date submitted) |
1. Service Summary
| SS# |
| Performance Objective |
| PWS Ref |
| Method of Surveillance |
| Comments |
(Positive or Negative) In Compliance
| Y |
| N |
Non
SS#
| Requirement |
| PWS Ref |
| Method of Surveillance |
| Comments |
(Positive or Negative) In Compliance
| Y |
| N |
CORRECTIVE ACTION REPORT (CAR)
TO: (Contractor / Managers Name)
FROM: (COR)
CAR#:
DATES
DATE PREPARED
RETURNED BY CONTRACTOR
COMPLETED
GOVERNMENT FINDINGS
DESCRIPTION OF NON-COMPLIANCE (Include PWS/SOW/FAR reference of Deficiency)
SIGNATURE OF CONTRACTING OFFICER
CONTRACTOR RESPONSE
| TO: |
| FROM: |
CONTRACTOR RESPONSE AS TO CAUSE, CORRECTIVE ACTION AND ACTIONS TO PREVENT RECURRENCE: ATTACH CONTINUATION SHEET IF NECESSARY.
SIGNATURE OF CONTRACTOR REPRESENTATIVE
DATE
GOVERNMENT RESPONSE TO CONTRACTORS ACTIONS
GOVERNMENT EVALUATION
GOVERNMENT ACTIONS
CLOSE OUT
| NAME-TITLE |
| SIGNATURE |
| DATE |
CONTRACTOR
COR
PCO
CMO/COR, SPF Form 060, version-1, Nov 08 PMAP Attachment A6
Continuation of GOVERNMENT FINDINGS
Continuation of CONTRACTOR RESPONSE
Continuation of GOVERNMENT RESPONSE
CMO/COR, SPF Form 060, version-1, Nov 08 PMAP Attachment A6
PERFORMANCE ASSESSMENT REPORT (PAR)
(If more space is needed, use reverse and identify by number)
| 1. CONTRACT/TASK ORDER NUMBER |
| 2. CONTRACTOR |
| 3. TYPE OF SERVICES |
4. QUALITY ASSURANCE PERSONNEL (QAP) SIGNATURE AND DATE
| 5. QAP PHONE |
| 6. SUSPENSE DATE |
I. PERFORMANCE
7. |_| DEFICIENCY (CHECK ALL BOXES THAT APPLY)
|_| NEW
|_| REPEAT
|_| NO DEFICIENCY NOTED
8. SERVICES SUMMARY or SOW PARAGRAPH ITEM REVIEWED
| 9. BRIEF DESCRIPTION OF DEFICIENCY (IF DEFICIENCY BOX WAS CHECKED) |
| 10. DETAILED PERFORMANCE ASSESSMENT |
II. CONTRACTOR VALIDATION
11. CONTRACTOR REPRESENTATIVE |_| CONCUR |_| NON-CONCUR
12. CORRECTIVE ACTION ESTIMATED COMPLETION DATE
13. CONTRACTOR REPRESENTATIVE CORRECTIVE ACTION AND PREVENTION OF RECURRENCE OR REASON FOR NON-CONCURRENCE OF QAP CITED DEFICIENCY
III. ACTION CORRECTED
14. |_| CONCUR |_| NON-CONCUR QAP SIGNATURE AND DATE
15. QAP REMARKS (REQUIRED)
16. CONTRACTOR REPRESENTATIVE REMARKS
Performance Assessment Report (PAR) Template, Feb 05 (SAF/AQCP)
PERFORMANCE ASSESSMENT REPORT
Continuation Sheet (Number to correspond with applicable Item Number on reverse)
Performance Assessment Report (PAR) Template, Feb 05 (SAF/AQCP)
Performance Assessment Report (PAR) Instructions
Block 1. COR or Quality Assurance Personnel (QAP) enters contract or task order number.
Block 2. QAP enters contractor name.
Block 3. QAP enters type of services.
Block 4. QAP signs and dates.
Block 5. QAP enters telephone number.
Block 6. QAP assigns suspense date for Contractor Representative validation if a deficiency box was checked.
Part I. Contractor Performance
Block 7. QAP checks all boxes that apply.
Block 8. QAP enters Services Summary or Statement of Work (SOW) paragraph item reviewed.
Block 9. QAP enters brief description of deficiency and tracking number if the deficiency box was checked in Block 7. Detailed description will be on Corrective Action Report (CAR).
Block 10. QAP enters a detailed performance assessment if the deficiency box in Block 7 was not checked.
Parts II and III will be used only if a deficiency was documented in Part I.
Part II. Contractor Validation
Block 11. Contractor Representative checks one box in response to QAP cited deficiency. If Concurrence is indicated, Contractor Representative continues to Block 12. If Non-Concurrence is indicated, continue to Block 13 and state reason(s) for Non-Concurrence with QAP cited deficiency and return PAR to QAP.
Block 12. Contractor Representative enters Estimated Completion Date of Corrective Action and continues to Block 13.
Block 13. Contractor Representative details Corrective Action and the Action Taken to Prevent Recurrence or Reason for Non-Concurrence of QAP cited deficiency.
Part III. Deficiency Corrected
Block 14. QAP checks appropriate block, signs, and dates.
Block 15. (Required Entry) QAP remarks regarding the Corrective Action and the Action Taken to Prevent Recurrence. If Non-Concur was checked, this block should be very detailed to explain why.
Block 16. Contractor Representative enters remarks if further discussion is needed about QAP concurrence with Contractor’s Corrective Action and Action Taken to Prevent Recurrence.
Continuation Sheet. The Continuation Sheet is to be used to expand on any information that will not fit in the applicable numbered block.
CUSTOMER COMPLAINT FORM
| Contracted Services Location: Bldg. #: |
| Organization: |
| Contract Noun: |
| Contract #: |
| Time: |
| Date: |
WE DESIRE TO IMPROVE THE QUALITY AND RELIABILITY OF THE CONTRACT LISTED AND APPRECIATE YOUR COMMENTS VIA FEEDBACK REPORTING. PLEASE COMPLETE (PERFORMANCE COMMENTS BELOW AND E-MAIL OR SEND THFORM TO THE QUALITY ASSURANCE EVALUATOR (QAE) ASSIGNED TO THIS CONTRACT.
| EXCEPTIONAL: |
| VERY GOOD: |
| SATISFACTORY: |
| MARGINAL: |
| UNSATISFACTORY: |
Contract Performance Comments:
| NAME/GRADE |
| PHONE: |
INITIATOR'S ORGANIZATION:
SPF FORM 90 Version Aug 10
FOR OFFICIAL USE ONLY
image1.png
File details come from the government source that posted it. Updated .