What TKP 472 regulates
Scope. TKP 472 establishes the procedure for organizing and performing maintenance of security equipment and systems. Design, installation and acceptance are governed by TKP 664; electrical safety during work is governed by TKP 427.
For facility teams, the document matters because it defines the inspection procedure and how to prove the system works.
Traceability is not paperwork here. Every action must leave a record: an act, a protocol, a log entry or a photo. Facilities serviced on an ad-hoc basis usually lack exactly that.
Where it applies
- commercial and residential property;
- industrial and warehouse complexes;
- sites with anti-terrorism protection requirements;
- systems handed over to the facility operations team.
Installation and acceptance checklist (TKP 664)
Installation starts with design and cable routing, not with mounting a camera. In practice, violations occur in three areas: unprepared cable routes, missing labeling, and the wrong mounting height or angle.
- Cable routes follow the design, with service slack and labeling on both ends.
- Connections are made in sealed boxes, not twisted in conduit.
- Camera power is backed up; outdoor nodes use thermal housings and surge protection.
- Recorders are placed in a secured room with restricted access.
- After commissioning, check angles, detail, night performance and archive depth.
Acceptance under TKP 664
A signature on an act proves nothing by itself. Acceptance is a set of measurable checks, and each one belongs in a protocol.
| Check | What it proves |
|---|---|
| All cameras online | No hidden disconnections |
| Day and night recording quality | Footage is suitable for identification |
| Archive depth | Compliance with the declared retention period |
| Time synchronization | Correct time on all devices |
| Backup power | Operation during a power outage |
| Documentation | Schemes, datasheets, log and acts available |
Operations log and documentation
The maintenance log is the primary document during an inspection. It records the date, scope of work, findings, actions taken and the responsible person's signature. Entries must be continuous: gaps are treated as missing maintenance.
Also keep as-built documentation, cable route schemes, an equipment list with serial numbers, acceptance acts, and repair reports. A digital trail strengthens the evidence.
Common mistakes
- An act without a test protocol. Signed, but it does not prove operation.
- No cable labeling. Any fault turns into a blind search.
- A formal log. Entries written in one hand after the fact.
- No archive control. Disks overflow and footage is overwritten early.
- Hidden camera disconnections. The camera is listed but not recording.
Checklist for facility teams
- Is there up-to-date as-built documentation and routing?
- Does the actual camera count match the design?
- Is recording quality tested, not just signal presence?
- Is the maintenance log kept without gaps?
- Are emergency response times fixed in the contract?
- Is there a fleet health report for the last period?
If two or more answers are “no”, the system formally works but does not protect the facility. Start with an independent audit and fix critical findings before replacing equipment.