ATTACHMENT_8-Domain_8_Sample_RFTOP.docx

ATTACHMENT 8 SAMPLE TASK ORDER 8

DOMAIN 8: RFTOP 2016-8-Task Order 001

Antibiotic Use, Resistance, and Stewardship in Veterinary Practice.

ESTIMATED CEILING PRICE:

|X| Over $450,000 but less than $551,000

Proposed Period of Performance: Work shall begin from date of award of the order and shall continue for a period of 24 months. This project is a non-severable service funded that will be fully funded at the time of award Page Suggestion: The Contractor shall limit the proposal for this task order to 10 pages single-spaced pages.

DESCRIPTION OF WORK

1. Background and Need Antibiotic resistance is a growing problem in human and veterinary medicine, and given the dearth of new antibiotics being developed, it is very important that the human and veterinary medical profession work together to preserve the effectiveness of antibiotics that are currently available. In many households, humans are in close contact with their pets, which creates the opportunity to share bacterial microorganisms, including antibiotic resistant bacterial microorganisms. Humans can also be exposed to antibiotic resistant bacteria in foods of animal origin and through direct contact with food animals and their environments. There are opportunities to improve antibiotic use and stewardship in human and veterinary medicine, and the current project aims to address knowledge gaps in current antibiotic use and resistance in veterinary practice, and how addressing those gaps might help inform antimicrobial stewardship materials for veterinary and other relevant animal husbandry audiences.

It is important to understand current antibiotic prescribing practices and resistance so that, as more antibiotic stewardship principles are applied, the impact of adopting those principles can be measured and evaluated by the veterinary profession. There is a paucity of representative information on current antibiotic prescribing practices for common conditions affecting urinary, integumentary and respiratory systems that represents various types and sizes of veterinary practices. Representative data on antibiotic resistance in urinary tract, skin, respiratory and other pathogens infecting veterinary patients are also scarce, so veterinarians are unaware of local and regional antibiotic resistance patterns that could inform their current prescribing practices. Barriers to performing culture and susceptibility testing exist in many cases, and the available data may be biased towards complicated or refractory infections and therefore may not adequately represent the susceptibility of the majority of bacterial infections veterinarians treat. Measuring current antibiotic use and resistance is a key dimension in understanding current practice, determining if there are opportunities to improve use, and if so, developing stewardship guidance that will support antibiotic stewardship in companion animal and other veterinary settings.

2. Scope of Work The goal of this project is to improve antibiotic use, resistance, and stewardship in veterinary medicine by:

· Measuring current antibiotic prescribing, use, and resistance in veterinary practice as a pilot study.

· Implementing antibiotic stewardship principles in veterinary practice.

· Developing approaches to measure the impact of adopting antibiotic stewardship principle in veterinary practice for improvement of guidance and education materials and broad implementation amongst veterinary practitioners.

3. Tasks Overall: The contractor will work with their current networks of veterinary academic institutions and other veterinary partners to provide all labor, expertise, materials and supplies and perform all services required to carry out the work under this contract. The contractor will demonstrate their existing network of partners and develop a comprehensive design and implementation plan for pilot collection of representative antibiotic prescribing and resistance data in veterinary practice. The vendor will also provide a communications plan and recommendations for how antibiotic use and resistance data collection could be continued, expanded, and used to inform antibiotic stewardship educational efforts.

Task 1: Start Up meeting

· The Contractor shall arrange and conduct an initial meeting (by teleconference) with the CDC Contracting Officer Representative/Science Officer within 2 weeks of the effective date of the task order. The purpose of the meeting will be to discuss critical contract performance milestones, to delineate roles and responsibilities, and to establish communication protocols (such as a regular call schedule). Each task and deliverable will be reviewed.

· The Contractor shall submit an agenda for the above meeting within 1 week of the effective date of the task order.

· Desirable dimensions of antibiotic use and resistance data (for example animal species, body systems, practice types and volume) will be explored.

Task 2: Maintain Communication with the COR/CDC Science Officer

· The contractor will organize a second meeting, via webinar with the purpose of familiarizing CDC staff with the technical approach, networks, partners the vendor intends to work with to gather antimicrobial use in veterinary practice

· The contractor shall coordinate with the COR/Science Officer a monthly teleconference. The Contractor shall maintain regular communications with the Contracting Officer Representative/Science Officer involved with the project.

