Version monitoring

Version Modification Date

1.0 Initial document October 2010
1.1 V/Vs setting on SPS administrator module November 2010
1.2 ‘Show border’ in configuration file and ‘Use of unpaved April 2011
runways’ in fleet file
1.3 Maximum tailwind for takeoff and landing in fleet file September 2011
2.0 Weight and Balance module addition September 2012

3.0 SPS on iPad addition January 2014

3.1 W&B data importation (§ B.3.9) June 2014

4.0 General – FOS interfaces modifications October 2015

Main menu – Options panel (§ B2.1)
Configuration file – Display mode (§ B3.2)
Fleet Database – Fleet common for FOS and SPS (§ B3.3)
SPS File Administrator – Databases removal (§ C1.2)

5.0 Release of version 2.0 July 2017

iOS version upgrade
Fleet Database – Operational limits computation

5.1 Release of version 2.1 January 2018

5.2 Release of version 2.2 June 2018

SPS Administrator – user guide 1 / 51 v5.2 – JUN 18

A. INTRODUCTION................................................................................................................................4

B. SPS/ ADMINISTRATOR ...................................................................................................................5

B1. SPS DATA FOLDER ...................................................................................................................................5

B2. SPS ADMINISTRATOR MENU ......................................................................................................................5
B2.1. MAIN MENU ........................................................................................................................................... 5
B2.2. HOME MENU ......................................................................................................................................... 7
B2.3. DATABASE MENU ................................................................................................................................ 7
B2.4. SPS MENU ............................................................................................................................................. 7
B3. SPS CONFIGURATION FILE .........................................................................................................................8
B3.1. CREATE OR OPEN A SPS CONFIGURATION FILE ................................................................................. 8
B3.2. GENERAL TAB ........................................................................................................................................ 8
B3.3. TAKEOFF TAB......................................................................................................................................... 9
B3.4. APPROACH/LANDING TAB ................................................................................................................... 10
B3.5. WEIGHT AND BALANCE TAB ................................................................................................................ 10
B3. FLEET DATABASE ....................................................................................................................................12
B3.1. CREATE OR OPEN A FLEET DATABASE ............................................................................................... 12
B3.2. DEFINE FLEET DATABASE AND SPS/USER UNITS.............................................................................. 13
B3.3. CREATE AN AIRCRAFT ......................................................................................................................... 13
B3.4. GENERAL TAB ...................................................................................................................................... 16
B3.5. TAKEOFF TAB....................................................................................................................................... 17
B3.6. APPROACH/LANDING TAB ................................................................................................................... 18
B3.7. WEIGHT & BALANCE GENERAL TAB .................................................................................................... 19
B3.8. WEIGHT & BALANCE CONFIGURATION TAB ........................................................................................ 20
B3.9. WEIGHT & BALANCE DATA IMPORTATION ........................................................................................... 22
B3.10. DUPLICATE AN AIRCRAFT .................................................................................................................. 23
B3.11. DELETE AN AIRCRAFT ....................................................................................................................... 23
B4. AIRPORT DATABASE ...............................................................................................................................23
B5. SPS UPDATE MODULE ............................................................................................................................24
B5.1. CREATE AN UPDATE PACKAGE............................................................................................................ 24
B5.2. GENERATION PROCESS SUCCESSFUL ................................................................................................ 27
B5.3. GENERATION PROCESS UNSUCCESSFUL ........................................................................................... 27

C. SPS FILE ADMINISTRATOR (WINDOWS-BASED PLATFORM ONLY) ...................................28

C1. UPDATE PACKAGE UPLOADING ..................................................................................................................28

C1.1. UPLOADING PROCESS ......................................................................................................................... 28
C1.2. SPS DATABASES MANAGEMENT ......................................................................................................... 30
C2. CALCULATION LOGS RETRIEVE ...................................................................................................................33

D. SPS FILE SHARING (IPAD) ...........................................................................................................34

D1. UPDATE PACKAGE UPLOADING .................................................................................................................34

D1.1. UPLOAD THROUGH ITUNES ................................................................................................................. 34
D1.2. UPLOAD THROUGH ‘OVER THE AIR’.................................................................................................... 36
D2. LICENSE FILE INTEGRATION .......................................................................................................................39
D2.1. INTEGRATION THROUGH ITUNES ........................................................................................................ 39
D2.2. INTEGRATION THROUGH ‘OVER THE AIR’........................................................................................... 40
D3. SPS FILES DOWNLOADING .......................................................................................................................41
SPS Administrator – user guide 2 / 51 v5.2 – JUN 18
E. APPENDIX........................................................................................................................................42

E1. WEIGHT & BALANCE CONFIGURATION – OPERATIONAL LIMITS COMPUTATION ....................................................42

E1.1. CERTIFIED LIMITS ................................................................................................................................ 42
E1.2. OPERATIONAL MARGINS...................................................................................................................... 42
E1.3. OPERATIONAL LIMITS .......................................................................................................................... 43
E2. ‘OVER THE AIR’ (OTA) CONFIGURATION.....................................................................................................44
E2.1. REPOSITORY CREATION ...................................................................................................................... 44
E2.2. SPS CONFIGURATION ......................................................................................................................... 47

SPS Administrator – user guide 3 / 51 v5.2 – JUN 18

 A. INTRODUCTION
The Single-point Performance Software (SPS) is the software that allows the crew or operational ground
staff to achieve fast, optimised, real-time takeoff, landing and load & trim computations.
The SPS falls in two parts:
- the SPS/ Administrator, hosted on Flight Operations Software (FOS) and dedicated for databases
creation and management, update generation; and
- the SPS/ User, which is composed of three computation modules: Takeoff, Landing and Weight &
Balance.
SPS/ User computations are based on airlines customised databases (airport, fleet and configuration)
generated via the SPS/ Administrator.
The update of SPS/User databases on SPS/User host platform includes two steps:
1. Generation of the update package using SPS Update module, within FOS.
2. Integration of the update package in SPS/User using SPS File Administrator, on host platform.
SPS/User can be hosted on any ground PC or class 1 or 2 EFB as specified in the installation document. An
example of SPS deployment in an airline is presented here below:

FLIGHT OPS ENGINEERS DISPATCHERS

LOADMASTERS

- Takeoff & Landing cards

- Weight limitations
- Databases management - Pilots’ support
- Back office calculations - Load & trim sheets
PILOTS ON GROUND

- Takeoff & Landing cards

- Weight limitations
- Load & trim sheets

PILOTS ON BOARD
Takeoff & Landing cards Load & Trim sheet

Administrator

Users
- Takeoff & Landing cards
Results - Weight limitations
- Load & trim sheets
- Following en-route failure

SPS Administrator – user guide 4 / 51 v5.2 – JUN 18

B. SPS/ ADMINISTRATOR
SPS/Administrator is integrated into the FOS (Flight Operations Software) interface.
SPS/Administrator can be run via the Windows Menu: click on ‘Windows Menu’, ‘All programs’, ‘ATR’, ‘ATR
Performance Software’ and launch the software by clicking on ‘FOS’.
SPS/Administrator falls onto:
- A databases manager which allows the user to manage:
 Fleet databases, common for FOS and SPS
 Airport databases, common for FOS and SPS
 Configuration files, only for SPS
- An update module which allows the user to generate database(s) package to update the database(s)
loaded on the SPS/User
B1. SPS Data folder

Once SPS is installed, “ATR Performance Software Data” is created in ‘My

Documents’. All the SPS data are stored in the “SPS” sub-folder.

B2. SPS Administrator menu

The SPS Administrator menus are common with the FOS.
Note: In case FOS has not been contracted, accesses to FOS computation modules in HOME menu are
inhibited.

B2.1. MAIN menu

This menu gives access to the following functions:

New session New FOS computation session

