Combined Synopsis Solicitation_75D30124Q78333.pdf

COMBINED SYNOPSIS / SOLICITATION FOR

COMMERCIAL PRODUCTS AND SERVICES

This is a combined synopsis/solicitation for commercial products prepared in accordance with the format in Federal

Acquisition Regulation (FAR) 12.6 as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; quotations are being requested, and a written solicitation will not be issued.

The solicitation number for this requirement is 75D30124Q78333 and is hereby issued as a Request for Quote

(RFQ).

The Centers for Disease Control and Prevention intends to award a firm-fixed-price purchase order for the following requirement. Please either fill in the dollar amounts in the table below or provide a separate excel spreadsheet containing the same information, including a list of line item number(s) and items, quantities, units of measure, and options, if applicable.

Supplies/Services and Prices/Costs:

ITEM SUPPLIES / SERVICES QTY / UNIT UNIT

PRICE

EXTENDED PRICE

0001 Title: Equipment Maintencance

Includes:

NextSeq Silver Supp Plan

MiSeq Silver Supp Plan

NextSeq Health Check

MiSeq Health Check

Period of Performance: 09/09/2024 –

09/08/2025

Custodial Account 91905

This is a Firm Fixed Price, Severable

Line Item

1 Each https://www.acquisition.gov/far/part-12#FAR_Subpart_12_6

1001 Title: Equipment Maintenance

MiSeq Silver Supp Plan

Period of Performance: 09/09/2025 –

09/08/2026

2001 Title: Equipment Maintenance

Period of Performance: 09/09/2026 –

09/08/2027

3001 Title: Equipment Maintenance

Period of Performance: 09/09/2027 –

09/08/2028

4001 Title: Equipment Maintenance

Period of Performance: 09/09/2028 –

09/08/2029

Custodial Account

It is the Offeror's responsibility to be familiar with the applicable clauses and provisions. Clauses and provisions may be accessed via the Internet at website: https://www.acquisition.gov/browse/index/far.

This solicitation document and incorporated provisions and clauses are those in effect through the Federal

Acquisition Circular (FAC) 2024-05 (April 22, 2024).

This acquisition is under North American Industry Classification System (NAICS) code 811219 – Other Electronic and Precision Equipment Repair and Maintenance. A firm-fixed-price purchase order will be issued in writing to the successful offeror. To be eligible to receive an award resulting from this solicitation, the contractor must be registered in the System for Award Management (SAM).

Offerors must include FAR 52.212-3, Offeror Representations and Certifications – Commercial Products and

Commercial Services, with its offer or indicate if it is available online at SAM.gov.

Questions Due: All questions regarding this combined synopsis/solicitation must be submitted via e-mail to Kristen

M. Tucker at xvc1@cdc.gov by 5:00 p.m. EDT on Friday, August 30, 2024. Questions will not be taken by telephone.

Responses Due: All responses to this combined synopsis/solicitation must be submitted via e-mail to Kristen M.

Tucker at xvc1@cdc.gov by 12:00 p.m. EDT on Wednesday, September 4, 2024.

https://www.acquisition.gov/browse/index/far mailto:xvc1@cdc.gov mailto:xvc1@cdc.gov

Statement of Work

Title: Annual Maintenance Services on Illumina Instruments

Period of performance of this contract is: 09/09/2024 to 09/08/2029

Base Period: 09/09/2024 to 09/08/2025

Option Period One: 09/09/2025 to 09/08/2026

Option Period Two: 09/09/2026 to 09/08/2027

Option Period Three: 09/09/2027 to 09/08/2028

Option Period Four: 09/09/2028 to 09/08/2029

SECTION 1 – BACKGROUND

The nation and world look to CDC's unique ability to rapidly detect, investigate, prevent, and control parasitic infectious health threats. Few agencies in the world have the capability for detection, surveillance, and detailed scientific evaluation of serious parasitic infections or deaths, including discovery of new emerging parasite pathogens as the causative agents.

The laboratories in the Laboratory Science and Diagnostics Branch (LSDB) within the Division of Parasitic

Diseases and Malaria (DPDM) at CDC play a critical role in the detection and identification of parasitic diseases in the United States as well as globally. Parasitic diseases continue to be an important domestic problem, increasingly associated with travel and immigration, immunodeficiency, and emerging and reemerging infectious agents. LSDB/DPDM is responsible for conducting diagnosis, surveillance, investigations, and studies of parasitic diseases to define disease etiology, mode of transmission, and populations at risk. LSDB’s Reference

Diagnostics Laboratory develops effective methods for diagnosis, prevention, control, and elimination of several parasitic diseases. The branch also provides laboratory support to epidemiologists and to state and local public health laboratories, other federal agencies, and national and international health organizations. Providing this support is essential in meeting the mission.

