Performance Statistics

From WikiLink
Jump to: navigation, search

The DPMF provides a facility to allow certain stakeholders to create statistics for their own domain filtered in various ways, for example between user specified dates. This facility is accessed via the stakeholder portals on the EUROCONTROL web site. ANSPs can use the facility to create a set of reports about all flights under their control, Aircraft operators can use the facility to create reports about their own flights, and aircraft manufacturers to use the facility to create reports about their own aircraft types. A series of videos is available to demonstrate how to use these portals. The data available in the tool is provided by the recordings of the ANSP systems. Currently only Maastricht UAC, Skyguide, DFS and NATS are providing their recordings, so that is the scope of the data available. Access to the facility is controlled; if you would like access please contact us.


The performance metrics are presented in the groups shown in the table below and are explained in more detail underneath:

General Performance Measures

The General Performance Measures as the name implies give some general measures of overall system performance. It covers the following metrics:

  • Technical Round Trip Delay. The distribution of the delay between when a uplink CPDLC message is sent and the corresponding LACK message is received. This gives a good indication of the overall performance of the technical system (i.e. the ACSP, avionics and the ground end-system).
  • Provider Aborts Count. This counts the number of provider aborts as a percentage of the number of CPLDC sessions and shows the trend over the preceding 12 months. It also provides the PAs counts per aircraft.
  • User Abort Count. This counts the number of user aborts as a percentage of the number of CPLDC sessions and shows the trend over the preceding 12 months.
  • CPDLC Technical Error Counts. This provides a count of the different technical errors encountered.


Context Management

The context management measures provide statistics about the usage of the context management application. It covers the following metrics:

  • DLIC Initiation Logon Counts. The number of unsuccessful logon attempts, the number of successful logon attempts followed by the establishment of a CPDLC connection, and the number of successful logon attempts that are not followed by the establishment of a CPDLC connection.
  • DLIC Contact Transaction Delay. The distribution of the delay between the ground system issuing a contact request and it receiving a contact response and the trend over the previous 12 months.
  • DLIC Contact Continuity. The probability that a contact request results in the reception of a contact response before the expiration timer expires. This metric is still under validation so is not yet available.

CPDLC Ground Initiated Transactions

This presents statistics relating to CPDLC transactions that are initiated by the controller. Air initiated transactions and ground initiated transactions are analysed separately since they have different performance requirements. It covers the following metrics:

  • CPDLC Ground Initiated Transaction Delay. The delay between when the controller initiates the transaction to when the operational response is received.
  • CPDLC Ground Initiated Continuity. The probability that the CPDLC transaction completes before the expiration timer expires (120 seconds). This metric is still under validation so is not yet available.
  • Uplink Message Usage. This presents counts of different groups of uplink messages; instructions, transfer of communications, level changes, speed changes, route changes and 'check stuck microphone' requests.
  • Uplink Error Counts. This presents a count of the different types of operational errors encountered.

CPDLC Air Initiated Transactions

This presents statistics relating to CPDLC transactions that are initiated by the flight crew. It covers the following metrics:

  • CPDLC Air Initiated Transaction Delay. The delay between when the flight crew initiates the transaction to when the operational response is received.
  • CPDLC Air Initiated Continuity. The probability that the CPDLC transaction completes before the expiration timer expires (270 seconds). This metric is still under validation so is not yet available.
  • Downlink Message Usage. This presents counts of different groups of uplink messages; request for level change and request for route changess.
  • Downlink Error Counts. This presents a count of the different types of operational errors encountered.