Start with the questions the record must answer
Before anyone picks up a torch and a clipboard, agree on what the documentation is for. In a broadcast facility three people ask three different questions.
- The on-call engineer at 03:00: where is
PO-SRV-04, which rack, which U, front or rear, and what else is in that rack that might be affected. - The planner: is there a free 2U block in the CAR for the new playout server, and can that rack take another 400 W.
- The installer: what is in
A07 U21right now, and which cables go to it.
A rack elevation drawing answers the second question on the day it is drawn. It does not answer the first or the third six months later. The goal is a record per device that answers all three, with the elevation drawn from it.
Fix the naming before the survey
Decide the names first, or the survey produces three spellings of every rack. Write the rules on one page and stick to them.
- Rooms: a short code per room that matches the signs on the doors. CAR, MCR, Studio 2 equipment room, Continuity gallery.
- Racks: row letter plus position, two digits:
A01toA12,B01onwards. Use the label already on the rack if there is one; renaming racks causes more confusion than it fixes. - U numbering: most 19-inch racks number U1 at the bottom, but some manufacturers number from the top. Check each rack's rail markings and record the convention. Record a device's position as the lowest U it occupies, plus its height: a 2U server at U21 occupies U21 and U22.
- Devices: function plus a number, the same as the monitoring host name where one exists.
PO-SRV-04for a playout server,RTR-01for the main router frame,KVM-CAR-02. Avoid putting the rack into the device name: when the device moves, the name becomes wrong. - Cables: a prefix by system and a sequence number,
NW-0001for network,SDI-0412for video. The label printed on the cable is the record key.
Survey one rack at a time
A rack survey is quick if it is methodical and slow if it is not. Work one rack at a time, top to bottom, front then rear.
- Photograph the front and the rear of the whole rack before you start, then each section close enough to read labels. Photos settle arguments later.
- Count U from the rail markings, not by eye. If the rails are unmarked, count holes: three holes per U.
- For each device note the lowest U, the height, the label on the bezel, make and model. Pull the asset tag or serial from the rear or the side if the front has none.
- Record blanking panels and empty U as empty. A gap is information: the planner needs it.
- Look behind. Half-depth devices mounted on the rear rails, a shelf with three small converters, a 0U PDU on the side: these are the items drawings forget.
- Write down the PDUs: how many, which feed (A or B), and which devices plug into which. This is the hardest information to get later.
- Note anything wrong: a device with no label, a unit resting on top of another without rails, a door that does not close. Put these on a list, not in the record.
What to record for each device
Keep the record narrow enough that people will fill it in. These fields cover the three questions above.
| Field | Example | Why it matters |
|---|---|---|
| Name | PO-SRV-04 | The key everyone uses; matches the monitoring host |
| Room / rack / U / height | CAR / A07 / 21 / 2 | Where it is, and how much space it takes |
| Face | Front | Rear-mounted devices are easy to miss |
| Type | Server | Grouping, filtering, capacity planning |
| Make and model | Generic 2U server | Spares, support contracts, power data |
| Serial / asset tag | SN-48213 | Support calls and audits |
| Management IP | 10.20.7.21 | Remote access and monitoring |
| Owner | Playout team | Who to call before touching it |
| Power | 2 × 750 W PSU, A and B | Feed redundancy and the power budget |
| Weight | 28 kg | Rack and floor load |
If a field is unknown, leave it empty rather than guessing. An empty serial is a task for the next visit; a wrong serial is a support call that goes nowhere.
Draw elevations from records, not the other way round
Once every device has a record, the elevation is a report: sort the devices in a rack by U and draw them. In a spreadsheet that means a column per field and one row per device. The drawing becomes something you generate, not something you maintain.
This is the single change that keeps documentation alive. When a device moves, one record changes and every view of it, the elevation, the room plan, the inventory list, follows. When the elevation is a separate Visio file, a move means editing two documents, and the second one is always the one that gets skipped.
Cables follow the same rule. Record each cable once, with its label and both ends, and generate the patching view from that. The details are in documenting patch panels and cables.
Doing it in RoomScene 3D
RoomScene 3D is built on that principle. Each device has one record with room, rack, U position, height, model, serial, management IP and owner, and the front view of a rack is drawn from those records. The front view reads like a rack elevation; the same racks appear in 3D in the room, next to the CRAC units and distribution boards, and in a top view as a floor plan.
- If your survey ends up in Excel, import it. The template has columns for room, rack, U and height next to model and serial, and the preview shows which rows it cannot place, and why.
- Each rack shows free U and its largest free block, nameplate power against its budget and weight against its load limit.
- Ports and patch panels hang off the same device records, so a cable trace runs through the racks you just documented.
- With Zabbix or the built-in ping/TCP check, each device takes the colour of its worst open problem. Gear that cannot be monitored, a passive patch panel or an analogue frame, is marked “not monitorable” so it does not show as missing.
Where nobody trusts the current documentation, the photos from your survey are enough for our modelling service to build the racks, at $40 per rack.
Keep it true after the first move
The survey is the easy part. The record is only worth having if the next change updates it. Three habits do most of the work.
- No move without a record change. The change is planned against the record, and the record is updated when the work is signed off, not afterwards from memory. In RoomScene 3D that is a draft layout, an approval and a work order; see planning an equipment move.
- Label before you leave. A device without a bezel label is undocumented, whatever the database says.
- Audit a few racks each month. Pick racks at random, compare the front view with the real rack, and fix what differs. Small regular checks find drift before it becomes a full re-survey.
The trial runs 30 days with every feature on. Download it, import one room from your survey sheet and compare the front view with the rack.