· The chief means of communication will be via conference calls that will be scheduled every month throughout the project period required to complete the project.

· Additional calls will be scheduled as needed.

· The vendor shall provide an agenda and meeting minutes for each call. All conference calls shall be scheduled and administered by the Contractor.

· The vendor shall respond to all emails and telephone communications from the COR/ Science Officer within 3 business days.

· In the event of multiple awards, the vendor shall participate on calls coordinated by the CDC COR/CDC Science Officer.

Task 3: Quarterly Progress Reports

· On the 10th day following the 3 months being reported. The contractor shall prepare and submit a quarterly progress report containing a summary of project activities and status updates on invoices. The report shall contain, at a minimum, the current progress on each of the requirements set forth below, the status of invoices pending on the project, problems encountered during the month, solutions implemented, planned activity for the upcoming month and any other information mutually agreed upon between the contractor and the CDC Contracting Officer Representative.

Task 4: Design a plan for pilot data collection on antibiotic use and resistance in veterinary practice

· The contractor will share the plan for pilot data collection with CDC stakeholders during an accompanying face-to-face presentation at CDC or webinar The design shall be limited to collecting only facility-level information. Include at a minimum the following:

· Technical description of key dimensions that will be captured, including proposed questions for participating facilities (CDC will review to determine whether subject to human subjects regulations apply)

· Anticipated volume of data per unit time

· Description of anticipated participants (providers and prescribers; non-animal)

· How participants will be de-identified or otherwise anonymized

· Proposed methods for validating data

· Draft example of what summary reports would look like

· Anticipated obstacles and proposed solutions

· Description of other potential barriers and possible solutions to ensure reporting within 12-18 months from the award date

Task 5: Implementation Plan

· The contractor, after incorporating input from Task 4, shall work with their networks and partners to enroll participants and perform the pilot data collection.

· The contractor shall provide bimonthly updates to the CDC Technical Monitor (or delegate) on progress, whether targets are being met, obstacles encountered and solutions implemented.

· The contractor shall discuss with their networks and veterinary partners what summary data would be most useful in the future to help inform prescribing practices, stewardship programs and/or educational materials.

Task 6: Final Report

· The contractor shall present a draft and final report (within 6 weeks after submission of a draft final report and within 4 weeks after receiving comments and recommendations on the draft report by CDC staff) of the project to the CDC Contracting Officer Representative. The report shall include:

· All prior reports

· A list of the contractor’s networks and partners (with names and contact information for points of contact) who helped develop the project

· The comprehensive design and implementation plans

· Summary of pilot data collected

· The contractor’s recommendations as to whether an ongoing surveillance project antibiotic use and resistance data collection could be designed based on lessons learned from the pilot project, and how such an ongoing system could be structured to inform practicing veterinarians and antibiotic stewardship educational efforts.

· A plan for communicating results of the pilot project to veterinary practitioners, veterinary colleges, and/or other relevant audiences

· A summary of lessons learned from the pilot project, suggested modifications that would be necessary in order to develop and validate an ongoing surveillance project

· Recommendations for future efforts related to this project.

Deliverables Summary

The following deliverables shall be provided to the COR/Science officer no later than the dates specified below:

Frequency Due Date

In person/ webinar presentations describing technical approach, network, partners, and systems Monthly

Agenda at least one day before the conference call. Responses to emails and telecommunications within 2 days of event.

2 months after award

3-4 months after award

1 final 22 months after award 24 months after award

1. General Information

A. Place of Performance: The work to be performed under this contract will be performed at the Contractor’s facility and associated academic, healthcare, or research facilities as required.

B. Type of Contract: The government will award a firm-fixed contract.

C. Contractor Travel: Contractor may be required to travel to Atlanta, Georgia for a face-to-face meeting during the first year of the project to discuss project implementation. The need for travel shall be determined by CDC, and may be substituted with a teleconference or webinar not requiring travel. Travel shall be in accordance with the Federal Travel Regulation (FTR) and the limitation of funds specified in this contract.

