Quickstart
From a table export to a conformant OCEL 2.x log, in the browser, without a data-engineering project. Everything below runs in the free studio; the full documentation ships with it.
Open the studio
Free, in the browser, no account. Your files are read locally into an in-browser engine; nothing is uploaded.
Drop in your data
Any OCEL serialization opens directly. Plain tables — CSVs straight out of an ERP — go through the mapping wizard instead.
Confirm the mapping
The wizard proposes which tables are objects, which are events, and how they relate — evidence shown beside every proposal. What you confirm becomes a versioned mapping file:
{
"mapping": 1,
"objects": {
"Order": { "table": "orders", "id": "order_id" },
"Item": { "table": "order_items", "id": "item_id",
"relations": { "line of": "order_id",
"of product": "product_id" } }
},
"events": {
"Place Order": { "from": "orders", "at": "created_at",
"subject": "Order" }
},
"status": "confirmed"
}
Illustrative — the full format ships with the studio.
Explore — and take the log with you
The Process Map, lifecycle strips, and the rest of the studio open on your data immediately. The translated log is yours, on the standard:
OCEL 2.x primer
Objects, qualified relationships, and why a log no longer has to pick a victim. The standard is public: ocel-standard.org.
Conformance checks
Every load is checked against the standard's constraints — findings surfaced, never thrown. You know where the holes are before you trust a chart.
The ledger method
How detectors make fractional claims on atomic cost events, why claims sum to one, and what the two confidence bands mean — the arithmetic behind every published figure.