platform

01 ViVE Insights

Your own reports and dashboards

The report you need is rarely the report you were shipped

ViVE Insights lets business users build the reports and dashboards they actually need from the Execution Data Model — choosing the measures, filters and layout without writing SQL.

field palettefieldsCasesCycle timeVariantWaiting timeRegionProductTeamCase valuefield in flightcanvasOperations review — onboardinglast 90 days · all regionswidget: bar chartcycle time by regionwidget: metric tilesheadline metrics16.6days avg38%rework2,847variantswidget: tableslowest variantsdocuments returned twice24.9 doffshore screening route21.4 dmanual credit override19.8 dwidget: trendrework trend
Fields on the left come from the Execution Data Model, so a report built here uses the same variant, rework and timing definitions as a process map in Optim or a control in Comply.
Drag and drop
no SQLanalysts build their own
Every EDM field
availablenot a fixed subset
One set of
definitionsshared with every module
Share and
scheduleto the people who need it

02 Why a builder rather than a report pack

Fixed reports answer last year's question

Pre-built reports are useful, but business questions change. ViVE Insights lets the person with the question build the view while RE-ViVE keeps the underlying process measures consistent.

  • Can I see this by product rather than by region?
  • What does this look like for the top fifty accounts only?
  • Can we put the SLA figure next to the rework figure?
  • Can the shift lead have this every morning at seven?
  • Why does the ops number differ from the finance number?
  • Can I add a filter without raising a ticket?

  • The question owner builds it

    Build the view directly without waiting for a separate report-development cycle.

  • Definitions stay central

    Cycle time, rework and variant mean one thing across the platform. Teams choose the view, not the arithmetic.

  • Drilldown comes for free

    Reports can drill from a summary measure back to the individual case because they use the same Execution Data Model.

03 What you can put on a canvas

Use the process data already in the EDM

ViVE Insights exposes the measures, process structures and mapped business attributes available in the Execution Data Model, so users can combine process performance with business context.

Available fields — Execution Data Modeldrag any field onto the canvas
measures
  • Case count
  • Cycle time
  • Working time
  • Waiting time
  • Rework count
  • Rework days
  • Handoff count
  • Case value
process structure
  • Activity
  • Variant
  • Transition
  • Rework loop
  • Path length
  • First activity
  • Last activity
actors
  • User
  • Role
  • Team
  • Site
  • System
  • Automated agent
business context
  • Customer
  • Product
  • Region
  • Channel
  • Priority
  • Segment
  • Mapped source attributes
time
  • Day
  • Week
  • Month
  • Quarter
  • Period comparison
  • Rolling window
control results
  • Rule
  • Outcome
  • Attainment
  • Projected breach
  • Exposure

Control results can appear beside process measures on the same dashboard because ViVE Comply and ViVE Insights use the same underlying process data.

04 How a report gets built

Four moves, no code

The interaction is intentionally familiar: choose fields, select a visual, filter, compare and arrange the result. RE-ViVE handles the process relationships underneath.

one

Drag the fields

Pull measures and dimensions onto the canvas. Their relationships are already defined in the EDM, so report authors do not build joins themselves.

two

Choose the visual

Table, bar, line, distribution or metric tile. Swap between them without rebuilding the underlying cut.

three

Filter and compare

Scope to a period, a region, a variant or a value band, and set a comparison period alongside it.

four

Arrange and share

Lay widgets out as a dashboard, then share it or schedule delivery to the people who run on it.

05 What teams build

One data model. Different views for different teams.

Operations, process teams, risk and executives often want different views of the same process. They can build those views without creating separate data definitions.

operations

The morning queue review

Open cases by age against SLA, cases approaching a threshold, and the activities where work is currently sitting.

process excellence

Variance by site

Cycle time, rework share and variant count per site, ranked, with the gap to the best performer sized so the standardization target is not theoretical.

risk and audit

The control pack

Attainment per rule, violations by type and owner, and trend against the previous period — assembled once and scheduled rather than rebuilt each quarter.

executive

The monthly one-pager

Cycle time, cost of rework, exposure and direction of travel across the processes in scope, on the same definitions the operating teams use.

06 The rest of the platform

Insights is one of four ways to use the same process data

The same process data used in ViVE Insights also powers ViVE Optim, ViVE Comply and ViVE Genie, so teams can move between dashboards, process analysis and controls using the same definitions.

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 Genie

Ask questions in natural language using the same RE-ViVE process data, with your SOPs and designs available as additional context.

See how the platform is builtArchitecture & deployment