LSDB uses Illumina instruments as part of these mission critical activities. Data generated by these instruments are provided to epidemiologists and to state and local public health laboratories, other federal agencies, and national and international health organizations to identify domestic outbreaks related to foodborne parasitic diseases, domestic cases of malaria transmission, and help partners understand the therapeutic efficacy of antimalarial drugs in Africa.

SECTION 2 – PURPOSE/OBJECTIVE

The purpose of this procurement is to obtain a 5-year service contract for DPDM’s NextSeq1000 (VL00373) and

MiSeq (M05039) instruments.

SECTION 3 – SCOPE OF WORK

This contract shall include full coverage of parts (using only manufacturer approved parts), labor, and travel; reagent replacement upon hardware related run failures, remote technical support; 2 business day on-site response for all repairs, control software and hardware updates, on-site applications support, discounts on advanced training, and remote monitoring of run metrics (if available).

SECTION 4 – TASKS TO BE PERFORMED

Task 1: Health Check, Preventive Maintenance, and Repair of NextSeq1000

1. Base Year: Instrument health check and preventive maintenance for NextSeq1000 performed within 2 weeks of award.

a. Health Check

b. Preventive Maintenance

c. Repair, if needed: respond with priority to any problems that arise with the instrument, send a field service engineer to include travel, labor, and consumable/parts to fix or repair the instrument and to make sure it is in proper working order, field calls and troubleshoot technical issues with runs including problems with clustering, or low data yield, that negatively affect sequencing performance.

2. Option Years 1-4: Instrument preventive maintenance for NextSeq1000 performed annually for the duration of the contract.

a. Preventive Maintenance

3. Entire Period of Performance: Instrument repair for NextSeq1000 as needed for duration of contract.

Must respond with priority to any problems that arise with the instrument, send a field service engineer to include travel, labor, and consumable/parts to fix or repair the instrument and to make sure it is in proper working order, field calls and troubleshoot technical issues with runs including problems with clustering, or low data yield, that negatively affect sequencing performance.

Task 2: Health Check, Preventive Maintenance, and Repair of MiSeq

1. Base Year: Instrument health check and preventive maintenance for MiSeq performed within 2 weeks of award.

a. Health Check

b. Preventive Maintenance

c. Repair, if needed: respond with priority to any problems that arise with the instrument, send a field service engineer to include travel, labor, and consumable/parts to fix or repair the instrument and to make sure it is in proper working order, field calls and troubleshoot technical issues with runs including problems with clustering, or low data yield, that negatively affect sequencing performance.

2. Option Years 1-4: Instrument preventive maintenance for MiSeq performed annually for the duration of the contract.

a. Preventive Maintenance

3. Entire Period of Performance: Instrument repair for NextSeq1000 as needed for duration of contract.

Must respond with priority to any problems that arise with the instrument, send a field service engineer to include travel, labor, and consumable/parts to fix or repair the instrument and to make sure it is in proper working order, field calls and troubleshoot technical issues with runs including problems with clustering, or low data yield, that negatively affect sequencing performance.

SECTION 5 – GOVERNMENT FURNISHED PROPERTY

No Government Furnished Materials

SECTION 6 – PLACE OF PERFORMANCE AND CONTRACT SUPPORT HOURS

SUBSECTION A – PLACE OF PERFORMANCE

1600 Clifton Rd

Roybal Campus

Bldg 23 Labs 1M-603C & 10-662

Atlanta Ga 30329

SECTION 7 – TRAVEL

In person visits to the laboratory are required to repair/maintain the instruments as needed throughout the duration of this contract. No additional funds are available for travel which shall be at the Contractor’s expense.

SECTION 8 – DELIVERABLES/REPORTING SCHEDULE

Task Deliverable Quantity Due Date Deliver To

Instrument health check & preventative maintenance for

NextSeq1000

Instrument health check & preventative maintenance

1x Within 2 weeks of award

Please send the health check & preventive maintenance documentation to:

Carol Bolden, ihw8@cdc.gov

Instrument repair for

NextSeq1000

Instrument repaired

As needed On-site within two business days of when issues arise:

documentation of visit (issue and resolution) within 2 business days of visit.

Please send the repair documentation to:

Carol Bolden, ihw8@cdc.gov

Instrument preventative maintenance for

NextSeq1000

Instrument preventative maintenance

1x per year On-site preventative maintenance

Please send the preventive maintenance documentation to:

Carol Bolden, ihw8@cdc.gov

Instrument health check & preventative maintenance for

MiSeq

Instrument health check & preventative maintenance

1x Within 2 weeks of award

Please send the health check & preventive maintenance documentation to:

Carol Bolden, ihw8@cdc.gov

