Difference between revisions of "CPDLC Ground Initiated Transaction Delay for ATN"

From WikiLink
Jump to: navigation, search
 
Line 1: Line 1:
The CPDLC Ground Initiated Transaction Delay is available from the DPMF [[Dashboards]] and is the time taken between the message that initiates a transaction being sent and the corresponding message that closes the transaction being received.  
+
The CPDLC Ground Initiated Transaction Delay for ATN is available from the DPMF [[Dashboards]] and is the time taken between the message that initiates a transaction being sent and the corresponding message that closes the transaction being received.  
  
 
Only transactions that are responded to by the flight crew are considered. Transactions that are triggered automatically by the ground system and automatically responded by the aircraft (for example UM160 Next Data Authority) are not considered as a part of this metric.
 
Only transactions that are responded to by the flight crew are considered. Transactions that are triggered automatically by the ground system and automatically responded by the aircraft (for example UM160 Next Data Authority) are not considered as a part of this metric.

Latest revision as of 09:59, 1 July 2021

The CPDLC Ground Initiated Transaction Delay for ATN is available from the DPMF Dashboards and is the time taken between the message that initiates a transaction being sent and the corresponding message that closes the transaction being received.

Only transactions that are responded to by the flight crew are considered. Transactions that are triggered automatically by the ground system and automatically responded by the aircraft (for example UM160 Next Data Authority) are not considered as a part of this metric.

CPDLC GROUND INITIATED TRANSACTION DELAY

Each different type of transaction is considered separately to determine which message initiates the transaction and which closes it. If the initial response is an ERROR message then the transaction is not included in the statistic (since the transaction will not be closed) but the error is counted. Also if the initial response is a LACK but an ERROR message is received subsequently for this transaction (because the pilot or the controller did not respond before the timer expired) then the transaction is also not included in the statistic but again the error is counted.

If a STANDBY response is sent then the two elements of the transaction are measured separately as illustrated below.

CPDLC GROUND INITIATED TRANSACTIONS INCLUDING A STANDBY

The graph on the dashboard shows the 95th and 99th percentile values for the delay for the centre/operator selected and teh overall aggregated values for all available data for the preceding 12 months.