NBIC RRBS draft SOW_Posted 3.02.2021.pdf

Draf t i

DEPARTMENT OF HOMELAND SECURITY (DHS)

STATEMENT OF WORK (SOW)

FOR

RAPID RESPONSE BIOSURVEILLANCE DATA SUBSCRIPTION

TABLE OF CONTENTS

1 GENERAL

1.1 BACKGROUND

1.2 OBJECTIVE

2 PERFORMANCE REQUIREMENTS SUMMARY

2.1 TASK ONE: Dataset Requirements

2.1.1 Emergency Medical Systems (EMS) Data

2.1.2 Meta Data Availability

2.1.3 Data Provenance

2.1.4 Temporal Resolution

2.1.5 Geographic Resolution

2.1.6 Human Population

2.2 TASK TWO: Application Programming Interface (API)

2.2.1 API Data Elements

2.2.2 Data Format

2.2.3 Data Retention

2.2.4 Data Access

2.2.5 Downtime

2.2.6 Training

3 OTHER APPLICABLE CONDITIONS

3.1 SECURITY

3.2 PERIOD OF PERFORMANCE

3.3 PLACE OF PERFORMANCE

3.4 POST AWARD CONFERENCE

3.5 PROJECT PLAN

3.6 BUSINESS CONTINUITY PLAN

3.6.1 Disruption of Operations

3.6.2 Emergency Circumstance Response

3.7 SYSTEM USE and TECHNICAL ISSUES REPORTS

3.8 MEETINGS

3.9 GENERAL REPORT REQUIREMENTS

3.10 PROTECTION OF INFORMATION

3.10.1 Privacy Compliance

3.10.2 HIPAA Compliance

3.10.3 Safeguarding Sensitive Information

3.11 SECTION 508 COMPLIANCE

3.11.1 Section 508 Requirements for Technology

3.11.2 Exceptions

ii

3.12 CONTRACTOR PRIMARY POINTS OF CONTACT

3.12.1 Program Manager/Technical POC (Key Personnel)

3.12.2 Operational Manager (Key Personnel)

3.12.3 Contract/Financial POC

3.12.4 Key Personnel Substitution:

3.12.5 Non‐Personal Services

3.13 INVOICES

4 GOVERNMENT TERMS & DEFINITIONS

5 GOVERNMENT FURNISHED RESOURCES

6 CONTRACTOR FURNISHED PROPERTY

7 GOVERNMENT ACCEPTANCE PERIOD

7.1 COR Deficiencies Rights

7.2 COR Review

7.3 Other Review Timetables

8 DELIVERABLES

LIST OF TABLES

Table 1: Required and Preferred National EMS Information System (NEMSIS) data elements and attributes. 2 Table 2: Deliverables Schedule

LIST OF FIGURES

No table of figures entries found.

DEPARTMENT OF HOMELAND SECURITY (DHS)

STATEMENT OF WORK (SOW)

FOR

RAPID RESPONSE BIOSURVEILLANCE DATA SUBSCRIPTION

1 GENERAL

1.1 BACKGROUND

The Countering Weapons of Mass Destruction (CWMD) Office serves as the Department of Homeland Security’s principal authority for countering attempts by terrorists and other threat actors to carry out an attack against the United States or its interests using a weapon of mass destruction. DHS CWMD works to prevent, protect against, and respond to a full spectrum of WMD threats to the Homeland including chemical, radiological, nuclear, and biological.

The Information and Analysis Directorate (IAD) within CWMD consolidates the mutually supportive information analysis related functions within CWMD. IAD works to understand and anticipate Weapons of Mass Destruction (WMD) and medical/health‐related threats to the Homeland and to equip DHS Components and Federal/state/local/territorial/tribal (FSLTT) first responders with timely and relevant information to help maintain technological advantage, mitigate vulnerabilities, and respond to and disrupt WMD threats.

