GS35F0577V 75D30120F09234 TrueTandem DSAT IPP Task Order.pdf

ORDER FOR SUPPLIES OR SERVICES

PAGE OF PAGES

1 30 IMPORTANT: Mark all packages and papers with contract and/or order numbers.

1. DATE OF ORDER 2. CONTRACT NO. (If any) 6. SHIP TO:

08/21/2020 GS35F0577V a. NAME OF CONSIGNEE

3. ORDER NO. 4. REQUISITION/REFERENCE NO. CDC OPHPR

75D30120F09234 000HCBCC-2020-45849 b. STREET ADDRESS

5. ISSUING OFFICE (Address correspondence to) Centers for Disease Control and Prevention (CDC) Office of Acquisition Services (OAS) 2900 Woodcock Blvd, MS TCU-4 Atlanta, GA 30341-4004

1600 Clifton Road

c. CITY

Atlanta

d. STATE

GA

e. ZIP CODE

30329-4018

f. SHIP VIA

a. NAME OF CONTRACTOR

TRUETANDEM, LLC

DUNS NUMBER: 826891546 8. TYPE OF ORDER

b. COMPANY NAME a. PURCHASE X b. DELIVERY

REFERENCE YOUR:

c. STREET ADDRESS

520 HUNTMAR PK DR STE A

d. CITY

HERNDON

e. STATE

VA

f. ZIP CODE

20170-5156

9. ACCOUNTING AND APPROPRIATION DATA

See Section B

10. REQUISITIONING OFFICE

HCBCC

11. BUSINESS CLASSIFICATION (Check appropriate box(es)) X a. SMALL b. OTHER THAN SMALL c. DISADVANTAGED d. WOMEN-OWNED

12. F.O.B. POINT

Destination

13. PLACE OF

a. INSPECTION b. ACCEPTANCE

14. GOVERNMENT B/L NO.

15. DELIVER TO F.O.B. POINT

ON OR BEFORE (Date)

08/23/2021

16. DISCOUNT TERMS

Net 30 Days

17. SCHEDULE (See reverse for Rejections)

ITEM NO.

(a)

SUPPLIES OR SERVICES

(b)

QUANTITY

ORDERED

(c)

UNI

T

(d)

UNIT

PRICE

(e)

AMOUNT

(f)

QUANTITY

ACCEPTED

(g) To ensure payment invoice must reference

Purchase Order# 75D30120F09234 and DUNS Number and Tax ID, Invoice/ Payment information: 404-718-8100. Send invoices to FAX: 404-638-5324 or Email:

fmoapinv@cdc.gov

Vendor: Sophy Kang Email: sophy.kang@truetandem.com

CDC: Rhonda Smith Tele: (770) 488-8618 Email: rtd6@cdc.gov

Contract Specialist: Michael Crow Tele:(770) 488-3208 Email: wyv2@cdc.gov

18. SHIPPING POINT

19. GROSS SHIPPING WEIGHT

20. INVOICE NO.

21. MAIL INVOICE TO: $439,659.90

a. NAME

Centers for Disease Control and Prevention (FMO)

b. STREET ADDRESS (or P.O. Box)

PO Box 15580 404-718-8100

c. CITY

Atlanta

d. STATE

GA

e. ZIP CODE

303330080 $735,156.78

22. UNITED STATES

OF AMERICA (Signature)

23. NAME (Typed)

Michael Crow

TITLE: CONTRACTING/ORDERING OFFICER

NSN 7540-01-152-8083

PREVIOUS EDITION NOT USABLE OPTIONAL FORM 347 (REV. 6/95)

Prescribed by GSA/FAR 48 CFR 53.213(e)

Except for billing instructions on the reverse, this delivery order is subject to instructions contained on this side only of this form and is issued subject to the terms and conditions of the above-numbered contract.

Please furnish the following on the terms and conditions specified on both sides of this order and on the attached sheet, if any, including delivery as indicated.

17(h) TOT.

(Cont.

pages) SEE BILLING

INSTRUCTIONS

ON

