36C10B21F0068 - Final - TechAnax signed_Redacted.pdf

PAGE 1 OF 1. REQUISITION NO.

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NO. 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

a. NAME b. TELEPHONE NO. (No Collect Calls) 8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY CODE 10. THIS ACQUISITION IS UNRESTRICTED OR SET ASIDE: % FOR:

SMALL BUSINESS

HUBZONE SMALL HUBZONE S

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS TION UNLE

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ IFB RFP

15. DELIVER TO CODE 16. ADMINISTERED BY CODE

17a. CONTRACTOR/OFFEROR CODE FACILITY CODE 18a. PAYMENT WILL BE MADE BY CODE

TELEPHONE NO DUNS: DUNS+4:

PHONE: FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19. 20. 21. 22. 23. 24. 19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA ARE ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________ 29. AWARD OF CONTRACT: REF. ___________________________________ OFFER

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

DATED ________________________________. YOUR OFFER ON SOLICITATION

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION (REV. 2/2012)

PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS 49

NNG15SD24B See Block 31c. 36C10B21F0068 36C10B21Q0074

William Freer, Contract Specialist 732-795-1063

R DUE DATE/LOCA

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X 100

X

541519

150 Employees

N/A

See Delivery Schedule

Technology Acquisition Centergy q

23 Christopher Way p y Eatontown NJ 07724

TechAnax LLC 14000 Crown Court Suite 206 Woodbridge, VA 22193-1471 g , PHONE: FAX:

EPHONE NO UNSDD D078573154

Financial Services Center PO Box 149971 Austin TX 78714-8971

LIES/SERVICES QU

Rockies Data Curation and Enrichment Tool

Order Type: Firm-Fixed-Price

( y)

N ___________ ________________________________ ARD OF CONTRACT

SSET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

ME OF CONTRACTING OFFICER (TYPE OR PRINT)

Contracting Officer

NNG15SD24B - 36C10B21F0068

Table of Contents

SECTION A

A.1 SF 1449 SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

B.2 GOVERNING LAW

B.3 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:

B.4 DELIVERY SCHEDULE

B.5 PRODUCT DESCRIPTION

SECTION C - CONTRACT CLAUSES

C.1 NASA SEWP V RFQ INTRODUCTORY LANGUAGE

C.2 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

C.3 FAR 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR

INFORMATION SYSTEMS (JUN 2016)

C.4 52.217-7 Option for Increased Quantity-Separately Priced Line Item (Mar 1989) ... 45

C.5 52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)

C.6 VAAR 852.212-70 PROVISIONS AND CLAUSES APPLICABLE TO VA

ACQUISITION OF COMMERCIAL ITEMS (APR 2020)

C.7 852.219-74 LIMITATIONS ON SUBCONTRACTING—MONITORING AND

COMPLIANCE (JUL 2018) (DEVIATION)

C.8 VAAR 852.270-1 REPRESENTATIVES OF CONTRACTING OFFICERS (JAN 2008)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

1. Contract Administration: All contract administration matters will be handled by the following individuals:

a. CONTRACTOR: TechAnax, LLC

14000 Crown Court, Suite 206, Woodbridge, VA 22193-1471

b. GOVERNMENT: Contracting Officer 003B2B

Peter Lewandowski Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown, NJ 07724

2. CONTRACTOR REMITTANCE ADDRESS: All payments by the Government to the contractor will be made in accordance with:

[X] 52.232-33, Payment by Electronic Funds Transfer—System for Award Management, or

[] 52.232-36, Payment by Third Party

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [x] Upon acceptance of deliverables in section B.4.

4. GOVERNMENT INVOICE ADDRESS: All Invoices from the contractor shall be submitted electronically in accordance with VAAR Clause 852.232-72 Electronic Submission of Payment Requests.

5. ACKNOWLEDGMENT OF AMENDMENTS: The offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

AMENDMENT NO DATE

A0001 2/19/2021

