Translation Management Service

Summary

TMS (Translation Management System) operates as an independent system but is still based on Workspace as the top-level structure. Its member management, permission management, etc. are still provided by the Workspace service. Unlike LCMS, for supplier tenants, each tenant will only have one workspace, which is implicit. When a Language Service Provider (LSP) is created, a workspace is automatically created and cannot be switched or deleted. The resulting localization projects, tasks, etc., will all be associated with this workspace.

Overview

The scope management service is responsible for converting confirmed localization orders into localization projects and managing them. It mainly has the following functions:

• Screening suitable suppliers for orders
• Converting orders to localization projects
• Localization project management
• Localization task management
• Service item configuration
• Resource (translator) management

Flow Chart

Providing Available Language Service Providers for Orders

Orders provide language pairs and service items as parameters. The TMS service screens suppliers that can provide services matching these requirements, calculates the number of projects produced by each supplier, then the TMS service calls the Workspace service to obtain information such as the names and avatars of these Workspaces, assembles them, and returns them to the order service.

Service Item Configuration

Service item configuration, also known as price management, is used for LSPs to configure which service items they support and detailed rates, such as rates for different language pairs, currency-related information, etc. In addition to basic language services, extended additional services can be offered, such as rush service fees, TM alignment services, etc. When a customer initiates an order that includes language pairs or additional services not supported by the LSP, the customer cannot select that supplier.

Converting Orders to Localization Projects and Project Management

When an order is confirmed, on the LSP side, by clicking the "Convert Order to Localization Project" button, the order is converted into a localization project for management. At this point, a localization project associated with the order is generated in the project table. Project management mainly includes:

• Managing members, setting roles (not translators, but PMs who can manage the project)
• Setting basic project information
• Setting project language assets
• Configuring QA parameters and Style Guide
• Configuring project pre-translation parameters
• Creating tasks

Task Management

In orders, the definition of specific work is actually a filter associated with the content repository. Therefore, the essence of creating a task is based on the filter in the order, and then the localization project manager extracts content from the content repository, imports it into the CAT system, forms a localization task, and manages it. The implementation logic is to transfer content from the content repository to the TMS translation content repository, then import it into the CAT repository to form an online translation task. P.S. It should be noted that when creating a task, according to the context strategy in the order, some segments that do not need to be translated but need to serve as context should be imported as locked segments.

Task Assignment

After a task is created, the localization project manager needs to assign the task to translators, selecting translators and setting the start and end times of the task. Before assignment, tasks can be deleted and recreated.

Task Splitting

Unlike file-based translation tasks, Flow's translation units have already been broken down to the segment level, and basic task granularity control can be manually controlled by the PM. However, when there are many segments, the PM may need to use automatic splitting to average the workload. In this scenario, the PM needs to first create a large task, and then the system automatically splits it into smaller projects through workload splitting settings and algorithms.

Task Delivery

After translators submit their work on the translation page, the PM needs to review the translation results. If the review passes, the task is completed; otherwise, modifications are needed.

Resource Management

Resource management is mainly responsible for maintaining translator information, including translator rates, capabilities, such as which language pairs translators are proficient in, which domains they are proficient in, which industries they are proficient in, etc. This information will be used when assigning tasks to select suitable translators based on the domain, industry, etc. of the task. It also includes directly adding translator accounts and inviting translators to join the system. The evaluation system evaluates the work completed by translators, and the evaluation results will be used as a reference when assigning tasks.

Supplementary Notes on Task Management

Workflow

• Tasks support three workflow phases: T (Translation), E (Editing), and P (Proofreading)
• Workflows can be configured as T, T+E, or T+E+P, with the order fixed and unchangeable
• Each phase needs to be assigned to specific translators, with rates set independently
• Once a workflow starts, no phase can be skipped

Task Creation and Assignment

• Tasks are automatically split by target language when created, with each language pair generating an independent task
• Tasks must be assigned to specific translators, team assignment is not supported
• Tasks take effect immediately after assignment, translators cannot refuse tasks