REVERSE

17(i)

GRAND

TOTAL

7. TO:

mailto:fmoapinv@cdc.gov mailto:sophy.kang@truetandem.com mailto:rtd6@cdc.gov mailto:wyv2@cdc.gov

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

ITEM SUPPLIES / SERVICES QTY / UNIT UNIT PRICE EXTENDED PRICE

0001 Task 1: Common Inspection Application:

This is a severable fixed price line item.

Period of Performance: 08/24/2020 – 08/23/2021

Awarded in accordance with the Authorization to Proceed (ATP) provided on 08/21/2020.

1 Job $439,659.90 $439,659.90

Line(s) Of Accounting:

9390EU6 2512 2020 75-2022-0943 CO23111101

$79,811.30

939ZSTY 2512 2020 75-20-0956 5623221201

$359,848.60

Optional Line Items:

ITEM SUPPLIES / SERVICES QTY / UNIT UNIT PRICE EXTENDED PRICE

0002 Task 2: Robust Reporting Platform:

This is a severable fixed price optional line item.

This optional line item may be exercised between 08/24/2020 – 08/23/2021, and may have an end-date up to and including 08/23/2021.

1 Job $295,496.88 $295,496.88

Recapitulation of Pricing Task 1: $439,659.90 Task 2 (Optional): $295,496.88 Total $735,156.78

Schedule of Milestones for Performance-based Payments

The following schedule in conjunction with the following payment schedule provides the milestones necessary to receive performance-based payments. The determination of eligibility for receipt of payment will be made by the Contracting Officer upon written certifications from the COR that the milestone has been met.

Milestone Payment Amount Task1-The Common Inspection Application - Kickoff Completion $ 137,372.84

Task1-The Common Inspection Application - Development Completion $ 183,163.80

Task1-The Common Inspection Application - Task Completion $ 119,123.26

Task 1 Total: $ 439,659.90 Task2-Preliminary Scope- EIPP Robust Reporting Platform and EPLC Documentation - Kickoff Completion

$ 91,500.78

Task2-Preliminary Scope- EIPP Robust Reporting Platform and EPLC Documentation - Development Completion

$ 122,001.02

Task2-Preliminary Scope- EIPP Robust Reporting Platform and EPLC Documentation - Task Completion

$ 81,995.08

Task 2 Total: $ 295,496.88

Overall Total: $ 735,156.78

Section C - Description/Specification/Work Statement

Title: Import Permit Program – DSAT – COVID-19 Response

C.1 BACKGROUND

The Division of Select Agents and Toxins contains the Import Permit Program (IPP). Section 361 of the Public Health Service Act (PHS Act) (42 U.S.C. 264) provides the Secretary of Health and Human Services (HHS) with the authority to make and enforce regulations to regulate infectious biological agents, infectious substances, and vectors of human disease to prevent the introduction, transmission, and spread of communicable diseases from foreign countries into the United States (including its possessions) and from one state or possession into another. Section 361 of the PHS Act also provides authority for the HHS Secretary to conduct inspections for purposes of carrying out and enforcing such regulations.

HHS delegated to CDC’s Division of Select Agents and Toxins (DSAT) regulatory (42 CFR Part 71.54; Import regulations for infectious biological agents, infectious substances, and vectors) responsibility of importation of infectious biological agents, infectious substances, and/or vectors which affect human health in the United States.

CDC’s Import Permit Program ensures laboratories importing infectious biological agents into the United States have appropriate biosafety measures to prevent introduction or spread of these biological agents by providing the following critical capabilities (not all inclusive):

• The ability to monitor and control importation of exotic agents and/or vectors of human disease into the U.S by providing import permits;

• The ability to perform risk-based inspections of the importer facilities to ensure sufficient biosafety measures are in place to work safely with the imported infectious biological agents, hosts, and vectors.

IPP is currently supporting the COVID-19 Response and the current system does not meet the required need. This Task Order is to provide development support to modify and enhance the current system in order to meet the urgent rising needs for the Import Permit Program in association with the COVID-19 Response.

