ISPACG ANSP – Ground System Compliance Register
Tahiti
Legend: F = Fully Compliant, P = Partially Compliant, N = Not Compliant
Requirement # |
DO-306 ED 122 Safety Requirement Description |
Status |
Type of evidence collected |
DO306 - ED 122 requirements allocated to the ATS Ground System |
|||
SR-1 |
An indication shall be provided to the initiator when a recipient rejects a data link service request at the application layer. |
F |
System (SSS) and air/ground server software (SRS) requirements of the TIARE system |
SR-2 |
A detected loss of data link service shall be indicated to the controller/flight crew. |
F |
SSS and SRS (HMI) requirements of the TIARE system |
SR-3 |
Data link service shall be established in sufficient time to be available for operational use. |
F |
Datalink service established at TIARE system startup |
SR-4 |
ATSU shall be notified of planned outage of data link service sufficiently ahead of time. |
F |
Contract with ACSP : Each planned outage is advertised 12 hours before by CSP Network Operations Center by fax and email |
SR-5 |
There shall be an indication to the initiator when a message cannot be successfully transmitted. |
F |
Software requirements (air/ground server and HMI) of the TIARE system |
SR-6 |
The end system shall provide unambiguous and unique identification of the origin and destination with each message it transmits. |
F |
Interface control document (ARINC 620 Data Link System Standard and Interface Specification) of the TIARE system with ACARS network |
SR-7 |
A response shall indicate to which messages it refers. |
F |
SSS requirement of the TIARE system |
SR-8 |
The aircraft and the ATSU shall exchange via data link and process the same route information. |
F |
SSS requirement of the TIARE system |
SR-9 |
The end system shall time stamp to within one second UTC for each CPDLC message when it is released for onward transmission. |
F |
Ad hoc tests regarding Air/ground server |
SR-11 |
Any processing (data entry/ encoding/ transmitting/decoding/ displaying) shall not affect the intent of the message. |
F |
Messages encoded/decoded according to DO-219 - Minimum Operational Performance Standards for ATC Two Way Data Link Comms (TWDL) - prepared by: SC169 |
SR-12 |
The end system shall reject messages not addressed to itself. |
F |
ACARS ICD |
SR-13 |
The initiator shall transmit messages to the designated end system. |
F |
Interface control document (ARINC 620 Data Link System Standard and Interface Specification) of the TIARE system with ACARS network |
SR-14 |
The ATSU system shall indicate to the controller when a required response for a message sent by the ATSU is not received within the required time (ETTRN). |
F |
TIARE system requirements |
SR-15 |
When the end system receives a message whose time stamp exceeds ETTRN, the end system shall provide appropriate indication. |
F |
ADS-C : |
SR-16 |
The ATSU and aircraft end system shall prevent the release of clearance and operational responses without controller or flight crew action. |
F |
TIARE system requirements |
SR-17 |
The recipient system shall prohibit operational processing of corrupted messages. |
F |
CRC implemented as per ARINC 622-2, ATS Data Link Applications Over ACARS Air-Ground Network. Messages with invalid CRC are rejected |
SR-18 |
The recipient shall be able to determine the message initiator. |
F |
SRS (HMI) requirements of the TIARE system |
SR-19 |
The recipient system shall prohibit operational processing of messages not addressed to the recipient. |
F |
Safety check : messages are rejected at the ARINC 620 level if the address does not match offline predefined system addresses |
SR-20 |
ATSU shall only establish and maintain data link services when the aircraft identifiers in data link initiation correlate with the ATSU’s corresponding aircraft identifiers in the current flight plan. |
F |
System (SSS) and air/ground server software (SRS) requirements of the TIARE system |
SR-21 |
The aircraft identifiers used for data link initiation correlation shall be unique and unambiguous (e.g. the Aircraft Identification and either the Registration Marking or the Aircraft Address) |
F |
System (SSS) and air/ground server software (SRS) requirements of the TIARE system : coupling an aircraft with a flight plan requires matching the Callsign and either one of the following fields from the message with the corresponding fields in the flight plan: |
SR-23 |
The ATSU shall not permit data link services when there are no compatible version numbers. |
F |
System requirement of the TIARE system : If CM logon is received with no compatible application, it shall be rejected: a warning shall be sent to the Operational Supervisor |
SR-24 |
Messages shall be responded to in |
F |
Training of controllers |
SR-25 |
The end system shall be capable of detecting errors that would result in mis-delivery introduced by the communication service. |
F |
CRC implemented as per ARINC 622-2, ATS Data Link Applications Over ACARS Air-Ground Network. Messages with invalid CRC are rejected |
SR-26 |
The end system shall be capable of detecting errors that would result in corruption introduced by the communication service. |
F |
System requirements (semantic checks shall be performed on each received message) |
