AV systems integration
Audio, lighting and video for theatres, concert venues and live events, designed to be operated by the people who work in the room.
Systems integration for live entertainment · Hamilton, Ontario
Ticketing, event management and venue operations software, plus the AV, show control, building automation and networks underneath it. Designed, built and commissioned by the same shop, for theatres, concert venues and live-event spaces across southern Ontario.
The platform
A venue is not a ticketing problem with some admin attached. It is one organisation where a ticket, a membership, a volunteer shift and a donation all belong to the same person. We build the system that treats it that way, and it runs a working theatre every night.

Seat maps, timed holds, subscriptions, comps, exchanges and QR check-in at the door. No commission skimmed off every ticket.

Rehearsals, performances, outside rentals and volunteer rotas against the same rooms and the same calendar.

Patron records, renewals, fundraising and grants, concessions, reconciliation and the reports a board actually asks for.

Software and building, one shop
Most software vendors hand you an integration guide and wish you luck. Because the same shop specifies the network, hangs the lobby displays, wires the door scanners and programs the building's own controls, the platform reaches the actual venue instead of stopping at the browser.
Disciplines
Real venues do not respect the boundaries between trades. A lighting rig depends on a network, a box office depends on data getting somewhere useful, the house lights and the HVAC need to know the show has started, and all of it depends on someone having written down how it works.
Audio, lighting and video for theatres, concert venues and live events, designed to be operated by the people who work in the room.
Cue automation, playback workflows and motorised stage systems tied together so one trigger does what it should, every night.
HVAC, house lighting and the building's own systems programmed to behave with the show, from the pre-show warm-up to the last patron out.
Networks for venues where production traffic, operations and public access have to coexist without sharing failure modes.
Structured cabling, access control, cameras and the quiet infrastructure that everything else depends on.
The venue platform above, plus purpose-built applications and device integrations where off-the-shelf software does not fit the workflow.
What each discipline includes, and what a typical engagement looks like.
Services
Specification through to the dry run, with the drawings and commissioning notes handed over as part of the job.

Segmented so production traffic, back-of-house operations and public access never share a failure mode.

HVAC schedules, house and lobby lighting, and the building's own controls brought into the same design as the show systems and the bookings calendar.
Where projects fail
Between the show control and the hardware. Between the network and the system depending on it. Between the building controls and the show that needs them to behave. Between the vendor who installed it and the person who has to run it.
Working across all of it is the point. When the same shop specifies the network, patches the console, programs the controller and writes the integration, there is nobody to hand the problem to, so it gets solved.
How we work
No account layer between the people specifying the work and the people doing it. Scope conversations happen with whoever will be on site during commissioning.
Drawings, signal flow, network diagrams and commissioning notes are handed over as part of the job, not reconstructed later by whoever inherits the system.
Systems are specified so that a competent technician who has never met us can service them. That constraint shapes component choices, and it is deliberate.
AI-native practice
BIS works with frontier AI models as a matter of course. Drawings, calculations, documentation and code are produced with AI assistance and reviewed by the people who sign off and commission the system. It is why a small practice can hand over a complete as-built package on every job, and why the tooling below exists.
As-built documentation pipeline. Rack elevations, cable schedules, port maps and a bound as-built PDF, generated from live network data instead of retyped.
UniFi design to as-built bridge. PoE budgets checked, cable lengths corrected for height, and a priced bill of materials pulled straight from the design export.
Lighting paperwork from MagicQ and MVR files. Instrument schedules, channel hookups, and a readable diff between two versions of a plot.
Lobby screens that fill themselves from tonight's show data: cast, sponsors, house notices and box office status, with no per-screen subscription.
Forge tooling is built for BIS's own jobs first. It is not for sale yet; it shows up as better paperwork on yours.
Working on something?
All reasonable places to start a conversation. No obligation attaches to the first one.