How it fits together
How Twiggy Modeller fits together: how scope is set and narrowed from the map down, what holds what and links to what, and how a model goes from first draft to signed off and back. Every picture here is interactive: click the steps or the parts to explain them.
Scope, top down
Scope starts on the map and narrows with every level you open. Click the steps: the picture changes as you go.
1. The map sets the scope
A process map is the list of what the business does: its enterprise processes, and the process areas inside each. Being on the map is what puts work in scope; anything not on it is outside. Each area’s name and its place on the map say what it covers.
The picture
1. Everything, in one picture
A folder owns diagrams. A process map opens a chain for each area and a flow for each process. Flows hold lanes, steps, decisions and events, each with properties, and steps link to items in shared registers. Sign-off publishes a flow to readers.
Click any part of the picture to explain it.
Three layers
- Diagrams, top down. A process map lists what the business does (enterprise processes, then process areas). An area opens a process chain (its processes in order) and each process opens a process flow (its steps). A step can open a flow of its own: a sub-process. See the modelling guide.
- Properties on everything in a flow. Description, how it's done, owner, SLA, exceptions, and properties your workspace adds (Administration › Properties). Lenses colour a diagram by any of them.
- Registers, shared. Risks, controls, applications, roles, business objects, requirements and rules live once, in registers, and steps link to them. An organisation can share registers across its workspaces.
Why link, not type
A step that names its system in free text is a picture. A step that links to the Credit decision engine in the Applications register is data: the register shows every step that uses it, the matrix shows processes × applications, retiring the application lists what breaks, and a risk with no control at a step is flagged. Link once; every view follows.
Ownership and sign-off
Folders own diagrams. A folder's rules (who is Responsible, Accountable, Consulted and Informed, who can see it, how its models are signed off) apply to everything in it. An owned folder's models are signed off before readers rely on them; a signed-off model is locked, and a change is a new revision that readers don't see until it too is signed off. Part of a map can be handed over to another team's folder: it becomes a map of its own, still opened from the original. How a model goes from a first draft to signed off: From map to signed-off process.
From first draft to re-approval
The same idea for the work itself: draft a model by hand, with the AI, or both; get people talking about it; get it reviewed; get it approved; then keep it current, with changes going round again for re-approval. More on each: Discuss, Review, Sign-off, comments and asking people, comparing versions.
1. Draft it by hand
Put the steps, decisions and lanes on the canvas yourself: the layout is automatic, so you think about the work, not the drawing. Properties (owner, system, duration, risks) go on each step as you learn them.