Bombardier adobe aem msm implementation
Download as PPTX, PDF6 likes1,547 views
The document presents a case study on Bombardier's implementation of the AEM Multi-Site Manager, which facilitates managing multiple localized websites across 46 countries. It discusses challenges regarding governance, content syndication, and user management, as well as the importance of balancing global and local needs. Key lessons emphasize the significance of content production and adopting a minimal viable product approach in development.
Bombardier adobe aem msm implementation
- 1. July 9, 2015 AEM Sites: Multi-site Manager Bombardier Country Sites Ken Knitter, Bombardier Inc. Alberto Vázquez, w.illi.am/ a Valtech Group company
- 2. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager2 / • AEM multi-sites introduction • Case study: Bombardier Country Sites • Questions TABLE OF CONTENTS Table of contents
- 3. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager3 / Multi-sites introduction
- 4. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager4 / Managing multiple sites in AEM MULTI-SITES INTRODUCTION Independent sites • Built as different applications • No association between sites Multi-site Manager (MSM) • Create a website that is used as a template for multiple sites • Strong association between sites • Share templates and components • It allows us to manage a single source for the content that is easily
- 5. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager5 / • The most common use cases are − Sites in multiple countries. − Sites in multiple languages. − Need to reuse the same content in multiple places like product catalogs. When should we use it? MULTI-SITES INTRODUCTION
- 6. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager6 / Case study
- 7. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager7 / Challenges • Bombardier has a presence in 46 countries • Over 15 countries have localized websites • No efficient way to launch global communications • Cost, effort and time to launch each site dependent on many external factors Key Questions? − Do we localize the primary web site? − Do we create smaller country-based websites? − Do we leverage other channels (e.g., Social Media) to represent in-country activities? Business case CASE STUDY: BOMBARDIER COUNTRY SITES
- 8. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager8 / Objectives • Ensure governance • Content syndication • Multilingual • Local enablement • Scale • Costs Business case CASE STUDY: BOMBARDIER COUNTRY SITES
- 9. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager9 / Governance Challenges • Difficult to maintain consistent branding and content across all sites • Many stakeholders at the table. Each with their own budget and team: − 6 Business segments − Shared business − Different organization structure • Balancing global and local needs Business case CASE STUDY: BOMBARDIER COUNTRY SITES Country Site B Inc. Business Aircraft Commercial Aircraft Aerostuctures Product Development Engineering Transportation Human Resources
- 10. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager10 / Implementation
- 11. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager11 / • Global Blueprint − Based on previous AEM projects − Only accessible to the global team − Rollout global changes as needed − New language branches as needed • Country Live-copy − Country team access only to country site − Local team manages content identified as local − No access to edit pages with global content − No rights to break inheritance of selected components Global + Local CASE STUDY: BOMBARDIER COUNTRY SITES
- 12. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager12 /
- 13. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager13 / • Multiple user groups are involved − Global authors o Permissions to create and edit, content in the global blueprint and country sites o Allowed to roll-out changes to the country sites − Local authors o Able to edit content on the allowed sections of the local site o Not allowed to publish content − Local publishers o Able to edit and publish content on the allowed sections of the local sites User management CASE STUDY: BOMBARDIER COUNTRY SITES
- 14. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager14 / • Blueprint Live-copies − Global to country • Shared services content − News − Events − Biographies − Media galleries − FAQs − Contacts − Country information − Physical sites information − Projects information • DAM Assets Content Syndication CASE STUDY: BOMBARDIER COUNTRY SITES
- 15. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager15 / LESSONS LEARNED
- 16. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager16 / • Before CMS • Promise of CMS • CMS Reality Curse of the CMS LESSONS LEARNED
- 17. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager17 / • 9 times out of 10 technology identified as the issue. • However once the technology is delivered the content rarely follows. • Content production is hard. Most communication teams are not structured for full and regular production. − “Creating content for a brand is like running a news room” (Tara Hunt 2013) − “the newsroom-like style in which we now manage our social media activities” (David Edelman & Marc Singer 2012) • Remember content is currency on the web, not the underlying technology. Let me wave my content magic wand LESSONS LEARNED
- 18. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager18 / • Resist the urge to solve the problem on the first development attempt • Use minimal viable product (MVP) approach to launch and understand real requirements You don’t know what you don’t know LESSONS LEARNED
- 19. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager19 / QUESTIONS
- 20. © 10.07.15 – Case Study: Bombardier AEM Multi-site Manager20 / THANK YOU!
Editor's Notes
- #6: For example: Want to use the same templates and components. Automatically update one or more sites based on a source site. Enforce a common base structure and use common content across multiple sites. Maximize the use of available resources. Maintain a common look and feel.
- #9: Governance: ensure consistent branding, quality, and content veracity Content syndication: allow the easy publication of content across multiple sites Multilingual: Need to support multiple languages Enablement: allow countries to have their own sites and local teams to focus on content Scale: manage all sites within the platform. Both live-copies and stand-alone websites Costs: control costs for launching, maintaining, hosting sites
- #10: 6 Business Segments (each with their own PR & Communications team). Shared business functions such as HR and country reps. Different organization schemes in business Aerospace-based segments organized around products Transportation segment organized on a regional-basis
- #12: Country site structure was defined prior to starting the project. This already streamlined structure helped to be the basis of the blueprint (we called it global). This ‘blueprint’ is in reality half the content since it only has the ‘global’ content. Each country has to decide which pages/sections of the global blueprint they want, and then they need to manage the local content.
- #13: Country site structure was defined prior to starting the project. This already streamlined structure helped to be the basis of the blueprint (we called it global). This ‘blueprint’ is in reality half the content since it only has the ‘global’ content. Each country has to decide which pages/sections of the global blueprint they want, and then they need to manage the local content.
- #14: Change management is very important, structure and processes must be aligned with system capabilities. In most cases a revision of processes and teams is needed.
- #17: Before CMS Web masters edited pages by hand taking care of form and content at the same time Promise of CMS Web masters would be freed of page to page creation and editing workload as communicators would be able to easily add their content in WYSIWYG editor CMS Reality Web masters or “digital” team still does majority of web page creation and editing Non-digital communicators lack capabilities to edit their own pages not in system frequently enough high level pressure for digital transformation not present per user licensing limits access free play environments not present
- #18: Required reading: Tara Hunt (2013) Let me wave my content magic wand. http://bit.ly/1ezKar4 9 times out of 10 technology identified as the issue. We need x technology in order to do y. However once the technology is delivered the content rarely follows. Our first country site saw no new content in 1st year after delivery. At 1.25 years the first edits came in and the central digital team was left to do the work as the local editors had not used the system in so long that they did not retain the training.