1. Localization 3.0, Solution for SaaS Transformation
Anson Zhang

2. 1. Evolving Localization @ VMware 2. Next, Localization 3.0
Agenda
1. Evolving VMware
2. Next, Localization 3.0
, People’s Role
Tech Stack
Operation
6. Q & A
Transformation is on the air and truly the same at VMware.
It definitely demands out-of-the-box strategy and adventurous ideas to respond to the new and rapid changes. Localization 3.0 comes in as that response in alignment with our SaaS transformation, which requires fundamental changes today for various role plays including dev, globalization, translators and release, etc.
In this presentation, we will brief how localization evolves at VMware over the last two decades, followed to share some latest status and finally dive into the strategy, people and operation transformation to build an era of Localization 3.0 for another decade to come. 2

3. ？ Evolving Localization @ VMware
Localization 2.1 TMS with higher automations + offline vendors
Localization 1.0 Trados, Passolo + offline vendors
Before 2012 – 1.0
Since after until 2015 – 2.0
Over recent two years – 2.1
Localization 2.0 TMS with limited integrations + offline vendors ？
WE ARE HERE 3

4. L10n 2.1 @ VMware - UI Localization Automation
check-in localized files
source files in native formats
(properties, rc, strings …)
Translation Management System
pull source files
Middleware
xml2natives
natives2xml
TM for WS, etc
Profile / Project
The key idea is seamlessly integrate a middleware and WorldServer, and PM then need no longer to access to WorldServer from create, manage and close the project.
That middle tool servers as a core and as the center connecting PM, CMS and WorldServer to streamline the whole production. The tool checks out resources from for example Git, and then parse those files, saved in Database with customized string ID, and generate structured resource file for translation in a single format – XML.
PM creates a project in the tool and it will push it to WorldServer, and after translation, it will auto generate target files in their native file formats.
Impacts on conventional process:
Passolo no longer needed for translation which is a cost pressure on vendor side , and Vendor only work on text translation in single file format – XML.
Conventional vendor engineering service no longer needed.
Highly automated process from creating, managing to closing the project, all done in this midleware.
push source xml files to TMS
pull localized xml files from TMS 4

5. L10n 2.1 @ VMware – RN Publishing Automation
Workflow
ONE click to:
Auto fix language info in meta data.
Auto fix language code in URL links.
Auto push localized release notes to CDF Dropbox.
TMS
CDF Dropbox
IX Dashboard
Every 30 seconds to:
Scan new target files pulled from TMS.
Auto deploy to IX dashboard.
Go Live:
Stage
Prod

6. L10n 2.1 @ VMware – LQA Process Automation
QA Kickoff
Reviewers comment
Translators committing changes
BEFORE
Offline
NOW
TMS
LQE
Full integration
QA Kickoff
Reviewers commit changes
Online

7. 1. Evolving Localization @ VMware 2. Next, Localization 3.0
Agenda
1. Evolving VMware
2. Next, Localization 3.0
3. 3.0, People Role
Tech Stack
Operation
6. Q & A 7

8. NEXT @ VMware Localization 2.0 Localization 3.0
TMS with limited integrations + offline vendors
Localization 3.0
Seamless,
Intelligent,
Connected
2018 is our 20th Anniversary and onwards, we will embark on another decade milestone, for VMware and also for localization at VMware.
With the SaaS transformation goal of 2020 at VMware in mind and have the development and business model changes to adapt, and to support SaaS localization delivery, what’s next for us is exactly the Localization 3.0, which has fundamental different characteristics than the last two decades.
Localization 2.1
TMS with higher automations + offline vendors
NEXT
DECADE
Localization 1.0
Labor intensive
Trados, Passolo, etc 8

