Presented at 3|SHARE's EVOLVE'15 - The Adobe Experience Manager Community Summit on August 18th, 2015 at the Hard Rock Hotel in San Diego, CA. http://evolve.3sharecorp.com

1. AUGUST 17, 2015
AUTODESK GLOBAL LAUNCH & LOCALIZATION
Benjamin Delman & Sharat Radhakrishnan

2. 2
ABOUT AUTODESK
Autodesk, Inc., is a leader in 3D design, engineering and
entertainment software. Since its introduction of AutoCAD
software in 1982, Autodesk continues to develop the broadest
portfolio of 3D software for global markets.
Customers across the manufacturing, architecture, building,
construction, and media and entertainment industries—
including the last 19 Academy Award winners for Best Visual
Effects—use Autodesk software to design, visualize, and simulate
their ideas before they're ever built or created.

3. 3
AUTODESK.COM TIMELINE

4. 4
AUTODESK.COM LOCALIZATION EVOLUTION
Year1 Year 2 Year 3

5. 5
Launch Rebranded, Re-designed Global site on new
CMS (CQ5.5) on the same day (Big Bang Launch)
• 24 Languages
• 39 Local sites
• 1000’s of pages
YEAR 1 (2013) : VISION

6. 6
1. Enable Publishers, Editors, and Local Marketers
across the world
2. Local sites to have syndicated content & local
market content
3. Content Personalized by Location on Global site
4. Annual Global Launch across all sites
YEAR 1 : GOALS

7. 7
YEAR 1 – CQ/AEM SYSTEM ARCHITECTURE
01
Author
02
Author
AEM
Publish(s)
Localization
Process
CQ5.5 Active Cluster
Adapter
Vendor VendorVendor
Activation

8. 8
1. Scale :
• 1500+ EN Pages  24 languages  39 local sites
• 30,000+ Translation Jobs : Start  Finish in just 3 months
• Support updates to existing sites during this phase
• 500+ Global Authors & Editors
• Author Clustering out of sync (CQ 5.5)
2. Dashboard & notifications
3. Components with Composite-multi field properties
4. Referenced & Shared content areas
YEAR 1 : CHALLENGES

9. 9
COMPONENTS WITH COMPOSITE MULTI-FIELD PROPERTY
Translatable
Fields
Translatable & non-translatable values get stored In the same JCR property separated by de-
limiters making it difficult to filter for translation

10. 10
YEAR 2 (2014) : ANNUAL GLOBAL LAUNCH

11. 11
1. Reduce overall marketing localization cost by 30%
2. Reduce time to market for localized web content by
50%
3. Maintain or improve quality of localized marketing
content
YEAR 2: VISION/GOALS

12. 12
Enable continuous localization process
• by connecting and automating web production and
localization workflows
Reduce vendor dependency
• by taking full control of strategic components (TMs, glossaries,
systems, reporting)
Move from single to multiple-vendor model
Utilize more cost-efficient vendors
Remove Clustering; Move to single Author
YEAR 2: STRATEGIES

13. 13
YEAR 2 – AEM SYSTEM ARCHITECTURE
MySQL
AEM
Author
5.6.1 LS
Vendor VendorVendor
Information
Architecture
& Content
Web Services
Layer (OSGi)
Supports AEM Dashboard for Localization
• Projects
• Jobs
• Deliverables
• Reports
Autodesk Localization Services (LS) System:
• Translation Memory
• World Server, Athena
• Vendor Management
AEM
Publish(s)
5.6.1
Activation
Adapter

14. 14
INFORMATION ARCHITECTURE
• /content
– /autodesk
• /global
– /en
– /fr
– /es
– /de
• /europe
– /france
– /spain
• /north-america
– /mexico

15. 15
INFORMATION ARCHITECTURE
• /content/autodesk/global
– /en
• /products
– /autocad
» /overview
» /free-trial
» /buy
– /fr
– /es
– /de
• /content/autodesk/europe
– /france
– /spain
• /content/autodesk/north-america
– /mexico

16. 16
INFORMATION ARCHITECTURE
• /content/autodesk/global
– /en
• /products
– /autocad
» /overview
» /free-trial
» /buy
– /fr
• /products
– /autocad
» /overview
» /free-trial
» /buy
– /es
– /de
• /content/autodesk/europe
– /france
– /spain
• /

17. 17
INFORMATION ARCHITECTURE
• /content/autodesk/global
– /en
• /products
– /autocad
» /overview
» /free-trial
» /buy
– /fr
• /products
– /autocad
» /overview
» /free-trial
» /buy
– /de
• /content/autodesk/europe
– /france
• /products
– /autocad
» /overview
» /free-trial
» /buy

18. 18
LOCALIZATION DASHBOARD (AEM)

19. 19
END-TO-END LOCALIZATION PROCESS
1.  Author creates project
2.  Author creates job
3.  Export job
4.  Localization translation
5.  Localization adapter checks for new translations (5
minutes)
6.  Localization adapter creates translated content nodes
7.  Rollout to local sites
8.  Activate local site content (LIVE)

