Operations

Know where a disruption stands and who acts next

Heartbeat routines check your processes on a schedule. Weather and news open incoming reports, and an event past its escalation threshold proposes an incident that a person approves or declines.

The loop

The loop on daily operations

  1. Step 1

    Observe

    Weather and news feeds, connected systems and scheduled Heartbeat checks raise events on the Globe.

  2. Step 2

    Model

    Every process has an owner. Single points of failure and processes without coverage show up on the org view.

  3. Step 3

    Optimize

    Process mining shows where cases wait and which variants loop back for rework.

  4. Step 4

    Act

    An overdue event proposes an incident. A person approves, declines or snoozes it, and the decision is logged.

Process mining

See where lead-to-cash cases wait

The seeded lead-to-cash log as a process map, checked against the reference model, with two variants compared side by side.

  • Conformance against your reference model
  • Rework marked in each variant
The event log draws the process as it actually ran.Conformance checks every case against the reference model.Overlay one variant to see where it leaves the model.Compare two variants side by side.Rework loops are marked in the trace, with the time they cost.
Dashboards

A cycle-time dashboard you can question

An AI-built order-to-cash dashboard on the same log. Explain this chart describes the long tail from the figures it reads.

  • Built from your event log
  • Every figure traces back to the log
Ask for the dashboard you need, in your own words.Wisp picks a template and binds it to your event log.Every tile reads the same event log.Wisp answers only from the histogram's own evidence.
Status

What runs today and what comes next

  • HeartbeatScheduled agent checks whose findings land on the map.Live
  • WatchpointsMonitor a location, region or flow with a cadence and a proposed reaction.Live
  • Owner registry and single points of failureA filterable owner table and markers on processes that depend on one person.Live
  • Owner actions and “Assigned to me”Request a review, delegate a reviewer, transfer ownership or verify, one process or many at once. Each owner sees their queue, access requests and personal workboards.Live
  • Assignments on tasks and commentsRACI roles on lanes and tasks, @-mentions that assign a comment to a person or an agent, and field work assigned by role or team.Live
  • Live cases boardRunning cases projected from your event logs, shown per process step with owner and location filters.Live
  • Dispatch on the mapOperational events on Horizon dispatch into field assignments, which you can reassign and replay.Live
  • Event escalationEvents past their threshold propose a ServiceNow incident for a person to approve.Beta
  • Disruption responseWeather and news open incoming reports with due decisions. Release checks are still open.Beta
  • Process tower dashboardsStarters for order-to-cash, procure-to-pay and other end-to-end processes.Beta
  • Governed work ordersA signed-off process will run its agent tasks as tracked work orders and stop at the human steps you modeled.Planned

Agents propose, and nothing escalates without a person accepting it.

Set up one routine on a process you run

We pick a process with you, schedule a Heartbeat check and look at its first findings together.