Bite-sized, not wallpaper

How TAOM models are structured

Bite-sized, not wallpaper.

No giant chart on the wall that nobody reads any more. Every workflow is a small model with a fixed place in the enterprise process model. The models are connected where the work passes from one to the next.

The structure

One picture for everything – or one model per workflow.

Every model has its place on one of six levels. Modelling happens at the very bottom – where a workflow still fits on one page.

Not like this

The giant wallpaper

One diagram for everything: hundreds of shapes, nobody finds their step, every change affects everyone.

Like this

Six levels – one model per workflow

Click your way from the overall picture down to the step. You may skip L3 and L4.

L5 · Procedure – the BPMN model
This is where modelling happens: a manageable workflow such as “Create BOM”. Every step gets its identifier – P2M.01.02.01-AC001 – and carries roles, systems, requirements and tests.
One model = one workflowThe BPMN model sits on L5 – manageable, with one person responsible.
Models connectAn event leads into the next model, a step points to its detail model.
One identifier travels alongP2M.01.02.01-AC001 appears in BPMN, in the target system (e.g. Jira, Confluence) and in reporting.
No L6 below L5There, roles, systems, requirements, controls and knowledge are attached to the step.
Chain and sub-process

Stay small – and still show the whole.

Many separate pictures do not make a landscape: every team draws for itself, and how it all fits together is written nowhere. In TAOM one model refers to the next – and the tool knows every connection.

Enter orderO2C.01.01.01
Deliver goodsO2C.02.01.01
Sub-process
Pick goodsO2C.02.01.02
Issue invoiceO2C.03.01.01
Post paymentO2C.04.01.01
Transition: the end of one model is the start of the next. Sub-process: a step points to its detail model.Example: Order to Cash (O2C).
Transition · the chain

The workflow continues in the next model.

You connect the event at the end of one model with the event where it continues in the other model. Event to event – that is how the chain forms.

AB
A shows: “Continues in B”B shows: “Comes from A”
Sub-process · the depth

A step gets its own model.

If a step is too big for one box, it points to a model that shows it in detail. There you choose the step or the event it corresponds to – that does not have to be the start.

AC
A shows at the step: “Details in C”C shows: “Called from A”
Two places to connectEvents for the transition, tasks for the sub-process. Branches are not connected.
A sign shows itTwo chain links above the element – on both sides. One click shows the other side.
The other model stays as it isConnecting changes only your own model. The approval and the seal of the other one remain valid.
The connection holdsIt points to the element, not to a name. The TAOM identifier is read afresh every time.

Where others sweep it under the carpet, we put our finger on the sore spot.

The spot between two models is where work gets stuck: at the handover. That is exactly where TAOM connects – visibly, on both sides.
Who it is for

Only for corporations? No.

Every company has processes. One workflow is enough to start – the one people are talking about most right now.

One workflow is enoughStart with one model. Its place in the overall picture follows as their number grows.
It grows with youEvery further model is connected, not bolted on. The existing ones stay as they are.
Readable for everyoneA small model fits on one page – also for people who never learned BPMN.
Start with one bite.A workflow you know well – TAOM gives it its place in the overall picture.

Are you deciding on the roll-out? TAOM for management – in four steps → · View the enterprise process model →