Task Deliverable Quantity Due Date Deliver To

Instrument health check & preventative maintenance for

NextSeq1000

Instrument health check & preventative maintenance

1x Within 2 weeks of award

Please send the health check & preventive maintenance documentation to:

Carol Bolden, ihw8@cdc.gov

Instrument repair for MiSeq

Instrument repaired

As needed On-site within two business days of when issues arise:

documentation of visit (issue and resolution) within 2 business days of visit.

Please send the repair documentation to:

Carol Bolden, ihw8@cdc.gov

Instrument preventative maintenance for

MiSeq

Instrument preventative maintenance

1x per year On-site preventative maintenance

Please send the preventive maintenance documentation to:

Carol Bolden, ihw8@cdc.gov

SECTION 9 – REFERENCE MATERIALS

No Government Furnished Reference Materials

SECTION 10 – MINIMUM VENDOR QUALIFICATIONS

1. Vendor must be well versed in all applications of software, including error codes, etc for both MiSeq and

NextSeq1000.

2. Vendor must be well versed with all components of hardware for both MiSeq and NextSeq1000.

3. Vendor must be able to use only genuine Illumina parts and reagents during health check, preventive maintenance, or repairs.

4. Vendor must offer full coverage for parts, labor, and travel.

5. Vendor must offer remote technical support in addition to on-site visits.

6. Vendor must offer a 2-business day on-site response.

7. Vendor must offer discounts on any advanced training.

SECTION 11 – ADDITIONAL REQUIREMENTS

Information Security and Privacy

Security Compliance

➢ If the contract is the vendor to provide the products as hardware and/or software to CDC, the vendor shall comply with the applicable IT security references Standards 1, 2, 5 and 6.

Standard-1: Procurements Requiring Information Security and/or Physical Access Security

1. Baseline Security Requirements

a. Applicability. The requirements herein apply whether the entire contract or modification (hereafter

"contract"), or portion thereof, includes either or all of the followings. No contractor will be permitted to access or operate CDC infrastructure or systems overseas unless prior approval is received from

CDC CISO.

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

(electronic) access to government information.

ii. 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 CDC 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.

b. Safeguarding Information and Information Systems. All government information and information systems must be protected in accordance with HHS/CDC policies and level of risk. At a minimum, the

Contractor (and/or any subcontractor) must:

i. Protect the:

▪ 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.

ii. Categorize all information owned and/or collected/managed on behalf of CDC and information systems that store, process, and/or transmit HHS information 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. Based on information provided by the ISSO, CISO, CDC CPO, or other representative, the impact level for each Security Objective (Confidentiality, Integrity, and

Availability) and the Overall Impact Level, which is the highest watermark of the three factors of the information or information system are the following:

▪ Confidentiality: [ x ] Low [ ] Moderate [ ] High

▪ Integrity: [ x ] Low [ ] Moderate [ ] High

▪ Availability: [ x ] Low [ ] Moderate [ ] High

▪ Overall Impact Level: [ x ] Low [ ] Moderate [ ] High

iii. Based on the agreed-upon level of impact, implement the necessary safeguards to protect all information systems and information collected and/or managed on behalf of CDC regardless of location or purpose.

iv. Report any discovered or unanticipated threats or hazards by either the agency or contractor, or if existing safeguards have ceased to function immediately after discovery, within one (1) hour or less, to the government representative(s).

http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol2-Rev1.pdf http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol2-Rev1.pdf http://csrc.nist.gov/publications/nistpubs/800-60-rev1/SP800-60_Vol2-Rev1.pdf

v. Adopt and implement all applicable policies, procedures, controls, and standards required by the

CDC 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 all applicable security and privacy policies by contacting the CO/COR or CDC security and/or privacy officials.

c. Privacy Act. Comply with the Privacy Act requirements (when applicable), and tailor FAR and

HHSAR clauses as needed.

d. Privacy Compliance. Comply with the E-Government Act of 2002, NIST SP 800-53, and applicable

CDC privacy policies, and complete all the requirements below:

i. Per the Office of Management and Budget (OMB) Circular A-130, Personally Identifiable

