Connector

Q.1 What Connectors are planned for future integration?

Answer: The following systems are currently on the roadmap for future integration via TI Connectors:

  • EvidentIQ (EDC)
  • Medrio (EDC)
  • Castor (EDC)
  • WorkDay LMS
  • DayForce LMS

Q.2 Is re-validation required when new TI platform versions are released?

Answer: No. All Connectors are built on standardized APIs and operate independently of the core TI platform. Therefore, re-validation is not required after each platform release. TI monitors any upstream vendor changes and coordinates updates as needed.

Q.3 Have any solutions been implemented from your own company or other vendors? Please explain the preferred approach to handle infrequent, batch, near real-time, and real-time (synchronous) interactions. What is the typical volume of data and transactions that you handle?

Answer: We have integrated with many different systems through a combination of our enterprise API and our connector platform, which provides a pub-sub capability to other provider APIs that TransPerfect maintains. For the enterprise API, we prefer near real-time interaction, and the API connects directly to our internal enterprise resource bus and application-level queues. Through our connector platform, we can support any of the preferred synchronization approaches and have found that infrequent and batch approaches often suffice for most integrations using our server less connector architecture. Typical volume depends upon the customer, but we have customers who regularly send us thousands or tens of thousands of data points and documents daily.

Q.4 Can TI integrate with a data lake, such as Denodo or Teradata?

Answer: Yes. Through our connector framework, we have integrated with several data lakes, including Teradata.

Q.5 What services/utilities are available for bulk load and bulk export to support archival, legal discovery, mergers, acquisitions/divestitures?

Answer: Multiple approaches are supported. The TI reporting framework is built of denormalized domains from our various platform applications, using an Extract, Transform, and Load (ETL) that runs every hour. These domains can then be exported easily to AWS Athena, which may then be easily accessed as a data source through several means. We also support a simpler export of these domains to flat files on SFTP sites as well as a direct connection to AWS S3.

Q.6 Explain how TI merges data elements based on metadata?

Answer: Our connector framework mirrors the endpoint API in its data model and translates data elements to the TI ESB data model using GraphQL, which supports 1 to 1, 1-to-many, and many-to-many relations.

Q.7 How do you abstract the solution interfaces from the data model?

Answer: We use GraphQL to help us with the abstraction.