The National Biosurveillance Integration Center (NBIC) organizationally falls within CWMD/IAD and conducts biosurveillance activities to enable early warning and situational awareness of acute biological events and supports better decisions through rapid identification, characterization, localization, and tracking. The objective of NBIC is to advance the safety, security, and resilience of the Nation by leading an integrated biosurveillance effort in support of Federal, state, and local stakeholders.

1.2 OBJECTIVE

NBIC seeks a nation‐wide dataset (i.e., a data subscription) providing de‐identified early medical data. The exact data elements required are listed in Table 1. The prehospital human‐health‐care data will allow CWMD to carry out analytics and visualizations that will improve CWMD’s capability for biological threat awareness, detection, and information sharing to respond to incidents that may cascade into a nationally significant event. The dataset will allow analysts across DHS CWMD to perform independently defined, flexible geo‐temporal medical syndrome trend and anomaly detection analyses within regular, repeatable, operationally relevant timeframes of hours or days versus weeks or months. The contractor’s dataset shall therefore provide geographic, temporal, population, and medical data breadth and specificity. The contractor shall allow CWMD end users maximum flexibility in defining adjustable binning and querying options to include independently defining medical events and syndromes as well as using predefined syndromes.

2 PERFORMANCE REQUIREMENTS SUMMARY

The contractor shall furnish CWMD biosurveillance data through ten individual and application accesses to its Biospatial Syndromes Web Application, Biosurveillance Tier (SYN‐WEB‐BIO); Biospatial Syndromes Web Application, Opioid Tier (SYN‐WEB‐OPI); Biospatial Biosurveillance API (SYN‐API‐BIO); and Biospatial Opioid

API (SYN‐API‐OPI).

The Performance Requirements Summary (PRS) plays an integral role in the administration of the contract.

In addition to any applicable inspection clauses or other related terms and conditions contained in the contract, the PRS shall serve as a primary tool for inspection and acceptance of the subscription service and associated dataset as facilitated by the Contracting Officer’s Representative (COR). Evaluation of the contractor’s overall performance shall be in accordance with the performance standards set forth in the PRS and will be conducted by the COR. The PRS constitutes a material aspect of the contract and will not be changed or otherwise modified without prior written approval of the Contracting Officer.

2.1 TASK ONE: DATASET REQUIREMENTS

The contractor shall provide CWMD dynamic and static nation‐wide pre‐hospital anonymized human health care dataset that complies with federal health, privacy, and security protections as well as DHS Information Technology requirements in these areas and others.

2.1.1 Emergency Medical Systems (EMS) Data

Table 1 describes the required and preferred National EMS Information System (NEMSIS) or NEMSIS‐derived data elements and attributes.

Table 1: Required and Preferred National EMS Information System (NEMSIS) data elements and attributes.

Data Element Required Attributes Preferred Attributes

Situation: Chief Complaint Anatomic Location Primary Symptom Injury Provider's Primary Impression Provider's Secondary Impressions Initial Patient Acuity

Chief Complaint Organ System

Injury: Cause of Injury

Arrest: Cardiac Arrest Etiology

Outcome: None Hospital Diagnosis

Medications: Medication Given

Exam: Mental Status Assessment Neurological Assessment

Data Element Required Attributes Preferred Attributes

Patient: Age Age Units Race Gender

Scene: Mass Casualty Incident Incident State Incident County Incident City

Incident Zip Code

Facility: Type of Facility Facility State

Facility County Facility ZIP Code

Time: Event time derived from one of the following:

Public Safety Answering Point Call Date/Time Arrived at Patient Date/Time Patient Arrived at Destination Date/Time

Disposition: Destination State Destination County Incident/Patient Disposition EMS Transport Method Type of Destination

2.1.1.1 Age Data.

Age data shall allow for distinction between pediatric (17 years or younger), adult (18 years or older), and elderly populations (55 years or older).

2.1.1.2 EMS Data Coverage.

• The contractor shall provide data from at least 20 of the 50 states of the United States and the District of Columbia, to include at least 45% of the US population, with geospatial resolution at the county‐level.

