Attachment_0010R1_PASS-SB_QASP_3February2016.pdf

W15QKN-16-R-0027

Section J, Attachment 0010

(3 February 2016)

QUALITY ASSURANCE SURVEILLANCE PLAN

For

PROGRAM AND SYSTEMS SUPPORT-SMALL BUSINESS (PASS-SB)

Reviewed By:

Requiring Activity

Contracting Officer

PASS-SB QASP 3 February 2016 W15QKN-16-R-0027

1.0 INTRODUCTION

1.1. Purpose. In accordance with FAR 46.103 the purpose of the Quality Assurance Surveillance Plan (QASP) is to identify the methods and procedures the Government will use to evaluate contractor performance while concurrently determining the contractor is meeting the mission essential elements of the Performance Work Statement (PWS). The QASP is designed to provide an effective surveillance method by monitoring contractor performance for each listed performance objective in the Performance Requirements Summary (See Section 7).

1.1.1.The QASP provides a systematic method to evaluate the services the contractor is required to perform as specified in the PWS and the contract proposal.

1.1.2.The QASP is developed by the requiring activity. It is designed to provide direction to personnel performing contractor surveillance activities. Personnel surveying the contract terms and conditions and PWS requirements will periodically review the QASP throughout the life of the contract.

2.0. ROLES AND RESPONSIBILITIES.

2.1. Government. The role of the Government in quality assurance is to ensure the contractor is performing in accordance with the contract requirements and contract standards are achieved.

2.2. Contracting Officer. The Contracting Officer (KO) is responsible for safeguarding the interests of the United States Government in contractual relationships. Only the KO is authorized to bind the Government and then, only to the extent of the authority entrusted to them through the issuance of a warrant.

2.2.1. The KO designates authority for inspection and/or acceptance responsibilities to the Contracting Officer Representative (COR) – or delegates authority to another certified acquisition professional - in accordance with the FAR/DFARS. This documented authority allows the COR or other certified acquisition professionals to act on the KO’s behalf.

2.2.2. The KO informs the contractor of the names, duties, and limitations of authority for all quality assurance personnel assigned to the contract.

2.3. Contracting Officer Representative (COR). The COR when designated:

2.3.1. The COR develops and creates the QASP.

2.3.2. The COR serves as the eyes and ears for the KO at the contractor’s site.

2.3.3 The COR monitors contractor performance to ensure contract requirements are met for:

Performance, Cost, and Schedule.

2.3.4 The COR ensures that contract quality requirements, provisions, standards, and thresholds are defined, practical, enforceable, necessary, and verifiable.

2.3.5 The COR evaluates and documents contractor performance in accordance with this QASP and the

PWS.

2.3.6 The COR notifies the KO of any significant performance deficiencies using a Contractor Discrepancy Report with supporting documentation.

2.3.7 The COR maintains surveillance documentation.

2.3.8 The COR recommends improvements to the QASP and PWS throughout the life of the contract.

3.0. DESCRIPTION OF SERVICES

3.1. Scope of Work. The scope of this contract is to provide total integrated life cycle management activities for the following main task areas: Project, Program and Portfolio (PPP) Management;

Business, Cost Estimating and Financial Management; Life Cycle Logistics (Integrated Product Support); Systems Engineering; Business Analytics; Information Technology; Facilitation, Education and Training; Technical Editor, Writing and Illustration and Physical Security Operations. The PWS also includes efforts required for moving to an enterprise-wide, life cycle alignment of resources and outputs to achieve top-down performance driven outcomes for all DoD Commands, Agencies, Field Activities, all other organizational DoD entities, including Medical, and their partners for both CONUS / OCONUS sites. Foreign Military Sales (FMS) services are also included.

4.0. QUALITY REQUIREMENTS

4.1 Quality Control Program. The contractor, not the Government, is responsible for management and quality control actions to meet the terms of the contract.

4.2 Level of Performance Evaluation. The contractor will be evaluated in the following areas:

Staffing Stability and Resource Planning; Consistent, timely delivery of high quality services and deliverables; Positive Business Relations, Customer Satisfaction and Timely and Open Communications; Timely, Accurate and Complete Program Reporting; Services are Completed within Negotiated Price; and Task Order Participation. In addition, each customer supported by contractor personnel will provide an independent performance evaluation. Any discrepancies will be brought to the attention of the KO.

