S02 ATTACHMENT 3 QASP DQ v2 061225.docx

DOCX document 117 KB Posted

Attached to
R702--DQ Technical Analysis & Functional Support Federal contract opportunity
Solicitation number
36C77625Q0232
Issued by
Department of Veterans Affairs Technology Acquisition Center Austin

About this file

This document is a Quality Assurance Surveillance Plan (QASP) for the Department of Veterans Affairs Office of Health Informatics, specifically for Data Quality (DQ) Technical Analysis & Functional Support services. The contract requires the contractor to provide support services for the Data Quality Program, including reviewing technical documents, developing enterprise requirements, executing user acceptance testing, providing data quality expertise, and performing data quality analysis and reporting.

The QASP outlines performance standards across multiple task areas such as project management, identity management technology configuration, document development and review, data quality support, requirements development, and data quality analytics. The government will use a 100% inspection method to evaluate deliverables, with an Acceptable Quality Level (AQL) of 100% for most tasks. Performance will be assessed quarterly using a rating scale from Exceptional to Unsatisfactory, and the government will consider the contractor's performance when determining option exercise. The solicitation is targeting administrative management and general management consulting services under NAICS code 541611, with a size standard of $24.5 million, and is seeking responses by December 20, 2024.

View the file

Other files for this federal contract opportunity

Other files attached to R702--DQ Technical Analysis & Functional Support, newest first.
File Type Posted
S02 ATTACHMENT 5 CONTRACTOR ROSTER.doc DOC document
S02 ATTACHMENT 2 Business Associate Questionnaire.pdf PDF
36C77625Q0232.docx DOCX document
S02 ATTACHMENT 7 Labor Cat and Descr Ex.xlsx XLSX spreadsheet
S02 ATTACHMENT 6 CONTRACTOR CHANGE FORM.doc DOC document
S02 ATTACHMENT 4 VAAR 852 219 75.docx DOCX document
S02 ATTACHMENT 1 PWS DQ v3 061225.docx DOCX document

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

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

DEPARTMENT OF VETERANS AFFAIRS

Office of Health Informatics (OHI) Health Information Governance (HIG), Data Quality (DQ)

DQ Technical Analysis & Functional Support

Date: 6/12/2025 OHI Identifier #- QASP Version Number: 2.0 THIS DOCUMENT DOES NOT GET INCORPORATED INTO THE CONTRACT/ORDER; IT IS USED BY GOVERNMENT REPRESENTATIVES TO MONITOR PERFORMANCE AND THE GOVERNMENT HAS THE RIGHT TO CHANGE ITS METHOD OF SURVEILLANCE AT ANY TIME. THE CO/COR SHOULD PROVIDE A COPY TO THE CONTRACTOR THROUGH CORRESPONDENCE.

QUALITY ASSURANCE SURVEILLANCE PLAN

For: DQ Technical Analysis & Functional Support

Contract/Order Number: Blank until contract/order award

Contract/Order Description: The Contractor shall provide support services for the Data Quality Program that includes reviewing business and technical project documents for proper incorporation of defined requirements to implement data quality and identity management; developing, and refining enterprise requirements, use cases, and business rules used to implement and support data quality; planning and executing user acceptance testing (UAT) of software products; providing business and technical expertise in the areas of data quality and identity management; and performing formal and informal data quality analysis and reporting in support of implementations and updates to the matching algorithm and other software.

Contractor’s Name: Blank until contract/order award Purpose This Quality Assurance Surveillance Plan (QASP) provides a systematic method to monitor Contractor performance. This QASP describes:

What will be monitored How monitoring will take place Who will conduct the monitoring How monitoring efforts and results will be documented

Copies of the original QASP and revisions shall be provided to the Contractor and Government officials responsible for surveillance activities. The Government can change the method of surveillance at any time without the approval of the contractor.

Performance Management Approach The PWS sets forth “what” service is required as well as the performance standards associated with that task, as opposed to “how” the Contractor should perform the work (i.e., results, not compliance). This QASP will define the performance management approach taken by the Government to monitor the Contractor’s performance to ensure the expected outcomes or performance standards communicated in the PWS are achieved. Performance management rests on developing a capability to review and analyze information generated through performance assessment. The ability to make decisions based on the analysis of performance data is the cornerstone of performance management; this analysis yields information that indicates to what extent the expected outcomes for the project are being achieved by the Contractor.

