Reports

Reports turn the readings already stored in your Organization into a document someone else can read: a trend study for a single piece of equipment, a compliance record for an inspector, a runtime log for an environmental filing, or a weekly recap in your inbox. Every report is generated from the same time-series data the rest of the platform reads, so nothing has to be re-entered by hand.

Workflow Stage: Report

Introduction

Open Reports in the sidebar. The group holds four entries: Domain Specific for the generator reports, Assets for the asset data report, Scheduled Reports for recurring email deliveries, and Weekly Digest for the organization recap.

The Report stage sits after Analyze and Visualize. Data explored in Platform Explorer and watched on a dashboard is live and interactive; a report is the fixed, dated version of it that can be saved to PDF and handed on. The equipment reports are built around an Asset, so a generator or a service entrance has to exist as an Asset with its Variables attached before a report can cover it.

Domain Specific appears only for Organizations that have the advanced reports feature enabled. Without it the entry is hidden from the sidebar and the page shows "Feature Not Available"; asset data reports, scheduled reports and the weekly digest are unaffected.

Report Types

Report	What it covers	Where it lives
Asset Data Report	Trends the Variables of one Asset over a chosen period, with statistics, insights and optional weather correlation	Reports → Assets
Scheduled Report	Runs an asset data report on a recurring schedule and emails the PDF to a list of recipients	Reports → Scheduled Reports
Generator Compliance Report	Records each generator load test against Joint Commission requirements, pass or incomplete	Reports → Domain Specific
Generator Runtime Report	Lists every generator run split into emergency and non-emergency hours for EPA reporting	Reports → Domain Specific
Weekly Digest	A recap of Alarm activity and Organization changes for the past week	Reports → Weekly Digest

Load factor analysis of utility billing data is part of Energy Management rather than this page: it reads utility accounts, billing periods and bills, and reports peak demand, energy use and load factor per utility company.

Asset Data Reports

The asset data report trends metrics for a single piece of equipment over time. Open Reports → Assets to configure one.

Pick the Asset first. The Variables list then shows everything attached to that Asset, with a Recommended badge on the Variables that carry an electrical classification and a Missing unit badge on Variables that have no unit while the report groups by unit. Select all recommended ticks the classified set in one click. Below the list, Data Aggregation sets the bucket size (from 10 minutes up to 1 day), Group By arranges the results by unit, by classification type or not at all, Timezone controls how timestamps are printed, and Include Weather Data correlates the readings with weather for the Asset's Location. Date Range defaults to the last 30 days.

The Report summary card on the right mirrors the configuration as you build it and counts the days and Variables selected. View Report stays disabled until an Asset and at least one Variable are chosen.

The Asset Data Report configuration page with an asset selected, three variables ticked and the report summary card filled in — Configuring an asset data report: asset, variables, aggregation and date range

The generated report opens as a full-page document: an asset and study summary, a Report Configuration card recording exactly what was requested, a Data Insights section that flags variability, outliers, trends and data quality concerns, then one card per group of Variables with its chart and per-parameter statistics. When weather is included, a weather conditions table follows, and the Asset's Location is drawn on a map at the end.

A generated asset data report showing the asset summary and the report configuration card — The generated report, built from 30 days of stored readings

Three actions sit in the bar above the report. Export to CSV downloads the raw readings, either flat (one row per reading) or pivoted (one row per timestamp with a column per variable metric). Save to PDF renders the same document as a PDF. Schedule delivery carries the current configuration into the scheduled report form so the same report can be sent out on a recurring basis.

The whole configuration is encoded in the page URL, so copying the browser URL shares the exact report with a colleague.

Scheduled Reports

A scheduled report runs on its own and emails the result. Open Reports → Scheduled Reports, click Scheduled Report and choose Asset Report, which is the type available today. The create button is shown to users whose role allows creating scheduled jobs; reading the list has its own permission, so an operator can watch the schedule without being able to change it.

The form is three steps. Report describes what the run covers: an optional Description that labels the row in the list, the same Asset and Variable fields as the one-off report, and a Reporting Window, a rolling period such as the last 30 days that is resolved fresh on every run. Schedule sets the Frequency (hourly, daily, weekly or monthly) with the hour, AM or PM, minute, and day of week or day of month that the frequency needs, plus an Enabled switch. Delivery collects the Email Recipients: pick people from your Organization or type any address. Each run delivers the report as a PDF to those addresses.