C.2 PURPOSE

The purpose of this task order is to support one primary task and one optional task in support the COVID-19 Response:

Task 1: Common Inspection Application

Task 2 is an optional task that may be exercised during the 12-month period of performance.

Both tasks are in association with the electronic Import Permit Program System (eIPP)

C.3 SCOPE OF WORK

The contractor shall provide development support to modify and enhance the current Import Permit Program system in order to meet the urgent rising needs for the Import Permit Program in association with the COVID-19 Response.

C.4 MINIMUM VENDOR QUALIFICATIONS

The contractor shall be a Microsoft Premier Support Services authorized partner/reseller.

C.5 TASKS TO BE PERFORMED

Task 1: Common Inspection Application

In order to support the needs of the COVID-19 Response, this Task Order is to build a common inspection application, which shall be re-platforming and simplification of the existing inspections module on eFSAP, able to host multiple CDC organizations data. It shall have these attributes:

1. Users shall be segmented into “Organizations” and each organization shall only be able to view their own data. Example organizations would be “Polio eradication” or “Import Permit Program.”

2. Each organization would be able to do a limited amount of branding and can customize checklist definitions via the common checklist service, but otherwise would share the same processes.

3. The common inspections application would also have a common service API layer. Authentication shall rely on Azure AD and/or SAMS OAUTH.

4. The use of a common platform shall aid in future-proofing potential decisions that may transitions inspections related to COVID-19to be regulated by FSAP rather than IPP regulations.

In addition, the scope of work to be completed shall include the following elements:

1. New table structures to receive data from external source – A separate effort not in scope for this Task Order is building the collection device.

2. API to receive data from device and push most recent versions of incomplete checklists to the device.

3. Ensure encryption of all communications.

4. EPLC compliant documentation.

The following eIPP Modifications to support inspections shall also need to be completed.

1. Technical reviewers can initiate inspections.

2. Technical reviewers can schedule inspections.

3. Technical reviewers can define which checklists to utilize on an inspection.

4. Technical reviewers can complete checklists and save their results in a web interface.

5. Technical reviewers can review all completed checklists prior to releasing information to the inspected facility.

6. Permittees can see scheduled inspections (once/if announced)

7. Permittees can see checklist and inspection results, once released by technical reviewers.

8. Permittees can communicate with technical reviewers about inspection findings.

9. Technical reviewers can update findings with documentation based upon communication with permittees.

10. Technical reviewers can generate an approval letter (pdf) including inspection findings.

11. Technical reviewers can denial letter (pdf) including inspection findings and corrective actions that need to be taken in order to reapply.

12. EIPP users receive relevant notifications of changes in inspection scheduling, status, release and communication.

These capabilities may be hosted within the common inspections platform or within eIPP itself, so long as the user experience is not negatively affected.

Task 2: EIPP Robust Reporting Platform (Optional Task)

While some reporting is available within the current system, it is desired to greatly expand this to include:

1. Operational Data Store (ODS) – this repository allows the application to export its data for use in reporting in a relational database format in such a way as to be end user accessible by tools such as PowerBI or Tableau.

2. Processing of data from the common inspections platform and common checklist service, when built.

3. ETL processes to support load of all data from EIPP to the ODS.

4. Full documentation to include both logical and physical data models.

5. Series of three prebuilt reports as determined by program leadership.

6. Capacity for Ad Hoc reporting.

7. Train the trainer for support staff to be able to self-support the reporting functions going forward.

Compliance Requirements:

Office Of Chief Information Officer (OCISO) Security Configurations Requirements: Applies to all tasks

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) employee 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 or less, bring the situation to the attention of the other party, as well as be notified to the system security steward for potential escalation to ISSO and CSIRT

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.

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: [X ] Low [ ] Moderate [] High Availability: [ X] Low [ ] Moderate [] High Overall Risk Level: [X ] Low [ ] 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:

[ ] No PII [X ] 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 32 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 mailto:fisma@hhs.gov 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.

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.

