Product Description RFI.docx

Health and Data Analytics Data Platform Request For Information

PRODUCT DESCRIPTION (PD)

DEPARTMENT OF VETERANS AFFAIRS

REQUEST FOR INFORMATION (RFI)

Office of Information & Technology (OIT) Brand Name or equivalent Alteryx (formerly known as Trifacta) Health and Data Analytics Data Platform (HDAP) End User Data Curation and Preparation Tool Replacement

VA-24-00014246

PD Version Number: 1.0

This RFI is for planning purposes only and shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation, or a Request for Proposal. Additionally, there is no obligation on the part of the Government to acquire any products or services described in this RFI. Your response to this RFI will be treated only as information for the Government to consider. You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract.

Contents

PRODUCT REQUIREMENTS

Veterans Affairs (VA) Office of Information and Technology (OIT), Summit Data Platform (SDP) has a requirement to procure Brand Name or equivalent Alteryx (formerly known as (fka) Trifacta) software licenses for a low-code/no-code cloud based Commercial Off the Shelf (COTS) Data Curation Product to meet VA requirements. SDP is a cloud-based data analytics platform comprised of Cloud Service Provider (CSP) and supports VA’s data & analytics community. SDP is an established data lake environment where storage and compute components are separated to ensure scalability. The solution will enable VA to organize its data to create models for machine learning (ML) and Artificial Intelligence (AI), and provide the ability to quickly assess, aggregate and analyze data patterns, clean and transform data from large to multiple datasets, store configurable complex workflows, improve data visualization and geographical modeling. The solution will also allow VA to configure data validation rules, and data quality assessments to ensure consistency and quality of enterprise data.

VA also requires the following:

· Product Support: An annual subscription that provides Brand Name or equivalent Alteryx product support contact, enhanced service level agreement, and regularly scheduled support status reviews.

· Incidental Services/Support up to 300 hours within a twelve (12)-month licensing period.

The period of performance shall be from date of award for a 12-month base period, and two (2) 12-month option periods.

Brand Name or equivalent Alteryx fka Trifacta Qty/Unit (12 Months)

Base Year

Brand Name or equivalent Alteryx fka Trifacta Qty/Unit (12 Months)

Option Year 1

Brand Name or equivalent Alteryx fka Trifacta Qty/Unit (12 Months)

Option Year 2

SALIENT CHARACTERISTICS

The purchase of the Alteryx (brand name or equivalent) product licenses must meet the following requirements:

For highly complex transformation logic not supported by a no-code method in the GUI, the product shall support insertion of the transformation logics written in (a) Structured Query Language (SQL), (b) Python, (c) R, (d) Java, (e) Scala (f) JSON, or (g) Other non- proprietary, open-source, freely available, industry-standard language. Example of highly complex transformation logic: k-NN, multivariate imputation by chained equation (MICE), deep learning (Data wig, etc.), semi-supervised human-in- the-loop, multiple imputation, stochastic regression, extrapolation, and interpolation, and/or others).

Versioning & Effective Collaboration

CE-113

The product shall provide the functionality to create, update, and debug transformation logic within the product.

Versioning & Effective Collaboration

CE-114

The product shall enable an end user to collaborate on data curation/enrichment activities with other end users via VA’s GitHub repository.

The product shall enable users to add comments and annotations to any values or columns in the table. (For example, if a SME user does not think RxNorm-123 should be excluded from the value set, he/she can annotate this as a comment or in a user-added column).

The product shall provide a built-in workflow management engine that allows users to configure approval workflow for transformation logic without writing custom code. This capability shall enforce approval processes are followed before the changes are published.

User Experience

CE-118

When the product returns the data transformation logic according to users' search, the transformation logics name, approval status, author, and time stamp shall be included in the search results.

User Experience

CE-119

The product shall provide assistance using recommendations, tool tips or automated drop downs to help the data stewards resolve anomalies identified during data quality assessment.

The GUI shall be able to display the data descriptions, such as number of rows and columns, before and after a transformation.

User Experience

The GUI shall be able to display the entire transformation linage, which may include hundreds of transformation steps. Furthermore, the GUI shall support user interactively zoom in/out to a particular subset of transformation steps in the linage.

Working with Metadata

CE-128

The product shall allow import/export of metadata in portable industry-standard machine-processable form (either JSON, JSON-LD, XML, RDF, or other open industry standard)

Working with Metadata

CE-129

The product shall enable metadata enrichment and integration with external metadata sources using industry standard.

Working with Metadata

CE-130

The product shall support search of datasets based on metadata in the GUI.