9. Localization 3.0 Strategy
100%
O2O
Cloud
Platform
Simplified
Experience
Automated
To prepare people, tech stack and operation to deliver at the speed of continuous deployment for SaaS transformation at VMware
Offline to Online
So, Localization 3.0 is the next state at VMware for delivering localized products and services especially mobile apps, SaaS applications and Web contents to our global customers. It is not just our new model but also a disruptive mindset to take to respond to our transformation. From strategy prospective, we will build well these 4 pillars
Its stack features deploying an one-for-all cloud-based platform, integrating to auto sync for a dynamic 100% automated E2E process, and bringing all partners/linguists fully online, plus empathizing for all the stakeholders in the whole lifecycle.
Adaptability
100% new mindset, skills and role play readiness for individual of the team
100% team readiness for Agile and SaaS model
Speed
100% centralized online translation and collaborations
100% source and target strings sim-ship for each deployment in a continuous cadence
Well-customized intelligent MT with mature adaption strategy in place for various contents
Agility
100% E2E localization delivery pipeline in place between upstream and downstream
100% responsive on demand to enable continuous translation of any words, anywhere, anytime and on any device
Empathy
Delighted customers
Delighted developers
Delighted x-functional teams
Delighted partners 9

10. 3.0, People’s Role Partners New mindset and expanded skill set.
Focus shift upstream (development and business).
Closer global customers engagement.
Data-driven.
Certify global linguists.
Rely more on product experts than pure linguistic professionals.
Build a global ecosystem for new partnership.
CONNECTED
People
Tech stack
Deliver right the first time.
Focus more on resources nurturing and management.
Reliable and available anytime, anywhere and on any device.
As product expert and localized market consultant.
Support continuous delivery transparency and new business model, etc.
On People transformation, changes will be adapted on both sides – Localization team at VMware and global partners and linguists.
TO DELIVER VALUES FAST 10

11. Powered on Automation, Agility and Speed
3.0 Tech Stack
String-based
Powered on Automation, Agility and Speed
Agile/SaaS application development, CI/CD
DEVELOPMENT
UI strings
Backend Service
L10n 3.0 Platform
Translation/PE + LQA
Product Backlog
SaaS SDLC
Translation/PE online
LQA online
Resource on-demand online
Continuous Localization
Continuous Localization Architecture for SaaS Delivery
User’s Application
Iterative Development
deployment
Iterative Localization
OTA Service
With people readiness, now let’s talk about tech stack we will need to enable localization 3.0. This is for string-based model.
Collaborations real time, online

12. Powered on Automation, Agility and Speed
3.0 Tech Stack
File-based
Agile/SaaS application development, CI/CD
Iterative Development
deployment
Iterative Localization
Product Backlog
SaaS SDLC
Powered on Automation, Agility and Speed
Continuous Localization
CI/CD
REPOSITORY
UI resource files
User’s Application
This is for file-based model
Sync
L10n 3.0 Platform
Translation/PE online
LQA online
Resource on-demand online
Translation/PE + LQA
Collaborations real time, online
Continuous Localization Architecture for SaaS Delivery

13. 3.0 Operation – Typical Process
L10n Process 3.0
Sync source
strings or files
Leverage
from TM and then MT
Post Edit
by global partners
Sync targets
Live update
for continuous deployment
Now, basing on the infrastructure we are building, this graphic shows a typical localization life cycle. The highlights are push/pull for a seamless end-to-end automation. 13

14. 3.0 Operation – Continuous Process String-based
Push and pull
Agent
Application
Continuous Localization FR
…..
L10n 3.0 Platform DE
Service
And, let’s take a closer look how we push source and pull target translations for string-based model.
Scan, push and pull 14

15. 3.0 Operation – Continuous Process File-based
Development Sprint
3 - Deployment
Test
Stage
Prod
2 – Master branch
1 – Feature branch
And, this illustrate how we sync source and target files to provide a dynamic localization for the file-based model.
0 - Private
sync
sync
sync
sync
sync
sync
sync
Continuous Localization
sync
sync MT
MT + PE 15

16. 3.0 Operation - Localization Platform
Support traditional projects
Enable continuous localization
Workflow management with auto assignment
Intelligent MT
Quality management
Service rating
Finally, to support both models and enable continuous delivery, we need a one-for-all localization platform, and it is far beyond of traditional translation management system.
Besides of providing core features for daily operations of project managers and translators, it must simplify.
Real-time collaborations (linguistic query, IM, discussions, support online)
Self-service
Partner management
SDK/APIs (for integrations, customizations, data-driven requirements, etc.)

17. Changes never stop, yet faster today and will be tomorrow.
What else
Changes never stop, yet faster today and will be tomorrow.
SELF EVOLUTION of people, tech stack and operation are the key
to be aligned all the time with the new changes.

18. Q&A thank you Product Localization, VMware on behalf of Anson Zhang,
on behalf of
Product Localization, VMware