• At least 70% of EMS data elements shall be updated within 24 hours of the first responder or health care encounter; available within the system interface and API dynamically; and available to download statically based on a query based on a given time span.

2.1.2 Meta Data Availability.

Contractor meta data shall be included and provided as structured data sets that users can determine dynamically and export for analytic use. The meta data used to assess data availability shall include when and where EMS data was:

• available and above a de‐identification masking case count threshold (e.g., 10 cases in a county in a specified time period), including the number of cases

• available and below a de‐identification masking case count threshold (e.g., 1 to 9 cases in a county in a specified time period)

• available and nothing found (e.g. no cases within a county in a specified time period)

• not available (e.g., the system does not contain any EMS data from that county during the specified time period).

Meta Data within a specified time span shall be available as quantitative structured data reflecting the number of cases as described above and having time units of at least a week within a user‐specified time span (e.g., by week over a multi‐month time span) and at county and state geographic levels. The user shall be able to retrieve data for multiple states or counties in a single query versus having to construct multiple queries for each county or state.

National and state choropleth map‐based visualizations of data availability at the county level shall also be provided.

2.1.3 Data Provenance.

Data provenance shall be provided through a list of executed partnerships with current original data owners at the start of the contract, and updates of the list as Data Use Agreements are entered, amended, or discontinued. The list shall include the name of the data owner, state or counties for which data is provided, date of agreement execution, date of signed data export authorization, start date of data export from data owner to contractor system, start date of continuous historical data integration into system, and stop date of data integration into the system.

2.1.4 Temporal Resolution.

Temporal resolution shall be provided at daily, weekly, monthly, and annual intervals at a minimum and CWMD analysts shall be able to select the time span and resolution used for queries (e.g. from any past date to any other past or current date in daily, weekly, monthly, or annual intervals).

2.1.5 Geographic Resolution.

Geographic resolution shall be provided at county and state levels and CWMD analysts shall be able to select multiple states or multiple counties within a state or across states to be used in queries.

2.1.6 Human Population.

Human population census data shall be included and used to calculate and provide medical event cases per population (i.e. incidence) at both county and state geographic levels based on CWMD analyst defined queries with adjustable event case, geographic area, and time span parameters. Documentation of which population census data source is currently and has been previously used will be provided to CMWD, preferably within the system and API.

2.2 TASK TWO: APPLICATION PROGRAMMING INTERFACE (API)

Representation State Transfer Application Programming Interface (REST API) and other data requirements

2.2.1 API Data Elements.

The contractor shall provide access to all the required data elements through a REST API.

• The REST API shall have proper authentication that verifies the credentials of the request.

• The REST API shall authorize programmatic connections only.

• The REST API shall accept credentials in the request headers only and shall not allow requests to send credentials in plain text. OAuth 2.0 or JSON Web Tokens (JWT) shall be implemented.

• The REST API shall return responses in JavaScript Object Notation (JSON).

• The REST API shall return success and error statuses. The error responses shall contain relevant information about the error and why the request failed.

2.2.2 Data Format.

Data formatted for analytic use. All data elements required shall be readily downloadable as JSON files and shall include the following minimum capabilities:

• The system and API data output shall provide the ability to define event counts based on any of the required data elements for anomaly detection analyses.

• The system and API shall allow users to create custom syndromes from the required data elements and shall include an Application specific data dictionary for advanced analytical interpretation.

• Inclusion of contractor‐defined syndromes with complete documentation of the syndrome definition, preferably within the system, is encouraged. Syndromes without completely documented definitions provide little added value.

• The system and API shall allow downloading of daily syndromic data at both the state and county level.

• The system and API shall provide the ability to organize and download multiple states’ and counties’ syndromic data simultaneously.

2.2.3 Data Retention.

System shall archive and retain data elements and attributes as described above and in accordance with data use agreements. The contractor shall not retain any DHS sensitive information in its information systems.