Working with Metadata

Working with Metadata

CE-132

The product shall allow users to share search results in portable industry standard format (CSV, JSON, XML, XLS, etc.)

Working with Metadata

Monitoring, alerting, auditing and usage insights

Monitoring, alerting, auditing and usage insights

Monitoring, alerting, auditing and usage insights

Monitoring, alerting, auditing and usage insights

Monitoring, alerting, auditing and usage insights

Working with multiple data sets

Working with multiple data sets

Dashboards and Reports

Dashboards and Reports

Dashboards and Reports

(https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentS erver.aspx?DocumentId=4525852&FileName=36C10B18R2609-004.pdf )

Deployment

DR-02

The product shall integrate with VAEC Azure identity and access management services.

Deployment

Deployment

Deployment

Deployment

Security

Security

Security

Platform as a Service (PaaS)

The product shall provide a PaaS deployment option.

Federal Risk and Authorization Management Program (FedRAMP) Certified

The product shall be FedRAMP certified, if it only provides a Software as a Service (SaaS) option.

NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) PROCUREMENTS (SECTION 508) On January 18, 2017, the Architectural and Transportation Barriers Compliance Board (Access Board) revised and updated, in a single rulemaking, standards for electronic and information technology developed, procured, maintained, or used by Federal agencies covered by Section 508 of the Rehabilitation Act of 1973, as well as our guidelines for telecommunications equipment and customer premises equipment covered by Section 255 of the Communications Act of 1934. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) STANDARDS

The Section 508 standards established by the Access Board are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure ICT. These standards are found in their entirety at: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines. A printed copy of the standards will be supplied upon request.

Federal agencies must comply with the updated Section 508 Standards beginning on January 18, 2018. The Final Rule as published in the Federal Register is available from the Access Board: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule.

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

COMPATABILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery. The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

INFORMATION TECHNOLOGY USING ENERGY-EFFICIENT PRODUCTS

EPEAT

EPEAT product compliance is not required in this acquisition. There are no EPEAT standard required for the Brand Name or equivalent Alteryx (formerly known as Trifacta) Health and Data Analytics Data Platform (HDAP) End User Data Curation and Preparation Tool Replacement. For information about EPEAT®, see www.EPEAT.net.

ENERGY STAR

Energy Star compliance products for the Brand Name or equivalent Alteryx (formerly known as Trifacta) Health and Data Analytics Data Platform (HDAP) End User Data Curation and Preparation Tool Replacement effort is not required in this acquisition. The complete listing of Energy Star categories and associated products can be found at https://www.energystar.gov/products

FEMP

FEMP or FEMP low standby power products for the Brand Name or equivalent Alteryx (formerly known as Trifacta) Health and Data Analytics Data Platform (HDAP) End User Data Curation and Preparation Tool Replacement effort is not required and not included in this acquisition. The complete listing of FEMP product categories can be found at https://www.energy.gov/eere/femp/search-energy-efficient-products

4.0 Shipment of sotware equiptment

Electronic Delivery:

Primary

Alternate

Address:

Address:

Voice:

Voice:

5.0 GENERAL REQUIREMENTS

5.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (VA TRM). The VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. Moreover, the VA TRM, which includes the Standards Profile and Product List, serves as a technology roadmap and tool for supporting OIT. Architecture & Engineering Services (AES) has overall responsibility for the VA TRM.

5.2 SOCIAL SECURITY NUMBER (SSN) REDUCTION

The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the Integrated Control Number (ICN) in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA Master Person Index (MPI) for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA.

5.3 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support Internet Protocol Version 6 (IPv6) based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). IPv6 technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices shall support native IPv6 and dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g. web, email, DNS, ISP services, etc.) shall support native IPv6 and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and dual stack (IPv6 / IPv4) operations.

5.4 SOFTWARE AND LICENSING REQUIREMENTS

The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.

6.0 INFORMATION SECURITY CONSIDERATIONS

The Assessment and Authorization (A&A) requirements do not apply and a Security Accreditation Package is not required

All VA sensitive information shall be protected at all times in accordance with local security field office System Security Plans (SSP’s) and Authority to Operate (ATO)’s for all systems/LAN’s accessed while performing the tasks detailed in this Product Description.

7.0 POINTS OF CONTACT

VA Program Manager:

Contracting Officer’s Representative:

Contracting Officer:

Contract Specialist:

Page Intentionally Left Blank ****Please proceed to clause on Pg 17-18

8.0 SDVOSB SET-ASIDE CONFIRMATION CLAUSE FAR 852.219-75

