Five Levels of Process Modeling in Ontoz

A real business process has structure at more than one altitude. There is the shape of the whole journey, the phases it moves through, the clusters of work inside each phase, the individual units of work, and the specific operations a person or system performs. Collapse all of that into a single layer of boxes and arrows and you get a diagram that looks fine in a demo and turns unmaintainable the moment the business changes.

Ontoz keeps these altitudes separate. A process is modeled at five distinct levels, each with exactly one responsibility. The result is a structure you can read, reason about, and change one layer at a time.

The Five Levels

Flow

A Flow is the complete business process, end to end. It is the outermost container, the thing you name when someone asks what is being orchestrated. A Flow owns the list of stages it moves through, the rule set that decides how its activities are orchestrated, and the entry point that starts a new instance. Everything else nests inside it.

Stage

A Stage is a major lifecycle phase within a Flow. A stage represents a meaningful chapter of the journey, and it completes when its milestone condition is met, typically when all the mandatory work inside it is done. Progression from one stage to the next is automatic: when the milestone evaluates true, the flow advances. Stages give you the high-level read of where any instance currently sits.

Activity

An Activity is a logical group of related tasks inside a stage. Activities are how work is organized within a phase, and they can run in sequence or in parallel depending on what the business actually requires. Some activities are mandatory and some are optional; the orchestrator decides which ones begin next based on a rule, not a hard-wired arrow. There is also room for parallel work that runs alongside the main path without blocking it, so genuinely concurrent work does not force you to distort the diagram.

Task

A Task is a single unit of work, the smallest thing you would assign or hand off. Crucially, a task can be carried out by a human, by an automation, or by an integration with another system. That is what lets the same process model span people and machines without switching tools or notations. Allocation, and the form a person sees for a human task, are attached at this level.

Action

An Action is one operation performed on a task: submit, approve, reject, request clarification. Actions are where intent becomes an event. Each action can trigger downstream effects and may move a task or a stage forward. They are the verbs of the system, the points at which something actually happens and gets recorded.

Why the Separation Matters

The vocabulary is not the point. The separation is.

Each of the five levels stays pure structure. None of them contains business logic. The logic, the rules that decide what is allowed, what happens next, and under what conditions, lives separately and is referenced by the tasks that need it. This single design choice is what makes an Ontoz process durable.

Because structure and logic are decoupled, you can change a rule without touching the flow. You can add a parallel activity without redrawing the rest of the diagram. You can reason about one altitude at a time instead of holding the entire process in your head. And when a new requirement arrives, you change the layer it belongs to and leave the others untouched.

Most modeling approaches force everything onto one plane, which is exactly why those models become brittle. The moment reality introduces a parallel path, an optional step, or a policy exception, the single-layer diagram has nowhere clean to put it, and the workarounds accumulate until no one trusts the model anymore.

The Payoff

The test of a process model is not how it looks on day one. It is whether it is still readable and safely changeable at year three, after dozens of policy updates, new participants, and shifting priorities. Five clean levels, with logic held separately, is how Ontoz keeps a process honest over that span. Structure that holds its shape as the business evolves.