Open session Open FOS computation session
Close Close active database or FOS computation session
Save Save active database or FOS computation session
Save As… Save As active database or FOS computation
session
Print Print FOS computation session results
Options Open the options panel
Help Access to the User Guides, “About FOS” and
Latest developments information
Exit Exit FOS

SPS Administrator – user guide 5 / 51 v5.2 – JUN 18

 B2.1.1 Options panel

General See details below

Performance files folder
Takeoff and Landing chart
In-flight Performance
Flight Planning
En-route net flight path
Cruise Performance Monitoring
See details below
N/A for SPS/Administrator
N/A for SPS/Administrator
N/A for SPS/Administrator
N/A for SPS/Administrator
N/A for SPS/Administrator

B2.1.2 Options panel – General

Fleet database parameters visibility

In the Fleet database, only FOS, only SPS or FOS
+ SPS parameters can be chosen to be displayed.
Note: This option is useful when using only FOS
to avoid unnecessary parameters display (see
Figure below).

Session expert mode

Gives access to expert mode calculations for the
FOS sessions.

Only FOS parameters vs. FOS + SPS parameters display in the Fleet database (takeoff tab)

Access to Expert mode sessions when activated

SPS Administrator – user guide 6 / 51 v5.2 – JUN 18

 B2.1.3 Options panel – Performance files folder

This gives the possibility to modify the folders where the Performance files are located. By default, there are
in C:\ Program Files (x86)\ ATR Performance Software\ Common\ Performance Data Files.

B2.2. HOME menu

Not used for SPS/Administrator.

B2.3. DATABASE menu

This menu gives access to the following functions:

Open Fleet Database
Create Fleet Database
Open Airport database
Create Airport database
Open Route Database
Create Route Database
Open an existing Fleet database
Create a new Fleet database
Open an existing Airport database
Create a new Airport database
Not used for SPS/Administrator
Not used for SPS/Administrator

B2.4. SPS menu

This menu gives access to the following functions:

Open SPS Configuration file Open an existing SPS configuration file
Create SPS configuration file Create an SPS Configuration file
Create SPS Update Package Create an SPS update package

SPS Administrator – user guide 7 / 51 v5.2 – JUN 18

 B3. SPS Configuration file

The Configuration file allows the user to define general settings for the SPS/User. Several SPS Configuration
files can be created and managed. The SPS Configuration file is used only for the SPS/User.
Example: A configuration file for EFB, with full-screen display and no Print button, and a configuration file
for PC, with display in a window, and access to the Print button.

B3.1. Create or Open a SPS Configuration file

To create a new Configuration file: in the SPS menu, choose ‘Create SPS configuration file’ and specify a
name for the new Configuration file.

To open an existing Configuration file: in the SPS menu, choose “Open SPS Configuration file” and choose
the file that needs to be opened.

B3.2. General tab

General window tab allows defining interface parameters. Default settings are proposed as below.

Module
If selected, enable access to takeoff and/or landing and/or weight and balance modules in SPS/User.
Note: Only the modules eligible in the airline license are enabled.
Buttons
If selected, enable access to the following functions in SPS/User:
- Modify: to modify runway data within a takeoff or landing calculation session.
- MEL: to select MEL item(s) for takeoff and landing calculations.
- ER Failures: to select en-route failure item(s) for en-route landing calculations.
- Print: to print takeoff and landing data cards and load & trim sheet.
- Save: to save takeoff, landing and weight & balance inputs and outputs for a specific calculation, on
user demand (CSV files for takeoff, landing and weight and balance stored in SPS “Log” folder).
Note: A trace of each computation is automatically saved, whatever the “Save” configuration is. Automatic
logs are stored in SPS “AutoLog” folder for a period of one month (current month and previous one).
Display mode
‘PC configuration’ is used for SPS/User display on PC:
 ‘Portrait’, opens SPS/User in portrait format with borders (access to minimize)
 ‘Landscape’, opens SPS/User in landscape format with borders (access to minimize)
 ‘Maximized’, opens SPS/User on full screen with no border
SPS Administrator – user guide 8 / 51 v5.2 – JUN 18
If selected, ‘Tablet configuration’ displays SPS/User in full screen, and in Portrait or Landscape depending on
the tablet’s orientation.
Start page
If ‘Flight number mandatory’ is ticked, the flight number will be considered as a mandatory field in SPS/User.
It is mandatory when the Weight & Balance module is installed, as it is required for the printed Load & Trim
sheet.
‘Identification’ field allows changing the name of the identification field in the SPS/User welcome page.
Virtual keyboard
If selected, SPS/User virtual keyboard will be automatically displayed as soon as a field is activated.

B3.3. Takeoff tab

Takeoff window tab allows defining SPS/User takeoff module settings. Default settings are proposed as
below.

Flaps default setting

If several flaps settings are available, ‘Yes’ allows defining a default one (to be done in the Fleet database).
This default setting will be displayed in the SPS/User takeoff module, in the ‘Flaps’ field. If ‘None’ is selected,
‘Flaps’ field will be empty, and user will need to select a flaps setting for each calculation.
If only one flaps setting is available, it will be displayed by default without any possibility to change;
whatever this setting is.
Power default setting
If several power settings are available, ‘Standard’ allows defining ‘Standard’ as a default power setting, to be
displayed in the SPS/User takeoff module, in the ‘Power’ field. If ‘None’ is selected, ‘Power’ field will be
empty, and user will need to select a power setting for each calculation.
If only ‘Standard’ power setting is available, it will be displayed by default without any possibility to change;
whatever this setting is.
Air conditioning default setting
If several air conditioning settings are available, ‘Yes’ allows defining a default one (to be done in the Fleet
database). This default setting will be displayed in the SPS/User takeoff module, in the ‘Air Cond.’ field. If
‘None’ is selected, ‘Air Cond.’ field will be empty, and user will need to select air conditioning setting for each
calculation.
If only one air conditioning setting is available, it will be displayed by default without any possibility to
change; whatever this setting is.
Cross wind warning
If selected, a warning message will be displayed in case the crosswind limit (to be defined in the Fleet
database) is exceeded.
Output
If selected, enables display of limitation code and/or min acceleration height/altitude and/or V REF in the
SPS/User takeoff calculation outputs.
Note: For ATR 42, VREF displayed will be the one from the default landing flaps set in the SPS Fleet
database\Landing tab.
For instance if the default flaps set for landing is 35°, VREF for flaps 35 will be displayed.
SPS Administrator – user guide 9 / 51 v5.2 – JUN 18
 B3.4. Approach/Landing tab
Approach/landing window tab allows defining SPS/User landing module settings. Default settings are
proposed as below.

Flaps default setting

See B3.3. Takeoff tab above
Power default setting
See B3.3. Takeoff tab above
Approach type default setting
If several approach type are available, ‘Yes’ allows defining a default one (to be done in the Fleet database).
This default approach type will be displayed in the SPS/User landing module, in the ‘App. Cat.’ field. If ‘None’
is selected, ‘App. Cat.’ field will be empty, and user will need to select an approach category for each
calculation.
If only one approach is available, it will be displayed by default without any possibility to change; whatever
this setting is.
Braking default procedure setting
If several braking procedure settings are available, ‘Normal’ allows defining ‘Normal’ as a default braking
procedure setting, to be displayed in the SPS/User landing module, in the ‘Braking’ field. If ‘None’ is selected,
‘Braking’ field will be empty, and user will need to select a braking procedure setting for each calculation.
If only ‘Normal’ braking procedure setting is available, it will be displayed by default without any possibility
to change; whatever this setting is.
Note: The braking procedure list is displayed in the fleet database (see B3.6. Approach/Landing tab).
Note: The braking procedure settings are available if ticked in the fleet database.

Note: The ‘Braking’ field will not be displayed and the computation will be done in normal braking in the
SPS/User landing module if:
 The braking procedure list is not displayed in the fleet database (depends on aircraft
version), or
 No braking procedure setting is available (not ticked in the fleet database).
