Infrastructure. Under control.
From existing files to a live infrastructure database.
Transform legacy sources, validate the master workbook and prepare a controlled online migration.
Keep the source unchanged. Identify physical inventory and cable connections before mapping.
Use prompts that never invent data and mark ambiguity with REVIEW.
Check IDs, hostnames, U ranges, overlaps, endpoints and duplicated ports.
Choose an implementation path, validate the workbook and export normalized migration files.
Maintain assets, racks, ports and connections through a controlled operational cycle.
// INITIAL LOAD
INVENTORY contains one row per physical asset. CABLING contains one row per connection and matches Source_Hostname and Destination_Hostname against INVENTORY.Hostname.
// PHYSICAL NAVIGATION
Use Dashboard Racks for rankings, Rack List for technical capacity, Room View for the 10 + 10 physical layout, View Row for a horizontal 42U comparison, and Rack View for vertical detail.
// SERVER & SWITCH VIEW
Select an asset from Rack View. RackScope builds the rear port view from CABLING and shows remote hostname, remote port, type, speed and media.
// DATABASE EVOLUTION
INVENTORY can become ASSET and CABLING can become CONNECTION. Asset_ID remains the stable business key while Hostname supports the initial cable matching.
// MOVING ONLINE
Use Central Excel for a controlled starter, Dataverse for a governed multi-user MVP, or SQL plus an API for automated ingestion. Export the migration package only after readiness checks pass.