2.2.4 Data Access.

The contractor shall furnish access to authorized DHS users 24/7/365. In accordance with DHS Directive

103‐01, Enterprise Data Management Policy, data in the possession of DHS users is designated Enterprise

Data and is to be shared as required for support to NBIC enterprise missions and functions.

2.2.5 Downtime.

The contractor shall notify the DHS CWMD Contract Officer’s Representative at least 48 hours in advance of scheduled downtime and as soon as feasible following identification of unscheduled downtime.

2.2.6 Training.

The contractor shall provide training to CWMD staff on its system within 30 days of award. Training can be provided in person or via webinar.

Additional training shall be provided as needed with a two week notice from the government, and not to exceed four times per year, and can be conducted via webinar.

3 OTHER APPLICABLE CONDITIONS

3.1 SECURITY

Contractor access to classified information is not currently required under this SOW.

3.2 PERIOD OF PERFORMANCE

The period of performance for this contract is a one‐year base period with four (4) one‐year option periods:

Base Period: March 25, 2021 through March 24, 2022 Option Period #1: March 25, 2022 through March 24, 2023 Option Period #2: March 25, 2023 through March 24, 2024 Option Period #3: March 25, 2024 through March 24, 2025 Option Period #4: March 25, 2025 through March 24, 2026

The contract also includes FAR clause 52.217‐8, which permits the Government to require additional performance at the rates and terms specified in the contract. The clause may be exercised more than once, at the end of the base period or any option period and permits a combined maximum of six months of additional performance.

3.3 PLACE OF PERFORMANCE

The primary place of performance will be the Contractor’s facilities.

3.4 POST AWARD CONFERENCE

The Contractor shall attend a Post Award Conference with the Contracting Officer and the COR no later than 7 days after the date of award. The purpose of the Post Award Conference, which will be chaired by the Contracting Officer, is to discuss technical and contracting objectives of this contract and review the Contractor's draft project plan. The Post Award Conference will be held at the Government’s facility, located at 1120 Vermont Avenue Northwest, Washington, D.C. or via teleconference.

3.5 PROJECT PLAN

The Contractor shall provide a draft Project Plan at the Post Award Conference for Government review and comment. The Contractor shall provide a final Project Plan to the COR not later than 30 days after the Post Award Conference. The final Project Plan shall describe agreed upon training on the existing system and technical connection to a predictive analysis tool identified by CWMD.

3.6 BUSINESS CONTINUITY PLAN

The Contractor shall prepare and submit a Business Continuity Plan (BCP) to the Government. The BCP Plan shall be due 30 days after the date of award and will be updated on an annual basis. The BCP shall document Contractor plans and procedures to maintain support during an emergency, including natural disasters and acts of terrorism. The BCP, at a minimum, shall include the following:

• A description of the Contractor’s emergency management procedures and policy

• A description of how uninterrupted access to the system will be maintained during an emergency

• How the Contractor will communicate with the Government during emergencies

• A list of primary and alternate Contractor points of contact, each with primary and alternate:

o Telephone numbers o E‐mail addresses

3.6.1 Disruption of Operations.

When any disruption of normal, daily operations occurs, the Contractor and the COR shall promptly open an effective means of communication. The BCP shall be activated immediately after determining that an emergency has occurred, shall be operational within 12 hours of activation or as directed by the Government, and shall be sustainable until the emergency situation is resolved and normal conditions are restored, or the contract is terminated, whichever comes first.

3.6.2 Emergency Circumstance Response.

The Government and Contractor shall make use of the resources and tools available to continue contracted functions to the maximum extent possible under emergency circumstances.

The Contractor shall obtain approval from the Contracting Officer prior to incurring costs over and above those allowed for under the terms of this contract.

3.7 SYSTEM USE AND TECHNICAL ISSUES REPORTS

