Vocabulary

Role See Roles and tasks	Your role in the Lionbridge TMS™ is determined by your position in the localization process. Three main role categories are the Project Administrator, the Project Team, and the End-user. The following roles belong under the End-user class: the Project Manager, the Customer, the Translator, the Reviewer, the DTP, and the Engineer.
End-user	A user (covers several user roles) which receives Tasks from the Project Administrators, and accepts or rejects them.
Project Administrator	A user (role) that plans and creates projects and jobs. May also assign tasks to End-users.
Project Team	A user (role) which can see everything visible to Project Administrators (Project planning and Status information) and has full access to several views.
Project See Working with the Project Tabs	Projects are created into the TMS™ by the Deployment Team. A project is a localization project. Inside a project there are jobs that include job items, which include tasks.
Job	A Job contains the tasks in all locales. A user sees only tasks assigned to her. When a Job is created, a Workflow Configuration is used as a template.
Activity	An Activity is a class of tasks belonging to a job; one step in the workflow includes one Activity.
Activity Setting	The configuration of one workflow activity (for example Analysis, Filtering) saved as a setting with parameters that can be included in a Workflow Configuration.
Workflow Configuration	A Workflow Configuration is created by combining a group of Activity Settings with a Workflow Template. The Configuration is used for creating new client specific projects into the TMS. See Workflow Template, Activity Settings, and Workflow Configuration
Workflow Template	A predefined Workflow Template including different localization project steps for a Job from word count analysis to delivery. The activities can be further configured by the Project Administrators.
Task See Tasks, Managing your Tasks, Accepting and Rejecting Tasks, and Working with Your Tasks	A Task is a work item, a file to be localized in a given locale, or a generic task, which the TMS™ system takes care of (for example analysis, file conversion). A Pending Task is a task that has no determined Status. An Overdue Task is a task that has not been finished in the limits of the defined deadline. TMS™ creates tasks based on the selected Workflow Configuration when you submit a job. The Workflow Configuration may also automatically assign and plan tasks. A Project Administrator can still control and override any automatic assignments and planning.
Assign	Tasks are assigned to different users (with different roles), in Pool or Priority mode. The role representatives (Customer, Project Manager, Translator, Reviewer, and Engineer) accept and process or reject the tasks. See Managing your Tasks, Accepting and Rejecting Tasks
Fallback Delay	The Fallback Delay controls the time period during which a task is open for accepting or rejecting by the assignees of the task. When the task is neither accepted or rejected by any assignee or rejected by all assignees, the task is updated as defined in the Fallback Options. If the fallback is set to "0" in priority mode, TMS does not assign second priority users unless all first priority users reject the task. The Fallback Options can be defined by creating a Planning setting and linking it to a Workflow Configuration. The default Fallback Options are: Calendar: Full Week (24/7) Behavior: Reset to New
Pool	When a task is assigned in the Pool mode, all the assignees of the pool see the task open for claiming at the same time. The first assignee who accepts the task, gets it. In the Pool assignments the Fallback Delay defines the time during which the task is open for accepting and rejecting for all assignees. If the Fallback Delay is 1 hour, the task is open for assignees to claim for only one hour, after which it expires if no assignee accepts it.
Priority See General	When a task is assigned in thePriority mode, the first prioritized assignee sees the task first, and can accept or reject the task before the assignees prioritized after her can accept or reject the task. In the Priority assignments the Fallback Delay defines how long the task is open for accepting or rejecting to a user, before also the next user in the priority can accept or reject the task. If the Fallback Delay is 1 hour, the second user sees the task after 1 hour (or after the first user has rejected the task). The third user sees the task after 2 hours (or after the both users before her have rejected the task).
Status	The status of the different Jobs and Job activities informs you whether the item is: Not Started In Progress Completed
Skip Delay	The Skip Delay controls the time period after which a task that has become active, is skipped if it is not accepted. When a Skip Delay is set: As soon as the task is active (current) the system triggers the Skip Delay When the end of the delay is reached, the Task is considered as SKIP (skip status, as if it was manually skipped) The On Skip property set to the activity in the Workflow Template defines which activity then follows If the task is accepted and then unclaimed, the skip delay is not reset Skip Delay is not taken into account for in-progress tasks, same as Fallback Delay If there is no assignee for the task, the Skip Delay is also taken into account
Threshold Delay and Threshold Date See Tasks	The Threshold Start Date is computed if the Threshold Start Delay is set in the activity settings. Threshold Start Date = Start Date minus Threshold Start Delay The Threshold End Date is computed if the Threshold End Delay is set in the activity settings. Threshold End Date = End Date minus Threshold End Delay
References See Documents	Any (additional) reference material useful to e.g. the End-user in performing the task. Reference material is not processed in any way, i.e. localized. Reference material is managed by the Project Administrator. See Documents.
Deliverables See Uploading deliverables and Deliverables.	Deliverable material uploaded to the TMS™ by the End-user. See Uploading deliverables LangAI External Service reports and Linguistic Toolbox reports are saved as deliverables in TMS. See Deliverables.
Home tab See Working with the Home Tab	The first tab displayed when you log into Lionbridge TMS™. It includes information about and links to user's: Received jobs Alerts (if any system error has occurred) New tasks In Work Tasks Contextual menu command for user's Profile Contextual drop-down list for Projects dedicated to the user Contextual drop-down command for creating new projects (if privileges are granted)
Dashboard See Using the User Interface	The area on the Home tab where the section headings are displayed.