Compliance & Oversight
A bad reading should not wait. The work order opens itself.
Give any checklist item a unit and a normal range. The moment a technician submits a reading outside it — chiller temperature, pump pressure, chlorine level — Laksana raises the work order itself, with the reading, the severity and the evidence attached.
- Chiller 02 · 2°C–8°C
- Reading 11.4°C · out of range
- WO-1042 · one breach, one job
- Photo required on breach
The problem
The reading is on a clipboard. The breach is found at the next round.
Chiller 02 showing 11 today, I think normal?
A bad number sits in a log. The reading is written on a sheet or dropped in a chat, and nobody compares it with the limit until the next round, or until the plant trips.
Pump pressure low again, I told Ah Seng already
Alerts depend on memory. Whether a reading counts as out of range depends on who is reading the sheet, so the response is a phone call, not a rule.
Sent the same reading 3 times, still no one came
Repeats bury the real job. When every repeat of a breach becomes another call or ticket, the one job that matters is lost among the duplicates.
How It Works
Set the range once. Every reading is checked.
The rule lives on the checklist item, so the technician does nothing differently.
1
Set the range
Unit and limits. Add a unit, a minimum and a maximum to a numeric checklist item, switched on per template.
2
Submit a reading
Same check everywhere. The reading comes in from the console, a QR scan, mobile web or a chat bot and is checked against the same range.
3
One work order opens
Severity from the gap. The first breach raises the job with severity mapped from how far out it is; repeat readings comment on that open job.
Under the hood
Ranges on your own checklists
Your ranges, your checklists. Any numeric checklist item can carry a unit, a minimum and a maximum. You switch it on per template, e.g. Chiller 02 at 2°C–8°C; every template you leave alone behaves exactly as before.
Every door in, one brain
Same rules on every channel. The console, the public QR page, mobile web and the WhatsApp/Telegram bots all evaluate readings through the same rules — a breach is a breach no matter how the reading arrived.
Exactly one work order
One breach, one job. The first out-of-range reading creates the job with severity mapped from how far out it is. Repeat readings comment on the same open job — a chiller read hourly never floods you with duplicates.
Evidence when it matters
Proof attached. A breached reading can require a photo before the submission is accepted, and managers are told on the channels they already use the moment it happens — so the job starts with proof, not a phone call.
Works With
Where readings come from, and where breaches go
Preventive Maintenance
Drift becomes a ticket. Scheduled service orders and meter readings that drift trigger corrective work.
Asset QR Management
Scan, then record. The code on the equipment opens a page where a meter reading is logged.
Compliance Checklist
Checklists carry the rules. The templates whose numeric items hold the units and ranges.
Work Orders
Breach lands as a job. The raised work order goes on the board like any other.