The contractor shall provide a monthly report to the Contracting Officer and COR via electronic mail. This report shall include any Contractor concerns or recommendations for the previous reporting period. In addition, the monthly report will provide user statistics (i.e. how often the system is accessed by individual DHS users) and system statistics (i.e. any interruptions, system speed, changes in data coverage.)

3.8 MEETINGS

The Contractor shall meet with the COR quarterly to present deliverables, discuss reports, and resolve emergent technical problems and issues. These meetings shall take place in person at the NBIC office or via teleconference.

3.9 GENERAL REPORT REQUIREMENTS

The Contractor shall provide all written reports in electronic format with read/write capability using applications that are compatible with DHS workstations (Windows XP and Microsoft Office Applications).

3.10 PROTECTION OF INFORMATION

Contractor access to sensitive information is required under this PRS. Such information includes that protected under the Privacy Act of 1974 and the Health Insurance Portability and Accountability Act of 1996 (HIPAA) as well as Federal Contract information and other sensitive information which the NBIC will be separately identify, should needs arise.

Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the law and Government policy and regulation.

The contractor shall implement role‐based access to data and shall limit user access to data in accordance with access authorizations.

3.10.1 Privacy Compliance.

The contractor shall comply with established personal information protection guidelines, specifications, and applicable legislation.

3.10.2 HIPAA Compliance.

The contractor shall safeguard electronic protected health information (ePHI) in its systems in accordance with the requirements of the HIPAA Security Rule.

The contractor shall provide CWMD access to only that data authorized for entities not covered under the rules defining HIPAA. CWMD will be permitted access to only de‐identified, aggregated data, and visualizations necessary to understand emerging biological, chemical, and radiological threats.

3.10.3 Safeguarding Sensitive Information.

The contractor shall safeguard information, not intended for public release, that is provided for or generated for the Government under a contract to develop or deliver a product or service to the Government in accordance with the requirements of FAR Clause 52.204‐21 Basic safeguarding of covered contractor system.

The contractor shall safeguard all other DHS sensitive information authorized by DHS to be held in contractor information systems in accordance with HSAR 3052.204‐70 Security requirements for unclassified information technology resources and HSAR 3052.204‐71 Contractor employee access.

3.11 SECTION 508 COMPLIANCE

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105‐220) (codified at 29 U.S.C. § 794d) requires that when Federal agencies develop, procure, maintain, or use information and communications technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public with disabilities must be afforded access to and use of information and data comparable to that of Federal employees and members of the public without disabilities.

All products, platforms and services delivered as part of this work statement that, by definition, are deemed ICT shall conform to the revised regulatory implementation of Section 508 Standards, which are located at 36 C.F.R. § 1194.1 & Appendix A, C & D, and available at https://www.gpo.gov/fdsys/pkg/CFR‐2017‐title36‐ vol3/pdf/CFR‐2017‐title36‐vol3‐part1194.pdf. In the revised regulation, ICT replaced the term electronic and information technology (EIT) used in the original 508 standards. ICT includes IT and other equipment.

Exceptions for this work statement have been determined by DHS and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the Contracting Officer and a determination will be made according to DHS Directive 139‐05, Office of Accessible Systems and Technology, dated November 12, 2018 and DHS Instruction 139‐05‐001, Managing the Accessible Systems and Technology Program, dated November 20, 2018, or any successor publication.

3.11.1 Section 508 Requirements for Technology

Section 508 applicability to Information and Communications Technology (ICT): Emergency Medical Data

Applicable Exception: Fundamental Alteration Authorization #: _____________

3.11.2 Exceptions

Exceptions for this work statement have been determined by DHS and only the exceptions described herein may be applied. Any request for additional exceptions shall be sent to the Contracting Officer and a determination will be made according to DHS Directive 139‐05, Office of Accessible Systems and Technology, dated November 12, 2018 and DHS Instruction 139‐05‐001, Managing the Accessible Systems and Technology Program, dated November 20, 2018, or any successor document.”

3.12 CONTRACTOR PRIMARY POINTS OF CONTACT

