An AV touch panel can run lighting, blinds and air-conditioning scenes, as long as the AV system asks the building systems to act and does not replace them. Each building system keeps its own controller, wall switches and safety behaviour; the AV panel sends scene commands through a defined interface. If the panel fails, the room must still be usable.
This reference is written by Singapore-based AV and IPTV integrator Prestige Solutions for technical managers, AV consultants and system integrators who plan AV control and signal routing for meeting rooms, ballrooms and multi-purpose venues. It covers the interface choices, who should own each system, how to sequence scenes, what must stay outside AV control and the tests we expect at handover. Protocol facts are general as of 2026; confirm the gateway and controller documentation for the actual equipment.
Use the interface the building system already speaks, through a gateway the building contractor supports. The AV programmer should not wire directly into dimmer or motor circuits when a supported bus or IP interface exists.
| System | Common interface | What the AV panel sends | Planning notes |
|---|---|---|---|
| Lighting, addressable | DALI through a gateway; KNX; vendor IP API | Recall of a stored scene or group level | DALI (IEC 62386) supports up to 64 devices and 16 groups per line, so scenes are stored in the lighting controller and recalled by number |
| Lighting, conventional | 0-10 V dimming or relay contact closure | On, off, fixed level | Contact closure gives no feedback unless a status contact is wired back |
| Motorised blinds and curtains | Dry contacts (open, close, stop), KNX, RS-485 or IP motor controller | Open, close, stop, preset position | Check whether the motor supports position presets or only end stops |
| Projection screen | 12 V trigger or contact closure | Down and up | Link to the projector warm-up so the screen is not lowered with the lamp off |
| HVAC, room unit | BACnet/IP (UDP port 47808), Modbus TCP (port 502), or a gateway | Mode and setpoint request within limits | The BMS normally stays the owner of the plant; the AV panel requests, it does not command the plant |
| Occupancy and CO2 | Read-only from the BMS or room controller | Nothing; only shown on the panel | Do not let AV logic override a ventilation interlock |
For any of these, ask the building contractor to name the interface point in writing: the gateway model, the address list and the person who maintains it. An interface without a named owner is the most common reason a panel button stops working a year after handover.
Split ownership by function and write it in a responsibility matrix before programming starts. Disputes over "whose fault is it" cost far more time than the programming itself.
| Item | Owner | AV integrator provides |
|---|---|---|
| Lighting scene definitions and levels | Lighting contractor or lighting designer | Scene numbers on the panel and a recall command |
| Gateway, bus and addresses | Building or electrical contractor | IP address, port and command list agreed |
| Blind motor limits and presets | Blind contractor | Open, close, stop, and preset commands |
| Setpoint limits and schedules | BMS contractor or facility team | Request buttons within the allowed range |
| Panel layout and scene sequencing | AV integrator | Programming, user text and documentation |
| Safety systems | Fire and life-safety contractors | No control; read-only status at most |

Run the scene as an ordered list of short steps with a feedback check between them. A "Presentation" scene that dims lights, closes blinds, lowers the screen and starts the projector should not fire everything at once on a shared supply.
Keep the sequence in the control processor, not on the panel itself, so a panel reboot does not interrupt a running scene. The same approach applies to source routing, as described in the AV signal path maintenance plan.
Keep life-safety functions outside the AV system entirely. This is a design rule as well as a good practice: the AV integrator cannot test or certify those systems, and a software fault must never be able to affect them.
Where a fire alarm contact is used, wire it as a normally closed supervised input, so a broken cable shows as an alarm rather than silence.

Let the panel request a setpoint within a narrow band and show the actual room temperature next to it. Giving users the full range of the thermostat invites a complaint every time a presenter turns the room to 16 degrees and leaves it.
| Setting | Planning starting point | Reason |
|---|---|---|
| Setpoint range on the panel | Plus or minus 2 degrees around the BMS default | Limits energy waste and conflict with the BMS schedule |
| Return to default | Automatically after the event, or at a set time | Prevents a setting from staying overnight |
| Fan or mode choice | Hidden unless the venue needs it | Fewer buttons, fewer wrong choices |
| Pre-cool before an event | Requested through the booking system, not the panel | A large room takes time to change |
For rooms that are booked through a calendar system, the HVAC and lighting state can follow the booking times. That integration belongs with the room booking interface, not on the touch panel.
Every building function must have a local fallback: wall switches for lighting, key switches or wall controls for blinds, and a thermostat for the room. The panel then adds convenience on top of a system that already works.
| Failure | Expected result | What to check |
|---|---|---|
| Panel offline | Wall switches and thermostat still work; the scene stays as it was | Wall switch labelling and access |
| Control processor offline | Building systems keep their last state; no scene recall | That no output defaults to an unsafe state |
| Gateway offline | Panel shows the function as unavailable | Status feedback on the panel |
| IP address changed | The related buttons stop working | Reserved addresses and the address list |
Test every scene with the real equipment, and test the failure cases as well as the normal ones. A pass means the room operator can use the panel without training and recover without calling the integrator.

Not safely. Each motor needs its own interlocked up and down outputs, and the two loads should have separate circuits and overload protection. Sharing outputs also prevents separate scenes for the two devices.
The party that maintains the building system, with a copy in the handover pack under the venue's own password policy. The AV integrator needs only a service account with the rights required for scene recall.
Yes, if the BMS or room controller can provide it as a read-only value. A panel that shows only the setpoint suggests the room has reached it, which causes complaints when the plant takes time to respond.
Visit Prestige Solutions for the wider AV and IPTV service range.
Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337 or +65 9825 8218, message us on WhatsApp (+65 8010 2337), or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.
Explore our full product range or speak with our technical team for a tailored consultation.