Atch_2_-_SMS-CMS_QASP.pdf

FOR OFFICIAL USE ONLY

QUALITY ASSURANCE SURVEILLANCE PLAN

FOR

UNITED STATES TRANSPORTATION COMMAND

SINGLE MOBILITY SYSTEM

and

COALITION MOBILITY SYSTEM DEVELOPMENT SUPPORT

28 March 2013

APPROVED:

ALAN LEE LISA A. GROSS

SMS / CMS Program Manager Contracting Officer

USTRANSCOM/TCAQ-T USTRANSCOM/TCAQ

1. INTRODUCTION

This Quality Assurance Surveillance Plan (QASP) was developed in accordance with AFI 63- 124, Performance-Based Services Acquisitions (PBSA), for work performed under the Enterprise Project Portfolio Management (EPPM) Support Contract for the United States Transportation Command (USTRANSCOM) PMO at Scott AFB IL. From herein USTC PMO will be referred as PMO. This QASP sets forth the procedures and guidelines to be used by the Government to ensure that the contractor achieves the required performance standards as specified in the Performance Work Statement (PWS). The PWS contains a Delivery Schedule that summarizes performance objectives (service required) and performance thresholds (specific standard) contained within the body of the PWS. The Delivery Schedule does not identify every service required, but only those services considered most important for mission accomplishment. This QASP is based on the premise that the contractor, and not the Government, is responsible for management and quality control actions to meet the terms of the contract. It is recognized that the contractor is not a perfect manager and that unforeseen and uncontrollable problems do occur. Good management and use of an adequate quality control plan will allow the contractor to meet or exceed the performance standards specified in the PWS.

2. PURPOSE

This QASP is designed to accomplish the following:

a. Provide a systematic method to survey and evaluate contractor services to determine conformity with the technical requirements of the contract.

b. Define the roles and responsibilities of participating Government officials.

c. Describe the evaluation methods that will be employed by the Government in assessing the contractor’s performance.

d. Describe the process of performance documentation.

e. Provide copies of the Quality Assurance (QA) monitoring forms that will be used by the Government in documenting and evaluating contractor’s performance.

3. ROLES AND RESPONSIBILITIES

The Government monitors contractor performance on a continuing basis through the services of a surveillance team. The surveillance team consists of the following members: Contracting Officer (CO) and Contracting Officer’s Representative (COR).

3.1. Contracting Officer (CO)

The CO has overall responsibility for contract administration. The CO is responsible for monitoring contract compliance and resolving any and all disagreements regarding interpretation of contract terms and conditions. The primary function of the CO, with regard to the surveillance activity, is to authorize changes to the contract. The CO is the only Government official authorized to revise the contract. Additionally, the CO is responsible for approving the

QASP.

3.2. Contracting Officer’s Representative (COR)

The COR serves as a functional expert and is responsible for monitoring, assessing, recording and reporting the technical performance of the Contractor on a continuous basis. The COR schedules surveillance activity; evaluates and documents performance by the contractor, initiates requests for and evaluates adequacy of the corrective action, and reports contractor performance of contractor requirements. CORs are sufficiently trained to perform the required duties and to ensure their knowledge of the terms and conditions of the contract.

3.2.1. The COR is to be objective, fair, and consistent in evaluating contractor performance against standards.

3.2.2. The COR will notify the CO immediately when an evaluation shows that performance does not meet the standards identified in this QASP.

3.2.3. The COR is required to ensure changes in work are not initiated before a written authorization or modification is issued by the CO.

3.2.4. The COR is responsible for inspection of services and contract deliverables, and for reviewing invoices submitted in Wide Area Workflow (WAWF). The COR must ensure that all services have been performed.

3.2.5 The COR is required to provide an assessment of contractor performance to the contracting officer for input into CPARS.

4. METHODS OF SURVEILLANCE

4.1. Delivery Schedule

The Delivery Schedule provides the expected service objectives (outcomes) that will be tracked to determine whether the outcomes are being achieved at the appropriate levels of performance.

The Government, through the COR, will monitor contractor performance using the surveillance method(s) described below. In determining the evaluation criteria, the Government has considered what the contract specifically calls for, how performance can be surveyed, and if the proposed method of surveillance is adequate to assure the required level of performance has been achieved. Additionally, contractor performance will be a factor affecting application of the plan, i.e., surveillance frequency may be increased or decreased based on contractor demonstrated and documented performance. One or a combination of the following surveillance methods will be used to produce a well-rounded indication of contractor conformance:

a. Sampling (Spot, Periodic and Random Sampling)

b. Third Party Audit

c. Inspection/Review (verification of specific tasks, weekly, monthly, quarterly, biannual, annual)

d. Customer/Government Input

4.1.1. Sampling

This is the most appropriate method for frequently recurring tasks. Random sampling is done to determine whether to accept or reject the contractor’s performance of the total lot of a particular task for a given period of time, using the premise that the statistically selected sample is representative of the entire lot. Sampling may be spot, periodic or random.

