01
Place endpoints
Add cameras, doors, readers, locks, controllers, NVR, and switch.
Example output
Example: security and access control layout with cable schedule.
Security examples should show how cameras, NVRs, door devices, controllers, switches, and cable runs are coordinated for review.
02
Generate paths
Review network, access-control, power, and cable assumptions.
03
Export
Use the BOM and schedule for estimating review.
Example system intent
A security design package should explain camera coverage, access-controlled openings, reader/lock/REX assumptions, head-end devices, and cable types.
- IP cameras affect PoE and switch count.
- Access devices must stay tied to door locations.
- NVR, controller, and network paths should be reviewable.
Review focus
The value is in surfacing missing endpoints, under-sized switches, ambiguous locks, and uncounted cable runs before estimating.
- Check each door for reader, lock, REX, and controller path.
- Check each camera for network and recording path.
- Confirm life-safety coordination outside the generated package.
Common questions
These answers are visible on the page and mirrored in structured data so crawlers see the same content users do.
Does the tool decide door egress code?
No. It coordinates low-voltage devices and wiring assumptions. Door hardware, egress, and AHJ requirements require project review.
Can cameras and access control be in the same project?
Yes. LV-Architect is meant to coordinate multiple low-voltage disciplines in one project model.