Information (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.

ii. To ensure that the public's personal information is protected in a manner commensurate with the privacy risks, CDC uses a privacy analysis process to assess the risks associated with CDC's collection and maintenance of PII and to ensure information is handled in accordance with applicable legal, regulatory, and policy requirements. PTAs analyze how information is handled in IT systems and electronic information collections and determines if the IT system or electronic information collection collects, disseminates, maintains, or disposes of PII. PIAs are used to assess the privacy risks of IT systems and electronic information collections that collect, disseminate, maintain, or dispose of PII about members of the public. PIAs also provide transparency into how CDC collects, disseminates, maintains, or disposes of the public's PII.

iii. The Contractor must support the agency with conducting a Privacy Threshold Analysis (PTA) for the information system and/or information handled under this contract to determine whether or not PII is collected, disseminated, maintained, or disposed as part of the contract. The PTA will determine if a full Privacy Impact Assessment (PIA) needs to be completed.

▪ If the results of the PTA show that a full PIA is needed, the Contractor must support the agency with completing a PIA for the system or information within 60 days after completion of the PTA and in accordance with CDC policy and OMB M-03-22, Guidance for Implementing the Privacy Provisions of the E-Government Act of 2002.

▪ The Contractor must support the agency in reviewing the PIA at least every three years throughout the system development lifecycle (SDLC)/information lifecycle, or when determined by the agency that a review is required based on a major change to the system, or when new types of PII are collected that introduces new or increased privacy risks, whichever comes first.

e. Controlled Unclassified Information (CUI). Executive Order 13556 defines CUI 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. The requirements below apply only to nonfederal systems that process, store, or transmit CUI, or that provide security protection for such components.

All sensitive information that has been identified as CUI by a regulation or statute, handled by this solicitation/contract, must be:

i. Marked appropriately;

ii. Disclosed to authorized personnel on a Need-To-Know basis;

iii. Protected in accordance with NIST SP 800-53, Security and Privacy Controls for 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

iv. Returned to HHS/CDC control, destroyed when no longer needed, or held until otherwise directed. Information and/or data must be disposed of in accordance with NIST SP 800-88, Guidelines for Media Sanitization.

f. 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) must protect all government information that is or may be sensitive by securing it with a solution that is validated with current FIPS 140 validation certificate from the NIST

CMVP.

g. Confidentiality and Nondisclosure of Information. Any information provided to the contractor

(and/or any subcontractor) by CDC or collected by the contractor on behalf of CDC must be used only for the purpose of carrying out the provisions of this contract and must 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 must ensure that all work performed by its employees and subcontractors must be under the supervision of the Contractor. Each Contractor employee or any of its subcontractors to whom any

CDC records may be made available or disclosed must 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 must be protected in accordance with HHS/CDC policies. Unauthorized disclosure of information will be subject to the HHS/CDC sanction policies and/or governed by the following laws and regulations:

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

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

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

h. Internet Protocol Version 6 (IPv6). All procurements using Internet Protocol must comply with

OMB Memorandum M-05-22, Transition Planning for Internet Protocol Version 6 (IPv6).

i. Information and Communications Technology (ICT). ICT products and services from prohibited entities/sources must not be used/acquired in compliance with Public Law 115-232, Section 889 Parts

A and B, FAR 4.21, FAR 52.204.23, FAR 52.204.24, and FAR 52.204.25. The contractor (and/or any subcontractor) must notify the government if they identify prohibited ICT products and/or services are used during the contract performance.

j. 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 must enable HTTP Strict Transport Security

(HSTS) to instruct compliant browsers to always assume HTTPS to reduce the number of insecure redirects and protect against attacks that attempt to downgrade connections to plain HTTP. For internal-facing websites, HTTPS is not required, but it is highly recommended. Consult HHS/CDC

Policy for Internet and Email Security for additional information.

k. Contract Documentation. The Contractor must use provided templates, policies, forms, and other agency documents specify which documents/forms will be provided to contractor] to comply with contract deliverables as appropriate.

l. Standard for Encryption. The Contractor (and/or any subcontractor) must:

i. Comply with the HHS Standard for Encryption of Computing Devices and Information to prevent unauthorized access to government information.

ii. Encrypt all sensitive federal data and information (i.e., PII, protected health information [PHI], proprietary information, etc.) in transit (i.e., email, network connections, etc.) and at rest (i.e., servers, storage devices, mobile devices, backup media, etc.) with encryption solution that is validated with current FIPS 140 validation certificate from the NIST CMVP.

iii. Secure all devices (i.e.: desktops, laptops, mobile devices, etc.) that store and process government information and ensure devices meet and CDC Component-specific encryption standard requirements. Maintain a complete and current inventory of all laptop computers, desktop computers, and other mobile devices and portable media that store or process sensitive government information (including PII).

iv. Verify that the encryption solutions in use have been validated under the Cryptographic Module

Validation Program to confirm compliance with current FIPS 140 validation certificate from the

NIST CMVP. The Contractor must provide a written copy of the validation documentation to the COR.

v. Use the Key Management system on the CDC personal identification verification (PIV) card or establish and use a key recovery mechanism to ensure the ability for authorized personnel to encrypt/decrypt information and recover encryption keys http://csrc.nist.gov/publications/.

Encryption keys must be provided to CSPO.

