The client uploads files from a new translation job into their Business Management System (BMS). The Automator connects to the client’s vendor portal, accepts the new job, creates a new project in its own BMS and downloads the project files from the vendor portal. The project files may or may not be manipulated as described in Scenario 2. Let’s imagine the client uploads XML files and a translation memory, and wants to receive the files back. In this case, the Automator uses memoQ and creates a template to process the XML files.
These are the steps involved in this scenario:
1. vendor delivers in CAT tool only,
2. vendor delivers in vendor portal only,
3. vendor delivers in both systems.
Ultimately, it is always best if the project task is marked as delivered in both systems, so automation here is highly useful. Finally, when the job is finalized, the delivery of the files in the vendor portal must be preceded by a download of the deliverables from the CAT tool.
This is a highly complicated workflow, though very useful in large projects.
PREREQUISITES FOR AUTOMATION
There are few business management systems – Plunet, XTRF, LBS Suite and Protemos – that already support project management in a CAT tool. It depends on the CAT tool whether project packages can be imported via APIs or only as translatable files, thus some automation already exists, but it is very limited.
THE BELAZY SOLUTION
At this point, we are listening to user requirements and integration possibilities between business management systems and CAT tools. Rather than reinventing the wheel, our goal is to convince business management system providers and CAT tool providers to improve their integrations and support end-to-end automated workflows. We are open to implementing workflows that do not interfere with the business goals of our business management system partners.
CLIENT’S VENDOR PORTAL
AUTOMATOR’S OFFLINE CAT TOOL
Try BeLazy with your team
Tell us more about your workflow and we will get back to you shortly