EXHIBIT B - QASP.doc
DOC document 75 KB Posted
- Attached to
- FA7022-11-R-0024, MSSS Federal contract opportunity
- Solicitation number
- FA7022-10-R-MSSS
About this file
Exhibit B - QASP
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| CDRL A0019.pdf | ||
| Revised GFE Listing.pdf | ||
| Clarification 2nd Set of Questions.docx | DOCX document | |
| FA7022-11-R-0024 Amendment 0001.rtf | RTF text file | |
| Clarifications regarding FA7022-11-R-0024.docx | DOCX document | |
| EXHIBIT D Past Performance Cover Sheet and Questionnaire.docx | DOCX document | |
| ATCH 4 - Labor Category Rates for Task Orders 21 Jul 11.xlsx | XLSX spreadsheet | |
| ATCH 5 - GFE and Base Support.docx | DOCX document | |
| EXHIBIT A - CDRLS.pdf | ||
| ATCH 3 - Labor Category Descriptions.docx | DOCX document | |
| FA7022-11-R-0024 RFP as of 22 July 11.doc | DOC document | |
| ATCH 2 - DD254.pdf | ||
| EXHIBIT C - Past Performance Information.docx | DOCX document |
Show all 13
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
EXHIBIT B
FA7022-11-R-0024
QUALITY ASSURANCE SURVEILLANCE PLAN
FOR
Modeling and simulation system support (MS3)
1.0 PURPOSE: The purpose of this Quality Assurance Surveillance Plan (QASP) is to establish procedures for monitoring, reporting and evaluating the performance of the contractor for work performed pursuant to the Performance Work Statement (PWS) for MS3.
2.0 OBJECTIVE: This QASP is designed to provide the Multi-Functional Team (MFT) with a vehicle to ensure delivery of the desired mission support services within cost and on schedule. The QASP will provide the Contracting Officer’s Representative (COR) with a systematic surveillance method for each item listed on the Service Summary (SS).
3.0 DESIRED RESULTS: The MFT will strive to manage this performance-based acquisition through effective monitoring, evaluating, and reporting of contractor performance. The Government will maintain an accurate awareness of contract status and contractor work performance. The team will manage risk to ensure mission performance is within cost and schedule constraints.
4.0 ROLES AND RESPONSIBILITIES: The Multi-Functional Team (MFT) is a customer-focused team responsible for planning and managing the service acquisition throughout the life of the requirement. The MFT is responsible for planning and designing a mission support strategy that aligns mission support needs with a performance-based strategy. Responsibilities are outlined as follows:
4.1 The Contracting Officer’s Representative (COR) is the representative of the requiring activity, nominated by the requiring activity and designated by the Contracting Officer (CO), to assist in the technical monitoring or administration of a contract. The COR must be a Government employee. The COR must complete required training prior to contract award, or prior to performing COR duties if assigned as COR after contract award. The COR will establish and maintain COR contract file IAW DFARS PGI 201.602-2(ii) and MP5301.602-2(d), and remain abreast of changes to terms and conditions of contract resulting from contract modifications. The source of COR authority is the CO. The COR may perform only those duties delegated by the CO in the CO’s Delegation Letter without re-delegation. The COR must provide reports on contractor performance to the CO.
4.2 Contracting Officer (CO): The Contracting Officer (CO) is the only person with the authority to enter into contracts and contractually obligate the Government. The CO shall designate the CORs IAW MP5301.602-2. The CO shall notify the requiring activity of the need for COR support by submitting a Request for COR Support. After receipt of the COR nomination package from the requiring activity, the CO shall determine the acceptability of the COR, ensure contract-specific training is provided to the COR and appoint the COR via a COR Designation Memo. The CO shall review the COR’s reports of surveillance for accomplishment and completeness. The CO shall provide an assessment on COR performance to the COR supervisor, as requested. Only the CO can terminate a COR Designation.
4.3 Contract Administrator: The Contract Specialist/Contract Administrator (CS/CA) is the authorized representative of the Contracting Officer who is assigned the responsibility of administering a service contract for the Government. The CA is the focal point for issues regarding the contract; prepares and processes modification to the contract; assists the CO in ensuring contractor performance meets contract standards; provides COR contract specific training, records and transcribes minutes for MFT.
4.4 Contracting Officer’s Representative (COR) Supervisor: The supervisor of the COR does not have any authority over the duties a COR performs in their COR position, but is responsible for preparing the performance rating of an employee with COR responsibility. Supervisors will evaluate the performance of COR duties as part of their performance assessments throughout the period of the contract. The supervisor’s management authority exercised through the performance evaluation process is distinct from a CO’s authority. A satisfactory or higher rating of a COR by a supervisor does not preclude the CO’s authority to terminate a COR appointment.
4.5 The Quality Assurance Program Coordinator (QAPC) is responsible for the health and management of the Quality Assurance Program for Performance Based Service Acquisitions. The QAPC supports the MFT in the development of contract quality assurance requirements, assists market research efforts and the evaluation of the contractor Quality Control Plan (if required). The QAPC maintains a record of all COR designations and terminations. The QAPC provides the COR with Initial COR training and ensures all required COR training is completed prior to contract award and performance of COR duties.
4.6 Contracting Squadron Commander: The Contracting Squadron Commander (CSC) ensures a QAPC is appointed to integrate the quality control requirements into the quality assurance program and act as the liaison between the contracting and functional organizations. Contact the CSC if you have any problems or issues on the contract that cannot be resolved by the CO or CA.
4.7. The Services Designated Official (SDO) is the individual authorized IAW 10 U.S.C. 2330, to exercise responsibility for the management and oversight of the acquisition of contract services.
5.0 SURVEILLANCE FOLDER. The COR’s assigned to perform surveillance of this contract are required to prepare a surveillance folder for their assigned contract requirements. The folder shall contain the following documents:
a.
Request for COR Support and Nomination of COR
b. CORs – Training Certification (Initial training and specific training) to include
DoDD Directive 5500.7 (ethics) and DAU training documents c.
COR Designation Memorandum d.
Contract (to include PWS, SS, DD254, etc) with all Modifications e.
QASP signed by all MFT members f.
Contractor Quality Control Plan (if applicable) g.
Log of Surveillance Activities, including reports to CO h.
Documentation of Surveillance Findings and Reporting i.
Certification of Services (Invoices)/Receiving Reports j.
Correspondence and Memorandums for Record k.
Discrepancy Reports l.
Customer and User comments m.
Contract Deliverables Tracking System
n. Names of Technical and Administrative Personnel assisting the COR (if any)
o. Copy of all reports done by technical and administrative personnel referenced in COR reports
6.0 PROCEDURES: Procedures for observing the contractor’s performance are developed, documented, and agreed upon in the QASP. The Method of Measurement will determine how the COR will evaluate the contractor’s performance.
| PERFORMANCE OBJECTIVE |
| PWS PARA |
| PERFORMANCE THRESHOLD |
| METHOD OF MEASUREMENT |
| Develop and provide timely and quality CDRLs |
| 1.4 – 1.13 |
| One-time deliveries no later than two (2) working days of due date. Periodic deliveries on time at least 95% of time, all other deliveries no later than ten (10) calendar days after due date. |
| Inspection of deliverable receipt against deliverable schedule |
Inspection of deliverable and comparison against requirements and Data Item Descriptions
| Comply with all security requirements |
| 1.10 |
| Zero (0) security violations |
| Inspection. Security incidents will be tracked and addressed by Government and contractor security offices |
Respond to software problem calls by mission impact as determined by the Government
| 1.5 |
| Urgent responses and initial diagnosis no later than four (4) hours after notification |
Urgent responses and initial diagnosis no later than one (1) business day of notification
Routine responses and initial diagnosis no later than five (5) business days of notification Observation, inspection, contractor metrics, acceptance testing, site visits
| Install software patches within scheduled time period |
| 1.5 |
| Urgent software modifications implemented no later than twenty-four (24) hours of notification |
Priority software modifications implemented no later than seven (7) calendar days of notification
Routine software modifications implemented no later than ninety (90) calendar days of notification Observation, inspection, contractor metrics, acceptance testing, site visits
| Provide accurate and timely technical and analytical support |
| 1.4 – 1.9 |
| Contractor shall receive no more than two (2) validated customer complaints or corrective action requests per task order. Contractor shall successfully resolve customer complaints within fourteen (14) calendar days of receipt with no exceptions |
| Observation. All deficiencies will be documented by the Government and contractor responses will be logged |
| Provide software configuration management |
| 1.0 – 1.9 |
| Modifications are in accordance with ISO-12207 and other pertinent Government requirements made within ten (10) working days of expected completion |
| Inspection of configuration documentation |
| Meet all stated baseline requirements on time and within approved schedule |
| 1.0 – 1.13 |
| Implement in accordance with individually-defined requirements for each paragraph listed; 95% on time |
| Review of requirements monthly status and period of performance |
7.0 PERFORMANCE MANAGEMENT: The MFT will develop, implement and execute performance measurement and management processes to ensure optimum contractor performance and early identification of deficient areas and unacceptable performance.
Timely feedback to the contractor on unacceptable performance will be provided by the COR. Any unacceptable performance or delinquencies will be documented with a copy to the CO. Prompt feedback is essential for the contractor to develop and implement a corrective action plan. The contractor’s corrective action must be reported to the COR and the CO for tracking purposes.
8.0 CERTIFICATION OF SERVICES: The Government expects the contractor to meet all of the requirements of the contract. The contractor expects timely payment for all services rendered. Certification of services will be performed by the COR. The format for this process will be Wide Area Work Flow (WAWF).
9.0 CUSTOMER COMPLAINTS: The COR will gather all customer comments. The COR will investigate negative comments and determine their validity. Valid negative comments will be discussed with the contractor and corrective action will be taken by the COR and Contracting Officer. All customer complaint forms must be maintained in the COR file.
10.0 LIST OF NON-SDS ITEMS SUBJECT TO OBSERVATION: The Government retains the right to inspect any item included in the contract. These items will be inspected periodically during the contract period.
11.0 CONTRACTOR RATING (CPARS): Contractor’s Performance Assessment Rating (CPAR) is an annual reporting requirement applicable to all service contracts valued over $1,000,000. Guidance on CPARS is available from the Department of the Air Force CPARS Guide and the AF ISR Agency A7KO representative or at the following web http://www.cpars.csd.disa.mil/.
12.0 CONTRACT DELIVERABLE TRACKING SYSTEM: Every service contract is required to have a contract deliverable tracking system. The following deliverables are prepared by the contractor and delivered to the COR throughout the POP.
| DELIVERABLE |
| PWS PARA. |
| SCHEDULE |
A001
Monthly Status Report
| 1.4 – 1.8 |
| Due forty-five (45) calendar days after contract award; subsequent submissions due by 5th business day of each month |
A002
Contract Funds Status Report
| 1.4.2 |
| Due forty-five (45) calendar days after contract award; subsequent submissions due by 5th business day of each month |
A003
Software Product Specification
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A004
Software User Manual
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A005
Software Requirements
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A006
Software Test Plan
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A007
Software Test Description
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A008
Software Test Report
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A009
Test Plan
| 1.4 - 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A0010
Software Installation Plan
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A0011
Test Procedure
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A0012
Test/Inspection Report
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A0013
Interface Requirements Specification
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A0014
Interface Design Description
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A0015
Technical Report – Study/Services
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A0016
Scientific and Technical Reports
| 1.4 – 1.8 |
| Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days |
A0017
Conference Agenda
Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final agenda due within fifteen (15) calendar days
A0018
Conference Minutes
Draft due date will be specified in individual task orders. Government will complete review within fifteen (15) calendar days. Upon receipt of Government comments, final submission due within fifteen (15) calendar days
The following MFT Members have reviewed and approved this QASP:
Contracting Officer
Date
Contracting Officer’s Representative
Date
Quality Assurance Program Coordinator Date
AF ISR Agency/A7K Committee
Date
Small Business Specialist
Date
File details come from the government source that posted it. Updated .