QASP.docx

QUALITY ASSURANCE SURVELLIENCE PLAN

FOR

Product Lifecycle Management (PLM) Data Cleansing Requirements

Contract Number: TBD Contractor: TBD

Prepared by

OC-ALC/ENSN

TINKER AFB, OK

29 July 2011

FC/FD_________________________________ Date:__________

Primary COR___________________________ Date:__________

Alternate COR__________________________ Date:__________

QAPC_________________________________ Date:__________

PCO___________________________________ Date:__________

Contractor______________________________ Date:__________

Signature does not signify agreement with the content of this document rather it indicates the Contractor’s cognizance of this document and its content.

INTRODUCTION

This Quality Assurance Surveillance Plan has been developed to evaluate contractor actions while implementing this Performance Work Statement (PWS). It is designed to provide an effective surveillance method of monitoring contractor performance for each listed objective on the Service Delivery Summary (SDS) in the support contract.

The Quality Assurance Surveillance Plan provides a systematic method to evaluate the services the contractor is required to furnish.

This Quality Assurance Surveillance Plan is based on the premise the government desires to maintain a quality standard in operating, maintaining, and repairing facilities and that a service contract to provide the service is the best means of achieving that objective.

The contractor, and not the government, is responsible for management and quality control actions to meet the terms of the contract. The role of the government is quality assurance to ensure contract standards are achieved.

In this contract the quality control program is the driver for product quality. The contractor is required to develop a comprehensive program of inspections and monitoring actions. The first major step to ensuring a “self-correcting” contract is to ensure that the quality control program approved at the beginning of the contract provides the measures needed to lead the contractor to success.

Once the quality control program is approved, careful application of the process and standards presented in the remainder of this document will ensure a robust quality assurance program.

This surveillance plan is developed IAW AFI 63-124 to establish the procedures for monitoring, reporting, and evaluating the sustainment, development, modification and transition performance requirements of the contractor as identified in PWS. Contractor requirements, level of performance, frequency and method of inspection, review responsibilities and reporting requirements follow.

A004 A006 A010 A012 A013

A004 A006 A010 A012 A013

A003 A004 A006 A010 A012 A013

A004 A006 A010 A012 A013

A004 A005 A006 A010 A012 A013

A006 A007 A008 A009 A011

The contractor shall provide, for Government review, all agendas, meeting minutes, and handouts for each proposed review and working group meeting. Microsoft Professional Applications Electronically delivered (email)

A001

As required. The Contractor shall plan and support reviews to allow the Government to examine the Contractor's chosen approach and establish the requirements baseline.

Para 3, I, III, & IV, Schedule of Surveillance paragraphs below.

The contractor shall provide, for Government review, all agendas, meeting minutes, and handouts for each proposed review and working group meeting. Microsoft Professional Applications Electronically delivered (email)

A002

As required. The Contractor shall plan and support reviews to allow the Government to examine the Contractor's chosen approach and establish the requirements baseline, and document action items and each meetings notes.

Para 3, I, III, & IV, Schedule of Surveillance paragraphs below.

Contractor shall provide detail report with all deliverables throughout contract (included on external hard drive), recommendations, lessons learned and tracking information.

A003

A004 A005 A006 A010 A012 A013

A006 A007 A008 A009

Reviews/Technical Interchange Meetings

Program Management Reviews A001 A002 A004 A010 A012 A013

Note: Should 15th of the month fall on Saturday or Sunday, deliverables shall be delivered to AF on the following Monday. Should Monday be a holiday, deliverables shall be delivered to AF on Tuesday.

SURVEILLANCE: The government contracting officer representative (COR) will receive complaints from customers and pass them to the contractor’s quality control inspector (QCI) for correction. Surveillance Methods: 100% Inspection, STANDARD: The contractor shall perform all work required in a satisfactory manner in accordance with the appropriate PWS paragraph. The COR shall not consider the services complete until all deficiencies have been corrected. Customer complaints shall be provided on any services that exceed the thresholds cited above for each performance objective. The COR shall notify the contracting officer for appropriate action in accordance with FAR 52.246-4, Inspection of Services—Fixed, if any of the above performance objectives exceed the limitations cited in the above performance thresholds.

