Quick Start Guide

Data to first answer, in about fifteen minutes. This walks the whole path once — workspace, upload, project, map, variants, copilot — so you know where everything is.

What you'll do

• Create a workspace
• Upload data and approve how it was read
• Create a project and set its scope
• Read the process map
• Look at the variants
• Ask the copilot a question

Before you start

You need an account and something to analyse.

Access — Flow Myna is not self-serve sign-up; access starts with a conversation. See onboarding if you do not have an account yet.

Data — a CSV with timestamps, activities and identifiers, or an XES / OCEL 2.0 event log. If you would rather not use your own data yet, the upload step offers samples.

Step 1: Create a workspace (1 minute)

1. Sign in and, from Workspaces, click New Workspace
2. Give it a name — something durable, like "Process Analysis" — and, optionally, a description
3. Click Create workspace

Step 2: Upload your data (5 minutes)

2.1 Start a dataset

1. Open Data Management and click Create New Dataset
2. Pick the closest process type, or Custom Process
3. Click Continue to Upload

2.2 Upload

1. Drop your files onto the upload area, or click browse — or pick one of the samples
2. When every file is in, click Proceed to Mapping

2.3 Auto Mapping (a minute or two)

Three agents run in turn — Reader, Mapper, Inflator — and the step shows which one is working. Nothing is imported yet.

2.4 Check Mapping (the step that matters)

1. Read the object types the agents found, and the event types under them
2. Check each event type is attached to the right object type
3. Check the Unmapped Fields tab for anything important that was left out
4. Fix what you can directly: rename, include or exclude a field, correct a timestamp format
5. For anything structural, write what is wrong in the feedback box and press Remap — the agents run again with your correction, and you review the new proposal
6. When it looks right, click Approve & Continue

2.5 Transform Data (a minute or two)

The approved mapping is executed — Transformation, then Data Sync, then Optimizing for Analysis — and your dataset appears in Data Management.

Step 3: Create a project (2 minutes)

1. From the workspace, create a new project: give it a name and, optionally, a description
2. Select Your Data Scope — tick the object types and their event types. For a first project, take everything.
3. Define Process End Points — the events that mark a process finished. High-confidence suggestions are already ticked; check the completion coverage figure against what you expect and adjust.
4. Click Complete Setup

Where a project has several object types, one becomes the default lens — the object the map is centred on — and you can switch it at any time.

Step 4: Read the process map (3 minutes)

4.1 Get your bearings

The map opens on the default lens. Above it, how many event types are drawn and how many objects they belong to. Follow the thick edges: that is the route most work takes.

4.2 Click a node

A panel opens with the two numbers from the node in full — how many objects reached this activity (green) and how many are still sitting here (grey) — plus where they came from, where they went next, when the event happened over time, and the objects themselves.

4.3 Click an edge

The edge panel gives you how many objects took that transition, the median wait between the two activities, and a distribution plot of that wait. The plot is the interesting part: a wide spread means unpredictable, which is usually a bigger problem than merely slow.

4.4 Look for the shape

• Thick edges — the main route
• Red edges — the long waits
• Backwards edges — rework
• A node with a high grey number — work arriving and not leaving

Step 5: Look at the variants (2 minutes)

1. Open Variants in the sidebar
2. Read the coverage line — Top N of M cover X% of objects. That one line tells you how disciplined the process is.
3. Tick a variant or two to draw them; hover the eye icon to preview a path, click it to pin the highlight in a colour so you can compare two at once
4. Found one worth chasing? Use the With toggle to filter the whole project to exactly those paths

Step 6: Ask the copilot (4 minutes)

1. Open Co-Pilot and ask something specific: "Show me the objects that took longer than 14 days"
2. It applies a filter, tells you how many matched, and the map beside it redraws to that cohort
3. Follow up — "What's the biggest wait for these?" — and it answers about the cohort you are already in
4. Use one of the suggested follow-ups, or a link card to carry the cohort through to Compare or Bottlenecks and keep going by hand

Everything the copilot says is computed from your data at the moment you ask, and the filter it applied is visible in the Active Filters panel where you can remove it.

What you have now

A dataset whose mapping you approved, a project whose scope and end points you chose, and a first pass over the map, the variants and a conversation. That is the whole loop; everything else is doing it again with better questions.

Next steps

Understand what you are looking at

• What is Process Mining? — the fundamentals
• Object-Centric Approach — why the lens matters
• Process Map — the controls you did not touch yet

Go deeper

• Filters & Exploration — build the cohorts worth comparing
• Saved Filters — keep the ones you will want again

Bring your team in

• Collaboration — invite colleagues, share a view by link

Common questions

How do I act on a bottleneck I found? Filter to the objects it affects, compare them against everything else, and find out what they have in common. That is usually the difference between "this step is slow" and something you can change.

Can I add more data later? Yes. Upload to the same dataset and the saved transformation is reused, so new rows land in the same object and event types.

How do I compare before and after a change? A timeframe filter, and the Compare page, which puts two cohorts side by side and ranks what differs.

My process is nothing like order to cash. The path is identical: upload, approve the mapping, scope a project, explore.