Cross wind warning
See B3.3. Takeoff tab above
Output
If selected, enable display of limitation code in the SPS/User landing calculation outputs.

B3.5. Weight and Balance tab

Weight and Balance window tab allows defining SPS/User weight and balance module settings. Default
settings are proposed as below (except for Electronic sending which is unticked by default).

SPS Administrator – user guide 10 / 51 v5.2 – JUN 18

Crew configuration default setting
If several crew configurations are available, ‘Yes’ allows defining a default one (to be done in the Fleet
database). This default setting will be displayed in the SPS/User weight and balance module, in the ‘Crew’
field. If ‘None’ is selected, ‘Crew’ field will be empty, and user will need to select a crew configuration for
each calculation.
If only one crew configuration is available, it will be displayed by default without any possibility to change;
whatever this setting is.

Catering default setting

This setting is applicable to the ‘Catering’ field in the SPS/User weight and balance module. The setting logic
is the same as for ‘Crew configuration default setting’ detailed above.

Taxi fuel default setting

‘Yes’ allows defining a default value (to be done in the Fleet database). This default setting will be displayed
in the SPS/User weight and balance module, ‘Taxi (fuel)’ field. If ‘None’ is selected, ‘Taxi (fuel)’ field will be
empty, and user will need to select a taxi fuel quantity for each calculation.

Output
If selected, enable display of the ticked items in SPS/User weight and balance calculation outputs.
CG and Trim refer to takeoff configuration. Certified limits are the flight limits and takeoff and landing limits.

Pax distribution filling

If ‘Per pax type’ is selected, the ‘Pax’ zone will be displayed before the ‘Cabin’ zone in the SPS/User main
page. The user will start filling the type of pax, then distribute the pax on the cabin zones.
A cabin distribution may be automatically suggested if ‘Auto cabin distribution’ is ticked. In the SPS/User, a
function button will appear.
If ‘Per cabin zone’ is selected, the ‘Cabin’ zone will be displayed before the ‘Pax’ zone in the SPS user main
page. By zone, the user will be able to specify pax types.
The calculated passenger index is more precise in case of ‘Per cabin zone’ selection as the pax weight per
type is considered for the index calculation of each cabin zone. Whereas in the ‘Per pax type’ case, the pax
distribution per type is unknown; so the passenger index per cabin zone is calculated assuming the weight of
the highest pax type (generally Male’s weight). Even if less precise, this latest option is still acceptable.

Optional functions
If selected, enable display of the function buttons ‘U/L’ and/or ‘ACK LMC’ and/or ‘DATA TRANSFER’ and/or
‘SEND’ in SPS/User weight and balance outputs.
Electronic sending

SPS Administrator – user guide 11 / 51 v5.2 – JUN 18

If selected, the associated fields must be filled-in:
o SMTP outgoing mail server (mandatory for Windows-based SPS User only)
 Host name: SMTP server DNS name.
 Server port: SMTP server port. (Typically 25).
 Authentication: Specifies the mechanism used when authenticating to an SMTP service over
the network (Anonymous, basic or NTLM).
 SSL: To active the SSL connection.

o Sender mail information (mandatory for Windows-based SPS User only)

 User name: if any, otherwise email address
 Password: email account password
 Mail: email address

o Recipient emails (mandatory)

List of e-mails to which the electronic loadsheet must be sent. A maximum of 10 recipients may be
defined.
Note: For iPad version, the sender account settings are configured in the Mail application of the iPad. The
Load and Trim sheet (W&B output) is sent to the recipients attached in an email.

B3. Fleet database

The Fleet database allows the user to define the characteristics impacting performance and weight &
balance calculations for each aircraft within a fleet.
The aircraft defined in the Fleet database will be available for selection in the SPS/User or in a FOS session.
Several Fleet databases can be created and managed.
The Fleet database is common for SPS/User and FOS. The fields necessary only for SPS are marked with a
star *. To filter the fields used for FOS or SPS, refer to B2.2. Options panel – General.

B3.1. Create or open a Fleet database

To create a new Fleet database: in the DATABASE menu, choose “Create Fleet Database” and specify a
name for the new Fleet database.

To open an existing Fleet database: in the Database menu, choose ‘Open Fleet Database’ and choose the file
that needs to be opened.

SPS Administrator – user guide 12 / 51 v5.2 – JUN 18

 B3.2. Define Fleet database and SPS/User units
Units to be used within the Fleet database can be customized by clicking on “Units” in the tree view. The
same units will be used in the SPS/User.
Note: Units used in the airport database have no impact on SPS/User.
Note: If Pounds (lb) is selected, the length unit will be automatically set to inches and volume unit to
gallons in the Weight & Balance tabs.

B3.3. Create an aircraft

To add a new aircraft in the file: right click in the tree view on the Fleet database name and choose “Add
new aircraft” in the proposed menu.

An “Add new aircraft” window pops-up. Fill the aircraft Identification (registration or aircraft type for
example); field is limited to 40 characters. This identification will be the one displayed for selection in the
SPS/User, or in a FOS session.

SPS Administrator – user guide 13 / 51 v5.2 – JUN 18

A comment can be associated to the aircraft, this is an optional setting (18 characters maximum). This
comment will not be displayed in SPS/User but will appear in the tree view right to the identification.
Select the aircraft Model into the list. Once selected, other fields are filled in with default values.
Note: Only the aircraft eligible in the airline license are displayed.

SPS Administrator – user guide 14 / 51 v5.2 – JUN 18

Select the aircraft Modifications fitted on the aircraft.
Note: Only the Modifications eligible in the airline license are displayed.
Note: To know the aircraft modifications, refer to the “List of Modifications”
in FCOM General information part.

Select the regulation under which the aircraft is operated: JAR for European
regulations, FAR for American regulations or JAL for Japanese regulations.
Note: There are different JAR regulations depending on the aircraft model.
o JAR-DGAC, French Civil Aviation Authorities
o JAR-CAA, United Kingdom Civil Aviation Authorities
o JAR-DOT, Canadian Civil Aviation Authorities
Once the previous parameters are set, the following information fields are automatically filled:
- Engines (for information only)
- Propellers (for information only)
- Brakes (for information only)
- Performance files
These are the files that contain all the Performance Data of the aircraft,
there are classified in Low speed or High speed performance. The
performance file selection is made automatically (latest file version available),
however the user still has the choice to change them.
Note: After modification of the performance file content, the last letter of the file name is incremented.
Example: If the current ATR 72-500 fitted with PW127M low-speed performance file is MUE4DB1P. The
previous version was MUE4DB1O and the future version will be MUE4DB1Q.
Important: Performance files in the Fleet database are the ones that have been registered at aircraft
creation. When a performance file is updated (listed in the ‘ReadMe’ file sent with each APS release), the
performance files references have to be updated manually by the user in the Fleet database.
In a FOS computation session, the aircraft has to be (re)selected and the computation run again to take into
account the new performance data.
For the SPS computation, an update package with the Fleet database has to be generated and re-loaded in
the SPS platform, to take into account the new performance data.

Click on <OK> to validate the information. The aircraft appears in the tree view. No further information
needs to be filled-in.

SPS Administrator – user guide 15 / 51 v5.2 – JUN 18

 B3.4. General tab
This page displays data entered during aircraft creation and allows changing aircraft version and/or aircraft
regulation and/or associated performance files if needed.
Reminder: Performance files in the Fleet database are the ones that have been registered at aircraft
creation. When a performance file is updated (listed in the ‘ReadMe’ file sent with each APS release), the
performance files references have to be updated manually by the user in the Fleet database.
In a FOS computation session, the aircraft has to be (re)selected and the computation run again to take into
account the new performance data.
For the SPS computation, an update package with the Fleet database has to be generated and re-loaded in
the SPS platform, to take into account the new performance data.

