B.01.__QASP_for_W81XWH19Q0270__-_In-silico_Screening.pdf

QUALITY ASSURANCE AND SURVEILLANCE PLAN

For In-Silico Screening for Drug Discovery Contract Number: < upon award, enter contract number>

Contract Description: This is a service requirement for the technical expertise and support services necessary to perform in-silico screening of commercially available database(s) for novel small- molecule drug discovery, docking of drug candidates into protein targets, and performing molecular modeling in support of the Wound Infections Department (WID), Bacterial Diseases Branch (BDB), Walter Reed Army Institute of Research (WRAIR).

Contractor’s name: < upon award, enter contractor name > (hereafter referred to as the contractor).

Contents

1. PURPOSE

2. GOVERNMENT ROLES AND RESPONSIBILITIES

3. CONTRACTOR REPRESENTATIVES

4. PERFORMANCE REQUIREMENTS SUMMARY MATRIX

5. METHODS OF SURVEILLANCE ................................................ Error! Bookmark not defined.

PERFORMANCE REPORT

CONTRACT DISCREPENCY REPORT (CDR)

1. PURPOSE

This Quality Assurance Surveillance Plan (QASP) provides a systematic method to evaluate performance for the stated contract. This QASP explains the following:

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

This QASP does not detail how the contractor accomplishes the work. Rather, the QASP is created with the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. It is the Government’s responsibility to be objective, fair, and consistent in evaluating performance. In addition, the QASP should recognize that unforeseen and uncontrollable situations may occur.

This QASP is a “living document” and the Government may review and revise it on a regular basis. However, the Government shall coordinate changes with the contractor. Updates shall ensure that the QASP remains a valid, useful, and enforceable document. Copies of the original QASP and revisions shall be provided to the contractor and Government officials implementing surveillance activities.

The following FAR clauses may apply depending on contract type:

52.246-4 Inspection of Services – Fixed-Price

2. GOVERNMENT ROLES AND RESPONSIBILITIES

The following personnel shall oversee and coordinate surveillance activities.

Contracting Officer (KO) - The KO 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 KO shall also assure that the contractor receives impartial, fair, and equitable treatment under this contract. The KO is ultimately responsible for the final determination of the adequacy of the contractor’s performance.

Assigned KO: Laura Tomitz Organization or Agency: USAMRAA Telephone: 301-319-2051 Email: laura.a.tomitz.civ@mail.mil

Contract Specialist (CS) - The CS acts as an acquisition consultant and serves as liaison between the contract office and Walter Reed Army Institute of Research (WRAIR).

Assigned CS: Brenda Mena Telephone: 301-788-4321 Email: brenda.i.mena.civ@mail.mil

Contracting Officer’s Representative (COR) - The COR is responsible for technical administration of the contract and shall assure proper Government surveillance of the contractor’s performance. The COR shall keep a “QASP and Performance” file. At the conclusion of the contract or when requested by the KO, the COR shall provide documentation to the KO. The COR is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf. The contractor shall refer any changes they deem may affect contract price, terms, or conditions to the KO for action.

Assigned COR: <enter name> Telephone: <enter number> Email: <enter address>

Other Key Government Personnel - <enter name or delete these lines if not applicable. This may include Performance Monitors, Inspectors, etc. who act on behalf of the COR to monitor performance.> Title: <enter title>

3. CONTRACTOR REPRESENTATIVES

The following employees of the contractor serve as the contractor’s Program Manager and Task Manager for this contract. <Communication should occur with them during QASP development. It will help if they review the draft QASP and accept the final version. You may delete the stated roles or change the naming convention if applicable. >

Program Manager - <upon award, enter name> Telephone: <enter number> Email: <enter address>

Task Manager - <upon award, enter name> Telephone: <enter number> Email: <enter address>

Other Contractor Personnel - <upon award, enter name or delete these lines if not applicable> Title: <enter title>

4. PERFORMANCE REQUIREMENTS SUMMARY MATRIX

PERFORMANCE REQUIREMENTS SUMMARY MATRIX

# PW

S Ref.

Performance Objective Performance Measurement

Acceptable Quality Level

Method of Surveillance Incentive

1 6.2.3 6.2.3 .1

Operating System Requirement The contractor shall have Linux operating systems or Mac OS X, capable of performing the tasks outlined in this PWS, including writing computer scripts such as PERL, Linux batch script, and commercial molecular simulations software

Contractor shall possess the required operating systems to perform the tasks set forth in this PWS; calculated by percentage of tasks completed

Meets: 100%.

Does Not Meet: <100%

Direct observation by

COR

Frequency: As needed

Past Performance

2 6.2.3 .2

Technical and Functional Support The contractor shall possess the technical capability to provide support to the COR in the use of Linux computer cluster

Contractor shall possess the technical knowledge to support the COR in all tasks set forth in this PWS; calculated by number of complaints by

COR

At most 1 complaint per period of performance

Direct observation by

COR

Frequency:

Annual

Past Performance

3 6.2.4

Location and Accessibility The contractor shall be within 50 miles of WRAIR to meet in-person with the COR

Contractor shall be available for all in-person meeting requested by

COR

At most 1 missed meeting per month

Direct observation by

COR

Frequency:

Monthly

4 6.2.4 .1 6.2.5 .2

Operating System Accessibility The contractor shall provide the COR with access to the contractor location to process data using the Linux cluster, in order to further refine the co-crystal structure.

Contractor operating system shall be available at requested of COR

At most 1 incident of unavailability per quarter

Direct observation by

COR

Frequency:

Quarterly

Past Performance

5 17.1 1.1

Installation Access - Contractor shall follow installation access procedures.

Sum of all incidents in which contractor personnel did not follow installation access procedures

< 1 incident per month

Direct observation by

COR and installation security.

Past Performance

6 17.1 1.5

OPSEC SOP –

Contractor shall submit OPSEC SOP that meets minimum quality standards.

Number of calendar days after contract award that the contractor submits the OPSEC SOP to the COR

< 90 calendar days after contract award

COR receipt of

OPSEC SOP

PERFORMANCE REPORT

Contract Number: <insert number>

Prepared by: (Name of COR) <insert name>

Date and time of observation: <insert date>

Observation:

<Examples of items to include in a report are:

- Method of surveillance.

- How frequently you conducted surveillance.

- Surveillance results (Exceeds, Meets, Does Not Meet).

- Number of observations.>

Prepared by: <Enter COR’s name>

COR’s Signature Date

CONTRACT DISCREPENCY REPORT (CDR)

< The COR may initiate a CDR at any time, including whenever the number of monthly recorded defects for a performance standard exceeds the allowable number of defects; anytime unacceptable performance is determined critical in nature and requires formal corrective action; and whenever an unfavorable trend is detected in contractor performance.>

Contract Number: <insert number>

Contractor Project Manager: <insert name>

From: <insert name of COR>

Date and time observed discrepancy:

Contract Discrepancy:

<Describe in detail. Identify any attachments.>

Corrective action plan:

A written corrective action plan < is / is not > required.

< If a written corrective action plan is required include the following. > The contractor shall provide the COR with the Corrective Action Plan not later than < # days after receipt of this CDR. >

Prepared by: <Enter COR’s name>

COR’s Signature Date

Received by: <Enter contractor project manager’s name>

Contractor Project Manager’s Signature Date