Performance management represents a significant shift from the more traditional quality assurance (QA) concepts in several ways. Performance management focuses on assessing whether outcomes are being achieved and to what extent. This approach migrates away from scrutiny of compliance with the processes and practices used to achieve the outcome. A performance-based approach enables the Contractor to play a large role in how the work is performed, as long as the proposed processes are within the stated constraints. Required processes are those required by law (federal, state, and local) and compelling business situations, such as safety and health. A “results” focus by the Government provides the Contractor flexibility to continuously improve and innovate over the course of the contract/order as long as the critical outcomes expected are being achieved and/or the desired performance levels are being met.

Performance Management Strategy The Contractor is responsible for the quality of all work performed. The Contractor measures that quality through the Contractor’s own quality control (QC) program. QC is work output, not workers, and therefore includes all work performed under this contract/order regardless of whether the work is performed by Contractor employees or by Subcontractors. The Contractor’s QC program will set forth the procedures for self-inspecting the quality, timeliness, responsiveness, customer satisfaction, and other performance requirements in the PWS. The Contractor will implement a performance management system with processes to assess and report its performance to the designated government representative.

The government representative(s) will monitor performance by the Contractor to determine how the Contractor is performing against performance standards. The Contractor will be responsible for making required changes in processes and practices to ensure performance is managed effectively. The Contractor will be monitored and assessed throughout the period of performance of the contract/order as to either meeting or not meeting the performance thresholds stated in the Performance Metrics Section of the Performance Work Statement (PWS). The Performance Based Service Assessment, or other method, may be used to document this assessment. A Performance Based Service Assessment is provided at the end of this document. When Contractor performance is unacceptable, the COR will notify the Contractor Program Manager (CPM) and the Contracting Officer (CO). Unacceptable performance is defined as; “the contractor is not meeting the Acceptable Levels of Performance (ALPs) as defined in the PWS or is in violation of any contract clause or terms and conditions. Notification of unacceptable performance issues shall be immediately provided to the CPM and shall not remain un-addressed until the end of an assessment period. In order to remediate performance issues in a timely manner, the COR should work collaboratively with the CPM. The COR/CO will engage the CPM to resolve the discrepancy.

Performance Feedback For instances where immediate notification of performance issues is not required, the COR should review the assessment in accordance with the quarterly reviews with the CPM and provide the assessment to CO. The COR/CO will notify the Contractor of the results for a rating of 3 or less, no later than 15 working days after the end of the assessment period.

Government Roles and Responsibilities The following personnel shall oversee and coordinate surveillance activities:

a. Contracting Officer (CO) - The CO shall ensure performance of all necessary actions for effective contracting, ensure compliance with the contract/order terms, and shall safeguard the interests of the United States in the contractual relationship. The CO shall also assure that the Contractor receives impartial, fair, and equitable treatment under this contract/order. The CO is ultimately responsible for the final determination of the level of acceptability of the Contractor’s performance.

Assigned CO: Michelle Rhodes, Contracting Officer Organization: Department of Veterans Affairs, Program Contracting Activity Central

b. Contracting Officer’s Representative (COR) - The COR is responsible for technical administration of the contract/order and shall assure proper Government surveillance of the Contractor’s performance. The COR shall keep a quality assurance file. This file shall contain all quality assessment reports. The COR is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf.

Assigned COR: Denise Zibura

c. Other Key Government Personnel – Sara Temlitz, PM

Contractor Representatives

a. Program Manager – To be completed at award

b. Other Contractor Personnel – To be completed at award; if any (name and title)

Performance Standards Performance standards define desired services. The Government performs surveillance to determine if the contractor exceeds, meets or does not meet these standards.

The Performance Requirements Summary Matrix, paragraph 6.5 Performance Metrics in the Performance Work Statement (PWS), includes performance standards. The Government shall use these standards to determine contractor performance and shall compare contractor performance to the Acceptable Quality Level (AQL).

