01
AV systems integration
Audio, lighting, video and the infrastructure that carries them, designed to be operated by the people who work in the room.
Systems integration · Hamilton, Ontario
Systems that have to work when someone is watching.
Ticketing, event management and venue operations software, plus the AV, show control and networks underneath it. Designed, built and commissioned by the same engineer, for venues across southern Ontario.
$ bis commission main-stage --dry-run
▸ network vlan 30 production ............ ok 1.8 ms
▸ show ctrl osc /cue/12/go → qlab ......... ok
▸ lighting sACN u1-u4 @ 40 fps ........... ok
▸ audio dante clock locked ............ ok
▸ video ndi lobby-01 lobby-02 ......... ok
▸ docs as-built package .............. generated
✓ 6/6 subsystems ready · handover 09:42
05disciplines under one roof
01engineer from scope to commissioning
00account managers between you and the work
AInative practice: documentation, drawings and code produced with frontier models, reviewed by the engineer
The platform
Sell the seat. Run the season. Close the books.
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.
Ticketing
Box office and ticketing
Seat maps, timed holds, subscriptions, comps, exchanges and QR check-in at the door. No commission skimmed off every ticket.
Event management
Productions, bookings and volunteers
Rehearsals, performances, outside rentals and volunteer rotas against the same rooms and the same calendar.
Venue ERP
Memberships, donations, finance
Patron records, renewals, fundraising and grants, concessions, reconciliation and the reports a board actually asks for.
Software and building, one shop
The screens, the scanners and the network are ours too.
Most software vendors hand you an integration guide and wish you luck. Because the same shop specifies the network, hangs the lobby displays and wires the door scanners, the platform reaches the actual building instead of stopping at the browser.
Disciplines
One shop for the room, the network and the show.
Real installations do not respect the boundaries between trades. A lighting system depends on a network, a box office depends on data getting somewhere useful, and both depend on someone having written down how it works.
02
Show control & venue automation
Cue automation, playback workflows and motorised stage systems tied together so one trigger does what it should, every night.
03
Networking & infrastructure
Networks for buildings where production traffic, operations and public access have to coexist without sharing failure modes.
04
Low-voltage systems
Structured cabling, access control, cameras and the quiet infrastructure that everything else depends on.
05
Ticketing & operations software
The venue platform above, plus purpose-built applications and device integrations where off-the-shelf software does not fit the workflow.
Every service, point by point
What each discipline includes, and what a typical engagement looks like.
Services
Where projects fail
Most integration problems live in the seams.
Between the show control and the hardware. Between the network and the system depending on it. 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 person specifies the network, patches the console and writes the integration, there is nobody to hand the problem to, so it gets solved.
How we work
Small shop, direct line.
01
You talk to the engineer
No account layer between the person specifying the work and the person doing it. Scope conversations happen with someone who will be on site during commissioning.
02
Documentation is a deliverable
Drawings, signal flow, network diagrams and commissioning notes are handed over as part of the job, not reconstructed later by whoever inherits the system.
03
Built to be maintained
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
A small shop with the output of a larger one.
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 engineer who signs off and commissions the system. It is why a one-person practice can hand over a complete as-built package on every job, and why the tooling below exists.
It knows this site, nothing more, and it will not quote.
In development
Forge Docs
As-built documentation pipeline. Rack elevations, cable schedules, port maps and a bound as-built PDF, generated from live network data instead of retyped.
In development
Forge Link
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.
In development
Forge Plot
Lighting paperwork from MagicQ and MVR files. Instrument schedules, channel hookups, and a readable diff between two versions of a plot.
In development
Callboard Signage
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?
Retrofits, new builds, a system someone else left half finished.
All reasonable places to start a conversation. No obligation attaches to the first one.