Reminder: The fields marked with a star * are for SPS/User Takeoff and Landing modules use only.
Note: Access to unpaved runway can be inhibited in SPS/User (to reduce runway status choices) by
choosing ‘No’ in ‘Use of unpaved runways’ section.
Note: Depending on aircraft version, an optional window tab appears to choose the type of environmental
envelop.
Extended minimum temperature refer to ATR 42-300 fitted with MOD 8243 (OAT = -54°C).
Extended maximum temperature refers to ATR 72 fitted with MOD 4384 (ISA +40°)

SPS Administrator – user guide 16 / 51 v5.2 – JUN 18

 B3.5. Takeoff tab
Reminder: The fields marked with a star * are for SPS/User Takeoff module use only.

This page allows customizing:

- V1/VR and V2/VS ratio (radio button). If set to “fixed value”, a value needs to be filled-in.
Note: Those settings are for SPS/User only. The V1/VR and V2/VS ratio for FOS calculations are set
directly in the FOS Module 1 session.
- Default air conditioning setting, if several settings are available (depends on aircraft version) and if
option is selected into the Configuration file. If only one setting is available, field will not be accessible
for change in SPS/User.
- Flaps settings available for takeoff, if several settings are available (depends on aircraft version). If
only one setting available, field will not be accessible.
- Flaps default setting for takeoff, if several settings are available and if option is selected into the
Configuration file.
- Power settings available for takeoff, if several settings are available (depends on aircraft version).
Standard power cannot be deselected.
- Use of reverse on wet and contaminated runway (radio button). This setting cannot be changed
in the SPS/User.
- Wet/Contaminated screen height set by default to 15 ft.
- Wet/Contaminated obstacle clearance set by default to 35 ft.
- Minimum acceleration height set by default to 400 ft. Can be set to higher values.
- Maximum tailwind limitation allowed for takeoff, set by default to the maximum value certified for
the aircraft type.
- Maximum crosswind limitation, depending on runway status and width. Default values are
proposed.
- Takeoff alignment distances for 0°, 90° and 180° entry angle. Default values are proposed. A fixed
value could also be used. Entry angle will then be defined in the airport database.
- Fluids type II/IV list. Complying methodology used when takeoff is performed with de-icing fluids
II/IV previously applied. Labels can be customized following airline policy. If neither “Method 1” nor
“Method 2” is selected, “Fluids type II/IV list” field will not be available on SPS/User. If at least “Method
1” or “Method 2” is selected, “None” is activated and cannot be deselected.
Note: MTOW is defined in the W&B General.
SPS Administrator – user guide 17 / 51 v5.2 – JUN 18
 B3.6. Approach/Landing tab
Reminder: The fields marked with a star * are for SPS/User Landing module use only.

This page allows customizing:

- VREF setting (VREF or VREF + 5). If set to Vref+5, ‘Vref+5’ will be displayed in the SPS/User landing
module outputs and ‘Vref+5’ will be used in the speed calculation.
- Flaps settings available in SPS/User landing module, if several settings available (depends on aircraft
version). If only one setting available, field will not be accessible.
- Flaps default setting for landing, if several settings are available and if option is selected into the
Configuration file.
- Power settings available in SPS/User landing module, if several settings are available (depends on
aircraft version). Standard power cannot be deselected.
- VGA/Vs ratio is set by default to the AFM reference and could be changed throughout the available
range. This ratio is effective for normal conditions only. The one for icing conditions being fixed.
- Dispatch landing factor. Default values are proposed depending on regulation and could be
increased.
- Additional en-route landing factor could be defined if airline policy requires additional factor to the
actual landing distance computed in case of en-route failure.
- Use of reverse on contaminated runway. This setting could then not be changed in SPS/User
landing module, except in en-route failure calculation.
- Approach types available in SPS/User landing module. It is the SPS administrator responsibility to
select only approved approach types.
Note:
Selection on a particular approach type will have the following impacts on the calculation:
- “Visual”: will allow using a go-around value of 2.1% for the go-around performances calculation;
whatever the airport database value is. Air Conditioning will be set OFF; V/V S ratio will be equal to the
value set in the Fleet file.
- “Classic” and “Cat I”: the go-around gradient used for the calculation will be at least the greatest
between the database value and 2.5%. Air Conditioning will be set OFF; V/V S ratio will be equal to the
value set in the Fleet file.
- “Cat II”: the go-around gradient used for the calculation will be at least the greatest between the
database value and 2.5%. Air Conditioning will be set ON; V/VS ratio will be the one defined in the AFM.
- “Steep” will have no impact on go-around performances calculation. Settings for the go-around
calculation will be the same as the “Classic” and “Cat I” ones. If certified on the aircraft type “Steep with
reduced landing distances” will be available for selection. “Steep with reduced landing distances” will
have an impact on the landing performances, as per the AFM supplement.

SPS Administrator – user guide 18 / 51 v5.2 – JUN 18

- Approach type default setting, if several approach type are available and if option is selected into the
Configuration file.
- Maximum tailwind limitation allowed for landing, set by default to the maximum value certified for the
aircraft type.
- Maximum crosswind limitation, depending on runway status and width. Default values are proposed.
- Braking procedure list, available in SPS/User landing module. if several settings are available (depends
on aircraft version). If only one setting is available, field will not be displayed.
Note: if several settings are available and none selected, ‘Braking’ field will be displayed in the SPS/User
landing module. Normal braking will be used for computation.
Note: MLW is defined in the W&B General.

B3.7. Weight & Balance general tab

Reminder: The fields marked with a star * are for SPS/User Weight & Balance module use only.

This page allows defining:

- BW (Basic Weight) = DOW (Dry Operating Weight) – Crew weight (including baggage) – catering
weight
Note: BW is used to compute the operational limits in ‘Automatic computation’ mode.
Note: BW will be used in the FOS Module 3 session to set the OEW by default.
- MAC: BW CG position expressed in % MAC. Basic Index is automatically calculated.
- MZFW (Maximum Zero Fuel Weight), MRW (Maximum Ramp Weight), MTOW (Maximum TakeOff
Weight) and MLW (Maximum Landing Weight).
Note: MZFW is used to compute the operational limits in ‘Automatic computation’ mode.
Note: Fields are pre-filled with the maximum weights authorized for the aircraft model.
Note: Change in MTOW and MLW automatically updates the weight values shown in the Takeoff and
Approach/ Landing window tabs.
Note: MZFW, MTOW and MLW will be used in the FOS Module 3 session to set the weights by default.
- Fuel density, used for the tanks maximum volume check for Fuel On Board in SPS/User.
Note: Fuel density is used to compute the operational limits in ‘Automatic computation’ mode.
- Default Taxi fuel, displayed in SPS/User if option is selected into the Configuration file.
- Index and MAC formula

SPS Administrator – user guide 19 / 51 v5.2 – JUN 18

  C and K coefficients: when modified, all indexes in the tab are automatically updated, as well
as DOI (Dry Operating Indexes) in W&B Configuration tab.
Note: C and K coefficients are used to compute the operational limits in ‘Automatic
computation’ mode.
 RefSta (for information only): Horizontal distance from the station zero to Reference Station
around which all index values are calculated, which is 25%MAC on ATR.
 LEMAC (for information only): Horizontal distance from the station zero to location of the
Leading Edge of the MAC.
- Flight / Cabin Crew member weights and their bag weights/locations (if applicable). The weights and
locations are used for DOW and DOI calculations in W&B Configuration tab.
Note: Flight / Cabin crew member weights are used to compute the operational limits in ‘Automatic
computation’ mode.
- Cabin crew seats: number of seats and location. Seats’ location is used for DOI calculation in W&B
Configuration tab.

B3.8. Weight & Balance configuration tab

Note: This page is only for SPS/User Weight & Balance module use.

This page allows defining one or several aircraft W&B configurations. An aircraft configuration can be added,
duplicated or deleted. The following fields are defined:

- Configuration name is the name that will be displayed in the SPS/User W&B intermediate page.
- Cabin Version is optional. This information will not be shown in SPS/User, but printed in the load and
trim sheet.

SPS Administrator – user guide 20 / 51 v5.2 – JUN 18

 Note: The configurations will be listed in the order they have been created in the SPS/User W&B
intermediate page (no alphabetical order).
- Configuration type: Choose the configuration type between Passenger or Cargo. In case of Cargo
selection, the ‘Pax policy’ and ‘Cabin zones’ frames are replaced by additional ‘Cargo zones’ frames.

Note: automatic computation of operationnal envelope is not available in cargo configuration.

- Cabin zones (passenger configuration): Define the name, the mean H-arm and the maximum of seats
available.
o If ‘Manual Setting’ of operational limits: enter manually in the table the name, the mean H-
arm and the maximum of seats available for each cabin zone.
o If ‘Automatic computation’ of operational limits: double-click on the table to open a “Seat
configuration” window.

 Define a cabin zone name,

 In the table, enter the H-arm of the seat rows of the cabin zone and whether the
seats are installed or not,
 Click on <OK> to validate the information and close the window. The cabin zone
appears in the table. The name, the mean H-arm and the maximum of seats
available are automatically calculated and displayed.
Note: The cabin zones are used to compute the operational limits in ‘Automatic computation’ mode.
Note: To delete a row, select a line and press ‘Del.’ key.
Note: The fields will appear in the same order and position in SPS/User main page, ‘Cabin’ section.
Note: ATR recommends having at least 3 cabin zones defined for the accuracy of the passengers’ index
calculation; as suggested in the Weight & Balance Manual.
- Pax policy (passenger configuration): Define the name, the weight and whether this passenger type
occupies a seat or not.
An optional Hand baggage weight may be defined as well; this weight will be automatically added to all
passenger occupying a seat in the SPS/User, ‘Pax’ section.
Note: The pax policy is used to compute the operational limits in ‘Automatic computation’ mode.
Note: The fields will appear in the same order and position in SPS/User main page, ‘Pax’ section. If a
pax policy is defined, at least one cabin zone must be defined.

- Cargo zones: Define the name, the mean H-arm, the maximum allowed loading and the length.
Note: The cargo zones are used to compute the operational limits in ‘Automatic computation’ mode.

SPS Administrator – user guide 21 / 51 v5.2 – JUN 18

 Note: The fields will appear in the same order and position in SPS/User main page, ‘Cargo’ section.
Note: in passenger configuration, standard cargo compartment lengths are:
 Left forward cargo compartment: 1.977m.
 Right forward cargo compartment: 1.977m (if club seat configuration: 1.213m)
 Aft cargo compartment: 2.212m.
Note: In cargo configuration, three Cargo zones frames are available.

- Catering: Define one or several catering configurations and the maximum trolley weight in operation.
Define the default catering configuration displayed in SPS/User if option is selected into the
Configuration file.
For one catering configuration, weights may be defined at different location (H-arm). To delete a row,
select a line and press ‘Del.’ key.
Note: The catering (H-arm and trolley weight) is used to compute the operational limits in ‘Automatic
computation’ mode.
Note: The catering configurations will be listed in the order they have been created in SPS/User
intermediate page (no alphabetical order).

- DOW items: Additional DOW items not considered previously may be defined; e.g. rafts, repair kits,
ballast... Define a name, location, weight and maximum weight for each. The user will have the
possibility to make modifications to these DOW items in [0-max] weight interval.
Note: The DOW items are used to compute the operational limits in ‘Automatic computation’ mode.
Note: If no DOW items are listed, no <DOW DEVIATIONS> function button will appear in SPS/User
main page.

- Crew configuration: Define one or several crew configurations.

o Define a name,
o tick a default configuration, displayed in SPS/User if option is selected into the Configuration
file,
o tick if an Observer is present in the cockpit (jump seat),
o tick the cabin crew locations: CC1 referring to CC1 defined in W&B General tab.
DOW and DOI are automatically calculated, depending on the catering being selected.
DOW = BW + Flight and Cabin crew weight (and baggage) + Catering weight + DOW items
Note: To delete a row, select a line and press ‘Del.’ key.
Note: The crew configurations will be listed in the order they have been created here and in SPS/User
intermediate page (no alphabetical order).

- Operational limits: Forward and aft operational limits, displayed in plain lines in SPS/User Graphical
output.
 ‘Manual setting’: enter manually the operational limits.
 ‘Automatic computation’: operational limits automatically computed.
Note: ‘Automatic computation’ mode computes the operational limits according to data entered in
Weight & Balance General tab and Weight & Balance Configuration tab
Note: ‘Automatic computation’ mode does not compute the operational limits if no pax policy is defined
and at least one cabin zone is defined (error message is displayed).
Note: for more information about operational limits computation, refer to Appendix E1. Weight &
Balance configuration – Operational limits computation.

B3.9. Weight & Balance data importation

ATR may provide Weight and Balance data (xml file format) in order to fill-in automatically some fields of the
W&B general and W&B configuration tabs. The data comes from the information contained in the Weight &
Balance Manual for a given MSN. The data imported will be:
- In W&B general tab
o MTOW, MLW, MZFW and MRW
- In W&B configuration tab

SPS Administrator – user guide 22 / 51 v5.2 – JUN 18

 o Cabin zones name, location and maximum seats
o Cargo zones name, location and maximum loading

To import the W&B data, right click in the tree view on the aircraft
and choose ‘Import W&B data from XML’.

Browse for the XML data file, and click on ‘Open’.

B3.10. Duplicate an aircraft

A new aircraft can be created by copying an existing aircraft. The resulting aircraft will be initialized with the
same properties (model, version, takeoff and landing options, weights…).

Right click in the tree view on the aircraft that needs to be duplicated and choose ‘Copy' in the menu.
Right click in the tree view on the fleet file name and choose ‘Paste’ in the menu.
Enter the new aircraft identification and comment if any.

The new aircraft will appear in the tree view, stored under the same model
as the initial aircraft.

B3.11. Delete an aircraft

In order to delete an aircraft, right click on it and select ‘Delete’ in the menu. Click on ‘Yes’ to confirm
deletion.
B4. Airport database
Refer to FOS User Guide.

SPS Administrator – user guide 23 / 51 v5.2 – JUN 18

 B5. SPS Update module
The SPS Update module allows creating packages to update the SPS/User databases. The package consists
of a .zip file including updated databases to be delivered to SPS/User.

B5.1. Create an update package

- Check that all SPS files and database are closed.
- Open the update module: SPS menu, choose “Create SPS Update Package”.

- Select which database(s) need(s) to be included in the update package: Fleet database and/or
Configuration file and/or Airport database.

- Select the database to be included in the update package.

The browser is opened by clicking on the appropriate
“select file” button. Choose the database and press
“Open”.

SPS Administrator – user guide 24 / 51 v5.2 – JUN 18

- Select the validity date: the date at which the database will become effective within the SPS. This allows
the update to be loaded in advance and activated at a desired date.

- Do the same for all databases that need to be updated.

- Select the SPS User platform type with the radio button: Windows-based or iPad.
Specify a name and location for the update package (.zip file) by clicking on the “Browse” button.
Note: For iPad package generation, the name of the update package is “database.zip” and cannot be
changed.

Note: If a Fleet file is included in the iPad package generation, a file named “performance.zip” will be
created at the same location than “database.zip” file. This file contains the performance data files of the
aircraft included in the Fleet file.

- Click on “Create Update” button to launch the package generation process.

SPS Administrator – user guide 25 / 51 v5.2 – JUN 18

During package generation, following checks are done on the Fleet database, Configuration file and Airport
database.

Data
Parameters Criteria Error message in .log file
base
MZFW, MTOW, MLW MTOW ≥ MLW ≥ MZFW … must be greater than …

More than 2 dots defined Forward operational limit not defined

