Instructions

1Creating a workspace

Two ways: upload an existing .bpmn/.xmlfile, or click “+ New process diagram” at the top left – this automatically creates a new, empty workspace with a valid BPMN skeleton, with no file upload at all. Every workspace receives its own ID and its own Original and Generated files on the server.

×

2Original vs. Generated (split view)

On the left is Original – the unchanged, uploaded (or empty) source file, view only, no editing. On the right is Generated – the full editor, this is where you work. The arrow button on the left of the Original title collapses the Original column so the editor gets more room. Both sides have their own independent zoom controls.

3Editor toolbar

Above the canvas you control all layout and saving functions:

• ↶ Undo / ↷ Redo – also via Ctrl/Cmd+Z and Ctrl/Cmd+Shift+Z. Every completed change (move, rename, add, delete, connect, attributes) can be undone.
• Snap to grid – aligns all (unlocked) shapes to the grid and tidies the connections. The reference is always the centre of a shape, so symbols of different sizes sit consistently.
• Align lanes – stacks the lanes within a pool without gaps or overlap, re-centres the steps in their lane and re-routes the connections – so line jumps disappear.
• Tidy layout – centres every box within the lane it sits in and straightens the connections (without changing lane). Uses the same centre grid as “Snap to grid”, so both functions match and the shapes do not jump when switching.
• Align to phase licence – arranges the steps by their phases: the phase blocks are grouped cleanly and in order along the direction of flow (the internal arrangement within a phase is preserved).
• Assign IDs – automatically numbers all elements with TAOM IDs (TB-001, TL-001, TLD-001; associated texts with “-T”).
• Delete – deletes the selected element (does not work on locked elements).
• Save – commits the current working state on the server.

×

4Symbol palette

The left palette holds the complete BPMN 2.0 symbol set, grouped into categories. The filter bar at the top narrows it down by diagram type (BPMN process, organisation, process map, system landscape, RACI matrix). Three ways to insert a symbol:

• Click – inserts the symbol at the next free grid position.
• Drag and drop – pick up the symbol, drag it to the desired place on the canvas and release – it lands exactly there.
• Mark a point, then click – first click an empty spot on the canvas (a dashed marker appears), then click a symbol in the palette – it is placed at the marked position.

• Events – mark what triggers a flow (start), occurs along the way, or ends it (end). Variants such as message, timer, signal, condition, error, escalation or compensation show what triggers the event.
• Activities – the actual work steps: general task, user task (person), service task (system), script, send, receive and manual tasks, plus sub-processes for nested flows.
• Gateways – branches and merges: exclusive (XOR – exactly one path), parallel (AND – all paths at once), inclusive (OR – one or more paths), plus complex and event-based gateways.
• Data & artefacts – data object and data store (information used or produced) as well as text annotation and a free text field for notes in the diagram.
• Swimlanes – pool and lane structure the diagram by responsibility (area, role, system). Switchable in the attribute panel between landscape (label on the left) and portrait (label on top).
• Roles & systems – person/role, system/engine and IT interface highlight those responsible and the systems involved.
• WRICEF – classification of development objects: Workflow (W), Report (R), Interface (I), Conversion (C), Enhancement (E) and Form (F).
• Organisation / process map / system landscape / RACI matrix – additional symbols for organisational charts, process overviews, system landscapes and responsibility matrices.

4aPhases – grouping process steps into sections licence

The phase (at the very top of the palette, with TAOM marking) is a speciality of Process Studio: an organisational object that groups several process steps into one section – for example “Intake”, “Review”, “Completion”. This keeps even a long flow clear and divided into distinct stages.

• Create a new phase – select a step and click “Phase” in the palette: a new, consecutively named phase is created and the selected step is assigned to it. The name can be changed freely.
• Assign or move a step – in the attribute panel under “Phase / sub-process” in the field “Phase of this step”: choosing an existing phase moves the step, typing a new name creates a new phase.
• Coloured band – where steps belong to phases, a coloured band appears automatically at the edge. The phase window sets name, colour, lock and order.
• “Align to phase” – brings the phase blocks into order along the direction of flow and gathers scattered steps of a phase together.

6aRight-click on an element

A right-click on an element opens the context menu. It bundles the most frequent actions right where you are working – without a detour via toolbar or attribute panel.

7Attribute panel

When an element is selected it shows: name, description, BPMN ID (display only), TAOM ID (editable), position (lock/hide), fill, border and text colour, font size. Depending on the element type also: routing & condition expression (arrows), gateway type, event trigger, task type & WRICEF type & script fields (tasks), Jira/Confluence link (tasks), orientation & “show area” (swimlanes). Governance & classification per step are editable for signed-in users.

Phases carry text as well: Clicking a phase band at the edge shows its description in the lower area – just like for an individual process step. This lets a flow be read first at section level and only then in detail.

×

8Settings (⚙)

Freely available: show grid, snap to grid (while dragging), grid size, zoom speed, workspace width, show TAOM ID and WRICEF badges, Jira and Confluence base URLs.

Behind a simple local sign-in (not a real security mechanism, only protection against accidental changes): lock/unlock all elements, show/hide history & log, permanently delete the active workspace.

