Process Revealer Free Edition: A Complete Beginner’s Guide

How to Use Process Revealer Free Edition to Visualize Workflows

Visualizing workflows helps teams spot bottlenecks, standardize steps, and improve throughput. Process Revealer Free Edition is a lightweight tool for turning event logs and process data into clear, interactive diagrams. This guide shows a straightforward, end-to-end workflow: preparing data, importing into Process Revealer Free Edition, creating visualizations, and using findings to improve processes.

1. Prepare your data

  • Format: Export process data as CSV with columns for Case ID, Activity, and Timestamp. Optional useful columns: Resource, Department, Duration.
  • Timestamp consistency: Use ISO 8601 (YYYY-MM-DDThh:mm:ss) or a consistent, sortable format.
  • Clean: Remove duplicates and correct misspelled activity names (merge variants like “Approve” / “Approval”).
  • Sample size: For initial exploration, 200–2,000 cases is a good balance between clarity and performance.

2. Import data into Process Revealer Free Edition

  1. Open Process Revealer Free Edition.
  2. Select “Import” or “Upload log” and choose your CSV file.
  3. Map CSV columns to required fields: Case ID → Case ID, Activity → Activity Name, Timestamp → Timestamp. Map optional fields if available.
  4. Confirm parsing and proceed. The tool typically validates timestamps and highlights parsing errors—fix those in the CSV and reimport if needed.

3. Configure basic settings

  • Time window: Set the analysis period if you want to focus on a subset (e.g., last quarter).
  • Aggregation level: Choose whether to group by activity name only or include resource/department splits. For initial runs, keep it simple: activity names only.
  • Noise filtering: Apply minimum frequency thresholds (e.g., hide transitions with <1% frequency) to reduce clutter.

4. Generate and read the process map

  • Process Revealer will create a node-and-edge map: nodes = activities, edges = transitions. Edge thickness or labels show frequency; nodes may show average duration or count.
  • Key visuals to inspect:
    • Main path: The most frequent sequence of activities—this shows the standard workflow.
    • Loops and repeats: Rework cycles indicate inefficiency.
    • Long branches: Rare but long branches may be exceptions or errors.
    • Bottlenecks: Nodes with high incoming flow but slow outgoing throughput.

5. Use filters and highlights

  • Filter by resource or department to see handoffs and responsibility.
  • Highlight paths by case outcome (e.g., “Completed” vs “Cancelled”) if outcome data was included.
  • Time-slice analysis: Compare maps for different months to spot process drift.

6. Drill down into metrics

  • Click a node or edge to view:
    • Frequency: how many cases pass through.
    • Average/median duration at that step.
    • Throughput times between nodes.
  • Export these metrics (CSV or Excel) for further analysis or to combine with KPI dashboards.

7. Identify improvement opportunities

  • Target long durations: Prioritize nodes with high average time and high frequency.
  • Reduce handoffs: Consolidate steps or clarify ownership where many resources are involved.
  • Address rework loops: Investigate root cause (missing information, unclear criteria) and create controls to prevent repeats.
  • Standardize variants: If many minor branches exist, create a decision guide to reduce unnecessary variation.

8. Share findings

  • Export the process map as an image or PDF for stakeholders.
  • Include key metrics and a short action plan: top 3 issues, proposed fixes, expected impact (time saved or % fewer reworks).
  • Use exported CSVs to create executive dashboards (Power BI, Tableau).

9. Iterate and monitor

  • After implementing changes, re-run analysis on new logs to verify improvements.
  • Schedule periodic reviews (monthly or quarterly) to catch regressions or new variants.

Quick tips

  • Standardize activity naming before import to avoid fragmented nodes.
  • Use median duration alongside average to reduce skew from outliers.
  • Start with a focused subset (one product line or department) to make findings actionable.

If you want, I can provide a CSV template (columns and sample rows) you can use to export your data for Process Revealer Free Edition.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *