The next engineer finds something odd
An engineer attends a service at a school. A sounder circuit does not behave as the zone chart suggests. After some digging, it turns out a colleague changed the cause and effect programming last year when a new extension opened, at the request of the business manager. There is no record in the office of what was changed, why, or who asked. The only record is the panel itself, and the configuration backup is on the colleague's laptop, if it exists.
The engineer spends an hour working out what the programming is meant to do before they can carry on with the service.
Why panel changes go unrecorded
Programming changes are often small, done on site at a customer's request, and recorded in the engineer's head or a line on a job sheet.
- Changes are made at the customer's request without a written instruction.
- Configuration backups are saved on engineers' laptops.
- Zone charts and device labels are not updated with the change.
- The reason for the change is not recorded.
- There is no approval step for significant changes.
What changes are appropriate, and how they are approved and documented, is set by your technical lead and the standards and procedures your firm works to. We build the tools to record and store them.
What unrecorded changes cost
Engineers waste time working out undocumented programming. Mistakes are harder to spot. When a customer later questions how their system behaves, there is no record of who asked for what. And when an engineer leaves, their laptop may hold the only backups for dozens of panels.
A change log per panel, with backups
We build a panel change log linked to each system, used by engineers on site and reviewed in the office.
- Each panel has a change log, visible on the engineer's phone and laptop before and during a visit.
- Before changing programming, the engineer records the requested change, who requested it and why. A request from the customer can be confirmed by them through a link or signature.
- Changes that your technical lead defines as significant need approval before or after, according to your procedure, and the log shows the status.
- The engineer uploads the configuration file before and after the change, where the panel software allows export, so both versions are stored against the panel.
- Updated zone charts or device lists are attached, and the site pack is updated for the next engineer.
- A report shows recent changes by customer, pending approvals and panels with no stored configuration.
| Item | Held today | Held after |
|---|---|---|
| What was changed | Panel only | Change log entry |
| Who asked and why | Engineer's memory | Recorded with confirmation |
| Configuration backup | Engineer's laptop | Stored against the panel, before and after |
| Approval | Informal | According to your procedure |
| Zone chart | Out of date | Updated with the change |
The school's next service, with a change log
Before the visit, the engineer reads the change log. Last year's entry shows the extension's devices were added, the cause and effect was changed at the business manager's request with her confirmation on file, and both configuration files are stored. The zone chart in the site pack reflects the change. The engineer starts the service knowing what the system is meant to do.
When an engineer leaves
Most firms only discover the laptop problem when an engineer hands theirs back. With configuration files stored against each panel as changes are made, a leaver's laptop holds nothing the business needs. For the backlog of older panels, the report of panels with no stored configuration gives your technical lead a list to work through on routine visits, so the gap closes steadily instead of all at once.
What you end up with
A history for every panel that any engineer can read. Backups that belong to the business, not to a laptop. Customer requests that are confirmed and on record. And a technical lead who can see what is being changed across the customer base.
Is this your situation?
- Programming changes are not recorded outside the panel.
- Configuration backups sit on engineers' laptops.
- Engineers find undocumented changes on service visits.
- Customer requests for changes are verbal.
- Zone charts do not reflect changes made.