10) Contract Documentation. The Contractor shall use provided templates, policies, forms and other agency documents to comply with contract deliverables as appropriate. See Section 7 for full list of contract deliverables

11) Standard for Encryption. The Contractor (and/or any subcontractor) shall:

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

b. 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 FIPS 140-2 validated encryption solution.

c. Secure all devices (i.e.: desktops, laptops, mobile devices, etc.) that store and process government information and ensure devices meet HHS and CDC-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).

d. Verify that the encryption solutions in use have been validated under the Cryptographic Module Validation Program to confirm compliance with FIPS 140-2. The Contractor shall provide a written copy of the validation documentation to the COR.

e. Use the Key Management system on the HHS 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. Encryption keys shall be provided to CDC Office of Chief Information Security Officer (OCISO).

12) Contractor Non-Disclosure Agreement (NDA). Each Contractor (and/or any subcontractor) employee having access to non-public government information under this contract shall complete the CDC non-disclosure agreement, as applicable. A copy of each signed and witnessed NDA shall be submitted to the Contracting Officer (CO) and/or CO Representative (COR) prior to performing any work under this acquisition.

13) Privacy Threshold Analysis (PTA)/Privacy Impact Assessment (PIA) – The Contractor shall assist the CDC Senior Official for Privacy (SOP) or designee with conducting a PTA for the information system and/or information handled under this contract in accordance with HHS policy and OMB M-03-22, Guidance for Implementing the Privacy Provisions of the E-Government Act of 2002.

a. The Contractor shall assist the CDC SOP or designee in reviewing the PIA at least every three years throughout the system development lifecycle (SDLC)/information lifecycle, or when determined by the CDC SOP that a review is required based on a major change to the system (e.g., new uses of information collected, changes to the way information is shared or disclosed and for what purpose, or when new types of PII are collected that could introduce new or increased privacy risks), whichever comes first.

B. Training

1) Mandatory Training for All Contractor Staff. All Contractor (and/or any subcontractor) employees assigned to work on this contract shall complete the applicable HHS/CDC Contractor Information Security Awareness, Privacy, and Records Management training (provided upon contract award) before performing any work under this contract. Thereafter, the employees shall complete CDC Security Awareness Training (SAT), Privacy, and Records Management training at least annually, during the life of this contract. All provided training shall be compliant with HHS training policies.

2) 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 (RBT) within 60 days of assuming their new responsibilities. Thereafter, they shall complete RBT at least annually in accordance with HHS policy and the HHS Role-Based Training (RBT) of Personnel with Significant Security Responsibilities Memorandum.

All HHS employees and contractors with SSR who have not completed the required training within the mandated timeframes shall have their user accounts disabled until they have met their RBT requirement.

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

C. Rules of Behavior

1) The Contractor (and/or any subcontractor) shall ensure that all employees performing on the contract comply with the HHS Information Technology General Rules of Behavior.

2) All Contractor employees performing on the contract must read and adhere to the Rules of Behavior before accessing Department 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 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.

D. Incident Response

The Federal Information Security Modernization Act (FISMA) defines an incident as “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. The HHS Policy for IT Security and Privacy Incident Reporting and Response further defines incidents as events involving cybersecurity and privacy threats, such as viruses, malicious user activity, loss of, unauthorized disclosure or destruction of data, and so on.

A privacy breach is a type of incident and is defined by FISMA as 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.

OMB Memorandum M-17-12, “Preparing for and Responding to a Breach of Personally Identifiable Information” (03 January 2017) states:

Definition of an Incident:

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.

Definition of a Breach:

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.

It further adds:

A breach is not limited to an occurrence where a person other than an authorized user potentially accesses PII by means of a network intrusion, a targeted attack that exploits website vulnerabilities, or an attack executed through an email message or attachment. A breach may also include the loss or theft of physical documents that include PII and portable electronic storage media that store PII, the inadvertent disclosure of PII on a public website, or an oral disclosure of PII to a person who is not authorized to receive that information. It may also include an authorized user accessing PII for any other than authorized purpose.

