What a system is, adding one, its devices and batteries, and the one history per system.

The per-type form holding the panel login, activation code, recovery email and network settings — and where the user and engineer codes actually live.

Test rules per system type, Done / Due / Missed, walking round the call points, and the logbook PDF.

Who writes into the logbook, recording a scheduled test, what a failed test triggers, and correcting an entry.

The daily emails to the client's responsibles, the escalation to you after two misses, and the dashboard queue.

Maintenance jobs generated from the service schedule, and remedial jobs built from what failed.