Contests

Company Name: Assa Abloy Opening Solutions (Americas Division)

Company URL: https://www.assaabloy.com/

Example Website: https://www.hesinnovations.com/

Your Name: Pawan Gupta

Your Title: Sr. Tech Program Manager

Our company is the leader in door & security solutions. The implementation which is referred here is for Assa Abloy Opening Solutions Americas Division.

The journey has started more than a year before when we have decided to migrate all our legacy web sites and digital functions from old platform EPiServer to AEM AaCS. The reasons for migrations were

1. Create digital journey for end user to support marketing growth dynamically
2. Remove static non centralized content management without self-publishing model
3. Advance into digital functions to support lead generations for B2B and B2C markets, personalized content delivery, eCommerce, visibility in process and flow etc…
4. Go to market fast
5. Advance learning platform

We have not done “As is” migration but introduced advanced digital journey and feature while migrating the sites.

As we are product-based company but obvious we want to support features improving B2B and B2C segments via including architecture design around eCommerce (magento), personalization/preferences, lead generation, support, order fulfillment process from underneath system, assets & content managements and more important clarity within system from sales to marketing and underneath operations.

Some of the unique designs/features we have implemented to overcome business challenges are:

1. Our entire implementation relies on AEM OOTB OSGI configs and Context aware configs to provide flexibility to switch integration per site basis (opt in or opt out features available per site basis to support dynamic nature)
2. APIM Springboot acting as integration layer for serving products integration both from Agility PIM (source of truth for all products) for non-eCommerce and Magento for eCommerce sites. APIM Springboot layer decides based on site context configs. We have also implemented OOTB CIF for same components just via context configs (so with that our implementation now fits all flavors of product-based sites for commerce or non-commerce). Light weight product search enabled via Algolia
3. Agility PIM product sync to Magento or AEM is dynamic and schedule basis to support dynamic nature of site to promote products and features
4. Oracle DAM is powerful asset management platform and we integrated it via Azure Applogic to push only necessary assets to AEM for rendering on schedule basis per sites again from context aware config
5. DAM assets search on top of Oracle DAM but header/footer and theme of search pages dynamically delivered from AEM to support the branding
6. Entitlement based content delivery via AEM campaigns and segmentations
7. GA/GTM/Matomo integrated dynamically per site basis via context aware configs. Data used for lead generation and follow ups
8. MS Dynamic Server and Client-side integration for commerce and non-commerce sites for lead generation and support via Salesforce. Again, based on context aware configs to support dynamic nature
9. Dynamic Search via integrating AEM through Kafka with Solr to index page dynamically after page publish/unpublish
10. Configuration based theme design for individual sites and supported by template/components (similar as styling system but site level)
11. built components sites to show case each components functionalities in different break points and enable self-publishing model

Our high-level architecture is as below. Some of dotted lines are still in progress…

Note: The dotted lines indicate current in progress.

Significant wins:

            After implementing the core platform based on above architecture, we saw a great shift in

1. Self-publishing model: Our business team has a huge shift in managing their sites & content with great turnaround ratio to make marketing content live. They became independent for their day-to-day site management activities
2. Improved Lead Generation: As a result, from above, business now plans and start executing great benefits of true content management platform as content optimization, user journey, personalization and tracking/analyzing the data for engagement leads
3. Go To Market: New business interest to engage & build sites on AEM because of available capabilities to support the go to market timelines & goals
4. Improved business methodology: B2B and B2C relationships get better in terms of eCommerce features & implementations, direct connection with business along with fulfilling market needs
5. Speed up with market:
   1. With AEM AaCS faster release cycle helping business to drive go to market strategy on time and quality
   2. Launched 26+ multi languages sites in last 4-5 months and will launch rest 30+ sites with same pace because of self-publishing & faster release cycle support (with increased productivity)
6. Centralized & dynamic learning: AEM to Docebo integration makes a success story for our end customer to take courses and training on products
7. Onboarding new business and sites comes with ease