View the file

Other files

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

REQUEST FOR QUOTATIONS

(THIS IS NOT AN ORDER)

THIS RFQ X IS IS NOT A SMALL BUSINESS SET-ASIDE.

PAGE OF PAGES

1. REQUEST NO.

2. DATE ISSUED

3. REQUISITION/PURCHASE REQUEST NO.

00HCUHCB-2020-45411

4. CERT. FOR NAT. DEF.

UNDER BDSA REG. 2

AND/OR DMS REG. 1

RATING

5a. ISSUED BY

Centers for Disease Control and Prevention (CDC)

Office of Acquisition Services (OAS)

2900 Woodcock Blvd, MS TCU-4

Atlanta GA 303414004

6. DELIVERY BY (Date)

5b. FOR INFORMATION CALL (No collect calls)

NAME
TELEPHONE NUMBER
AREA CODE
NUMBER
Henrietta Fumbah Wei
(770)
488-8239 x
8. TO:
9. DESTINATION
a. NAME
b. COMPANY
a. NAME OF CONSIGNEE
c. STREET ADDRESS
b. STREET ADDRESS

c. CITY

d. CITY
e. STATE
f. ZIP CODE
d. STATE
e. ZIP CODE

10. PLEASE FURNISH QUOTATIONS TO

THE ISSUING OFFICE IN BLOCK 5a ON

OR BEFORE CLOSE OF BUSINESS (Date)

IMPORTANT: This is a request for information, and quotations furnished are not offers. If you are unable to quote, please so indicate on this form and return it. This request does not commit the Government to pay any costs incurred in the preparation of the submission of this quotation or to contract for supplies or services. Supplies are of domestic origin unless otherwise indicated by quoter. Any representations and/or certifications attached to this Request for Quotations must be completed by the quoter.

11. SCHEDULE (Include applicable Federal, State and local taxes)

ITEM NO.

(a)

SUPPLIES/SERVICES

(b)

QUANTITY

(c)

UNIT

(d)

UNIT PRICE

(e)

AMOUNT

(f)

For questions please contact Gbolii Henrietta Fumbah Wei at ehu0@cdc.gov Or (404)-498-8239

Deadline for quotes:

Noon, August 11, 2020 EST Please email quotes to Gbolii Henrietta Fumbah Wei at ehu0@cdc.gov

12. DISCOUNT FOR PROMPT PAYMENT
a. 10 CALENDAR DAYS

b. 20 CALENDAR DAYS

c. 30 CALENDAR DAYS

d. CALENDAR DAYS

NUMBER
PERCENTAGE

NOTE: Additional provisions and representations

13. NAME AND ADDRESS OF QUOTER
14. SIGNATURE OF PERSON AUTHORIZED TO

SIGN QUOTATION

15. DATE OF

QUOTATION

a. NAME OF QUOTER

b. STREET ADDRESS
16. SIGNER
a. NAME (Type or print)
b. TELEPHONE

c. COUNTY

AREA CODE

d. CITY
e. STATE
f. ZIP CODE
c. TITLE (Type or print)
NUMBER

AUTHORIZED FOR LOCAL REPRODUCTION

STANDARD FORM 18 (REV. 6-95)

Previous edition not usable

Prescribed by GSA

FAR (48 CFR) 53.215-1(a)

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

ITEM
SUPPLIES / SERVICES
QTY / UNIT
UNIT PRICE
EXTENDED PRICE
0001
Enhancing the National Violent Death Reporting System (NVDRS) Restricted Access Database (RAD) Through Automation

Period of Performance: 9/1/2020 – 8/31/2021

Firm Fixed Price

Severable Line Item

1 Job
$0
$0
0002
Option 1: Enhancing the National Violent Death Reporting System (NVDRS) Restricted Access Database (RAD) Through Automation

Period of Performance: 9/1/2021 – 8/31/2022

Firm Fixed Price

Severable Line Item

1 Job
$0
$0
0003
Option 2: Enhancing the National Violent Death Reporting System (NVDRS) Restricted Access Database (RAD) Through Automation

Period of Performance: 9/1/2022 – 8/31/2023

Firm Fixed Price

Severable Line Item

1 Job
$0
$0

B.1. Continuous Support of Organization:

If reorganization or other actions impact the Government’s Department/Agency/Division/or Program Office name, office structure, number of offices and divisions, or name of divisions, the Contractor shall continue to provide support to the new organization that is directly derived from such Department/Agency/Division/or Program Office. The Contractor shall continue supporting the core group that evolves, as described herein, whether or not this contract is formally modified to incorporate the new nomenclature or office structure.

Section C - Description/Specification/Work Statement

Title: Enhancing the National Violent Death Reporting System (NVDRS) Restricted Access Database (RAD) Through Automation

C.1 – BACKGROUND

Violence is a major public health problem. In 2017, more than 67,000 people died violently in the U.S., or seven deaths per hour (1). Approximately 47,173 people died by suicide. Suicide is the 10th leading cause of death for Americans and the 2nd leading cause of death among persons aged 10-34 years (2). In 2017, a total of 19,510 people died by homicide (1), the 3rd leading cause of death that year among persons aged 15-34 years (2). The economic costs are staggering, with suicide costing the U.S. economy $50.8 billion and homicide $26.4 billion (3). Information is needed to describe the magnitude and circumstances of violent deaths in order to help inform and develop violence prevention programs.

The National Violent Death Reporting System (NVDRS) was implemented in 2003 in response to an Institute of Medicine (now National Academy of Medicine) report citing the need for surveillance of fatal violent injuries. NVDRS is a surveillance system funded by the Centers for Disease Control and Prevention (CDC) and implemented by state and territorial health departments or their bona fide agents. The system is unique as it uses information primarily from three sources: death certificates (vital statistics), coroner/medical examiner reports (including toxicology reports), and law enforcement reports to provide states and communities a comprehensive picture of the circumstances surrounding violent deaths. NVDRS data are collected under federal security and confidentiality guidelines that govern surveillance activities.