B.2 GOVERNING LAW

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto, as permitted by FAR 12.212. If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the Government with the commercial computer software or documentation (shrink-wrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing license and data rights regarding the Government’s use, duplication and disclosure of commercial software and/or data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address license or data rights regarding the Government’s use, duplication and disclosure of commercial software and/or data shall not be included or made a part of the Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. § 3901 et seq.), Contracts for Data Processing or Maintenance (38 USC § 5725), and FAR clauses 52.212-4, 52.227-14, 52.227-19 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement. In the event of conflict between this clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this clause shall prevail. The Contractor shall deliver to the Government all data first produced under this Contract/Order with unlimited rights as defined by FAR 52.227-14. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ) in accordance with 28 U.S.C. § 516; at the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by modification (Standard Form 30) and shall only be made by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.3 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:

(1). Definitions.

a) Licensee. The term “licensee” shall mean the U.S. Department of Veterans Affairs (“VA”) and is synonymous with “Government.”

b) Licensor. The term “licensor” shall mean the Contractor having the necessary license or ownership rights to deliver license, software maintenance and support of the computer software being acquired. The term “Contractor” is the party identified in Block 17a on the SF1449. If the Contractor is a reseller and not the Licensor, the Contractor remains responsible for performance under this Contract/Order.

c) Software. The term “software” shall mean the licensed computer software product(s) cited in the Schedule of Supplies/Services.

d) Maintenance. The term “maintenance” is the process of enhancing and optimizing software, as well as remedying defects. It shall include all new fixes, patches, releases, updates, versions and upgrades, as further defined below.

e) Technical Support. The term “technical support” refers to the range of services providing assistance for the software via the telephone, email, a website or otherwise.

f) Release or Update. The term “release” or “update” are terms that refer to a revision of software that contains defect corrections, minor enhancements or improvements of the software’s functionality. This is usually designated by a change in the number to the right of the decimal point (e.g., from Version 5.3 to 5.4). An example of an update is the addition of new hardware.

g) Version or Upgrade. The term “version” or “upgrade” are terms that refer to a revision of software that contains new or improved functionality. This is usually designated by a change in the number to the left of the decimal point (e.g., from Version 5.4 to 6).

(2). Software License.

a) The software license provided to the Government is a term, nonexclusive license to use the software.

b) The Government may use the software in a networked environment.

c) Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in FAR 52.212-4(d).

d) All limitations of software usage are expressly stated in the Schedule of

Supplies/Services and the Performance Work Statement/Product Description, and incorporated license agreement.

(3). Software Maintenance and Technical Support.

a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this Contract/Order, the Government will issue a separate contract or order for maintenance and support. Conversely, if a contract or order for continuing software maintenance and technical support is not received, the Contractor is neither authorized nor permitted to renew any of the previously furnished services.

b) The Contractor shall provide software support services, which includes periodic updates, enhancements and corrections to the software, and reasonable technical support, all of which are customarily provided by the Contractor to its commercial customers to cause the software to perform according to its specifications, documentation or demonstrated claims.

c) Any telephone support provided by Contractor shall be at no additional cost.

d) The Contractor shall provide all maintenance services in a timely manner in accordance with the Contractor’s customary practice or as defined in the Performance Work Statement or Product Description. However, prolonged delay (exceeding 2 business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.ppirs.gov).

e) If the Government allows the maintenance and support to lapse and subsequently wishes to reinstate it, any reinstatement fee charged shall not exceed the amounts that would have been charged if the Government had not allowed the subscription to lapse.

(4). Disabling Software Code. The Government requires delivery of computer software that does not contain any code that will, upon the occurrence or the nonoccurrence of any event, disable the software. Such code includes but is not limited to a computer virus, restrictive key, node lock, time-out, or other function, whether implemented by electronic, mechanical, or other means, which limits or hinders the use or access to any computer software based on residency on a specific hardware configuration, frequency of duration of use, or other limiting criteria. If any such disabling code is present, the Contractor agrees to indemnify the Government for all damages suffered as a result of a disabling caused by such code, and the contractor agrees to remove such code upon the Government’s request at no extra cost to the Government. Inability of the Contractor to remove the disabling software code will be considered an inexcusable delay and a material breach of contract, and the Government may exercise its right to terminate for cause. In addition, the Government is permitted to remove the code as it deems appropriate and charge the Contractor for consideration for the time and effort expended in removing the code.

(5). Manuals and Publications. Upon Government request, the Contractor shall furnish the most current version of the user manual and publications for all products/services provided under this Contract/Order at no cost.

