Practical guide
NFPA 70: documenting building power and circuits
Review the electrical information needed by fire alarms, automation, access control and video systems.
Power problems can appear as communications loss, panel trouble, restarts or recording interruptions. Before attributing a fault to software, document the power sources supporting the building’s systems and check them against the engineering.
Where NFPA 70 fits
NFPA 70, the National Electrical Code (NEC), addresses electrical design, installation and inspection. For a project in Peru, the applicable basis must be established with local provisions, approved documentation and the technical lead. Publication of a newer NEC edition does not mean it has automatically been adopted for the building.
Electrical information supporting diagnosis
- Power diagrams, distribution boards, identified circuits and connected loads.
- Primary and backup supplies, batteries and an uninterruptible power supply (UPS) where relevant, with capacity and maintenance records.
- Conduit routes, conductor identification and circuit separation documentation under the approved design.
- History of outages, power disturbances, ground faults and correlated equipment events.
Connect each symptom to evidence
| Symptom | Information to check | Acceptance |
|---|---|---|
| Recurring restart | Event history, power supply and equipment dependencies. | Supported cause and stability verified over an agreed period. |
| Unverified backup | Load, capacity, condition and secondary supply documentation. | Approved validation method and recorded result. |
| Unidentified circuit | Drawings, labels and traceability to the supplied system. | Reviewed identification and updated drawing. |
Scope, safety and restoration
Electrical measurements and intervention require competent personnel, appropriate permissions and a safety procedure. Do not improvise disconnections to assess backup power or alter protective devices without engineering. Planning must account for the shared dependencies of fire systems, servers, communications, access control and video.
A proposed correction needs available backups, a work window, contingency measures and return-to-service testing. Reports should distinguish document observations, completed checks and unverified conditions. Calculations, drawings and protocols may require a registered engineer’s signature under the agreed scope.
How BBS organises the work
- Initial assessmentInventory, fault history and criticality.
- Intervention planScope, permissions, owners, contingency and acceptance.
- Execution and testingChange control and verification of authorised interfaces.
- Handover and follow-upEvidence, validated results and outstanding actions.
Sources and scope
Public reference sources checked on 5 October 2026. This BBS guide provides planning recommendations; applicable editions and requirements must be validated for each project.
LET’S TALK