Rack space and power

A rack position connects an asset to a rack code, a starting unit, occupied height and a power figure. It gives the operations team a concrete placement record when equipment is installed or checked. The linked asset carries its service and location context. A technician reading an incident can therefore identify the asset first and then inspect the recorded position without guessing which service the equipment supports.

The rack observation is a record of what the technician submits. The person entering it needs to check the asset and the measured values at the point of work. A wrong rack code or power figure can mislead the next shift, even when the asset link is valid. Review physical labels and the asset tag together before accepting the entry.

The Asset Manager keeps asset identity stable; the Service Technician records the observed placement.

• Asset link. A position belongs to the equipment record that was checked.
• Rack values. Starting unit, occupied height and power are entered together with the rack code.
• Attribution. The technician checks the observation against the physical installation.

Set a rack naming convention that floor staff can use without translation. Agree on how to measure occupied units and power, and who checks those figures after equipment is moved. Define which asset states can receive a current placement. Choose a practice for correcting a wrong observation so that the team can tell what was changed. Use an example from a real rack to confirm that labels, units and power are interpreted consistently.

A technician installs a tagged asset in a named rack. The Asset Manager confirms that the asset is the one assigned to the service under maintenance. The technician records the rack code, starting unit, height and power, then checks them against the physical installation. The operations manager can read that placement from the asset and use it to brief the next shift.

Try a second submission with a missing asset link or an invalid unit or power value. The record should be rejected with a reason, allowing the technician to correct the observation. Repeat with the right values and confirm that the accepted record points to the intended asset.

• Rack positions — Rack code, starting unit, height, power and linked asset in one working list.
• Asset inventory — The equipment identity and service behind a rack observation.

Trace physical work and review the data model.