Contact

Reporting and analytics

GAUS Reports.
The report is ready
before anyone asks.

A report and dashboard builder. Shift summaries, energy accounting, equipment runtime, regulatory forms — assembled and delivered on their own. Runs inside the GAUS platform and standalone, on top of your own SCADA or BMS.

Today a person
assembles the report

On most sites the shift summary is born like this: an engineer exports the archive to Excel, reconciles it with the event log, adds up the totals by hand and emails it out before morning. That takes from half an hour to half a shift — every day.

The report stays a private file on somebody’s computer. There is no way to check where a figure came from. When that person is on leave, there is no report.

  • Figures disagree. The same number differs between the energy report and the maintenance report, and the argument is settled by whoever speaks louder.
  • Errors stay invisible. A manual summary leaves no trail: a wrong formula in a cell survives for months and feeds into decisions.
  • No retrospective. When someone asks a year later what happened on the night of the failure, the only source is old correspondence.
  • Regulators need a document. A spreadsheet without a signature, stamp or layout will not pass an inspection.
→ Auto

Assembled and delivered on schedule: shift, day, week, month — with nobody involved

→ 5+

Export formats: PDF, Excel, HTML, CSV and more — straight from the interface

→ Inside

Reports are assembled inside your own perimeter — no data goes to external services

→ BI

Power BI, Grafana and Tableau connect to the same data directly

Inside the platform
or on its own

Option 1
As part of the GAUS platform

The builder is already installed and wired to the platform logs. No separate server, database or administrator — a report reads the data where the system writes it.

The module is licensed separately from the platform. We size it for the site.

Option 2
As a standalone product

Deployed next to the system you already run — a third-party SCADA, BMS, accounting or dispatch system. It reads their databases and connects over REST API; the existing system does not have to change.

Fits when the GAUS platform is not being rolled out but reporting is needed now.

Eight reports
teams usually start with

Control room
Shift summary

System status at shift handover, events dealt with, and what is still open.

Chief power engineer
Energy consumption

Consumption by feeder and by load, comparison with the previous period, deviations from the norm.

Maintenance
Runtime and servicing

Running hours, number of starts, and upcoming scheduled service dates.

Chief engineer
Failures and downtime

What failed and how often, how long the system was unavailable, and which failures repeat.

Security
Incidents and alarms

Activations, duty shift response time, breakdown by type and by zone.

Pass office
Access and passages

Passages by zone, passes issued and revoked, and access violations.

Property manager
Tenant report

Climate, availability of building systems and SLA performance — in the manager’s own layout.

Regulators
Statutory form

A document with signature, stamp and watermark — in the form an inspector accepts.

Templates are built
by an engineer,
not a programmer

A report is assembled in a visual editor: the data query, the page layout, the styling. Set up once — after that the template works on its own. Open an item to see the detail.

Charts, tables, parameters and nested structures in one document. Sub-reports and master-detail layouts are built without code: a single template covers both the summary and the per-facility breakdown.

Pivot tables grouped by several dimensions at once — facility, system, period. Totals and subtotals are calculated automatically and the structure survives when a new facility is added.

Grouping, calculated fields and nested tables. Deviations are highlighted where they matter, so the reader does not have to hunt for them.

Filters, drop-downs and control panels. From a summary figure you can drill down to the underlying log records — one report replaces a dozen near-identical exports.

Localisation, watermarks, signatures, barcodes and QR codes. A report can carry the client’s branding and be handed over as a formal document — to a regulator, for instance.

From a sensor reading
to an email

01
Data accumulates
Events, operator actions, setpoint and state changes are written to the platform logs.
02
A template is built
An engineer defines the query, layout and styling once — after that the template works on its own.
03
The schedule fires
Shift, day, week or month — the report is produced without anyone touching it.
04
The document leaves
Delivered to recipients in the required format. The same report is available in the operator dashboard.

The data is already there — it just needs reading

Events and alarms

Filtered by type, priority and time.

Operator actions

Who did what in the system — for incident review and audit.

Setpoints and states

History of equipment parameter changes.

Dashboards and KPIs

Energy use, temperature and response time — with output to a video wall.

If you already have a BI system

GAUS reports do not replace corporate analytics — they feed it.

Method What we hand over When it fits
Files CSV, XLSX One-off exports and exchange with contractors
REST API JSON on request Your own system pulls data on a schedule
Straight from the database PostgreSQL, MSSQL, InfluxDB The BI system reads data with nothing in between
Connectors Power BI, Grafana, Tableau Analytics is already in place and should stay

What buyers ask
before signing

If your question is not here, ask it directly — we answer within one business day.

Yes. GAUS Reports also ships as a standalone product, running on top of the SCADA, BMS or accounting system you already have. It uses their databases and REST APIs as the source; there is no need to move the site onto the GAUS platform.

Inside the platform — no: the builder already runs there and reads its logs. As a standalone product, GAUS Reports is deployed next to your system and connects to its database.

The reporting module is licensed separately — both inside the platform and when deployed alongside a third-party system. The licence depends on the site and the delivery mode: send us the details and we will size it for your case.

Whichever suits you. We build the standard forms for your site during rollout, after which your maintenance team edits them itself — no programming required. Training on the builder is part of the platform course.

No. Reports are produced on your own server, inside your own perimeter — in both delivery modes. No cloud services are involved: a requirement on sites where external connections are forbidden.

Reports are built from the archive you already have — nothing needs to be stopped or rewritten. The depth of the retrospective is limited only by log retention.

We will build your report during the demo

Show us the form you fill in by hand today — we will build it in front of you and send you the finished document.