PROCEDURES: The government COR will inspect the performance objective at least monthly to ensure contractor compliance with the appropriate paragraphs of the Performance Work Statement (PWS). Results of inspection will be recorded, noting the date and time of inspection. If inspection indicates unacceptable performance, notify the contract manager and the contract monitor will notify the contractor's Quality Control Inspector (QCI) of the deficiencies for correction. The Contractor shall be given 24 hours after notification to correct the unacceptable performance or the COR may approve additional time if the COR considers additional time appropriate. If deficiencies are not corrected within the required time frame the COR should notify the Contracting Officer for action.

a) Customer Complaint Procedures:

When the contractor’s performance becomes unsatisfactory, the authorized representative will either contact the COR with the relevant information, or provide the COR a properly completed Customer Complaint Record Template, Feb 11 (OC-ALC/ENSN).

b) The COR Customer Complaint Procedures:

1) When the contractor’s performance becomes unsatisfactory, the customers shall either contact the Monitor with the relevant information, or provide the Monitor a properly completed Customer Complaint Record Template, Feb 11 (OC-ALC/ENSN).

2) The Monitor will review the information and validate the complaint.

3) When validated, the Monitor will notify the Contract Administrator and request corrective action. The customer complaint will be used to document/seek resolutions to problems and serve as evidence of unsatisfactory service.

CONTRACT REQUIREMENTS: The Contractor shall establish and use disciplined, comprehensive, systematic program management operations in supporting Product Lifecycle Management (PLM) Cleansing Requirements Performance Work Statement that outlines/defines processes, business rules, tools, training and transition. Establishes contractor activities required to support Product Lifecycle Management (PLM) Cleansing program. The Contractor responsibility includes not only meeting all the requirements defined in Performance Work Statement it includes identifying problems in current Product Lifecycle Management (PLM) Cleansing programs, and provides all materials required that address the problems. The Contractor agrees to work with the Government to resolve any issues that may arise.

1. SURVEILLANCE FOLDER. The Contracting Officer representative (COR) assigned to perform surveillance of Product Lifecycle Management (PLM) and Logistic Transformation Data Cleansing Requirements contract is required to prepare a Surveillance Folder for assigned contract requirements. This folder will have the following divisions by requirement area (requirement defined as sustainment, development, modification and transition):

a. Appointment letter, training record.

b. PWS, Interface Control document, schemas, and other pertinent parts of the contract.

c. Surveillance Plan.

d. Surveillance Reports.

e. Other applicable documentation.

2. LEVEL OF PERFORMANCE EVALUATION. The contractor will be evaluated in the areas of Engineering/Technical Performance, Schedule and Timeliness of Deliveries in each area as identified in PWS. Any discrepancies will be brought to the attention of the Contracting Officer.

3. SCHEDULE OF SURVEILLANCE.

I. Cleanup Accuracy

1. Method of Surveillance: Periodic Surveillance

2. Performance Threshold:

a. Validation of corrective actions to part attributes shall be at least 95% accurate.

3. Inspection Procedures:

a. The COR will collect all reports (Monthly Status Reports) completed during the surveillance period. DI-MGMT-80368

b. The COR will review the reports for costs and expenses during the reporting period. DI-MGMT-81467

c. If the COR determines that the performance threshold is met, no further action will be taken.

d. If the COR determines that the performance threshold is not met, the COR will annotate the discrepancy on the surveillance checklist and collect a get-well plan within 10 working days of receipt of the monthly report. If a get-well plan has not been received within 10 working days, the COR will notify the CO of non-compliance.

II. Customer Satisfaction

