Use case · Governance conformance
Is it right who is accountable for what?
Not how long a case takes — but whether accountability for it is described, lived, and matches the access rights. roleALPHA checks that against your own records.
No data project·Findings with evidence·A way to change it
Context
The organisational model gets described and then never checked
Roles, value streams and policies exist somewhere. Whether they fit together shows up during the audit.
- 01 Accountability without a check For many value streams nobody is explicitly accountable — and nobody counts it afterwards.
- 02 Approvals without hindsight Whether a change really went through the agreed approval mode is rarely verifiable after the fact.
- 03 Rights without a role Permissions grow with every stand-in — which of them can be justified through a role is anyone's guess.
Solution
How you check your accountability structure
On day one, from data you already have.
- 01 Analysis over your own records Contradictions in the model, gaps in accountability, self-approvals — without a single row from your source systems.
- 02 Every finding with evidence and one action Accepting turns it into a change proposal, rejecting needs a reason, "intended" needs an expiry date.
- 03 Name a state and compare it A named organisational state can be compared with today — that is how "what changed, and for whom" arises.
Data & control
Data and control stay with you
- EU operation & GDPR Operation in the EU, Austrian law — your data stays within Europe.
- Data sovereignty Domain data optionally in your own cloud or on-premise; the control layer stays separate.
- Accountable Access, approvals and agent context are logged — solid for the audit.
FAQ
Frequently asked
Is this process mining?
No. Process analysis assesses the case — an order, an invoice, a ticket — and optimises cycle times. roleALPHA assesses the accountability structure: role, responsibility, decision right, competence, policy, permission. The two complement each other; we do not compete there.
Do we need an event log from our ERP?
No. The analysis runs on data the platform holds itself: your approval and change history, recorded effort, permission assignments. If you later want to include a case log from an operational system, we first run a dry run to check whether it is fit for the purpose at all — it stores nothing and returns one of three clear verdicts.
What does roleALPHA explicitly not do?
No control-flow conformance on business value streams, no BPMN or XES import, no desktop capture, no connector library for ERP systems, and no statement about cycle times. If you want to know why a case takes long, you need a process analysis tool — not this one.
More context