Reports for Plant and Facility Managers

Run hours, stoppage reasons, excursions outside range, energy, device gaps and raw readings are all counted from the same recorded readings. Each report keeps the history behind it.

Share your requirements

Reports built from one record

Many plants keep run hours in one place, alarms in another and meter readings on a sheet. These reports are counted from the readings the gateway has recorded, so the figures can be set beside each other. They open from the screen supervisors use.

The reports

Run hours and downtime by shift

Running, idle and stopped time per machine, by shift.

Stoppage reasons for the month

Reasons chosen at the panel by the operator, counted over the month.

Excursions outside range

Each one with its duration and, by name, who acknowledged it.

Condition against a batch or date

The history for a batch, a consignment or a date, for a customer or assessor.

Energy, water and fuel

Consumption per machine, line or block, with generator run hours and fuel level.

Devices that stopped reporting

The devices concerned and the gap they left in the record.

Raw readings for any period

Exported as a file or over an API for the period you name.

Who acts on them

The supervisor reads excursions and acknowledgements at handover, and maintenance reads device gaps and the calibration due list. Each report is read by the person who can act on it. Plant heads read downtime by reason and energy per line. Quality heads and consultants take the raw export.

What the figures reflect

The figures reflect what the devices have reported. A reading that did not arrive shows as a gap, and a value that could not physically be true is marked suspect until somebody checks the sensor. Reports beyond this list can be built on the same device readings, and are agreed during scoping.

FAQ

Frequently asked questions

Are the figures live?

Yes. Reports read the current readings, so they change as readings arrive. Buffered readings fill in after an outage with the times they were taken.

Can a report show a stoppage reason?

Yes. When a stop crosses the set duration, the operator picks a reason at the panel, and the monthly count is built from those choices.

Can we take the raw data into our own tools?

Yes. Readings for any period download as a file, and an API serves them into your own tools.

Can other reports be added?

Yes, where the readings are held in the system. Extra reports are agreed with your team during scoping.

Talk to us

Tell us what you need.

Share your requirements and one of our engineers will come back to you within one business day.

What happens after you share your requirements

A senior engineer reads your answers. Nobody phones first.
Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.