Campus navigation gets a person to a specific room across a multi-building site: a searchable map of rooms, offices, facilities and services, routes that account for floors, lifts and step-free access, and directions delivered on a phone, a kiosk or a link. Live position tracking — the moving blue dot — is one possible component and frequently the least necessary one.

Most people do not need to watch themselves move on a map. They need to know which building, which floor, and which door.

  • Search by room, person, service or course, not just building
  • Step-free and accessible routing as a first-class path
  • Routes generated from the timetable, not typed by the student
  • Positioning specified only where it earns its cost
Digital map displayed on a mobile phone
A route to a named room answers the real question. Watching a dot move across a floor plan is a different and much more expensive product.

Nobody is lost on the campus. They are lost in the building

Campus navigation problems are concentrated in a few predictable moments: the first two weeks of an academic year, examination days, open days and conferences, and every visitor's first meeting. Outside those, the population knows where it is going. This matters because it defines what a system has to be good at — high-volume, unfamiliar, one-off journeys — and what it does not need to be good at, which is guiding people who already know the way.

The second observation is where people actually get lost. Reaching the right building is usually straightforward with signage and an outdoor map. The failure happens inside: the wrong floor, the wing that does not connect on level two, the room numbering scheme that restarts after a refurbishment, the lecture theatre with an entrance on a different level from its number. And the person most affected by all of it is the one who cannot use stairs and for whom a wrong turn is not a minor inconvenience.

  • Navigation demand is concentrated in a few weeks and a few event days each year.
  • The failure is inside buildings — wrong floor, wrong wing, inherited room numbering.
  • Accessible routes are usually undocumented, so step-free journeys are guesswork.
  • Reception and departmental staff absorb the cost as constant verbal directions.
  • Static signage is expensive to change and is therefore rarely changed after a refit.

Solution overview

Swedish Technology starts with the route engine and the data behind it, because that is what answers the question. A structured model of the campus — buildings, floors, rooms, entrances, lifts, stairs, accessible paths and the connections between them — supports search by room number, department, service, person or timetabled class, and produces directions that are correct about floors and entrances. Delivered on a phone, at a kiosk, or as a link in a meeting invitation or admission letter.

Live positioning is then specified only where it pays for itself. In an atrium-heavy modern building with clear sightlines, a step-by-step route and good signage outperform a drifting blue dot. In a dense multi-wing complex where visitors arrive daily and disorientation is chronic, positioning is worth its cost — and we say which technology, at what accuracy, with what maintenance burden. A campus is more often badly modelled than badly positioned, and fixing the model is the cheaper half of the problem.

How the solution works

  1. 1
    Model the campus properly Buildings, floors, rooms, entrances, vertical connections and paths captured as structured data from drawings and survey. This is the majority of the work and the part that determines whether anything else is any good.
  2. 2
    Record the accessible network separately Step-free routes, lift capacities, door widths and ramp locations captured as their own path network, because an accessible route is not the ordinary route with stairs removed.
  3. 3
    Connect the searchable things Room numbers, department names, staff offices, services and timetabled classes, so a student searches for their lecture and not for a room code they do not know.
  4. 4
    Decide the positioning question honestly Survey the buildings and determine where live positioning is justified, which technology suits each space, and where good routing plus signage is the better answer. This is a recommendation with numbers, not a default yes.
  5. 5
    Deliver at every touchpoint Phone browser, native app where one exists, lobby kiosks, printed QR anchors at decision points, and deep links inside invitations and admission letters.
  6. 6
    Keep it current Room changes, closures and refurbishments updated by estates through a simple editor. An out-of-date map is worse than a printed one, because people trust it.
Modern building corridor with directional signage
People get lost inside buildings, not between them — which is where the modelling effort belongs.

Key capabilities

Structured campus model

Buildings, floors, rooms and connections as data rather than as images, which is what allows routing, search and integration to work at all.

available

Accessible route network

Step-free paths modelled independently, so a wheelchair user gets a route that is genuinely usable rather than one with the stairs edited out.

available

Search that matches intent

Find a class, a service, a department or a person — not only a room code the person does not have.

available

Multi-channel delivery

Phone, kiosk, QR anchor and deep link from a calendar invitation or letter, so no app install is required to get a route.

available

Positioning where justified

BLE, Wi-Fi, UWB or visual positioning specified per space with its real accuracy and maintenance cost stated, and omitted where it is not worth it.

available

Estates-maintained content

Room changes and closures updated by the estates team directly, because a map that requires a vendor ticket becomes stale within a term.

available

Reference architecture

The map data is the asset and the route engine is the product. Positioning, where used, is a layer on top — not the foundation.

Deployment options: Cloud or on-premise. Map and route data can be cached on the device so a route continues to work in a basement or a lecture theatre with no signal — which is exactly where people need it.

Hardware options

The honest section. Hardware here is optional, and a proposal that opens with a beacon count has usually skipped the question of whether beacons are needed.

