01 / INVENTORY STANDARDS
A type defines the information you collect
The catalogue includes common types such as servers, switches, routers, UPS units and patch panels. You can create a client-specific type or a variant of an existing type. Private standards remain within that client’s scope.
A type combines a name, code, icon and inventory fields. It separates structured equipment information from free-form notes. An administrator no longer has to decide where to put firmware versions or capacity on every new record.
02 / INVENTORY STANDARDS
Add parameters that suit your environment
Custom fields support text, numbers, dates and yes/no values, and can be required. A stable field key identifies the parameter independently of its readable display name.
In an OT environment, these fields could describe an industrial switch, communication gateway or edge computer: for example a production area identifier, firmware version or inspection date. These are examples of using generic custom fields, rather than dedicated automation modules.
03 / INVENTORY STANDARDS
Create repeated equipment from a template
A template defines device height and ports on both faces. The library offers a starting point for common configurations. Clone a global template to tailor it to a client’s standard.
When creating another device, use the prepared layout rather than defining every socket again. Cloning a device copies its data and ports, but does not recreate its cables. Template changes apply to new devices; existing equipment retains its own documentation.
Practical workflow
Create a standard for equipment across a facility
- Select a standard type or create a client-specific one.
- Add useful fields such as installation area, firmware and inspection date.
- Prepare a port template, then create and document individual assets.
RackDocs supports OT documentation through generic inventory records, custom types and fields. It does not claim industrial protocol support, controller polling, process control or SCADA functionality.
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.