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

06 / INVENTORY CHECKS

Compare documentation with reality on site.

The initial inventory is only the beginning. Subsequent checks establish whether records still match reality. RackDocs connects asset identifiers to a separate inventory round workflow.

WHAT THE ADMINISTRATOR GAINS

The team sees what has been checked, what is missing and which discrepancies need investigation, while retaining the inspection’s starting snapshot.

01 / INVENTORY CHECKS

An identifier takes you to the right record

Labels are available for devices, racks, locations, off-rack places, ports, cables, modules and fibres. Filters help select assets, and label dimensions adapt the print layout. Cables receive identifiers for their endpoints.

Stable codes continue to open a record after a name or mounting change. QR does not bypass access controls: the viewer must sign in and have client permissions. The browser print preview can be used for printing or saving a PDF.

Part of the label generator: asset type, location, dimensions and items to print. Click to enlarge.

02 / INVENTORY CHECKS

Each inspection retains its starting scope

An inventory round keeps its own asset list and snapshot from the start of the inspection. On site, select an item, search its code or use QR through a camera, image, pasted identifier or scanner.

Results include confirmed, missing and discrepancy. Counters separate checked items from those still pending. A team can work within one inspection rather than exchange successive versions of an equipment spreadsheet.

Part of the active DEMO-OPEN round: progress, item lookup tools and example results. Click to enlarge.

03 / INVENTORY CHECKS

Separate findings from inventory corrections

An item view compares the starting snapshot with current documentation. This matters when the inventory has changed since the round began. Inspection results include comments, and discrepancies require a description of the observed state.

Photos and attachments can support findings. A result does not move the device or overwrite its parameters. First record the observation, then deliberately correct the inventory.

Starting snapshot and current inventory for the WAW-HV01 server. Click to enlarge.
An inspection result with a discrepancy note. Saving changes the inspection, not the device record automatically. Click to enlarge.

04 / INVENTORY CHECKS

Complete the round with a clear result

Before closing a round, explicitly resolve how unchecked items are handled. A closed round is read-only. A CSV report helps hand over findings and prepare follow-up actions.

This separates what was physically confirmed, what still needs explanation and which corrections were subsequently applied to the device record. Device history adds the later changes to this context.

Practical workflow

Verify a rack during a scheduled inspection

  1. Start a round with the required asset scope.
  2. On site, scan labels and record confirmations, missing items or discrepancies with notes.
  3. Investigate differences, correct the relevant records and close the round with a report.
Understanding the scope

Camera use depends on browser support and HTTPS. Marking an item missing does not delete it; a discrepancy does not automatically update the device record.

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 ↗