Equipment downtime log

When it went down, what it affected, and when it came back.

Out of service from, what was affected, who attended, expected back, and what actually fixed it — filed against the equipment in your asset registry rather than a second list of machines. This is the history that makes a repair-or-replace conversation an argument from evidence. It computes no uptime, availability or cost-of-downtime figure.

What the equipment downtime log is for

Out of service from, what was affected, who attended, expected back, and what actually fixed it — filed against the equipment in your asset registry rather than a second list of machines. This is the history that makes a repair-or-replace conversation an argument from evidence. It computes no uptime or availability figure. The thing you came to do is “record an outage”, and this is the page that does it.

It is filed under maintenance & work — dispatching, doing and proving the physical work — and under “track something”, which is registers that answer a question later. There is one page for it, at this address, however you arrived.

When people reach for it

  • When it went down, what it affected, when it came back — people arrive here typing “downtime”, “out of service”, “equipment down”.

What it records, and where the record goes

When it went down, what it affected, and when it came back. What you enter stays in this browser, on this device. There is no account to make and nothing is uploaded; it reaches another device only if you activate CompliMaint Cloud Beta and sign in.

  • Records — every document this device holds, filed as you work.
  • CompliMaint Facilities — Know what is required, do it on the day, keep the record that proves it.
  • Equipment — Plant, machines and the record of what was done to them.

Related tools and workflows