Almost every business process tool on the planet is built on a hidden assumption: that the world is a sequence of cases. A case has a case ID. It moves through a series of states. It produces a series of events. It has a single customer, a single worker, a single timeline. The case is the spine of the model.
This is wrong. Not slightly wrong. Architecturally wrong. The world is not made of cases. The world is made of objects — patients, appointments, claims, treatments, payments, recalls — and the objects interact in ways that no single case ID can capture.
The cost of the case-shaped model is paid in the dashboards you cannot build, the analytics you cannot run, and the AI you cannot train. The fix is not a better case tool. The fix is to abandon the case.
A dental patient calls on Tuesday to book a cleaning. The call is a case. While she is on the phone, she asks about her husband's outstanding treatment plan. Two cases — or one? Her insurance is verified, which is a third case. Her appointment is confirmed, which is a fourth. She reschedules, which spawns a fifth. By Friday, the patient has touched nine cases, three systems, and two staff members.
In a case-shaped world, you have nine disconnected timelines. You can tell the story of each. You cannot tell the story of the patient. The patient is the unit that matters — and the patient is invisible in the case model.
In an object-shaped world, the patient is the object. The appointment is the object. The treatment plan is the object. The insurance verification is the object. The events attach to the relevant objects. The patient's full story is the join. The join is one query, not a research project.
Object-Centric Process Mining (OCPM) is the discipline of analysing processes where events relate to typed objects, not to a single case. The reference meta-model is OCEL 2.0 (Object-Centric Event Log). The four operational tasks are:
The shift from case-centric to object-centric is the same shift that the database world made from hierarchical to relational in the 1970s. The unit is no longer the record. The unit is the entity and its relationships.
Walk through any service business and count the object types:
Every one of these object types has its own lifecycle. Every one of them interacts with the others. A patient does not have a single timeline; the patient has many overlapping timelines, one per object type. The case-shaped model flattens this into one timeline per "interaction." The object-shaped model preserves all of them.
The downstream effects are enormous. In object-shaped data:
In a case-shaped world, each of these queries is a data engineering project. In an object-shaped world, they are routine.
Object-shaped data is the natural substrate for an AI agent. The agent does not need to know which case to ask about. The agent queries the object graph: "patient X, treatment Y, appointment Z, insurance A." The graph returns the answer. The agent never loses context because the context is the join.
The vendors who win the next decade will be the ones who build on object-shaped data from day one. The vendors who try to bolt object-shaped data onto case-shaped tools will spend the decade rebuilding.
There is a non-obvious convergence here. The same intellectual move — abandon the case, treat the customer as a first-class entity — shows up in two completely different fields:
The two fields use different vocabularies. They describe the same structural shift. The customer — whether a patient, a process event, or a buyer — is the first-class object. The "case" was always a workaround.
If you are building a process tool for a service business: build it object-shaped from day one. The temptation to start with a case-shaped model and migrate later is the same temptation as "we'll add indexing later." You will not. Start object-shaped. Pay the modelling tax now. Reap the analytics leverage for the rest of the product's life.
If you are buying a process tool for a service business: ask whether it is case-shaped or object-shaped. If the vendor cannot answer, the answer is case-shaped. If the vendor says "case-shaped but with foreign keys," the answer is still case-shaped.
If you are running a service business: the dashboards you cannot build today are not because you do not have the data. They are because the data is in case-shaped silos that do not join. The fix is not a better Excel template. The fix is an object-shaped system underneath.
The case is a fiction the original process tools invented to make the math tractable. The fiction has run out. The world is objects. Build accordingly.
CTO