m. Contractor Non-Disclosure Agreement (NDA). Each Contractor (and/or any subcontractor) employee having access to non-public government information under this contract must complete the

CDC non-disclosure agreement, as applicable. Contractors (and/or subcontractors) must submit a copy of each signed and witnessed NDA to the Contracting Officer (CO) and/or CO Representative (COR) prior to performing any work under this acquisition.

2. Training Requirements

a. Mandatory Training for All Contractor Staff. All Contractor (and/or any subcontractor) employees assigned to work on this contract must complete the applicable CDC Contractor Information Security

Awareness, Privacy, and Records Management training (provided upon contract award) before performing any work under this contract. Thereafter, the employees must complete CDC Security

Awareness, Privacy, and Records Management training at least annually, during the life of this contract. All provided training must be compliant with CDC training policies.

b. Role-based Training. All Contractor (and/or any subcontractor) employees with significant security responsibilities (as determined by the program manager) must complete role-based training annually http://csrc.nist.gov/publications/ commensurate with their role and responsibilities in accordance with HHS/CDC policy and the CDC

Role-Based Training (RBT) of Personnel with Significant Security Responsibilities.

c. Training Records. The Contractor (and/or any subcontractor) must maintain training records for all its employees working under this contract in accordance with CDC policy. A copy of the training records must be provided to the CO and/or COR within 30 days after contract award and annually thereafter or upon request.

3. Rules of Behavior

a. The Contractor (and/or any subcontractor) must ensure that all employees performing on the contract comply with CDC Implementation of the HHS Rules of Behavior for Use of HHS Information

Technology Resources.

b. All Contractor employees performing on the contract must read and adhere to the Rules of Behavior before accessing agency data or other information, systems, and/or networks that store/process government information, initially at the beginning of the contract and at least annually thereafter, which may be done as part of annual CDC Information Security Awareness Training. If the training is provided by the contractor, the signed ROB must be provided as a separate deliverable to the CO and/or COR per defined timelines above.

4. Incident Response

a. The Contractor (and/or any subcontractor) must respond to all alerts/Indicators of Compromise (IOCs) provided by CDC Computer Security Incident Response Center (CSIRC) IRT teams within 24 hours, whether the response is positive or negative. In accordance with FISMA and OMB M-17-12, Preparing for and Responding to a Breach of Personally Identifiable Information (PII)1, an incident is

"an occurrence that (1) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (2) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies" and a privacy breach is "the loss of control, compromise, unauthorized disclosure, unauthorized acquisition, or any similar occurrence where (1) a person other than an authorized user accesses or potentially accesses personally identifiable information or (2) an authorized user accesses or potentially accesses personally identifiable information for an other than authorized purpose." For additional information on the CDC breach response process, please see the CDC Standard for

Responding to Breaches of Personally Identifiable Information (PII).2"

b. Contracts with entities that collect, maintain, use, or operate Federal information or information systems on behalf of CDC must include in the following requirements:

i. The contractor shall cooperate with and exchange information with CDC officials, as deemed necessary by the CDC Breach Response Team, to report and manage of a suspected or confirmed breach.

ii. All contractors and subcontractors shall properly encrypt PII in accordance with OMB Circular A-

130 and other applicable policies, including CDC-specific policies, and comply with HHS-specific policies for protecting PII. To this end, all contractors and subcontractors shall protect all sensitive information, including any PII created, stored, or transmitted in the performance of this contract, 1 Memorandum is available at: https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2017/m-17-12_0.pdf 2 Standard is available at: https://cdc.sharepoint.com/teams/OCIO-CSPO- PUBDOCS/Standards/CSPO%20Responding%20to%20Breaches%20of%20Personally%20Identifiable%20I nformation.pdf with encryption solution that is validated with the current FIPS 140 validation certificate from the

NIST CMVP.

iii. All contractors and subcontractors shall participate in regular training on how to identify and report a breach

iv. NOT notify affected individuals unless so instructed by the Contracting Officer or designated representative. If instructed by the Contracting Officer or representative, the Contractor must send

[CDC Component] approved notifications to affected individuals [insert CDC Component

Specific timeline, process, and format].

v. Report all suspected and confirmed information security and privacy incidents and breaches to the

CSPO Incident Response Team (IRT) [CDC Component inserted contact information should be cited here], COR, CO, CDC CPO (or his or her designee), and other stakeholders, including breaches involving PII, in any medium or form, including paper, oral, or electronic, as soon as possible and without unreasonable delay, no later than one (1) hour, and consistent with the applicable CDC Component and CDC policy and procedures, NIST standards and guidelines, as well as US-CERT notification guidelines. The types of information required in an incident report must include at a minimum: company and point of contact information, impact classifications/threat vector, and the type of information compromised. In addition, the Contractor must:

