Attachment_0001_QASP_ _PRS_Survey_Ops_and_Analytics_IDIQ.docx
DOCX document 42 KB Posted
- Attached to
- Survey Operation and Analytical Support
- Solicitation number
- W15QKN-16-R-0081
About this file
Attachment 0001 - QASP PRS for Survey IDIQ
View the file
Other files
Show all 19
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
QUALITY ASSURANCE SURVEILLANCE PLAN
Survey Operations and Analytic Support
1.0 INTRODUCTION
1.1. Purpose. 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 is responsible for safeguarding the interests of the United States Government in contractual relationships. Only the Contracting Officer 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 Contracting Officer designates authority for inspection and/or acceptance responsibilities to the 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 Contracting Officer’s behalf.
2.2.2. The Contracting Officer 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. The Contracting Officer Representative (COR) when designated:
i. develops and creates the QASP
ii. serves as the eyes and ears for the Contracting Officer at the contractor’s site
iii. monitors contractor performance to ensure contract requirements are met for: Performance, Cost, and Schedule
iv. ensures that contract quality requirements, provisions, standards, and thresholds are defined, practical, enforceable, necessary, and verifiable.
v. evaluates and documents contractor performance in accordance with this QASP and the PWS.
vi. notifies the Contracting Officer of any significant performance deficiencies using a Contractor Discrepancy Report with supporting documentation.
vii. maintains surveillance documentation.
viii. 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 requirement is for the Contractor to provide ARI with the necessary capabilities to conduct attitude and opinion surveys in support of ARI’s scientific and technology program. The survey(s) will be distributed to samples of junior enlisted Soldiers and non-commissioned, warrant, and commissioned officers. The survey(s) assesses Soldiers’ attitudes and opinions on an array of issues critical to the Army. The accuracy and timeliness of this survey data is of paramount importance in supporting senior leader decision-making.
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. Details of these controls will be document (when required) in the contractor’s Quality Control Program document.
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 a specific performance standard/AQL.
5.1 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.
| 6.1 | Monthly Reports in VCE COR Tool |
| 6.2 | Surveillance Folder (to include QASP, QCP, Activity Log, Contract, Appointment letters, Training Certificates, Surveillance Checklists, Reports, Minutes, Memoranda, and Miscellaneous Correspondence) |
| 6.3 | Progress Reports as required |
| 6.4 | Technical Reports, as required |
| 6.5 | Discrepancy Reports 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 note 2 below.
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 REQUIREMENTS SUMMARY
| Performance Objective |
| Standard |
| Performance Threshold |
| Method of Surveillance |
GENERAL TASKS (Paras 5.2.2)
PRS #1. Monthly Report and Progress Updates Contractor shall provide updates on survey operations, as required Para 5.2.2 --For each task order, contractor shall provide a monthly report. Additional progress updates may be specified in each TO --The first monthly report for a task order will include documentation of the kickoff meeting.
| Monthly report and progress updates will contain all of the information requested by the Government |
| 100% Inspection by COR or designee |
SURVEY DEVELOPMENT AND ADMINISTRATION TASKS (Paras 5.3-5.3.8)
PRS #2. Develop, Update, and Maintain Databases and Address and Status Updates
Contractor shall develop, update, and maintain population, sample, and respondent databases in accordance with TO specifications.
Paras:
5.3.1 5.3.1.1 5.3.1.2 5.3.2 -- No breach of PII and sensitive data --All databases are complete, accurate, and regularly updated --Sample and respondent databases contain disposition and eligibility indicators are in accordance with best practices --Respondent data files completely and accurately reflect respondents’ survey responses and administrative file data. The preliminary and final SPSS or SAS datasets are clean and contain accurate: variable and value labels, coding of all status indicators (e.g., eligibility and disposition), and created variables.
No deviation from standard
Random sampling by COR or designee
PRS #3. Prepare and Distribute Paper Sample Communications and Survey Questionnaires
Contractor shall prepare paper/printed survey questionnaires and sample communications.
Paras:
5.3.3.1 5.3.3.2 --Paper/printed sample communications and survey questionnaires are printed without error.
--Sample communications are sent via postal mail on schedule as agreed upon by the Government and Contractor.
| No deviation from standard |
| Random sampling of printed materials by COR or designee |
PRS #4. Prepare and Distribute On-line Sample Communications and Survey Questionnaires
Contractor shall prepare on-line sample communications and survey questionnaires. Para: 5.3.4 --On-line surveys and sample communications have no typographical errors.
--Survey notifications are sent on schedule as agreed upon by the Government and Contractor --Online surveys contain accurate skip patterns and branching.
| No deviation from standard |
| 100% inspection of on-line communications and questionnaire by COR or designee |
PRS #5. Monitor Data Collections
Contractor shall monitor data collections as specified in individual TOs.
Para: 5.3.5
| Accurate, up-to-date counts of disposition, eligibility, and up to four (4) other key stratification variables shall be available throughout the data collection. All PII and sensitive information shall be safeguarded. |
| No deviation from standard |
| Random sampling by COR or designee |
PRS #6. Respond to Sample Members
Contractor shall respond to sample members’ questions, problems, or concerns Para: 5.3.6 Contractor will telephonically or via e-mail address sample members concerns, questions, or difficulties within 72 hours of receipt
| No deviation from standard |
| Periodic inspection by COR or designee |
PRS #7. Develop Qualitative/Comments File(s)
Contractor shall develop databases containing verbatim comments.
Para: 5.3.7
| Respondent-entered comments from “Other (please specify)” type responses and from comment boxes are copied verbatim into separate Access or other software databases with several key demographic survey variables. |
| No deviation from standard |
| Random sampling by COR or designee |
PRS #8. Provide Databases and Methodological Documentation and Codebooks
Contractor shall develop database documentation.
Paras: 5.3.8 --Database documentation which accurately describes all response and administrative variables on the databases, coding, variable and value labels, skip patterns, and branching --Documentation of survey operations shall comprehensively describe the methodological approach and its implementation.
| No deviation from standard |
| 100% inspection by COR or designee |
SURVEY ANALYTIC AND METHODOLOGICAL SUPPORT TASKS (Paras 5.4-5.4.5.9)
PRS #9. Oral Presentation/Briefing
Para: 5.4.1
| --Oral presentation on a methodological or statistical issue as requested by the Government |
| No deviation from standard |
| Observation by COR or designee |
PRS #10. Database development
Para: 5.4.2-5.4.2.4 --No breach of PII and sensitive data --Databases are complete and accurately represent Government requirements
| No deviation from standard |
| 100% inspection by COR or designee |
PRS #11. Develop and Implement Sampling Plan
Para: 5.4.3.2 --No breach of PII and sensitive data --Sampling plan meets Government requirements for representation of key subgroups and confidence intervals --Sampling plan to be delivered no later than 1 month after receipt of request
| No deviation from standard |
| 100% inspection by COR or designee |
PRS #12. Implement Sampling Plan
Para: 5.4.3.3 --No breach of PII and sensitive data --Sample is selected exactly as indicated in the Sampling Plan --Sample to be delivered no later than 10 business days after receipt of request to draw sample
| No deviation from standard |
| Random sampling by COR or designee |
PRS #13. Develop and Implement Weighting Plan
Para: 5.4.4.
--No breach of PII and sensitive data --Weights reflect sampling approach and Government requirements --Weights to be delivered no later than 2 weeks after either: (a) close of the fielding period, or (b) respondent data become available.
| No deviation from standard |
| Random sampling by COR or designee |
PRS #12. Document Final Sampling and Weighting
Paras:
5.4.3.4 5.4.4.
--No breach of PII and sensitive data --Report accurately describes all assumptions and procedures used in the development and implementation of sampling and weighting --To be delivered within 3 months after the close of the fielding period
| No deviation from standard |
| 100% inspection by COR or designee |
PRS #13. Develop Methodological Reports
Para: 5.4.5.9 --Report provides an in-depth review of the latest scientific research on a critical methodological issue such as, but not limited to, non-response, weighting, survey administration.
--Revisions to draft report to be delivered 15 business days after receipt of Government comments
| No deviation from standard |
| 100% inspection by COR or designee |
Note 1. The evaluation ratings are as follows:
a. Very Good - Performance meets contractual requirements and exceeds some to the Government’s benefit. The contractual performance of the task and sub-task being assessed was accomplished with some minor problems for which corrective actions taken by the contractor were effective.
b. Satisfactory - Performance meets contractual requirements. The contractual performance of the task and sub-task contain some minor problems for which corrective actions taken by the contractor appear or were satisfactory.
c. Marginal - Performance does not meet some contractual requirements. The contractual performance of the task and sub-task being assessed reflects a serious problem for which the contractor has not yet identified corrective actions. The contractor’s proposed actions appear only marginally effective or were not fully implemented.
d. Unsatisfactory – Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance of the task or sub-task contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective.
Note 2. Surveillance methods
The COR must use at least 1 of the surveillance methods listed above 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.)
File details come from the government source that posted it. Updated .