NVDRS data are stored in an incident-based database. Detailed data from NVDRS are available through the NVDRS Restricted Access Database (RAD) to approved researchers. NVDRS RAD is a de-identified, multi-year, multi-state, case-level dataset comprised of hundreds of unique variables. The data set is available to researchers who meet eligibility criteria. The NVDRS RAD database also includes short narratives to describe violent deaths, including descriptions abstracted from law enforcement and medical examiner or coroner reports. There is no cost for accessing the NVDRS RAD. The NVDRS RAD was created to provide researchers the opportunity to analyze the data. The NVDRS RAD database currently consists of data from 2003–2017. The NVDRS dataset is currently provided via secure file transfer protocol (FTP).

Researchers initiate the process for accessing the NVDRS RAD data set by sending an email to the CDC NVDRS RAD Help Desk. Historically, NVDRS Science Officers have triaged the NVDRS RAD Help Desk and have rotated who is the lead for managing requests on a monthly basis. The lead Science Officer for NVDRS RAD sends information to the researcher about how to apply for the NVDRS RAD and the supporting documents needed to complete their application. As part of the application process, researchers are required to submit 1) a cover letter on official home institution letterhead, 2) a concept proposal (including documentation of Institutional Review Board review, if needed), 3) a spreadsheet that lists variables needed for the analysis, 4) and a signed Data Sharing Agreement. The application is reviewed by the NVDRS RAD review committee, which consists of 3-4 scientific and data analysis experts within CDC’s National Center for Injury Prevention and Control (NCIPC). Members of the review committee include the Team Lead for the Mortality Surveillance Team (MST), one NVDRS Science Officer, the Division of Violence Prevention (DVP) Associate Director for Science, as needed, and NCIPC’s Information Systems Security Officer (ISSO). The NVDRS RAD review committee’s feedback is compiled by the lead NVDRS Science Officer and sent to the researcher, who may be asked to provide revisions and to submit an updated application.

Once the application is approved, the lead NVDRS Science Officer sends the researcher a letter of approval, and the request is sent to a data analyst to prepare the requested data set. The data set and other supporting documents are then shared via a secure file transfer protocol (FTP). Researchers are expected to obtain appropriate written permissions from CDC in the form of an amendment for changes to a previously approved application that may substantially alter study questions or proposed analyses, add new investigators or staff, or add additional data years or variables. Amendments are also initiated via emails to the NVDRS RAD Help Desk.

Since its inception, the number of NVDRS RAD requests has grown, from 3 in 2014 to a high of 91 in 2019. The purpose of this contract is to create an electronic, automated system to enable the MST to respond more quickly and efficiently to NVDRS RAD requests (queries about the NVDRS RAD as well as requests for NVDRS RAD data). The system will be used by researchers to submit inquiries and RAD packages, and used by MST to streamline and simplify the RAD application review process through automation. Given the increased number of NVDRS RAD applications, the proposed funding will support building an automated infrastructure for the NVDRS RAD.

CDC staff will have access to this system that fulfills NVDRS RAD requests and automates the NVDRS RAD Help Desk. The system will allow MST to

· Conduct an assessment of the NVDRS RAD process from start (when a researcher submits a question or application) to finish (when a researcher receives the data set)

· Allow for queries to identify the number of NVDRS RAD requestors (including initial applications as well as amendments to previously approved applications), how the requestor heard about the NVDRS RAD, their institution (e.g., academia, hospitals, non-governmental organizations), whether they are repeat users, and description of any products, reports, or publications that used the NVDRS RAD data

· The system will also be designed to include links to and allow for uploading of published manuscripts and reports

1. CDC, National Center for Injury Prevention and Control. Web-based Injury Statistics Query and Reporting System (WISQARS) [online]. Atlanta, GA: CDC; 2019. https://www.cdc.gov/injury/wisqars/index.html

2. CDC, National Center for Health Statistics, National Vital Statistics System. 10 Leading Causes of Death by Age Group, United States – 2017. Produced by: National Center for Injury Prevention and Control, CDC, using WISQARS [online]. Atlanta, GA: CDC: 2019. https://www.cdc.gov/injury/images/lc-charts/leading_causes_of_death_by_age_group_2017_1100w850h.jpg

3. Florence C, Simon T, Haegerich T, Luo F, Zhou C. Estimated Lifetime Medical and Work-Loss Costs of Fatal Injuries--United States, 2013. MMWR Morb Mortal Wkly Rep. 2015 Oct 2;64(38):1074-7. doi: 10.15585/mmwr.mm6438a4.

SUBSECTION A – DEFINITIONS

National Violent Death Reporting System (NVDRS) – web-based surveillance system that collects facts from death certificates, coroner/medical examiner reports, law enforcement reports, and toxicology reports into one anonymous database.

NVDRS Restricted Access Database (RAD) - A de-identified, multi-state, case-level data set comprised of hundreds of unique variables. The database includes short narratives to describe the circumstances related to violent deaths, including descriptions from law enforcement and coroner or medical examiner investigative reports.

C.2 – PURPOSE

The purpose of this project is to enhance the NVDRS RAD application process for users to enter and submit proposals through automation and by way of an electronic tool or portal. The specific tasks to accomplish this goal are as follows:

1) Ensure proper documentation, training and knowledge transfer of NVDRS RAD application processes, tools and services

2) Develop a tracking and workflow process to monitor NVDRS RAD requests, including which phase of the review process they are in and when reviews are complete,

a. Both the requestor and CDC will be able to monitor to see which phase of the review process the request is in

b. Only CDC will have access to more detailed information, such as reviews that have been completed to date, and the actual content of the reviews