4.3 Timely Feedback to Contractor: Timely feedback to the contractor on unacceptable performance will be provided by the COR and documented in writing. Prompt feedback is essential so that the contractor can develop and implement a corrective action plan. The contractor's corrective action must be reported to the contracting officer for tracking purposes.

5.0 SURVEILLANCE. The COR will perform monthly surveillance based on the quality and effectiveness of the contractor’s data deliverables as well as the services provided. Regardless of the surveillance method, the COR shall always contact the contractor's quality manager or on-site representative when a defect is identified and inform the manager of the specifics of the problem. The COR, when designated, shall be responsible for monitoring the contractor’s performance in meeting specific performance standards. The COR(s) assigned to perform surveillance of the contractor’s performance manages a Surveillance Folder for their assigned contract requirements. The folder has the following divisions:

5.0.1. COR appointment letter, KO letter of designation, and Training Record.

5.0.2 PWS and other pertinent parts of the contract.

5.0.3. Surveillance Plan.

5.0.4. Surveillance Reports

5.0.5. Other applicable documentation, such as (1) Customer and user comments and (2) Data and technical reports.

5.1 Surveillance methods

The COR, with potential input from the Technical Point of Contact (TPOC)/User, must use at least 1 of the surveillance methods listed below in the administration of this QASP.

a. PLANNED - DIRECT OBSERVATION. (Can be performed periodically or through 100% surveillance.)

b. PERIODIC INSPECTION. (Uses a comprehensive evaluation of selected outputs.

Inspections may be scheduled [Daily, Weekly, Monthly, Quarterly, or annually] or unscheduled, as required.)

c. PERIODIC SAMPLING. (Variation of random sampling. However, sample is only taken when a deficiency is suspected. Good follow-up to MIS analysis. Sample results are applicable only for the specific work inspected. Since sample is not entirely random, it cannot be applied to total activity performance.)

d. RANDOM SAMPLING. (Designed to evaluate the outputs of the award requirement by randomly selecting and inspecting a statistically significant sample. Highly recommended for large quantity repetitive activities with objective and measurable quality attributes.)

e. USER SURVEY. (Combines elements of validated user complaints and random sampling.

Random survey is conducted to solicit user satisfaction. Appropriate for high quantity activities that have historically been satisfactory. May also generate periodic and 100% inspections.)

f. VALIDATED USER/CUSTOMER COMPLAINTS. (Relies on the user of the service to identify deficiencies. Complaints are then investigated and validated. Highly applicable to services provided in quantity and where quality is highly subjective.)

g. 100% INSPECTION. (Evaluates all outputs. Most applicable to small quantity, but highly important services. May be used where there are written deliverables and stringent requirements such as tasks required by law, safety, or security.)

5.2 Unacceptable Performance. If the number of complaints/defects exceeds the performance threshold for any objective, the COR will determine the possible cause of this unacceptable performance.

Government-caused complaints/defects will not be counted against the contractor. The same applies to any other requirement of the contract when Government-caused complaints/defects are the cause of unacceptable contractor performance. If the contractor’s performance is judged unacceptable for any requirement by the COR, the COR will document the discrepancy as a non-conformance and inform the contracting officer (if needed) for resolution. Significant (major non-conformance) performance deficiencies must be submitted to the Contracting Officer using a Contractor Discrepancy Report and include supporting documentation.

6.0 DOCUMENTATION REQUIREMENTS.

A copy of the Monthly Status Report shall be provided to the KO and COR. Issues and concerns that cannot be resolved at the working level or which impact on contractual requirements shall be reported to the KO for resolution and contractual action.

6.1 Deliverable # 1 Status Report (PWS 3.1.1) CDRL DI-MGMT-80368A

6.2 Deliverable #2 Technical Report-Study/Services (PWS 3.1.2) CDRL DI-MISC-80508B

6.3 Deliverable #3 Design to Cost/Life Cycle Cost and Variance Analysis Report (PWS 3.1.3) CDRL DI-FNCL- 80449

6.4 Deliverable #4 Acquisition Support Documentation (PWS 3.1.4) CDRL DI-MGMT-81607

6.5 Deliverable #5 Contractor's Risk Management Plan (PWS 3.1.5) CDRL DI-MGMT-81808

6.6 Deliverable #6 Contractor's Risk Management Plan (PWS 3.1.6) CDRL DI-MGMT-81808

6.7 Deliverable #7 Contract Summary Report (PWS 3.1.7) CDRL DI-ADMN-80447A

