Rack Unit Tracking
Back to Data Center Management · Power Circuit Headroom · Cooling Capacity · Growth Forecasting · Service Offerings
Rack unit tracking is knowing exactly how much physical space is actually free, not approximately. The emphasis is deliberate, because the approximate answer is always available and is almost always wrong in the same direction: more optimistic than the truth.
This is the arithmetic sibling of rack elevation diagrams. The elevation is the picture of what is where; this is the question the picture gets asked — can this specific thing go in, and where — and the two answers differ more often than people expect.
1. A Count of Free Units Is Not an Answer
The illustration above is the ordinary case. A rack reports nine free units. A four-unit chassis arrives. It does not fit, because the nine free units are in runs of one and two, scattered between installed equipment.
The useful figure is the longest contiguous run, not the total. A capacity report that says "9 U free" invites a purchase that cannot be installed; one that says "9 U free, longest run 2 U" prevents it. Report both, and treat the second as the real number.
Fragmentation accumulates naturally as equipment is removed one unit at a time over years. It is reversible — consolidating a rack during a maintenance window recovers usable space without buying anything — but only if someone can see that it has happened.
2. Four Things That Make a Free Unit Unusable
Even a contiguous run can fail to accept hardware. A unit counts as available only if all four of these hold.
| Constraint | What goes wrong |
|---|---|
| Depth | A 900 mm chassis in an 800 mm rack, or one deep enough that the rear door will not close over the cabling |
| Weight | The rack has a static load rating and so does the floor. Space can remain while the weight budget is gone — and heavy equipment belongs low, so the free units at the top may be the wrong ones |
| Power | Free units with no outlets left of the right type on both feeds. See power circuit headroom |
| Cooling | The rack is already at the heat load that can actually be delivered to it. See cooling capacity |
Space is the constraint people check first and the one least likely to bind. In a modern estate it is normal to run out of power or cooling for a rack long before running out of units in it.
3. Reserved Is Not Free
Units committed to a project that has not arrived yet must be recorded as reserved, with an owner and a date. Without that, two people plan into the same run weeks apart and find out on install day.
Reservations need an expiry, or they become permanent. A reservation that has passed its date without hardware appearing should be challenged automatically rather than quietly held for a year.
The mirror image is equipment that is decommissioned but still racked. It is not free space and should not be counted as such, but it is the cheapest space you own: recovering it costs a maintenance window rather than a purchase order. Tracking it as a distinct state is what turns it into a to-do rather than furniture.
4. The Things People Forget to Count
- Zero-U space. Vertical PDUs and cable managers occupy the sides, not units — but they occupy depth, and they constrain what can be mounted.
- Blanking panels. They sit in empty units and that is correct; the unit is still free, but somebody has to remove and replace the panel. Track the unit as free and the panel as present, not the other way round.
- Rail and bezel clearance. Some hardware needs a unit of air above or below for cabling or airflow, which makes a 2 U device occupy 3 U of plan.
- The top and bottom units, which are frequently unusable in practice because of cable entry, floor brush, or the containment roof.
- Shelved equipment. Anything on a shelf rather than rails occupies more units than its specification suggests.
5. Keeping the Number True
Rack unit tracking fails exactly the way asset tagging fails, and for the same reason: the data is correct the day it is collected and nothing updates it afterwards.
- Position is a field on the asset, not a separate list. One place to update, and the elevation, the capacity figure and the register all move together.
- The install and removal procedures include the update, in the ticket, as a step.
- Reconcile on a walk, with the elevations in hand, on the same schedule as the asset audit.
- Report usable capacity, not raw counts — longest contiguous run, qualified by depth, weight, power and cooling.
How We Approach It
- Establish the true occupancy of every rack by survey, including what is racked but decommissioned.
- Record the constraints per rack — depth, weight rating and current total, power position, deliverable heat load.
- Compute usable capacity: contiguous runs filtered by all four constraints, per rack and across the room.
- Identify fragmentation worth reversing, and what consolidating would recover.
- Formalise reservations with owners and expiry dates.
- Wire updates into the change process, and hand the series to growth forecasting.
What You Get
- Per-rack usable capacity: total free units, longest contiguous run, and what each run can actually accept once depth, weight, power and cooling are applied.
- A fragmentation report, with the space consolidation would recover.
- Reserved space recorded with an owner and an expiry, and a list of expired reservations.
- A list of decommissioned-but-racked equipment, which is the cheapest capacity available.
- The update step inside your install and removal procedures, so the figure stays true.
The question worth being able to answer in under a minute is not "how much space do we have". It is "where exactly does this particular box go, and what has to be true for it to go there".