The OMS
End-to-end orchestration — loan product, payment, warehousing, fulfilment — on a Kafka event layer. Built from the model; no vendor ships it.
The situation
A leading Philippines financial-services company needed something no vendor ships off the shelf: end-to-end orchestration across loan product, payment, warehousing and fulfilment — processes that span systems no single platform owns.
What we did
We built it. The OMS orchestrates the whole flow on a Kafka event layer — engineered from the Connectivity Model, not configured from a product. Events flow, processes cross systems cleanly, and the business runs as one system rather than a set of integrated parts.
Why it matters
This is “engineering, not configuration” made physical — the Connectivity Model built for real. When no platform fits, you build; the OMS is why that isn’t a failure but the point.
The client stays unnamed by design. Keep the framing general and the architecture concrete.