6.8 Deliverable #8 Contract Summary Report (PWS 3.2.1.1) CDRL DI-ADMN-80447A

6.9 Deliverable #9 Contract Summary Report (PWS 3.2.1.2) CDRL DI-ADMN-80447A

6.10 Deliverable #10 Contract Summary Report (PWS 3.2.2) CDRL DI-ADMN-80447A

6.11 Deliverable #11 Acquisition Support Documentation (PWS 3.2.3.1) CDRL DI-MGMT-81607

6.12 Deliverables #12 Contractor's Progress, Status and Management Report (PWS 3.2.3.2) CDRL DI-MGMT- 80227

6.13 Deliverable #13 Contract Summary Report (PWS 3.3) CDRL DI-ADMN-80447A

6.14 Deliverable #14 Engineering and Technical Services Accomplishment Report (PWS 3.4) CDRL DI-MGMT- 80061A

6.17 Deliverable #15 Technical Report-Study/Services (PWS 3.5) CDRL DI-MISC-80508B

6.21 Deliverable #16 Technical Report-Study/Services (PWS 3.6.1.1) CDRL DI-MISC-80508B

6.25 Deliverable #17 Technical Report-Study/Services (PWS 3.6.1.2) CDRL DI-MISC-80508B

6.27 Deliverable #18 DoD Architecture Framework Documentation (PWS 3.6.1.3) CDRL DI-MGMT-81644B

6.28 Deliverables #19 Technical Report-Study/Services (PWS 3.6.1.4) CDRL DI-MISC-80508B

6.29 Deliverable #20 Technical Report-Study/Services (PWS 3.6.1.5) CDRL DI-MISC-80508B

6.30 Deliverable #21 Technical Report-Study/Services (PWS 3.6.1.6) CDRL DI-MISC-80508B

6.31 Deliverable #22 Management Plan (PWS 3.6.1.7) CDRL DI-MGMT-80004A

6.32 Deliverable #23 Contractor's Configuration Management Plan (PWS 3.6.1.8) CDRL DI-CMAN-80858B

6.33 Deliverable #24 Status Report (PWS 3.6.1.9, 3.9) CDRL DI-MGMT-80368A

6.34 Deliverable #25 Status Report (PWS 3.6.1.10) CDRL DI-MGMT-80368A

6.35 Deliverable #26 Request for Engineering or Technical Assistance (PWS 3.6.2.1) CDRL DI-TCSP-80235A

6.36 Deliverable #27 Computer Software System Document (PWS 3.6.2.2) CDRL DI-IPSC-80942

6.37 Deliverable #28 Request for Engineering or Technical Assistance (PWS 3.6.2.3) CDRL DI-TCSP-80235A

6.38 Deliverable #29 Request for Engineering or Technical Assistance (PWS 3.6.2.4) CDRL DI-TCSP-80235A

6.39 Deliverable #30 Technical Report-Study/Services (PWS 3.6.2.5) (DI-MISC-80508B)

6.40 Deliverable #31 Technical Report-Study/Services (PWS 3.6.2.6) CDRL DI-MISC-80508B

6.41 Deliverable #32 Technical Report-Study/Services (PWS 3.6.2.7) CDRL DI-MISC-80508B

6.42 Deliverable #33 Request for Engineering or Technical Assistance (PWS 3.6.2.8) CDRL DI-TCSP-80235A

6.43 Deliverable #34 Software Documentation (PWS 3.6.3.1) CDRL DI-IPSC-81756

6.44 Deliverable #35 Computer Software System Documentation (PWS 3.6.3.2) CDRL DI-IPSC-80942

6.45 Deliverable #36 Computer Software Product (PWS 3.6.3.2) CDRL DI-IPSC-81488

6.46 Deliverable #37 Test and Evaluation Program Plan (TEPP) (PWS 3.6.3.3) CDRL DI-NDTI-81284

6.47 Deliverable #38 Technical Report-Study/Services (PWS 3.6.3.4) CDRL DI-MISC-80508B

6.48 Deliverable #39 Program Progress Report (PWS 3.6.3.5) CDRL DI-MGMT-80555A

6.49 Deliverable #40 Technical Report-Study/Services (PWS 3.6.3.6) CDRL DI-MISC-80508B

6.50 Deliverable #41 Computer Software System Documentation (PWS 3.6.3.7) CDRL DI-IPSC-80942

