Loading
We connect OEM, supplier, factory and dealer systems so orders, despatch advices and telemetry arrive as events rather than overnight files. It is built on EDI, AS2 and modern APIs, and it runs on your cloud or on the plant floor.
FOUR PARTNER FORMATS · ONE MODEL
Where it breaks
One mapping per partner works at twenty. At two hundred it becomes a full-time team, and nobody can say what an order looks like across all of them.
OEMs, Tier-1s, logistics providers and aftermarket suppliers each send EDIFACT, X12, VDA or a portal export. Every one gets its own transformation, and every change breaks one of them.
One canonical model that every partner format maps into, so no two partners are ever wired to each other.
Documents move on a schedule, so an ASN error surfaces at goods receipt rather than at despatch. By the time anyone knows, the part is on a truck or the line is already short.
Event-driven flows with validation at ingestion, so the error comes back to the sender in minutes.
MES, ERP and PLM hold different versions of the same build. Quality data sits on the shop floor, planning sits in the ERP, and reconciling them is a weekly export.
Plant systems publish to the same model as the supply chain, with the layer running locally so the line does not depend on a WAN link.
How it works
Nobody has to re-onboard. We parse each document, validate it against the partner profile, route it and archive it on the way through.
Scroll the diagram sideways →
EDIFACT, X12, VDA and OFTP2 for the partners you already trade with, REST and event streams for everything new. When a partner changes, you change a mapping and leave the architecture alone.
The runtime sits on Azure, AWS, in your data centre, or locally at each site. Plants that cannot depend on a WAN link keep processing when the link drops.
Document tracking, acknowledgement matching, retries and exception queues are in place from day one. We can run them under a support agreement if you would rather not.
Products
MetricMonitor, Easy-Invois and DwaniAI read the same normalised documents and events, so a partner is the same partner in all three.
Line performance, supplier delivery reliability, telematics health and integration pipeline status on one screen, with alerts on the thresholds you set.
Explore MetricMonitor →It generates and clears invoices across multi-country supply chains under Malaysian e-Invoice, ZATCA and EU VAT rules, and wires into SAP, Oracle or your own ERP.
Explore Easy-Invois →Dealer and owner support over chat and voice: parts availability, service booking, warranty questions and vehicle configuration, in the languages your markets use.
Explore DwaniAI →How we work
Every channel we build runs alongside the one it replaces. Both send, the partner confirms which they received, and the old channel stays open until you close it.
It is included in every engagement. Every partner cutover works this way, on the first and on the two hundredth.
A channel is correct when the receiving system acknowledges it and the contents match the documents they were already getting.
The channel we replaced stays configured until you retire it. Reverting during a shift means flipping a switch. There is nothing to restore.
Recent work
Anonymised at the client's request
A Tier-1 supplier held a separate mapping for every customer and logistics provider. Adding a partner took weeks, and a schedule change from one OEM meant editing a transformation nobody else understood.
We defined a canonical order and despatch model, moved partners onto it in waves, and put acknowledgement matching in front of the plant. Each partner ran on both channels until they confirmed.
Talk to us about your estate →Questions
Every partner maps to one internal model rather than to each other. EDIFACT, X12, VDA and portal exports all become the same order or despatch object on the way in, and the same object becomes whatever that partner expects on the way out. Adding the next OEM means writing one mapping.
Get started
Tell us which partners and systems you are trying to connect. An integration architect reviews it and comes back within two working days.