20. 20
1. Goal: Reduce overall marketing localization cost by 30%
• Reduced global content localization cost by 23%
1. Goal: Reduce time to market for localized web content
by 50%
• Reduced time to market of localized content by ~35%
1. Goal: Maintain or improve quality
• Quality tracking and reporting did not work accurately
• Anecdotal feedback indicates decrease in quality (varies
depending on language and content type)
YEAR 2: WHAT WE ACHIEVED

21. 21
Ability to edit current and future states of page is
critical:
1. Content versioning did not scale
• Template changes aren’t supported
• Bulk version changes aren’t supported
• Versions can be out of sync when localized content is
imported
• No system level checks; prone to errors
YEAR 2: LESSONS LEARNED

22. 22
Ability to edit current and future states of page is
critical:
2. Renaming nodes did not scale
• Publishing overhead
• Each rename in blue-print affects references in 23
languages & 38 local site pages
• Systems resource consumption Is high
• Daily Authoring environment restarts
YEAR 2: LESSONS LEARNED (CONTD.)

23. 23
YEAR 3 (2015) : ANNUAL GLOBAL LAUNCH

24. 24
1. Ability to edit current and future states of
multiple pages
2. Reduce publishers’ overhead
3. Increase system stability
4. Support Personalized Content (campaigns)
YEAR 3: VISION/GOALS

25. 25
AEM LAUNCHES:
1. Create a branch (a launch) of the existing
content
2. Edit content of the launch
3. Promote the launch to replace production
version on author
4. Activate the content
YEAR 3: STRATEGIES

26. 26
/content ../launches
/autodesk /autodesk
/global /global
-en -en
/Products /Products
/Autocad /Autocad
-fr -fr
/Products /Products
/Autocad /Autocad
AEM LAUNCHES
Challenge with our localization process
• AEM launches is a great
feature for content areas that
exist on our Global En site
• It didn’t solve all of our
localization challenges
• Didn’t support template
changes
• Duplicate live-copy
relationships
Live-copy

27. 27
YEAR 3 – AEM SYSTEM ARCHITECTURE
MySQL
AEM
Author
5.6.1
Adapter
LS
Vendor VendorVendor
Content for
Global Launch
Web Services
Layer (OSGi)
Supports AEM Dashboard for Localization
• Projects
• Jobs
• Deliverables
• Reports
Autodesk Localization Services (LS) System:
• Translation Memory
• World Server, Athena
• Vendor Management
Prod. Content
2nd
Author
5.6.1

28. 28
Y E AR 3 – AE M SY STE M ARCHI TECTURE (CONTD.)
AEM
Author
5.6.1
Content for
Global Launch
2nd
Author
5.6.1
AEM
Publish(s)
5.6.1
Localization
Process
Localization
Process
Migration of content in Batches (manual
process) & cleared replication status on
nodes using a simple custom script
OOTB AEM Replication
Agent to migrate Global
Launch Content
Activation
We got this idea at
Evolve last year

29. 29
1. Goal : Ability to edit current and future states
of multiple pages
2. Goal: Reduce publishers’ overhead
3. Goal: Increase system stability
4. Goal: Support Personalized Content
(campaigns)
- Couldn’t complete this due to other priorities
YEAR 3: WHAT WE ACHIEVED

30. 30
1. Global Campaigns:
• AEM Campaign content section doesn’t have the
same Blueprint/live-copy mechanism
• Publishing overhead to replace campaign teasers
manually on every local site
2. Meta-data & Content Tagging Strategy is crucial
YEAR 3: LESSONS LEARNED

31. 31
YEAR 4: 2016 ANNUAL GLOBAL LAUNCH

32. 32
1. Support IPM Localization : In Product Messaging (IPM) is
relevant content delivered to our customers directly in
their product/trial
2. Automate Process to migrate content from Prod. Author
to 2nd author
1. Support localization of Personalized Campaign Content
2. Implement a new tag hierarchy& bulk tagging process
3. Improve Quality
YEAR 4: GOALS/VISION

33. 33
YEAR 4: STRATEGY
• /content
– /campaigns
- /homepage-banner
- /content-for-segment-A
- /content-for-segment-B
• /content
– /autodesk
• /global
– /en
- /campaign-data
-/homepage-banner
- /content-data-for-segment-A
- /content-data-for-segment-B
– /fr
-/campaign-data
-/homepage-banner
- /content-data-for-segment-A
- /content-data-for-segment-B
– `
Reference
component In addition, we modified
Teaser Component to
pickup content from right
locale if used on a local site

34. 34
facebook
facebook.com/autodesk
twitter
twitter.com/autodesk
linkedin
linkedin.com/autodesk
QUESTIONS?
Benjamin Delman
Product Manager
Web Delivery
Industry Strategy & Marketing
DIRECT +1 415 675 8221
MOBILE +1 415 203 8221
benjamin.delman@autodesk.com
Sharat Radhakrishnan
Principal Engineer
Web Delivery
Industry Strategy & Marketing
DIRECT +1 415 539 4894
MOBILE +1 312 860 7525
sharat.radhakrishnan@autodesk.com
Autodesk, Inc.
One Market Plaza
San Francisco, CA 94105

35. 35