B.4 DELIVERY SCHEDULE

The Base Period of Performance (PoP) shall be 12 Months from date of award.

CLIN Description QTY Unit Unit Price Total

Data Curation Tool License for 20 data stewards; 150 end-users

In Accordance With (IAW) PD Section 1.0 & 1.1

12 Months

(MO)

Incidental Services – up to 300 hours

IAW PD Section 1.0 & 1.1

1 Lot

(LO)

Base Period Total $ 732,193.74

Option Period One- PoP shall be 12 months from completion of Base Period, if exercised.

Data Curation Tool License for 20 data stewards; 150 end-users

IAW PD Section 1.0 & 1.1

12 MO

Option Period One Total

Optional Task FAR 52.217-7, Option for Increased Quantity – Separately priced Line Item (MAR 1989) may be exercised at any time and from time to time up to the quantity set forth in each

Contract Line Item Number (CLIN). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer

Incidental Services – up to 300 hours

IAW PD Section 1.0 & 1.1

1 LO

Option Period One Optional Task Total

Option Period One Grand Total

Option Period Two- PoP shall be 12 months from completion of Option Period One, if exercised.

Data Curation Tool License for 20 data stewards; 150 end-users

IAW PD Section 1.0 & 1.1

12 MO

Option Period Two Total

Optional Task FAR 52.217-7, Option for Increased Quantity – Separately priced Line Item (MAR 1989) may be exercised at any time and from time to time up to the quantity set forth in each

CLIN. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer

2002 Incidental Services – up to 300 hours 1 LO

IAW PD Section 1.0 & 1.1

Option Period Two Optional Task Total

Option Period Two Grand Total

Option Period Three- PoP Shall be 12 months from completion of Option Period Two, if exercised.

Data Curation Tool License for 20 data stewards; 150 end-users

IAW PD Section 1.0 & 1.1

12 MO

Option Period Three Total

Optional Task FAR 52.217-7, Option for Increased Quantity – Separately priced Line Item (MAR 1989) may be exercised at any time and from time to time up to the quantity set forth in each

CLIN. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer

Incidental Services – up to 300 hours

IAW PD Section 1.0 & 1.1

1 LO

Option Period Three Optional Task Total

Option Period Three Grand Total

Base and Options Grand Total $3,063,225.49

B.5 PRODUCT DESCRIPTION

1.0 REQUIREMENTS:

The Department of Veterans Affairs (VA) requires a low-code/no-code cloud-based Commercial Off the Shelf (COTS) Data Curation product that meets all the functional and non-functional requirements out-of-the-box as a minimally viable product. Under a separate, existing contract the tool will be configured and integrated into the Rockies platform. This solicitation is for the licensing of a data curation COTS product and incidental services, specifically product subject matter experts (SME) working in collaboration (no hands-on keyboard) to consult with an existing Development Operations team to configure the COTS product in the VA Enterprise Cloud (VAEC) as an integrated component of the Rockies platform. A system integrator is not needed. Additionally, once the tool is procured, VA will take the product and host it in a controlled VA environment due to data sensitivity and security requirements. As such, the hosting shall be on the VAEC and must conform with requirements for enterprise cloud providers (see Attachment A – VA architectural diagram).

For information purposes only: “Rockies” is a data and analytics platform that is built on cloud-native services to ease the burden of data access, integration, and organization while supporting an interoperable ecosystem for data analytics in VA.

Rockies enables capabilities for managing data and knowledge, discovering new knowledge, using algorithms to make inferences on individuals or cohorts, and managing reports and inferences in workflows. Business and Information Technology programs within VA can leverage the Rockies platform to rapidly adapt shared capabilities and develop and share reference products to realize and collaborate on their mission use cases. This solicitation is not for Rockies, only for the data curation software tool which VA will integrate into VAEC under a separate contract.

The vendor shall provide incidental services in the form of domain experts to consult on topics such as configuration, troubleshooting, patches and upgrades, knowledge sharing, and support to the VA system integration team on an as-needed basis for up to 300 hours annually.

The vendor shall include licensing for the software, while VA will provide the hosting and infrastructure through VAEC to include getting the product hosted in VAEC. Licensing should be on a 12-month basis for up to 150 users.

