BeLazy's AI Hub allows you to perform automated operations on exports from translation management systems.


Two directions

The BeLazy AI Hub distinguishes between two directions:

  • when the translation management system project is set up prior to BeLazy's processing, i.e. the TMS project comes from the Content and Project Hub,
  • when the translation management system project is set up by BeLazy via the TMS Processing Hub.

In this article we will refer to the first scenario as "From TMS" scenario, and to the second scenario as "Into TMS" scenario.


The export process

Translation management systems can generally export and import XLIFF files. BeLazy offers this XLIFF export-import at every step of the TMS workflow.

However, not every system includes all information in their XLIFF exports and update all information via XLIFF. For example, Phrase TMS does not store comments in XLIFF. Crowdin and others do not store most of the segment status and other information in XLIFF. Therefore BeLazy developed a JSON-based localization format that is exclusively used for AI Hub operations, especially with large language models. BeLazy does not only convert the XLIFF into JSON, but uses a combination of XLIFF export and API operations to gather all data that can be necessary for AI processing, and performs an XLIFF import and API operations to update the data in TMSes. This way LLMs have full access to fields and attributes that may be important to perform certain operations, for example match rate, comments or locking.


Automated BMS steps

In BeLazy's workflow the central workflow is not the TMS or the source workflow, but the BMS workflow, because this can be arbitrarily changed and extended in any systems supported by the Business Management Hub. More than one BMS workflow step can belong to one origin system (From TMS) or one TMS Processing Hub (Into TMS) step, therefore this is the ideal place to include automated steps.


An automated BMS step consists of exporting the content, processing the content, importing the processed content and closing the BMS job. No matter whether you work with the APIs or automated steps via BeLazy's own integrations, this is the approach we take.


The API-driven workflow

BeLazy is an API-first application, therefore the XLIFF export - transformation - import logic is available through exclusively relying on the BeLazy APIs. This works both in the case of From TMS and Into TMS scenarios.


The automated workflow steps

Automated workflow steps are configurable actions performed by AI providers with configuration stored using presets. This can be set up via the workflow mapping. Currently only Into TMS scenarios are supported.