Locations and Sites
A physical map of everything you manage — buildings, floors, rooms, racks, customer sites and vehicles — with the assets, stock, networks and power that live at each one.
The problem
Somebody asks which switch is in the Calgary comms room and the answer is a spreadsheet last edited fourteen months ago, a photo of a rack on a technician’s phone, and a guess. A device gets decommissioned and nobody knows which floor it was on, so it stays on the asset register for two more years. A new circuit is ordered for a site whose power budget nobody has measured. When the client asks “what do you actually have here”, the honest answer takes a site visit.
What Solidlio does about it
Every place is a record that nests: site, floor, room, rack. Assets, spare-parts stock, subnets, VLANs, wall jacks, receiving sessions and purchase-order deliveries each point at one, so a site’s page is the complete answer to what is there. Power and rack capacity roll up the whole tree — a PDU in a rack counts toward the room, the floor and the building above it — and a capacity dashboard flags anything over 80%. Floor plans are uploaded, scaled to real metres, and annotated with hotspots that jump to the site or asset they mark. Every change to a site is recorded field by field, with who and when.
Capabilities
| Capability | What it does |
|---|---|
| Nested hierarchy | 17 site types nesting to any depth; re-parenting rewrites the whole subtree in one transaction |
| Asset placement | Put an asset at a site from the asset form; the site’s asset list, count and archive guard follow |
| Stock at a site | Spare-parts inventory per location with on-hand, reserved and available quantities |
| Rack elevations | U-by-U front and rear layout with per-slot labels, asset links, power draw and circuit |
| Power budget | A site’s watt budget against the summed draw of every PDU beneath it, to any depth |
| Environmental sensors | Temperature, humidity, airflow, power, water leak, door contact and smoke, with warning and critical bands |
| Capacity dashboard | Rack and power utilization across every site, flagged at 80% warning and 90% critical |
| Floor plans | Uploaded images, scaled in pixels per metre, with clickable hotspots linking to sites and assets |
| Physical access | Who may enter and how — key, badge, PIN, biometric, combination, remote or escorted — with expiry and revocation |
| Site documents | Leases, permits, wiring diagrams and plans attached to the place they describe |
| Structured cabling | Patch panels, wall jacks, port-to-port connections and a generated patching schematic per site |
| Change history | Every create, field-level edit, move and archive, with actor, IP and timestamp |
Built for MSPs and their clients
An MSP runs its own sites and its clients’. Both sides work from the same site records; what differs is reach.
| Organization | MSP | |
|---|---|---|
| Sites visible | Its own | Its own plus every client it services |
| Creating a site | For itself | For itself or for any managed client, chosen at creation |
| Capacity dashboard | Its own sites | Every site it can see |
| Customer sites | — | CUSTOMER_SITE records linked to the client organization they belong to |
| Change history | Its own sites | Its own and its clients’ |
| End users | Read-only “My Sites” list and detail | n/a |
Reach follows the servicing relationship, not the billing owner: a co-managing MSP holding an active management link sees the client’s sites too. A site identifier outside that set is rejected identically to one that does not exist, so the API cannot be used to probe another tenant’s records.
How it works
- Map the place — create a building, then the floors, rooms and racks beneath it. Type an address once and the autocomplete fills city, province, postal code, coordinates and timezone.
- Record its limits — power budget in watts, cooling in BTU/hr, rack height in U, floor area, ceiling height, weight capacity, commissioning date.
- Put things in it — assign assets from the asset form, book stock in through receiving, attach subnets and VLANs from IPAM, point purchase-order deliveries at it.
- Lay out the rack — click a U slot, set the side, the label, the asset and the draw. The summary shows occupied versus total.
- Watch the capacity — the dashboard compares each site’s rack and power utilization against its budget and lists everything over 80%.
- Show it visually — upload a floor plan, set its scale, drop hotspots that link to the racks and devices they mark.
- Control who gets in — grant badge, PIN or key access with an expiry; revoke it and the grant stays on the record as history.
Compliance and audit
Every location change is written to an immutable log: the action (CREATED, UPDATED, MOVED, ARCHIVED), the exact field, its old and new value, the person, their IP address and the timestamp. A site’s full history can be reconstructed from that log alone.
Physical access is a first-class record. Each grant names the holder — a person in the system, or an external name, email and phone — the access mechanism, the badge number or code, the access level, when it was granted and when it expires. Revocation stamps the record rather than removing it, so a past holder remains answerable for the period they held access.
Sites are archived, not deleted. Archiving is refused while children, assets, stock or an open receiving session still point at the site, and permanent deletion is refused while any receiving history, subnet, VLAN, wall jack or contract reference remains. Purchase-order history survives a site’s removal outright: the delivery link is cleared, the order is not.
Editions
Locations and Sites carries no plan gate. There is no entitlement check, no tier check and no seat limit anywhere in it — every paying tier gets the whole feature. What a person sees depends on portal and role:
| Capability | Customer | Organization | MSP |
|---|---|---|---|
| View sites, assets, stock, power | ● | ● | ● |
| Create, edit, re-parent, archive | — | organization administrator | ● |
| Racks, PDUs, sensors, floor plans | — | organization administrator | ● |
| Access grants and documents | — | organization administrator | ● |
| Capacity dashboard | — | ● | ● |
| Cross-client site view | — | — | ● |
The count of assets you can place at a site is bounded by your plan’s asset entitlement, which is enforced on asset creation.
Integrations
GLPI — entity-to-location mapping, so devices imported from a GLPI entity arrive already placed at the right Solidlio site.
ConnectWise Automate — location mapping on client sync, placing imported agents at their recorded site.
A site record is only worth having if it still matches the room.