Forward ops limit No duplicated weight
Higher weight ≥ MTOW
Aft ops limit Same checks as forward ops limit
At least one defined
Crew configuration
Consistency with Cabin crew seats
Fleet
…with duplicated weight values
…not defined for MTOW
Same as forward ops limit
Crew configuration not defined
… not consistent

Weight ≤ Max DOW item weight higher than max

DOW item
Max > 0 DOW item max weight not consistent
If a pax policy is defined, at least At least one cabin zone/ pax policy
Pax policy one cabin zone must be defined and must be defined.
vice versa.
Total number seats ≤ 74 (ATR
Cabin zones 72) Total seats number too high
≤ 60 (ATR 42)
If electronic sending activated,
Configu
ration

Electronic sending
SMTP fields not empty, Sender and … not defined
recipient email not empty (1)
TORA value out of range
Runway length < (9999m or TODA value out of range
Runway lengths
33333ft) ASDA value out of range
(TORA, TODA, ASDA,
LDA value out of range
LDA)
TODA ≥ TORA TODA, TORA lengths not compatible
ASDA ≥ TORA ASDA,TORA lengths not compatible
Runway slope -4,5% ≤ runway slope ≤ +4,5% RWY slope out of range
Runway width ≥ 14m (46ft) RWY width too narrow
Steep slope approach 4,5° ≤ steep slope approach ≤ 6° Steep Slope App out of range
Airport

Approach climb ≥ regulatory approach climb Approach Climb gradient below

gradient gradient (2.1%) regulatory
Landing climb ≥ regulatory landing climb gradient Landing Climb gradient below
gradient (3.2%) regulatory
Obstacle number ≤ 20 Number of obstacle above 20
If defined from:
● beginning of TORA: no obstacle
Obstacle within TODA. Obstacle within TODA
● end of TORA: no obstacle within
CWY

(1)
For iPad version, only recipient address field must be filled. The sender account settings are configured
in the Mail application of the iPad.

Note: Runway slope, runway width and steep slope approach gradient are checked against certification
values. It is the SPS administrator responsibility to ensure that data are in accordance with airline
operational approvals and aircraft modifications.

SPS Administrator – user guide 26 / 51 v5.2 – JUN 18

 B5.2. Generation process successful
If the update package generation is successful, “Update package created” message is displayed in green.

B5.3. Generation process unsuccessful

If the update package generation fails due to Fleet database, Configuration file or Airport database error
(see checks here above), following error message is displayed in the dialog box.

The .zip file, update package, is not created. A log file is automatically generated in the directory previously
defined, with the name previously defined for the update package and with the extension “.log”.
A summary of the errors is also displayed on the validation dialog box.

SPS Administrator – user guide 27 / 51 v5.2 – JUN 18

If the update package generation fails due to other error, following error message is displayed in the dialog
box. In that case, make sure that no file is already opened. If the error persists, please contact ATR.

C. SPS FILE ADMINISTRATOR (WINDOWS-BASED PLATFORM ONLY)

The SPS File Administrator allows:
- the integration of the license file required to run the SPS/User (please refer to the APS installation user
guide),
- the integration of the update package (.zip file) created with the SPS Update module in the SPS/User,
- The configuration of ‘Over the air’ (OTA) function.
To launch SPS File Administrator: Start / Programs / ATR Performance Software / SPS / SPS File
Administrator.

C1. Update package uploading

The SPS files (databases and license) can be transferred through:

- Manual transfer: ‘Update License’ and ‘Update Package’ tabs
- Wireless transfer: ‘Over The Air’ function.

In ‘Over the air’ tab, OTA function can be enabled or disabled:

- If disabled, update package and license are loaded manually, through ‘Update License’ and ‘Update
Package’ tab.
- If enabled, update package and license are loaded through OTA. ‘Update License’ and ‘Update Package’
tabs should not be used.

SPS Administrator – user guide 28 / 51 v5.2 – JUN 18

 C1.1. Manual upload (‘Update package’ tab)

C1.1.1 Uploading process

- Select ‘Update package’ tab
- Click on the “Browse” button to open the update package browser.

- Select the update .zip file and click “Open” to confirm.

SPS Administrator – user guide 29 / 51 v5.2 – JUN 18

- Click on the “Load” button to load the update package.

If update is successful, a validation message is displayed in green as above.

If update is unsuccessful, “Error installing update package” is displayed in red.

C1.1.2. SPS databases management

Active databases are presented in bold. The active database being the one with the newest validity date,
provided its effective date is earlier or at least equals to today.
Databases can be removed, using the button ‘Remove’.

C1.2. Upload through ‘Over The Air’

The ”Over The Air” (OTA) function allows transferring SPS files wirelessly from a repository (server or local
machine) to multiple computers and/or tablets using Content Management Interoperability Services (CMIS)
protocol.

C1.2.1 Repository server

The repository folder must contain all the SPS files:
 Fleet database,
 Airport database,
 Configuration file,
 License file.
Note: the SPS files must be unzipped before uploaded in
server repository folder.
Note: for more information about OTA configuration, refer to
Appendix E2. ‘Over The Air’ (OTA) configuration.

SPS Administrator – user guide 30 / 51 v5.2 – JUN 18

 C1.2.2 Update package loading process
The ‘Over the air’ tab allows defining server parameters.

- Binding: binding protocol

type offered by CMIS. See
backend compatible
binding to choose
accordingly.

- Endpoint: url endpoint

where the service (CMIS) is
deployed.

- Repository: repository to
connect when there are
multiple repositories
available.

- Path: folder to synchronize

for ATR-SPS.

- Authentication: authentication mode to use to connect. In standard, credentials must be provided by

giving an authorized user and password.

- User: authorized user name.

- Password: associated password.

Note: the SPS files must be unzipped before uploaded in server repository folder.

- Once the OTA function is enabled and

the server parameters are defined, SPS
has to be restarted.
At opening, a message confirms that the
OTA function is activated.
An “UPDATE” button is displayed.
Note: if the credentials data are missing,
a message asks to provide credentials in
SPS settings.

SPS Administrator – user guide 31 / 51 v5.2 – JUN 18

 - If new content is available, the
“UPDATE” button is highlighted.
Note: a spinner on the status bar is
rolling while checking for new content or
synchronizing the SPS files from the
server.
“UPDATE” button is highlighted only when
full content has been correctly
downloaded on the device.

- Click on “UPDATE” button.

A message confirms that the update has
been successfully done.

SPS Administrator – user guide 32 / 51 v5.2 – JUN 18

 - Databases effective dates can be
checked.
Note: Databases will be activated
immediately only if the effective date is
anterior or equal to the current date. If the
effective date is posterior to the current
date, the database will be automatically
activated at the defined date.
Only the active databases effective dates are
displayed here.

C2. Calculation logs retrieve

If ‘Save’ function is activated (see B3.2. General Tab), the saved computations are stored in “Log” folder.
(see B1. SPS Data folder)
Note: A trace of each computation is automatically saved, whatever the “Save” configuration is. Automatic
logs are stored in SPS “AutoLog” folder for a period of one month (current month and previous one). Files
from Autolog folder can be retrieved by the same way.

SPS Administrator – user guide 33 / 51 v5.2 – JUN 18

D. SPS FILE SHARING (IPAD)
D1. Update package uploading

The SPS files (databases, performance and license) can be transferred to iPads through:
- Manual transfer: iTunes
- Wireless transfer: ‘Over The Air’ (OTA) function.

In ‘Settings’ application, ‘SPS’, OTA function can be

enabled or disabled:
- If disabled, update package is loaded through
iTunes.
- If enabled, update package is loaded through
OTA. iTunes cannot be used.

D1.1. Upload through iTunes

The SPS files (database, performance and license) uploading with iTunes is done in the ‘Apps’ tab, ‘File
Sharing’ section.

SPS Administrator – user guide 34 / 51 v5.2 – JUN 18

