The Translation Layer turns the data architecture you already have into the open OCEL 2.x standard — object-centric, auditable, ready for any tool that can mine it. Then our analytics find where margin leaks between your processes, in dollars you can defend.
Free · no account · nothing uploaded
Two items, one shipment, one invoice — one order. Visible in an object-centric log; destroyed by a case id.
A CSV of tables straight out of your ERP, or any OCEL file you already have. It never leaves your machine.
The studio proposes which tables are objects and which are events, with the evidence shown. You approve; nothing is guessed silently.
Your object graph, your process map — and a bounded, honest taste of the leakage figure, with its assumptions stated.
The hosted studio arrives at this address shortly — design-partner conversations are open now.
Classical event logs force one case id per log. Real processes don't have one — orders have items, items share shipments, shipments share invoices. Choosing a victim duplicates some events and hides others, and every number downstream inherits the distortion.
Every new question means a new extract, a new model, and a round-trip through a specialist. Analysts stop asking questions that aren't worth a two-week wait — which is most of the good ones.
OCEL 2.0 removed the flattening tax at the data layer. The wall that remains is translation — and the industry treats that wall as a services engagement. We made it the product.
A pay-to-use service that converts your existing data architecture into a robust, object-centric, mineable one — on the open standard, on your infrastructure, with the assumptions on the table.
Mappings are proposed from evidence — your foreign-key graph, key statistics, naming — with the evidence shown. You confirm once. From then on translation runs silently and continuously, and schema drift is flagged, never silently adapted to.
Versioned, diffable, promotable between environments, and confirmed by you before a single figure ships. The log is exactly what the mapping says it is — and you approved the mapping.
JSON, XML, relational SQLite, CSV, Parquet — the standard's full surface. Portable by design: your log works in any tool that reads OCEL, competitors included. That is the point of an open standard.
Runs client-side today; in your warehouse at maturity. No replication, no second copy of your operational data, and a security review measured in minutes rather than quarters.
The overstatement a naive sum of detectors would have shipped — caught by the attribution ledger. Every dollar exists once, claims sum to one, and the books balance before any figure is shown.
Annualized leakage, single-counted, each dollar attributed to one cause — published with its population, its assumptions, and two confidence bands that are never blended into one number.
A stockout's true cost after causal attribution: two-thirds of it lands in warehouse handling, redeliveries, and expedites — three cost centers that would never blame inventory on their own.
Sampling error cannot move our totals. Only cost rates can — and you own the rates.
Four questions, answered in dollars — with the assumptions published beside every figure.
Ranked findings, each with an annualized value, a causal chain, and the rate workspace where you set your own costs and watch every figure move.
Fractional claims on atomic cost events, symptom separated from cause. The difference between a number and a defensible number.
Interventions ranked by depth, after Donella Meadows — so you fix the stockout upstream instead of repainting the packing line downstream.
Before and after, with both bands: leaks closed, leaks reopened, leaks new. The sentence a renewal is built on.
The studio over OCEL files, metered translation with the full mapping experience, and an honest, bounded taste of what your data is worth. Nothing is uploaded, ever.
Connected, continuous, at scale: every serialization out, the Connection Auditor, mapping versioning, and schema-drift detection.
The analytics on top: the Leakage Report, the Leverage Points, Continuous Monitoring. Your rates, your ledger, your exports.
A six-week diagnostic on one process pair, run by us end to end. A quantified leakage figure — or a refund.
Design-partner conversations are open now.
Nothing here asks to be trusted. It asks to be checked — and it brings the checking tools.