The VA anticipates awarding a contract with a 12-month base period (12-month licenses) with three 12-month option periods.

1.1 Salient Characteristics

Category Req Number Description

Vendor capability response: (Y/N &

Explanation)

D at a Tr an sf or m at io n C re at io n an d

M an ag em en t in G ra ph ic al

U se r I nt er fa ce CE-101 The product shall create, clone, modify, and delete transformation logics all within the GUI (browser-based GUI required) and shall not require coding from users to achieve the aforementioned functions.

Yes, supported out of the box.

CE-102 The product shall support transformation logics: column modification, filter, join (left, right, inner, outer), group-by, aggregation operations within GUI

Yes, supported out of the box.

CE-103 The product shall support text string format editing: (a) concatenating two columns, (b) formatting data based on regular expressions such as date/time, SSN and phone number format, (c) splitting one column into multiple columns based on regular expression, all within the GUI without requiring coding.

CE-104 The product shall support column filtering features by: (a) a set of values, (b) numerical range, (c) regular expression (i.e., letter and digits combination), (d) string pattern,

(e) wild card, all within the GUI without coding requirements. For the set of values such as medical codes, the GUI allows users to upload a list of values from an external file or point to the corresponding tables in the database or files in data lake.

CE-105 The product shall support data imputation for missing data or incorrect data: (a) nearest-neighbor value, (b) average, (c) mode, (d) constant, (e) other statistical methods all within the GUI without coding requirements.

CE-106 The product shall automatically apply data matching using built-in advanced statistics and (supervised, unsupervised, and/or active) machine/deep learning techniques (e.g., probabilistic matching, packages like DeepMatcher, etc.)

when joining two tables within the GUI. The probability matching operation can be applied to a single column or multiple columns.

CE-107 The product shall provide built-in record linkage and de-duplication capability. It shall provide users the ability to detect and remove duplicate data using built-in advanced statistics and/or a machine learning model.

CE-108 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

Yes, supported. We currently support SQL, Java, with Python support coming in the near term as well as other languages (R

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

possibly) supported in our future roadmap.

Trifacta typically integrates with analytic and machine learning platforms to prep the data and hand it off where complex analysis and AI/ML work is done.

CE-109 The product shall support both the creation/modification of transformation logic and the execution of the transformation logic within one integrated GUI. Both the input transformation code and output results shall be accessible and viewable in the same GUI

Yes, supported out of the box.

Ve rs io ni ng

E ffe ct iv e C ol la bo ra tio n

CE-110 The product shall allow users to share search results in the GUI.

CE-111 The product shall provide source control of all generated code and transformation logic using industry standard version control systems (Github) It shall enable users to push, pull, and compare different versions, and revert changes.

Yes, supported. All Trifacta recipes and flows (scripts) can be exported and shared.

It’s common for our customers to use tools like GitHub repositories to manage versions of Trifacta recipes and flows.

CE-112 The product shall allow collaborative creation and management of transformation logic with other end users or end user groups through the

GUI

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

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.

Yes. Trifacta has collaboration capabilities built in for working on data wrangling efforts.

Trifacta flows and recipes can be exported and delivered into GitHub for collaboration and sharing. This is commonly done by our customers.

Usually, GitHub is where customers manage “golden copies” of Recipes and wrangling elements for sharing.

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

Yes, Trifacta supports the addition of comments data “Flows” as well as “recipes”.

From a hierarchy perspective a Trifacta “Flow” contains one to many “Recipes”.

CE-116 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.

Please see the Trifacta blog post on “Deployment Manager:”

https://docs.trifacta.com/ display/r076/Overview+ of+Deployment+Manag er

U se r Ex pe rie nc e

CE-117 The product shall support users to search for transformation logic via a simple search box. The product shall provide a GUI that allows users to interact with it using natural language so that they do not have to learn complex query languages for semantic search.

Yes, searching for functions in an integral part of Trifacta’s self-service low/no code platform.

Furthermore, once the user has found the function they are looking for, the guided use of the function reduces the need to even delve into the documentation. (Put another way, the documentation and search is baked into the product.)

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.