Task
Indicator
Standard
AQL
Method of Surveillance
5.1 Project Management
A. Provide a monthly progress report that covers all work completed during the reporting period and work planned for the subsequent reporting period.
Timely submission of deliverable (monthly) without substantiative errors.
100%
Review of deliverable prior to acceptance.
5.2 Data Quality Identity Management Technology Configuration, Implementation, and Analysis
A. Provide guidance and recommendations on configuration parameters, threshold settings, and implementation details, including functionality to be included, and requirements for implementation.
Timely submission of deliverable (according to IT project schedule) without substantiative errors.
100%
Review of deliverable prior to acceptance.
B. Provide expertise and guidance on parameters and configuration details required for the on-going “fine-tuning” of probabilistic matching algorithm technologies, based on analysis and recommendations for enhanced performance of the matching and duplicate/error detection, including changes to matching thresholds and consideration of incorporation of additional data fields.
Timely submission of deliverable (according to IT project schedule) without substantiative errors.
100%
Review of deliverable prior to acceptance.
C. Provide analysis and reporting of Identity Management data, in order to provide guidance and information necessary for configuration, implementation, error detection, enhancement and other decisions, related to the probabilistic matching algorithm and/or management of identity data
Timely submission of deliverable (according to IT project schedule) without substantiative errors.
100%
Review of deliverable prior to acceptance.
5.3 Business and Technical Document Development and Review
A. Business document development and review: Summary of findings for each document reviewed.
Timely submission of deliverable [three (3) workdays after review is complete]. Business documents developed are well-written, fulfill the requirements, and require few revisions or corrections.
100%
Review of deliverable prior to acceptance.
B. Technical document development and review: Summary of findings for each document reviewed.
Timely submission of deliverable [three (3) workdays after review is complete]. Technical documents developed are well-written, fulfill the requirements, and require few revisions or corrections.
100%
Review of deliverable prior to acceptance.
5.4 Support of Data Quality, Data Governance, and Data Stewardship
A. Provide a comprehensive list of resolved data quality issues or tickets from internal and external stakeholders that have been investigated, analyzed, and resolved. The list shall also include identified defects and unresolved issues.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
B. Provide a monthly status report of any new or updated dashboards or other tools used to improve or monitor clinical or other quality measures.
Timely submission of deliverable (monthly) without substantiative errors.
100%
Review of deliverable prior to acceptance.
C. Provide a monthly status report of conference calls and/or meetings attended with data quality, data stewardship, and data governance entities in support of the incorporation of data quality, data governance, and data stewardship in VA processes and functions and resulting action items and follow-up.
Timely submission of deliverable (monthly) without substantiative errors.
100%
Review of deliverable prior to acceptance.
5.5 Requirements and Business Rules Development, Modification, and Validation
A. Provide new and/or updated business rules and requirements in the appropriate format.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
B. Provide submission of test plans and overview of testing completed including high-level test cases, testing results, and record of any recommendations for remediation that were submitted in support of User Acceptance Testing (UAT) on software development.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
5.6 Data Quality Analytics
A. Provide informal analysis in the form of a white paper, presentation, data report, dashboard, graph, table, or narrative within an email message as appropriate per analysis.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
B. Provide reports and findings from DQ analytics services performed in response to business process improvements or re-engineering requests in the form of formal written reports including tables, flow diagrams, dashboards, graphs and presentations.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
C. Provide deliverables for creation of data quality metrics and monitoring would be: creation of new metrics, and monitoring of DQ metrics, determined based on frequency of data refreshes and could be monthly, quarterly, or annually, and recurring monitoring that would identify issues or anomalies that need to be addressed and plans for remediation or improvement.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
5.7 OPTIONAL TASK – Data Quality Analytics
A. Provide informal analysis in the form of a white paper, presentation, data report, dashboard, graph, table, or narrative within an email message as appropriate per analysis.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
B. Provide reports and findings from DQ analytics services performed in response to business process improvements or re-engineering requests in the form of formal written reports including tables, flow diagrams, dashboards, graphs and presentations.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
C. Provide deliverables for creation of data quality metrics and monitoring would be: creation of new metrics, and monitoring of DQ metrics, determined based on frequency of data refreshes and could be monthly, quarterly, or annually, and recurring monitoring that would identify issues or anomalies that need to be addressed and plans for remediation or improvement.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
5.8 OPTIONAL TASK – Business and Technical Document Development and Review
A. Business document review: Summary of findings for each document reviewed.
Timely submission of deliverable [three (3) workdays after review is complete] without substantiative errors.
100%
Review of deliverable prior to acceptance.
B. Technical document review: Summary of findings for each document reviewed.
Timely submission of deliverable [three (3) workdays after review is complete] without substantiative errors.
100%
Review of deliverable prior to acceptance.
5.9 OPTIONAL TASK – Support of Data Quality, Data Governance, and Data Stewardship
A. Provide a comprehensive list of resolved data quality issues or tickets from internal and external stakeholders that have been investigated, analyzed, and resolved. The list shall also include identified defects and unresolved issues.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.
5.10 OPTIONAL TASK – Requirements and Business Rules Development, Modification, and Validation
A. Provide new and/or updated business rules and requirements in the appropriate format.
Timely submission of deliverable without substantiative errors.
100%
Review of deliverable prior to acceptance.