DeviceWhere it is usedSelection notes
None (routing only)Most campuses, most buildingsA correct model and a good route engine need no hardware at all. This is a legitimate answer and often the right one, particularly in buildings with clear sightlines.
BLE beaconsDense, disorienting interiorsTypical accuracy of a few metres — enough to know the floor and corridor, not the exact door. Battery replacement across hundreds of units is the recurring cost people underestimate.
Wi-Fi based positioningBuildings with dense, well-mapped Wi-FiUses infrastructure that already exists, at coarser accuracy. Quality depends entirely on access point density and how well the site was surveyed.
UWB anchorsSmall high-value zones onlySub-metre accuracy at a cost that rules out campus-wide deployment. Justified for specific rooms or asset tracking, not for general wayfinding.
Wayfinding kiosksLobbies, main entrances, faculty receptionsThe highest-value hardware in most deployments: serves visitors with no app, no phone battery and no patience, and doubles as campus signage.
QR anchorsDecision points, lift lobbies, corridor junctionsPrinted, nearly free, and surprisingly effective. A scan establishes exact position with no infrastructure and no batteries.

Swedish Technology supplies and integrates positioning hardware from established manufacturers where a survey shows it is warranted.

AI capabilities

Applied to keeping the model correct and understanding how the campus is really used.

  • Drawing extraction — Reads CAD and PDF floor plans to extract rooms, doors and corridors into the campus model, which turns a multi-month manual digitisation task into a reviewed one.
  • Route quality learning — Identifies routes people abandon or deviate from, which is how modelling errors — a locked connecting door, a lift that does not serve a floor — are found without a survey.
  • Search intent matching — Maps what people actually type — a lecturer's name, a course code, 'prayer room', a misspelt building — to the right destination, in both English and Arabic.
  • Demand analytics — Shows which destinations, buildings and times generate navigation demand, which tells estates where signage and kiosks are genuinely needed.

Integrations

These can be designed within project scope.

SystemIntegration point & data exchangedDirection
Esri ArcGIS and ArcGIS Indoors Campus GIS as the authoritative spatial source where the institution already runs Esri, with indoor floor plans maintained alongside outdoor campus data. bi-directional
Timetabling and room booking Class and meeting locations so a route is generated from the timetable, and a room change reroutes the student rather than stranding them. inbound
Student information systems Programme and enrolment data so a student's own schedule drives their map. inbound
Campus visitor management A visit destination becomes a route delivered with the invitation, so a visitor arrives at the right building without asking. → University Campus Visitor Management bi-directional
CAFM and estates systems Room changes, closures and works updated from the estates system so the map reflects the building rather than the drawing. → Facility Management bi-directional
Digital signage Wayfinding content pushed to existing screens rather than deployed as a separate estate of displays. outbound

The integrations above are designed and implemented within project scope using vendor APIs, webhooks or standard connectors. They do not imply partnership, certification or endorsement by the system owner unless stated on that vendor's official pages.

Dashboards & analytics

  • Navigation demand — Most-searched destinations by day and hour, which identifies where signage or a kiosk would remove the demand entirely.
  • Failed searches — What people looked for and did not find — usually the fastest route to a better campus model.
  • Accessible route usage — Step-free route requests and where they fail, which gives estates an evidence-based accessibility improvement list.
  • Content freshness — Rooms and paths not reviewed since a change, so the map is maintained deliberately rather than allowed to decay.

Security & deployment

Wayfinding is one of the few systems here that can be largely anonymous, and it should be. Routing works without an account: a person searches, gets directions and leaves no personal record. Sign-in is needed only for timetable-linked routing, and that uses the institution's existing identity provider rather than a separate account. Map data is cached on the device so routes survive a signal loss in a basement or a lecture theatre, and kiosks fall back to a static campus map rather than an error screen.

Data privacy

Indoor positioning is the point at which a navigation product becomes a tracking product, and the distinction is entirely in the design. Position should be computed on the device and used to draw a route on that device. It should not be sent to a server as a continuous trail, and if a system does send it, the institution has acquired a movement-tracking database it did not ask for and cannot easily justify.

We design for on-device positioning, aggregate rather than individual analytics, and no identified location history by default. Under UAE Federal Decree-Law No. 45 of 2021, location data linked to a student or staff member is personal data with a high sensitivity, and the fact that a campus can technically retain it is not a reason to. Where an institution has a specific and defensible need — an emergency mustering case, for example — that is a separate decision made explicitly, with its own retention rule, rather than an unnoticed consequence of installing wayfinding.

Industry use cases

Large multi-building university

Orientation week handled by timetable-linked routes on students' own phones instead of by volunteers pointing at buildings.

Campus with significant accessibility commitments

A properly modelled step-free network, with failed accessible routes reported to estates as an improvement list.

Institution hosting frequent conferences

Delegate routes delivered by link with the joining instructions, and lobby kiosks carrying the load for those who arrive without them.

Medical or research faculty

Dense multi-wing buildings where positioning is genuinely justified, deployed in those buildings only rather than campus-wide.

Campus after a major refurbishment

Room renumbering and changed connections reflected immediately, where replacing static signage would take months and a budget cycle.

Mixed-use campus with public facilities

Public visitors routed to the library, clinic or auditorium without entering academic areas, which is a wayfinding contribution to the access model.

UAE & GCC considerations

