The Lionbridge TMS vendor portal is the vendor portal for Lionbridge (https://www.lionbridge.com). There is only one instance of this system running. The TMS is a special portal because it does not contain pricing - it's more a portal for project specifics, and to claim a job. Lionbridge has migrated to LCX, which contains full pricing details as well, but some files and projects still need to be retrieved via TMS, which we support. We recommend that you set up the Auto-approve functionality for Lionbridge's portals, because they mostly work on a first come-first served basis.

Use cases:

BeLazy supports integration with Lionbridge TMS through a specialized connector that enables file retrieval and job claiming. The main use cases where the TMS integration is valuable:

  • You need to retrieve files from Lionbridge TMS for projects managed in LCX or other systems
  • You want to claim jobs and access project specifications through TMS
  • You need automated job claiming for first come-first served offers
  • You want to deliver completed work by uploading files through TMS
  • You want to synchronize TMS job details with your business management system or tracker while using external pricing

Integration type:

The Lionbridge TMS integration uses web scraping and logs in with your specific credentials. This implementation provides access to job claiming functionality and file retrieval while respecting the portal's permission structure.

Requirements:

There are no requirements to use the Lionbridge TMS portal other than having a valid username and password. To use the Lionbridge TMS vendor portal, you will only need the URL, user name, password that you use on the portal.

 

Expected URL format:

The URL is always https://tms.lionbridge.com/
 

Lionbridge TMS-specific configuration:

No additional connector-specific configuration options are available for Lionbridge TMS. The integration automatically adapts to the portal's job claiming system and file retrieval functionality.


Functionalities and connector-specific information:

  • Unit of acceptance: Task
  • Multiple target languages: Not supported, only through bundling
  • End Client, Workflow: End client and workflow extracted from job details
  • Pricing: Not available - TMS does not contain pricing information
  • Project exclusion: Not supported
  • Download source files: Supported, including reference materials
  • Delivery: File upload and job closing supported for delivering completed work
  • Manual delivery detection: Not supported
  • Linguist assignment: Not supported - TMS portal does not support this functionality
  • Project bundling: Supported
  • 2-factor authentication: Not supported
  • Data synchronization: Project specifications and job details are synchronized, excluding pricing information
  • Legacy support: TMS is not used much any longer, mostly for sharing files, but remains fully supported


Typical issues and how to resolve them:

  • Synchronization: By default, the connector is synchronized every 30 minutes, but you can also synchronize immediately once an email with a new job offer comes in.
  • Pricing configuration: Lionbridge TMS does not contain prices, so prices should be taken from the customer's price list or price profile in your business management system.
  • Project bundling and workflow structure: Each workflow in TMS is single-step. You can use the job bundling to turn consecutive steps such as translation, revision into one workflow in your business management system or tracker. For tasks like LQA or LSO for the same project, we recommend using task bundling, meaning they are added under the same project in Plunet, XTRF Classic and any custom integration under a new task or item. Daily and monthly project bundling and project bundling creating one project with different language pairs are supported.
  • Instruction mapping: All instructions are extracted from the various instruction fields in TMS, and can be automatically reused in your customizable, client and program-specific instructions to the project managers and the vendors.


Connector-specific data extracted: See here.