Why equipment moves go wrong
Most failed moves are not engineering failures. The server was racked correctly; it was just racked in a U that the drawing said was free and that held a frame nobody had recorded. Or the move was half done when the maintenance window closed, and for a week the documentation described neither the old layout nor the new one. The same causes come up again and again.
- The plan was made against documentation that was already out of date.
- Power and weight were checked in someone's head, or not at all.
- Nobody outside the planner saw the full list of changes before the work started.
- The work happened in a different order from the plan, and the record was updated afterwards from memory.
- Cables were re-patched without the cable records following.
A process that fixes these has four parts: a draft that is separate from the live layout, a reviewed list of differences, an approval with a recorded reason, and a work order that the floor engineer ticks off.
Draft and live: two layouts, never mixed
The live layout describes what is in the racks now. The draft describes what the planner wants. The two must never be the same document. If the planner edits the live record while designing, then for the length of the project the record is wrong, and the on-call engineer who opens it at night sees a server in a rack it has not reached yet.
Keep the draft separate until the work is done. The live layout changes only when the last step is signed off, all at once. Until then, anyone looking at the live view sees the facility as it is, including the half that has not moved.
What the approver should check
The approver does not need to see the drawing. The approver needs the difference: every device that is added, moved or removed, with its old and new position. Read as a list, a change is much easier to check than two elevations side by side. Go through it with these questions.
- Does each target U range exist and is it really free in the live layout, not just in the draft?
- After the change, is each affected rack within its power budget, with one feed able to carry the whole rack? See rack capacity planning for the arithmetic.
- Is each rack within its load limit, with heavy units low?
- Does anything on air depend on a device that moves? Which playout channels, which galleries, and when is the window?
- Are redundant pairs split correctly? Moving the main and the backup encoder in the same step defeats the backup.
- What happens to the cables, and who updates the records?
If the answer to any of these is wrong, the draft goes back with a note that says why. A recorded reason matters more than it seems: three months later, “sent back: A08 over its weight limit” explains a layout choice that otherwise looks arbitrary.
Work orders on the floor
An approved change becomes a work order: one step per move, each with the device, its old position and its new position. Printed, it goes on a clipboard next to the rack. The engineer ticks each step as it is done.
The order of the steps matters in broadcast. Move the backup before the main, so that something is always on air. Install and power-test a new rack before anything goes into it. Retire old equipment last, once the replacement is confirmed working. Agree the order with MCR before the window opens, not during it.
If the window closes with steps left, the ticked steps are exactly what was done. Nobody has to reconstruct it the next morning.
Cables describe now, not the plan
Cables are different from rack positions. A device's position can be planned in a draft and applied later. A cable record says what is plugged in right now, and the on-call engineer relies on it to trace a fault tonight. So cable records should change when the patch actually changes, during the work, not when the plan is drawn.
In practice: before the move, list every cable on each device that moves, with labels such as NW-0001 at both ends. During the move, update the record as each cable is re-patched. After the move, trace a few paths end to end and compare with the real patching. Documenting patch panels and cables covers the record format.
Walk-through: a new rack for storage in the CAR
An example in RoomScene 3D, with example figures. The CAR is running out of space in rack A03. The plan: add rack A08, move five storage units ST-NAS-01 to ST-NAS-05 from A03 into it, and retire KVM-CAR-02, which has been unused since the KVM-over-IP system went in.
- The designer opens a draft for the CAR, adds A08 at the end of row A, and drags the five storage units across. Each is 4U. A UPS with its battery pack goes into the bottom of A08 for the storage. The KVM is removed.
- The capacity page shows “now” and “after the draft” side by side. A03 drops from red to green on U. A08, given an example load limit of 300 kg, turns red on weight: five storage units at 48 kg each plus a 120 kg UPS make 360 kg. The draft is flagged, not blocked.
- The designer sends the draft for approval with a note: “Storage out of A03 to free U for the new playout servers. Weight on A08 to be discussed.” While it is under approval the draft cannot be edited. An import someone runs in the meantime opens a new draft instead.
- The approver reads the list of moves and the warning, and sends it back: “A08 over its load limit. Put the UPS at the bottom of A06, which has the weight headroom, and move ST-NAS-05 only after ST-NAS-04 is confirmed in service.”
- The designer moves the UPS to A06 U1. A08 drops to 240 kg, inside its limit. The designer uses “what fits where” to confirm A06 can take the UPS on power and weight, then sends the draft again. It is approved.
- The approved draft becomes a work order. It is printed for the night shift.
Work order, CAR: storage to A08 (outline)
1 Add rack A08 row A, position 8
2 Add UPS-CAR-03 (new) A06 U1
3 Move ST-NAS-01 A03 U10 A08 U5
4 Move ST-NAS-02 A03 U14 A08 U9
5 Move ST-NAS-03 A03 U18 A08 U13
6 Move ST-NAS-04 A03 U22 A08 U17
7 Move ST-NAS-05 A03 U26 A08 U21
8 Remove KVM-CAR-02 A03 U30 -
During the night the engineers tick the steps. The cable records for each storage unit are updated as it is re-patched, and each change goes to the change log with who and when. When the last step is ticked, the draft becomes the live layout. Who sent it, who sent it back and why, who approved it and when, stays in the draft's history.
Setting it up in RoomScene 3D
- Design mode always works on a draft. The live layout does not change until the draft is applied. See the rack elevation page for how racks and devices are placed.
- Approval is switched on in Settings. Without it, designers apply drafts directly, which suits a small team.
- Power and weight warnings travel with the draft. At 80 % of the budget a rack is yellow, at 100 % red.
- Work orders print cleanly for the engineer on the floor.
- Cables are live records, outside any draft, and every change is logged. Paths can be traced through the patch panels with cable tracing.
The DCIM comparison explains where RoomScene 3D differs from a data-hall DCIM suite. The 30-day trial has every feature on, approvals included; download it and run your next move through a draft.