3) Develop a process to inform NVDRS RAD applicants when their application has been received and is being reviewed,

4) Develop a process to collect signed NVDRS RAD Data Sharing Agreements that will become part of the RAD repository. Any NVDRS RAD Data Sharing Agreements will be consistent with the CDC Office of Science (OS) guidelines.

5) Develop a process to send reminders to reviewers to complete their reviews,

6) Develop a process for organizing and tracking feedback from reviewers and the IT Security Specialist (please see attachment, The feedback will consist of information in the RAD review committee feedback report, which outlines how comments from reviewers regarding the application are organized into 3 categories: “Response Required, Action Required,” “Response Required, Action Optional,” and “Of Note-No Response or Action Required.”). The feedback will be available on a central location in the system, and accessible and visible to members of the RAD review committee. The system will also have the capability to see which members of the review committee have responded, and will send the RAD coordinator a message when all members have provided feedback on a specific proposal.

7) Develop a process to inform NVDRS RAD applicants when their application has been approved or requires further revisions,

8) Develop a secure data pickup hub,

9) Develop a process for NVDRS RAD users to revise or amend previously accepted applications, and monitor requests as mentioned in #3 above

10) Develop a process for receiving and storing information regarding reports, publications, or other products created as a result of the NVDRS RAD request.

Funding this work would allow CDC to better monitor the number and type of NVDRS RAD requests through an automated system and would create an enhanced user experience for both researchers, NVDRS Science Officers, and members of the NVDRS RAD review committee.

C.3 – SCOPE OF WORK

The vendor will provide all labor, materials, and equipment required to complete the tasks outlined below. The vendor may require travel or communication with CDC to obtain materials or information needed to complete NVDRS RAD automation.

C.4 – TASKS TO BE PERFORMED

Task 1: Architectural Documents and Source Code Files

The contractor shall:

1. Design, code, test and implement UI functionality to demonstrate NVDRS RAD Automation application interaction with CDC SAMS authentication.

2. Activities include sessions with CDC SAMS support team to resolve issues with staging end points.

3. Provide an analysis that fit the most current “Big Data tool stack”. This includes the production of a list of tools and services for the upcoming big data prototype.

4. Provide a basic set of metrics that can be produced from the data. For example: Microsoft Visio Workflow diagrams, Word Documents with embedded images, PowerPoint Presentation Slide decks, etc. Vendors will produce the documents as needed to gain approval for developing each component of the solution.

5. Provide data warehouse and physical data model in support of NVDRS track.

6. Implement and release NVDRS functionality. This includes data dictionary, validation rules, testing and updates.

7. Participate in and demonstrate NVDRS RAD automation processes to CDC government committee and leadership.

Task 2: TRANSITION PLAN

The Contractor shall provide a Transition Plan for the transition or phase-in of this contract as well as phase-out. The Transition Plan shall include a technical and management transition approach that is clear and complete including the timeline and resources required for the transition. The Transition Plan shall detail the planned transition methodology in logical sequence to ensure a smooth transition of all tasks/subtasks of the Statement of Work (SOW) without interruption or degradation of service levels. The Transition Plan shall include an approach that ensures the successful achievement while limiting impact to existing programs/projects. The Transition Plan shall also include a complete description of risks (cost, technical, and performance to both the Contractor and the Government), issues and risk mitigation strategies.

C.5 – GOVERNMENT FURNISHED MATERIALS

CDC will not provide information technology equipment and the computers used by contractor personnel shall meet CDC’s standard software and security configuration before logging into CDC’s network.

C.6 – PERIOD OF PERFORMANCE

The period of performance is;

Base Period:

09/01/20 - 08/31/21

Year 1 (Option Period 1):

09/01/21 - 08/31/22

Year 2 (Option Period 2):

09/01/22 - 08/31/23

C.7 – PLACE OF PERFORMANCE

Work will be performed primarily off-site at the contractor’s locations, will require access to CDC’s network.

C.8 – DELIVERABLES/REPORTING SCHEDULE

The vendor shall provide the following deliverables to the Project Officer by the dates reflected below. All electronic files should be delivered in MS Word and provided via email.

Contract Phases and Deliverables

Project Milestones, Timeline, and Outcomes

1) Create a Cloud-Based Computing Platform (Phase I)

Outcome: Create a Cloud-Based Computing Platform (CBCP) development environment based upon project requirements. This phase is dedicated to creating and establishing the base cloud architecture, and necessary environments to create an automated NVDRS RAD system.

a. Timeline: 4 months from the project start date

b. Milestones/Deliverables:

i. Start-up Meeting Agenda
In first week after contact award and prior to start-up meeting
ii. Startup Meeting
Within 10 business days of award
1. Startup Meeting Notes, Briefing Document outlining the Contractor’s strategy to begin the task
Within 3 business days of Start-up Meeting to the COR and CDC Project Lead
iii. Project meeting weekly or biweekly after startup meeting for the duration of project
Contractor to setup and provide summary in Microsoft Word file to the COR and CDC Project Lead
iv. Acquire development staffing team (IE. Sr. Business Analyst, Developer; Cloud architect)
One week from awarding of project
v. Conduct usability testing to meet the needs of its users.
Four weeks from awarding of project
vi. Monthly Progress Report (MPR) provided monthly for the duration of project to include Monthly Invoice Summary, Monthly Project Cost and Schedule Reporting or EVM (“Burn Rate Report”)
Monthly Contractor to provide to COR or NCIPC a progess summary in Microsoft Word file for duration of Project
vii. Alternative Analysis Report
One month from contract award to COR
viii. Determine the best technology that can be maintained in a cost-efficient manner.
Five weeks from awarding of project
ix. Define technical and functional requirements for system
Five weeks from awarding of project
x. Select the cloud provider & purchase CBCP development environment
Six weeks from awarding of project
xi. Design Interface Document
2 months from contract award
xii. Architectural Documents/Source Code Files
Quarterly from contract award and 30 days before contract end date to COR
xiii. Data Warehouse Model
3 months from contract award to COR
xiv. Create development, test, and production database environments
Ten weeks from awarding of project
xv. Import and populate cloud database with test or historical RAD cases
Three months from awarding of project
xvi. Create web-based RAD service to receive RAD requests and populate database
Four months from awarding of project