Methods of QA Surveillance Various methods exist to monitor performance. The COR shall use any or a combination of the surveillance methods listed below in assessing performance using this QASP.

1. 100% INSPECTION. (Evaluates all outcomes to include tasks and deliverables.)

Each deliverable will be reviewed by the program and the COR to determine acceptability prior to acceptance.Acceptable Quality LevelS (AQLs) Metrics and methods are designed to determine if performance exceeds, meets, or does not meet a given standard and AQL.

The AQLs are included in the Performance Metrics Section 6.5 of the PWS for Contractor performance and are structured to allow the Contractor to manage how the work is performed, while providing negative incentives for performance shortfalls.

Incentives The Government shall consider the Contractor’s performance when making a determination to exercise any options.

Documenting Performance

a. ACCEPTABLE PERFORMANCE

The Government shall document acceptable performance accordingly. Any report may become a part of the supporting documentation for any contractual action.

b. UNACCEPTABLE PERFORMANCE

When unacceptable performance occurs, the COR shall inform the CO. This will always be in writing although when circumstances necessitate immediate verbal communication, that communication will be followed up in writing. The COR shall document the discussion and place it in the COR file.

When the CO determines formal written communication is required, the COR shall prepare a Contract Discrepancy Report (CDR), and present it to the Contractor's program manager.

The Contractor shall acknowledge receipt of the CDR in writing to the CO. The CDR will state how long after receipt the Contractor has to take corrective action. The CDR will also specify if the Contractor is required to prepare a corrective action plan to document how the Contractor shall correct the unacceptable performance and avoid a recurrence. The CO shall review the Contractor's corrective action plan to determine acceptability.

Any CDRs may become a part of the supporting documentation for any contractual action deemed necessary by the CO.

Frequency of Measurement

a. Frequency of Measurement.

During contract/order performance, the COR will periodically analyze whether the negotiated frequency of surveillance is appropriate for the work being performed, and at a minimum shall be quarterly.

Quality of submission should also be considered. See examples below. Error rates or resubmits for content flaws would be the measures associated with these standards.

· Accuracy Work Products shall be accurate in presentation, technical content, and adhere to accepted elements of style.

· Clarity Work Products shall be clear and concise. Any/All diagrams shall be easy to understand and be relevant to the supporting narrative.

· Consistency to Requirements All work products must satisfy the requirements of this PWS.

· File Editing All text and diagrammatic files shall be editable by the VA in Windows-based or Adobe environments/platforms.

· Format - Follow specified VA Directives or Manuals and/or best business practices.

· Presentations - Presentations shall be clear, concise, executive-focused, and written in plain, clear English with minimal jargon, understandable by lay persons. The quality of deliverables directly contributes to organizational communications.

· Project Plan - Project Plan shall be comprehensive; recognize and address authority, perceptions, and concerns of stakeholders; incorporate scope of requisite requirements across the organization and/or agency.

· Reports - There shall be no omissions in the reports, documents or functional requirements.

· Publications and other documents - Deliverables shall be in formats appropriate to target audiences; user friendly, clear, thorough and comprehensive.

· Meeting support - Pre-meeting preparations and logistics demonstrate smooth meeting operations; complete comprehensive post-meeting summaries to include but not limited to: Minutes, Action Items, Attendees, Program Objectives and Milestones and major decision points.