6.51 Deliverable #42 Technical Report-Study/Services (PWS 3.6.4.1) CDRL DI-MISC-80508B

6.52 Deliverable #43 Implementation Plan (PWS 3.6.4.2) CDRL DI-MGMT-81737

6.53 Deliverable #44 Technical Report-Study/Services (PWS 3.7) CDRL DI-MISC-80508B

6.54 Deliverable #45 Technical Report-Study/Services (PWS 3.8) CDRL DI-MISC-80508B

6.55 Deliverable #46 Contractor's Progress, Status and Management Report (PWS 3.1 – 3.10) CDRL DI-

MGMT-80227

6.56 Deliverable #47 Status of Government Furnished Equipment (GFE) Report (PWS 4.4) CDRL DI-MGMT- 80269

6.57 Deliverable #48 Operations Security (OPSEC) Plan (PWS 6.1) CDRL DI-MGMT-80934C

6.57 Contract Manpower Reporting Application: The COR is responsible for validating the contractor’s input into the Contract Manpower Reporting Application (CMRA) website at http://www.ecmra.mil/. The COR is to obtain a user name and password, and validate that the contractor has completely filled in required contractor information at the CMRA web site by November 30 of the first year of the contract and annually by November 30 thereafter for the duration of the contract, or sooner if the contract is closed out. The COR shall perform this validation during the month of November each year. The COR shall report the CMRA results in the November Monthly COR Report (due in December of each year) to the KO each year. Discrepancy Reports are as required.

7.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS)

7.1 Overview. The PRS details and identifies the contractor requirements by performance objectives that relate directly to mission essential elements from the PWS. The performance threshold describes the minimum acceptable levels of service required for each contractor requirement. These thresholds define minimum acceptance standards critical to mission success. Various methods of surveillance exist to monitor performance; see Section 5.1.

7.2 Performance Evaluation. Performance of a service will be evaluated to determine whether or not it meets the performance threshold. Revising and resubmitting the documentation at no cost to the Government is the preferred method for correcting unacceptable performance. The contractor shall provide the Government a written response as to why the performance threshold was not met, how performance will be returned to acceptable levels, and how recurrence of the cause will be prevented in the future.

7.3 Performance Objectives, Indicators, Thresholds, and Surveillance Methods. The services required by the contractor are summarized into performance objectives and indicators, along with the minimum standards that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of quality or service required for each requirement. These thresholds are critical to mission success.

Performance Objective Performance Threshold

(Satisfactory Performance) Method of

Surveillance Minimum Level of Performance

Standard PRS #1 (PWS 3.1 thru 3.10) Excellent staffing stability and resource planning across the effort defined in this contract.

1. Management of personnel (retention, replacements, etc.) does not negatively impact quality or timeliness of products and services across the program

1. TPOC /

Customer Feedback

No more than one (1) valid complaint during the contract performance period

PRS #2 (PWS 3.1 thru 3.10, 8.0) Consistent, timely delivery of high quality services and deliverables.

1) Deliverables were delivered accurate, complete and incorporate all pertinent data with no (or minor) adjustments required by the Government.

2) Deliverables were submitted according to, or ahead of, agreed upon schedule. Exceptions were due to circumstances outside of the Contractor’s control.

3) Consistent quality services delivered throughout period of performance.

1) Random Sampling of CDRLs by COR / (with TPOC input).

2) Customer Feedback

3) Performance evaluation completed by COR semi-annually.

1) No more than one (1) instance where major adjustments to deliverables is required by the Government.

2) 98% of errors / omissions identified by the Government were corrected within ten (10) business days.

3) Overall performance rating of

Satisfactory or better on 98% of semi-annual assessments.

PRS #3 (PWS 3.1 thru 3.10) Positive Business Relations, Customer Satisfaction and Timely and Open Communication.

1. The contractor was responsive to Government concerns and promptly applied corrective action to performance issues.

2. The contractor provided timely notification of issues and/or items requiring Government actions.

1. Customer Feedback

No more than one (1) untimely corrective action or untimely notification within the contract performance period.

PRS #4 (PWS 3.10)

Timely, Accurate and Complete Program Reporting.

1. CDRL A014 (Contractor’s Progress, Status and Management Report) is delivered on time and meets all PWS content requirements.

1. 100% Inspection of CDRL A014 by COR (with TPOC input).

100% accuracy during the contract performance period.