D. Data Rights : 52.227-14 Rights in Data-General, Alternate IV (Dec 2007). As prescribed in 27.409(b)(5), substitute the following paragraph (c)(1) for paragraph (c)(1) of the basic clause: (c) Copyright—(1) Data first produced in the performance of the contract. Except as otherwise specifically provided in this contract, the Contractor may assert copyright in any data first produced in the performance of this contract. When asserting copyright, the Contractor shall affix the applicable copyright notice of 17 U.S.C. 401 or 402, and an acknowledgment of Government sponsorship (including contract number), to the data when such data are delivered to the Government, as well as when the data are published or deposited for registration as a published work in the U.S. Copyright Office. For data other than computer software, the Contractor grants to the Government, and others acting on its behalf, a paid-up, nonexclusive, irrevocable, worldwide license for all such data to reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, by or on behalf of the Government. For computer software, the Contractor grants to the Government and others acting on its behalf, a paid-up, nonexclusive, irrevocable, worldwide license for all such computer software to reproduce, prepare derivative works, and perform publicly and display publicly (but not to distribute copies to the public), by or on behalf of the Government.

E. Confidentiality of Information: Work on this project may require that personnel have access to Privacy Information. Personnel shall adhere to the Privacy act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations. The user agency will identify and provide direction and guidance for safeguarding all information subject to the Privacy Act. Reports and case files containing individual personal information are confidential. The CDC is not authorized to release individual case reports, and access to individual case data is strictly controlled. The contractor personnel are required to work with case records as well as databases. It is a requirement that the data remain in a controlled access environment.

F. Section 508: Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) helps to ensure that federal employees with disabilities have access to, and use of, the information and data they need to do their jobs. Furthermore, this law ensures that members of the public with disabilities have the ability to access government information and services. Regardless of format, all Web content or communications materials produced for publication on or delivery via CDC Web sites - including text, audio or video - must conform to applicable Section 508 standards to allow federal employees and members of the public with disabilities to access information that is comparable to information provided to persons without disabilities. All contractors (including subcontractors1) or consultants responsible for preparing or posting content intended for use on a CDC-funded or CDC-managed Web site must comply with applicable Section 508 accessibility standards, and where applicable, those set forth in the referenced policy or standards documents below. Remediation of any materials that do not comply with the applicable provisions of 36 CFR Part 1194 as set forth in the SOW or PWS, shall be the responsibility of the contractor or consultant retained to produce the Web-suitable content or communications material. Checklists for various file formats are available at http://www.hhs.gov/web/508/index.html.

The following Section 508 provisions apply to the content or communications material identified in this SOW or PWS: 36 CFR 1194.21 (for software and programmatic elements in websites), 36 CFR 1194.22 (for documents and websites), and 36 CFR 1194.24 (for video and multimedia content) References: HHS Policy for Section 508 Electronic and Information Technology (E&IT) (January 2005): http://www.hhs.gov/od/Final_Section_508_Policy.html HHS Section 508 Web site: http://508.hhs.gov/ HHS ASPA Web Communications Division Web site: http://www.hhs.gov/web/policies/index.html US General Services Administration (GSA) Section 508 Web site: http://www.section508.gov/index.cfm 1 Prime contractors may enter into subcontracts in the performance of a Federal contract, but the prime remains obligated to deliver what is called for under the contract.

G. Security Compliance: The below information complies with HHSA Security compliance requirements for E-Government Act of 2002 (FISMA 2002) and Federal Information Security Modernization Act of 2014 (FISMA 2014)

If the contractor will host or create an information system on behalf of the CDC, provide IT services to the CDC, or provide IT products to the CDC, then the contractor must comply with the applicable IT security references below. We provide the following information to assist in the preparation of documents necessary for the Security Assessment and Authorization (SA&A) of an Information System. The FISMA 2014, (Federal Information Security Modernization Act of 2014) and the below federal policies dictate the framework for assuring information security for data systems operated by or on behalf of the Federal government. These are summarized below.