Yes/No, Trifacta does not have a built-in approval engine in the current version. Our customers leverage a best-practices approach to build wrangling workflows (Recipes and Flows) in development environments and migrate them safely across test, QA and into production following SDLC best practices. Trifacta will work with the VA to operationalize the platform properly to meet the requirements as outlined which may include integrating Trifacta into the overall DataOps workflow to tie into scheduling, notification and configuration management tools across the Azure architecture.

Edit history across all users/collaborators is maintained in the recipes.

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.

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

CE-121 The GUI shall be able to display the data before and after a transformation, ideally side by side without jumping between UI pages, for debugging and reviewing purposes. For situations where displaying the entire large data does not meet human-computer interactive performance, the GUI shall be able to preview a subset of data before and after the transformation.

CE-122 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.

CE-123 The product shall support users to search for data set including the intermediate output in the transformation. The search interface should be "google-like".

Yes/No, Trifacta is not a data catalog or a search engine;

however, Trifacta can be used to populate a data catalog or search engine. Data that is sampled into the UI during wrangling can be searched to identify specific values or patterns that can be used to drive transformations in recipes

CE-124 Once a user chooses a dataset of interest from the search results, he/she can expand the data linage graph which displays the transformations upstream and downstream.

CE-125 When users choose the join operation, they can select all output columns from the original tables with 1-2 clicks, (i.e., users do not need to manually type each column's name or select each column).

CE-126 The product’s GUI shall allow users to add tag datasets and

Yes. Trifacta’s GUI allows users to define logic that should be transformation logics for better grouping and search experience.

applied to data for downstream use.

Based on our understanding of this question, Trifacta can allow data to be enriched through tagging or adding additional logic (if/then or case statements) to improve data grouping so it can be loaded into a catalog or search tool.

W or ki ng w ith

M et ad at a

CE-127 The product shall enable users to manage (i.e., view/create/modify) metadata associated with each data set including its lineage, business, operational, technical metadata using a GUI.

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)

CE-129 The product shall enable metadata enrichment and integration with external metadata sources using industry standard

CE-130 The product shall support search of datasets based on metadata in the

GUI

CE-131 The product shall support multiple levels granularity of data views based on users’ access permissions.

Yes, Trifacta adheres to your security models by passing user credentials through to the source/destination data stores. The source/destination is what enforces security. Additionally, there are other 3rd party software providers like Immuta that specifically solve data access control and governance challenges designed for the type of need VA has.

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

Yes, supported out of the box. Please see the following link:

https://docs.trifacta.co m/display/DP/Support ed+File+Formats

CE-133 The product shall capture and graphically display data lineage information ingested from an external system. In other words, if there are additional transformations executed in an upstream or a downstream system and the metadata is ingested through the current product of interest, the current product of interest shall be able to graphically display the full data lineage information. Please describe how your product receives external metadata such as the corresponding API’s specifications.

Yes, Trifacta captures and graphically displays the lineage of a “Job”.

The job metadata is used for general tracking, data governance, or audits.

Please see the following link:

https://docs.trifacta.com/ display/r076/Job+Detail s+Page

CE-134 The product shall support users with specific roles to organize and standardize transformation logics and tagged information all within the product GUI.

CE-135 The product shall support automatic extraction of metadata from transformation logics written in SQL and Python. The extracted metadata shall be stored in this product metadata depository along with the metadata associated with the product’s GUI-generated transformation logics.

Yes, Python can be used to integrate / extract metadata from Trifacta. (SQL is not supported for this functionality) See API docs:

https://api.trifacta.com /ee/7.6/index.html

Sc al ab ilit y an d Pe rfo rm an ce

CE-136 The product shall support transformation of large tables, including full join between two tables each of with 10 billion rows.

CE-137 The product shall support preview of transformation results within <3 seconds to achieve human-computer interactive experience.

M on ito rin g, a le rti ng au di tin g an d us ag e in si gh ts

CE-138 The product shall provide audit trails on who made changes to the data and what type of transformation were done.

CE-139 The product shall provide audit data on the actor accessing data to include date and time information for when the data was accessed.

CE-140 If there is any abnormal usage pattern detected (i.e., attempts by data consumers to access sensitive data without having proper privileges), the product shall provide full auditability of the action and provide the ability to raise an alert.

The recipient of the alert shall be configurable.

