Verana models spaces, fixtures, touchpoints, and feedback as part of one system. Build reusable looks and touchpoint blocks once, then let each room, role, and device context resolve what those controls actually do.
A touchpoint should not need a custom interface for every room. In Verana, the same control resolves to the right space, scene, role, and system state based on where the touchpoint is assigned.
A single ON button can load the correct scene for Ballroom A, Ballroom B, or the combined ballroom because Verana maps the control through context instead of hardcoding the panel.
Build touchpoints from reusable blocks: scene buttons, dimmers, color controls, space selectors, and room controls.
Each touchpoint can keep the same layout while resolving its own space, scenes, roles, defaults, and room-combine state. The result is simpler for operators and far easier to maintain for programmers.
In legacy systems, giving eight ballrooms individual scene control means eight duplicated configurations. Change a color and you change it eight times.
A look is a reusable definition — not a copied scene tied to one room. Apply the same look across spaces, fixture groups, and room-combine states. When the design changes, update the look once and every linked space follows.
Touchpoints resolve the right look for the space they control, so the same interface can serve many rooms without duplicating scene lists.
Verana treats DMX fixtures, Lutron-compatible zones, relay outputs, shades, HTTP devices, and future integrations as Managed Fixtures: endpoints the system is responsible for orchestrating.
Programmers work with spaces, looks, and intended behavior instead of rebuilding logic around every protocol. A Managed Fixture can be a light, zone, relay, shade, sensor, HTTP endpoint, or any other supported control point.
In legacy systems, feedback often has to be custom-built for each integration. Verana makes feedback part of the fixture model.
Where a device or integration supports feedback, its state reports into a shared layer — giving operators and integrators a consistent view of what the system is actually doing, not just what it was told to do.
Spaces and walls are part of the control model. When rooms combine or split, Verana updates fixture membership, active looks, and touchpoint context so operators see controls that match the room they are actually using.
This avoids special one-off panel logic for every possible room configuration. No workarounds. No special programming. The model handles it.
Verana compares the planned fixture list against discovered devices, suggests matches, writes addresses where supported, verifies readback where available, and produces a structured report for the field team. The system automates the tedious parts without taking decisions away from the programmer.
Bring venue calendars, astronomical events, manual schedules, and show-day timing into one trigger system. Build relative actions like pre-show looks, event locks, and restore states without custom scripting.
When a client says a touchpoint is wrong, Verana lets support open the same control experience, observe it, guide them, or take control with permission.
No screenshots. No guessing which button they mean. No site visit for a configuration issue.
Ask plain-English questions about the system, draft common changes, and troubleshoot faster. Verana AI can explain behavior and prepare proposed actions for review.
Programmers can draft schedules, scenes, and diagnostic steps in plain English, then review and confirm before anything changes. It proposes. A human confirms. Nothing important changes without approval.
The local controller operates the building. Cloud services provide remote visibility, updates, diagnostics, and AI-assisted workflows when connected. Because local and cloud tools share the same system model, support understands spaces, looks, touchpoints, and fixture state instead of tunneling into a black box.
A live demo walks through context-aware touchpoints, the look system, remote support visibility, and commissioning on a real installation.