ATIMS: Asset Tracking & Incursion Management System—What Deployment Looks Like
Updated: 1 day ago
A successful Asset Tracking & Incursion Management System (ATIMS) deployment starts with operational fit: configuring vehicles, alert zones, and interfaces around how the airport actually works.
One of the biggest misconceptions about airfield operational awareness systems is that deployment has to be disruptive or overly complex. In reality, successful deployments are built around operational fit.
Airport operations are already complex. Crews are managing changing priorities, active movement areas, winter deployments, maintenance coordination, low visibility, contractor activity, and runway timing pressure.
The goal of an operational awareness system is not to add complexity. The goal is to support visibility, coordination, alerting, and decision-making in a way that fits real airport workflows.
Planning an ATIMS deployment
A practical ATIMS deployment begins by understanding how the airport operates.
That includes:
vehicle types
movement area boundaries
runway safety areas
hotspots
common routes
winter operations workflows
temporary work zones
contractor activity
operational roles
reporting requirements
alerting needs
This matters because ATIMS is configurable. The system can support moving maps, in-vehicle alerts, geofenced zones, dashboards, reports, historical playback, and different vehicle configurations depending on the airport’s needs.
The strongest deployments are not built around a generic setup. They are built around how the airport actually works.
Geofences and alert zones are configured around the airfield
ATIMS uses GIS-based geofencing to support Runway Incursion Warning System (RIWS) capabilities and other operational alert zones. These zones can include:
runway safety areas
ILS critical areas
line markings
hotspots
one-way travel roads
temporary “no go” zones
construction areas
ponding or temporary hazards
other airport-defined areas
Alerts can be configured for approaching, entering, or leaving a zone. They can also be customized based on heading or speed.
This gives airports the ability to create practical warnings that match real operational risk, rather than relying on generic alerts that may not fit the airfield.
Vehicle setup matters
Each vehicle can be configured to support more accurate awareness and alerting.
ATIMS allows the airport to define vehicle size and the location of the GPS antenna. This matters because airfield vehicles vary in size, and accuracy is important when determining whether a vehicle has entered or fully exited a runway safety area.
This vehicle-specific setup helps improve confidence in the alerting logic and supports more precise operational awareness.
Not every vehicle needs the same configuration
A practical deployment does not require every vehicle to use the same setup.
Some vehicles may need a full moving-map display with audible and visual alerts. This can show the vehicle’s location on the airfield, nearby warning zones, and nearby vehicle position and heading.
Other vehicles may only need simplified audible and visual alerts. ATIMS LITE provides a sound/light panel option for operators who need immediate warnings near alert zones without the distraction of a map display.
This flexibility is useful for:
permanent airport operations vehicles
snow removal fleets
maintenance vehicles
contractors
temporary vehicles
visiting operators
phased deployments
The goal is to match the configuration to the role.
Edge computing supports continuity
Each vehicle can be equipped with an EagleLink edge computing device. This device provides GPS and cellular connectivity while also supporting the local map and RIWS logic.
In normal operation, the vehicle stays connected to the EagleView cloud platform. If connectivity is interrupted, key in-vehicle functionality continues. The vehicle’s position on the map and RIWS alerts continue to work, and data re-syncs when the connection is restored. That matters because airport operations do not stop when connectivity is imperfect.
Operator familiarization supports adoption
Operational awareness systems are human systems. Their value depends on whether crews understand and trust them during active operations.
That is why deployment should include practical operator familiarization around:
alert behavior
zone meanings
movement area awareness
in-vehicle interface use
ATIMS LITE alerts
operational expectations
what to do when alerts occur
how the system supports existing procedures
The most successful systems are the ones crews can use confidently under pressure.
Phased rollout can reduce disruption
ATIMS can support phased deployment across different vehicles, teams, and operational roles. A phased rollout may include:
initial operational review
zone configuration
pilot vehicles
moving-map deployment for selected vehicles
ATIMS LITE deployment for temporary or simplified use cases
operator familiarization
dashboard and reporting setup
expansion across additional vehicles or departments
This approach helps airports test, learn, and refine the system without forcing a disruptive all-at-once implementation.
In one sentence
A successful ATIMS deployment is phased, configurable, and built around real airport workflows so crews get the right level of awareness without unnecessary operational disruption.