Yes/No. There are specific tools out there that Trifacta partners with and integrates with - (For example Immuta) - that are designed to provide deep access control, auditing and action for this type of need, where Trifacta is focused on enabling self-service data preparation while adhering to the security models in your environment.

Trifacta adheres to the security policy by passing user credentials through vs enforcing security. Put another way, Trifacta does not store any data but is a tool/mechanism by which users can access end systems for the purpose of “wrangling” or preparing data for further downstream consumption. Users actions on data in the form of Job runs is captured and is auditable.

Furthermore, there are APIs that can be used to build additional functionality that might be able to satisfy this requirement.

CE-141 The product shall support using machine learning/AI and advanced statistics actively inspect data and provide intelligent tagging. For instance, the product can detect anomaly in the dataset, flag data quality issues, and provides suggestions to reduce/eliminate potential degradation of the data quality.

CE-142 The product shall be capable of identifying schema differences and provide advisories to the user for these changes.

CE-143 The product shall support automated data quality checks. These quality checks shall be defined by the user via a clearly defined rules engine, or via clearly defined rules table that the end-user can inspect, modify, and update.

W or ki ng w ith m ul tip le d at a se ts

CE-144 The product shall support import and management of multiple different data sources including (but not limited to) SQL database data exports (Oracle, SQL server, MySQL, PostgreSQL), NoSQL database data exports (MongoDB, Cassandra, Redis, YottaDB) and data files (Parquet, CSV, JSON, XML, XLS, Excel, Avro, ORC)

Yes/No, Generally supported.

Trifacta has an open architecture that features a robust connectivity palette, as well as open connections using JDBC to enable integration with various databases, storage engines and applications.

https://www.trifacta.com /blog/bringing-whole-new-world-connectivity-wrangler-edge-enterprise/

CE-145 The product shall provide the capability to manage multiple versions of schemas for each data set using industry-standard source control (i.e., on the VA Enterprise Github)

Yes, Trifacta Flows and Recipes can be exported and integrated with source-control or configuration management tools (GitHub for example).

CE-146 The product shall allow users to do data transformation by combining two or more data sets from any combination of sources (as defined in CE-141)

CE-147 The product shall enable users to manage master data and, based on this master data model link multiple external data sets as a single virtual dataset that can be queried and browsed.

No. Trifacta is not a data virtualization or Master Data Management tool/product. However, Trifacta can automate the creation of composite “master” data sets that can be published out to repositories and/or catalogs where they can be queried and browsed.

CE-148 The product shall automatically collect and manage all data linage, data quality information from all data sources imported.

Yes. Trifacta maintains lineage for transformations applied to date in the recipes. Additionally, features in Trifacta are designed to support data lineage through the overall DataOps lifecycle.

Ap pl ic at io n

Pr og ra m m in g In te rfa ce s