Step 2 of the scheduled report form showing the frequency, hour, AM or PM, minute and enabled fields — Step 2 of 3: when the report runs

The list shows every scheduled report with its schedule in plain words, its timezone, its last result and next run time, its delivery method with the number of recipients, and whether it is enabled. Clicking the last run opens Run history for that job. The row menu adds Preview report, which opens the report as it would be generated right now, along with Edit and Delete.

The Scheduled Reports list with two recurring asset reports, their schedules, last and next runs, and email delivery — Scheduled reports, with the last result and the next run for each job

Generator Compliance Reports

Generator compliance reports document that your emergency generators meet the load-test requirements set by the Joint Commission and similar bodies. Open Reports → Domain Specific and choose View Reports under Generator Compliance Reports.

A configuration lists the generators it covers. For each generator you set the Min Load Percentage the machine must hold during a test (30 by default, so a 750 kW generator has to hold 225 kW), the Report Trigger that marks the start of a run (GENERATOR_BREAKER when the generator breaker closes, or ATS_RUN_REQUEST when a transfer switch calls for the engine), any extra Variables to capture alongside the standard ones, and the transfer switches involved with the transfer time each one is required to meet.

Before a configuration can run, the generator Asset needs a maximum load and its Variables need electrical classifications: the editor shows kW Classification Found and Breaker Aux Classification Found when it locates them, and a red badge when it does not.

Reports are generated for you. The platform re-checks each active configuration hourly, scans the previous day for generator runs, and writes one report per run it finds, so a test performed on Tuesday shows up without anyone opening the page. The list of configurations shows how many generators each one covers and when it last produced a report.

The Generator Compliance Reports list showing two configurations with their generator count and last generated date — Generator compliance configurations, each producing a report per detected run

Opening a configuration lists its generated reports by period, each marked Passed or Incomplete, with a filter for the result and an information button that shows why a run was incomplete. A run passes when the generator holds the configured minimum load for 30 continuous minutes. Typical incomplete reasons are that the generator never reached the load threshold, that it held the load for less than 30 continuous minutes, or that a transfer switch took longer than its required transfer time.

The report itself carries the report name, the site address, the period and timezone, any incomplete reasons, a summary per generator with the breaker closing time, the time taken to reach load and how long the load was maintained, then charts of the run with the transfer switch timings and weather at the time. Save to PDF produces the copy you hand to an inspector. If the underlying data changed, Regenerate on a row rebuilds that report from the stored readings.

Generator Runtime Reports

Generator runtime reports track how long each generator has been running and why, which is the information EPA reporting asks for. Open Reports → Domain Specific and choose View Reports under Generator EPA Runtime Reports.

Pick the generator at the top left and the period at the top right; the report opens on the current year to date. The summary counts non-emergency and emergency hours separately, the Runtime Events chart plots each run as a bar in hours, and Generator Detailed Timestamps lists every run with its start time, end time and total duration, labelled Emergency, Non-Emergency, or Emergency (Overridden).

The Generator Runtime report with the emergency and non-emergency hour summary, the runtime events chart and the detailed timestamps table — Generator runtime for the year to date, split into emergency and non-emergency hours

Runs are detected from the generator's engine hours reading, so a generator that reports hours to the platform builds its own log. When a run was recorded as routine but was in fact an outage, the row menu offers Mark As Emergency, which opens Create Override to record the emergency duration and a comment. The original record is kept and the row is then shown as overridden.

Weekly Digest

The weekly digest is a recap of Alarm activity and Organization changes, generated every Monday morning in your Organization's timezone and covering the previous Monday to Sunday. Open Reports → Weekly Digest for the archive, which lists each week with the number of Alarms fired, how many are still unacknowledged, and the timezone the week was measured in.

A digest opens with a summary of the week, the Alarms that fired most often, generator runs when the Organization has generators, and the activity in the Organization such as Devices, Dashboards and people added. A week with nothing to report shows "All quiet". The same digest is delivered by email to members who have not opted out, and appears in the notification bell in the app.

Reporting depends on everything upstream of it. Your equipment has to be Connected and its readings Collected through the Edge Server, and Stored long enough to cover the period you want to report on. Read the numbers first in the Analyze stage with Platform Explorer, or in the Visualize stage on a dashboard, then reach for a report when the result has to leave the platform.

After the Report stage comes Integrate: the REST API exposes the same Assets and Variables the reports are built from, so external systems can pull the underlying data on their own schedule.