The HHS Policy for IT Security and Privacy Incident Reporting and Response further defines a breach as “a suspected or confirmed incident involving PII.”

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

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

2) 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 so as to avoid a secondary sensitive information incident with FIPS 140-2 validated encryption.

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

4) All contractors and subcontractors shall report a suspected or confirmed breach in any medium as soon as possible and no later than 1 hour of discovery, consistent with applicable CDC IT acquisitions guidance, HHS/CDC and incident management policy, and United States Computer Emergency Readiness Team (US- CERT) notification guidelines. To this end, the Contractor (and/or any subcontractor) shall respond to all alerts/Indicators of Compromise (IOCs) provided by HHS Computer Security Incident Response Center (CSIRC) or CDC Computer Incident Response Team (CSIRT) within 24 hours via email at csirt@cdc.gov or telephone at 866-655-2245, whether the response is positive or negative.

5) 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.

6) All contractors and subcontractors shall allow for an inspection, investigation, forensic analysis, and any other action necessary to ensure compliance with HHS/CDC Policy and the HHS/CDC Breach Response Plan and to assist with responding to a breach.

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

8) Identify roles and responsibilities, in accordance with HHS/CDC Breach Response Policy and the HHS/CDC Breach Response Plan. To this end, the Contractor shall NOT notify affected individuals unless and until so instructed by the Contracting Officer or designated representative. If so instructed by the Contracting Officer or representative, all notifications must be pre-approved by the appropriate CDC officials, consistent with HHS/CDC Breach Response Plan, and the Contractor shall then send CDC-approved notifications to affected individuals.; and,

9) 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.

E. 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 requiring activity representative, in conjunction with Personnel Security, shall use the OPM Position Sensitivity Designation automated tool (https://www.opm.gov/investigations/) to determine the sensitivity designation for background investigations. After making those determinations, include all applicable position sensitivity designations.

F. Homeland Security Presidential Directive (HSPD)-12 mailto:csirt@cdc.gov https://www.opm.gov/investigations/

The Contractor (and/or any subcontractor) and its employees shall comply with Homeland Security Presidential Directive (HSPD)-12, Policy for a Common Identification Standard for Federal Employees and Contractors;

OMB M-05-24; FIPS 201, Personal Identity Verification (PIV) of Federal Employees and Contractors; HHS HSPD-12 policy; and Executive Order 13467, Part 1 §1.2.

For additional information, see HSPD-12 policy at: https://www.dhs.gov/homeland-security-presidential-directive-12)

Roster. The Contractor (and/or any subcontractor) shall 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 shall be submitted to the COR and/or CO by the effective date of this contract. Any revisions to the roster as a result of staffing changes shall be submitted immediately upon 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 shall provide a position description and the Government will determine the appropriate suitability level.

G. Contract Initiation and Expiration

1) General Security Requirements. The Contractor (and/or any subcontractor) shall comply with information security and privacy requirements, Enterprise Performance Life Cycle (EPLC) processes, HHS 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 shall follow the HHS EPLC framework and methodology and in accordance with the HHS Contract Closeout Guide (2012).

2) System Documentation. Contractors (and/or any subcontractors) must follow and adhere to NIST SP 800-64, Security Considerations in the System Development Life Cycle, 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.

3) Sanitization of Government Files and Information. As part of contract closeout and at expiration of the contract, the Contractor (and/or any subcontractor) shall 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.

4) Notification. The Contractor (and/or any subcontractor) shall notify the CO and/or COR and system ISSO before an employee stops working under this contract.

5) Contractor Responsibilities Upon Physical Completion of the Contract. The contractor (and/or any subcontractors) shall 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 shall 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 HHS and/or CDC policies.

6) The Contractor (and/or any subcontractor) shall 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. All documentation shall be made available to the CO and/or COR upon request.

H. Records Management and Retention The Contractor (and/or any subcontractor) shall maintain all information in accordance with Executive Order 13556 -- Controlled Unclassified Information, National Archives and Records Administration (NARA) records retention policies and schedules and HHS policies and shall not dispose of any records unless authorized by

