01 / STRUCTURE
From a client to a mounting place
An organisation maintains infrastructure grouped by client. A client can represent a customer company or a separate documentation scope. Within each client, you create locations, then racks and named off-rack mounting places.
A location code, name and description provide a common reference. The same context appears on device records, cable endpoints, topology and reports. A cable can connect different racks and locations within the same client.
02 / STRUCTURE
Review racks before entering the server room
The rack list takes you from a location to an individual enclosure. Codes, names, height in U and device counts help identify the correct rack. Its record then expands this overview into mounting and connection views.
Agree on one naming convention for locations and racks. A label such as WAW-NET becomes a recognisable part of the infrastructure address in records, on printed labels and when speaking to an engineer on site.
03 / STRUCTURE
Equipment does not have to live in a rack
Named mounting places describe a desk, wall, storage area, room or another installation point. The inventory can therefore include equipment that does not belong at a particular U position.
This is useful for access points, edge equipment and IT or OT infrastructure outside a conventional server room. The asset still belongs to a location and can have ports, connections, custom parameters and a QR identifier.
Practical workflow
Prepare an inventory for three branches
- Create a client and agree on location codes.
- Register rack heights and named mounting places for equipment outside racks.
- Assign devices to these places, then document their ports and connections.
Locations and mounting places are documentation records. Creating them does not automatically discover devices or check their presence on the network.
Screenshots come from the working RackDocs application and show a demonstration environment with fictional infrastructure. They include selected views and screen details; the application is evolving. Screenshots retain the Polish interface in this English guide.