Process Studio
Not marketing copy but the list: what Process Studio contains, sorted by what you need it for. Anyone assessing a tool does not want adjectives – they want to know whether the capability is there.
Modelling, details on the element, search, collaboration and handover – including the limits.
Modelling
BPMN, complete and direct
Tasks, events, gateways, sub-processes, pools and lanes – BPMN 2.0 with diagram interchange, not a reduced subset.
Process from text
Describe instead of draw: the agent creates the model – new, replaced or extending an existing one.
Automatic layout
Orthogonal connections, grid, alignment to phases – in the style the Learning Model derived from your inventory.
Phases and lanes
Assign steps to a phase, colour the bands, set the order – the structure that reappears in Jira and Confluence.
Attached to the element
TAOM identifier
A stable identifier per step – the basis for keeping the Jira issue, Confluence page and test case tied to the same step.
Role, system, transaction
Who does it, in what, with which function – ERP functions on several lines, with suggestions from the Learning Model.
WRICEF and category
Standard or extension, and of which kind. Shown as a badge on the box.
Inspection duty, risk, control, test case
The chain of evidence on the step – with test result and approval state, not in a list beside it.
Description per language
German and English kept apart, switchable on the step, on the phase and in the edit panel.
Provenance and approval
Human-made, AI-generated or AI-modified – with the person and time of approval.
Find and compare
Inside the open model
Searches labels, descriptions, identifiers and ERP functions – jumps to the hit and zooms in instead of only highlighting.
Across every model
Free text and thirteen ready-made questions across the whole inventory – by term, attribute and context.
Split view
A second model on the left for viewing, the editor on the right – compare without leaving your own. Swap with one click.
Original and working state
The uploaded file stays selectable next to it: what was it originally, what has it become?
Collaboration and history
Work at the same time
You see who is working where – presence on the element, no merging of two versions afterwards.
Change history
What changed, by whom and when – with undo and a view of pending changes before saving.
Workspaces
Models separated per initiative, tied to a tenant – other workspaces visible, but marked as such.
Batch processing for learning
Pick a folder of BPMN files: each file becomes a workspace, and the evaluation for the Learning Model runs along.
Hand over
Jira and Confluence
Epic, stories per phase, issues per step and the page tree with specifications – from the same model.
HTML and PDF
Evidence to pass on – with descriptions, inspection data and identifiers, in the chosen language.
BPMN file
Everything is in the file, including the TAOM details. It opens in other tools without the additions getting in the way.
Interface
Fetch processes and attributes programmatically into your own systems.
Honestly
No process mining
The studio models BPMN and the details on it. It does not read event logs from running systems and does not measure cycle times. If you need both, use mining for measurement and TAOM for description, evidence and delivery.
No execution engine
The studio describes processes, it does not run them. The models serve understanding, evidence and delivery – they are not a workflow engine.
More than a diagram
Process Studio ties model, attributes, roles, systems, requirements, risks, tests and deliverables into one context that is available again for the next initiative.