Users Manual

ALL
EFFECTIVITY
© Honeywell International Inc. Do not copy without express permission of Honeywell.
Page 5-1
22 Apr 2019
23-15-49
SYSTEM DESCRIPTION, INSTALLATION, AND MAINTENANCE MANUAL
ASPIRE-400
SECTION 5 – SOFTWARE CONFIGURATION
1. Overview: (TASK 23-15-49)
A. Software Part Numbers
(1) SATCOM Products are identified by the software part numbers indicated in the following
table:
Table 5-1. Software Part Numbers
SATCOM Product Software Part Number
SDU EMG33-L011-0101
SCM
Not Applicable
HPA Not Applicable
B. Software
(1) The SDU software is non-partitioned and is developed to Design Assurance Level D
based on the failure classification provided in the FHA/PSSA. It contains COTS software,
and uses Object Orientated methodologies. SE Linux provides part of security domain
segregation.
(2) The SDU application software is on-wing data loadable, and is configured by parameter
data items.
C. Aspire 400 Licensing
(1) Some ORT configurable features require the installation of a license to activate. These
licenses are stored on the SCM either by Honeywell or by the Customer using a license
entry feature accessed by the Maintenance Web GUI, which also reports which licenses
are present. The licenses map directly to an ORT selection and thus the ORT files fully
define the SDU configuration. Cockpit licensed features are permanent, however cabin
licenses may have expiry dates.
(2) The presence of necessary licensing is only checked during on-ground power up, and
never during flight even if repowered. If a necessary license is missing, the SDU enters
the Safe Mode until either the license is loaded or the ORTconfiguration is changed to
selections that do not require licensing.
D. Aspire 400 Configuration
(1) The Aspire 400 functionalities are enabled/disabled and customized by a combination of
hardware discrete interfaces, and parameter data items within Owner Requirement Table
(ORT) Secure and User files. The SDU manages all hardware discrete and parameter
data item configuration for the SATCOM system.
(2) Installation options (for example: which ARINC 429 interfaces are in use and the
expected labels, and SATCOM LRUs present) are contained in the Secure ORT file. User
configurations of preferences that are not related to the installation (e.g. telephone
numbers) are typically in the User ORT files, however in some cases they are in the
secure file.
(3) Secure and User ORTs can be field loaded into the SCM via the Aspire 400 SDU using
the ARINC 615A [ID1] Data Loader. At power up the SDU reads the ORT files on the
SCM and aligns its local working copy if necessary. This alignment will occur if the local
DRAFT
3rd rvw Draft as of:
29 January, 2020