QASP_TADS_Order01.doc
DOC document 134 KB Posted
- Attached to
- Technology Applications Development and Sustainment (TADS) Federal contract opportunity
- Solicitation number
- FA4600-19-R-A001
About this file
This document includes a Quality Assurance Surveillance Plan (QASP) and Performance Assessment Report (PAR) template for the Technology Application Development and Sustainment (TADS) Task Order 01 contract. The QASP establishes procedures for monitoring contractor performance against requirements for hardware and software sustainment services. Key personnel roles are defined, including the Contracting Officer Representative (COR) who will use methods such as customer feedback, inspections, and on-site observations to assess availability, downtime, response times, and deliverable quality. The PAR template is provided for the COR to document quarterly performance reviews for submission to the Contracting Officer. Corrective Action Reports are also included for documenting and resolving any deficiencies.
This federal contract opportunity notice announces a full and open competition for the TADS contract to provide Air Force Weather capability deployment and sustainment services. The single-award IDIQ contract has a 5-year base period and 6-month option and allows various pricing models. Questions are due by July 16, 2019 in preparation for award in October 2019. The Department of the Air Force Air Combat Command is listed as the agency.
QASP for Task Order 01 - Transition and Sustainment
View the file
Other files for this federal contract opportunity
Show all 30
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
TECHNOLOGY APPLICATION DEVELOPMENT AND SUSTAINMENT (TADS)
TASK ORDER 01
TRANSITION AND SUSTAINMENT
QUALITY ASSURANCE SURVEILLANCE PLAN
(QASP)
FA4600-19-R-A001
Coordination and Approval:
Date:
Quality Assurance Program Coordinator (QAPC)
(55 CONS/PKP) **QAPC MUST review along with PWS before any other signatures are obtained
Contracting Officer Representative (COR)
(Organization/Squadron/Section)
Program Manager (PM)
(AFLCMC/HBAW-OL)
Contract Administrator (CA)
(55 CONS/PKT)
Contracting Officer (CO)
(55 CONS/PKT)
1. Purpose
This Quality Assurance Surveillance Plan is an internal, 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 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 and as such, can be updated without modification, at any point during the contract. 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 courtesy copy of the QASP to the contractor following award in order to facilitate open communication, but is not necessary. 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.
2. Authority
Authority for issuance of this QASP is provided under the following:
a. FAR Part 46, Quality Assurance.
b. AFI 63-138, Acquisition of Services (11 May 2017)
c. AFFARS MP5301.602-2(d) Designation, Assignment, and Responsibilities of a Contracting Officer’s Representative (COR)
3. Description of Services
Scope of Work.
The task order provides systems sustainment functions required to support Air Force Weather. The Government identifies systems sustainment functions that return systems to operations are corrective maintenance. Corrective maintenance occurs when a technician discovers a problem while completing a preventive maintenance action, completing an inspection, or performing a return-to-service action. Corrective maintenance identifies, isolates, and rectifies a fault so that the equipment, machine, or system can be restored to operations. The contractor shall provide all personnel, equipment, tools, materials, supplies, parts, test equipment that the Government does not provide, and supervision to meet sustainment requirements. The contractor shall accept subsystems and sub-baselines into sustainment according to agreed to criteria.
4. Multi-Function Team (MFT) Roles and Responsibilities The MFT is responsible for the success of this contract from start to finish. Their goal is to strive to achieve efficiencies, improve customer service and contractor performance, and ensure cost savings.
The following personnel are the key MFT members who shall oversee and coordinate surveillance activities.
4.1 COR Supervisor/Functional Commander (FC)/Functional Director (FD)
a. Identifies mission essential services, to include developing the necessary documents in accordance with DoDI 3020.37, Continuation of Essential DoD Contractor Services During Crisis.
b. Assigns Primary and Alternate CORs.
c. Reviews Contractor performance documentation, prepared by the COR, on a regular basis to ensure performance is compatible with contract and mission objectives while supporting a higher level of Contractor performance, and fostering synergistic partnerships.
Assigned COR Supervisor: <enter name> Organization or Agency: <enter organization or Agency name> Telephone: <enter number> Email: <enter address>
4.2 Contracting Officer:
a. Responsible for contract management. Implements the QASP after contract award by the MFT. Integrates the goals and objectives identified by the multi-functional team, oversight, performance management and performance measurement in accordance with the QASP.
b. Delegates authority for inspection and/or acceptance in accordance with terms of the contract and informs the Contractor of the names, duties, and limitations of authority for all contracting officer representatives assigned to the contract.
c. Is the only person who can direct the Contractor
d. 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.
e. Determine the final assessment of the contractor’s performance.
Assigned CO: <enter name>
Organization or Agency: 55th Contracting Squadron
Telephone: <enter number>
Email: <enter address>
4.3 Contract Administrator (CA): The CA is the individual within the Contracting office who performs day-to-day administration of the contract. The CA could also be the CO should they have a warrant that covers the cost of the contract.
Assigned CA: <enter name>
Organization or Agency: 55th Contracting Squadron Telephone: <enter number>
Email: <enter address>
4.4 Contracting Officer’s Representative (COR): The COR:
a. Responsible for providing continuous technical oversight of the contractor’s performance. The COR uses the QASP to conduct the oversight/surveillance process.
b. Shall keep a Quality Assurance file on the DoD CORT Tool (https://wawf.eb.mil) that accurately documents the contractor’s actual performance. The purpose is to ensure that the contractor meets the performance standards contained in the contract.
c. Responsible for reporting early identification of performance problems to the CO.
d. The COR is required to provide an annual performance assessment to the CO which will be used in documenting past performance (https://www.cpars.gov/). The QASP is the primary tool for documenting contractor performance.
e. Does not have the authority to make any contractual commitments or to authorize any contractual change on the Government’s behalf.
Assigned COR: <enter name> Organization or Agency: <enter organization or Agency name> Telephone: <enter number> Email: <enter address>
4.4 Quality Assurance Program Coordinator (QAPC) The QAPC will:
a. Train the COR/COR Supervisor on their duties/responsibilities as well as the contracting requirements associated with the quality assurance program.
b. Ensure required training is accomplished in accordance with DoDI 5000.72
Assigned QAPC: Paul A. Loede, Jr.
Organization or Agency: 55 CONS/PKP Telephone: 402-294-3974 Email: paul.loede.1@us.af.mil
4.5 Contractor Representatives
The following employees of the contractor serve as the contractor’s Program Manager and other key contractor personnel for this contract. (Complete this section after the contract award)
Program Manager - <upon award, enter name> Telephone: <enter number> Email: <enter address> Other Key Contract Personnel **include any other individuals from the contractor who can be contacted if necessary <upon award, enter name or delete these lines if not applicable>
Title: <enter title>
Telephone: <enter number>
Email: <enter address>
5. Method of Surveillance and Services Summary
5.1 Contract Surveillance
Performance objectives define the desired outcomes. Performance Thresholds define the level of service required under the contract to successfully meet the performance objective. The Method of Assessment defines how the service will be assessed in measuring performance. The methods and degree of performance assessment may change over the course of the contract in direct relation to the COR’s level of confidence in the contractor’s 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 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, Admin, 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.
5.1.1 Combating Trafficking in Persons (CTIP): In accordance with FAR In accordance with FAR 52.222-50 and DFARS PGI 222.17-1703(4) the Contractor shall be in compliance with the CTIP clause and all applicable laws. Compliance is mandatory; no failures to meet CTIP requirements are acceptable. The contractor is under constant surveillance from all government person for CTIP compliance; any person, government employee or contractor, is to report CTIP violations to the COR or CO. CTIP violations must be resolved immediately. Violations shall be reported to DoD Combat Trafficking in Persons (CTIP) Law Enforcement Support Office of Under Secretary of Defense (OUSD).
5.1.2 Methods of Surveillance (insert only the methods you are using—these are a few examples, but not all methods available. There must be a definition for every method you have in the 4th column of the SS so that the COR knows how to conduct surveillance)
5.1.2.1 Customer Complaints: If performance is determined to be unacceptable and appropriate remedial action is not taken in a timely/sufficient manner after the contractor task lead is notified, the COR will ensure a Customer Complaint Record (CCR) is documented, then notify the contractor’s Program/Task Manager (if one is assigned) and the Contracting Officer assigned to the task order. Depending on the severity of the problem, the Government may elect to bypass the CCR documentation and pursue resolution utilizing the Corrective Action Report (CAR). The CCR and CAR forms are attached at the end of this document. https://cs2.eis.af.mil/sites/10059/afcc/knowledge_center/templates/customer_complaint_record.pdf
5.1.2.2 Periodic Surveillance: Surveillance conducted at specific
Intervals or dates. This method of surveillance may be appropriate for tasks that occur infrequently.
5.1.2.3 Customer Feedback: Firsthand information from the actual Customer(s) of the service being provided by the contractor personnel. It forms the basis of the evaluation and assessment. Methods and degrees of performance assessment may change over time in proportion to the evaluator's level of confidence (high or low) in the contractor's performance. The COR is responsible for informing the Customer( s) of the procedures for relaying assessments of the contractor's performance.
5.1.2.4 100% Inspection: Surveillance is mandatory to be completed every time the requirement is called to be done.
5.1.2.5 On-Site Observance: Contractor works in the same office as the COR. COR will conduct daily observations of contractor’s work in accordance with PWS paragraph X.
5.1.3 Services Summary
PERFORMANCE
OBJECTIVE
PWS
PARAGRAPH
REFERENCE
PERFORMANCE
THRESHOLD
METHOD OF
ASSESSMENT
| Hardware maintenance, system administration, software sustainment and license management services for IBM AIX Production system as defined in Exhibit C Sustainment Requirements. |
| 2.0.1, 2.0.2, 2.3, 2.4.2, 2.4.1.1, 2.5.0.1, 2.5.1.1 2.6.1, 4.0 |
| Production operational availability shall be at least 99.2 percent. |
| Periodic surveillance (monthly) |
| Hardware maintenance, system administration, software sustainment and license management services for Red Hat Linux Production system as defined in Exhibit C Sustainment Requirements. |
| 2.0.1, 2.0.2, 2.3, 2.4.2, 2.4.1.1, 2.5.0.1, 2.5.1.1 2.6.1, 4.0 |
| Mean Down Time for the production system shall not exceed 6 hours monthly total to include scheduled and unscheduled events. |
| Periodic surveillance (monthly) |
| Hardware maintenance, system administration, software sustainment and license management services for Oracle (Sun) Solaris Production system as defined in Exhibit C Sustainment Requirements. |
| 2.0.1, 2.0.2, 2.3, 2.4.2, 2.4.1.1, 2.5.0.1, 2.5.1.1 2.6.1, 4.0 |
| Production operational availability shall be at least 99.2 percent. Mean Down Time for the production system shall not exceed 6 hours monthly total to include scheduled and unscheduled events. |
| Periodic surveillance (monthly) |
| Hardware maintenance, system administration, software sustainment and license management services for Red Hat Linux HPC Production system as defined in Exhibit C Sustainment Requirements. |
| 2.0.1, 2.0.2, 2.3, 2.4.2, 2.4.1.1, 2.5.0.1, 2.5.1.1 2.6.1, 4.0 |
| Production operational availability shall be at least 99.2 percent. Mean Down Time for the production system shall not exceed 6 hours monthly total to include scheduled and unscheduled events. |
| Periodic surveillance (monthly) |
| Hardware maintenance, system administration, and license management services for the UPS in Bldg 185. |
| 2.4.4.3 |
| UPS operational readiness shall be at least 99.4 percent. |
| Periodic surveillance (monthly) |
| Maintenance will include remedial and preventive maintenance. |
| 2.0.2, 2.3.1, 2.4.1.1, 2.4.3.1, 2.6.1.1 |
| Greater than 95% of on-call requests are responded to within 20 minutes of original call and greater than 95% of on-site arrivals are within 60 minutes of determination that on-site support is required. |
| Periodic surveillance (monthly) |
| Corrective implementations installed |
| 2.0.1, 2.0.2, 2.2.1, 2.2.2, 2.3, 2.4.1, 2.4.2, 2.4.3, 2.5, 2.6.1, 2.6.2 |
| 97% without errors |
99% without failures Periodic surveillance (monthly)
| Deliverables submitted |
| 2.0.3, 2.1.1, 2.1.2, 2.2.1, 2.2.2, 2.2.3, 2.3.2, 2.3.3, 2.3.4, 2.4.1.2, 2.4.2.1, 2.4.3.1, 2.4.4.1, 2.4.4.2.1, 2.4.4.2.3, 2.5.2.1, 2.5.3.1, 2.6.1 |
| 95% with no errors |
100% submitted before or on due date Periodic surveillance (monthly)
| Mandatory directives |
| 2.0.4, 2.3.4, 2.4.2.2, 2.6.2 |
| 100% completed no later than the due date. |
| Periodic surveillance (monthly) |
| Equipment Preventive Maintenance and Inspection |
| 2.4.1.1 |
| Zero repeat findings. All findings resolved within one month of Government report. |
| Periodic surveillance (annually) |
6 Performance Reporting 6.1 Corrective Action Report (CAR). CARs are used by the COR to document contractual requirement findings and subsequent corrective actions to be taken. A computer-generated CAR may be used to provide the information. https://cs2.eis.af.mil/sites/10059/afcc/knowledge_center/templates/corrective_action_report.pdf 6.1.1 The COR identifying the discrepancy is responsible for completing the CAR utilizing the instructions attached. If there are other questions as to how the CAR is completed, that individual should consult the CO.
6.1.2 Consult the assigned Contract Administrator (CA) to give them the opportunity to assist and advise how the CAR is to be worded. Forward a copy of the initiated CAR to the CO.
6.1.3 The COR will elevate any CARs that cannot be resolved with the Contractor to the CO for resolution.
6.1.4 Categories of Findings: A finding is any Government-identified noncompliance with contractual requirements that specifies an activity or action did not take place or was not performed to the quality or timeliness standard required by the contract. A finding can be categorized as either Major or Minor. Findings will be documented on a CAR and must also be tracked in a PAR (see paragraph 4.2). Major/Minor Findings are defined as follows:
6.1.4.1 A Major Finding is a conclusion that identifies a condition having a significant adverse effect on the quality of the activity under review such as:
a.
Failure to meet a Performance Threshold.
b.
Significant mission degradation in any Contractor operated function.
c.
A situation that is likely to result in hazardous or unsafe conditions for individuals (or any other Government resource) coming into contact with the work.
d.
Failure to provide adequate corrective action to preclude reoccurrence of Government identified findings.
e.
Failure to provide corrective action to deficiencies identified by the Contractor within a prescribed suspense period.
f.
Any failure to adhere to security regulations that results in a security incident.
6.1.4.2 A Minor Finding is a departure from established standards having little bearing on service provided. However, if the same minor finding is repeatedly identified, it may be an indication that Major Finding (d) above is occurring or has occurred because the Contractor quality system has not acted to prevent recurrence. In this case, the Minor Finding should be elevated to the level of a Major Finding and a new CAR initiated.
6.2 Performance Assessment Report (PAR). The COR must document performance assessment as it is accomplished, IAW the requirements/objectives listed in the Services Summary. The PAR is an official Government record of inspection of the performance objectives and other inspection items contained in this QASP (see link for PAR and instructions). On a quarterly basis (or in accordance with the PWS standards) the COR shall prepare a PAR and upload the same in the COR Online File within the CORT Tool (see paragraph 3.4). The CO will then review the PAR and either approve or disapprove the PAR, providing explanation for a disapproved PAR. https://cs2.eis.af.mil/sites/10059/afcc/knowledge_center/templates/performance_assessment_report.pdf 6.3 Acceptance of Services: The COR is required to accept contractor services in the Procurement Integrated Enterprise Environment (PIEE) and determine payments due.
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 FORMCHECKBOX
MAJOR FORMCHECKBOX
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
FORMCHECKBOX
ACCEPTED FORMCHECKBOX
REJECTED
12. CLOSE DATE
| CUSTOMER COMPLAINT RECORD |
| DATE/TIME OF COMPLAINT |
SOURCE OF COMPLAINT
ORGANIZATION
BUILDING NUMBER
INDIVIDUAL
PHONE NUMBER
NATURE OF COMPLAINT
CONTRACT REFERENCE
VALIDATION
DATE/TIME CONTRACTOR INFORMED OF COMPLAINT
ACTION TAKEN BY CONTRACTOR
RECEIVED/VALIDATED BY
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 (COR) SIGNATURE AND DATE
| 5. COR PHONE |
| 6. SUSPENSE DATE |
I. PERFORMANCE
7. FORMCHECKBOX
DEFICIENCY (CHECK ALL BOXES THAT APPLY)
FORMCHECKBOX
NEW
FORMCHECKBOX
REPEAT
FORMCHECKBOX
NO DEFICIENCY NOTED
8. SERVICES SUMMARY or PWS PARAGRAPH ITEM REVIEWED
| 9. BRIEF DESCRIPTION OF DEFICIENCY (IF DEFICIENCY BOX WAS CHECKED) |
| 10. DETAILED PERFORMANCE ASSESSMENT |
II. CONTRACTOR VALIDATION
11. CONTRACTOR REPRESENTATIVE FORMCHECKBOX
CONCUR FORMCHECKBOX
NON-CONCUR
12. CORRECTIVE ACTION ESTIMATED COMPLETION DATE
13. CONTRACTOR REPRESENTATIVE CORRECTIVE ACTION AND PREVENTION OF RECURRENCE OR REASON FOR NON-CONCURRENCE OF COR CITED DEFICIENCY
III. ACTION CORRECTED
14. FORMCHECKBOX
CONCUR FORMCHECKBOX
NON-CONCUR COR SIGNATURE AND DATE
15. COR REMARKS (REQUIRED)
6. CONTRACTOR REPRESENTATIVE REMARKS
File details come from the government source that posted it. Updated .