2) RAD-reporting services (Phase II)

Outcome: Create RAD-reporting services on CBCP to receive RAD data requests.

a. Timeline: 8 months from the project start date

b. Milestones/Deliverables:

i. Create RAD reporting service to receive RAD requests in CDC format and route to reporting Science Officer’s (SO’s) message queue
Five months from awarding of project
ii. Create a tracking and workflow system to monitor NVDRS RAD requests, including which phase of the review process they are in and when reviews are complete,
Five months from awarding of project

1. Both the requestor and CDC will be able to monitor to see which phase of the review process the RAD request

2. Only CDC users will have access to more detailed information, such as reviews that have been completed to date, and the actual content of the reviews

iii. Create a process to inform NVDRS RAD applicants when their RAD application has been received and is being reviewed
Six months from awarding of project
iv. Create a process to collect signed NVDRS RAD Data Sharing Agreements that will become part of the RAD repository.
Six months from awarding of project

1. Any NVDRS RAD Data Sharing Agreements will be consistent with the CDC Office of Science (OS) guidelines

v. Create a process to send reminders to reviewers to complete their reviews
Six months from awarding of project
vi. Create a process for organizing and tracking feedback from reviewers and the IT Security Specialist (please see attachment)
Six months from awarding of project

1. The feedback will consist of information in the RAD review committee feedback report, which outlines how comments from reviewers regarding the application are organized into 3 categories:

a. “Response Required, Action Required,”

b. “Response Required, Action Optional,”

c. “Of Note-No Response or Action Required.”).

2. The feedback will be available on a central location in the system, and accessible and visible to members of the CDC RAD review committee. The process will also have the capability to see which members of the review committee have responded, and will send the CDC RAD coordinator a message when all members have provided feedback on a specific proposal.

3. Create a process to inform NVDRS RAD applicants when their application has been approved or requires further revisions

vii. Create integrated data visualization tools embedded within system as confirmed by CDC.
Seven months from awarding of project
viii. Develop a process for RAD users to revise or amend previously accepted applications, and monitor requests as mentioned in #3 above
Seven months from awarding of project
ix. Create a process for receiving and storing information regarding reports, publications, or other products created as a result of the NVDRS RAD request.
Seven months from awarding of project
x. Create RAD request messages directly from the SO’s message queue
Seven months from awarding of project
xi. Pilot these reporting processes with CDC SO’s
Eight months from awarding of project

3) Integrate with current RAD Data (Phase III)

a. Outcome: Integrate current RAD history to new platform and operationalize

b. Timeline: 12 months from project start date

c. Milestones/Deliverables:

i. Create a secure data pickup hub for RAD files
Nine months from awarding of project
ii. Update RAD system to receive data metrics (number of requestors, how requestor heard about the RAD, etc.) from the RAD data requestors and populate databases on CBCP
Nine months from awarding of project
iii. Test end-to-end data flow from RAD requests to RAD data distribution
Ten months from awarding of project
iv. Pilot with CDC Science Officers
Eleven months from awarding of project

4) Transition Out

The contractor shall provide a Transition-Out Plan
NLT Ninety (90) Days

5) Future Directions: (Year Two)

a. Outcome: Future enhancements to the RAD automation release and maintenance od RAD release

b. Timeline: 12 – 24 months from project start date

c. Milestones/Deliverables:

i. Expand services to support Science Officers for additional reporting and follow-up (publications)
15 months from awarding of project
ii. Maintenance to fine tune system and minor software fixes from intial release
15 months from awarding of project
iii. Update the RAD system to facilitate linking, consolidation, and follow-back for these reports
18 months from awarding of project
iv. Maintenannce to fine tune system and minor software fixes from intial release
18 months from awarding of project
v. Maintenannce to fine tune system and minor software fixes from intial release
21 months from awarding of project
vi. Maintenannce to fine tune system and minor software fixes from intial release
15 months from awarding of project

6) Future Maintenance: (Year Three)

a. Outcome: Maintenance of RAD release

b. Timeline: 24 – 36 months from project start date

c. Milestones/Deliverables:

i. Maintenannce to fine tune system and minor software fixes from intial release
27 months from awarding of project
ii. Maintenannce to fine tune system and minor software fixes from intial release
30 months from awarding of project
iii. Maintenannce to fine tune system and minor software fixes from intial release
33 months from awarding of project
iv. Maintenannce to fine tune system and minor software fixes from intial release
36 months from awarding of project

Transition Out: The Transition-Out Plan shall facilitate the accomplishment of a seamless transition from the incumbent to an incoming contractor /government personnel at the expiration of the contract. The contractor shall provide a Transition-Out Plan NLT ninety (90) days prior to expiration of the contract. The contractor shall identify how it will coordinate with the incoming contractor and/or Government personnel to transfer knowledge regarding the following:

· Project management processes

· Points of contact

· Location of technical and project management documentation

· Status of ongoing technical initiatives

· Appropriate contractor to contractor coordination to ensure a seamless transition

· Transition of key personnel

· Identify schedules and milestones

· Identify actions required of the Government,

· Establish and maintain effective communication with the incoming contractor/ Government personnel for the period of the transition via weekly status meetings

C.9 – TRAVEL

Not applicable.

C.10 – SPECIAL REQUIREMENTS

Information Security Requirements:

A. Baseline Security Requirements

1) Applicability. The requirements herein apply whether the entire contract or order (hereafter “contract”), or portion thereof, includes either or both of the following:

a. Access (Physical or Logical) to Government Information: A Contractor (and/or any subcontractor) employee will have or will be given the ability to have, routine physical (entry) or logical (electronic) access to government information.

b. Operate a Federal System Containing Information: A Contractor (and/or any subcontractor) will operate a federal system and information technology containing data that supports the HHS mission. In addition to the Federal Acquisition Regulation (FAR) Subpart 2.1 definition of “information technology” (IT), the term as used in this section includes computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including support services), and related resources.

2) Safeguarding Information and Information Systems. In accordance with the Federal Information Processing Standards Publication (FIPS)199, Standards for Security Categorization of Federal Information and Information Systems, the Contractor (and/or any subcontractor) shall:

a. Protect government information and information systems in order to ensure:

· Confidentiality, which means preserving authorized restrictions on access and disclosure, based on the security terms found in this contract, including means for protecting personal privacy and proprietary information;

· Integrity, which means guarding against improper information modification or destruction, and ensuring information non-repudiation and authenticity; and

· Availability, which means ensuring timely and reliable access to and use of information.

b. Provide security for any Contractor systems, and information contained therein, connected to an HHS network or operated by the Contractor on behalf of HHS regardless of location. In addition, if new or unanticipated threats or hazards are discovered by either the agency or contractor, or if existing safeguards have ceased to function, the discoverer shall immediately, within one (1) hour, bring the situation to the attention of the other party.

c. Adopt and implement the policies, procedures, controls, and standards required by the HHS Information Security Program to ensure the confidentiality, integrity, and availability of government information and government information systems for which the Contractor is responsible under this contract or to which the Contractor may otherwise have access under this contract. Obtain the HHS Information Security Program security requirements, outlined in the HHS Information Security and Privacy Policy (IS2P), by contacting the CO/COR or emailing fisma@hhs.gov.

d. Comply with the Privacy Act requirements and tailor FAR clauses as needed.

e. Full compliance with all Federal, HHS and CDC IT Security, 508 and privacy policies

3) Information Security Categorization. In accordance with FIPS 199 and National Institute of Standards and Technology (NIST) Special Publication (SP) 800-60, Volume II: Appendices to Guide for Mapping Types of Information and Information Systems to Security Categories, Appendix C, and based on information provided by the ISSO, CISO, or other security representative, the risk level for each Security Objective and the Overall Risk Level, which is the highest watermark of the three factors (Confidentiality, Integrity, and Availability) of the information or information system are the following:

Confidentiality:

[ X ] Low [ ] Moderate [ ] High

Integrity:

[ ] Low [ X ] Moderate [ ] High

Availability:

[ X ] Low [ ] Moderate [ ] High

Overall Risk Level:

[ ] Low [ X ] Moderate [ ] High

Based on information provided by the ISSO, Privacy Office, system/data owner, or other security or privacy representative, it has been determined that this solicitation/contract involves:

[X ] No PII [ ] Yes PII

4) Personally Identifiable Information (PII). Per the Office of Management and Budget (OMB) Circular A-130, “PII is information that can be used to distinguish or trace an individual's identity, either alone or when combined with other information that is linked or linkable to a specific individual.” Examples of PII include, but are not limited to the following: social security number, date and place of birth, mother‘s maiden name, biometric records, etc.

PII Confidentiality Impact Level has been determined to be: [ X ] Low [ ] Moderate [ ] High

5) Controlled Unclassified Information (CUI). CUI is defined as “information that laws, regulations, or Government-wide policies require to have safeguarding or dissemination controls, excluding classified information.” The Contractor (and/or any subcontractor) must comply with Executive Order 13556, Controlled Unclassified Information, (implemented at 3 CFR, part 2002) when handling CUI. 32 C.F.R. 2002.4(aa) As implemented the term “handling” refers to “…any use of CUI, including but not limited to marking, safeguarding, transporting, disseminating, re-using, and disposing of the information.” 81 Fed. Reg. 63323. All sensitive information that has been identified as CUI by a regulation or statute, handled by this solicitation/contract, shall be:

a. marked appropriately;

b. disclosed to authorized personnel on a Need-To-Know basis;

c. protected in accordance with NIST SP 800-53, Security and Privacy Controls for Federal Information Systems and Organizations applicable baseline if handled by a Contractor system operated on behalf of the agency, or NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations if handled by internal Contractor system; and

d. returned to HHS control, destroyed when no longer needed, or held until otherwise directed. Destruction of information and/or data shall be accomplished in accordance with NIST SP 800-88, Guidelines for Media Sanitization.

6) Protection of Sensitive Information. For security purposes, information is or may be sensitive because it requires security to protect its confidentiality, integrity, and/or availability. The Contractor (and/or any subcontractor) shall protect all government information that is or may be sensitive in accordance with OMB Memorandum M-06-16, Protection of Sensitive Agency Information by securing it with a FIPS 140-2 validated solution.

7) Confidentiality and Nondisclosure of Information. Any information provided to the contractor (and/or any subcontractor) by HHS or collected by the contractor on behalf of HHS shall be used only for the purpose of carrying out the provisions of this contract and shall not be disclosed or made known in any manner to any persons except as may be necessary in the performance of the contract. The Contractor assumes responsibility for protection of the confidentiality of Government records and shall ensure that all work performed by its employees and subcontractors shall be under the supervision of the Contractor. Each Contractor employee or any of its subcontractors to whom any HHS records may be made available or disclosed shall be notified in writing by the Contractor that information disclosed to such employee or subcontractor can be used only for that purpose and to the extent authorized herein.

The confidentiality, integrity, and availability of such information shall be protected in accordance with HHS and CDC policies. Unauthorized disclosure of information will be subject to the HHS/CDC sanction policies and/or governed by the following laws and regulations:

a. 18 U.S.C. 641 (Criminal Code: Public Money, Property or Records);

