Skip to main content
Virtik
PlatformAnalytics

Reporting that agrees with itself, because every module counts the same events.

Cross-module operational reporting over incidents, response, personnel and compliance.

The problem

What goes wrong without it

Reporting is assembled by hand from systems that count things differently, so the number in the board pack and the number in the operations review disagree and nobody can say which is right.

Analytics reads the same operational event model every module writes to. Incident volume, response performance and coverage all derive from recorded events rather than from separate tallies.

Capabilities

What Analytics does

Described from the current product build. Availability can depend on your deployment and plan.

  • Cross-module reporting on one operational event model
  • Response performance measured from recorded timelines
  • Personnel and coverage reporting across the estate
  • Exports for review outside the platform

Operational workflow

How it is used

These are ordered stages of real use, not a feature list rearranged.

  1. 01Record

    Modules write to a shared operational event model.

  2. 02Aggregate

    Reporting derives from those events, not separate counters.

  3. 03Review

    Compare periods, sites and teams.

  4. 04Export

    Take the underlying data out for external review.

Operating it

Integration, security and deployment

Integrations

  • Export to external reporting and BI tools
  • Personal access tokens (no general public API or scheduled extraction yet)
Integration catalog

Security & permissions

Reports are scoped to the sites and teams the viewer is entitled to. An aggregate never becomes a way to infer data about a site the viewer cannot open directly.

Security model

Deployment

  • Meaningful reporting requires operational history to accumulate
  • Available on Professional and above
Installation Center

Documentation

Where the detail lives

Documentation for this module is being prepared against the product. It is not published yet.

We publish documentation only once it has been checked against the product, rather than listing procedures nobody has run. The documentation home shows what is written, in review or planned.

Documentation home

Related

These read from the same sites, personnel and incidents.

See Analytics against your own sites

A working session using your operational context rather than a scripted tour. If your operation fits a plan available online, we will say so rather than route you through a sales process.