Strategy9 min read
AV resilience in oil & gas: from the rig floor to the boardroom
Remote sites, regional offices, and headquarters need an AV standard that accounts for bandwidth, environment, security, monitoring, and failure.
Read article →
AV Strategy
Most teams inherit rooms they did not specify, then take tickets on them for years.
Our A/Vision™ Strategy writes a standard, a lifecycle, a named owner, and a runbook that the helpdesk can close from.
Book a 20-min callThe work has four parts
Design, Build, Support, and AV-over-IT. Those are the four things that have to exist before the estate is actually owned, not just installed.
Design
One written standard for how a room gets built and supported. Capital, facilities, and the integrator work from the same page, so the room still meets it after the truck leaves.
Build
Network path, identity, and acceptance tests written before anyone cuts a PO. If the call cannot hold on that path, the room does not get ordered.
Support
A named owner per room type, including after 5. Helpdesk works first touch from a runbook instead of guessing which codec is in there.
AV-over-IT
The rooms run on the same network, identity, and monitoring as the rest of IT. AV staff, if you have them, work from that stack. Helpdesk can see the rooms. No second set of tools nobody else can log into.
The 3-phase process
Strategy, then a roadmap, then we stay on the work. We run the process. You own what it produces, including against the next capital project that never asked IT.
01
A high-level AV strategy
A written standard, a lifecycle, and a named owner. We sit with you and write them. Once they exist, your staff enforces them. We do not keep the keys.
02
An execution roadmap
The rooms you already have, in the order they page you, with a schedule and a budget your staff can run without us in the room.
03
Execution guidance
We stay on after the roadmap, on a monthly retainer, while you stand up the AV team that will run the standard. Your staff enforces it. We are not your AV department.
What you leave with, and what you own
Roughly in this order. The room list and the standard usually get written in parallel, because one without the other does not change the ticket queue.
A read on the room you do not want your name on again
It comes out of the 20-minute call. You keep it whether or not you hire us.
A written list of your rooms, sorted by how often they page you
We build it from your ticket history and a walk of the worst sites. The list is yours from the day it exists.
One standard for how a room gets built and supported
We run the process that writes it with you. Your staff owns it at purchase, including against capital projects that never asked you.
A runbook per room type, and a named escalation after 5
Your helpdesk takes first touch from the runbook. When it runs out, we run the escalation process. The standard stays yours.
A lifecycle date and a refresh order for every room
We keep it current against the standard. You decide what gets funded and in what year.
The same three rooms stop reopening
That is the finish line, and it shows up in your ticket queue rather than in a report from us.
What we need from you
None of this is a project kickoff. It is an afternoon of pulling things you already have: rooms, tickets, contracts, and who takes the 5pm call.
- A list of your sites and the rooms in them, however rough. A spreadsheet somebody keeps by hand is fine.
- Ninety days of helpdesk tickets tagged anything close to conference room, video, or audio.
- Read-only access to whatever watches the rooms today, if anything does.
- The integrator contract and the warranty dates you are still paying on.
- One name on your side who can approve a standard without convening a committee.
- Thirty minutes with whoever actually takes the 5pm call today.
That is the whole ask. If nobody can pull the ticket export, we start from the site walk instead and you lose nothing but a week of evidence.
Who owns the ticket after 5
We are not replacing your vendor and we are not making you hire AV. The split is who writes the standard, who installs to it, and who takes first touch after 5.
Us
During the day
We own the process that builds the standard, the lifecycle, and the plan. Once they exist, they are yours. We help you hold the integrator to them and we review what they quote.
After 5
When the runbook runs out, we run the escalation process. Your cell is not the number on the room.
Your integrator
During the day
They still install, still warranty the gear, still roll the truck. Nothing in their contract moves to us and we take no margin on what they sell you.
After 5
They stay on the response time you already pay for. What changes is that they are installing to a written standard, so there is less to call about.
Your helpdesk
During the day
First touch on every room ticket, worked from a runbook written for that room type. If you have AV staff, they take the cases the runbook cannot close. If you do not, helpdesk escalates into the process we run.
After 5
Same runbook. When it does not close the ticket they escalate into the process we run, not back to your cell.
The standards. We own the process.
The method has a name
A/Vision is what we call the four parts above. It is our consulting method for AV estates you have to run, not a product and not a program you enroll in.
If you want a longer read
Frequently asked questions
How do I justify this to my CFO?
Treat AV like the rest of IT: a standard, a lifecycle, and a named owner. A vendor refresh is a purchase. A standard is how you stop buying the same failure twice.
What does this cost?
The 20-minute call is free. A/Vision is three phases, each with its own price. Discovery is a high-level strategy pass, usually two to three weeks: a written standard, a lifecycle, and a named owner. Quoted for the work and the tools we use to do it. The roadmap is the large piece. The rooms you have, in the order they page you, with a schedule and a budget your staff can run. Similar in cost to one large Microsoft Teams Room. Sized to your room count, quoted before it starts, and not tied to hardware spend. Advising is a monthly retainer after the roadmap, usually six to twelve months, while you stand up the AV team that will run the standard.
Are you replacing our integrator?
No. Your integrator still installs and still holds the warranty. They build to your standard. We run the process that writes it and help you hold them to it.
Does this mean we have to hire an AV person?
No. The staff you already have should be able to close room tickets from a runbook. If that staff includes AV people, we write the process they run. If it does not, helpdesk takes first touch. Hiring a director is a headcount decision. It is not a gate for this work.
We already have AV staff. Is this still for us?
Yes. A small AV team with no written process is on the same treadmill, just closer to the room. We write the standard and the runbook with them. We do not manage your AV staff and we do not replace them.
Can you unify mismatched rooms across departments?
Yes. We start from the rooms you have and define one standard your staff can own, not a new brand of hardware.
Will this hold up across our global offices?
The work is a standard and a named owner, then rooms follow that standard site by site. We do not promise a single worldwide rollout date.
Why you instead of our current AV provider?
We do not sell or install hardware, so nothing we recommend earns us margin. Founded in Houston in 2018. Consulting is the engagement, and Vision for AV at itirium.ai is the same method as software if you want it later.
Bring us the room.
Give us 20 minutes. We'll tell you what to do first, what to keep, what to toss, and what to never do again.
Book a 20-min call