Airport wayfinding and visitor flow in museums, venues and terminals
Airport wayfinding, and wayfinding in any large public building, covers two problems that get sold as one: helping a visitor find the gate, the gallery or the exit, and knowing where visitors actually get stuck. They need different technologies, and they do not need to be solved at the same time. We help you work out which of the two is costing you more, then implement the answer. Sometimes the answer is not a system at all: in a lot of museums, better signage beats an app nobody downloads.
Not sure whether you need navigation, measurement or a signage review? That is exactly what the first call is for.
The problems behind a wayfinding or visitor flow project
Airports, museums, exhibition centers, stadiums and large venues share the same set of complaints, even though the buildings could not be more different.
Visitors who cannot find where they are going
A terminal with several piers, a museum with a non obvious route, a congress center with rooms numbered by a logic only the architect understood. People stop, look up, look at a printed map and then ask the nearest person in uniform.
Queues that are only noticed when they are already bad
Security, ticketing, bag drop, the cloakroom, the popular exhibit. By the time someone reports the queue, it has been forming for a while. Nobody has a record of how long it lasted or how often it repeats, so the staffing plan never changes.
Flows that nobody has ever measured
Which route do visitors actually take? Which rooms do they skip? How long do they stay in front of the piece the whole exhibition was built around? Curators, retail managers and commercial teams make decisions about layout, pricing and concessions without any of that.
Staff who spend their shift giving directions
Trained people, hired to help, welcome, secure or curate, answering the same directional questions all day. It is the most visible symptom of a wayfinding problem and the easiest to quantify: ask your floor staff to count the questions for a week.
Capacity and crowd safety at events
How many people are in that hall right now, and is that within the limit you declared? During an event, a number that arrives late is not useful. Fire and safety plans require a defensible answer rather than an estimate from the door count at the entrance.
Three questions to answer before you buy anything
Answer these before comparing products. The first one saves a significant number of wayfinding projects from being built at all.
Is this a navigation problem or a signage problem?
Be brutal about this. If visitors get lost at one junction and at one staircase, the fix is a sign, a color, a floor marking and a redesigned map, not an app with an indoor positioning back end. Digital navigation earns its place in genuinely complex buildings, in terminals where the destination changes per person, and in places where visitors already have a reason to open your app. A museum app that has to be downloaded at the entrance, on a crowded Saturday, will be used by a small minority of your visitors, and that is the real constraint.
Do you need to guide people, or to measure them?
Guiding is an app, a map, a positioning layer and content that has to be kept up to date. Measuring needs none of that: visitors carry nothing, install nothing and consent to nothing beyond the usual notice, because they are counted rather than identified. Measuring is cheaper, it starts producing value immediately, and it tells you where guidance is actually needed. A hypothetical example, not a client of ours: a museum where the queue builds at one ticket desk every Saturday morning while a second entrance stays empty. Nobody needs an app to fix that. They need to know how long the queue lasts and how often it repeats, which is a measurement job. Most buildings in this sector should start there.
Who will own the content after go live?
Indoor maps, points of interest, exhibition layouts, gate changes and temporary closures all change. An unmaintained navigation app is worse than no app, because it directs people confidently to a room that is closed. If nobody in the organization owns that work, the honest recommendation is not to start it.
The technologies, and what each one is good for
We are not tied to one technology. The Sentinel Video Tracker and the Bluetooth Beacon Tracker are products we build ourselves. RFID, UWB and Wi-Fi positioning we do not build, and we supply and integrate them all the same: we compare the options for your building, specify what fits, supply it and run the project. In this sector the right answer is usually a combination of a small digital component and a decision about the building itself. Several museums and an aquarium are among our clients.
Video analytics for counts, queues and flows
Our Sentinel video tracker runs on existing CCTV cameras and reaches 20 cm spatial precision. For visitor flow work it produces counts per zone, dwell time and movement patterns, aggregated and without identifying anyone. It is usually the fastest way to see where the congestion actually is, because in airports, museums and venues the cameras are already installed.
BLE for indoor positioning
Bluetooth low energy is the practical layer for position inside a building. Our Bluetooth Beacon Tracker locates tagged objects with fixed nodes: accuracy 1 to 3 meters in 90% of cases, beacons detected up to 30 meters, nodes mounted at the same height on ceilings up to 7 meters, positions updated in the order of seconds. In a venue that fits wheelchairs, audio guides, AV equipment, tour devices and staff radios. Turn by turn navigation on a visitor's own phone is a different build: beacons in the building, an app or an SDK, and an indoor map that somebody keeps current. We assess that build, specify it against the alternatives and manage the project end to end. Whether the app and map layer comes from us or from a specialist partner depends on the platform you want to sit on, and we settle it on the discovery call.
Signage, maps and layout
We will say it on the page and not only in the meeting: reviewing decision points, sight lines, naming and floor maps solves a large share of wayfinding complaints for a fraction of the cost of any system on this list. We are happy to be the supplier who recommends that first, then measures whether it worked.
The data, in your systems
Counts, zones and positions are available through a REST API, push callbacks for events such as a zone exceeding a threshold, and daily CSV files on request. That is what lets an operations team put a live occupancy figure on their own dashboard, next to ticketing and staffing. Cloud by default, on-premise supported.
What these systems will not solve
The most common disappointments in this sector, stated before you spend anything.
It will not make visitors download an app
This is the single biggest risk in indoor navigation projects for museums and venues, and it has nothing to do with the technology. If your visitors have no other reason to install your app, most of them will not install it to find a room. Airports are the exception, because many travelers already use an airline or airport app and the destination genuinely changes per person. Elsewhere, plan for the app being used by a minority, and make sure the signage works for everyone else.
It does not shorten a queue
Measuring a queue tells you when it forms, how long it lasts and how often it repeats. The queue gets shorter when you open another desk, move a checkpoint or change the arrival policy. The data makes those decisions defensible and lets you check whether they worked. It does not act on its own.
It is not a life safety system
Occupancy counts support capacity management and help an operations team see a hall filling up. They are not a certified evacuation, fire detection or crowd safety system, and they should never be the only thing a safety plan depends on. Your safety officer owns that plan. We provide a measurement input to it.
It does not identify your visitors
Counting and flow analysis are aggregated. The system is configured to count people and measure movement, not to recognize who they are, and facial recognition is not required for any of the uses on this page. If someone in the project asks for individual visitor identification, that is a different project with a different legal basis, and in the EU a considerably heavier one.
It does not cover the journey to your door
Getting from the parking lot, the station or the highway to the entrance is outdoor navigation, handled by the map app already on the visitor phone. Indoor systems start at the door. Making the transition between the two work is a content and signage task more than a technical one.
What it costs
We work with a USD 5,000 minimum commitment, which covers a project we can run properly, assessment and pilot included. Above that, the building decides the price, not a catalog.
What drives the cost
The area to cover and the number of zones. Whether usable CCTV already exists and whether the angles suit counting. Ceiling height and mounting constraints, which in terminals and historic buildings are often the hardest part. The number of floors and buildings. Whether you need navigation content, which adds design and maintenance work well beyond the hardware. Integration with ticketing, operations or your app.
What keeps it down
Starting with measurement on the zones where the complaints are, using cameras you already have. Fixing the signage first and measuring the effect. Postponing the navigation app until the flow data says where guidance is really needed. Running a pilot and pricing the rollout on what it showed.
Licensing
There are two models: a cloud subscription, hosted and updated by us, or a one-time license for an installation on-premise. In this sector the choice is frequently made by someone who is not in your team. The network often belongs to an airport authority, a concession operator or a municipality, and their policy decides whether visitor data can sit in a hosted tenancy at all. A listed or historic building adds a second constraint, because where a server can physically sit, and what may be installed around it, is limited by the conservation rules on the building. The floor does not move: a USD 5,000 minimum commitment, with the model chosen once the assessment has told us what the building and its IT owner allow.
How we work
Four steps. The first two are where most of the value is, and they are the cheapest.
1. Discovery call
30 minutes, free, with an engineer. Where do visitors get lost, what does your floor staff get asked, when do queues form, and what decision are you trying to make. If the conclusion is that you have a signage problem rather than a technology problem, we will say so on that call.
2. Site assessment
Scaled floor plans with the zones marked, the camera inventory with positions and angles, the mounting and power constraints, and the visitor routes as they exist today. In listed and historic buildings we also map what cannot be drilled, moved or made visible.
3. Pilot
One gallery, one hall, one pier, one entrance. For BLE the pilot uses at least 6 nodes covering roughly 300 square meters, with a scaled floor plan and a reference system. For video we start with the cameras that already look at the area in question. The pilot measures what your building actually delivers rather than what a datasheet claims.
4. Rollout and integration
Extend to the areas that the pilot proved worth covering, connect the data to your operations tools through the REST API, callbacks or daily CSV, and agree who reads the numbers and when. Reporting is only useful if a person owns the decision it feeds.
Frequently asked questions
Do our visitors need to install an app?
Not for measurement. Counting, queue detection and flow analysis work on cameras and sensors in the building, so visitors carry nothing and install nothing. An app is only needed for turn by turn navigation on a personal device. Before committing to that, look honestly at how many of your visitors already have your app or a reason to install it. In airports that share is often meaningful. In many museums it is small, and better signage plus a good printed map will help more people.
Can we use the CCTV cameras we already have?
Usually yes, and that is the main reason video is the cheapest starting point in this sector. What matters is coverage and angle: a camera installed for security may not see enough of a space to count reliably. During the site assessment we list which cameras are usable as they are, which need repositioning and which zones need an additional device.
Does the system identify individual visitors?
No. Counting and flow analysis are aggregated by zone and by time. The system is configured to measure movement, not to recognize people, and facial recognition is not required for any of the use cases on this page. You still need the usual signage and privacy notice for camera based analytics, and in the EU a data protection impact assessment is normally expected. We provide the technical description that goes into it.
Our building is listed and we cannot drill into the walls. Is that a problem?
It is a constraint, and it is one of the reasons we insist on a site assessment before quoting. Nodes need a mounting point and power, beacons are small battery devices that can often be fixed without permanent damage, and cameras that already exist need no new holes at all. In heritage buildings we usually end up with a design that follows existing infrastructure, existing cable routes and reversible fixings. Sometimes the constraint rules out a technology, and it is better to find that out during the assessment.
Our terminal has very high ceilings. Does BLE still work?
Nodes are mounted on the ceiling, all at the same height, on ceilings up to 7 meters. In a terminal or a large atrium that is often not possible, so we look at mounting on columns, walls, gantries or structures at a workable height, or at covering only the zones where position is genuinely needed. This is a good example of why the assessment comes before the proposal: the same product performs very differently in a gallery and under a terminal roof.
Can we get a live occupancy figure per hall during an event?
Yes, that is a standard use of zone counting, and it can be pushed to your dashboard through the API or a callback when a zone crosses a threshold. Two honest caveats: the figure needs the pilot to establish how reliably each zone counts, and it is an operational aid, not a certified safety system. Your capacity plan and your safety officer stay in charge of the decision to stop admissions.
Specifications
Video precision: 20 cm, on existing CCTV cameras
What video measures: Counts, queues, dwell time and flows per zone, aggregated
BLE accuracy: 1 to 3 meters in 90% of cases
Node range and mounting: Beacons detected up to 30 meters, ceilings up to 7 meters
Update rate: In the order of seconds
Pilot: At least 6 nodes, about 300 square meters
Integration: REST API, push callbacks, daily CSV
Deployment: Cloud by default, on-premise supported
Minimum commitment: USD 5,000
Tell us where your visitors get stuck
Bring a floor plan and the places where people stop and ask for directions. We will tell you what is worth measuring, what is worth building and what should be fixed with a sign instead. If a system is not the right answer for your building, that is a perfectly good outcome of the call.