b. 18 U.S.C. 1905 (Criminal Code: Disclosure of Confidential Information); and

c. 44 U.S.C. Chapter 35, Subchapter I (Paperwork Reduction Act).

8) Internet Protocol Version 6 (IPv6). All procurements using Internet Protocol shall comply with OMB Memorandum M-05-22, Transition Planning for Internet Protocol Version 6 (IPv6).

9) Government Websites. All new and existing public-facing government websites must be securely configured with Hypertext Transfer Protocol Secure (HTTPS) using the most recent version of Transport Layer Security (TLS). In addition, HTTPS shall enable HTTP Strict Transport Security (HSTS) to instruct compliant browsers to assume HTTPS at all times to reduce the number of insecure redirects and protect against attacks that attempt to downgrade connections to plain HTTP. For internal-facing websites, the HTTPS is not required, but it is highly recommended.

C.11 – REFERENCE MATERIALS

Here is a link to the NVDRS RAD website:

https://www.cdc.gov/violenceprevention/datasources/nvdrs/RAD.html Documents shared with the RAD researchers (Guidelines for RAD users, RAD review committee feedback report) can be shared when the contract is awarded.

C.12 – CONTRACTING OFFICER’S REPRESENTATIVE INFORMATION

The Contracting Officer’s Representative (COR) for this procurement is:

TBD

United States Department of Health and Human Services

Centers for Disease Control and Prevention

4770 Buford Hwy NE, Mail Stop F63 Atlanta, Georgia 30341 Telephone Number: TBD E-mail Address:

TBD

Preferred method of communication: E-mail HHSAR Provision, 352.239-73: Electronic and Information Technology Accessibility Notice

(a) Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998 and the Architectural and Transportation Barriers Compliance Board Electronic and Information (EIT) Accessibility Standards (36 CFR part 1194), require that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

(b) Accordingly, any offeror responding to this solicitation must comply with established HHS EIT accessibility standards. Information about Section 508 is available at http://www.hhs.gov/web/508. The complete text of the Section 508 Final Provisions can be accessed at http://www.access-board.gov/sec508/standards.htm.

(c) The Section 508 accessibility standards applicable to this contract are: 1194.

205 WCAG 2.0 Level A & AA Success Criteria

302 Functional Performance Criteria

502 Inoperability with Assistive Technology

503 Applications

504 Authoring Tools

602 Support Documentation

603 Support Services

In order to facilitate the Government's determination whether proposed EIT supplies meet applicable Section 508 accessibility standards, offerors must submit an HHS Section 508 Product Assessment Template, in accordance with its completion instructions. The purpose of the template is to assist HHS acquisition and program officials in determining whether proposed EIT supplies conform to applicable Section 508 accessibility standards. The template allows offerors or developers to self-evaluate their supplies and documentation detail - whether they conform to a specific Section 508 accessibility standard, and any underway remediation efforts addressing conformance issues. Instructions for preparing the HHS Section 508 Evaluation Template are available under Section 508 policy on the HHS Web site http://hhs.gov/web/508.

In order to facilitate the Government's determination whether proposed EIT services meet applicable Section 508 accessibility standards, offerors must provide enough information to assist the Government in determining that the EIT services conform to Section 508 accessibility standards, including any underway remediation efforts addressing conformance issues.

(d) Respondents to this solicitation must identify any exception to Section 508 requirements. If a offeror claims its supplies or services meet applicable Section 508 accessibility standards, and it is later determined by the Government, i.e., after award of a contract or order, that supplies or services delivered do not conform to the accessibility standards, remediation of the supplies or services to the level of conformance specified in the contract will be the responsibility of the Contractor at its expense.

(e) Electronic content must be accessible to HHS acceptance criteria. Checklist for various formats are available at http://508.hhs.gov/, or from the Section 508 Coordinator listed at https://www.hhs.gov/web/section-508/additional-resources/section-508-contacts/index.html. Materials that are final items for delivery should be accompanied by the appropriate checklist, except upon approval of the Contracting Officer or Representative.

Section D - Clauses