4.1.2. Third Party Audits

Third Party Audits will be conducted by an authorized agent of the Government, federal, state, and local agencies (i.e. OSHA, DMV, EPA, Environmental Management etc.).

4.1.3. Inspection/Review

This surveillance type is preferred for those tasks that occur infrequently. It is also used frequently for those tasks having very stringent performance requirements. When this type of surveillance is used, COR must inspect and evaluate the contractor’s performance each time it is performed to determine acceptability.

This type of surveillance consists of the evaluation of samples selected on other than a 100 percent or statistically random basis. The results of periodic surveillance inspections may be used as the basis for actions against the contractor. In such cases the Inspection of Services clause becomes the basis for the contracting officer’s actions. This will be done more frequently at the beginning of the contract, and is expected to decrease as standards are consistently met, but may increase if performance falls below standard.

4.1.4. Customer Inputs

The COR may use customer input to document discrepancies in contractor performance. The contracting officer may use validated customer complaints as the basis for actions against the contractor. In such cases the Inspection of Services clause becomes the basis for the contracting officer’s actions. Under the philosophy of performance-based service contracting, we expect the customer to file complaints directly with the contractor with an automatic copy going to the COR. This allows COR oversight of the contractor’s progress in answering complaints, resolving problems and updating the Quality Control (QC) program, while the contractor is responsible to the customer. When used, customer complaints must follow a formalized procedure.

a. The COR is the primary point of contact for and must receive copies of all customer complaints. AF Form 714, Customer Complaint Record, or a locally devised form may be used, but all complaints and any resulting resolution must be documented with the information required on AF Form 714. Customer complaint forms become a permanent part of the COR surveillance records.

b. The COR will check customer complaints to ensure resolution of the deficiency and revision of QC program to prevent recurrence.

4.1.5. Management Review

Methods of surveillance can change after contract award based on acceptance of a contractor’s proposed Quality Control Program or agreement that establishes the metrics to be used. When metrics are used as a method of surveillance through the partnering process, they may be developed after contract award, but prior to the performance start date.

4.1.6. Non-Delivery Schedule Items

For required tasks not shown on the Delivery Schedule, including all other tasks in the PWS and any referenced documents, the Government still retains the right to inspect any item included in the contract in accordance with Federal Acquisition Regulation (FAR) Part 46, Inspection of Services clauses. Inspection of these services will be performed in the same general manner as periodic surveillance items mentioned above. The results of these inspections are documented and, if necessary, are provided to the CO for action. Should a discrepancy be observed, the CO will handle each documented discrepancy on a case-by-case basis.

5. EVALUATION METHODOLOGY

This QASP comprehensively guides the surveillance team's activities and has been developed in a format to ensure ease of understanding and implementation. For each performance objective (service required) in the Delivery Schedule, the specific method(s) of surveillance, performance thresholds (standards), sampling procedures, inspection procedures, and detailed objective task descriptors are shown in the QAS Summary in Attachment 1. The methodology described in the chart shall be used as the basis for performing surveillance of the respective performance objectives.

5.1. Established Procedures

Each contractor assessment shall follow an established procedure for surveillance, recording, reporting and follow-up, outlined as follows:

a. The frequency of surveillance will be in accordance with the COR Schedule.

b. Surveillance will be performed in accordance with Attachment 1 and results/comments recorded.

c. Performance/non-performance for a particular task will be entered chronologically by the

COR on a historical log of surveyed performance. If no deficiency exists in contractor performance for this element, no further action is required.

d. If contractor performance is deficient, the course of action is dependent on the severity/impact/frequency of the non-performance. Re-performance is the first action to resolve deficiencies. When the COR determines a deficiency is not government caused, an AF Form 802, Contract Discrepancy Report (CDR) is initiated. The COR completes blocks 1 through 6 of the form and sends it to the CO. The CO must evaluate the CDR and, if appropriate, sign and send it to the contractor. The contractor must complete blocks 9 and 10 according to the requirements of the contract and return it to the CO within five calendar days of receipt. Upon receipt of the contractor’s response, the CO, in consultation with the COR, must evaluate the contractor’s response and take the appropriate action. The CO must document the evaluation (in block 11) and action taken (in block 12) on the CDR.

e. When corrective action is reported by the contractor, the COR will follow up with additional surveillance to verify implementation.

5.2. Conversation Record

Conversation Record, DOD Optional Form 271, may be used throughout this process to effectively document program issues and concerns addressed with the contractor and Government points of contact. This provides a method to keep QA personnel informed of the status of issues and concerns.

6. DOCUMENTATION

All surveillance activities must be documented to provide the required audit trail to justify Government acceptance and payment. The Documented Audit Trail of the Surveillance (DAS) activities is required by FAR 46.104(c), Contract Administration Office Responsibilities, which states, “Maintain, as part of the performance records of the contract, suitable records reflecting,

(1) The nature of Government contract quality assurance actions, including, when appropriate, the number of observations made and the number and type of defects; and

(2) Decisions regarding the acceptability of the products, the processes, and the requirements, as well as action to correct defects.”

