Users Manual

ManualsBrandsHoneywell ManualsTelecom EquipmentAircraft Earth Station

111

112

113

114

115

116

117

118

119

120

ALL

EFFECTIVITY

Page 6-25

22 Apr 2019

23-15-49

SYSTEM DESCRIPTION, INSTALLATION, AND MAINTENANCE MANUAL

ASPIRE-400

(13) The SDU records an Historical Operational event when the flight number changes.

S. Data Load Monitoring

(1) The ACD records security events for the unsigned hash or similar data as calculated for

the part or file at the time the parts or data files are validated, for the software parts and

files protected from intentional corruption during the data load or file transfer process,

through the use of digital signatures or similar mechanisms.

NOTE: CRC values, checksums, parity bits, etc., for software parts and files are not

included in the security logs.

(a) Accepted data load requests including the identity of the initiating device.

(b) Rejected data load requests including the identity of the initiating device.

(d) Each file unsuccessfully transferred as part of the data load process.

(e) Any data load protocol failures that occur during the data load including those

failures that are automatically resolved by the data load process.

T. Software Events

(1) The SDU records events related to:

(a) Critical software errors that do not recover

(b) Software errors that do recover

U. External Interface Monitoring

(1) The SDU reports faults for:

(a) All enabled internal to the following SATCOM ARINC 429 receive interfaces that

are inactive for a minimum of 10 seconds:

1 "BITE Input from HPA"

2 "BITE Input from top/port BSU/Ant"

3 "BITE Input from STDB BSU".

(b) All enabled external to the following SATCOM ARINC 429 receive interfaces that

are inactive for a minimum of 5 seconds:

1 "Data from secondary IRS/GNSS"

2 "Data from GNSS to SDU"

3 "AES ID INPUT"

4 "Data from MCDU 1"

5 "Data from MCDU 2"

6 "Data from MCDU 3"

7 "Data from CFDS"

8 "Data from CMU 1"

9 "Data from CMU 2"

DRAFT

3rd rvw Draft as of:

29 January, 2020