HHS.

In the event that a contractor (and/or any subcontractor) accidentally disposes of or destroys a record without proper authorization, it shall be documented and reported as an incident in accordance with HHS policies.

https://www.dhs.gov/homeland-security-presidential-directive-12 https://www.dhs.gov/homeland-security-presidential-directive-12 http://intranet.cdc.gov/od/hcrmo/pdfs/hr/Out_Processing_Checklist.pdf

I. Privacy Act

It has been determined that this contract is subject to the Privacy Act of 1974, because this contract provides for the design, development, or operation of a system of records on individuals.

The System of Records Notice (SORN) that is applicable to this contract is: 09-20-0170 and 09-20-0180, both under final Departmental/OMB review for publication.

The design, development, or operation work the Contractor is to perform is: See requirements as outline in sections 3.1 (page 5) through 3.3 (Page 9).

The disposition to be made of the Privacy Act records upon completion of contract performance is: See section H above.

C.6 TASK ORDER REPORTS AND DELIVERABLES

See Attachment G.1 for additional deliverables requirements.

Program Oversight:

• Initial Briefing to introduce Contractor and CDC;

• Monthly Status Reports;

• Close out report at end of contract.

Assistance with updating of Divisions documentation based on outcome of resolved issues, to include:

• Update to existing Design Document;

• Update to existing User Training Guides;

• Update to existing O&M Manual.

Section D – Contract Administration Data

D.1 CDC0.G008 Contracting Officer’s Representative (COR) (Jul 2017)

Performance of the work hereunder shall be subject to the technical directions of the designated COR for this contract.

As used herein, technical directions are directions to the Contractor which fill in details, suggests possible lines of inquiry, or otherwise completes the general scope of work set forth herein. These technical directions must be within the general scope of work, and may not alter the scope of work or cause changes of such a nature as to justify an adjustment in the stated contract price/cost, or any stated limitation thereof.

In the event that the Contractor believes full implementation of any of these directions may exceed the scope of the contract, he or she shall notify the originator of the technical direction and the Contracting Officer, immediately or as soon as possible, in a letter or e-mail separate of any required report(s). No technical direction, nor its fulfillment, shall alter or abrogate the rights and obligations fixed in this contract.

The Government COR is not authorized to change any of the terms and conditions of this contract. Contract changes shall be made only by the Contracting Officer by properly written modification(s) to the contract.

The Government will provide the Contractor with a copy of the COR delegation memorandum upon request.

D.2 CDC0.G018 Payment by Electronic Funds Transfer (Feb 2018)

(a) The Government shall use electronic funds transfer to the maximum extent possible when making payments under this contract. FAR 52.232-33, Payment by Electronic Funds Transfer –System for Award Management, in Section I, requires the contractor to designate in writing a financial institution for receipt of electronic funds transfer payments.

(b) In the case that EFT information is not within the System of Award Management, FAR 52.232-34 requires mandatory submission of Contractor’s EFT information directly to the office designated in this contract to receive that information (hereafter: “designated office”); see below. The contractor shall submit the EFT information within the form titled “ACH Vendor/Miscellaneous Payment Enrollment Form” to the address indicated below. Note: The form is either attached to this contract (see Section J, List of Attachments) or may be obtained by contacting the Contracting Officer or the CDC Office of Financial Resources at 678-475-4510.

(c) In cases where the contractor has previously provided such information, i.e., pursuant to a prior contract/order, and been enrolled in the program, the form is not required unless the designated financial institution has changed.

(d) The completed form shall be mailed after award, but no later than 14 calendar days before an invoice is submitted, to the following address:

The Centers for Disease Control and Prevention Office of Financial Resources (OFR) P.O. Box 15580 Atlanta, GA 30333 Or – Fax copy to: 404-638-5342

D.3 CDC42.0002 Evaluation of Contractor Performance Utilizing CPARS (Apr 2015)

In accordance with FAR 42.15, the Centers for Disease Control and Prevention (CDC) will review and evaluate contract performance. FAR 42.1502 and 42.1503 requires agencies to prepare evaluations of contractor performance and submit them to the Past Performance Information Retrieval System (PPIRS). The CDC utilizes the Department of Defense (DOD) web-based Contractor Performance Assessment Reporting System (CPARS) to prepare and report these contractor performance evaluations. All information contained in these assessments may be used by the Government, within the limitations of FAR 42.15, for future source selections in accordance with FAR 15.304 where past performance is an evaluation factor.

The CPARS system requires a contractor representative to be assigned so that the contractor has appropriate input into the performance evaluation process. The CPARS contractor representative will be given access to CPARS and will be given the opportunity to concur or not-concur with performance evaluations before the evaluations are complete. The CPARS contractor representative will also have the opportunity to add comments to performance evaluations.

The assessment is not subject to the Disputes clause of the contract, nor is it subject to appeal beyond the review and comment procedures described in the guides on the CPARS website. Refer to: www.cpars.gov for details and additional information related to CPARS, CPARS user access, how contract performance assessments are conducted, and how Contractors participate. Access and training for all persons responsible for the preparation and review of performance assessments is also available at the CPARS website.

The contractor must provide the CDC contracting office with the name, e-mail address, and phone number of their designated CPARS representative who will be responsible for logging into CPARS and reviewing and commenting on performance evaluations. The contractor must maintain a current representative to serve as the contractor representative in CPARS. It is the contractor’s responsibility to notify the CDC contracting office, in writing (letter or email), when their CPARS representative information needs to be changed or updated. Failure to maintain current CPARS contractor representative information will result in the loss of an opportunity to review and comment on performance evaluations.

[End of Clause]

D.4 CDCA.G001 Invoice Submission (Jul 2017)

(a) The Contractor shall submit the original contract invoice/voucher as described below

The Centers for Disease Control and Prevention Office of Financial Resources (OFR) P.O. Box 15580 Atlanta, GA 3033

Or – The Contractor may submit the original invoice via facsimile or email: Fax: 404-638-5324

Email: FMOAPINV@CDC.GOV

NOTE: Submit to only one (1) of the above locations.

(b) The contractor shall submit 2 copies of the invoice to the cognizant contracting office previously identified in this contract. These invoice copies shall be addressed to the attention of the Contracting Officer.

(c) The Contractor is , is not required to submit a copy of each invoice directly to the Contracting Officer’s Representative (COR) concurrently with submission to the Contracting Officer.

(d) In accordance with 5 CFR part 1315 (Prompt Payment), CDC's Office of Financial Resources is the designated billing office for the purpose of determining the payment due date under FAR 32.904.

(e) The Contractor shall include (as a minimum) the following information on each invoice:

(1) Contractor’s Name & Address

(2) Contractor’s Tax Identification Number (TIN)

(3) Purchase Order/Contract Number and Task Order Number, if Appropriate

(4) Invoice Number

(5) Invoice Date

(6) Contract Line Item Number and Description of Item

(7) Quantity

(8) Unit Price & Extended Amount for each line item http://www.cpars.gov/ mailto:FMOAPINV@CDC.GOV

(9) Shipping and Payment Terms

(10) Total Amount of Invoice

(11) Name, title and telephone number of person to be notified in the event of a defective invoice

(12) Payment Address, if different from the information in (c)(1).

(13) DUNS + 4 Number

(14) Electronic funds transfer (EFT) banking information

D.5 CDCP.G009 Contracting Officer (Jul 1999)

(a) The Contracting Officer is the only individual who can legally commit the Government to the expenditure of public funds. No person other than the Contracting Officer can make any changes to the terms, conditions, general provisions, or other stipulations of this contract.

(b) No information, other than that which may be contained in an authorized modification to this contract, duly issued by the Contracting Officer, which may be received from any person employed by the United States Government, or otherwise, shall be considered grounds for deviation from any stipulation of this contract.

D.6 CDCP.G010 Contract Communications/Correspondence (Jul 1999)

