Which changes should trigger a cross-check?
Check any change to topology, equipment tag, rating, feeder, bypass path, room arrangement, controls interface or source requirement across the related sheets.
| Change | Affected references | Evidence |
|---|---|---|
| Topology | SLD and schedules | Approved markup |
| Equipment tag | GA and cable schedule | Updated source |
| Rating | Notes and protection | Engineer input |
| Room change | Plan and elevation | Current background |
| Control | Schematic and I/O | Logic revision |
How should the old revision be retained?
Keep it in the controlled history with status and issue record. A current file should never erase the record of what was previously issued.
- Revision note
- Source reference
- Affected sheets
- Comment disposition
- Transmittal
What is the final issue gate?
Confirm the set is internally consistent, the current sources are listed and the engineering review status is clear. The responsible engineer performs sign-off.
Common questions
What else should the bid team know?
What should a critical power revision control include?
It should show revision, source, change, affected sheets, reviewer, issue purpose and history.
Who reviews a critical power revision control?
Document control manages the record, while drafting and engineering close the technical review.
Does drafting approve the critical power design?
No. The responsible registered engineer makes design decisions and performs engineering sign-off.
Primary sources
- ANSI/TIA-942 Telecommunications Infrastructure Standard for Data CentersTelecommunications Industry Association
- Tier Standard: TopologyUptime Institute
- NFPA 70, National Electrical CodeNational Fire Protection Association
- NFPA 110, Standard for Emergency and Standby Power SystemsNational Fire Protection Association