Operon.Cloud Platform Orientation
Health plans
Business & operations leaders
Prior Authorization
No product, data, or API expertise
Turn the work already happening across people, vendors, systems, automation, and AI into operational evidence you can understand, improve, and value.
An operating model
or Queue
Movement
& ROI
One model covers workflow, work, ownership, time, efficiency, and value, so every participant reads the same account of what happened. The rest of this orientation follows one Case through those eight concepts, ending in the AI adoption and ROI evidence they add up to.
A useful operating model starts with one bounded workflow and one clearly identifiable unit of work.
Prior Authorization
The top-level organizational boundary. One or more Workstreams live inside it.
One bounded business workflow, narrow enough that its Cases, States, actors, clocks, and outcomes all mean the same thing.
One unit of work: the correlated history of all observed activity sharing one stable Case identifier.
We say “State or Queue” on purpose: the platform calls it a State, your team calls it a queue. Resist modeling the entire enterprise as one Workstream, because coherence is what gives Cases, actors, clocks, and outcomes a comparable meaning.
Touches show work. Movements show flow. Together, they tell the Case story.
Mon 09:12 → Fri 11:02
Work performed while the Case stays in its current State.
The Case moving from one State to another.
Repeated Touches and backward Movements reveal rework, loops, failed handoffs, and manual intervention after automation. That second review at 15:44 is not a story anyone had to report; it is simply what the Case history says.
The Resource that performed the last action may not be the Resource that owns the next one.
Thursday, 14:30
Thu 08:30
Unassigned for 6h 00m
Separating performer from owner is what enables workload visibility, accountability, vendor comparison, ownership-gap detection, and resource-level performance analysis. “Resource” is deliberately broad; it is not a synonym for employee.
Long cycle time does not automatically mean too much work. It may mean too much waiting.
Monday → Friday
Those two numbers describe the same Case. Only one of them is a staffing problem, and it is not the big one.
Different Clock patterns point to different interventions: staffing, ownership, workflow redesign, automation, or vendor accountability. When no observed duration exists, the Touch clock falls back to the Interaction’s As-Is Active Time time-study estimate, and tells you which one you are reading.
Every Interaction can represent expected effort, added effort, or avoided effort.
Measured in time and cost
The expected time and cost to perform the Interaction.
Time and cost added beyond Baseline: rework, escalation, failed automation.
Expected reduction in time and cost: automation, AI assistance, avoided handoffs.
Seconds, minutes, and hours of effort per occurrence, rolled up per Case and Workstream.
That same activity priced with your labor rates, vendor fees, or automation costs.
Cost is optional. Time alone is a complete value story.
How long the work took.
Whether the Interaction is Baseline, Increment, or Savings.
Waste interprets Increment activity, not a fourth category.
Operational clocks describe what happened to time. Value Metrics describe what that activity means for value. Both units stay labelled estimated or configured until you reconcile them against your own financial evidence.
Adoption is counted. AI ROI is earned.
Adoption and AI ROI
Where did AI, automation, or human activity participate?
Which Cases and Interactions did it touch?
Did active time, Queue time, or rework change?
Which Baseline, Increment, or Savings came with it?
Is the improvement enough to justify the spend?
Illustrative example data — not customer results
Adoption and impact live in one view, sliced by actor type, by unit, and by Interaction, so AI, automation, internal teams, and external vendors are all judged the same way. Recorded impact uses the contribution captured when the event was observed; Simulation replays that same history against your latest assumptions.
Now take a workflow you already run.
and you are ready
Health plan edition · Next: Getting Started