The Contractor shall identify all correspondence, reports, and other data pertinent to this contract by imprinting thereon the contract number from Page 1 of the contract.

Section E – Special Task Order Requirements

E.1 CDCA_H037 Observance of Legal Holidays and Administrative Leave (Government Facilities Performance) (Jun 2020)

(a) Holidays

Government personnel observe the following listed days as holidays:

Washington's Birthday Memorial Day Independence Day Labor Day Veterans' Day Thanksgiving Day Christmas Day New Year's Day Columbus Day Martin Luther King Day

Any other day designated by Federal Statute Any other day designated by Executive Order Any other day designated by Presidential proclamation

For purposes of contract performance, the Contractor shall observe the above holidays on the date observed by the Government. Observance of such days shall not be cause for an additional period of performance or entitlement to compensation except as otherwise set forth in the contract. No form of holiday or other premium compensation will be reimbursed , however this does not preclude reimbursement for overtime work authorized in writing by the Contracting Officer.

(b) Unscheduled Facility Closures

In the event Government facilities are closed due to inclement weather, potentially hazardous or unsafe conditions, or other special circumstances, contractor personnel assigned to work within those facilities are automatically dismissed.

Notwithstanding the terms herein, the contractor shall comply with any specific contract terms that require a level of ongoing support for critical operations during times of facility closure. The contractor may also continue to provide support under a scheduled telework arrangement in accordance with the terms of the contract if the contract expressly authorizes telework in writing.

(c) Cost Impact

Accounting for costs associated with an unscheduled facility closure is unique to each contract and depends upon a number of factors such as:

i) Contract type, e.g. Fixed Price, Time and Materials, or Cost Reimbursement.

ii) Contractor's established management and accounting practices for unproductive time.

iii) The inclusion and applicability of other contract terms & conditions.

iv) The ability of the contractor to mitigate costs by reassigning employees to work on other contracts, to work from a different facility, or to work remotely from home in accordance with contract telework provisions.

E.2 CDC0.H057 Telework by Contractor (Feb 2015)

Telework is the movement of contract performance from a CDC facility to a teleworker's residence or alternate work site. The Contractor's organizational decision to participate in telework is voluntary, and telework shall not increase the contract price. After contract award, telework arrangements shall be mutually agreed to in advance by the Contractor, the Contracting Officer, and the Project Officer. The Contractor shall submit written telework requests to the Contracting Officer in accordance with instructions provided by the Contracting Officer. The Contractor shall ensure the continuity of performance by Teleworkers and the monitoring of Teleworkers' time.

CDC staff do not supervise contractor employees and do not approve or monitor contractor employees’ telework.

Only the Contracting Officer has authority to approve telework arrangements on behalf of CDC.

Teleworkers shall use Government-Furnished Equipment (GFE) that has been properly configured for security by CDC’s Information Technology Services Office (ITSO). The Government's inability to provide GFE for telework shall preclude the use of telework but shall not constitute an excusable delay. The Government shall provide maintenance and technical support for GFE used by Teleworkers. A Teleworker's use of GFE and government information shall be for contractual performance only, and shall be protected from unauthorized access, disclosure, sharing, transmission, or loss. Teleworkers shall comply with CDC Policy No. CDCGA- 2005-02, "Use of CDC Information Technology Resources” (see http://aops-masiis.cdc.gov/Policy/Doc/policy90.pdf ).

All GFE used for telework shall be removed from and returned to CDC facilities in accordance with CDC Policy CDC-MM-2005-01 "Controls for Government Property and Guidance on Removing Government Property from CDC Facilities" ( see http:// aops-mas-iis.od.cdc.gov/Policy/Doc/policy480.htm ). Prior to removing GFE from CDC facilities, Teleworkers shall obtain written approval from the CDC Property Custodian. Teleworkers shall return all GFE to the CDC Property Custodian when he/she separates from the Contract or ceases to telework.

Teleworkers shall exercise due care in transporting and storing non-public information, to ensure it is safeguarded.

Controlled unclassified information – formerly called sensitive but unclassified (SBU)…