Detect
Detects aircraft, equipment and movement within configured operational zones in compatible camera feeds.
Operating 24/7 at Dalaman Airport (DLM)
APRONEX · AI-POWERED APRON ANALYTICS
Turn apron video into operational events your airport systems can use
Apronex applies computer vision and aviation-specific event rules to compatible stand-camera feeds — automatically detecting, validating and timestamping supported aircraft, ground-service and safety events.
Operations teams see each monitored turnaround as it happens, while validated event data can be delivered to AODB, billing and planning systems.
From camera activity to operational data
Raw apron video is not usable operational data on its own. Apronex converts detected activity into structured events associated with the correct stand, flight and turnaround context.
Validate
Evaluates detections against stand layout, event sequence and flight context.
Deliver
Shows validated events on the live operations board and delivers them to the relevant airport systems.
Camera & flight contextCompatible stand-camera feeds · AODB flight context
Apronex event engineDetection · sequence and stand-rule validation
Operational outputsLive stand board · turnaround timeline · event feed · AODB integration
Beyond object detection: turnaround context
A camera model may detect an aircraft, a passenger boarding bridge or a GPU. Apronex evaluates those detections against stand layout, flight context, turnaround state and aviation-specific event sequences.
- A turnaround is associated with the correct flight and parking occurrence before events are attributed.
- Camera-detected on-block establishes the active stand-occupancy and turnaround window.
- Service events are evaluated inside the relevant turnaround context, not in isolation.
- Intermittent detections caused by temporary occlusions are evaluated within the connection–disconnection sequence and its timing to produce a consistent service record.
- Off-block is based on the aircraft's first confirmed movement away from the parking position — not tug connection.
EVENT SCOPE
Events in use at Dalaman Airport
- On-block
- Off-block
- PBB
- GPU
- PCA
- Potable-water service
The Apronex event scope is not limited to a fixed list. New events can be configured within the project scope, based on camera coverage, operational priorities and validation criteria.
Which apron events do you want to monitor?
Let's define the events that matter to your operation, and assess camera coverage and the validation approach together.
Discuss the event scopeStand and turnaround operations in one view
The Apronex operations board brings active turnarounds, detected events, service states and the chronological flow of events into one shared view.
- Flight and stand information
- AIBT, AOBT, on-block and off-block status
- Elapsed turnaround time
- Ground handling events
- Chronological event timeline
- Event source and validation status
Event sources on the timeline
- Camera-detected
- AODB
- Operator-verified
- Derived
The timeline shows the source and validation status of each event.
Built around real stand and turnaround rules
MARS stand configuration
Combined and split parking positions are modelled using parent and sub-stand relationships. A MARS position can operate as one wide-body stand or as two independently monitored narrow-body positions, according to the airport configuration.
Turnaround event sequencing
Camera-detected on-block establishes the active turnaround and stand-occupancy window. Service events are evaluated within that context, and off-block closes the parking occurrence.
Flight association
Camera and equipment events are associated with the correct flight, stand and parking record using AODB flight context and operational rules.
Works with your existing airport systems
Apronex operates as an analytics layer that complements the airport's existing operational systems. It does not require replacement of the AODB.
Interfaces
- IATA AIDX
- REST API
- JSON
- XML
- Webhooks
- Project-specific interfaces
Supported systems
- AODB
- OCC operational screens
- Billing systems
- Equipment-planning systems
- Staff-planning systems
Events are validated, mapped and published according to the airport's integration and data-governance rules.
Works with compatible apron cameras
Apronex can reuse compatible existing stand cameras where coverage and image quality are sufficient. Each target stand is assessed for camera angle, resolution, night performance and operational occlusion.
Where required, camera repositioning, additional coverage or edge-processing infrastructure may be included in the project design. No sensors or tracking devices are installed on aircraft or GSE.
What it contributes to the operation
Turnaround visibility
Follow turnaround events on monitored stands in real time.
More reliable event times
Reduce dependency on radio calls and manually entered event times.
Service usage records
Capture equipment and service start and end times for operational analysis and billing review.
Event sequence visibility
Follow the order in which configured events actually occur while the turnaround is still in progress.
Privacy and data governance
Apronex can process camera streams on local infrastructure and produce operational events without facial recognition or biometric identification. Image retention periods, event-linked records and access permissions are configured according to the airport's data-governance requirements.
KVKK and GDPR requirements are addressed within the project scope, according to the agreed processing and retention model.
Where enabled, event-linked visual records can support service verification, billing review and dispute resolution.
Live operations reference: Dalaman Airport
Apronex runs 24/7 at Dalaman Airport, automatically producing operational events from compatible stand-camera feeds.
Start with one stand. Evaluate Apronex in your own operation.
We assess camera coverage, configure the operational events that matter to your airport and validate Apronex under real turnaround conditions.
Pilot scope can include camera assessment, event selection, stand configuration, operational validation and integration review.