BeLazy Technologies Ltd.

Use cases:

There are five main use cases where the Phrase TMS integration comes handy:

• Your customer sends you jobs via a buyer-vendor relationship, and you want these jobs to be managed in your business management system.
• You have connected Phrase TMS to a content management system and projects are automatically being created, and you want these jobs to be managed in your business management system.
• You are using the Phrase TMS Submitter Portal to allow your customers to create projects, and you want these projects to appear in your business management system.
• You create jobs in your instance of the Phrase TMS (for example due to content connectors or file engineering reasons), and you want these jobs to automatically appear in the business management system.
• You want everything that happens in Phrase TMS to be automatically reflected in your business management system for automated invoicing and PO handling reasons.
  
  

Requirements:

In order to access the Phrase TMS, BeLazy uses its APIs. The Starter and Freelance editions are thus not supported, because they does not have the APIs enabled.

Expected URL format:

The URL is https://cloud.memsource.com or https://us.cloud.memsource.com. 

Configuration:

• You authenticate in Phrase TMS with your username and password.
• You can select which Phrase TMS projects should not be created in BeLazy. For example, if your XTRF or Plunet Phrase TMS integration creates projects, you can use regular expressions to filter them out from being duplicated.
• You can set up a naming convention for the projects.
• You can map all the triplets of Phrase TMS clients, business units and cost centers to your business management system customers.
• You can map domains and subdomains to specializations in your business management system.
• You can select the business management system service based on Phrase TMS workflows and workflow steps. 
• You can map translation memory, non-translatable and machine translation rate cards to your internal rates.
• You can set up a rule to map vendors both ways.
• You can set up bundling.
• Language codes need to be mapped between the systems.
  
  

Functionality supported:

• Vendor and admin user scenarios are supported.
• Project-based and job-based modes (continuous projects) are both supported.
• Projects without a comprehensive analysis run an analysis before adding the information to the business management system. Once the analysis runs, the entire pricing is based on the newly run analysis. It is configurable whether you want this to be always created or take it over.
• Net rate schemes and price lists are supported. If they are not present, the price comes from the business management system, from the customer's pricing information.
• Only projects and jobs created after the configuration of the Phrase TMS connection automation will be implemented in the business management system.
• You can configure whether you want all jobs or only jobs that are not assigned to any user or are assigned to the user associated with the API access to be picked up.
• Automatic creation of projects through an auto-approve rule.
• A project delivered in the business management system may also be automatically delivered in Phrase TMS. 
• If all jobs are delivered, BeLazy can also close the Phrase TMS project.
• The integration is bi-directional, you can assign vendors in the business management system based on the Phrase TMS vendors and close BMS jobs when they are delivered on Phrase TMS.
  
  

Functionality not supported:

• Linguist user scenarios are not supported, due to rights limitation on the API.
• It is not possible to download bilingual documents, only online workflows are supported.

Vendor assignment functionality:

• You can explicitly create a vendor assignment using the assignment mapping dialog. This allows you to explicitly select BMS users and map them to your Phrase TMS user list appearing on the left.
• XTRF only:if explicit selection was not done, by default, we take the vendor's username in Phrase TMS from XTRF's Provider information:
  • Main data / System accounts / Username in external system.
• If this information is not available, we can check for the existence of vendors and create them in Phrase TMS as necessary if you enable the "I want BeLazy to automatically map my BMS users to Phrase TMS users and create accounts on demand." checkbox, and select a naming convention.
• BeLazy watches vendor assignments in the BMS projects and reassigns vendor based on this. In the case of Plunet and XTRF, webhooks are sent, so BeLazy picks up the changes immediately. In Protemos, the frequency of checks / reassignment is not more than 30 minutes, and as little as 5 minutes at the beginning and the end of the project, but it also happens every time you sync projects with your BeLazy connections.
• BeLazy can also check assignments in Phrase TMS and reassign vendors based on the reverse vendor assignment rules.

Additional information:

Jobs are merged according to languages and workflow steps.