The Importance of TMS scalability and Longevity
How Rubric Helped a Client Overcome TMS Limitations
When our client’s TMS could no longer handle the size of their files, the tool became a roadblock. Luckily, they partnered with Rubric and we had the knowledge, expertise, and tools to work around the limitations of the TMS.
A common issue with TMS platforms is scalability and longevity. As a client’s business grows and evolves, a TMS that initially seemed like a dream ticket, proves unable to keep up with increasing demand and content complexity.
This is undoubtedly frustrating for the client, but as a trusted localization partner, we can ease the burden and provide support and practical solutions.
The Challenge: TMS Scalability
One of our clients (who wished to remain anonymous) purchased a cloud-based TMS, which is designed to be a secure and efficient way to manage, store and collaborate on translations, regardless of format or location.
Unfortunately, this client quickly found that their TMS couldn’t handle files for a new content type (from their Product Information Management system or PIM). This resulted in system crashes during the project set-up and client-side reviewers found themselves unable to load files in the online editor.
Despite the client reaching out to the tool provider, progress was frustratingly slow.
It was vital that this content be localized in a timely manner, so Rubric implemented a workaround and were able to set up the project.
A Custom Approach: Working Around TMS Limitations
Eventually, Rubric identified the maximum workable file size: a disappointingly small 4MB.
Armed with this information we developed a custom automated process to split the files at the maximum size. They then need to be uploaded in small batches for the project set-up to succeed.
It’s progress, but it’s not perfect. We have automated the upstream process as much as possible, but the workaround still takes up unnecessary time and effort and means the process is inherently inefficient.
It’s a classic example of why scalability and longevity are key things to look for in a TMS. Susannah adds:
领英推荐
“When they bought this TMS this project wasn’t on the horizon, it came later and their TMS is not fit for the job. Luckily, they work with us so we can work around the problem.”
Susannah, CEO
More than 12 months later, the online editor issue remains unresolved by the tool provider but the cause has been identified – it is the large Translation Memory (TM) that is causing the online editor to crash, but reducing TM size is not a viable option without impacting content quality and consistency.
Rubric worked around the limitation of the TMS, but the shortcomings of this feature are a big disappointment to our client. Allowing in-country reviewers to see TM matches in the online editor whilst reviewing was an important factor in their decision to purchase this TMS over its competitors.
A partnership that gets more from your TMS
Rubric have seen it all when it comes to TMSs—we’ve experienced plenty and we can often help fix or work around problems clients have with their TMS.
Common TMS limitations and Rubric’s approach:
TMS limitations are often in-built or out of our control. Our experience is that TMS tool providers often prioritize client-facing features over functionality for the heaviest users – translators and project managers, impacting the tool’s efficiency and effectiveness, and the time, cost and quality of translation projects.
At Rubric, we look at every step in the client’s workflow and find the best tools and technology to handle each task, whether it’s our bespoke tools, or another best-in-class solution.
We call this big-picture approach orchestration and it involves us plugging into clients’ own TMSs to streamline and optimize the entire workflow.
Another option that can save clients a lot of hassle is to use our TMS, instead of buying their own. This allows us to handle configuration and be agile, taking action to resolve problems swiftly. By administering our own TMS we can optimize and customize it to meet our clients’ needs—unlike in this story, where we didn’t administer the client’s TMS so were unable to implement any fixes in the tool itself.
No TMS is perfect, but at Rubric we’ve got your back. When you partner with us, we’re committed to making your global content localization as efficient as possible.
Get in touch with us for help with your TMS.
You can read the full case study here.