▪ Cooperate and exchange any information, as determined by the Agency, necessary to effectively manage or mitigate a suspected or confirmed breach;

▪ Not include any sensitive information in the subject or body of any reporting e-mail; and

▪ Encrypt sensitive information in attachments to email, media, etc.

vi. Comply with OMB M-17-12, Preparing for and Responding to a Breach of Personally

Identifiable Information, and CDC Component and CSPO privacy breach response policies when handling PII breaches.

vii. Provide full access and cooperate on all activities as determined by the Government to ensure an effective incident response, including providing all requested images, log files, and event information to facilitate rapid resolution of sensitive information incidents. This may involve disconnecting the system processing, storing, or transmitting the sensitive information from the

Internet or other networks or applying additional security controls. This may also involve physical access to contractor facilities during a breach/incident investigation [CDC Component insert timeline if required].

viii. All contractors and subcontractors shall be able to determine what Federal information was or could have been accessed and by whom, construct a timeline of user activity, determine methods and techniques used to access Federal information, and identify the initial attack vector.

ix. Cloud service providers shall use guidance provided in the FedRAMP Incident Communications

Procedures when deciding when to report directly to US-CERT first or notify CDC first.

x. Acknowledge that CDC will not interpret report of a breach, by itself, as conclusive evidence that the contractor or its subcontractor failed to provide adequate safeguards for PII.

5. Position Sensitivity Designations

All Contractor (and/or any subcontractor) employees must obtain a background investigation commensurate with their position sensitivity designation that complies with Parts 1400 and 731 of Title 5, Code of Federal Regulations (CFR). The following position sensitivity designation levels apply to this solicitation/contract:

6. Homeland Security Presidential Directive (HSPD)-12

The Contractor (and/or any subcontractor) and its employees must comply with Homeland Security

Presidential Directive (HSPD)-12, Policy for a Common Identification Standard for Federal Employees and Contractors; OMB M-05-24; OMB M-19-17; FIPS 201, Personal Identity Verification (PIV) of

Federal Employees and Contractors; CDC HSPD-12 policy; and Executive Order 13467, Part 1 §1.2.

7. Roster

The Contractor (and/or any subcontractor) must submit a roster by name, position, e-mail address, phone number and responsibility, of all staff working under this acquisition where the Contractor will develop, have the ability to access, or host and/or maintain a government information system(s). The roster must be submitted to the COR and/or CO 30 days prior to the effective date of this contract. Any revisions to the roster as a result of staffing changes must be submitted immediately upon the 30 days change. The COR will notify the Contractor of the appropriate level of investigation required for each staff member.

If the employee is filling a new position, the Contractor must provide a position description and the

Government will determine the appropriate suitability level.

8. Contract Initiation and Expiration

a. General Security Requirements. The Contractor (and/or any subcontractor) must comply with information security and privacy requirements, Enterprise Performance Life Cycle (EPLC) processes, CDC Enterprise Architecture requirements to ensure information is appropriately protected from initiation to expiration of the contract. All information systems development or enhancement tasks supported by the contractor must follow the CDC EPLC framework and methodology and in accordance with the CDC Office of Financial Resources (OFR) Contract Closeout Guide and HHS

Closeout Guide: Contracts and Orders.

b. System Documentation. Contractors (and/or any subcontractors) must follow and adhere to CDC

System Development Life Cycle requirements, at a minimum, for system development and provide system documentation at designated intervals (specifically, at the expiration of the contract) within the

EPLC that require artifact review and approval.

c. Sanitization of Government Files and Information. As part of contract closeout and at expiration of the contract, the Contractor (and/or any subcontractor) must provide all required documentation to the

CO and/or COR to certify that, at the government's direction, all electronic and paper records are appropriately disposed of and all devices and media are sanitized in accordance with NIST SP 800-88, Guidelines for Media Sanitization.

d. Notification. The Contractor (and/or any subcontractor) must notify the CO and/or COR and system

ISSO within 15 days before an employee stop working under this contract.

e. Contractor Responsibilities upon Physical Completion of the Contract. The contractor (and/or any subcontractors) must return all government information and IT resources (i.e., government information in non-government-owned systems, media, and backup systems) acquired during the term of this contract to the CO and/or COR. Additionally, the Contractor must provide a certification that all government information has been properly sanitized and purged from Contractor-owned systems, including backup systems and media used during contract performance, in accordance with CDC policies.

f. The Contractor (and/or any subcontractor) must perform and document the actions identified in the

CDC Out-Processing Checklist

