Can’t find a document because it is written in 3 different ways?
Technical documentation can have ambiguities such as naming an item in different ways in different places. With EKR Orchestra this risk is reduced to zero.
Bring order to chaos
Let’s talk about the importance of ambiguity or unambiguousness in technical documentation. When a company produces a machine, this is composed of many parts and each body in the company names those parts several times in the bill of materials, in the technical documentation and often that information is named within the control software that manages the data of car. Often the same machine parts are called in just different ways and, as each time they are called differently, a different translation is required, it can frequently happen that within a technical document or within a localized machine software in language the same objects have completely different names. This causes ambiguity in the end user and sometimes real risks of misuse of the machine.
By introducing Ekr Orchestra this ambiguity is reduced to zero as there is a terminology management process that ensures that each machine component, when created, is baptized by the Information Owner (person who has the task of creating it) and all the entities in the company that refer to that component use exactly that term or set of words without ambiguity as a reference.
The same translators will only translate that name, that concept and it will always be translated in the same way in any translation occurrence within the company.
This will guarantee the company to reduce to zero an often costly ambiguity, which can generate a wrong use of the tool and give a perception of reduced quality or sometimes even legal problems.
Ask immediately for a meeting with an Ekr representative to introduce Ekr Orchestra for the optimization of your company’s vocabulary.