1. Method of Surveillance: Valid customer complaint (Customer Complaint Record Template, Feb 11 (OC-ALC/ENSN).

2. Performance Threshold:

a. No more than 3 valid customer complaints per month per Contractor Manpower Equivalent (CME).

3. Inspection Procedures:

a. The COR will collect all customer complaints filed during the surveillance period.

b. The COR will review the complaints for delivery dates and completion of required corrections/edits.

c. If the COR determines that the performance threshold is met, no further action will be taken.

d. If the COR determines that the performance threshold is not met, the COR will annotate the discrepancy on the surveillance checklist and collect a get-well plan within 10 working days of receipt of the monthly report. If a get-well plan has not been received within 10 working days, the COR will notify the CO of non-compliance.

III. Timely Data Delivery

1. Method of Surveillance: Periodic Surveillance

2. Performance Threshold:

a. 95% on time in compliance with the established burn down plan.

3. Inspection Procedures:

a. The COR will collect all reports (Monthly Status/Technical Reports) completed during the surveillance period. DI-MGMT-80368 & DI-MISC-80508

b. The COR will review the reports for delivery dates and completion of required corrections/edits.

c. If the COR determines that the performance threshold is met, no further action will be taken.

d. If the COR determines that the performance threshold is not met, the COR will annotate the discrepancy on the surveillance checklist and collect a get-well plan within 10 working days of receipt of the monthly report. If a get-well plan has not been received within 10 working days, the COR will notify the CO of non-compliance.

IV. Timely Deliverables

1. Method of Surveillance: Periodic Surveillance

2. Performance Threshold:

a. No more than 2 errors are identified per month, per document deliverable. .

3. Inspection Procedures:

a. The COR will collect all reports (Monthly Status/Technical Reports) completed during the surveillance period. DI-MGMT-80368 & DI-MISC-80508

b. The COR will review the reports for delivery dates and completion of required corrections/edits.

c. If the COR determines that the performance threshold is met, no further action will be taken.

d. If the COR determines that the performance threshold is not met, the COR will annotate the discrepancy on the surveillance checklist and collect a get-well plan within 10 working days of receipt of the monthly report. If a get-well plan has not been received within 10 working days, the COR will notify the CO of non-compliance.

V. Performance Management

1. Market Research: Market Research is used as a tool throughout the life of the contract to ensure the requirement remains current with the most efficient and effective assessment methods and techniques of the commercial marketplace.

2. 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.

3. Contract Performance Assessment Reporting System (CPARS): 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 Assessing Official Representative will be the COR; the Assessing Official will be the FC/FD.

4. Performance Metrics: Contractor progress will be evaluated using the monthly report which includes projected and actual financial data, and projected and actual schedule data.

5. Disputes: Every attempt will be made to resolve all disputes arising under this contact/plan using the Alternate Dispute Resolution (ADR) as outlined in FAR 33.214. If no resolution can be made under ADR, the CO will render a Contracting Officer’s final decision.

6. Performance Assessment: The approach, methods and tools the Multi-Functional Team will use to assess the contractor’s performance. Performance assessment is evaluating, assessing, and documenting the contractor’s performance IAW the overall Quality Assurance Surveillance Plan. The premise behind performance assessment is the contractor, not the government, is responsible for managing and ensuring that the contractor’s performance meets the terms of the contract. It is the government’s responsibility to monitor performance and hold the contractor accountable for performance.

Initial Performance Assessment shall be conducted on contract performance and shall take place within 30 days after the contractor assumes full performance responsibilities. Criteria that will be used for this evaluation is;

a) Contractor Management Plan identifying the overall requirements of the PWS.

b) Demonstrate working knowledge of cleansing data and processes to correct and validation errors and deficiencies.

3. TIMELY FEEDBACK TO CONTRACTOR. Timely feedback to contractor on unacceptable performance will be provided by the COTR. Prompt feedback is essential so the contractor can develop and implement a corrective action plan. The contractor’s corrective action plan must be reported to the Contracting Officer for tracking purposes.

PREPARED BY: Jim Wallin OC-ALC/ENSN 405-736-2603 Jimmie.Wallin@Tinker.Af.Mil

LOGISTIC MANAGER: Jim Wallin OC-ALC/ENSN 405-736-2603 TITLE: Product Lifecycle Management (PLM) Data Cleansing Requirements

As of 29 July 2011