FAR 52.252-2 -- Clauses Incorporated by Reference. (Feb. 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/far1toc.htm http://www.hhs.gov/policies/hhsar/subpart301-1.html www.farsite.hill.af.mil (End of Clause)

FAR SOURCE
TITLE AND DATE
52.204-7
System for Award Management (Oct 2016)
52.204-13
Contractor Code of Business Ethics and Conduct (Oct 2016)
52.204-18
Commercial and Government Entity Code Maintenance (Jul 2016)
52.212-4
Contract Terms and Conditions-Commercial Items (Jan 2017)
52.232-40
Providing Accelerated Payments to Small Business Subcontractors (Dec 2013)
52.242-15
Stop-Work Order (Aug. 1989)
HHSAR
TITLE AND DATE
352.203-70
Anti-Lobbying (Dec 2015)
352.222-70
Contractor Cooperation in Equal Employment Opportunity Investigations (Dec 2015)

FAR 52.237-3 -- Continuity of Services (Jan 1991) (a)The Contractor recognizes that the services under this contract are vital to the Government and must be continued without interruption and that, upon contract expiration, a successor, either the Government or another contractor, may continue them. The Contractor agrees to-

(1)Furnish phase-in training; and

(2)Exercise its best efforts and cooperation to effect an orderly and efficient transition to a successor.

(b)The Contractor shall, upon the Contracting Officer’s written notice, (1) furnish phase-in, phase-out services for up to 90 days after this contract expires and (2) negotiate in good faith a plan with a successor to determine the nature and extent of phase-in, phase-out services required. The plan shall specify a training program and a date for transferring responsibilities for each division of work described in the plan, and shall be subject to the Contracting Officer’s approval. The Contractor shall provide sufficient experienced personnel during the phase-in, phase-out period to ensure that the services called for by this contract are maintained at the required level of proficiency.

(c)The Contractor shall allow as many personnel as practicable to remain on the job to help the successor maintain the continuity and consistency of the services required by this contract. The Contractor also shall disclose necessary personnel records and allow the successor to conduct on-site interviews with these employees. If selected employees are agreeable to the change, the Contractor shall release them at a mutually agreeable date and negotiate transfer of their earned fringe benefits to the successor.

(d)The Contractor shall be reimbursed for all reasonable phase-in, phase-out costs (i.e., costs incurred within the agreed period after contract expiration that result from phase-in, phase-out operations) and a fee (profit) not to exceed a pro rata portion of the fee (profit) under this contract.

(End of clause)

FAR 52.212-5Contract Terms and Conditions Required to Implement Statutes or Executive Orders-Commercial Items (Jul 2020)

(a) The Contractor shall comply with the following Federal Acquisition Regulation (FAR) clauses, which are incorporated in this contract by reference, to implement provisions of law or Executive orders applicable to acquisitions of commercial items:

(1) 52.203-19, Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements (Jan 2017) (section 743 of Division E, Title VII, of the Consolidated and Further Continuing Appropriations Act, 2015 (Pub. L. 113-235) and its successor provisions in subsequent appropriations acts (and as extended in continuing resolutions)).

(2) 52.204-23, Prohibition on Contracting for Hardware, Software, and Services Developed or Provided by Kaspersky Lab and Other Covered Entities (Jul 2018) (Section 1634 of Pub. L. 115-91).

(3) 52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment. (Aug 2019) (Section 889(a)(1)(A) of Pub. L. 115-232).

(4) 52.209-10, Prohibition on Contracting with Inverted Domestic Corporations (Nov 2015).

(5) 52.233-3, Protest After Award (Aug 1996) (31 U.S.C. 3553).

(6) 52.233-4, Applicable Law for Breach of Contract Claim (Oct 2004) (Public Laws 108-77 and 108-78 ( 19 U.S.C. 3805 note)).

(b) The Contractor shall comply with the FAR clauses in this paragraph (b) that the Contracting Officer has indicated as being incorporated in this contract by reference to implement provisions of law or Executive orders applicable to acquisitions of commercial items:

[Contracting Officer check as appropriate.]

__ (1) 52.203-6, Restrictions on Subcontractor Sales to the Government (June 2020), with Alternate I (Oct 1995) ( 41U.S.C.4704 and 10 U.S.C. 2402).

__ (2) 52.203-13, Contractor Code of Business Ethics and Conduct (Jun 2020) (41 U.S.C. 3509)).

__ (3) 52.203-15, Whistleblower Protections under the American Recovery and Reinvestment Act of 2009 (Jun 2010) (Section 1553 of Pub. L. 111-5). (Applies to contracts funded by the American Recovery and Reinvestment Act of 2009.)

_X_ (4) 52.204-10, Reporting Executive Compensation and First-Tier Subcontract Awards (Jun 2020) (Pub. L. 109-282) ( 31 U.S.C. 6101 note).

__ (5) [Reserved].

__ (6) 52.204-14, Service Contract Reporting Requirements (Oct 2016) (Pub. L. 111-117, section 743 of Div. C).

__ (7) 52.204-15, Service Contract Reporting Requirements for Indefinite-Delivery Contracts (Oct 2016) (Pub. L. 111-117, section 743 of Div. C).

_X_ (8) 52.209-6, Protecting the Government’s Interest When Subcontracting with Contractors Debarred, Suspended, or Proposed for Debarment. (Jun 2020) (31 U.S.C. 6101 note).

__ (9) 52.209-9, Updates of Publicly Available Information Regarding Responsibility Matters (Oct 2018) (41 U.S.C. 2313).

__ (10) [Reserved].

__ (11) (i) 52.219-3, Notice of HUBZone Set-Aside or Sole-Source Award (Mar 2020) (15 U.S.C. 657a).

__ (ii) Alternate I (Mar 2020) of 52.219-3.

__ (12) (i) 52.219-4, Notice of Price Evaluation Preference for HUBZone Small Business Concerns (Mar 2020) (if the offeror elects to waive the preference, it shall so indicate in its offer) (15 U.S.C. 657a).

__ (ii) Alternate I (Mar 2020) of 52.219-4.

__ (13) [Reserved]

_X_ (14) (i) 52.219-6, Notice of Total Small Business Set-Aside (Mar 2020) of 52.219-6 (15 U.S.C. 644).

__ (ii) Alternate I (Mar 2020) of 52.219-6 .

__ (15) (i) 52.219-7, Notice of Partial Small Business Set-Aside (Mar 2020) (15 U.S.C. 644).

__ (ii) Alternate I (Mar 2020) of 52.219-7.

__ (16) 52.219-8, Utilization of Small Business Concerns (Oct 2018) (15 U.S.C. 637(d)(2) and (3)).

__ (17) (i) 52.219-9, Small Business Subcontracting Plan (Jun 2020) (15 U.S.C. 637(d)(4)).

__ (ii) Alternate I (Nov 2016) of 52.219-9.

__ (iii) Alternate II (Nov 2016) of 52.219-9.

__ (iv)Alternate III (Jun 2020) of 52.219-9.

__ (v)Alternate IV (Jun 2020) of 52.219-9 __ (18) (i) 52.219-13, Notice of Set-Aside of Orders (Mar 2020) (15 U.S.C. 644(r)).

(ii) Alternate I (Mar 2020) of 52.219-13.

_X_ (19) 52.219-14, Limitations on Subcontracting (Mar 2020) (15 U.S.C. 637(a)(14)).

__ (20) 52.219-16, Liquidated Damages-Subcontracting Plan (Jan 1999) (15 U.S.C. 637(d)(4)(F)(i)).

