Airport positioning for people and assets
Indoor positioning and wayfinding guide passengers between gates and services, alongside asset tracking and field operations. Asset2Work connects maintenance and cleaning with work assignments, checklists and evidence of completion.
An airport is an operational city in motion
Terminals, aprons, systems, equipment, passengers and external crews share the same space, yet they often work through separate systems. A reliable spatial data foundation helps connect what happens to where it happens, supporting maintenance, operational response and service continuity.
GiPStech's Solutions page already frames Travel as the meeting point between orientation, operational management and services. This page brings that message into the airport context while keeping the location layer distinct from Asset2Work's operational layer.
Location becomes useful when it translates into guidance, findability and verifiable action.
One spatial context, three layers of value
Location can serve three different processes: guiding people to gates and services, making assets and equipment findable, and triggering and documenting field missions. Value emerges when these layers share maps and references without blurring purposes, responsibilities or data.
GiPStech's experience at Tokyo Narita Airport shows the relevance of indoor location to the passenger journey; Asset2Work extends the same spatial principle to operational activities, evidence and work governance.
Wayfinding that stays with the passenger
Airport orientation spans roadways, parking, curbside, terminals, checkpoints and gates. FAA guidance on airport wayfinding shows why the system must remain coherent across the whole journey; digital guidance can add contextual directions and accessible routes without replacing physical signage.
Experiments with integrated indoor location services in real terminals also indicate that position can be exposed to applications through interoperable architectures. Accuracy, latency, battery use and scalability still need to be verified for the specific airport.
From asset to mission: traceable maintenance
Effective maintenance starts with a reliable asset register and the ability to identify the asset where it is located. The ACRP guide to airport CMMS integration recommends a phased approach and the integration of maintenance data into performance decisions.
Asset2Work brings this principle to the field through unique identification, an offline-capable mobile app, reports, preventive and corrective missions, checklists, time tracking and georeferenced evidence. It can receive events from ERP, GIS, BMS or other data layers and turn them into traceable action, without positioning itself as the airport's all-purpose IoT data platform.
Identify
An asset register, serial number and tag make each item identifiable in the field.
Locate
Maps, georeferencing and tracking reduce uncertainty about where to act.
Act
Faults, priorities and preventive plans become missions assigned to operators.
Verify
Time records, checklists and photographs create an auditable operational history.
Cleaning guided by how spaces are actually used
Flight schedules, flows, occupancy and feedback can help reveal when and where cleaning demand changes. A University of Twente study on Schiphol restrooms shows the potential of passenger-flow forecasting for dynamic planning, while also highlighting limits in the dataset, proxies and generalisability.
Usage data does not replace service organisation. Asset2Work can turn a threshold, forecast or report into a mission, assign it to internal staff or profiled contractors, record presence, time and evidence of completion, and support SLA control. Operational rules, thresholds and the legal basis for data use must be defined for each airport.
From the map to the operational process
The journey starts with a measurable problem, not with technology: a wayfinding flow, a critical asset family or a cleaning service. The phased approach described in the ACRP guide helps set priorities, integrate systems progressively and connect data to decisions.
Maps, assets and processes then need shared identifiers, responsibilities and quality criteria. Research on airport spatial data maintenance highlights interoperability, governance and information continuity as operational conditions, not implementation details.
1. Define the use case
Set the objective, users, area, baseline and outcome indicator.
2. Prepare the context
Align maps, assets, zones, roles and required integrations.
3. Run a pilot
Test accuracy, usability, workflows and evidence quality in the field.
4. Scale with control
Expand by process and area while measuring adoption, SLAs and operational continuity.
Where can location create value in your airport?
Start with one flow, asset family or operational service, then define the data, technologies, integrations and success criteria together.
