Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Studio Ideas
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
This topic contains condensed instructions to get you to quickly start working with SDL SDL Trados Business Manager.
First of all, when you run SDL Trados Business Manager for the first time (clean installation), you will be prompted to enter a password. By default, user name is Admin, and password is User@TBM. After logging in, you can select Security > Users (or click User icon on the top toolbar and select Manage user), then open Admin user and change its password (and even set to blank, so logon window won't appear when you launch TBM).
The more settings and reference data you enter to begin with, the better. But it is hard to fill in this type of baseline information in any program until you get a feel for the program itself. Here are the minimum fields that must be completed before you create your first job.
First of all, open application settings and go through all tabs and regions. There are a lot of settings which you can configure, and their description is provided in the Application settings article. However, main settings which is recommended to check before starting are:
After setting application parameters, it is recommended to go through all reference data tables and add necessary data where needed.
Of course, it is not mandatory to create all reference data in advance, because any reference data can be created on fly, when it's needed. However, while you start to use application and may be not familiar with its UI, it's better to create some data in advance, which allow not to distract on reference data creation when filling documents. For example, have a look at a translation job creation screen:
If you don't have necessary customer in the database, you can click Plus icon to create a new one. Job form will be greyed out, and a popup dialog will appear:
Here, you fill new customer's data, click OK, and it will be automatically selected in the Client field.
This step is optional, and you can directly move to a translation project creation. However, when you have a quote, project can be created using a single click.
To fill quote items, you have a few options:
Click SDL button and import a GroupShare or Trados Studio project.
Add quote items manually. In this case, click New button above the table and fill task information: Here, when you select service type, language pair, fuzzy type and unit, price will be determined automatically based on a client's price-list and selected fuzzy scheme.
Click Print button on the toolbar. You will see print preview dialog: Click Export to button to save generated document in one of supported formats.
When you receive a confirmation from a client, either in quote list or quote detail view, click Accept quote button. A new translation project will be created, along with translation jobs. The number of created translation jobs will correspond to a number of language pairs specified in a quote.
Source files will be automatically moved to a created project.
Translation project is a "box" for translation jobs. While translation project could have a single source language and multiple target languages, translation job always have a single language pair and possibly multiple tasks. Each task describes amount of work which should be done (for example, translation of 1000 words, or 3 hours of interpreting). Translation job describes amount of work which our company is going to do for our client (or ourselves, if our company is a content creator). For each task (or all tasks) in a translation job a translation assignment can be created, which could be assigned to some vendor (freelancer translator or LSP).
Translation projects allow to handle this by controlling a set of translation jobs and their assignments on a single screen. You can create translation project from a quote, manually by creating a new project or by cloning some previous project.
Here is an example of a procedure:
After delivering some jobs/projects, you can create invoices over them. There are few options to do that.
In the invoice list, you can quickly find unpaid invoices using filters. Overdue invoices are marked with special icon in the Payment term column.
Basic information about your current state and performance can be found on the Dashboard. Default dashboard provides information about ongoing jobs, unpaid invoices, as well as charts displaying total earnings and turnaround. So, dashboard could provide overview of a current state. If to add possibility to customize dashboard by adding custom views with custom filters, you can configure it to display almost any data contained in the database.
However, for more extensive insights you can view reports. Most interesting part here is QuickReports. They provide dashboard-style reports with quick filters and different ways of representing data, including simple and pivot tables, charts, scatter charts, cards, gauges, and even geo maps. Here is an example of such report:
There are plenty of built-in reports, and you can use them as a basis to create custom reports.
This article described only very basic description of the workflow used in TBM. Of course, it could be more complex and customized. For example, quote could be created by a client using a portal, application could send notifications to users upon different events (quote submitted, quote ready, job offer arrived, etc.), you can manage tasks and receivables in jobs separately, you can simplify project creation by importing data from existing GroupShare projects, or you can send files directly to Studio to generate project and analysis and immediately import it back to a project, you can pickup vendors based on vendor groups and machine learning system, you can send job offers to different vendors and compare them on a single screen to select the most suitable one, you can register incoming invoices, create credit notes, etc. Additionally, customization possibilities allow to create custom views for different users, custom filters, and security system allows to create limited access areas with granular control up to individual fields, allowing you to separate data between users depending on their rights and responsibilities. Printing templates (quotes, invoices, etc.) also can be customized using extensive visual designer allowing to control absolutely every part of a generated document, and localized up to 4 different languages.
This user's manual contains detailed information about each aspect of the system. Where possible, articles contain (or will contain) short videos demonstrating described functionality. We recommend you to carefully read the documentation, use search to find answers on your question, and don't hesitate to reach us on forums with your suggestions, questions and comments.