The problem

Engineering data lived in many places, regions needed local copies under different data rules, and release work depended on manual steps and email chains.

Key decisions

  • Migrate first, then master: one trusted record before anything is replicated.
  • Classify PII before it crosses a region, and replicate only what the law allows.
  • Write amisvnservice in C++ as the handler for internal communication.
  • Notify on a subscription: who had access to a module, and the expiry or subscription date that ended it.
  • Automate release submission mail so a BIOS release does not depend on a forwarded email.

Outcome

One governed source of master data, replicated safely across regions, and a release process engineering teams relied on. Recognised with the Team Excellence Award in 2015.

C++MDMReplicationNotificationsRelease automation

Architecture flow

  1. Scattered source systems
  2. Migration into a central store
  3. Master data management layer
  4. Regional replication with PII controls
  5. amisvnservice and release notifications
  6. Engineering teams across regions