The contractor shall identify Key Personnel. Key personnel are those Contractor personnel considered to be essential to the performance of the program and may only be replaced with the approval of or direction by the COR, or CO, in accordance with the terms and conditions of Key Personnel Substitution.

3.12.1 Program Manager/Technical POC (Key Personnel).

Program Manager/Technical POC is designated as key personnel. The contractor shall name a Program Manager prior to the Post Award Conference. The Program Manager shall be responsible for the day to day operations and primary contact with Government.

3.12.2 Operational Manager (Key Personnel).

Operational Manager is designated as key personnel. The contractor shall name a Program Manager by the Post Award Conference. The Operational Manager shall be responsible as an immediate back‐up to the PM.

If for some reason the PM is not available during the 24/7/365 operations the Operation Manager will be available to address any programmatic operational issues.

3.12.3 Contract/Financial POC.

The Contract/Financial POC is NOT designated as Key Personnel. The Contract/Financial POC shall be responsible as an immediate back‐up to the PM for issue relating to contract administration, invoicing and information archiving. The Contract/Financial POC will be available during normal business hours, normally 8am to 5pm Monday through Friday excluding Federal holidays.

3.12.4 Key Personnel Substitution:

The Contractor shall notify the COR, or CO, prior to making any changes in Key Personnel. No changes in Key Personnel will be made unless the Contractor can demonstrate that the qualifications of prospective replacement personnel are equal to, or better than the qualifications of the Key Personnel being replaced.

Unless approved by the Contracting Officer, all proposed substitutes shall have qualifications equal to, or higher than the qualifications of the person to be replaced. The COR shall be notified in writing of any proposed substitution at least fifteen (15) calendar days, or thirty (30) calendar days if a security clearance is to be obtained, in advance of the proposed substitution. Such notification shall include:

A. an explanation of the circumstances necessitating the substitution;

B. a complete resume of the proposed substitute; and, C. any other information requested by the COR to enable him/her to determine whether or not the

Contractor is maintaining the same high quality of personnel that provided the partial basis for award.

The COR will evaluate such requests and promptly notify the Contractor of his/her approval or disapproval in writing. All disapprovals will require resubmission of another substitution within fifteen (15) calendar days by the Contractor.

The Government and the Contractor understand and agree that the professional support services delivered by the Contractor to the Government are non‐personal services. The parties also recognize and agree that no employer‐employee or master‐servant relationship exists or will exist between the Government and the Contractor. The Contractor and the Contractor’s employees are not employees of the Federal Government and are not eligible for entitlement and benefits given Federal employees.

3.12.5 Non‐Personal Services

Contractor personnel under this contract shall not (i) be placed in a position where there is an appearance that they are employed by a Federal Officer, or are under the supervision, direction, or evaluation of a Federal Officer, or (ii) be placed in a position of command, supervision, administration or control over Government personnel.

3.13 INVOICES

Invoices will be submitted on a monthly basis, i.e., one invoice approximately every thirty days. Invoices shall be paid in accordance with the Prompt Payment Act, i.e., thirty (30) calendar days following receipt of a proper invoice.

A. Invoices must be submitted to the address identified in the contract. An electronic copy of the invoice shall be submitted to the CO, the COR, and FIN‐SMB‐CWMDinvoices@uscg.mil. If it is determined that the amount billed is incorrect, the Contractor will be required to submit a revised invoice.

B. To constitute a proper invoice, each invoice must include the following information and/or documentation:

a. Contractor Name, address and main telephone number

b. Contractor Contract/Financial POC Name, email address and telephone number

c. Date of invoice and invoice number

d. Contract number and modification number, if applicable

e. Description of the supplies/services rendered (including hours incurred, the beginning and end date rendered, and billing rate, if applicable to the contract)

f. A schedule depicting the following information by contract: Amt. Invoiced Cumulative, Authorized, Balance This Period, Amt. Invoiced, Value of Contract

g. Name of the COR

h. Signature of authorized representative of the firm with the following invoice certification:

“The undersigned hereby certifies to the best of my knowledge and belief that the sum claimed under this contract is proper and due, and all the costs of contract performance have been paid, or to the extent allowed under the applicable payment clause, will be paid by the Contractor when due in the ordinary course of business; the work reflected by these costs has been performed, and amounts involved are consistent with the requirements of this contract.”

BY:

TITLE:

DATE:

4 GOVERNMENT TERMS & DEFINITIONS

API Application Programming Interface BCP Business Continuity Plan CBRN Chemical, Biological, Radiological and Nuclear CO Contracting Officer (Government Representative) COR Contracting Officer’s Representative (Government Representative) CWMD Countering Weapons of Mass Destruction DOA Date of Award DHS Department of Homeland Security EIT electronic and information technology EMS Emergency Medical Systems ePHI electronic protected health information FSLTT Federal/state/local/territorial/tribal IAD Information and Analysis Directorate ICT information and communications technology IT Information Technology JSON JavaScript Object Notation JWT JSON Web Tokens NBIC National Biosurveillance Integration Center NEMSIS National EMS Information System NIST National Institute of Standards and Technology PM Program Manager PRS Performance Requirements Summary REST API Representation State Transfer Application Programming Interface SYN‐API‐BIO Syndromes Web Application, Opioid Tier, Biospatial Biosurveillance API SYN‐API‐OPI Biospatial Opioid API SYN‐WEB‐BIO Syndromes Web Application, Biosurveillance Tier SYN‐WEB‐OPI Biospatial Syndromes Web Application, Opioid Tier WMD Weapons of Mass Destruction

5 GOVERNMENT FURNISHED RESOURCES

The Government will not furnish any resources to the Contractor in support of this contract.

6 CONTRACTOR FURNISHED PROPERTY

The Contractor shall furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract, except for the Government Furnished Resources specified in PRS 2.0.

7 GOVERNMENT ACCEPTANCE PERIOD

The COR will review deliverables prior to acceptance and provide the contractor with an e‐mail that provides documented reasons for non‐acceptance. If the deliverable is acceptable, the COR will send an e‐mail to the Contractor notifying it that the deliverable has been accepted.

7.1 COR DEFICIENCIES RIGHTS.

The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection. The Contractor may have an opportunity to correct the rejected deliverable and return it per delivery instructions.

7.2 COR REVIEW.

The COR will have seven (7) days to review deliverables and make comments. The Contractor shall have Seven (7) days to make corrections and redeliver.

7.3 OTHER REVIEW TIMETABLES.

All other review times and schedules for deliverables shall be agreed upon by the parties based on the final approved Project Plan. The Contractor shall be responsible for timely delivery to Government personnel in the agreed upon review chain, at each stage of the review. The Contractor shall work with personnel reviewing the deliverables to assure that the established schedule is maintained.

8 DELIVERABLES

The Contractor shall consider items in BOLD as having mandatory due dates. Items in italics are deliverables or events that must be reviewed and/or approved by the COR prior to proceeding to next deliverable or event in this SOW.

Table 2: Deliverables Schedule

ITEM

SOW

REFERENCE DELIVERABLE / EVENT DUE BY DISTRIBUTION

1 2 Subscription Access Within 7 days of

DOA

COR, Contracting Officer

2 3.4 Post Award Conference Within 7 days of

DOA

N/A

3 3.5, 3.6 Draft Contractor Project Plan Post Award Conference

COR, Contracting Officer

4 3.6 Final Contractor Project Plan Within 60 days after Date of Award

COR, Contracting Officer

5 3.6 Original Business Continuity Plan Within 30 days after Date of Award

COR, Contracting Officer

6 3.6 Updated Business Continuity Plan Annually (30 days prior to Date of Award anniversary) or 30 day after written request from CO or COR

COR, Contracting Officer

7 3.9 Progress Reports Monthly, the 15th of each month for previous month

COR, Contracting Officer