UAE campuses are frequently large, recently built and still expanding, which produces the specific condition this system addresses: drawings that no longer match the building, room numbering that has been revised, and connections that exist on a plan but are locked in practice. Modelling the campus as it actually is, rather than as designed, is the unglamorous half of the project and the half that determines the outcome.

Bilingual delivery is not optional here. Search has to work in both English and Arabic, including Arabic building and faculty names that people type in several transliterations, and the map interface has to render correctly in RTL rather than mirroring the map itself. Climate shapes routing too: on many campuses the shaded or air-conditioned connection is the route people actually want between June and September, which means covered walkways deserve to be modelled as a routing preference rather than treated as an equivalent path.

Implementation approach

  1. 1
    Survey and scope Walk the buildings, compare them with the drawings, and identify where navigation demand is concentrated. The recommendation on positioning comes out of this, with reasons.
  2. 2
    Campus modelling Floor plans converted to a structured model with rooms, connections and the accessible network. The largest task, and the one worth resourcing properly.
  3. 3
    Content and search Room registers, departments, services and their real-world names — including what people call them rather than what they are called officially.
  4. 4
    Pilot in one building The building with the worst reputation for getting lost. If wayfinding works there it will work elsewhere, and if it does not the model is wrong.
  5. 5
    Delivery rollout Web and kiosks first, deep links into invitations and letters, positioning only in the buildings where the survey justified it.
  6. 6
    Handover to estates The editor, the update process and the freshness dashboard given to the team that owns the buildings, because that is the only sustainable arrangement.

Why Swedish Technology

  • We tell you where positioning is not needed, which is most places, and we show the survey that says so.
  • The accessible route network is modelled separately rather than derived by removing stairs.
  • QR anchors and kiosks are treated as serious tools, not as fallbacks — they serve the people who have no app and no patience.
  • Estates can update the map without raising a vendor ticket, which is the difference between a live map and a stale one.
  • Positioning is designed on-device by default, so wayfinding does not quietly become movement tracking.

Limitations & prerequisites

  • Indoor positioning accuracy is a few metres at best with BLE or Wi-Fi. It identifies a floor and a corridor reliably and a specific doorway unreliably, and any claim otherwise at campus scale should be treated sceptically.
  • Beacon deployments carry an ongoing battery and maintenance obligation across hundreds of units; an unmaintained beacon estate degrades into an unreliable one within a couple of years.
  • The campus model is only as good as the drawings and the survey. Buildings that differ from their documentation require physical verification, which takes time.
  • Routing cannot resolve genuinely ambiguous physical signage; a system may need to be accompanied by signage changes to be effective.
  • Timetable-linked routing depends on the timetabling system exposing room data reliably and promptly, which is not universal.
  • GPS is unreliable indoors and near large structures, so outdoor-to-indoor transitions need an anchor point rather than a seamless handover.

FAQ

Usually not. A correct campus model with a good route engine, clear signage and QR anchors at decision points answers most navigation needs with no hardware at all. Beacons are justified in dense, disorienting interiors with sustained visitor volume — and they bring an ongoing battery-replacement obligation across hundreds of units.

With BLE or Wi-Fi, a few metres in good conditions — enough to establish the floor and corridor, not the specific doorway. UWB achieves sub-metre accuracy at a cost that rules out campus-wide use. Claims of consistent doorway-level accuracy across a whole campus should be examined carefully.

Modelling the campus as it actually is. Drawings are out of date, room numbering has been revised, and connections shown on plans are locked in practice. This is the majority of the effort and the part that determines whether the system works.

As a separate path network with its own data — lifts, ramps, door widths, step-free connections — rather than as the ordinary route with stairs removed. The two are not the same graph, and treating them as one produces routes that fail at the first step.

No. Routing works in a phone browser, at a kiosk and from a QR anchor. An app is worth building only where the institution already has one students use, in which case wayfinding belongs inside it rather than beside it.

Yes, where the timetabling system exposes room data. A student then searches for their class rather than a room code, and a room change reroutes them instead of stranding them outside a locked door.

Not by design. Position is computed on the device and used to draw a route there; it is not sent to a server as a continuous trail. Analytics are aggregate. Individual location history is a separate decision an institution should make deliberately, if at all.

Estates updates the model directly through the editor, and the change is live immediately. This is the main advantage over static signage, which typically waits for a budget cycle.

Discuss your site with an engineer

Tell us the venue, the expected visitor volume and the systems you already run. We reply with a technical view, a realistic scope and the next sensible step — a site survey, a working demonstration, or a full technical and commercial proposal.

+971 56 404 6555 · info@swedishtechnology.com

Sources & evidence

  1. UAE Federal Decree-Law No. 45 of 2021 — Personal Data Protection Law — Governs collection, retention and cross-border transfer of visitor personal data in the UAE.
  2. Esri — ArcGIS Indoors — Indoor GIS platform commonly used for campus indoor mapping and wayfinding data.
  3. W3C Web Content Accessibility Guidelines (WCAG) 2.2 — Accessibility standard applied to wayfinding interfaces and kiosk software.

Vendor and product names are trademarks of their respective owners; references are for technical context and do not imply partnership, certification or endorsement.