· Analyses and Assessments - Analyses and assessments are performed with accuracy, completeness and adherence to industry best practices.

Obtain stakeholder input. Deliverables shall consist of the timely implementation of input mechanisms, and shall consist of an accurate and comprehensive synthesis of results and recommendations. Integration of relevant stakeholder input documented for each deliverable.

EVALUATION RATINGS DEFINITIONS

Rating
Definition
Notes

Exceptional

Performance meets contractual requirements and exceeds many to the Government’s benefit. The contractual performance of the element or sub-element being evaluated was accomplished with few minor problems for which corrective actions taken by the contractor were highly effective.

To justify an Exceptional rating, identify multiple significant events and state how they were of benefit to the Government. A singular benefit, however, could be of such magnitude that it alone constitutes an Exceptional rating. Also, there should have been NO significant weaknesses identified.

Very Good

Performance meets contractual requirements and exceeds some to the Government’s benefit. The contractual performance of the element or sub-element being evaluated was accomplished with some minor problems for which corrective actions taken by the contractor were effective.

To justify a Very Good rating, identify a significant event and state how it was a benefit to the Government. There should have been no significant weaknesses identified.

Satisfactory

Performance meets contractual requirements. The contractual performance of the element or sub-element contains some minor problems for which corrective actions taken by the contractor appear or were satisfactory.
To justify a Satisfactory rating, there should have been only minor problems, or major problems the contractor recovered from without impact to the contract/order. There should have been NO significant weaknesses identified. A fundamental principle of assigning ratings is that contractors will not be evaluated with a rating lower than Satisfactory solely for not performing beyond the requirements of the contract/order.

Marginal

Performance does not meet some contractual requirements. The contractual performance of the element or sub-element being evaluated 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.
To justify Marginal performance, identify a significant event in each category that the contractor had trouble overcoming and state how it impacted the Government. A Marginal rating should be supported by referencing the management tool that notified the contractor of the contractual deficiency (e.g., management, quality, safety, or environmental deficiency report or letter).

Unsatisfactory

Performance does not meet most contractual requirements and recovery is not likely in a timely manner. The contractual performance of the element or sub-element contains a serious problem(s) for which the contractor’s corrective actions appear or were ineffective.
To justify an Unsatisfactory rating, identify multiple significant events in each category that the contractor had trouble overcoming and state how it impacted the Government. A singular problem, however, could be of such serious magnitude that it alone constitutes an unsatisfactory rating. An Unsatisfactory rating should be supported by referencing the management tools used to notify the contractor of the contractual deficiencies (e.g., management, quality, safety, or environmental deficiency reports, or letters).

PERFORMANCE BASED SERVICE ASSESSMENT

CONTRACTOR: ________________________

GOVERNMENT REQUIRING ACTIVITY: _____________________

CONTRACT/ORDER NUMBER/ TITLE: _____________________

PERFORMANCE PERIOD COVERED: _____________________________________

NAME AND TITLE OF COR: _______________________________

DATE: __________________________

EVALUATION RATINGS FOR ASSESSMENT

EXCEPTIONAL

VERY GOOD

SATISFACTORY

MARGINAL

UNSATISFACTORY

All value ratings must be supported, objective and explained in the Narrative Section for each Performance Objective.

PERFORMANCE OBECTIVES:

A. TECHNICAL/QUALITY OF PRODUCT OR SERVICE: Rating: <Value>

How well does the contractor meet your Technical Requirement IAW the performance metrics in the PWS?

NARRATIVE: (enter narrative in box)

B. PROJECT MILESTONES AND SCHEDULE: Rating: <Value>

How well does the contractor meet the established schedule IAW the performance metrics in the PWS?

NARRATIVE: (enter narrative in box)

C. COST & STAFFING: Rating: <Value>

Are the staffing levels and expertise appropriate for accomplishing the mission IAW the performance metrics in the PWS?

Were the invoices current, accurate and complete?

D. MANAGEMENT: Rating: <Value>

How well did the contractor integrate/coordinate all activities needed to execute the contract IAW the performance metrics in the PWS?

QASP_Template_Mar_10_2016 image1.jpeg

File details come from the government source that posted it. Updated .