(A

PI

a nd A ut om at io n

CE-149 The product shall have a set of APIs that provide feature parity of what is possible using the UI so that manual processes can be automated.

CE-150 The product shall enable users to schedule sending of periodic and on-demand reports on data quality to the data stakeholders.

Yes, supported out of the box. Data loaded initially is assumed to not have a lineage but once a job is run (transformation logic is applied) that is when there is a lineage. Imported data isn't mutated, and data is only created when a Job is run. If you want to track the lineage outside of Trifacta's "per job run" lineage, Trifacta provides APIs to access this metadata in an external graph database, or other repository.

CE-151 All transformation logic generated by the product GUI shall be exportable in industry-standard languages (SQL, Python, R, etc.) and in the case of deep learning, industry standard models (e.g., Tensorflow, PyTorch, MXNet, ONNX, etc.). This export function can be automated based on pre-configured events or schedule.

Yes/No. Trifacta generates a domain specific language (DSL) called Wrangle script that takes elements from other open languages like Python, Java, Javascript and SQL that at runtime is compiled down to Spark / Scala and handed off to a Spark engine to run.

Currently we do not compile down to a specific open language as we are not a “code generation” platform.

There are considerations on our roadmap to potentially compile down to other languages in the future.

Currently, Trifacta can dynamically pushdown some transformation logic to SQL for execution by a database management system;

however, Trifacta is not a code generator that creates exportable industry-standard language exports for general purpose use.

D as hb oa rd s an d

R ep or ts

CE-152 The product shall provide capabilities for users to manage (add/update/delete) and master data and metadata including descriptive statistics (min, max, count, sum) and

Yes/No.

1. Yes, Trifacta does support statistical metadata about job runs when profiling of data is any structural issues (deviance from schema) via the GUI enabled (you will see data type, min, max, average, etc. as well as a high level histogram as well as mismatched and/or missing data.

2: Yes, Trifacta does infer the schema on import, as well as supporting transformations to shape the schema on output.

3. No, Trifacta is not a tool used to monitor schema drift. If you want to cleanse data in an automated fashion to keep consistent “master” data against data sets, that is possible and a common use case. Trifacta is not however an “MDM” solution.

CE-153 The product shall have dashboards and reports that provide data quality metrics to data stewards including any curation activities on data sets. It shall also enable data stewards to customize the dashboards and reports.

Yes, Trifacta provides this capability;

however, dashboards cannot be customized.

https://docs.trifacta.co m/display/r076/Jobs+ Page

CE-154 The product shall provide dashboard implementations to be reusable constructs with the ability to be configured and used for organizational and project level data quality initiatives that could be used for a single system or single data migration effort.

CE-155 The product shall provide the ability to track the status of anomalies, and progress in the remediation process.

Yes. Trifacta will help you discover anomalies and define remediation logic, but the remediation process is outside of scope for Trifacta. You will probably want to use a ticket tracking tool for that.

CE-156 The product shall offer reusable templates that can help create common and shared metadata and reporting structure such that metrics gathered at a lower project or system level can be natively reported up to an external dashboard software, such as PowerBI.

Yes, supported

D ep lo ym en t

DR-01

This product shall be able to be hosted and operated in the VA Enterprise Cloud (VAEC) environment and be fully functional no later than 45 days after contract award. Requirements for hosting and operating products are outlined in the VA Enterprise Cloud Technical Reference Guide, Version 1.3 July (https://www.vendorportal.ecms.va.g ov/FBODocumentServer/DocumentS erver.aspx?DocumentId=4525852&Fi leName=36C10B18R2609-004.pdf )

Yes, supported

DR-02

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

Yes, per the document link in DR- 01, Trifacta supports ADFS. Please see:

https://docs.trifacta.co m/display/r076/Config ure+SSO+for+SAML

DR-03

The product shall support data lake, database, and analytics technologies equivalent to VAEC Azure including Azure Data Lake Gen2, Azure Blob Storage, SQL server database, Cosmos database, Azure Databricks, Azure Synapse, Azure Data Factory, Azure Key Vault, Azure Log Analytics, Azure Kubernetes Service

Yes, Trifacta provides support data lake, database, and analytics technologies. Please see:

https://www.trifacta.com /solutions/azure/

DR-04

The product shall exhibit the characteristics of an open technology solution. Following is a subset of more detailed requirements: 1. The vendor or the product shall allow and enable VA to have access to all data ingested into the product. 2. The vendor or the product shall allow and enable VA to extract all data that was ingested into the product, including any data that has been curated and transformed using the product. 3.

Any data and metadata exported by VA shall not be in the vendor’s proprietary storage format. They must be decryptable and be in an open storage format such as Parquet, CSV, JSON, XML, ORC, AVRO, text or SQL. 4. The product shall either be based on an open-source project (>%80) or have well defined APIs to enable VA to extract all data, including metadata, and any transformation logic applied to the data.

1 & 2: Yes, as Trifacta facilitates transformation of data from the source system to the destination, Trifacta does not store any data. It is assumed that all sources and destinations of data are under your control, meeting your security requirements.

3: Yes, Trifacta metadata is generally exportible in JSON format via the documented API.

4: Yes, Trifacta has a well-defined API See:

https://api.trifacta.com /ee/7.6/index.html

DR-05

The product shall have fully searchable web-based product manuals for different types of users:

(at minimum Users Guide, Programmers Guide, Administration Guide)

Yes, Trifacta as a tool has a fully searchable user interface to minimize the need to go to the documentation.

Furthermore, Trifacta online documentation is also searchable.

https://docs.trifacta.co m/display/r076

DR-06

The product shall allow VA staff to provision user access with permission control to the product.

Yes, supported with configuration.

DR-07

The User’s Guide shall include video training materials

Yes. Trifacta has numerous videos available on the Trifacta Community (https://community.trif acta.com/s/) as well as on the Trifacta YouTube site (https://www.youtube.

com/user/TrifactaInc/p laylists).

Se cu rit y

SR-01

Cryptographic Modules:

a. The product shall be compliant with Federal Information Processing Standards Publications (FIPS PUBS) 140-2, Security Requirements for Cryptographic Modules

b. The product shall apply technology/standards that are consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500;

VA Directives 6004, 6513, and 6517;

and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards Publications (FIPS PUBS) 140-2, Security Requirements for Cryptographic Modules. The product shall ensure sensitive data is properly protected in compliance with all VA regulations.

Yes, Trifacta deployed in an Azure environment respects Azure data encryption for accessing and storing data at rest and in-flight. Please refer to Microsoft’s Encryption documentation:

https://docs.microsoft.

com/en-us/azure/azure-government/azure-secure-isolation-guidance#data-encryption-at-rest https://docs.microsoft.

com/en-us/azure/security/fund amentals/encryption-overview#encryption-of-data-in-transit

SR-02

The product shall provide fine granular access control across different data sources using role-based access control (RBAC) and / or Attribute Based Access Control

(ABAC).

SR-03

The product shall be able to be integrated with VA’s Security intelligence and event monitoring (SIEM) platform (e.g., Splunk or Azure Log Analytics).

Yes, Trifacta provides a robust set of REST API endpoints that enable customized integrations with external products such as Splunk or Azure Analytics.

SR-04

The product shall support VA active directory and Azure active directory integration to achieve the single-sign-on (SSO) experience for VA users.

Yes, Trifacta supports integration with Microsoft Azure Active Directory to achieve

SSO.

2.0 SECTION 508 NOTICE OF THE FEDERAL ACCESSIBILITY LAW

AFFECTING ALL ELECTRONIC AND INFORMATION TECHNOLOGY

PROCUREMENTS

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.

2.1 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:

E205 Electronic Content – (Accessibility Standard -WCAG 2.0 Level A and AA Guidelines)

E204 Functional Performance Criteria E206 Hardware Requirements E207 Software Requirements E208 Support Documentation and Services Requirements

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

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

3.0 SHIPMENT OF SOFTWARE

All software shall be electronically delivered to the Primary point of contact below:

3.1 Special Shipping Instructions

Prior to shipping, the Contractor shall notify Site POCs, by phone followed by email, of all incoming deliveries including line-by-line details for review of requirements. The Contractor cannot make any changes to the delivery schedule at the request of Site

POC.

All shipments, either single or multiple deliveries, shall bear the VA Purchase Order number on external shipping labels and associated manifests or packing lists. In the case of multiple container deliveries, a statement readable near the VA PO number will indicate total number of containers for the complete shipment (ex. “Package 1 of 2”), clearly readable on manifests and external shipping labels.

4.0 INFORMATION SECURITY CONSIDERATIONS:

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

While the Contractor shall strive to make reasonable accommodations to work within the VA’s security and compliance standards, the Contractor shall be allowed to use the audited and approved Contractor federal cloud service system security plan (SSP) and associated procedures as the core requirements for the operations of the system.

Where there is conflict between the SSP and Addendum B below, the SSP shall control.

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 OI&T 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 OI&T. Architecture & Engineering Services (AES) has overall responsibility for the VA TRM.

5.2 GOVERNMENT FURNISHED EQUIPMENT (GFE), PROPERTY (GFP),

MATERIALS (GFM), AND DATA (GFD)

As deemed necessary to be required by the PM, VA will provide the following in support of solution implementation. All onsite activities will be completed virtually as directed by the PM and COR through Cisco Webex, Skype or Microsoft Teams if offices are closed due to the COVID-19 pandemic.

Sponsored access to Government data sources as needed upon order award Sponsored onsite access to VA facilities for Contractor personnel as needed, including any required badging or clearances for implementation of the SaaS Solution, trainings and support.

No Government equipment is seen as needed but, if Required by VA, Government furnished equipment, property or materials as required to carry out the requirements of the solution (e.g., laptops)

Office space will be provided on an ad-hoc basis as needed if VA requires contractor personnel to…