Public TestsYour infrastructure. Help shape the future of RackDocs.Apply with your team

03 / RACKS AND DEVICES

Connect the rack view to each device record.

A rack view answers “where?”, while a device record answers “which equipment?”. RackDocs connects both, taking you from a mounting position to the individual asset and its connections.

WHAT THE ADMINISTRATOR GAINS

Before maintenance, find the mounting position, equipment identifiers, ports and recorded dependencies.

01 / RACKS AND DEVICES

Document how equipment occupies space

A rack has a defined height, and each device has a starting U position and height. Mounting can reserve the front, rear or full depth, with full width or the left or right half of a position.

Collision checks during saving help prevent overlapping reservations. A 2U device starting at U10 occupies U10 and U11. Switch between front and rear views while keeping the context of the same rack.

Detail of WAW-NET from the front, showing device mounting positions. Click to enlarge.
The same rack from the rear. Full-depth devices remain visible on both faces. Click to enlarge.

02 / RACKS AND DEVICES

Identify the individual asset

Code, name, type, manufacturer, model, serial number and asset number form the core device record. Additional parameters come from its type. Mounting information links back to the location and rack.

Documentation and files can be attached to assets. Rack and device galleries can hold photographs of panels, cabling or identification plates, with access governed by infrastructure permissions. The demonstration screen below shows identity and parameter data, rather than a populated photo gallery.

WAW-CORE01 record: mounting, parameters, model and fictional serial and asset numbers. Click to enlarge.
Close-up of mounting information and inventory fields for a demonstration device. Click to enlarge.

03 / RACKS AND DEVICES

Move equipment without losing its documentation

Moving a device to another rack or mounting place preserves its identity, ports, modules and cable endpoints. The form shows the current location, related port and cable counts and available destination positions.

Document a relocation without creating an unrelated second record. Changing the location in the application does not perform physical work: actual cable routes and patching still need to be checked and documented.

Part of the move form: current mounting, preserved ports and cables and destination selection. Click to enlarge.

Practical workflow

Prepare a switch relocation

  1. Check the device record and space in the destination rack.
  2. Choose the location, mounting face, width and starting U position.
  3. After the physical work, verify cabling, update documentation and review the change history.
Understanding the scope

The rack view represents documented information. A space reservation does not confirm power, cooling or physical dimensional compatibility; the administrator checks these separately.

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.

PUBLIC TESTS / TELL US ABOUT YOUR ENVIRONMENT

Try RackDocs in your own scenario.

RackDocs is in Internal final test. Apply for Public Tests and describe the infrastructure you want to organise. We will contact you about joining the public test edition.

Join Public Tests
Open full-size screenshot ↗