Skip to content
Japanese Automotive OEM — Asia-Pacific Regional HQ

One certification engine for five dealer-quality programmes across Asia-Pacific

The regional HQ's dealer certification ran on Excel macros on one staff member's PC, so every new programme, market or Office update put it at risk. We compared the options, designed for the people who would run it, and replaced the macros with a serverless cloud service. It now issues certificates, sends reminders and produces reports automatically, and has run under a managed-service SLA for more than three years.

5

programmes on one engine

1,000+

Dealers across around 10 distributor markets in scope

Automotive & MobilityBusiness ApplicationsManaged Services~10 distributor markets2022 – present4 min read
Client
Regional HQ of a Japanese automotive OEM
Users
Regional HQ, distributors in around 10 markets, 1,000+ dealers
Scope
Process redesign · Build · Go-live · Managed service
Timeline
2022 proposal → 2023 go-live → Run & Kaizen 2024–
Team
Consultants, bilingual bridge engineers, AWS engineers
3yr

Re-certification cycle tracked with automatic reminders and expiry notices

0

Local installations: no dependence on PC, OS or Office versions

3yrs+

In continuous operation under a managed-service SLA

The challenge

Certification depended on one laptop and a handful of macros

The regional HQ runs several programmes that check whether dealers meet the brand's standards for service quality and body & paint work. Distributors in each market send in evaluation sheets. The regional HQ combines them, issues certificates to the dealers that pass, and reports to its global headquarters.

All of this ran on three Excel macro tools on one staff member's PC: one combined the sheets, one wrote the emails, one created the certificates. As more programmes and more markets were added, the setup became fragile. And the three-year re-certification cycle had not started for most programmes.

Fragile environment

Every Windows or Office update, and every new PC, put the tools at risk.

Vendor for every change

A new dealer, a new signature or a new evaluation item each needed manual changes to the macros.

Errors nobody could trace

Problems depended on the local machine, so they were hard to reproduce and slow to fix.

Our approach

Compare the options honestly, then build for the people who will run it

We started by setting out what would change over the next few years: new dealers, new signatories, new evaluation items, staff turnover and PC replacements. We then scored three options against those changes before choosing one.

CriteriaCloud managed serviceExcel macroMacro + RPA
Maintainability (dealers, e-signatures, staff handover)●●●●●
Operational constraints on staff PCs●●●●●
Manual effort and speed of fixing errors●●●●●●
Predictable recurring cost●●??
REGIONAL HQ AWS · SERVERLESS Evaluation sheetuploaded per distributor Distributorsreceive certificates Regional HQ reportingquarterly export S3 + Lambdavalidate & extract DynamoDBdealers · status · expiry Certificate enginePDF → ZIP → secure URL SES + CloudFrontdelivery to distributors Reminders & reportsexpiry · monthly · quarterly
The architecture keeps a single step on the client side: uploading a file. Everything after that runs on AWS managed services, with logs that let the support team find the root cause of any error.

Fit-Gap

Q4 2022
  • Reverse-engineered the macro logic
  • Mapped 5 programmes × cert / re-cert
  • Compared options and ROI

Redesign

Q1 2023
  • Standardised evaluation sheets with built-in validation
  • Certificate and email templates
  • Data model and microservice flow

Build & go-live

2023 · two waves
  • Serverless pipeline on AWS
  • Migration and user acceptance testing
  • Upload SOP and regional HQ training

Managed run

2024 →
  • SLA-based support log
  • Kaizen: automated dealer code changes
  • Planned runtime upgrades
The impact

From something that keeps people up at night to a service they rarely think about

BeforeMacros depended on one person's PC and Office version
SolutionServerless pipeline on AWS
ResultHandover now means learning to upload a file
BeforeChanges to dealers or signatures needed a vendor
SolutionMaster data the regional HQ updates itself, plus a Kaizen that automates dealer code and name changes
ResultDay-to-day changes handled in-house, with an audit log
BeforeRe-certification and expiry tracked by hand, or not at all
SolutionAutomatic issuance, reminders and expiry notices
ResultThree-year cycle enforced across all 5 programmes
BeforeReports compiled by hand for internal use and the global HQ
SolutionMonthly and quarterly exports generated by the system
ResultCertificates issued every quarter for every dealer that qualifies, with no manual compilation
BeforeUnpredictable cost of supporting desktop tools
SolutionPay-as-you-go managed services plus an SLA
ResultServerless infrastructure that costs tens of SGD a month to run
The goal was never just to automate certificates. We wanted the regional HQ to own a process that keeps working when people, PCs and programmes change.
Engagement Lead, Taira Promote
What's next

From certificate engine to an end-to-end evaluation platform

With the engine stable, we are now working with the regional HQ on the next stage, running the whole cycle in one app, from the dealer's self-assessment to regional KPIs. The existing certificate engine stays as it is, which keeps the cost and risk of the change low.

Step 1

Dealer self-assessment

Mobile checklists with photo evidence, saved drafts and automatic tagging by quarter.

Step 2

Review and approval

Distributor review, send-back and regional HQ approval, all recorded in an audit trail.

Step 3

Certify and visualise

The existing engine issues certificates. The data feeds regional KPI dashboards in Power BI.

Platforms & partners
AWS LambdaAmazon S3DynamoDBAmazon SESCloudFrontCloudWatchServerless FrameworkNode.jsPower BI (roadmap)

Facing a similar challenge?

Tell us about it in a few lines. We will come back with a practical first step, usually within a week.