- Click on the “Add” button to open the browser.

- Select the “database.zip” file and click “Open” to

confirm.
Note: “performance.zip” file is created only if a Fleet file is
included in the iPad package. This file contains the
performance data files of the aircraft included in the Fleet
file.

- The .zip file is temporally visible

in the ‘SPS Documents’.
Note: No need to click on ”Sync”.

- SPS on iPad has to be restarted.

At opening, a message confirms
that the loading was successful.
Click on “ACK”.

SPS Administrator – user guide 35 / 51 v5.2 – JUN 18

 - Welcome page is displayed.
Databases effective dates can be
checked.
Note: Databases will be activated
immediately only if the effective date is
anterior or equal to the current date. If
the effective date is posterior to the
current date, the database will be
automatically activated at the defined
date.
Only the active databases effective
dates are displayed here.

D1.2. Upload through ‘Over The Air’

The ”Over The Air” (OTA) function allows transferring SPS files wirelessly from a repository (server or local
machine) to multiple iPads using Content Management Interoperability Services (CMIS) protocol.

D1.2.1 Repository server

The repository folder must contain all the SPS files:
 Fleet database,
 Airport database,
 Configuration file,
 License file,
 Performance file and associated MD5 file.
Note: the SPS files must be unzipped before uploaded in
server repository folder.
Note: for more information about OTA configuration,
refer to Appendix E2. ‘Over The Air’ (OTA) configuration.

SPS Administrator – user guide 36 / 51 v5.2 – JUN 18

 D1.2.2 Update package loading process
- In ‘Settings’ application, ‘SPS’ section, ‘Server’ allows defining server parameters.

- Binding: binding protocol type offered by

CMIS. See backend compatible binding to
choose accordingly.

- Endpoint: url endpoint where the service

(CMIS) is deployed.

- Repository: repository to connect when there

are multiple repositories available.

- Path: folder to synchronize for ATR-SPS.

- Authentication: authentication mode to use

to connect. In standard, credentials must be
provided by giving an authorized user and
password.

- User: authorized user name.

- Password: associated password.

- Once the OTA function is enabled and

the server parameters are defined, SPS
on iPad has to be restarted.
At opening, a message confirms that the
OTA function is activated.
An “UPDATE” button is displayed.
Note: if the credentials data are missing,
a message asks to provide credentials in
SPS settings.

SPS Administrator – user guide 37 / 51 v5.2 – JUN 18

 - If new content is available, the
“UPDATE” button is highlighted.
Note: a spinner on the status bar is
rolling while checking for new content or
synchronizing the SPS files from the
server.
“UPDATE” button is highlighted only when
full content has been correctly
downloaded on the device.

- Click on “UPDATE” button.

A message confirms that the update has
been successfully done.

SPS Administrator – user guide 38 / 51 v5.2 – JUN 18

 - Databases effective dates can be
checked.
Note: Databases will be activated
immediately only if the effective date is
anterior or equal to the current date. If the
effective date is posterior to the current
date, the database will be automatically
activated at the defined date.
Only the active databases effective dates are
displayed here.

D2. License file integration

D2.1. Integration through iTunes

The process is exactly the same as for uploading Update package. (See D1. Update package uploading for
print screens).

- Click on the “Add” button to open the browser.

- Select the “License.zip” file and click “Open” to confirm. The “License.zip” file is temporally visible in the
‘SPS Documents’.
Note: The SPS license must be named ‘License.zip’ for correct integration by SPS iPad.
- SPS on iPad has to be restarted.
- Only if the company name changed, at opening, a message “Invalid company name” is displayed. Click
on “OK”.

SPS Administrator – user guide 39 / 51 v5.2 – JUN 18

- And enter your company name and key code as sent by ATR Flight Operations Support department.
Click on “ENTER” and “ACK”.

- A message “License load was successfully installed” confirms that the loading was successful. Click on
“ACK”.

D2.2. Integration through ‘Over The Air’

The license file must be uploaded at the same time as the other SPS files.
See D1.2 Upload through ‘Over The Air’.

SPS Administrator – user guide 40 / 51 v5.2 – JUN 18

 D3. SPS files downloading

If ‘Save’ function is activated (see B3.2. General Tab), the saved computations are stored in “Log” folder.
.csv files from this folder can be retrieved by selecting the folder and clicking on “Save to…”.

Note: A trace of each computation is automatically saved, whatever the “Save” configuration is. Automatic
logs are stored in SPS “AutoLog” folder for a period of one month (current month and previous one). Files
from Autolog folder can be retrieved by the same way.

SPS Administrator – user guide 41 / 51 v5.2 – JUN 18

E. APPENDIX
E1. Weight & Balance configuration – Operational limits computation

E1.1. Certified limits

Center of Gravity envelopes are designed in compliance with regulations when aircraft Type Certificate is
granted. ATR aircraft are certified under JAR 25 regulations and follow this rule.
Two certified CG envelopes exist, one for the take-off & landing phases and one for flight phase. They are
defined to ensure a constant manoeuvrability and stability during the flight.

E1.2. Operational margins

The operational margins are determined in order to cover the possible weights and Center of Gravity
inaccuracies (passengers, cargo…) and to take into account the possible moving items during the flight
(landing gear, crew…).
The operational margins are obtained by taking into account individual effects that are assumed to occur at
each flight or not (systematic or non-systematic effects). Depending on the probability of occurrence of the
effects, the associated probability laws are different.

Both forward and aft margins are computed for take-off / landing and in-flight:

The non-systematic effects are:

 The OEW/OECG inaccuracy, assuming a maximum deviation on the OEW (0.5% of MLW) and the
OECG (0.5% of MAC).
 The cargo location inaccuracy, corresponding to ± 10% of the cargo compartment length, the cargo
compartment being loaded to its maximum allowed weight.
 The passenger distribution inaccuracy in each zone, taking into account two different scenarios:
o Passengers seating first on windows seats
o Passengers seating then on aisle seats.
 The passenger weight inaccuracy, assuming an average passenger weight with a standard deviation
σ (17.5kg), at 2σ Gaussian law, covering 95.4% of the population sample.
 The fuel density variation (0.025kg/L), assuming a standard fuel density and a variation of this fuel
density.
 The fuel weight inaccuracy, ± 1% of the full tank capacity, plus ± 1% of the actual fuel quantity in
the tank.

The systematic effects are:

 The Flaps deployment (28m.kg).
 The landing gear retraction:
o Nose landing gear: -26m.kg
o Main landing gear: -139m.kg on ATR72 and -97m.kg
 The cabin crew moving to the third cockpit occupant seat.
 The cabin crew with loaded trolley from galley station to the first passenger row.
 The flight crew from its seat to the lavatory.

SPS Administrator – user guide 42 / 51 v5.2 – JUN 18

 E1.3. Operational limits
The operational margins are applied to the certified limits, resulting in the operational limits.

Certified limits Operational margins Operational limits

The most conservative segment is used as operational limit:

Operational
envelope

Example on ATR 72-212A CG envelopes

Recommendations to figure out operational limits are described in the following documents:

 EASA / AMC3 CAT.POL.MAB.100(a) Mass and balance, loading

 FAA / AC120-27E Section 3 paragraph 110

SPS Administrator – user guide 43 / 51 v5.2 – JUN 18

 E2. ‘Over The Air’ (OTA) configuration

E2.1. Repository creation

‘Over The Air’ function uses the Content Management Interoperability Services (CMIS) protocol to exchange
files and data from a repository (on a server or a local machine) to the computers and tablets.
The first step is to create a repository using an Enterprise Content Management System provider allowing
CMIS, for example:
 Alfresco
 Microsoft SharePoint

E2.1.1 Apple requirements (mandatory for iPad only)

The repository must comply with Apple requirements for the communication with the tablets:
 The X.509 digital server certificate must meet at least one of the following trust requirements:
