01 ViVE Genie
Answers grounded in your context
Generic advice is the easy part. Your process is the hard part.
ViVE Genie combines RE-ViVE's computed process measures with your own operating context. Ask a question in natural language and get an answer grounded in the process data — with SOPs, policies and designs available to add the context behind how the work is supposed to run.
Why has onboarding slowed down since April, and what should we do about it?
Onboarding delays commonly stem from incomplete documentation, manual handoffs between teams, and bottlenecks in compliance review. Consider mapping your current process, identifying non-value-adding steps, and exploring automation for repetitive tasks.
You may also wish to review your service level agreements and establish clearer ownership at each stage.
Cycle time moved from 13.1 to 16.6 days between April and August. Almost all of it is one path: cases where documents are returned a second time now run 24.9 days and have grown from 9% to 13% of volume.
The return is triggered at document check, but the delay lands later — those cases wait 14.1 days unassigned before screening. Your SOP for corporate onboarding assigns screening to the regional desk within one working day, which is not what the execution shows.
318,000 cases · SOP-ONB-04 §3.2 · 4,100 cases with no owner on the queue
the applicationdata need not leave
the EDMcomputed, not generated
documentationSOPs, designs, policies
their evidencedrillable to the case
02 Why the answer is different
Your process data. Your operating context. Together.
Generic assistants can explain a process in general. ViVE Genie can answer from your process measures and, when provided, your own documentation — so the answer can connect what happened with how the work was intended to run.
It has the execution data
Quantitative process measures come from the Execution Data Model — the same paths, rework and timing used elsewhere in RE-ViVE.
It has your intent
SOPs, process designs and policies provide the intended operating context, allowing answers to compare observed execution with documented expectations.
It shows its working
Answers can point to the process population and supporting documentation used, with drilldown to the underlying cases where applicable.
03 Where it runs
Keep the deployment aligned with your security boundary
ViVE Genie is designed to work with RE-ViVE deployment options, including private-cloud and on-premises environments. The language-model configuration can be aligned with the security and deployment choices approved for the environment.
For security teams, the important question is where process data, documents and the language model run. That is addressed as part of the deployment design.
04 What you give it
Add the context your teams already use
Existing operating documentation can add context to the process data. Use the materials your teams already rely on rather than creating a new process description just for Genie.
Standard operating procedures
How the work is expected to run, step by step, so observed execution can be compared with the documented procedure.
Process and solution designs
Target flows, decision rules and handoff definitions that help explain intended process behavior.
Technology documentation
System boundaries, integration behavior and job schedules that can help explain where delays occur.
Policies and control definitions
Thresholds, mandated steps and segregation requirements that define the controls the process must respect.
Roles and ownership
Who owns an activity or queue, adding organizational context to a bottleneck or delay.
Local vocabulary
Your organization's terminology, so answers use the language your teams already understand.
05 How the two halves divide the work
Numbers are computed. Language is generated.
The separation matters. Every figure in a Genie answer is read from the Execution Data Model by the Large Process Model, which is deterministic. The language model explains, phrases and connects — it does not produce the arithmetic.
RE-ViVE computes the numbers
Counts, durations, variants, rework and other quantitative process measures are computed from the execution data rather than generated by the language model.
- Case counts, durations and distributions
- Variant, rework and bottleneck detection
- Comparisons across periods and dimensions
- The case population behind every claim
The language model explains
Interprets the question, uses the relevant context and presents the result in natural language.
- Understanding what was asked
- Finding the relevant SOP or design
- Phrasing the answer and the recommendation
- Naming what to look at next
If an answer includes a process measure, that measure comes from RE-ViVE's computation rather than being generated as prose.
06 What it is good for
Ask the question. Get to the evidence faster.
ViVE Genie does not replace ViVE Optim. It shortens the distance between a business question and the process evidence behind it, and makes RE-ViVE accessible to users who may never open a detailed process map.
- What changed in this process over the last quarter, and where?
- Which of our documented steps is most often skipped?
- Where does execution depart from the SOP, and by how much?
- What would you prioritize if we could fix three things?
- Which team is absorbing the cost of this rework loop?
- Explain this bottleneck to someone who has not seen the map.
Recommendations with evidence
Where supported by the process data, suggestions can include the affected population and the time or volume at stake.
See where execution differs from intent
Where execution differs from documented expectations, Genie can point to the relevant process evidence and supporting document context.
Wider access to the same process evidence
People who would not build a report can still ask a question and follow the answer back to the supporting process evidence.
07 The rest of the platform
Genie is one of four ways to use the same process data
ViVE Genie uses the same process data as ViVE Optim, ViVE Comply and ViVE Insights. Move from an answer to the detailed process analysis, control or dashboard behind it.
ViVE Optim
Variants, times, rework, bottlenecks and root cause, with drilldown to the individual case and what-if simulation.
ViVE Comply
SLAs, mandatory and sequenced activities, segregation of duties, and X-R and X-S controls monitored against real execution.
ViVE Insights
Drag-and-drop reports and dashboards over the Execution Data Model, built the way your team wants to monitor the process.