01
Place panel and devices
Add FACP, initiating devices, notification devices, and pathway assumptions.
Example output
Example: fire alarm device layout for coordination and estimating.
Fire alarm examples show device layout and schedule coordination while keeping AHJ and engineer-of-record limits explicit.
02
Generate schedule
Review device and cable rows.
03
Coordinate
Use output for review with the qualified project team.
Example system intent
A fire alarm coordination page should show the panel, initiating devices, notification devices, cable assumptions, and review notes.
- Device schedules support early estimating and coordination.
- FPLR and circuit assumptions need final review.
- No stamped or AHJ-approved design is implied.
Review focus
Fire alarm is high-risk. The output should make assumptions visible instead of presenting false certainty.
- Check device coverage and quantities.
- Confirm code, manufacturer, and AHJ requirements.
- Separate detection/notification coordination from suppression design.
Common questions
These answers are visible on the page and mirrored in structured data so crawlers see the same content users do.
Is this fire alarm design code-approved?
No. It is coordination output only. Code compliance, stamped design, and AHJ approval remain outside LV-Architect.
Why include disclaimers on example pages?
Because life-safety design requires clear limits. Search pages should not overpromise what the tool can legally or professionally provide.