All documentation resulting from surveillance is made a permanent part of the contract file. The COR must keep the documentation files during the term of the contract and either monthly or at the conclusion of the contract (as directed by the CO), transfer the files to the CO for inclusion in the official contract file. It is the responsibility of the COR to establish and maintain this information in a DAS Folder. The DAS folder(s) should include as a minimum:

a. Contract, including Modifications

b. Task Orders, including Modifications

c. Quality Assurance Surveillance Plan

d. COR Letter of Designation

e. Invoices

f. Surveillance Records

1) Written report of all inspections and timelines of deliverables

2) Written report of any deficiency

3) Any other written documentation relation to contract performance

g. General Correspondence

ATTACHMENT 1 - QUALITY ASSURANCE SURVEILLANCE SUMMARY

PWS

Para

Performance Objective

Performance Threshold Surveillance Method

1.4.2.

1.4.5

System Releases 100% of software shall pass J6-OIP security scans, GWT, and UAT prior to Government acceptance.

Inspection/Review to verify compliance IAW

PWS.

1.4.8 Security

Documentation

90% of draft documents delivered by the dates specified in the deliverable table.

90% of final documents delivered by the dates specified in the deliverable table and the rest NLT 10 days.

Inspection/Review to verify compliance IAW

PWS.

1.4.3 Fusion Center

Operations Support

95% of requests (filters, force movement trackers, etc.) shall be created or modified within 1 business day and the rest shall be completed within 3 business days. In the event a request is too large to be completed within 3 business days, an extension may be granted after coordination with the

COR.

Inspection/Review to verify compliance IAW

PWS.

1.4.3.3 Account

Management

90% of the account creation shall take place within 2 business days of request and the rest shall take place within 5 business days of request. 90% of the account deletion shall take place within 1 business day after request.

Inspection/Review to verify compliance IAW

PWS.

1.4.4.1 Help Desk

Support

Contact the user by telephone within 15 minutes 90% of the time and within 30 minutes the rest of the time. Respond to on-site assistance requests within 1 hour 90% of the time and the rest within 1.5 hours.

Inspection/Review to verify compliance IAW

PWS.

1.4.2.2.1.5 CMS Availability

/ System Performance

CMS shall be available 97.7% of the time Inspection/Review to verify compliance IAW

PWS.

1.4.2. System Releases 100% of software shall pass J6-OIP

security scans, GWT, and UAT prior to Government acceptance.

Inspection/Review to verify compliance IAW

PWS.

1.4.3 Operations

Support

90% of the Coalition creation or deletion shall take place within 1 business day of J3 approval and the rest shall take place within 3 business days of request.

Inspection/Review to verify compliance IAW

PWS.

The following items will be utilized for evaluation of performance during the duration of this contract.

1.4.3.8 Account

Management

90% of the account creation shall take place within 2 business days of request and the rest shall take place within 5 business days of request. 90% of the account deletion shall take place within 1 business day after request.

Inspection/Review to verify compliance IAW

PWS.

1.4.8 Security

Documentation

90% of draft documents delivered by the dates specified in the deliverable table.

90% of Final documents delivered by the dates specified in the deliverable table and the rest NLT 10 days.

Inspection/Review to verify compliance IAW

PWS.

1.4.4.2 Help Desk

Support

Respond to requests within 1 hour 90% of the time and the rest within 1.5 hours.

Inspection/Review to verify compliance IAW

PWS.

ATTACHMENT 2 – SAMPLE DISCREPANCY STATUS REPORT

DISCREPANCY STATUS REPORT

MEMORANDUM FOR: USTRANSCOM/TCAQ

Attn: _______________Contracting Officer

FROM: USTCAQ-

508 Scott Dr

Scott AFB, IL 62225-5302

SUBJ: Single Mobility System (SMS) Support Performance Analysis Discrepancy Status Report - (Month)

1. Period Covered: (First to last day of the reporting period, i.e. 1-31 October 2007)

2. Area Covered: (Performance Objective, PWS paragraph, Task Descriptor, i.e. Support Desk, 1.2.1.1..)

3. Overview of Performance:

a. Summary - (Summary of what was done by the COR to assure contract compliance, i.e. audits, data review, and surveillance)

b. Contract Discrepancy Reports (CDRs) - List all CDRs documented during the reporting period. Provide status of all open CDRs. Attach copies of CDRs to the monthly report.)

c. Corrective Action Follow Up - (Report any follow-up actions performed during the reporting period.)

4. Performance Analysis: (State your analysis of the contractor's performance.) Include positive and negative areas.

5. Areas of Concern: (Identify in narrative form ANY problem(s) or potential problem areas which may impact contract performance to PWS requirements or any aspect of the program.)

6. COR O&M Status: (Indicate current COR listing and their O&M status - Phases I and II;

and any information regarding COR changes planned - new personnel requiring training, etc.)

JOHN Q. PUBLIC

Contracting Officer’s Representative (COR)

Attachment:

CDRs