NCATS Collaborative Platform SOW.pdf

Statement of Work NCATS Collaborative Scientific Platform Pilot Continuation

Solicitation No. 75N95020P00014

1. Background and Objective

The NCATS Collaborative Scientific Platform (NCSP) is an NCATS-sponsored cloud-based system that provides a collaborative platform-as-a-service for NIH collaborators to manage and work with large amounts of complex, cutting-edge data. Collaborators include institutes and centers at NIH as well as external partners such as research hospitals, academic institutions, and industry stakeholders.

2. Requirements

2.1. Independently and not as an agent of the Government, the Contractor shall furnish all the necessary services, qualified personnel, material, equipment, and facilities, not otherwise provided by the Government, as needed to perform the following.

2.2. In accordance with the software requirements described below and in accordance with the Detailed Technical Specifications included therein, the Contractor shall provide a term license for the NCATS Collaborative Scientific Platform—Base Platform License to support the following users:

• 2019 NCATS Scientific Computing Platform: 125 users

• 2019 PEPFAR Base Platform: pilot users

For purposes of this contract, a “user” is defined as one named authorized user account, which may not be transferred, assigned to, or used by any other user who is not the named user. “NCATS Collaborators” are defined as organizations (e.g., research teams at other institutes and centers at NIH, universities, medical centers, small businesses and industry, patient groups and advocacy organizations, etc.) supported through an NCATS-sponsored initiative or program (e.g., CAN, CTSA), or performing a joint research project with NCATS utilizing data generated relative to the collaborative engagement. The President’s Emergency Program for AIDS Relief (PEPFAR) is a collaborator conducting a joint translational data research project with NCATS.

1. User access shall include:

• Installation;

• Implementation;

• System configuration;

• Mutually agreed-upon training; and

• Operations and maintenance.

2. User access does not include:

• A configuration for raw image management and processing;

• Other direct costs; and

• User-specific configurations unless mutually agreed-upon.

Solicitation No. 75N95020R00014

2.3. Software Requirements

The contractor shall provide its commercial software for enterprise data integration and management to meet the following requirements:

a. A commercial software solution deployable on day one of the project and that can be configured within expedited timelines. Respondents must possess FedRAMP authorization so that an agency ATO can be granted upon award of a contract.

b. An open data architecture, where data always remains under the full control of NCATS and can be easily exported in open, non-proprietary data formats via open APIs. The software should be built on an open, distributed microservices architecture with open, well-documented REST APIs that are designed to seamlessly interface with other systems, adapt to meet evolving needs, and avoid system lock-in.

c. Proven data integration capabilities, including the ability to rapidly ingest unprocessed high-throughput drug screening (HTS) outputs, genomic data (including DNA sequencing, RNA-Seq, miRNA, etc.), mass spectrometry, flow cytometry, and other data types used in basic and translational biosciences research.

d. The ability to maintain data and scientific provenance and reproducibility of all integrated data sources where every resource (dataset, analysis, code, plot, report) contains provenance, metadata, and can be both traced back to the exact version of all upstream dependencies, and where the dependency tree can be easily replayed given new data or updated analysis logic, while still retaining prior versions and branches.

e. Dynamic data model, object-based search/discoverability and analysis workflows, allowing easy definition of objects, properties, and links that propagate from a source table, and provide natural ways to move between tabular and object-oriented interfaces and data analyses.

f. Intuitive, highly configurable user interfaces that have been effectively utilized by technical bioinformaticians, cheminformaticians, and data scientists, as well as less technical biologists, chemists, and other scientists.

g. Ability to perform advanced analytics and informatics in a user's preferred coding language, as well as in non-code-based point and click tools, all within the same environment.

h. Collaboration capabilities enabling teams comprising of a range of technical and less technical roles to work seamlessly and concurrently on the same data, build on insights, merge similar analytical paths, and track progress in one place.

i. Ability to scale flexibly with increasing users, data, and pipeline complexity, while providing fine-grained ways to adjust resource consumption. Proven ability to scale up to thousands of users (including thousands of potential outside collaborators globally), petabytes of raw and processed data, daily updates in the terabytes, and complex

Solicitation No. 75N95020R00014 bioinformatic pipelines requiring processing components developed in a variety of languages and environments.

j. Proven granular, security controls with the ability for data owners to easily control all downstream uses of the originating data, and the ability to conform to NCATS security policies.

k. Proven interoperability with NCATS current IT investment landscape, and includes omnipresent APIs and plugin points that allow the system to keep up with the changing needs of NCATS, and support both third-party software and other analytic applications. NCATS also requires the ability to independently develop new configurations, plugins, integrations, and extensions to meet new and unforeseen needs and interface with external systems.

l. Adherence to Detailed Technical Specifications: the solution shall incorporate the specifications listed in the Detailed Technical Specifications document, attached to this SOW.

3. Attachments

Attachment 1, Detailed Technical Specifications