TECHNOLOGY FOR AIRPORTS
From passenger to apron. Every moment connected.
Passenger communication, apron intelligence and digital service records. Connected to the systems you already run.
Airports running our products
DLMPassenger Engagement · Apronex
SAWPassenger Engagement
COVPassenger EngagementOUR PRODUCTS
01 / PASSENGER COMMUNICATION
The flight changes. Your passenger knows.
Flight updates, a multilingual assistant and live support. In the messaging channels passengers already use, with no new app to install.
WhatsApp · Telegram
Explore Passenger Engagement
02 / APRON ANALYTICS
Apron activity becomes operational intelligence.
Detect aircraft and ground-service events from camera feeds. Follow contact and remote stand operations through timestamped records.
Explore ApronexThe aircraft comes to a complete stop at its parking position.
The aircraft first moves from its parking position.
Services can overlap. Each row shows its own event relationships; there is no mandatory sequence between rows.
Chock placement is recorded separately from AIBT. Chock removal is not AOBT either; AOBT is the aircraft’s first movement from its parking position.
Bridge connection and disconnection are tracked separately. Bridge connection alone does not establish the start of boarding or deboarding.
Positioning at the aircraft door and removal are distinct events. Access equipment is selected according to the stand and aircraft operation.
GPU cable connection and disconnection are tracked. A GPU seen on stand does not by itself establish that power is being supplied to the aircraft.
PCA hose connection and disconnection are recorded separately, rather than combined with GPU service.
Fuel vehicle or dispenser presence is separate from connection. A visually observed connection interval does not measure fuel flow or delivered volume.
The catering vehicle at the forward service door has separate arrival, docking, undocking and stand-exit events. Forward and aft records are independent; monitored doors are configured for aircraft type, service plan and camera coverage.
The catering vehicle at the aft service door has separate arrival, docking, undocking and stand-exit events. Forward and aft records are independent; monitored doors are configured for aircraft type, service plan and camera coverage.
The belt loader or high-loader serving the forward hold has separate first-seen, positioning, withdrawal and stand-exit events. Forward and aft hold records are independent. Equipment depends on the aircraft and loading configuration; positioning alone does not establish first bag off or last bag loaded.
The belt loader or high-loader serving the aft hold has separate first-seen, positioning, withdrawal and stand-exit events. Forward and aft hold records are independent. Equipment depends on the aircraft and loading configuration; positioning alone does not establish first bag off or last bag loaded.
Vehicle presence and water-service connection are separate records. Connection duration is not interpreted as delivered water volume.
This view is not a flight record or a duration plan. Active doors, holds and equipment vary with aircraft type and service plan. Event scope is configured for the stand, camera coverage and local procedures. Expand a service for details.
03 / DIGITAL SERVICE FORMS
Service complete. Record ready.
Link the service to the flight, record the times and collect sign-off. One digital record from the apron team to billing.
Explore Apronex Tablet
Bring in flight data, share operational events and pass service records to billing. Connect AODB, OCC and passenger communication in one information flow.
Contact us to learn more about passenger communication, apron analytics and digital service forms.