__ (21) 52.219-27, Notice of Service-Disabled Veteran-Owned Small Business Set-Aside (Mar 2020) (15 U.S.C. 657f).

_X_ (22) (i) 52.219-28, Post Award Small Business Program Rerepresentation (May 2020) (15 U.S.C. 632(a)(2)).

(ii) Alternate I (MAR 2020) of 52.219-28.

__ (23) 52.219-29, Notice of Set-Aside for, or Sole Source Award to, Economically Disadvantaged Women-Owned Small Business Concerns (Mar 2020) (15 U.S.C. 637(m)).

__ (24) 52.219-30, Notice of Set-Aside for, or Sole Source Award to, Women-Owned Small Business Concerns Eligible Under the Women-Owned Small Business Program (Mar2020) (15 U.S.C. 637(m)).

__ (25) 52.219-32, Orders Issued Directly Under Small Business Reserves (Mar 2020) (15 U.S.C. 644(r)).

__ (26) 52.219-33, Nonmanufacturer Rule (Mar 2020) (15U.S.C. 637(a)(17)).

_X_ (27) 52.222-3, Convict Labor (Jun 2003) (E.O.11755).

__ (28) 52.222-19, Child Labor-Cooperation with Authorities and Remedies (Jan2020) (E.O.13126).

_X_ (29) 52.222-21, Prohibition of Segregated Facilities (Apr 2015).

_X_ (30) (i) 52.222-26, Equal Opportunity (Sep 2016) (E.O.11246).

__ (ii) Alternate I (Feb 1999) of 52.222-26.

_X_ (31) (i) 52.222-35, Equal Opportunity for Veterans (Jun 2020) (38 U.S.C. 4212).

__ (ii) Alternate I (Jul 2014) of 52.222-35.

_X_ (32) (i) 52.222-36, Equal Opportunity for Workers with Disabilities (Jun 2020) (29 U.S.C. 793).

__ (ii) Alternate I (Jul 2014) of 52.222-36.

_X_ (33) 52.222-37, Employment Reports on Veterans (Jun 2020) (38 U.S.C. 4212).

__ (34) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (Dec 2010) (E.O. 13496).

_X_ (35) (i) 52.222-50, Combating Trafficking in Persons (Jan 2019) (22 U.S.C. chapter 78 and E.O. 13627).

__ (ii) Alternate I (Mar 2015) of 52.222-50 (22 U.S.C. chapter 78 and E.O. 13627).

__ (36) 52.222-54, Employment Eligibility Verification (Oct 2015). (Executive Order 12989). (Not applicable to the acquisition of commercially available off-the-shelf items or certain other types of commercial items as prescribed in 22.1803.)

__ (37) (i) 52.223-9, Estimate of Percentage of Recovered Material Content for EPA–Designated Items (May 2008) ( 42 U.S.C. 6962(c)(3)(A)(ii)). (Not applicable to the acquisition of commercially available off-the-shelf items.)

__ (ii) Alternate I (May 2008) of 52.223-9 (42 U.S.C. 6962(i)(2)(C)). (Not applicable to the acquisition of commercially available off-the-shelf items.)

__ (38) 52.223-11, Ozone-Depleting Substances and High Global Warming Potential Hydrofluorocarbons (Jun 2016) (E.O. 13693).

__ (39) 52.223-12, Maintenance, Service, Repair, or Disposal of Refrigeration Equipment and Air Conditioners (Jun 2016) (E.O. 13693).

__ (40) (i) 52.223-13, Acquisition of EPEAT®-Registered Imaging Equipment (Jun 2014) (E.O.s 13423 and 13514).

__ (ii) Alternate I (Oct 2015) of 52.223-13.

__ (41) (i) 52.223-14, Acquisition of EPEAT®-Registered Televisions (Jun 2014) (E.O.s 13423 and 13514).

__ (ii) Alternate I (Jun2014) of 52.223-14.

__ (42) 52.223-15, Energy Efficiency in Energy-Consuming Products (May 2020) (42 U.S.C. 8259b).

__ (43) (i) 52.223-16, Acquisition of EPEAT®-Registered Personal Computer Products (Oct 2015) (E.O.s 13423 and 13514).

__ (ii) Alternate I (Jun 2014) of 52.223-16.

_X_ (44) 52.223-18, Encouraging Contractor Policies to Ban Text Messaging While Driving (Jun 2020) (E.O. 13513).

__ (45) 52.223-20, Aerosols (Jun 2016) (E.O. 13693).

__ (46) 52.223-21, Foams (Jun2016) (E.O. 13693).

__ (47) (i) 52.224-3 Privacy Training (Jan 2017) (5 U.S.C. 552 a).

__ (ii) Alternate I (Jan 2017) of 52.224-3.

__ (48) 52.225-1, Buy American-Supplies (May 2014) (41 U.S.C. chapter 83).

__ (49) (i) 52.225-3, Buy American-Free Trade Agreements-Israeli Trade Act (May 2014) (41 U.S.C.chapter83, 19 U.S.C. 3301 note, 19 U.S.C. 2112 note, 19 U.S.C. 3805 note, 19 U.S.C. 4001 note, Pub. L. 103-182, 108-77, 108-78, 108-286, 108-302, 109-53, 109-169, 109-283, 110-138, 112-41, 112-42, and 112-43.

__ (ii) Alternate I (May 2014) of 52.225-3.

__ (iii) Alternate II (May 2014) of 52.225-3.

__ (iv) Alternate III (May 2014) of 52.225-3.

__ (50) 52.225-5, Trade Agreements (Oct 2019) (19 U.S.C. 2501, et seq., 19 U.S.C. 3301 note).

_X_ (51) 52.225-13, Restrictions on Certain Foreign Purchases (Jun 2008) (E.O.’s, proclamations, and statutes…

This is the start of the file's text. The full file is on GovTribe.

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