01
Place cameras and doors
Build a floor plan with camera views, controlled openings, and head-end location.
Security design
Lay out CCTV and access control systems with cabling and head-end logic.
Use LV-Architect to coordinate IP cameras, NVRs, access readers, controllers, door hardware, network switches, power, and cable schedules.
02
Generate network and access paths
Review NVR, switch, controller, reader, lock, REX, and cabling assumptions.
03
Export for review
Use BOM and cable schedule output for estimating and project coordination.
CCTV and network planning
IP cameras need PoE budget, network paths, switch capacity, NVR sizing, and clear cable schedules.
- Camera count drives NVR and switch assumptions.
- Field cameras route through low-voltage infrastructure rather than floating in the BOM.
- Network drops, patching, and PoE load are visible to the estimator.
Access control coordination
Door systems need reader, REX, lock, controller, power, and life-safety coordination. The tool supports layout and scheduling but does not replace code/AHJ review.
- Reader and lock devices stay tied to door locations.
- OSDP and power wiring assumptions are explicit.
- Door hardware and egress decisions remain project-specific.
Common questions
These answers are visible on the page and mirrored in structured data so crawlers see the same content users do.
Does LV-Architect design door hardware code compliance?
No. It coordinates low-voltage access-control devices and wiring assumptions. Egress, fire interface, and AHJ requirements still need project review.
Can it size PoE switches for cameras?
It can expose switch and PoE assumptions based on placed endpoints. Final switch models and budgets should be validated against selected equipment.