SSJ_pilot_interim_Redacted.pdf
PDF 7 MB Posted
- Attached to
- NCATS Collaborative Scientific Platform as a Service Pilot Continuation Federal contract opportunity
- Solicitation number
- 75N95020R00014
View the file
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Justification and Approval for Sole Source
"Source Selection Information - see FAR 2.101 and 3.104"
1. Identification of the agency and contracting activity.
a. Federal agency and contracting activity.
Department of Health and Human Services National Institutes of Health National Institute on Drug Abuse, Office of Acquisition
b. Sponsoring organization.
Department of Health and Human Services National Institutes of Health National Center for Advancing Translational Sciences
c. Project Officer information.
Sam Michael CIO and Chief, Information Technology Resources Branch (ITRB) National Center for Advancing Translational Sciences 9800 Medical Center Drive Rockville, MD 20850
2. Nature and/or description of the action being approved.
a. Acquisition purpose and objectives.
The National Center for Advancing Translational Sciences (NCATS) intends to award a contract to the incumbent contractor to continue work on a pilot program while a follow-on contract is negotiated.
b. Contractual background
The NCA TS Collaborative Scientific Platform-as-a-Service (the "Platform") is a specialized cloud-based software platform that can integrate, manage, secure, and analyze any kind of scientific data, and provide secure, controlled access to internal and external collaborators.
NCATS awarded IDIQ contract no. HHSN271201800020I to Palantir, Inc.
on 8/31/2018 to support a pilot effort of the Platform. A single contract was awarded following full and open competition in which multiple proposals were received. The Government used simplified acquisition
Branch. NCATS determined that only the incumbent meets the requirements.
The assessment of the capability statements is attached as attachment #3.
Statements were received from:
11. Statement of the actions, if any, the agency may take to remove or overcome any barriers to competition before any subsequent acquisition for the required supplies or services.
NCATS has begun the acquisition planning for full implantation of the pilot, titled the NCATS Translational Research Computational Platform (NCATS TRCP). The TRCP will be a longer-term contract negotiated using FAR Part 15 procedures.
Award of this contract is expected in FY20. Additional market research will include additional notices in Contract Opportunities (beta.sam.gov), review of capability statements, and surveys of the open market (to include academic and research institution efforts).
In addition, NCATS has taken measures throughout this engagement to prevent contractor technical lock-in, including:
• The project must use 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 well-documented application programming interfaces (APls) that are open to NCATS programmers. The contractor is required to be able to export all existing data in non-proprietary raw format and in the format best usable for destination systems.
• NCATS requires proven interoperability with NCATS' current IT investment landscape, with omnipresent APls 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 requires the ability to independently develop new configurations, plugins, integrations, and extensions to meet new and unforeseen needs and interface with external systems.
• NCATS requires the ability to maintain data and scientific provenance and reproducibility of all integrated data sources. Every resource (dataset, analysis, code, plot, report) contains provenance metadata, and can be traced back to the exact version of all upstream dependencies. The dependency tree can be easily replayed given new data or updated analysis logic, while still retaining prior versions and branches.
• The contract maintains intellectual property boundaries. The base Palantir platform is a commercial product governed by a commercial software license.
Programming performed by NCATS remains the property of NCATS.
12. Program office certification.
1. Background and Objective
J&A Attachment no. 1 - Existing Contract
Statement of Work
NCATS Collaborative Scientific Platform
Contract No. HHSN271201800020I
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. The NCSP is established through an indefinite delivery, indefinite quantity contract, with task orders issued to support the requirements of individual groups.
2. Requirements
Upon issuance of a task order, Palantir Technologies Inc. (Contractor) shall provide its commercial software for enterprise data integration and management, the Palantir Gotham Platform for Enterprise
Data Management ("Palantir"), 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.
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 APls. The software should be built on an open, distributed microservices architecture with open, well documented REST APls 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.
Contract No. HHSN2712018000201
Services (AWS) Cloud hosting infrastructure and/or hardware for the specified configuration. ODCs will be priced at the order level dependent upon the configuration and needs.
Items 0006, 0007, and 0008: Professional Services. These items for professional services provide additional flexibility to meet potential needs/requirements under specific orders as they may arise over the life of the vehicle.
For the purposes of the pricing contained herein, 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. Use of Palantir Technologies, Inc. software is subject to the Palantir License and Service
Agreement, attached.
4. Attachments
Attachment 1, Detailed Technical Specifications
Attachment 2, Palantir License and Service Agreement
Detailed Technical Specifications
Collaborative Scientific Platform as a Service
National Center for Advancing Translational Sciences
(NCATS)
National Institutes of Health
June 19, 2018
Table of Contents
Technical Solution Requirements
1. Solution Architecture, Data Integration, and Data Management
1.1 Unified, Commercial Software Data Management Architecture
1.3 Flexible Data Integration Engine & Bioscience Data Experience
1.4 Data Storage, Access, and Catalog
1.5 Full Data Provenance and Schema
1.6 Data Transformation Management
1.7 Data deposition back to established repositories
1.8 Cohesive User Interfaces for Data Management
2. Data Analysis, Discovery, and Bioscience Workflows
2.1 Analytic Tool Suite
2.2 Search and Exploration
2.3 Web Application Builder
3. Security and Administration
3.1 Security and Access Controls
3.2 Platform Management and Administration
3.3 End - nothing follows
c. Each widget can be synchronized to live data with straightforward SQL queries, and complex workflows can be built by defining JavaScript functions that determine interaction between widgets and reaction to user triggered events.
d. Is natively compatible with reading from a SQL connection, via REST API, or anything that provides a JSON response, offering the ability to tie in external systems or APls.
2. As all other solution components, applications built in this web interface should fully respect the propagated dynamic access controls of the data dependencies.
3. Security and Administration
3.1 Security and Access Controls
1. The solution shall have a security and auditing subsystem to enforce security in the solution. The solution must provide authorization of resource access to users who have been authenticated.
2. Security and access controls that include:
a. Multi-source authentication (enterprise LDAP, PKI, Active Directory, etc.) as well as Single Sign-On (SSO) capabilities.
b. Access controls to secure each piece of information individually in addition to traditional blanket permissions across entire data sources.
c. Ability to assign individual users granular permissions to data access (including ownership, read, write, access denied, etc.).
d. Role-based access controls (RBAC) are assignable to individual users or group of users.
e. Allow for conditional policies based upon defined criteria. For example, applications and individual actions (termed "resources") can each be given a policy, taking the form of statements that express a (Condition, Verb, Operation) tuple, such as "if User Xis a member of Group Y (condition) they are Allowed
(verb) to Edit (operation) resource Z."
f. Access and role-based access controls that can be:
1. assigned by administrators and/or
2. inherited from source systems and updated at any time.
3. Role-based access control based on least privilege and privileged access for access administration.
g. Propagation and inheritance of access controls to all data and analyses derived directly or indirectly from the originating data, whether those data transformation or analyses are performed:
1. In a standard coding language (Java, SQL, Scala, Python, etc.)
2. As technical scripting language (R, SAS, etc.), or
3. A point-and-click analytical environment
h. Data is encrypted at rest via compliant mechanisms (e.g., full disk encryption, LUKS, TrueCrypt).
d. These containers allow only a limited number of gateways into the host environment, greatly limiting the potential vectors that could compromise one or more hosts.
3.3 End - nothing follows.
mutual agreement and shall be effective only if made in writing and signed by each party. No waiver of any breach shall be deemed a waiver of any subsequent breach. Unless otherwise specified by Palantir, the Products, Documentation, and Support Services provided hereunder are subject to U.S. trade controls and sanctions and may only be further exported or transferred in accordance with applicable export and sanctions requirements, including consultation of the U.S. Consolidated Screening List. It is
Customer's responsibility to provide Palantir with the necessary information for Palantir to comply with applicable requirements, and to ensure that all end-uses and end-users relating to Customer's reexports and retransfers of the Products, Documentation, and Support Services comply with applicable controls. Palantir is in no way affiliated with, or endorsed or sponsored by, The Saul Zaentz Company d.b.a. Tolkien Enterprises or the Estate of J.R.R. Tolkien.
Page6
File details come from the government source that posted it. Updated .