The Main Equipment Room (MER) of a building holds one access switch and one or more patch panels. Every suite’s fibre is spliced once onto a panel rear port; a patch cord runs from that port’s front to a switch port; the platform then mints a location for that switch port — the identifier and QR code an order is placed against. This guide walks the chain in the order you work it in the Site Manager.
Open Network → Site Manager → [building]. The Units tab is the register; the Documentation tab is the rack with the wiring sheet.

1. Lay out the units

The register lists every suite the building has. Two numbers describe it:
  • in register — the unit rows that exist (what can be spliced and ordered).
  • planned — the count on the building record, for the pipeline and coverage.
Change layout… (Units tab, or Change layout → on the Overview record) is a tool, not a field: give floors × units per floor and Preview. The plan says what it would add (<floor><nn> — floor 2, unit 3 → 203), what it keeps and which extra units it would remove. Shrinking is opt-in and never touches a unit that carries a subscription, a minted location, a splice or a CPE — the preview names the blocker instead. Use + Unit for the one-off (a penthouse, a 4B).
A unit’s number is frozen once its location is minted — the number is part of the identifier printed on labels. Rename before minting.

2. Splice — rear ports

On Documentation, each panel has a wiring sheet: one row per panel port, Rear · unit on the left, Front · switch port on the right, and the state of the pair.
  • Pick the unit on a rear port to record its splice (one unit per rear port, one rear port per unit).
  • Batch splice… fills a range of rear ports with the units that are not spliced yet, in register order (floor, then number). The preview lists every pair before anything is written; the batch is applied all-or-nothing.
  • + New unit (sheet header, and inside the rack’s Splice dialog) creates the unit the register is missing and selects it — “unit first” is never a dead end.

3. Patch — front ports

The front side is the movable cord to the switch.
  • Pick the switch and its port on a front port.
  • Batch patch… runs a range of front ports onto the switch’s access ports one to one from a start port (front 1–12 → ethernet1/1–12). Ports already patched are skipped; a switch port already used on the panel is not reused.
Re-patching a cord changes the unit’s effective port. Nothing else moves: the splice stays, the location is re-minted in place when you mint again.

4. Mint the location

Back on Units, the Path to service column shows the four steps — spliced › patched › minted › CPE — and a verdict: Mint now on a row, or Mint n ready units in the toolbar, writes the location for the effective port: for a NetBox-synced building the canonical identifier REGION|SITE|MER|UNIT-nn with the unit location, ONT placeholder and cable in NetBox; a legacy-named row on the same port is re-minted in place (same row, new identifier and QR hash). Minting needs the building’s country, province, city and street on the record — the tab says so when one is missing.

Reading the Occupancy column

Occupancy is derived from the subscriptions, not typed: vacant, install pending or active, with the ISP that serves the line and the subscription reference. The operator never sees a customer name here.
  • A subscription can be anchored on the unit (install-path orders) or on the port (captive-portal, QR and partner-direct orders). The register reads both, so a live line ordered against the port shows on its suite.
  • via port marks a line whose subscription has no unit anchor yet. Assign unit sets it, so a unit delete is refused while the line is live and the dispatch board knows the suite. New port-keyed orders get the anchor automatically when the port serves a unit.
  • A CPE bound to the port with no subscription is still vacant: the suite is orderable, the device is simply already there.
Status… in the row is the legacy escape hatch: the stored status the provisioning and the nightly reconciler maintain. Correcting it by hand needs a reason and is written to the audit log.

Deleting a unit

Delete is refused while anything holds the unit: a subscription in any status, a live line on its port, a minted location, a splice or a bound CPE. The tooltip on the greyed button names the blockers; clear them (cancel or move the line, unsplice, remove the CPE) and try again.

At a glance