852.219-75 VA Notice of Limitations on Subcontracting—Certificate of Compliance for Services and Construction.

As prescribed in 819.7011(b), insert the following clause:

VA NOTICE OF LIMITATIONS ON SUBCONTRACTING—CERTIFICATE OF COMPLIANCE FOR SERVICES AND CONSTRUCTION (JAN 2023) (DEVIATION)

(a) Pursuant to 38 U.S.C. 8127(l)(2), the offeror certifies that—

(1) If awarded a contract (see FAR 2.101 definition), it will comply with the limitations on subcontracting requirement as provided in the solicitation and the resultant contract, as follows: [Contracting Officer check the appropriate box below based on the predominant NAICS code assigned to the instant acquisition as set forth in FAR 19.102.]

(i) [ ] Services. In the case of a contract for services (except construction), the contractor will not pay more than 50% of the amount paid by the government to it to firms that are not certified SDVOSBs listed in the SBA certification database as set forth in 852.219-73 or certified VOSBs listed in the SBA certification database as set forth in 852.219-74. Any work that a similarly situated certified SDVOSB/VOSB subcontractor further subcontracts will count towards the 50% subcontract amount that cannot be exceeded. Other direct costs may be excluded to the extent they are not the principal purpose of the acquisition and small business concerns do not provide the service as set forth in 13 CFR 125.6.

(ii) [ ] General construction. In the case of a contract for general construction, the contractor will not pay more than 85% of the amount paid by the government to it to firms that are not certified SDVOSBs listed in the SBA certification database as set forth in 852.219-73 or certified VOSBs listed in the SBA certification database as set forth in 852.219-74. Any work that a similarly situated certified SDBOSB/VOSB subcontractor further subcontracts will count towards the 85% subcontract amount that cannot be exceeded. Cost of materials are excluded and not considered to be subcontracted.

(iii) [ ] Special trade construction contractors. In the case of a contract for special trade contractors, the contractor will not pay more than 75% of the amount paid by the government to it to firms that are not certified SDVOSBs listed in the SBA certification database as set forth in 852.219-73 or certified VOSBs listed in the SBA certification database as set forth in 852.219-74. Any work that a similarly situated certified SDBOSB/VOSB subcontractor further subcontracts will count towards the 75% subcontract amount that cannot be exceeded. Cost of materials are excluded and not considered to be subcontracted.

(2) The offeror acknowledges that this certification concerns a matter within the jurisdiction of an Agency of the United States. The offeror further acknowledges that this certification is subject to Title 18, United States Code, Section 1001, and, as such, a false, fictitious, or fraudulent certification may render the offeror subject to criminal, civil, or administrative penalties, including prosecution.

(3) If VA determines that an SDVOSB/VOSB awarded a contract pursuant to 38 U.S.C. 8127 did not act in good faith, such SDVOSB/VOSB shall be subject to any or all of the following:

(i) Referral to the VA Suspension and Debarment Committee;

(ii) A fine under section 16(g)(1) of the Small Business Act (15 U.S.C. 645(g)(1)); and

(iii) Prosecution for violating 18 U.S.C. 1001.

(b) The offeror represents and understands that by submission of its offer and award of a contract it may be required to provide copies of documents or records to VA that VA may review to determine whether the offeror complied with the limitations on subcontracting requirement specified in the contract. Contracting officers may, at their discretion, require the contractor to demonstrate its compliance with the limitations on subcontracting at any time during performance and upon completion of a contract if the information regarding such compliance is not already available to the contracting officer. Evidence of compliance includes, but is not limited to, invoices, copies of subcontracts, or a list of the value of tasks performed.

(c) The offeror further agrees to cooperate fully and make available any documents or records as may be required to enable VA to determine compliance with the limitations on subcontracting requirement. The offeror understands that failure to provide documents as requested by VA may result in remedial action as the Government deems appropriate.

(d) Offeror completed certification/fill-in required. The formal certification must be completed, signed and returned with the offeror’s bid, quotation, or proposal. The Government will not consider offers for award from offerors that do not provide the certification, and all such responses will be deemed ineligible for evaluation and award.

Certification:

I hereby certify that if awarded the contract, [insert name of offeror] will comply with the limitations on subcontracting specified in this clause and in the resultant contract. I further certify that I am authorized to execute this certification on behalf of [insert name of offeror].

Printed Name of Signee: ________________________________________

Printed Title of Signee: _________________________________________

Signature: ___________________________________________________

Date: _____________________

Company Name and Address: ______________________________________

(End of clause)

Product Description Template_JUL_21_2021 image1.jpeg