What is Carrotz?#

Carrotz is a system for maintenance, documentation, risk and compliance. It is used to plan work, carry it out and document it, and to show afterwards what was done, by whom and when.

The terms you’ll meet everywhere#

These recur throughout the system. Once you have them, the rest of the documentation makes far more sense.

Term	What it means
Location	Where the work is. Building, site, plant room, pump station. Organised in a hierarchy that mirrors the facility.
Object	What it concerns. Pump, motor, vehicle, valve, lift, compressor or building. Can have sub-components.
Work order	The job itself, to be planned, carried out and documented. Often abbreviated WO.
Work type	Why the job exists: preventive, corrective, internal control, condition check or one-off job.
Task	A single job inside a work order, tied to one object or one location. A work order can have several.
Sub-item	The individual points in a checklist task. A task can have many.
Checklist	Fixed points to be reviewed the same way every time the work is done.
Maintenance plan	The rule that makes Carrotz create work orders automatically — at a fixed interval, or based on a meter reading.
Measuring point	A value recorded on equipment: temperature, running hours, pressure, number of cycles, mileage. Can be set up to trigger a work order when a threshold is reached.
Case / deviation	An event or need that must be followed up: rule breach, technical fault, HSE incident, improvement suggestion.
JSA	Job Safety Analysis — an assessment of the risk in a specific job, before it is carried out.
Discipline	Trade or specialism. Used to assign work and to control who must sign documents. A user has one main discipline and can be linked to up to four more — five in total.
Department	Separates data between parts of the organisation.

How it fits together#

The most common chain through the system looks like this:

Location  →  Object  →  Maintenance plan  →  Work order  →  Work done  →  History
                ↑                                 ↓
         Measuring point                   Case / deviation

A maintenance plan tied to an object at a location creates work orders automatically. The field user carries out the work order, and everything recorded along the way becomes history on the object. If something is found to be wrong during the job, it is recorded as a case/deviation, which in turn can trigger a new work order.

What Carrotz is used for in practice#

Daily checks and rounds — fixed checklists carried out and documented
Planned maintenance — weekly, monthly or annual servicing that creates itself
Condition-based maintenance — work triggered when a measured value passes a threshold
Deviation handling — recording and following up faults, incidents and improvements
Documentation and compliance — O&M documentation, procedures, instructions and signing
Risk management — risk assessment and JSA before the work is carried out

Everything you record along the way becomes history. It is that history which makes reporting, auditing and condition assessment possible later — which is why it pays to record while the work is happening, not afterwards.