OMB Circular A-130 (https://www.whitehouse.gov/omb/Circulars_a130_a130trans4/) establishes policy for the management of Federal information resources, pursuant to a number of laws and regulations, including the Paperwork Reduction Act of 1980 (amended in 1995), the Computer Security Act of 1987, and other laws. Circular A-130 requires all federal information systems to have security plans, emergency response capabilities, designated individuals who are responsible for security, security awareness training, and regular review of the system. Appendix III of Circular A-130, entitled “Security of Federal Automated Information Resources,” establishes a minimum set of controls to be included in Federal automated information security programs; assigns Federal agency responsibilities for the security of automated information; and links agency automated information security programs (such as the DHHS AISSP) with OMB Circular No. A-123

The Federal Information Security Management Act of 2002 (P.L. 107-347) (FISMA) (http://csrc.nist.gov/drivers/documents/FISMA-final.pdf ) and the Federal Information Security

Modernization Act of 2014 (P.L. 113-283) (FISMA 2014) (https://www.congress.gov/113/plaws/publ283/PLAW-113publ283.pdf) requires each agency to develop, document, and implement an agency-wide information security program to safeguard information and information systems that support the operations and assets of the agency, including those provided or managed by another agency, contractor (including sub-contractor), or other source. The National Institute of Standards and Technology (NIST) has issued a number of publications that provide guidance in the establishment of minimum security controls for management, operational, and technical safeguards needed to protect the confidentiality, integrity, and availability of a Federal information system and its information.

Pursuant to Federal and HHS Information Security Program Policies the following standards and guidelines apply:

1. FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems (http://csrc.nist.gov/publications/fips/fips200/FIPS-200-final-march.pdf),

1. FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems (http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-final.pdf),

1. NIST Special Publication 800-18, Guide for Developing Security Plans for Federal Information Systems (http://csrc.nist.gov/publications/nistpubs/800-18-Rev1/sp800-18-Rev1-final.pdf),

1. NIST Special Publication 800-60, Guide for Mapping Types of Information and Information Systems to Security Categories Vol. 1 (http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol1-Rev1.pdf) and Vol. 2 (http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol2-Rev1.pdf),

1. NIST Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach (http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r1.pdf),

1. NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organizations (http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf),

1. NIST Special Publication 800-63, Electronic Authentication Guideline (http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63-2.pdf).

The System Security Plan (SSP) is part of the Security Assessment and Authorization (SA&A) process required by the FISMA 2014 and NIST Special Publication 800-18, 800-37 and will include selected mandatory controls required by NIST Special Publication 800-53, Volume I & II. The successful contractor in conjunction with the NCEZID Information System Security Officer (ISSO) will submit SA&A documentation to the CDC Chief Information Security Officer (CISO). The successful completion of the SA&A documents will result in an award of an Authority To Operate. Based on guidance in FIPS 199 and NIST SP 800-60 the system will be assigned an overall security category (SC) of LOW or MODERATE based on (confidentiality, LOW/MODERATE), (integrity, LOW/MODERATE), and (availability, LOW/MODERATE) impact levels. These impact levels will be initially determined by the NCEZID ISSO and confirmed by the CDC Certifying Authority as part of the SA&A process.

The successful contractor is responsible for providing pertinent security information to the NCEZID ISSO and Security Staff and assisting in completing the below CDC SA&A documents to include Annual Assessments, Annual Business Continuity Plan, Re-Certifications and applicable significant/non-significant change requests. Appropriate security templates will be provided to the successful Contractor by the NCEZID Security Staff. Completed documents will be sent by the NCEZID Security Staff to the CDC Chief Information Security Office (CISO) for review, approval and subsequent issuance of an Authority To Operate (ATO)

1. Baseline System Information (BSI)

1. Privacy Impact Assessment (PIA)

1. System Security Plan (SSP)

1. Business Continuity Plan (BCP)

1. Risk Assessment Report (RAR)

The Contractor shall respond to the following seven security–associated requirements in the application:

(1) Position Sensitivity Designations CDC requires a Public Trust Level 5 for the following

The following position sensitivity designations and associated clearance and investigation requirements apply under this licensing contract:

Level 5: Public Trust - Moderate Risk (Requires Suitability Determination with NACIC, MBI or LBI). Licensor employees assigned to a Level 5 position with no previous investigation and approval shall undergo a National Agency Check and Inquiry Investigation plus a Credit Check (NACIC), a Minimum Background Investigation (MBI), or a Limited Background Investigation (LBI).

Upon award, the Licensor will be required to submit a roster of all staff (including sub-contractor staff) working under the contract that will have the ability to access NCEZID sensitive information from the system.

Non-Disclosure Agreements The Contractor and any sub-Contractors or employees are forbidden from sharing any technical or logistical information they may gain in conjunction with matters related to this task order that could jeopardize the physical or information security of CDC or its employees, projects, or information systems.

The following apply to Licensor employees and their subcontractors associated with the project:

1. Personnel may not begin work under the contract until the contractor has submitted the employee roster and non-disclosure agreements as described above.

1. Personnel without necessary background investigations will not have access to sensitive project data.

1. Violation of these conditions may lead to termination of the contract.

It is the Contractor's responsibility to ensure that all employees have met CDC and federal requirements, such as, for example, completion of background checks, before gaining or utilizing access to CDC information technology resources.

(2) Privacy Compliance Licensor in conjunction with CDC Center ISSO shall conduct and maintain an initial Privacy Impact Assessment (PIA) as defined by Section 208 of the FISMA 2014. Periodic reviews shall be conducted by the system owner, with assistance from the CDC Center ISSO and contractor, to determine if a major change to the system has occurred, and if a PIA update is needed.

(3) Contractor’s Official Responsible for Information Security The contractor shall include in the “Information Security” part of the Technical Proposal the name and title of its official who will be responsible for all information security requirements shall the contractor be selected for an award.

(4) Rules of Behavior The contractor’s employees and subcontractors shall comply with the HHS Information Technology General Rules of Behavior.

(5) Information Security Training HHS policy requires that contractors and subcontractors shall receive security training commensurate with their responsibilities for performing work under the terms and conditions of their contractual agreements. The successful contractor shall be responsible for assuring that each employee, including subcontractors, has completed the HHS Computer Security Awareness Training course (or another course designated by CDC) prior to performing any contract work, and thereafter completing the HHS-specified annual refresher course during the period of performance of the contract. This would be provided at the Contractor's expense and would be the Contractor's responsibility to plan and arrange.

The successful contractor shall maintain a listing of all individuals who have completed this training and shall submit this listing to the Science Officer.

(6) HSPD-12 Compliance Federal Information Processing Standard 201 (FIPS-201) (vii) compliant, Homeland Security Presidential Directive 12 (HSPD-12) card readers shall: (a) be included with the purchase of servers, desktops, and laptops; and (b) comply with FAR Subpart 4.13, Personal Identity Verification.

As part of the Federal HSPD-12 directive, all information systems deployed within/outside of any federal infrastructure must be able to support HSPD-12 compliant Personal Identity Verification (PIV) of federal employees and contractors. The government has complied with HSPD-12 by issuing PIV cards with embedded digital certificates to all users of federal information systems. In accordance with this directive, all contractors providing hardware and software to the federal government are now required to ensure that these PIV cards will integrate with their software and hardware at the application level. Contractor must be able to implement and support PIV card integration.

(7) Encryption

All sensitive CDC-funded data stored on desktop computers used on behalf of HHS shall be secured either through a FIPS 140-2 compliant encryption solution or through adequate physical security and operational controls at the desktop’s residing location.

All mobile devices, portable media and transfer data files that contain CDC- data shall have full-disk encryption using FIPS 140-2 compliant algorithms.

2. Government Furnished Property, Equipment, and Services (Not Applicable)

3. Payment Terms

Payment will be made quarterly and subject to receipt of deliverables in accordance with the payment schedule established herein and in accordance with FAR 52.232-25. Prompt Payment, which states that the due date for making invoice payments shall be the 30th day after the designated billing office (see block 21 of the order) has received a proper invoice from the contractor or the 30th day after Government acceptance of the services provided by the contractor, whichever is later.

Quarter 1

Quarter 2

Quarter 3

Quarter 4

Quarter 5

Quarter 6

Quarter 7

Quarter 8

4. Special Clearances:

|_| OMB

|_|Human Subjects

|_| Print

SPECIAL CLAUSES:

HHSAR 352.224-70, Privacy Act (Dec 2015) This contract requires the Contractor to perform one or more of the following:

(This contract requires the Contractor to perform one or more of the following: (a) design; (b) develop; or (c) operate a Federal agency system of records to accomplish an agency function in accordance with the Privacy Act of 1974 (Act) (5 U.S.C. 552a(m)(1)) and applicable agency regulations. The term system of records means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual. Violations of the Act by the Contractor and/or its employees may result in the imposition of criminal penalties (5 U.S.C. 552a (i)).The Contractor shall ensure that each of its employees knows the prescribed rules of conduct in 45 CFR part 5b and that each employee is aware that he/she is subject to criminal penalties for violation of the Act to the same extent as Department of Health and Human Services employees. These provisions also apply to all subcontracts the Contractor awards under this contract which require the design, development or operation of the designated system(s) of records (5 U.S.C. 552a(m)(1)). The contract work statement: (a) Identifies the system(s) of records and the design, development, or operation work the Contractor is to perform; and (b) specifies the disposition to be made of such records upon completion of contract performance.

HHSAR 352.270-12 Needle Exchange (December 18, 2015) The Contractor shall not use any funds obligated under this contract to carry out any program of distributing sterile needles or syringes for the hypodermic injection of any illegal drug.

(End of Clause)

CONTRACTING OFFICER REPRESENTATIVE:

TBD

SCIENCE OFFICER:

TBD

5. Technical Evaluation Criteria

Award: This task order will be awarded to the contractor whose proposal is considered to be the most advantageous to the Government, price and other factors identified below considered. Technical factors will be more important in the evaluation than price. The Government will not make an award at a significantly higher overall cost to the Government to achieve only slightly superior performance.

Technical Evaluation for this RFTOP is as follows:

A. Technical Plan (10):

1. The Contractor shall provide a detailed plan of their approach for providing the required services, included details that have been specified. This shall be in the contractor’s own words, not a restatement of listed requirements. The plan shall describe in detail the current relationship the contractor has with networks of veterinary institutions and other veterinary partners and potential participants in the project.

2. The Contractor must provide documentation of previous work and collaborations with veterinary practitioners and organizations in the form of peer-reviewed publications on this and directly related topics, web-based materials on antibiotic resistance and stewardship, past and current cooperative agreements with veterinary practitioners, colleges of veterinary medicine and other partners directly related to veterinary prescribing practices and antibiotic resistance in animals.

B. Similar Experience (10):

1. The contractor shall provide information reflecting the contractor’s organizational experience with projects similar in nature, scope, and complexity.

2. The contractor shall provide details on previous research work on antibiotic use, resistance, and stewardship specific to veterinary practice.

3. The contractor shall have substantial experience in the field of animal healthcare or animal healthcare epidemiology.

4. The Contractor shall have experience conducting projects related to resistance and use of antibiotics in companion animal and/or other veterinary species.

5. The Contractor shall have demonstrated experience to initiate and lead quality improvement projects and/or multiple steps across the spectrum of scientific inquiry including formulating a research question related to antibiotic resistance and/or use in veterinary species, developing a detailed plan and protocol designed to address the question, including epidemiological and prevention research plans and protocols, and successfully implementing the protocol, analyzing and interpreting results, and presenting and leading publication of the findings in peer reviewed literature and in web-based materials.

C. Staffing and Management Plan (10):

1. The Contractor shall provide a detailed statement of staffing and management approach for managing the work outlined in this task order by demonstrating their understanding of the labor requirements listed in this RFTOP. Contractor shall include:

a. Resumes from key personnel outlining the credentials and background of key management, professional, and technical personnel to be used for this task order, including the percent time on this and other projects;

b. Detailed plan that describes current staff available for this task order and how the team will interface with CDC, as well as descriptions of methods the Offeror’s approach to rapidly obtain and/or replace qualified staffing resources to support the contract;

c. Clear delineation of staff authorities and line of responsibility with special emphasis on relationships with subcontractors, other Office of Antibiotic Stewardship Contractors, and CDC partners;

d. Detailed description of how conflicts are managed; and

e. Measurement of fiscal responsibility and accountability paying particular attention to the deliverable timeline in this task order.

2. Ideal staffing to successfully accomplish the tasks of this acquisition include some portion of time from the following individuals:

a. Project Manager with sufficient time devoted to overseeing the implementation of the project. This person shall have experience in veterinary public health related projects and existing networks of veterinary institutions and other veterinary partners, and shall be well versed in veterinary antibiotic prescribing practices.

b. Subject Matter Expert/Technical Consultant (or Data Analyst) with experience in oversight of study and analysis of scientific data and familiarity with veterinary antibiotic prescribing practices.

c. Subject Matter Expert/Technical Consultant with experience with veterinary medical information systems.

SHEPheRD RFTOP 2016-8-001