o Issued by a certificate authority (CA) whose root certificate is incorporated into the
operating system
o Issued by a trusted root CA and installed by the user or a system administrator.
 The negotiated Transport Layer Security (TLS) version must be TLS 1.2. Attempts to connect
without TLS/SSL protection, or with an older version of TLS/SSL, are denied by default.
 The connection must use either the AES-128 or AES-256 symmetric cipher. The negotiated TLS
connection cipher suite must support perfect forward secrecy (PFS) through Elliptic Curve Diffie-
Hellman Ephemeral (ECDHE) key exchange, and must be one of the following:
o TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
o TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
o TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
o TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
o TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
o TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
o TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
o TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
o TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
o TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
o TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 The leaf server certificate must be signed with one of the following types of keys:
o Rivest-Shamir-Adleman (RSA) key with a length of at least 2048 bits
o Elliptic-Curve Cryptography (ECC) key with a size of at least 256 bits.

In addition, the leaf server certificate hashing algorithm must be Secure Hash Algorithm 2 (SHA-2) with a
digest length, sometimes called a “fingerprint,” of at least 256 (that is SHA-256 or greater).

See https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Ar
ticles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW57) for more details.

E2.1.2 Repository creation with Alfresco

Alfresco offers two possibilities:
 to host the repository on a local machine (requires installation)
 or a cloud solution, the repository is hosted on Alfresco servers and is accessible through a web
interface.
See https://www.alfresco.com/platform/content-services-ecm for more details.

See https://www.alfresco.com/platform/content-services-ecm/trial/online for 14-day free trial of cloud

solution.

SPS Administrator – user guide 44 / 51 v5.2 – JUN 18

 E2.1.3 Repository creation with Microsoft SharePoint
For companies using Microsoft SharePoint, the following requirements should be respected to ensure correct
functioning of ‘Over The Air’ function:
 SharePoint version 2010 or later should be used
 CMIS services must be activated
 Basic Authentication must be set:
- Go to ‘Security’.

- Select ‘Specify authentication providers’.

SPS Administrator – user guide 45 / 51 v5.2 – JUN 18

 - Enable ‘Basic authentication’.

 Configuration of SharePoint server using SSL with an https end point.

See https://dev.office.com/sharepoint/docs/general-development/content-management-interoperability-
services-cmis-in-sharepoint for more information.

SPS Administrator – user guide 46 / 51 v5.2 – JUN 18

 E2.2. SPS configuration
The second step is to configure the tablets and/or the computers.
 For Windows based platform, Configuration is performed with SPS file administrator, ‘Over the air’ tab:

 For iPad, the ATR SPS Settings can be set using the “Settings” native application, ‘SPS’ section. ‘Server’
allows defining OTA server parameters:

The over the air mode is introduced in the V2.0.0 release of the application. If enabled, then SPS will be able
to update load package over the air. It means that the update package upload through ‘SPS File
Administrator’ (Windows based platform) or the iTunes mechanism (for iPad) must not be used anymore in
this case.

OTA mode should be disabled to come back to the basic update mechanisms.

SPS Administrator – user guide 47 / 51 v5.2 – JUN 18

For OTA mode, the computers and/or tablets must be configured by entering the following server
parameters:

Parameter Description
Binding The binding protocol type offered by CMIS. See backend compatible
binding to choose accordingly
Endpoint The url endpoint where the service (CMIS) is deployed
Repository The repository to connect when there are multiple repositories available.
Path Indicate the folder to synchronize for ATR-SPS
Authentication The authentication mode to use to connect. In standard, you need to
provide your credentials by giving an authorized user and password
User An authorized user name
Password The associated password

E2.2.1 Alfresco
With Alfresco, the fields should be:

Parameter Value
Binding AtomPub or Browser
Endpoint http://<hostname>:<port>/alfresco/ will list all the endpoints available
for instance there are:
http://<hostname>:<port>/alfresco/api/-default-
/public/cmis/versions/1.1/atom
Repository -default- (if you are using the default configuration)

Path /<folder> (by default it is the user home directory, so it can contain a lot of
files. It is preferable to indicate a sub-folder)
Authentication Standard
User admin (if you are using the default configuration)
Password admin (if you are using the default configuration)

SPS Administrator – user guide 48 / 51 v5.2 – JUN 18

 E2.2.2 Microsoft SharePoint
With SharePoint, the fields should be:

Parameter Value
Binding AtomPub
Endpoint https://[SERVER]/_vti_bin/cmis/rest?getRepositories
Repository [Repository ID] (be careful, repository is case sensitive)
Path /
Authentication Standard
User <username>
Password <password>

SPS Administrator – user guide 49 / 51 v5.2 – JUN 18

 E2.2.3 List of error displayed in SPS concerning OTA
Here after, the list of technical errors managed by the OTA system:

Note: as the server doesn’t transfer any error code, it is necessary to map messages
displayed in SPS to the content of the received messages.

ERROR CONDITION MESSAGE RAISED ON MESSAGE DISPLAYED IN SPS OS

ALFRESCO SHAREPOINT 2013

The server is KO Cannot access The service method invoked Cannot access %url%: One or NET & iOS
%url%: One or requires an optional capability more errors occurred
more errors not supported by the
occurred repository.
Bad gateway Cannot access %url%: One or
more errors occurred or invalid
repository or path doesn’t exist

The EndPoint URL is
missing
Error on binding
The server is OK but the
repository is not found
Parsing Exception Parsing Exception EndPoint URL is missing or invalid NET & iOS
Binding
Parsing Exception Parsing Exception EndPoint URL is missing or invalid NET & iOS
Binding
Bad gateway Repository ‘%repository_id%' For Alfresco NET & iOS
Cannot access %url%: One or
not found!
more errors occurred or invalid
repository or path doesn’t exist

The server is OK, the
repository is OK but the
path is not found
Bad gateway The service call has specified
an object that does not exist in
the Repository.
Other
Invalid repository
For Alfresco NET & iOS
Cannot access %url%: One or
more errors occurred or invalid
repository or path doesn’t exist

Other
Path doesn’t exist
Invalid Login/Password Unauthorized Unauthorized Invalid login/password. NET & iOS
Server is not compliant EndPoint URL must use HTTPS iOS
with https protocol
Certificate is not in TLS Server connection/certificate is not iOS
1.2 version AND/OR compliant with Apple App
Certificate is not cipher Transport Security requirements.
AND/OR the Key of
certificate is KO

SPS Administrator – user guide 50 / 51 v5.2 – JUN 18

 Here after, the list of business errors managed by the OTA system.
Note: In case of error, the package is not synchronized.
Error Condition
The package is not complete, i.e. one of
mandatory files is missing (*.fleet
AND/OR *.airport AND/OR *.conf
AND/OR License)
The package is not complete, i.e. one of
mandatory files is missing (*.fleet
AND/OR *.airport AND/OR *.conf
AND/OR License AND/OR performance
files and corresponding MD5)
No license file is detected but a zipped
license file is found
Several licenses files are found
The package is not complete AND at least
one file with an extension corresponding
to the missing file is found
SPS Administrator – user guide
Message OS
“At least one of mandatory files is missing:” NET
Message is completed with following text(s)
If Fleet database is missing,
Fleet database file is missing
If Airport database is missing
Airport database file is missing
If Configuration file is missing
Configuration file is missing
If License file is missing
License file is missing
“At least one of mandatory files is missing:” iOS
Message is completed with following text(s)
If Fleet database is missing
Fleet database file is missing
If Airport database is missing
Airport database file is missing
If Configuration file is missing
Configuration file is missing
If License file is missing
License file is missing
If Performance files are missing
Performance files are missing
License file must be unzipped. NET & iOS
Several license files found. Only one license must be distributed. NET & IOS
Fleet, Airport and Configuration files must respect the following NET & iOS
format name: YYYYMMDD%file_name%.%extension%
51 / 51 v5.2 – JUN 18