Floor Plans

Floor plans are the centerpiece of LogicSite. They provide the visual foundation for placing devices, planning coverage, and communicating your system design to clients and team members.

Uploading Floor Plans

Supported Formats

• PDF — multi-page supported. Each page becomes its own floor plan page. Sheet numbers are auto-detected from title blocks (4-strategy fallback).
• Images — PNG, JPEG, and TIFF (auto-converted to PNG). Max 150MB per file.

Navigating the Canvas

• Pan — click and drag
• Zoom — scroll wheel or pinch
• Fit to screen — reset view to the full page
• Rotate page — pages can be rotated in 90° steps when no devices are placed yet

Multi-Page Floor Plans

Every page of a PDF becomes its own canvas — ideal for multi-story buildings, multi-building campuses, or phased documents. Pages uploaded together in a single operation stay grouped as one version in the version tree. Navigate between pages via the page selector in the editor header.

Reordering Pages

Open the Pages panel in the sidebar and click the gear icon in the panel header to enter reorder mode. Drag pages by their handles to rearrange them, then click the check to save or the X to cancel. The active page stays anchored to the same content — if your current page moves to a new slot, the editor follows it without losing your zoom or selection.

Floor Plan Editor Tools

The toolbar exposes these tool modes:

• Select — drag to move device icons, anchors, and annotations
• Add Device Group — drop a new device group anchor at the clicked location
• Add Cloud / Arrow / Text / Circle — the four annotation types
• Detect Symbols — server-side symbol detection on the rasterized page (surfaces candidate device placements for review)

Layer Visibility

Every page has per-layer toggles controlling what renders on the canvas:

• Anchor Label — the text label next to each device group anchor
• Device Icon — the SVG icon inside each device group
• Device Lines — connecting lines between group anchor and child device badges
• Status Dot — the colored status indicator on each anchor
• Annotations — clouds, arrows, text, circles
• Coverage — camera cones, reader read-ranges, and other device-specific coverage shapes

Visibility is saved per page. Press V to cycle through six preset combinations (full view, clean view, devices only, annotations only, etc.). Coverage shapes are direction-aware (right / bottom / left-right / 360°) and can be edited per device from the device detail drawer.

Edit Locks

Floor plans support two lock modes to prevent concurrent or unauthorized edits:

• Project Lock — auto-engages when the project moves out of Design. Project managers can request a temporary unlock for adjustments. The unlock modal exposes a "This is a Change Order" toggle.
• Site Lock (site owners) — a facility-manager protection lock with optional duration or indefinite hold, shown with a Shield icon. Only users with the canManageLock permission can toggle it.

The edit lock badge in the editor header shows the current state: green (unlocked / design) or orange (locked).

Floor Plan Versioning

LogicSite uses a version tree (Google Docs model) for floor plan documents. Versions are structure-owned, so site owners and contractors share the same history across projects.

Structure: Building A – Floor 2
└── v5  As-Built (current)             ← isLatest = true
    ├── v4  CO #2 – Panel relocation   ← named milestone
    ├── v3  CO #1 – Added 4 cameras    ← named milestone
    ├── v2  Contractor working draft
    └── v1  Original Design            ← frozen at project start

• Named versions (change orders, milestones, as-builts) are surfaced prominently.
• Minor edits between milestones collapse under a "Show full history" toggle.
• The project tab filters to the project's own versions; the structure tab shows the complete history across projects.

Change Orders

Change orders are created from the floor plan unlock modal:

Conduits and Junction Boxes

LogicSite models physical cable runs as a graph: junction boxes (nodes) connected by conduit paths (edges). Branching emerges naturally by sharing a junction box between multiple paths.

Junction Boxes

Junction boxes are first-class canvas entities. Each has a label, border color, text color, and an auto-derived border width taken from the heaviest incident path. Click a JBox to open its detail drawer, which lists every conduit path touching it with a stroke swatch and from-to label preview.

Drawing a Conduit

Hold Shift while moving to disable snapping. Press Esc or right-click to abort before the second click — nothing is persisted until then.

Path Types and Routing

Orthogonal routing injects a single computed elbow when no waypoints are set, aligned with the dominant axis between the two endpoints. Up to 10 total nodes per path (2 endpoints + 8 waypoints).

Annotation Links

Junction boxes can be visually linked to annotation labels with a dotted connector, mirroring the device-to-annotation pattern. Use this to tag a JBox with a reference note without crowding the canvas.

Floating Panels and Action Menus

Selecting a shape on the canvas surfaces a floating action menu (anchored chip row with Edit, Duplicate, Delete) and a floating edit panel for inline property edits — both dismiss on outside click or Escape, and isolate keyboard events so editor shortcuts don't fire while typing.

Best Practices

• Name floor plans clearly — "Level 1 – Main Lobby" beats "Page 1".
• Upload the latest revision — older named versions remain in the tree for audit.
• Use vector PDFs — crisp at any zoom, faster server-side rasterization.
• Leave Coverage on during design review — fastest way to spot gaps before Install.
• Share junction boxes — a single JBox shared across paths is cleaner than parallel runs.

What's Next?