Three questions, under a minute each for the next event or show you walk.
The word on every sign
Walk any security show floor and count the signs that say AI. You’ll lose count before your first coffee.
The trouble isn’t that the word is everywhere. It’s that the same two letters are doing three different jobs. At one booth AI is a feature: search that’s faster than it used to be or an alert that’s a little smarter. At the next it’s a separate product: an appliance or a plug-in that talks to the system you already run. At a third it’s the whole design: a platform where intelligence was the reason the thing was built.
From the aisle all three look the same. Same two letters. Same big screen. Same friendly person in a lanyard explaining it well. That’s the problem the sign can’t solve for you.
Why the demo won’t settle it
A demo is the one place every system works. That isn’t a knock on anyone. A booth is built to show a product at its best and it should. The moment that matters comes later, in the year after the install, when your building has to run on whatever you bought. The demo can’t show you that year. A few good questions can get you close.
So here’s a small card to bring with you. Three questions that turn a booth visit into three things you write down and carry to the next aisle. None of them needs the demo running to answer.
Building owners and operators. Security directors. The integrators and consultants who’ll be asked to spec whatever gets picked. If you’re going to live with the answer for the next ten years, the three questions are for you.
Question 1: What year did AI become part of the design?
Why ask: Every company can answer this one because it’s their own history. The year tells you whether intelligence was in the plan from the start or added later to meet the moment. Neither answer is wrong. They’re different architectures and they tend to age differently.
What to listen for: A specific year is a good sign whatever the year is. A recent year can be a perfectly honest answer about a new product. “We’ve always had AI” deserves one more question.
The follow-up: “What changed in the hardware or the platform when it arrived?” If nothing changed underneath, you’ve learned something about where it lives.
Write down: the year.
Why ask: AI can only see what the architecture lets it see. If the intelligence lives in a separate product, it sees that product’s slice of the building. If it lives in the same system as the doors, the cameras and the people moving through them, what one of them sees can mean something to the others.
What to listen for: “Integrated” is a good word that can mean two things. Sometimes it means one system. Sometimes it means two products talking over a connection. Both can work. They aren’t the same thing and it’s fair to ask which one you’re looking at.
The follow-up: When the demo shows an alert or a summary, ask “Where did that answer come from?” Count the systems in the reply.
Write down: one or several.
Why ask: This is the question your security leadership will ask anyway, so ask it first. Software that can act on a building is only useful if you know where the person sits in the loop. The loop usually runs in five steps: it sees, it suggests, a person approves, it acts, it logs. Find out which of those steps need a human.
Autonomy without governance is a liability. — Patrick Barry, CEO, BluBØX
What to listen for: “It recommends and a person approves” is an honest answer and a good one. So is “nothing yet.” Ask a little more about any answer that skips the approval step without telling you what governs it instead.
The follow-up: “Can you show me the record of what it did and why?”
Write down: person or software.
Look at where the years cluster. Count how many said one system and how many said several. Note who could show you the record of what the software did. Then go back to the problem you picked before you walked in and ask which of those answers would still be solving it five years from now.
The answers you got in writing with a year attached are the ones worth keeping.
The three questions work just as well on a vendor call, at the end of a demo or as three lines in an RFP. The show floor is simply where you’ll hear the most answers in the shortest time. Keep the card. You’ll use it again.
It’d be a strange thing to hand you three questions and skip ourselves. So here’s our card, filled in.
The year: 2018. That’s when we standardized our hardware platform on NVIDIA Jetson because we believed AI belonged at the edge. The AI on an ARC board sits next to the door it serves.
The systems: one. One platform that reasons across people, spaces, devices, elevators, cameras and sensors.
The approval: you. BluBØX Oracle acts only within the permissions you already have and every action is logged. It acts when you ask it to. Acting on what it sees is the roadmap, not the pitch.
What should I ask AI security vendors at a trade show?
Three questions cover most of it. What year did AI become part of the design? Is the AI in the same system as the doors and cameras? What can it do without a person approving it? Each one takes under a minute and gives you something you can write down and compare.
What’s the difference between built-in and bolted-on AI?
Built-in AI was part of the design from the start and lives in the same system as the doors, cameras and people it reasons about. Bolted-on AI was added later as a feature or a separate product that talks to the rest of the system. Both can work. They tend to age differently, which is why the year and the system count are worth asking about.
What does “integrated” mean when a vendor says it about AI?
It can mean one system. It can also mean two products connected to each other. Neither is wrong, but they aren’t the same thing. Ask where an answer on the screen came from and count the systems in the reply.
Should AI in a security system act without a person approving it?
That depends on the action and on your policies. What matters is knowing which steps need a person, what governs the steps that don’t and whether every action leaves a record you can review.
Do these questions only work at trade shows?
No. They work just as well on a vendor call, in a demo or in an RFP. The show floor is simply where you’ll hear the most answers in the shortest time.
Every building is getting smarter or getting older. Same goes for everything on the show floor. Take the three questions to every booth you visit. Then ask us the same three.
Print it or screenshot it. One row per booth.
| Booth | Year | Systems (one or several) | Who approves (person or software) | Showed the record? (yes or no) |