(http://intranet.cdc.gov/od/hcrmo/pdfs/hr/Out_Processing_Checklist.pdf) when an employee terminates work under this contract within 15 days of the employee's exit from the contract. All documentation must be available to the CO and/or COR upon request.

9. Records Management and Retention

a. The Contractor (and/or any subcontractor) must maintain all information in accordance with Executive

Order 13556 -- Controlled Unclassified Information, National Archives and Records Administration

(NARA) records retention policies and schedules and CDC Policy for Records Management and HHS policies and must not dispose of any records unless authorized by CDC Program.

b. If a contractor (and/or any subcontractor) accidentally disposes of or destroys a record without proper authorization, he/she must document and report the incident in accordance with CDC policies.

10. High Value Asset (HVA):

If a system is identified as HVA, the contractor must comply with the HHS Policy for the High Value Asset

(HVA) Program and the Department of Homeland Security (DHS) HVA Control Overlay[22] in addition to the above requirements.

11. Deliverables

Deliverable Title/Deliverable

Type

Description Due Date

Roster Roster Within 30 days of the effective date of this contract

Contractor Employee Non-

Disclosure Agreement (NDA)

Contractor Employee Non-

Disclosure Agreement (NDA)

Prior to performing any work on behalf of HHS

Privacy Threshold Analysis

(PTA)/ Privacy Impact

Assessment (PIA)

Assist in the completion of a

PTA/PIA form

Within 60-90 days after contract award

Training Records Copy of training records for all mandatory training

In conjunction with contract award and annually thereafter or upon request

Rules of Behavior Signed ROB for all employees Initiation of contract and at least annually thereafter

Incident Response Incident Report (as incidents or breaches occur)

As soon as possible and without reasonable delay and no later than 1 hour of discovery

Personnel Security

Responsibilities

List of Personnel with defined roles and responsibilities

Within 7 days; that is before an employee begins working on this contract.

Personnel Security

Responsibilities

Off-boarding documentation, equipment and badge when leaving contract

Within 5 days or less after the

Government’s final acceptance of the work under this contract, or in the event of a termination of the contract.

Background Investigation

Onboarding documentation when beginning contract.

Prior to performing any work on behalf of HHS http://intranet.cdc.gov/od/hcrmo/pdfs/hr/Out_Processing_Checklist.pdf https://login.max.gov/cas/login?service=https%3A%2F%2Fcommunity.max.gov%2Flogin.action%3Fos_destination%3D%252Fpages%252Fviewpage.action%253FspaceKey%253DHHS%2526title%253DHHS%252BCyberSecurity%252BPolicy%252BCollaboration%252BPage

Certification of Sanitization of

Government and Government

Activity-

Related Files, Information, and

Devices.

Form or deliverables required by

CDC

At contract expiration.

Contract Initiation and

Expiration

If the procurement involves a system or cloud service, additional documentation will be required, such as Disposition/Decommission

Plan

At contract expiration.

Standard-2 Requirements for Procurements Involving Privacy

Appropriate security controls and Rules of Behavior should be incorporated to protect the confidentiality of information, proprietary, sensitive, and Personally Identifiable Information (PII) the Contractor may encounter during the performance of this contract.

Standard-5 Other IT Procurements

1. Hardware Procurements

a. Card Readers. The Contractor (and/or any subcontractor) must include Federal Information

Processing Standard (FIPS) 201-compliant smart card readers (referred to as LACS Transparent

Readers) with the purchase of servers, printers, desktops, and laptops.

b. Mobile Devices. The contractor must follow NIST 800-124, Rev. 1, Guidelines for Managing the

Security of Mobile Devices in the Enterprise and comply with Public Law 115-232 § 889, when purchasing mobile devices that process or store CDC data.

2. Non-Commercial and Open-Source Computer Software Procurements

The Contractor (and/or any subcontractor) must follow secure coding best practice requirements, as directed by the United States Computer Emergency Readiness Team (US-CERT) specified standards and the Open Web Application Security Project (OWASP) that will limit system software vulnerability exploits. The contractor will be liable for malicious or defective code or failure to reduce risk.

3. Information Technology Application Design, Development, or Support

a. The Contractor (and/or any subcontractor) must ensure IT applications designed and developed for end users (including mobile applications and software licenses) run in the standard user context without requiring elevated administrative privileges.

b. The contractor must consult the guidelines from NIST SP 800-160 volume 1, Systems Security

Engineering: Considerations for a Multidisciplinary Approach in the Engineering of Trustworthy

Secure Systems, NIST SP 800-160 volume 2, Systems Security Engineering: Considerations for a

Multidisciplinary Approach in the Engineering of Trustworthy Secure Systems, and NIST SP 800-53 to implement security during the development of all applications and throughout the life cycle stages of software development.

c. The Contractor (and/or any subcontractor) must follow secure coding best practice requirements, as directed by United States Computer Emergency Readiness Team (US-CERT) specified standards, the

Open Web Application Security Project (OWASP), System Admin, Audit, Network and Security

(SANS), HHS Policy for Software Development Secure Coding Practices and CDC Secure Software

Development Standard that will limit system software vulnerability exploits.

https://www.idmanagement.gov/approved-products-list-pacs-products/ https://www.idmanagement.gov/approved-products-list-pacs-products/

d. The Contractor (and/or any subcontractor) must ensure that computer software developed on behalf of

CDC or tailored from an open-source product, is fully functional and operates correctly on systems configured in accordance with government policy and federal configuration standards. The contractor must test applicable products and versions with all relevant and current updates and patches updated prior to installing in the CDC environment. No sensitive data must be used during software testing.

e. The contractor must, at a minimum, segregate physically or logically, all test and development systems from production systems as applicable in accordance with the HHS Standard for Segregation of

Dev/Test Environments from Production.

f. The Contractor (and/or any subcontractor) must protect information that is deemed sensitive from unauthorized disclosure to persons, organizations or subcontractors who do not have a need to know the information. Information which, either alone or when compared with other reasonably-available information, is deemed sensitive or proprietary by CDC must be protected as instructed in accordance with the magnitude of the loss or harm that could result from inadvertent or deliberate disclosure, alteration, or destruction of the data. This language also applies to all subcontractors that are performing under this contract.

4. Physical Access to Government Controlled Facilities

(NOTE: For procurements involving physical access to government facilities, selected language from

Appendix B: Standards may apply. This includes, but not limited to security awareness, incident response, and HSPD-12. Consult with the CDC Component Information Systems Security Officer (ISSO), CDC

CPO, and other relevant stakeholders to select applicable language.)

Additionally, due to the COVID-19 Epidemic of 2020 (Effective as of March 30, 2020), The below contract language must be included in all COVID-19 contract actions until such time the CDC Director makes a determination to issue rated contracts related to items used for allowing CDC employees/contractors to physically use and/or operate in CDC facilities and spaces.

"CDC reserves the right to exercise priorities and allocations authority with respect to this contract, to include rating this order in accordance with 45 CFR Part 101, Subpart A—Health Resources Priorities and

Allocations System."

5. Deliverables

Deliverable Title Description Due Date

Other IT Procurements (Non-

Commercial and Open-Source

Computer Software Procurements)

Computer software, including the source code.

Prior to performing any work on behalf of HHS

Standard-6 Installation and Servicing of Equipment

Contractor shall scan all media (CDs, DVDs, portable hard drives, thumb drives, etc.) used for upgrading and installing the vendor’s software/firmware with antivirus software that has the latest virus signatures. The scans shall occur before using the media in a CDC computer/device and when moving the media between CDC computers/devices.

If in the performance of this contract, the contractor must replace an information storage device (hard drive, non-volatile flash memory module, etc.) or service equipment offsite, the contractor must remove the information storage device(s) from the equipment and provide it to CDC to be either destroyed or erased. The contractor shall not bring off-site any part of the equipment they are servicing that contains CDC data.

SECTION 1 – PROPOSED CONTRACT TYPE

We intend for this to be a firm-fixed price contract.

SECTION 2 – OPTIONAL SPECIAL CONSIDERATIONS

SUBSECTION A – PAYMENT CLAUSES

HHSAR 352.232-71 Electronic Submission of Payment Requests

(a) Definitions. As used in this clause—

(1) “ Payment request” means a bill, voucher, invoice, or request for contract financing payment with associated supporting documentation. The payment request must comply with the requirements identified in FAR 32.905(b), “Content of Invoices” and the applicable Payment clause included in this contract.

(b) Except as provided in paragraph (c) of this clause, the Contractor shall submit payment requests electronically using the Department of Treasury Invoice Processing Platform (IPP) or successor system. Information regarding

IPP, including IPP Customer Support contact information, is available at www.ipp.gov or any successor site.

(c) The Contractor may submit payment requests using other than IPP only when the Contracting Officer authorizes alternate procedures in writing in accordance with HHS procedures.

(d) If alternate payment procedures are authorized, the Contractor shall include a copy of the Contracting Officer's written authorization with each payment request.

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

402 Closed Functionality

403 Biometrics

404 Preservation of Information Provided for Accessibility

405 Privacy

406 Standard Connections

407 Operable Parts

408 Display Screens

409 Status Indicators

410 Color Coding

OTHER CONSIDERATIONS AND ADDITIONAL INFORMATION FOR OFFICE

OF ACQUISITION SERVICES

http://www.ipp.gov/ http://www.hhs.gov/web/508 http://www.access-board.gov/sec508/standards.htm

411 Audible Signals

502 Inoperability with Assistive Technology

503 Applications

504 Authoring Tools

602 Support Documentation

603 Support Services

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.