×

×

9Export

“HTML preview” opens the view in a new tab (Original: last saved state; Generated: current working state including TAOM/TRANIVA branding). “As PDF” opens the same view and starts the browser print dialogue; the page size (A4–A0) is chosen to match the diagram size. “Download” downloads the .bpmnfile – the file name matches the title of the process. In HTML and PDF the origin and AI notice and a QR code appear at the bottom.

9aRelated diagrams

Extensive flows can be split into several self-contained diagrams – for example goods receipt, production supply, shipping and stocktaking. If they come from one agent run they stay permanently connected: number, total count and the names of the related diagrams are held in each BPMN file itself.

In the editor they appear as coloured numbers next to the active workspace; a click switches to the respective diagram. On export, “all diagrams of the group” downloads every file together as a ZIP, named by number and title. Because the relationship is held in the file, it survives sharing, export and display in the viewer.

Elaboration: The first diagram built is elaborated automatically. For the others, elaboration can be triggered per element via “Elaborate now” in the attribute area – which saves effort compared with elaborating all diagrams in full.

10TAOM quality seal & origin

Every BPMN file created or edited in TAOM receives an invisible, signed origin seal: source, TAOM version, timestamp, licence status and an AI marker. We never adopt someone else’s origin – if a file was not created in TAOM it honestly says “Unknown”; an existing origin is preserved and only extended by our processing. On export a QR code is added that points to the verification page at taom.ai/beleg. There you can enter number and seal and verify the origin without access to TAOM.

Responsibility & history: On import of a third-party file we adopt neither an existing seal nor an origin – the history starts honestly anew with “Imported (unknown)”. We take responsibility only once the file is actually edited or saved in TAOM. Only without an upload (empty diagram or via the TAOM agent) does the history begin with TAOM. This history is stored in the file and is part of the signature.

In the spirit of the EU AI Act we mark AI involvement openly using the official EU icons: diagrams generated entirely by AI carry “AI GENERATED”, every file edited in TAOM (even partly) carries at least “AI MODIFIED”. The marker is part of the signature – tampering with the relevant details shows up during verification.

Basis of the signature: a cryptographic checksum in accordance with SHA-256 over the file content. This allows verification of whether a file originates from this environment and whether it was altered after being produced.

The same method applied to documents: invoice, licence document, data processing agreement, certificate and contract documentation carry a document seal with number and QR code – verifiable through the same page at taom.ai/beleg. Not only the model has a verifiable origin, but every document produced from it. Which features are in which state is set out in the Trust Center.

11TAOM Agent – a process from text or speech

In the expandable “TAOM Agent” panel above the editor you describe a process in your own words – typed or dictated. TAOM automatically produces a BPMN draft in the editor, which you then adjust as usual. If the agent asks a question, simply keep answering until the diagram fits. The answer appears directly in the panel.

The agent reads only your text. Two things it cannot guess – they must be stated explicitly:

The orientation. Without a statement the diagram is built in portrait, that is top to bottom. If it should run across, a word such as landscape or horizontal belongs in the text – ideally right at the start. The choice then applies for the whole session: it is kept through follow-up questions and additions as well.

The type of diagram. Without a statement a BPMN process is created. If something else is needed it has to be named – for example RACI matrix, organisational chart, process map or system landscape. One sentence is enough: “Create a RACI matrix for the following roles and tasks …”

Everything else may be stated but need not be: industry, level of detail, roles and systems are recognised by the agent from the text.

If the agent recognises that a description is ambiguous – for instance several independent flows with no visible connection – it does not build on suspicion but asks a question with concrete answer options. Question and answer are recorded in the history, so it remains traceable later on what basis a model was created.

How long it waits for an answer is set in the settings. If that field is left empty, the editor waits indefinitely – the decision thus stays expressly with the human.

12Jira & Confluence integration

TAOM elements carry Jira metadata in their attributes (issue type, priority, status, component, version, assignee and others) as well as a Confluence link – in preparation for the connection. The issue type is preset by TAOM level (WRICEF → sub-task, otherwise task) and can be overridden per element; the shapes use the official, unaltered Jira issue type icons and status colours from Atlassian. All details are stored permanently in the BPMN.

Jira and Confluence are products of Atlassian and stand for separate systems – they are not merged with TAOM/TRANIVA.

13Licensing & access

Without registration or sign-in you can upload your own BPMN files and use the editor fully: view, edit, save and export as HTML or PDF. For the full range of functions please register via the contact page.

Free to use (without signing in)

• Upload files or create an empty diagram.
• Place, connect and rename all symbols.
• Move, resize, lock, hide; colours & typography.
• “Snap to grid”, “Align lanes”, “Tidy layout”, “Assign IDs”.
• Grid and view settings; HTML/PDF preview and download.

Licence required licence

• Create phases, assign them to steps, and “Align to phase”.
• Attach documents to a step (stored with access protection).
• Edit classification & governance per step.
• Create a blueprint for Jira/Confluence.
• TAOM Agent (process from text or speech) and batch processing.
• Full export of very large or mixed models (without a licence the demo shows an excerpt).