Routine Test Schedules
Test rules per system type, Done / Due / Missed, walking round the call points, and the logbook PDF.
Routine Test Schedules
A fire alarm needs a call point tested every week; emergency lights need a monthly function test and an annual duration test. dynamik.app knows these rules per system type, works out which period is current, and shows every system as Done, Due or Missed from what is in its logbook — nothing has to be scheduled by hand.
Test Rules per System Type
Rules belong to the system type. Open Projects → Settings → System Types and click the clipboard icon on a type (or Rules on any system's Tests card). A rule has a Name, a Frequency — Weekly, Monthly, Quarterly, Six-monthly or Annual — optional Instructions shown to the person recording the test, and a switch, The person records which device was tested, with the Device type to pick from (the device slug, e.g. call-point).
Every company starts with these rules:
| System type | Rule | Frequency |
|---|---|---|
| Fire Alarm | Weekly call point test — records the call point | Weekly |
| Emergency Lights | Monthly function test | Monthly |
| Emergency Lights | Annual full duration test | Annual |
| Intruder Alarm | Monthly walk test | Monthly |
| CCTV | Monthly recording check | Monthly |
A new rule reaches every system of that type the next time its Tests card is opened. Deleting a rule keeps the history; the test simply stops being expected.
The Tests Card on a System
Each system's Tests card lists its rules with a status badge and a Default frequency dropdown. The switch turns a rule off for this one system (a building with no call points, say); the dropdown overrides the frequency — a site whose insurer wants fortnightly tests can have them without changing the company rule.
Done, Due, Missed
Periods are calendar periods: a week runs Monday to Sunday, a month is the calendar month, quarters, half-years and years likewise. The status is read from the logbook alone:
| Badge | Meaning |
|---|---|
| Done | A test is recorded for the current period |
| Due | Nothing recorded yet this period, and nothing missed before it |
| Missed ×n | The current period is open and the previous n consecutive periods have no test |
| Off | The rule is switched off for this system |
Counting starts from the later of the system's installation date and the day the rule was attached, so a system you add today is never in arrears for last month.
Walking Round the Call Points
When a rule records the device, the form pre-selects the device tested longest ago — devices never tested first, then the oldest last tested date. Week by week the test walks round every call point in the building instead of testing the one by the panel fifty-two times. A device's last tested date only ever moves forward, so a correction to an old entry cannot drag it back.
The Logbook PDF
The Tests card also carries two date pickers with Preview and Download: the logbook for this system over the range, A4, with every entry, who recorded it, the rule, the device and the job. The default range is the last twelve months. Your client can download the same document from the portal if their contact can record tests.