American Megatrends · 2014 - 2017
Master Data & Release Platform
Built the central master data system, with regional replication that respected PII, amisvnservice in C++ for internal communication, and the subscription notices and email around a BIOS release.
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.
Architecture flow
- Scattered source systems
- Migration into a central store
- Master data management layer
- Regional replication with PII controls
- amisvnservice and release notifications
- Engineering teams across regions
More work
Book a conversationEnterprise Data Foundation
A reusable data foundation for risk, products, analytics and AI, not one-off pipelines. Ingestion, medallion warehouse layers, domain marts and operational distribution from a single architectural spine.
Read case studyGlobal Risk Data Platform
Large-scale company risk-data architecture that ingests, enriches, normalizes and distributes company-level intelligence across countries. Built as a reusable risk pool for underwriting, products, analytics and intelligent systems, and today the data foundation beneath Cowbell's OMNI AI agents.
Read case studyGlueFlux
Metadata-driven processing framework. Pipelines defined in YAML so teams onboard Spark, Python and dbt workloads without rebuilding orchestration, deployment and operational patterns every time.
Read case study