Amadeus Altea Administration Flight Management Business Rules UG May2016

Amadeus Alta
Administration
Flight Management
Business Rules
User Guide
amadeus.com
YOUR USE OF THIS DOCUMENTATION IS SUBJECT TO THESE TERMS
Use of this documentation
You are authorized to view, copy, or print the documentation for your personal use only.
None of the Amadeus data included in the documentation may be sold, transferred, redistributed, retransmitted, published or commercially
exploited in any way without the express advance written permission of Amadeus.
This documentation is provided on an AS IS basis and Amadeus does not warrant any maintenance or support in using this documentation.
Data ownership
This documentation is protected by Intellectual Property rights and is the exclusive property of Amadeus. No licence over these Intellectual
Property rights is herein being granted. You acknowledge that the documentation is the valuable intellectual property of Amadeus and that if you
use, modify or distribute the documentation for unauthorized purposes, you will be liable to Amadeus for any damages it may suffer.
The examples in this document are for illustrative purposes only. The naming of particular airlines, hotels, car rental agencies, or other companies
in these examples does not constitute an endorsement, express or implied, of Amadeus by these companies or of these companies by Amadeus.
Product offers, prices, terms and other information provided herein are subject to change without notice. You should determine the appropriateness
of any product for your intended purpose and needs.
Amadeus makes no warranty of any kind including but not limited to the implied warranty of merchantability and fitness for a particular purpose.
This application is using the XulRunner open source project. You can download its source code using the following URL:
For 1.X versions: http://coderepo.eu/smrbVwgf/EuxkMtpX
For 2.X versions: http://coderepo.eu/zhLJbaFf/eDCaRWhb
2016 Amadeus s.a.s.

All Rights Reserved.
Edition 8.5 For Amadeus Alta Administration 3.511
Job Number 4010 FE 0814
Published by:
Amadeus Learning Services

email: learning@amadeus.com
May 2016
Table of Contents
Before You Start ..................................................................................... 1

What's New in This Document.............................................................. 3
Chapter 1
Introduction to Business Rules............................................................. 5
Starting the Business Rules Application ............................................... 6
Market Pair Rules................................................................................. 7
Chapter 2
Managing Markets .................................................................................. 9
What Are Markets and Market Pairs? ................................................... 9
Examples of Market Definitions ..................................................................... 9
Displaying Existing Markets................................................................ 10
Creating Markets ................................................................................ 12
Updating Markets ............................................................................... 15
Deactivating and Reactivating Markets .............................................. 17
How to Display Market History ........................................................... 18
Chapter 3
Managing Rules.................................................................................... 21
Overview of Market Pair Rules ........................................................... 21
Application of Rules ........................................................................... 22
Rule Criteria Weight ........................................................................... 22
Understanding Rule Content Windows ............................................... 27
Creating a Business Rule ................................................................... 31
Updating Rules................................................................................... 33
Deleting Rules .................................................................................... 35
Exporting a Business Rule Table ....................................................... 36
Viewing the Market for a Business Rule ............................................. 38
Viewing Flight Usage for a Business Rule .......................................... 39
Comparing Rules ............................................................................... 40
Duplicating Rules ............................................................................... 41
Splitting Rules .................................................................................... 43
Displaying Rule History ...................................................................... 45
Printing a List of Business Rules ........................................................ 47
Searching for Business Rules ............................................................ 48
Verifying the Business Rules for Flight Management.......................... 51
2016 Amadeus s.a.s. - All Rights Reserved i

Amadeus Alta Administration Flight Management Business Rules User Guide
Chapter 4
Managing Flight Groups ...................................................................... 53
Displaying Existing Flight Groups ....................................................... 53
Creating Flight Groups ....................................................................... 55
Updating Flight Groups ...................................................................... 57
How to Delete a Flight Group ............................................................. 58
How to Display Flight Group History ................................................... 59
Chapter 5
Mandatory Rules .................................................................................. 61
Chapter 6
Ground Handling Rules ....................................................................... 63
Rules in a Ground Handling Solution.................................................. 63
Handling Organisation Business Rules ....................................................... 63
Operating Airline Business Rules ................................................................ 65
Ground Handling Rule ........................................................................ 66
Chapter 7
Engineering Rules................................................................................ 69
Aircraft Basic Weight Name Rule ....................................................... 70
Aircraft Limitations Message Priority Rule .......................................... 72
Aircraft Maximum Weights Name Rule ............................................... 76
Aircraft Schedule Rule........................................................................ 79
Baggage Weights Rule....................................................................... 81
Carrier/Aircraft Subtype Fitted Interior Rule ........................................ 84
Carrier/Aircraft Subtype Rule.............................................................. 87
Crew Baggage Weights Rule ............................................................. 90
Crew Distribution Rule........................................................................ 95
Crew Weights Rule ............................................................................ 99
Dry Operating Weight Change ......................................................... 102
Dry Operating Weight Name Rule .................................................... 105
Dynamic Passenger Weights Rule ................................................... 108
Final Fuel Release Rule ................................................................... 111
Forecast ZFW Calculation Rule ........................................................ 113
Forecast ZFW Change Rule ............................................................. 119
Fuel CG Targeting Processing Rule ................................................. 122
Fuel Change Tolerance Rule............................................................ 127
Fuel Density Rule ............................................................................. 129
Fuel Density Update Rule ................................................................ 131
Fuel Reduction Rule ......................................................................... 133
Fuel Standard Distribution Name Rule ............................................. 136
Fuel Retention in Tank Rule ............................................................. 138
Fuel Status Rule............................................................................... 140
Ideal Trim Area Rule ........................................................................ 142
Loadsheet Tolerance Rule ............................................................... 145
Passenger Weights Rule .................................................................. 148
Passenger Non-Standard Weights Rule ........................................... 151
Pantry Code Rule ............................................................................. 155
Pantry Food Content No Uplift Rule ................................................. 158
Pantry Food Content Weight Rule .................................................... 161
ii Edition 8.5
Table of Contents
Potable Water No Uplift Rule............................................................ 166

Potable Water Weight Rule .............................................................. 169
Predicted ZFW Fuel Split Rule ......................................................... 174
Ramp Tolerance Limits Rule ............................................................ 176
Taxi Fuel Rule .................................................................................. 181
Chapter 8
Administrator Rules ........................................................................... 183
ACARS Fuel Status Request Frequency Rule .................................. 184
ACARS Header Rule ........................................................................ 186
ACARS Response Notification Rule ................................................. 188
Approve Distribution Rule ................................................................. 190
Autoload Bulk Mixing Rule ............................................................... 193
Autoload Distribution Options Rule ................................................... 196
Autoload Theme Name Rule ............................................................ 199
Baggage Classification Rule............................................................. 203
Baggage Commodity Creation Rule ................................................. 205
Baggage Segregation Rule .............................................................. 207
Baggage Statistics Override Rule ..................................................... 212
Baggage Type Rule ......................................................................... 214
Cargo Delivery Sequence Rule ........................................................ 216
Commodity Conversion Threshold Rule ........................................... 219
Create Hub Containers Rule ............................................................ 222
Deadload Uplift Offload Message Parameter Selection Rule ............ 225
DG/SL Conflicts Rule ....................................................................... 228
DG/SL Maximum TI Rule ................................................................. 234
DG/SL Notification Rule ................................................................... 236
DG/SL TI Maximum Height Rule ...................................................... 239
Document Type Facility Routing Rule .............................................. 243
Domain Rule .................................................................................... 248
Dynamic Capacity Calculation Rule.................................................. 253
Equipment Configuration Rule.......................................................... 254
Express Cargo Commodity Rule ...................................................... 257
Flight Departed Status Rule ............................................................. 260
Flight Departure Minimum Status Required Rule.............................. 263
Flight Event Notification Data Rule ................................................... 266
Flight Handling Type Rule ................................................................ 268
Forecast ZFW Dependency Rule ..................................................... 271
Ground Handling Document Format Rule......................................... 274
IATA Service Type Rule ................................................................... 276
Inhibit ACARS Preliminary Loadsheet Creation Rule ....................... 278
Inhibit Approval of Distribution Rule.................................................. 281
Inhibit EOP Creation Rule ................................................................ 284
Inhibit Final Loadsheet Creation Rule............................................... 287
Inhibit Load Instruction Report Creation Rule ................................... 290
Inhibit Provisional Loadsheet Creation Rule ..................................... 293
Last Minute Change Threshold Limits Rule ...................................... 295
Manual Last Minute Change Rule .................................................... 300
Maximum Baggage ULD Rule .......................................................... 303
Notification Priority Rule ................................................................... 305
NOTOC Emergency Number Rule ................................................... 309
Offload Reasons Rule ...................................................................... 311
Outbound Teletype Message Delivery Rule ..................................... 315
2016 Amadeus s.a.s. - All Rights Reserved iii

Outbound Teletype Message Originator Rule ................................... 319

Out of Scope System Address Rule ................................................. 322
Parallel Run Rule ............................................................................. 324
Passenger Gender Type Weights Rule ............................................ 325
Process External Cargo Feed Message Rule ................................... 327
Process External Crew Message Rule ............................................. 330
Radio Frequency Rule...................................................................... 332
Ramp Final Clearance Rule ............................................................. 334
Selected Passenger and Baggage Statistics Rule ............................ 336
Shift Summary Layout Rule .............................................................. 339
SK/SSR Total Volume Rule .............................................................. 343
Supplementary Information Rule ...................................................... 346
Template Flight Type Rule ............................................................... 349
ULD Capacity Rule ........................................................................... 351
ULD Stock Control Rule ................................................................... 354
UWS/NTM Message Processing Rule .............................................. 357
WWF Limits Rule ............................................................................. 360
WWF Override Rule ......................................................................... 363
Chapter 9
Departure Plan Simulation................................................................. 365
How to Simulate a Flight .................................................................. 366
Departure Plan Simulation Screen ................................................... 368
Appendix A
Reference Information ....................................................................... 371
Service Type Codes ......................................................................... 371
Country Codes ................................................................................. 371
Region Codes .................................................................................. 375
Document and Message Types ........................................................ 376
Departure Control Event and Activity Codes .................................... 377
When Are Rules Called? .................................................................. 386
Index ................................................................................................... 389
iv Edition 8.5
Before You Start
Purpose of This Document

This document describes the Business Rules used to configure the Alta
Departure Control - Flight Management application.
It describes how to create, modify, or delete business rules.
Audience
This document is intended for airline, or in certain situations, ground handling
personnel, who are responsible for creating and modifying Flight Management
business rules.
Conventions
Functionality that can be activated upon request is indicated in this document

with the spanner icon. The terms and conditions of features available for
activation are described in the Alta Departure Control - Flight Management
Product Catalogue. Please contact Amadeus Product Management for more
information.
Related Reference Material

The reference materials related to this document are as follows:
Flight Management Getting Started
Flight Management Glossary
Load Controller User Guide
Flight Management Mobile User Guide
Flight Management Functionality for Freighter & Combi Aircraft
DBM for Flight Management User Guide
Plan Template Management User Guide
Note: Information on the following functions is available in online help format

only: Load Controller Supervisor, Domain Allocation, Departure
Controller, Freight, Ramp.
2016 Amadeus s.a.s. - All Rights Reserved learning@amadeus.com 1

Latest Version of This Document

For the latest version of this document, and other reference material:
For Airline and Ground Handler Agents:

Contact your supervisor for further information and help.
For Airline Supervisors and Helpdesk Agents:

1. Connect to the Amadeus Airline Extranet:
https://customers.amadeus.com/extranets/airlines/index.jsp
2. New users need to click on Register with Amadeus.
3. When you are logged in, click on the Learning & Support link.
4. Click on the e-Support Centre link.
5. In Amadeus e-Support Centre, browse or search in in Reference Materials >
Alta Suite > Alta DC Flight Management to find the document you need.
For Ground Handler Supervisors and Helpdesk Agents:

1. Connect to Amadeus e-Support Centre:
https://mye-supportcentre.amadeus.com
2. Select Ground Handler in the Who Are You field.
3. Click on the User ID tab.
4. Enter the Organisation, User ID and Password that you use to access
Amadeus Alta Flight Management and Customer Management.
New users need to register by following the on screen instructions.
5. Browse or search in in Reference Materials > Alta Suite > Alta DC Flight
Management to locate the document.
Feedback on This Document

Your feedback is very important, and will help us to improve this document.
Please email us with your comments and suggestions:
learning@amadeus.com
2 Edition 8.5
Before You Start
What's New in This Document

This edition includes the following changes related to updated functionality in
Alta Departure Control - Flight Management 16.2 and Alta Administration
3.511:
New Business Rules
Activation Business Rule

Required
Y DG/SL Notification Rule on page 236.
Modified Business Rules

Required
Y Additional fields in the Fuel CG Targeting Processing Rule on page 122.

Y Additional fields in the Out of Scope System Address Rule on page 322.
Other Changes

Required
Y When the following rules are updated, Flight Management updates the
potable water or pantry figures on existing and subsequent flights, up to
status LSF:
Pantry Food Content No Uplift Rule on page 158.
Potable Water No Uplift Rule on page 166.
N/A Clarification of the Aircraft Type code, available in the rule criteria of
several business rules.
N The Inhibit Approval of Distribution rule will be renamed the Approve
Distribution rule in July 2016. Both titles of this rule have been included
in this version of the user guide.
For further information about product changes in each release, refer to the latest
Flight Management Release Notes and Product Catalogue, available from the
Flight Management Product Info site.

Chapter 1
Introduction to Business Rules
The Amadeus Alta Administration Business Rules application allows you to set
up business rules for Customer Management and Flight Management.
Business rules are used to automate system processes in order to have the least
amount of manual intervention possible.
For example:
For Flight Management, the system references the pantry and crew
information from the business rules at flight creation to know what is required
for a flight.
For Customer Management, the system references which APIS information is
required at customer acceptance.
When the system calls a business rule, it compares the current scenario with the
criteria defined in each rule. When a match is made, the rule returns information
that instructs the system how to behave. Standard rule criteria typically include
the operating airline, market pairs for the flight, flight numbers, and start and end
dates for the rule.
Business rules are called at various times throughout the lifecycle of a flight in
Alta Departure Control.
Flight Management Business Rules Called by Customer

Management
The following Flight Management business rules are called within Customer
Management:
Document Type Facility Routing rule, using the handling airlines reference
data.
Out of Scope System Address rule.
Template Flight Type rule.

Starting the Business Rules Application

All aspects of Business Rules are managed through the Amadeus Alta
Administration user interface.
From the File menu, select Amadeus Business Rules. The system displays the
following menu:
Example: Alta Administration File Menu
The Amadeus Business Rules menu contains the following options:
Table: Reference to Menu Options Description
This Menu Option: Is Described in:
Market Management Managing Markets on page 9.

Rule Management Managing Rules on page 21.
Flight Group Management Managing Flight Groups on page 53.
Market History How to Display Market History on page 18.
Rule History Displaying Rule History on page 45.
Flight Group History How to Display Flight Group History on page 59.
6 Edition 8.5
Chapter 1 Introduction to Business Rules
Market Pair Rules

The rules stored and managed in Business Rules are generally based on the
market pair concept. Every rule has an origin and destination market as part of
the criteria that determine when the rule is applied.
Although rules are automatically applied to the appropriate data elsewhere in
Alta Departure Control, they can be overridden manually when required.
Markets
Markets themselves are also stored and managed in Amadeus Business Rules.
For more information, see Managing Markets on page 9.
Flight Groups
Flight Groups is an identification tool that you can use as part of market pair rule
management. A Flight Group allows you to create and apply the same rules to a
group of flights instead of creating and applying separate rules for each flight.
For information about managing Flight Groups in Amadeus Business Rules, see
Managing Flight Groups on page 53.

Chapter 2
Managing Markets
What Are Markets and Market Pairs?

Markets are groups of geographical elements that define a business-oriented
location. Markets can consist of different levels of geographical information.
A market pair is made up of an origin market and destination market.
You can use the following elements to define a market:
Airport
City
State and country
Country
Region
World
You can also exclude elements from a market. You may want to exclude a
specific country from the region you include in the market, for example, or
exclude a specific airport from a country.
You can only exclude an element if the market includes an element at a higher
geographical level. To exclude a country, for example, the region that includes
that country must be part of the market.
For a list of region codes, see Region Codes on page 375.
Examples of Market Definitions

Here are some examples of markets that could be defined.
Market Name Level Definition Explanation
OTHERFRANCE Country +FR-PAR All airports in country FR

and city except those in city PAR
LONDON Airport +LHR+LGW+LTN Airports LHR, LGW, and LTN
in city LON
AUSTL Region +AUSTL All airports in region AUSTL

Displaying Existing Markets

How to Display an Existing Market
1. Start Business Rules and select File > Market Management.
The Search Markets screen appears.
Example: Search Markets Screen
2. Enter your search criteria using the information in the following table.
You can search for all existing markets or specific markets only. For example,
you might want to display the markets containing a specific country code.
Table: Search Markets Fields
Field Explanation
Reference The 2-character code of the airline that owns the markets, which is
data airline your own airline. This field is mandatory.
Enter the airline code in this field and leave all the Search Option
fields blank to display all the markets belonging to your airline.
Application The name of the Amadeus application to be searched.
Select New Gen Inventory in the drop-down list to search for the
markets used in Automated SSR Handling rules.
This field is mandatory.
Name The name of the market. This field is optional.
You can also enter part of the name along with a wildcard character.
For example, FR* or TEST?.
Enter the market name in this field if you want to display a specific
market and you know at least part of the market name.
Element Specific elements that must be part of the market.
type and You can specify up to six elements as criteria for the market search.
code
Select the element type from the drop-down list in the Type field:
Airport or city, State, Country, Region, or World.
Enter the element code in the Code field.
Specify element criteria if you only want to display markets that
contain specific elements.
10 Edition 8.5
Chapter 2 Managing Markets
3. Click on Search.
The Market Management screen appears showing the existing markets that
match the criteria you specified.
Example: Market Management Screen
To change your search criteria, click on New Search in the Search Criteria
frame at the top of the screen.
How to Expand the Market Display

1. In the Market Management screen, expand a market by double-clicking on
the market name or the associated page icon.
Alternatively, click on the market name or icon, then click on Actions in the
application toolbar. Finally, click on Display.
The contents of the market are displayed on both the left and right sides of
the screen.

Example: Expanded Market Screen
2. To expand the market in the tree view on the left side of the screen only, click
on the market and then click on Expand below the tree view.
Whenever you expand a new market on the left side of the screen, a tab is
created on the right side. You can move between the markets that you
previously opened by clicking on the tabs.
How to Close the Market Display

To close a market or a level of detail in the Market Management screen:
Double-click on the folder icons as appropriate.
Alternatively, close all the markets that are currently expanded by clicking on
Collapse All below the tree view. This only affects the tree view on the left
side of the screen.
To close a tab on the right side of the Market Management screen:
Right-click on the tab and select the Close option for the tab.
You can close all the tabs by selecting the Close All option.
Creating Markets
How to Create a Market
1. In the Market Management screen, click on Actions in the toolbar, then click
on New.
Alternatively, click on New below the tree view.
2. In the Create Market screen, define the contents of the new market in the
available fields using the information in the following table.
12 Edition 8.5
Example: Create Market Screen
Table: Create Market Fields
Field Explanation
Name The unique name of the market.

Enter a name up to 15 characters in length and do not include
blank spaces or symbols.
Description The free-flow text description of the market.
This field is optional.
Element type You must include at least one element in the market.
and code In the Type field, select the type of element in the drop-down list:
Airport, City, State, Country, Region or World.
In the Code field, enter the airport, city, state, country, region, or
world code.
For a list of valid region codes and the regions they represent,
see Region Codes on page 375.
3. When you have entered a new market element type and code, click on
Include to add it to the market.
Example: New Market Including Two Country Elements

4. To exclude an element, enter the element type and code in the Type and
Code fields, then click on Exclude.
Example: New Market Excluding One Airport Element
5. To delete an element code that you have added, click on the element code,
then click on Delete.
You must delete all the element codes individually.
6. Click on Save.
How to Duplicate a Market

1. In the Market Management screen, select the market in the tree view.
2. Click on Actions in the toolbar, then click on Duplicate.
Alternatively, click on Duplicate below the tree view.
3. In the Duplicate Market screen, enter the name of the new market in the
Name field. You can also enter a description in the Description field.
Example: Duplicate Market Screen
14 Edition 8.5
4. The Elements field shows the contents of the market. Make the required
changes using the Type and Code fields and the Include and Exclude
buttons.
5. To delete an element code, click on the code, then click on Delete.
You must delete all the codes individually. When you delete the last code, the
element type is also deleted.
6. Click on Save.
Note: The contents of each market must be unique. If you did not make
any changes to the market contents, the system displays an error
message.
Updating Markets
How to Update a Market
You can modify the name, description, or contents of a market.
2. Click on Actions in the toolbar, then click on Update.
Alternatively, click on Update below the tree view.
3. In the Update Market screen, change the market name and description.
Example: Update Market Screen
For an explanation of the fields on this screen, see How to Create a Market
on page 12.
4. The Elements field shows the contents of the market. Make the required
changes using the Type and Code fields and the Include and Exclude
buttons.
5. To delete an element code, click on the element code, then click on Delete.
You must delete all the element codes individually. When you delete the last
code, the element type is also deleted.
6. Click on Save to update the market.

Example: Updated Market Screen
16 Edition 8.5
Deactivating and Reactivating Markets

If you want to delete an existing market, you cannot delete it immediately but you
can deactivate it.
Once a market is deactivated, it will be deleted automatically after a specific
number of days. The number of days depends on the systems current file
maintenance process. Before the number of days has passed, however, you can
reactivate the deactivated market.
Note: You cannot deactivate a market that is currently being used by existing
Amadeus Business Rules.
How to Deactivate a Market

1. In the Market Management screen, select the market to be deactivated in
the tree view.
2. Click on Actions in the toolbar, then click on Deactivate.
Alternatively, click on Deactivate below the tree view.
The system prompts you to confirm the deactivation.
Example: Deactivate Warning Message
3. Click on Yes to confirm.

The market appears greyed-out in the tree view of existing markets until it is
automatically deleted by the system. Deactivated markets appear below
active markets in the tree view.
Note: You can expand a deactivated market and display its contents, but
you cannot update or duplicate it.
How to Reactivate a Market

2. Click on Actions in the toolbar, then click on Reactivate.
Alternatively, click on Reactivate below the tree view.

How to Display Market History

1. From the Business Rules sub-menu, select Market History.
The Search Market History screen appears.
Example: Search Market History Screen
2. Enter the following information to search for market history:
Table: Search Market History Fields
Field Explanation
Reference data The 2-character code of the airline

airline
Application Select the application for which you want to view the market
history.
Market name Optionally, enter the name of the market.
Office ID/sign You can enter the office ID and sign of the office or person
that make the update. To do so, first click on the button on the
left of the Office ID field.
User You can enter the user ID and organisation of the person that
ID/organisation makes the update. To do so, first click on the button on the left
of the User ID field.
Start date Enter the start or end date of the search period in the format
End date DDMMMYY. For example, 15JUL04.
18 Edition 8.5
Field Explanation
Start time Enter the start time of the search period in the format HH:MM.
For example, 15:00.
End time Enter the end time of the search period in the format HH:MM.
For example, 23:59.
Constraint Select from the drop-down menu:
to display results that match the selected type.
to display results that exclude the selected type.
Type Select the type of entry history from the drop-down menu.
3. Click on Search to display the Market History for the criteria that you entered.

Chapter 3
Managing Rules
Overview of Market Pair Rules

Each market pair rule that is stored and managed in Business Rules consists of
the following:
Rule Owner
Rules cannot apply to all the airlines hosted by Amadeus Alta so each
market pair rule has an owner defined for it. All the rules which apply to other
areas of Alta are owned by the airline that maintains the Reference Data
and is therefore called the Reference Data airline. Through Security,
however, the Reference Data airline can allow another Alta-hosted airline to
maintain the market pair rules.
Client Application
Amadeus Business Rules is used to manage rules for more than one
application, such as Alta Inventory or Alta Departure Control.
Rule Type Group
The rule type group reflects the nature of the information contained in the
rule. Rules that are used for Customer Management are put in the Departure
Control Customer Management and Self-service Check-in groups.
Rule Type
The rule type is the actual purpose of the rule.
Rule Criteria
Each market pair rule type has a set of criteria which determines when it will
be applied. Some criteria are mandatory for the rule type while some are
optional. Generally, the more criteria that is defined for a rule, the more
specific the application of the rule will be. Only one rule of each type is
applied to a flight.
Rule Contents
The contents contain the information that is applied when the rule is called.

Application of Rules
In general, market pair rules are not defined at flight date level. Therefore, a
single rule can apply to a large number of flights. If there is only one rule of a
certain type, for example, for the market pair WORLD-WORLD, that rule applies
to all the flights that exist in the system. Due to the potential impact of market pair
rules, you should take great care when creating and updating rule criteria and
content.
When you save a new rule, or save updates to an existing rule, the changes are
applied the next time that the rule is called.
Rule Criteria Weight

Each rule includes a series of mandatory and optional criteria based on the
requirements and contents of the rule.
Typically, the airline code, and the market origin and destination, are mandatory
criteria, while the flight group, day of week, start date and end date are optional
criteria.
Optional Criteria Priority

Each optional rule criterion has a priority that the system uses to determine which
version of a rule to apply when there is more than one version that matches a
flight.
Each of the optional criteria is given a weight based on its priority and the number
of other optional criteria in the rule. The higher the priority, the higher the weight.
Certain criteria, such as Date begin and Date end, are considered as pairs with
a combined weight.
Image: Outbound Teletype Message Delivery Rule Criteria
The following table shows the weights used in the Outbound Teletype Message
Delivery rule.
Table: Outbound Teletype Message Delivery Rule Optional Criteria
Criteria Weight
Terminal 8
Flight group 4
Day of week 2
Date begin 1
Date end See Note below.
Terminal has the highest priority and weight, followed by Flight group, Day of
week, Date begin and Date end.
22 Edition 8.5
Chapter 3 Managing Rules
Date begin and Date end have the lowest priority and weight.
Note: Date begin and Date end are considered as a pair and have a
combined weight, in this example, of 1.
The rule that is applied when the market pair and the optional criteria of more
than one version of the rule matches a flight is the rule with the highest total
weight.
When you create a new version of a rule, the system checks to make sure that
the criteria do not overlap with an existing version of the rule for the same market
pair and with the same weight. If an overlap exists, you will not be able to create
the rule.
Market Pair Priority

If the optional criteria of more than one version of the rule have equal weight, the
system uses the most precise match between the market pair and the flight to
determine which rule is applied.
Because a market can consist of non-homogeneous elements such as countries
and airports, the system assigns a weight to each element type in order to
calculate the most precise match between origin market and origin of the flight
and between destination market and destination of the flight. The total weight of a
match between the market pair and the flight is determined by the sum of the
weights of the individual market matches. The rule that is applied is the rule with
the lowest weight.
The higher the priority of a match is, the lower its weight will be. A match between
an origin market containing an airport code and a flight departing from the same
airport, for example, is the most precise match possible and therefore has the
highest priority but the lowest weight (1).
Table: Market Element Weights, From Highest to Lowest Priority
Element Type Weight
Airport 1
City 2
Country and state 3
Country 4
Region 5
WORLD 6

Example of Weight
The following example illustrates how Business Rules matches the most precise
rule to a flight. Assume that the following three markets are defined:
Table: Markets (Example 1)
Market Name Market Contents
M1 FR
M2 EUROPE
M3 WORLD
Also assume that within the Customer Management rules, the following versions
of the Baggage Details Required rules are defined:
Table: Rules (Example 1)
Rule Criteria Rule Contents
Version 1
Market Pair M3-M1 Baggage Details Required
Flight No. Range 8X1-9 Hold: Weight
Day of Week 12345 Cabin: Weight
Version 2
Effective From/To dates Hold: Weight
25NOV09-31DEC09
Because different types of optional criteria are defined for each rule, the system
prioritises the rules according to the total weight of their optional criteria.
The first rule has flight group and frequency defined as optional criteria. Flight
group has a weight value of 4 and frequency has a weight value of 2. Therefore,
the total weight value of the criteria of the first rule is 6.
The second rule has only the Effective from and Effective to dates defined as
optional criteria, with a combined weight of 1.
Note: Effective from and Effective to are considered as a pair and have a
combined weight.
Comparing 6 and 1, the system determines that the first rule has greater weight.
Now assume that the following flight is created:
Table: Flight Period (Example 1)
Flight Information Type Flight Information
Departure airport SYD

Arrival airport CDG
Operating airline 8X
Flight number 8X3
Date range 01DEC-31DEC09
Frequency 12345
24 Edition 8.5
Both versions of the Baggage Details Required rule could apply to this flight
because the departure and arrival airports of the flight match both market pairs of
the rules. The system creates the flight with the contents of the version of the rule
with the greatest weight. Since version 1 of the rule has the greatest weight, the
system creates this flight as requiring hold baggage weights and cabin baggage
weights.
Example of Weight for Market Pairs

The following is an example to illustrate how Business Rules matches the most
precise rule to a flight when there is more than one rule with the same optional
criteria weight that matches the flight.
Assume that the following three markets are defined:
Table: Markets (Example 2)
Market Name Market Contents
M1 FR
M2 EUROPE
M3 WORLD
Also assume that within the Customer Management rules, the following versions
of the Baggage Details Required rule are defined:
Table: Rules (Example 2)
Rule Criteria Rule Contents
Version 1
Day of Week 12345 Cabin: Weight
Version 2
Day of Week 12345
Both rules have the flight group and frequency defined as optional criteria. Flight
group has a weight value of 4 and frequency has a weight value of 2. Therefore,
the total weight value of the criteria of both versions of the rule is 6.

Now assume that the following flight is created:
Table: Flight Period (Example 2)
Flight Information Type Flight Information
Departure Airport SYD

Arrival Airport CDG
Operating Airline 8X
Flight Number 8X3
Date Range 01DEC-31DEC09
Frequency 12345
Both versions of the Baggage Details Required rule could apply to this flight
because the departure and arrival airports of the flight match both market pairs of
the rules. Because the value of the optional criteria of both versions of the rule is
equal the system determines which version of the rule to use based on the
mandatory rule information (the carrier, market origin, and market destination.)
For the first version of the rule the market pairs WORLD to FR are used. WORLD
has a weight of 6 and FR has a weight of 4, so the total is 10.
For the second version of the rule, the market pairs are WORLD and EUROPE.
WORLD has a weight of 6 and EUROPE has a weight of 5, so the total weight
is 11.
For markets, the system selects the lowest weight to determine which version of
the rule to apply. Since version 1 of the rule has the lowest weight, the system
creates this flight as requiring hold baggage weights and cabin baggage weights.
26 Edition 8.5
Understanding Rule Content Windows

A rule content window is displayed after you click Search on the Search Rule
window.
If information exists for the rule you identified, that information is displayed on the
rule content window directly below the Search Criteria pane.
Image: Rule Contents Window
The top row of information in the Rule Criteria section of the window is selected
automatically.
If no information exists for the rule and for the options you identified, the following
error message is displayed:
Image: Warning Message When Rule Not Found

If you click Create or press Enter, the Create Rule window appears.
Image: Create Rule Window
Buttons on Rule Content Windows

Most of the buttons exist on all the rule content windows. If a button does not
exist on the rule content window for the specific rule, that action is not available
for that rule.
Table: Buttons In Rule Content Windows
Button Action
New Display the Create Rule window. In this window, you can add a row of
information for the rule you are currently working with.
Update Allow you to edit information for the row that is currently selected in the
rule criteria section of the rule content window. The top row is selected
automatically.
Duplicate Create a duplicate row of information based on the row that is currently
selected in the rule criteria section of the rule content window. You can
then edit the information to make any desired changes.
Delete Delete the currently selected row of information.
Note: Once you delete a row, it cannot be undone or restored. It
must be created again.
View market Display information for the Market origin and Market destination that
exists for the currently selected row. The view market button is enabled
when market is included in the rule criteria.
View flight Display flight usage data for the Market origin and Market
usage destination.
28 Edition 8.5
Button Action
Compare Open an additional Rule Contents pane at the bottom of the rule
Rule content window. The rule contents are displayed for the currently
selected row of information. Select the row you want to compare then
click the Compare rule button.
Close Allow you to close the rule contents pane.
New Search Display the Search Rule window and allows you to choose a different
rule to work with.

Menu Items
The following menu items are available to help you navigate through Business
Rules.
Table: Menu Items
Menu Items Sub-menu Items Action
Actions New Search Displays the Search Rule window and allows you
to choose a different rule to work with.
New Displays the Create Rule window. In this window,
you can add a row of information for the rule you
are currently working with.
Update Allows you to edit information for the row that is
currently selected in the Rule Criteria section of
the rule content window.
Duplicate Creates a duplicate row of information based on
the row that is currently selected in the rule criteria
section of the rule content window. You can then
edit the information to make any desired changes.
Delete Deletes the currently selected row of information.
Note: Once you delete a row, it cannot be
undone or restored. It must be created
again.
Export Table Allows you to copy the existing rule criteria rows
and use them in an external spreadsheet program.
Refresh Redisplays the current rule criteria information.
This is useful if more than one person is allowed to
modify the rules.
Display View Market Displays information for the market origin and
market destination that exist for the currently
selected row. The View market button is enabled
when market is included in the Rule Criteria.
View Flight Usage Displays flight usage data for the market origin
and market destination.
Compare Rule Opens an additional Rule Contents pane at the
bottom of the rule content window. The rule
contents are displayed for the currently selected
row of information. Select the row you want to
compare then click the Compare rule button.
Print Prints the list of rules returned that match the
search criteria. This is the table in the window you
are currently viewing.
History Displays a list containing information on who
created, modified and deleted rule content for the
rule you are currently working with.
30 Edition 8.5
Creating a Business Rule

How to Create a Business Rule
1. Open the rule type you want to work with.
This would be a business rule that you have roles and permissions to use.
Image: Flight Handling Type Rule Screen
2. Click on the New button or press Alt+N.

The Create Rule window is displayed. None of the fields contain information.
The required fields contain a Mandatory Field icon.
Image: Create Flight Handling Type Rule Screen
3. Complete all the mandatory criteria and any optional criteria that you want to
use as for the new rule.
Each criterion contains a weight, which is used to indicate which row of
information should be returned if two or more rows contain similar
information.
Note: In Flight Management, a higher number causes greater weight to be
given to the search criteria.

4. Enter a tag or label in the additional information panel, if required.

5. Complete the required rule contents fields.
Image: Create Flight Handling Type Rule Screen
6. Click on the Save button.

The application verifies that the new rule does not overlap an existing rule. If
there are errors, messages are displayed that identify the errors.
The rule is added to the table.
32 Edition 8.5
Updating Rules
How to Update a Rule
1. In the rule screen, select the rule you want to update from the list.
Image: SSR Standard Screen (Rule Selected for Update)
2. Click on Update.
Image: Update SSR Standard Screen
3. In the Update screen, make the required changes.

Image: Update SSR Standard Screen (Rule Content Amended)
Changed content
4. Click on Next.
The system verifies that the updated rule can be distinguished from other
rules by at least one criterion.
If there are problems, correct any identified errors, then click on Next again.
5. Click on Save.
Image: SSR Standard Screen (Rule Replaced)
Rule replaced with

updated rule
34 Edition 8.5
Deleting Rules
How to Delete a Rule
1. In the rule screen, select the rule you want to delete from the list. You can
delete more than one rule at a time.
- To select rules that are next to each other in the list, hold down the Shift
key and select the first and last rules you want to delete.
- To select rules that are separated by other rules in the list that you do not
want to delete, hold down the Ctrl key and click on each of the rules you
want to delete.
Image: SSR Standard Screen (Rule Selected for Deletion)
2. Click on Delete.
A confirmation message appears.
Image: SSR Standard Screen (with Deletion Confirmation Message)
3. If you want to continue with rule deletion, click on OK.

Exporting a Business Rule Table

How to Export a Business Rule Table
You can export a business rule table so you can use the information in a
spreadsheet.
1. Open the rule type.
This would be a business rule you want to export for which you have the
required roles and permissions to use.
Image: Flight Handing Type Rule Screen
2. Press Alt+A to open the Actions menu.
36 Edition 8.5
3. Press Alt+X to open the Save window.
4. Enter a file name.
5. Click the Save button.

The file is saved in My Documents because that is the folder shown in the
Save in drop-down. You can open the file in Microsoft Excel and update it
as you would any other spreadsheet.

Viewing the Market for a Business Rule

How to View the Market for a Business Rule
This would be a business rule you want to work with that you have roles and
permissions to use.
2. The top rule is selected by default. If you want to view the Market for a
different rule, select that rule.
3. Click the View Market button or press Alt+V.
The following window is displayed.
4. If you double-click the Market icon, it expands to provide details of the

market descriptor.
5. Click on OK to close this window.
38 Edition 8.5
Viewing Flight Usage for a Business Rule

How to View Flight Usage for a Business Rule
This would be a business rule you want to work with that you have roles and
permissions to use.
The top rule is selected by default. If you want to view flight usage for a
different rule, select that rule.
2. Click the View Flight Usage button or press Alt+I.
The following window is displayed.
You can use the scroll bar to view the additional flights that are impacted by
the rule that you selected.

3. Click on OK to close this window.
Comparing Rules
How to Compare Two Rules
1. In the rule screen, click on Compare rule.
The currently selected rule criteria and contents are displayed in a panel at
the bottom of the screen.
2. Select another rule from the list.
The lower pane remains frozen and the second rule is displayed above the
first.
Image: SSR Standard Screen (Rules Compared)
Contents of first rule selected Contents of second rule selected
You can visually compare the contents of two rules. The lower rule remains
until you close the Compare Rule pane.
If you click on Compare rule again, the lower pane is updated with the rule
criteria and contents of the currently selected rule. Both panes display the
same rule until you select another rule.
40 Edition 8.5
Duplicating Rules
How to Duplicate a Rule
1. In the rule screen, select the rule you want to duplicate from the list.
Image: SSR Standard Screen (Rule Selected for Duplication)
2. Click on Duplicate.
Image: Duplicate SSR Standard Screen

3. In the Duplicate screen, make any changes you require for your new rule.
Image: Duplicate SSR Standard Screen (Rule Criteria Changed)
Changed criteria Added criteria
4. Click on Next.
The system verifies that the new rule can be distinguished from other rules by
at least one criterion.
If there are problems, correct any identified errors, then click on Next again.
5. Click on Save.
Image: SSR Standard Screen (New Rule Added)
New rule added
42 Edition 8.5
Splitting Rules
Why Split Rules?
To create exceptions to a given rule, you can split it into multiple new rules that
will apply to different periods. These new rules can then be modified so their
content differs from the content of the initial rule.
How to Split a Business Rule

1. Display the rule you wish to split.
2. Click on Actions in the application toolbar and click on Split, or click on the
Split button at the bottom of the screen.
The Split Rule Management screen is displayed.
3. Choose the Split Criteria that define how the rule is to be split:
- By date range
Or:
- By frequency
4. Click on Next step.
The Define Split step is displayed.
5. If you chose to split the rule by date range:
a) Insert a new start and end date and click on Add to create a new date
range.
You can create up to 20 date ranges. For each date range that you
define, a new pending rule will be created. All date ranges must be
confined within the date range of the initial rule.
b) Click on Next.
In the Define New Rules Content step, you can see the list of date
ranges for which new pending rules have been created.
6. If you chose to split the rule by frequency:
a) Select one or more days of the week to the new split frequency and click
on Add.
For each frequency range that you define, a new pending rule will be
created.
b) Click on Next.
In the Define New Rules Content step, you can see the list of frequency
ranges for which new pending rules have been created.
7. Select a range and click on Update Content.
The corresponding pending rule is displayed and you can modify its content.

Image: Define New Rules Content Step in the Split Rule Management Screen
8. Click on Save.
The rule is redisplayed in the list of pending rules and flagged as modified.
9. Once you have updated the content of each pending rule as required, click
on Commit rules.
The system checks that none of the rules overlap before informing you that
the changes have been committed.
44 Edition 8.5
Displaying Rule History

How to Display Rule History
You can display Rule History by selecting Rule History from the Business
Rules sub-menu.
The Search Rule History screen appears.
Image: Search Rule History Screen
You can enter the following information to search for rule history.
Table: Search Rule History Fields
Field Explanation
Reference data airline The 2-character code of the airline.

Client application Select the application for which you want to view the rule
history.
Rule type group Select the rule type group.
Rule type You can select a specific rule that you want to display history
for, or select All to display the history for all the rules.

Field Explanation
Office ID/sign You can enter the office ID and sign of the office or person
that make the update. To do so, first click on the button to
the left of the Office ID field.
User ID/organisation You can enter the user ID and organisation of the person
that make the update. To do so, first click on the button to
the left of the User ID field.
Start date Enter the start date of the search period in the format
DDMMMYY. For example, 15JUL04.
End date Enter the end date of the search period in the format
DDMMMYY. For example, 15JUL04.
Enter the start time of the search period in the format
Start time
HH:MM. For example, 15:00.
Enter the end time of the search period in the format HH:MM.
End time
For example, 23:59.
Select from the drop-down menu:
Constraint to display results which match the selected type.
to display results which exclude the selected type.
Select the type of entry history from the drop-down menu.
Create
Type
Update
Delete
When you have finished, click on Search to display the Rule History for the
criteria that you entered.
46 Edition 8.5
Printing a List of Business Rules

How to Print a List of Business Rules
1. Display the rule you want to print.
2. Click the Print tab or press Alt+P.
The Print Preview window is displayed.
3. If you want to change your print options, click on the Setup button.
4. Click the Print button.
When the document prints, the rules appear in table form in the order they
are displayed on the window.

Searching for Business Rules

Many business rules have numerous versions of the rule based on the different
parameters in use.
It is possible to search for specific versions of a rule using the search facility.
When you log in to Rule Management, the Search Rule screen is displayed.
Image: Search Rule Screen
Table: Search Rule Screen Fields
Field Description
Reference The 2-character code of the airline or handling agency.

data airline
Application The rule application. Select from drop-down menu:
Amadeus Alta Departure Control.
New Gen Inventory.
PNR Push to Customs.
Rule type The type group to which the rule belongs. Select from drop-down
group menu.
The contents of the menu will depend on the application you select.
Rule type The name of the rule. Select from drop-down menu.
The contents of the menu will depend on the application and rule type
group you select. It will also depend on which rules are activated for
your airline or handling agency.
Criteria The criteria will depend on the selected rule.
If you leave the criteria fields blank and click on the Search button, all
versions of the selected rule will be displayed.
You can reduce the size of the response by entering some or all of the
known parameters.
The response will display any version of the rule which fit any of those
parameters.
48 Edition 8.5
Field Description
Additional Information
Tags Enter the unique tag (or label) of the rule. The application will display all
See below. rules with that tag.
Timestamp Start Enter the start date and time of your search window.
of last
update End Enter the end date and time of your search window.
See below.
Last updater Used ID or Enter the user ID or sign of the agent who performed
See below. sign the most recent update.
Office ID Enter the office ID of the agent who performed the most
recent update.
Organisation Enter the organisation of the agent who performed the
most recent update.
Timestamp of Last Update
Image: Timestamp of Last Update
Last Updater
Image: Last Updater
In this example, the user ID is DHUNT, the sign is 0914DH, the office ID is
LON1A0955 and the organisation is 1A.
Tags
It is possible to add a tag or label to a business rule. This will enable you to
display a group of business rules with a common tag or label.
Examples: Summer, Winter, Domestic, International.

Image: Business Rules With a Tag
Image: Business Rules Search With a Tag
In this example, the tag FRANCE has been found in two versions of the rule.
50 Edition 8.5
Verifying the Business Rules for Flight

Management
How to Verify Business Rules
When working with Flight Management rules, the Departure Plan Simulation
window allows you to:
Enter departure plan criteria to simulate the creation of the departure plan
based on the specified criteria.
View the departure plan data retrieved by the business rules associated with
the entered departure plan criteria.
Departure Plan Simulation is a separate application. For more information, see
Departure Plan Simulation on page 365.
Note: The final validation of the business rule content occurs when the
business rule is applied.

Chapter 4
Managing Flight Groups
A Flight Group is one or more flights or flight ranges identified by a single

keyword.
Flight Groups are used as criteria for the application of market pair rules. A Flight
Group allows you to create and apply the same rules to a group of flights instead
of creating and applying separate rules for each flight.
This section explains how to manage the Flight Groups that you create and
maintain in Reference Data.
Displaying Existing Flight Groups

How to Display an Existing Flight Group
1. Start Amadeus Business Rules and select File > Flight Group
Management.
The Search Flight Groups screen appears.
Example: Search Flight Group Screen
2. Enter your search criteria using the information in the following table.
You can display all the flight groups or specific flight groups only. You might
want to display the flight groups containing a specific flight number range, for
example.

Table: Search Flight Group Fields
Field Explanation
Reference data airline The 2-character code of the airline that owns the
markets, which is your own airline.
Enter the airline code in this field and leave the Flight
group keyword and Flight range fields blank to display
all the markets belonging to your airline.
Application The name of the Amadeus application to be searched.
Select New Gen Inventory in the drop-down list to
search for the markets used in Automated SSR Handling
rules. This field is mandatory.
Flight group keyword The name of the flight group.
Enter the flight group name in this field if you want to
display a specific flight group.
Flight range The 2-character airline code and flight number range.
These fields are optional.
Specify these fields if you want to display flight groups
that contain a specific flight number or flight number
range.
3. Click on Search.
The Flight Group Management screen appears showing the existing flight
groups that match the criteria you specified.
Example: Flight Group Management Screen
54 Edition 8.5
Chapter 4 Managing Flight Groups
The Flight Group table contains the following information:
Table: Flight Group Table Columns
Column Heading Explanation
Flight Group Keyword The name of the flight group.

Flight Ranges The flights or flight ranges contained in the flight
group.
To change your search criteria, click on New Search in the Search Criteria
frame at the top of the screen.
Creating Flight Groups

How to Create a Flight Group
1. In the Flight Group Management screen, click on Actions in the toolbar,
then click on New.
Alternatively, click on New at the bottom of the screen.
2. In the Create Flight Group screen, define the contents of the new flight
group in the available fields using the information in the following table.
Example: Create Flight Group Screen
Table: Create Flight Group Fields
Field Explanation
Reference data airline The 2-character code of the airline that owns the flight
groups, which is your own airline.
Flight group keyword The name of the Amadeus application to be searched.
Select New Gen Inventory in the drop-down list to
search for the flight groups used in Automated SSR
Handling.
Flight group description The free-flow text description of the flight group.

Field Explanation
Flight range You must include at least one flight or flight range in
the flight group.
In the first field, enter the airline code of the flight or
flight range you want to include.
In the second field, enter the flight number or the flight
number range.
3. When you have entered a new flight number or flight range, click on Include
to add it to the flight group.
The flights appear in the Flight Group Contents field.
Example: New Flight Group Containing a Single Flight Range
4. To delete a flight or flight range that you have added, click on it, then click on
Delete.
5. Click on Save.
Example: List of Flight Groups in the Flight Group Management Screen
56 Edition 8.5
Updating Flight Groups

How to Update a Flight Group
1. In the Flight Group Management screen, select the flight group from the list
of flight groups.
2. Click on Actions in the toolbar, then click on Update.
Alternatively, click on Update at the bottom of the screen.
3. In the Update Flight Group screen, make the required changes.
Example: Update Flight Group Screen
- To change the description, enter the new information in the Flight group
description field.
- To delete a flight or flight range, click on it in the Flight group content
field, then click on Delete.
- To add a flight or flight range to the flight group, enter the information in
the Flight range fields, then click on Include.
For an explanation of the fields on this screen, see How to Create a Flight
Group on page 55.
Note: The name in the Flight group keyword field appears greyed out
because you cannot change this information. If you want to change
the flight group name, you must create a new flight group.
4. Click on Save to update the flight group.
Note: If you added a flight range to the flight group, the market pair rules
that apply to the flight group are applied automatically to the new
flight range.

How to Delete a Flight Group

1. In the Flight Group Management screen, select the flight group you want to
delete.
You can only delete a flight group if it is not currently in use. If there are
existing Amadeus business rules that apply to a flight group, you cannot
delete it.
2. Click on Actions in the toolbar, then click on Delete.
Alternatively, click on Delete at the bottom of the screen.
- If there are no rules that currently apply to the flight group, it is deleted
and removed from the list of flight groups on the Flight Group
Management screen.
- If there are market pair rules that currently apply to the flight group you
are trying to delete, the system does not delete the flight group and
displays a warning message that indicates which rules apply to the
group.
58 Edition 8.5
How to Display Flight Group History

1. From the Business Rules sub-menu, select Flight Group History.
The Search Flight Group History screen appears.
Example: Search Flight Group History Screen
2. Enter the following information to search for flight group history.
Table: Search Flight Group History Fields
Field Explanation
Reference data airline The 2-character code of the airline.

Client application Select the application for which you want to view the
flight group history.
Flight group name Optionally, enter the name of the flight group.
Office ID/Sign You can enter the office ID and sign of the office or
person that make the update. To do so, first click on
the button to the left of the Office ID field.
User ID/Organisation You can enter the user ID and organisation of the
person that makes the update. To do so, first click on
the button to the left of the User ID field.

Field Explanation
Start date Do one of the following:

End date Enter the start or end date of the search period in
the format DDMMMYY. For example, 15JUL04.
Click on the calendar icon to select a specific date
from the calendar.
Select Today or Open from the drop-down menu.
Start time Enter the start and end times of the search period in
End time the format HH:MM, for example 15:00.
Constraint Select from the drop-down menu.

to display results which match the selected type
to display results which exclude the selected
type
Type Select the type of entry history from the drop-down
menu:
Create
Update
Delete
3. Click on Search to display the Flight Group History for the criteria that you
entered.
60 Edition 8.5
Chapter 5
Mandatory Rules
The mandatory rules required for a flight depend on whether the flight is a Flight
Management (Weight and Balance) or a Customer Management (Check-In) flight.
Table: Mandatory Flight Management Rules for Weight and Balance
Rule Notes Does Flight

Create Fail if
Rule is Missing
or Incorrect?
Aircraft Basic Weight Name Rule on Mandatory for Basic Weight type flights if Yes
page 70. more than one Aircraft Basic Weight name
exists in DBM for the registration.
Aircraft Maximum Weights Name Rule Mandatory if more than one Max Weights Yes
on page 76. name exists in DBM for the subtype or
registration.
Baggage Type Rule on page 214. Mandatory. Yes
Baggage Weights Rule on page 81. Mandatory if more than one Bag Weights Yes
category exists in DBM for the carrier.
Carrier/Aircraft Subtype Rule on page Mandatory. Yes
87. However, if the aircraft registration is
received from Alta Inventory, the subtype
is identified from the aircraft registration in
DBM.
Carrier/Aircraft Subtype Fitted Interior Mandatory if more than one fitted interior Yes
Rule on page 84. for the subtype and ACV exists in DBM.
Crew Baggage Weights Rule on page Mandatory for Basic Weight type flights. No
90. If missing, no crew baggage commodity is
created for the flight.
Crew Distribution Rule on page 95. Mandatory for Basic Weight type flights. Yes
Crew Weights Rule on page 99. Mandatory for Basic Weight type flights. Yes
Document Type Facility Routing Rule Mandatory to direct messages and No
on page 243. documents to the correct recipients.
Domain Rule on page 248. Mandatory. Yes
Dry Operating Weight Name Rule on Mandatory for Dry Operating Weight type Yes
page 105. flights.
Flight Handling Type Rule on page Mandatory. Yes
268.

Rule Notes Does Flight

Create Fail if
Rule is Missing
or Incorrect?
Fuel Standard Distribution Name Rule Mandatory if more than one Fuel Standard No if data exists
on page 136. Distribution - Ramp Fuel name exists in in DBM.
DBM for the subtype. Yes if data in the
rule is invalid.
IATA Service Type Rule on page 276. Mandatory, but flights default to the No
passenger service type (J) if no rule is
present.
Pantry Code Rule on page 155. Mandatory for Basic Weight type flights. Yes
Passenger Gender Type Weights Rule Mandatory. Yes
on page 325.
Passenger Weights Rule on page 148. Mandatory. Yes
ULD Capacity Rule on page 351. Mandatory to process a Weight and No, but baggage
Balance flight correctly. commodities are
created as bulk
during Capacity
Calculation.
Taxi Fuel Rule on page 181. Mandatory if more than one Taxi Fuel No, but the taxi
category exists in DBM for the carrier. fuel is set to
zero.
Template Flight Type Rule on page Mandatory. Yes
349.
Note:
The following Flight Management rules are mandatory for Check-In Only flights:
Baggage Type Rule on page 214.
Flight Handling Type Rule on page 268.
Template Flight Type Rule on page 349.
The IATA service type is mandatory for a check-in only flight, but defaults to the
passenger service type (J) if the IATA Service Type Rule on page 276 is missing.
62 Edition 8.5
Chapter 6
Ground Handling Rules
Rules in a Ground Handling Solution

Alta Ground Handling enables a ground handling organisation or airline (called
the ground handler) to provide ground handling services on behalf of the
operating carrier.
In a ground handling solution, the business rules related to engineering and
aircraft data are set up and called from the reference data of the operating airline.
These rules must be created and maintained by the operating airline.
Operational-related rules, however, are called from the reference data of the
ground handling organisation (ground handler or handling airline).
Mandatory Rule for Ground Handling

The Ground Handling Rule on page 66 is mandatory in a ground handling
solution. This rule is called from the reference data of the operating airline.
Handling Organisation Business Rules

The following rules, when defined, are called from the reference data of the
ground handling organisation. If the rule is not defined in the reference data of the
handling organisation, the default system behaviour applies.
Aircraft Limitations Message Priority Rule on page 72.
Autoload Bulk Mixing Rule on page 193.
Autoload Distribution Options Rule on page 196.
Baggage Segregation Rule on page 207.
Baggage Statistics Override Rule on page 212.
Cargo Delivery Sequence Rule on page 216.
Commodity Conversion Threshold Rule on page 219.
Deadload Uplift Offload Message Parameter Selection Rule on page 225.
Document Type Facility Routing Rule on page 243.
Domain Rule on page 248.
Note: Special restrictions apply. See The Domain Rule in a Ground
Handling Solution on page 248.

Dry Operating Weight Change on page 102.

Equipment Configuration Rule on page 254.
Express Cargo Commodity Rule on page 257.
Final Fuel Release Rule on page 111.
Flight Departure Minimum Status Required Rule on page 263.
Flight Event Notification Data Rule on page 266.
Forecast ZFW Change Rule on page 119.
Forecast ZFW Calculation Rule on page 113.
Forecast ZFW Dependency Rule on page 271.
Fuel Change Tolerance Rule on page 127.
Fuel Density Rule on page 129.
Fuel Density Update Rule on page 131.
Fuel Reduction Rule on page 133.
Fuel Status Rule on page 140.
Ground Handling Document Format Rule on page 274.
Ideal Trim Area Rule on page 142.
Inhibit ACARS Preliminary Loadsheet Creation Rule on page 278.
Inhibit Approval of Distribution Rule on page 281.
Inhibit EOP Creation Rule on page 284.
Inhibit Final Loadsheet Creation Rule on page 287.
Inhibit Load Instruction Report Creation Rule on page 290.
Inhibit Provisional Loadsheet Creation Rule on page 293.
Last Minute Change Threshold Limits Rule on page 295.
Loadsheet Tolerance Rule on page 145.
Manual Last Minute Change Rule on page 300.
Notification Priority Rule on page 305.
NOTOC Emergency Number Rule on page 309.
Out of Scope System Address Rule on page 322.
Outbound Teletype Message Delivery Rule on page 315.
Outbound Teletype Message Originator Rule on page 319.
Parallel Run Rule on page 324.
Process External Cargo Feed Message Rule on page 327.
Radio Frequency Rule on page 332.
Ramp Final Clearance Rule on page 334.
Ramp Tolerance Limits Rule on page 176.
Shift Summary Layout Rule on page 339.
Supplementary Information Rule on page 346.
WWF Limits Rule on page 360.
64 Edition 8.5
Chapter 6 Ground Handling Rules
WWF Override Rule on page 363.
ALL in the Operating Carrier Field

When a ground handling organisation works with multiple operating airlines, the
value ALL can be entered into the Operating Carrier field of certain business rules
to simplify the rule creation process.
This applies to the following rules:
Domain Rule on page 248.
Ground Handling Document Format Rule on page 274.
Operating Airline Business Rules

All Flight Management business rules not listed in Handling Organisation
Business Rules on page 63 are called from the reference data of the operating
airline, and must be set up and maintained by the operating airline.

Ground Handling Rule
Activation is required for this feature.
Rule Description
This rule determines which ground handling organisation or airline is responsible
for the ground handling an airline's flights. It is created by the operating airline,
and indicates which ground handling organisations it works with.
This rule is mandatory for a ground handling solution.
Related Rules
This rule works in conjunction with the Ground Handling Document Format Rule
on page 274, which determines the document format to be used for a ground
handled flight.
Rule Criteria
Table: Ground Handling Rule Criteria
Field Weight Explanation
Operating
0 The two-character carrier code.
Carrier
Market Origin 0 The market of the flight origin. Mandatory.
Market
0 The market of the flight destination. Mandatory.
Destination
Flight No.
Range 0 To specify the flight number range, click on and select
the Flight Group Keyword or the Flight Range.
Outbound The departure airport terminal where the document is
32
Terminal routed.
Aircraft The aircraft subtype, for example, 747-438ER.
16
Subtype
Registration The registration number of the specific aircraft, for
8
example, 6X-XYZ.
Day of Week The days that this row applies to, such as 12 (for Monday
4
and Tuesday).
STD From The starting and ending standard time of departure in the
2 format HH:MM.
STD To
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
66 Edition 8.5
Chapter 6 Ground Handling Rules
The following rule content window is displayed, based on the search criteria:
Indicates where the rule is stored in this case, the reference data of operating
airline 8Z.
Rule Contents
Table: Ground Handling Rule Contents
Field Explanation
Handling Organisation The two-character code of the ground handling organisation

or carrier.
Example Business Rule

In the following rule, operating airline 8Z defines ground handling organisation 6X
for all of its flights departing from Nice airport.
Impact on Flight Management

Authorised users in the 6X ground handling organisation can perform Flight
Management activities on 8Z flights departing from NCE airport provided that
the flights are part of the agent's active domain, and according to the roles and
permissions delegated to them by airline 8Z in Amadeus Security Management.

Chapter 7
Engineering Rules
Information about the Engineering Rules is included in this section. For general
information about starting the Business Rules application and using the menus
and buttons, see Understanding Rule Content Windows on page 27.

Aircraft Basic Weight Name Rule

Note: For an add middle stop disruption (when flight leg AAA-BBB becomes
AAA-XXX-BBB) this business rule is not called for the newly created
flight leg (XXX-BBB). The data from the original flight leg (AAA-BBB) is
used instead.
Rule Description
This mandatory rule is used for basic weight operating type flights, and
determines which basic weight schedule to use for the registration when more
than one exists in DBM.
The aircraft basic weight name must match exactly the name stored in the
Carrier & Aircraft > General > Aircraft Information tab, at the registration level,
to work correctly in Flight Management.
Example: Carrier & Aircraft > General > Aircraft Information Tab in DBM
(Registration Level)
Rule Criteria
Table: Aircraft Basic Weight Name Rule Criteria
The two-character code for the operating airline.

Carrier 0
Mandatory.
The aircraft subtype, as defined in DBM.
Carrier/Aircraft Subtype 0
Mandatory.
To specify the flight number range, click on

Flt No Range 2 and select the Flight Group Keyword or the Flight
Range (s).
70 Edition 8.5
Chapter 7 Engineering Rules
The registration number of the specific aircraft, for

Registration 1
example, 6X-NLA.
Rule Contents
Table: Aircraft Basic Weight Name Rule Contents
Field Explanation
Aircraft Basic The Aircraft Basic Weight name. Mandatory.

Weight Name The name must match exactly the Aircraft Basic Weight name
stored in DBM in the Carrier & Aircraft > General > Flight
Information tab at the registration level.

Aircraft Basic Weight Name - 'Basic Weight' for all 6X flights operated by subtype
74E and registration 6X-NLA.

The Flight Information screen for 6X117 displays the basic weight schedule for
6X-NLA (179400 / 590.00) stored in DBM for the selected Aircraft Basic Weight
Name.

Aircraft Limitations Message Priority Rule
Rule Description
This optional rule is used to determine the priority of notification messages sent to
the load controller when weight and balance limits stored in DBM are exceeded,
or when weight and balance limitation buffers are exceeded.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
The limits and limit buffers are stored in DBM, in the following tabs:
Carrier & Aircraft > Limits > Max Weights.
Carrier & Aircraft > CG Data > Centre of Gravity.
Carrier & Aircraft > CG Data > WT/CG Limit Buffer.
Example: Carrier & Aircraft > Limits > Max Weights Tab in DBM
Example: Carrier & Aircraft > CG Data > Centre of Gravity Tab in DBM
72 Edition 8.5
Example: Carrier & Aircraft > CG Data > WT/CG Limit Buffer Tab in DBM
Rule Criteria
Table: Aircraft Limitations Message Priority Rule Criteria
Mandatory.
Operating Carrier 0
The two-character carrier code.
Mandatory.
Market Origin 0
The market of the flight origin.
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 32 The aircraft subtype, as defined in DBM.
Aircraft
16
Registration
2 format HH:MM.
STD To
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Flight No. Range
8 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Ranges.
4
and Tuesday).

Rule Contents
Table: Aircraft Limitations Message Priority Rule Contents
Field Explanation
Display warning on flight Select if a warning icon is to be displayed on the flight tile
tile when limits exceeded when the weight and balance limits are exceeded.
Display warning on flight Select if a warning icon is to be displayed on the flight tile
tile when buffer limits when the buffer limits defined in the Carrier & Aircraft >
breached CG Data > WT/CG Limit Buffer tab in DBM are breached.
Priorities Select from the drop-down menu for each field.
None
Low
Medium
High
Very High
Priorities structural weights exceeded
(Message) Priority when The message priority if the weight and balance limits are
Limit Exceeded at 'LO' exceed, at each load control status.
(Message) Priority when
Limit Exceeded at 'LL'
Limit Exceeded at 'LC'
Limit Exceeded at 'LF'
Limit Exceeded at 'LSF'
Priorities WT/CG buffer limits exceeded
(Message) Priority when The message priority if the buffer limits defined in the
WT/CG Buffer Limit Carrier & Aircraft > CG Data > WT/CG Limit Buffer tab
Breached at 'LO' of DBM are breached, at each load control status.
WT/CG Buffer Limit
Breached at 'LL'
WT/CG Buffer Limit
Breached at 'LC'
74 Edition 8.5
Field Explanation

WT/CG Buffer Limit
Breached at 'LF'
WT/CG Buffer Limit
Breached at 'LSF'
For all 6X World Market flights operating with aircraft subtype 74K the message
priority is set for each Load Control status.

The warning icon is displayed on the flight tile.
A tooltip is displayed by hovering over the warning icon.
If the message is sent with very high or high priority, a warning message is
displayed.

Aircraft Maximum Weights Name Rule

Rule Description
This mandatory rule determines which aircraft maximum weights schedule to use
for a subtype or a registration when more than one exists in DBM.
The aircraft maximum weights name must match exactly the name stored in the
Carrier & Aircraft > Limits > Max Weights tab, at the subtype or registration
level, to work correctly in Flight Management.
Example: Carrier & Aircraft > Limits > Max Weights Tab
This rule sets the Aircraft Weights Name indicator in the Departure Plan Data
panel of a departure plan simulation. See Departure Plan Simulation on page
365.
Rule Criteria
Table: Aircraft Maximum Weights Name Rule Criteria
Carrier 0 The two-character carrier code. Mandatory.

Market
Destination
Carrier/Aircraft
0 The aircraft subtype, as defined in DBM. Mandatory.
Subtype
Registration 32
example, 6X-XYZ.
Flight No. To specify the flight number range, click on and

16
Range select the Flight Group Keyword or the Flight Range (s).
The days that this row applies to, such as 12 (for Monday
Day of Week 8
and Tuesday).
76 Edition 8.5
Select from the following code:

LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
2
STD To format HH:MM.
1
Example: Aircraft Maximum Weights Name Rule
Rule Contents
Table: Aircraft Maximum Weights Name Rule Contents
Field Explanation
Aircraft Maximum The Aircraft Maximum Weights name.

Weights Name The name must match exactly the Aircraft Maximum Weights name
stored in DBM in the Carrier & Aircraft > Limits > Max Weights
tab at the subtype or registration level.
Mandatory.

Aircraft maximum weights name 'STD' for 6X World market flights for subtype
74E with registration 6X-NLA.


The Fuel screen for 6X117 displays the STD option for the Max Operating
Weights stored in DBM for the selected Aircraft Maximum Weights Name.
78 Edition 8.5
Aircraft Schedule Rule
Rule Description
This rule is used to determine the onward or return flight number to be operated
by a departing flight.
Related Rules
This rule is used in conjunction with the following rules, to determine the onward
flight number associated with a departing flight:
Pantry Food Content No Uplift Rule on page 158.
Pantry Food Content Weight Rule on page 161.
Potable Water No Uplift Rule on page 166.
Potable Water Weight Rule on page 169.
Rule Criteria
Table: Aircraft Schedule Rule Criteria
Operating Carrier 0 The two-character carrier code.

Mandatory.
Market Origin 0
Market Mandatory.
0
Mandatory.
Flight No. Range 0
The flight numbers of the departing flights.
Aircraft Subtype 0 The aircraft subtype, as defined in DBM. Mandatory.
Registration 2
1 format DDMMMYY.
Effective To

Rule Contents
Table: Aircraft Schedule Rule Contents
Field Explanation
Onward Flight Number The flight number of the onward or return flight.
The day difference indicator. Select from drop-down
menu:
Number of Days Difference
In this example, flight 9S123, when operated by aircraft subtype 733, also
operates the 9S124, which departs on the following day (+1).

When used in conjunction with the Pantry Food Content Weight rule and the
Pantry Food Content No Uplift rule, flight 9S123 will also uplift food for flight
9S124.
80 Edition 8.5
Baggage Weights Rule

used instead.
Rule Description
This mandatory rule determines the baggage weights category to be used for a
pieces-only flight, when more than one category exists in DBM for the carrier.
The baggage weights category name must match exactly the name stored in the
Carrier > General >Bag Weights tab, to work correctly in Flight Management.
Example: Carrier > General > Bag Weights Tab in DBM
Related Rules
This rule works in conjunction with the Baggage Type rule if the PO (Pieces Only)
option is required.
The Baggage Type rule determines whether the baggage option to be used for a
flight is PO (Pieces Only) or PW (Pieces and Weight). See Baggage Type Rule
on page 214.
The Baggage Weights rule determines the baggage weights category to be used
for a pieces-only flight when more than one category exists in DBM for the carrier.
Rule Criteria
Table: Baggage Weights Rule Criteria

Market
Destination
Crew Owner 64 Crew owner airline code.


LH - Long-haul
SH - Short-haul
Template Flight
32 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range 16 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range (s).
Registration 8
example, 6X-XYZ.
Carrier/Aircraft
4 The aircraft subtype, as defined in DBM.
Subtype
The days that this row applies to, such as 12 (for
Day of Week 2
Monday and Tuesday).
1
Rule Contents
Table: Baggage Weights Rule Contents
Field Explanation
Weights The Weights Category name.

Category The name must match exactly the name stored in DBM in the
Carrier > General > Bag Weights tab. Mandatory.
82 Edition 8.5

Weights category STD BAG for world market flights for carrier 6X.

Baggage weights based on STD BAG weight set per class.
Example: Flight Management - Planned Baggage Panel

Carrier/Aircraft Subtype Fitted Interior Rule

Rule Description
This mandatory rule is required if more than one fitted interior exists for an aircraft
subtype and when there is no registration supplied by Alta Inventory, or the
supplied registration does not exist in FM. If an aircraft registration is present, the
fitted interior of the registration is applied and this rule is not required.
The fitted interior name must match exactly the name stored in the Carrier &
Aircraft > Fitted Interior > General tab in DBM to work correctly in Flight
Management.
Example: Carrier & Aircraft > Fitted Interior > General Tab in DBM
This rule sets the Fitted Interior indicator in the Departure Plan Data panel of a
departure plan simulation. See Departure Plan Simulation on page 365.
Related Rules
This rule works in conjunction with the Carrier/Aircraft Subtype Rule on page 87
to establish the correct aircraft subtype and fitted interior for a flight.
The Carrier/Aircraft Subtype rule establishes the subtype, and the Carrier/Aircraft
Subtype Fitted Interior rule establishes the Fitted Interior.
Rule Criteria
Table: Carrier/Aircraft Subtype Fitted Interior Rule Criteria

Market
Destination
Carrier/Aircraft
Subtype
The three-character Aircraft Configuration Version.
ACV 0
Mandatory.
The fitted configuration in each class. For example,
Fitted Config 0
P14J64Y265. Mandatory.
84 Edition 8.5

Day of Week 2
1
Rule Contents
Table: Carrier/Aircraft Subtype Fitted Interior Rule Contents
Field Explanation
Fitted Interior The Fitted Interior name.

Name The must match exactly the Fitted Interior name stored in DBM in
the Carrier & Aircraft > Fitted Interior > General tab. Mandatory.

Fitted interior name '14F/70J/30W/177M' for 6X World market flights operated by
subtype 74E.


The Flight Information screen for 6X117 displays the Fitted Interior stored in DBM
for the selected Fitted Interior Name.
86 Edition 8.5
Carrier/Aircraft Subtype Rule

Rule Description
This mandatory rule is required to determine the aircraft subtype to be applied for
a flight when there is no registration supplied by Alta Inventory, or the supplied
registration does not exist in FM.
This carrier/aircraft subtype must match exactly the Aircraft Subtype code that
exists in DBM in the Carrier & Aircraft > General > Aircraft Information tab, to
work correctly in Flight Management.
Example: Carrier &Aircraft > General > Aircraft Information Tab in DBM
This rule works in conjunction with the Carrier/Aircraft Subtype Fitted Interior rule
and links a fitted interior to a subtype.
Related Rules
This rule works in conjunction with the Carrier/Aircraft Subtype Fitted Interior rule
to establish the correct aircraft subtype and fitted interior for a flight. See
Carrier/Aircraft Subtype Fitted Interior Rule on page 84.
The Carrier/Aircraft Subtype Fitted Interior rule establishes the fitted interior, and
The Carrier/Aircraft Subtype rule establishes the subtype.

Rule Criteria
Table: Carrier/Aircraft Subtype Rule Criteria
Carrier 0 The two-character carrier code.

The Aircraft Type code, taken from the relevant ACV for
Aircraft Type 0 the aircraft, as defined in Alta Inventory. Example 74A.
Mandatory.
Market
Destination
ACV 32 Aircraft Configuration Version.
Flight No. To specify the flight number range, click on and select
16
Range the Flight Group Keyword or the Flight Range (s).
The fitted configuration in each class. For example,
Fitted Config 8
P14J50Y315.
Day of Week 4
and Tuesday).
Effective
From The starting and ending effective date of this row in the
2
format DDMMMYY.
Effective To
1
STD To format HH:MM.
Rule Contents
Table: Carrier/Aircraft Subtype Rule Contents
Field Explanation
Aircraft Subtype The Aircraft Subtype code to use for this row.
This must match exactly the Aircraft Subtype code that exists in
DBM in the Carrier & Aircraft > General > Aircraft Information
tab.
Mandatory.
88 Edition 8.5

Aircraft subtype 74E for 6X World market flights operated by type 744 with fitted
config of F14J70W30M177.

The Flight Information screen for 6X117 displays the Aircraft Subtype stored in
DBM for the selected Aircraft Subtype code.

Crew Baggage Weights Rule

used instead.
Rule Description
This mandatory rule is required when crew baggage is to be considered for the
flight. However, if an applicable rule does not exist, the flight is created without
crew baggage.
The Crew Baggage Weights categories are stored in DBM in the Carrier >
General > Crew Baggage Weights tab.
Example: Carrier > General > Crew Baggage Weights Tab in DBM
The Bulk/ULD locations are stored in DBM in the Carrier & Aircraft > Holds >
Holds Summary tab.
Example: Carrier & Aircraft > Holds > Holds Summary Tab in DBM
90 Edition 8.5
Related Rules
This rule works in conjunction with the Crew Distribution Rule on page 95 to
determine the weight of crew baggage carried on a flight.
The Crew Distribution rule determines the number of crew on a flight, and the
Crew Baggage Weights rule determines the number of pieces and weight of
baggage for each crew member.
Rule Criteria
Table: Crew Baggage Weights Rule Criteria
Operating Carrier 0 The two-character carrier code. Mandatory.

Market
Destination
Crew Owner 16 Two-character code of the crew owner.

LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
1

Rule Contents
Table: Crew Baggage Weights Rule Contents
Field Explanation
Crew Bag Category Mandatory.

Enter the Crew Bag Category name.
The name must match exactly the Crew Baggage
Weights name stored in DBM in the Carrier > General
> Crew Baggage Weights tab.
Loading Type Select the loading type for the crew bags:
Bulk (default)
Crew Baggage ULD
Crew Baggage BARROW

With Crew - bags will be loaded in the cabin.
Baggage ULD
Baggage BARROW
Location Optional.
Enter the specific aircraft location for the crew bags.
Example: 44R.
Commodity If the loading type is set to Baggage ULD or Baggage
BARROW, the Commodity field is mandatory.
It determines which baggage sub-commodity the crew
baggage is included in.
Example: Enter J to include the crew baggage in
commodity BJ.
92 Edition 8.5
If activated, the Rule Content panel displays the following additional fields.
Table: Additional Crew Baggage Weights Rule Contents
Field Explanation
Receive Crew Baggage from Crew baggage that is accepted from the check-in
Check-in System system is processed and added to the crew baggage
rest location.
Create Zero Weight Crew A zero-weight and pieces crew baggage rest location
Baggage Commodity is created at flight creation.
You can only select this field if Receive Crew
Baggage from Check-in System is selected.
Crew Baggage Included in For basic weight operating type flights, crew baggage
Traffic Load is included in the traffic load instead of the dry
operating weight/dry operating index (DOW/DOI).

The crew bags number of pieces and weight are defined in DBM under the name
LONGHAUL.
The crew baggage commodity D is located in bulk hold 52.


The DOW Crew window in Flight Management shows crew baggage weights of
240 Kgs (20 pieces x 12 Kgs), based on the LONGHAUL crew baggage weights
category in DBM, which defines one bag of 12 Kgs per crew member.
When the rule defines that crew baggage is received from the check-in system.
In the Passenger window, crew baggage is displayed as accepted baggage in

the Crew column on the Baggage table.
Example: Accepted Baggage on the Passenger Window
Crew baggage weight is added to the Crew Baggage commodity as it is received

from the check-in system.
94 Edition 8.5
Crew Distribution Rule

used instead.
Rule Description
This mandatory rule determines the number of technical and cabin crew on board
a flight. It is required when more than one crew distribution exists for a fitted
interior.
The Crew Distributions stored in DBM in the Carrier & Aircraft > Fitted Interior
> Crew Distribution tab determine where the crew will be seated.
Example: Fitted Interior > Crew Distribution Tab in DBM
Related Rules
This rule works in conjunction with the Crew Baggage Weights rule to determine
the weight of crew baggage carried on a flight. See Crew Baggage Weights Rule
on page 90.
The Crew Baggage Weights rule determines the weight of baggage for each crew
member and the Crew Distribution rule determines the number of crew on a flight.
This rule also works in conjunction with the Crew Weights rule to determine the
number of crew and their distribution on a flight. See Crew Weights Rule on page
99.
The Crew Weights rule determines the crew weight category to be used and the
Crew Distribution rule determines the number of crew and their distribution on a
flight.

Rule Criteria
Table: Crew Distribution Rule Criteria

Market
Destination
Carrier/Aircraft The aircraft subtype, as defined in DBM. Mandatory.
0
Subtype
Fitted Interior The name given to the fitted interior, for example
0
Name 14P/50J/315Y. Mandatory.
64 Crew owner airline code.

Crew Owner
32
example, 6X-XYZ.
LH - Long-haul
SH - Short-haul
Template Flight
16 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flt No Range
Day of Week The days that this row applies to, such as 12 (for
4
2
STD From The starting and ending standard time of departure in

1
STD To the format HH:MM.
96 Edition 8.5
Rule Contents
Table: Crew Distribution Rule Contents
Field Explanation
Enter the Crew Distribution name.

Crew Distribution The name must match exactly the Crew Distribution name stored
in DBM in the Carrier & Aircraft > Fitted Interior > Crew
Distribution tab. Mandatory.
Default Number TC Enter the default number for the tech and cabin crews.
The number of crew cannot be higher than the number defined in
Default Number CC DBM. Mandatory.

Crew distribution 6X LH 1for 6X World market flights for subtype 74E with fitted
config of F14J70W30M177.


The DOW window for Distribution Name 6X LH 1 displays 3 Tech Crew and 15
Cabin Crew. Their distribution and weight are displayed in the Crew Distribution
panel, for example 2 male Cabin Crew located at C1; 2 male Tech Crew located
at FD.
98 Edition 8.5
Crew Weights Rule

used instead.
Rule Description
This mandatory rule determines the crew weights category to be used when more
than one category exists in DBM.
The crew weights category name must match exactly the name stored in DBM in
the Carrier > General > Crew Weights tab, to work correctly in Flight
Management.
Example: Carrier > General > Crew Weights Tab in DBM
Related Rules
This rule also works in conjunction with the Crew Distribution Rule on page 95 to
determine the weight of crew and its distribution on a flight.
The Crew Distribution rule determines the number of crew and their distribution
on a flight and the Crew Weights rule determines the crew weight category to be
used to calculate the weight of the crew and its index effect.
Rule Criteria
Table: Crew Weights Rule Criteria
Crew Owner 32 Crew owner airline code.
Market Origin 16 The market of the flight origin.

Market
16 The market of the flight destination.
Destination


LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
1
Rule Contents
Table: Crew Weights Rule Contents
Field Explanation
Crew Weights The Crew Weights Category name.

Category The name must match exactly the Crew Weights name that exists
in DBM in the Carrier > General > Crew Weights tab. Mandatory.

Crew weights category 1ASTD for 6X World market flights.
100 Edition 8.5


Crew weights calculated for each crew location on the aircraft based on crew
weights category 1ASTD. For example, two male Tech Crew in location FD with a
weight of 162 kgs (2X81 kgs) and an index effect of -5.49 index units; two male
Cabin Crew in location C1 with a weight of 152 kgs (2x76 kgs) and an index
effect of -2.55 index units.
The total weight of the crew and their baggage (1746 kgs) and its index effect
(-2.68 iu) is displayed in the DOW panel.
Notes: The number of crew at each location is determined by the Crew
Distribution rule. See Crew Distribution Rule on page 95.
The balance arm for each crew location is stored in DBM in the Carrier
& Aircraft > Fitted Interior > Crew Seats tab.
Example: DOW Buildup (Crew) Window

Dry Operating Weight Change
Rule Description
This rule determines the tolerances allowed for changes to an aircraft's basic or
starting weight, and basic or starting index, when the Load Controller modifies
these values from the DOW Buildup window, available from the Flight
Information screen.
The BW & BI Modification Allowed setting in DBM determines whether the Load
Controller can modify the Basic Weight and Basic Index values.
Example: Carrier > General > Detail Tab in DBM
Note: If this business rule does not exist for the flight, and BW & BI
Modification is allowed in DBM, the system does not validate the weight
or index changes made by the Load Controller.
102 Edition 8.5

Rule Criteria
Table: Dry Operating Weight Rule Criteria
Mandatory.
Operating Carrier 0
Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 4
Flight No. Range
select the Flight Group Keyword, or Flight Ranges.
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Table: Dry Operating Weight Change Rule Contents
Field Explanation
Basic/Starting Weight The change in units of weight that the new value cannot
Change Tolerance deviate from the weight stored in DBM for the registration (or
aircraft subtype, if no registration is present).
Basic/Starting Index The change in index unit that the new value cannot deviate
Change Tolerance from the index stored in DBM for the registration (or aircraft
subtype, if no registration is present).


In the following example, BW and BI modification is enabled in DBM. The
business rule defines a tolerance of 500 weight units below or above the
basic/starting weight, and a tolerance of 5 index units below or above the index
for the registration.

The Load Controller attempts to update the Basic Weight, but mistypes the value
and enters an incorrect value.
The value for the Basic Weight is outside of the tolerance defined in the rule, and
the following error is displayed:
The Load Controller can correct the value if it is a mistake, or choose to override
the warning if correct.
104 Edition 8.5

Dry Operating Weight Name Rule

used instead.
Rule Description
This mandatory rule for dry operating weight operating type flights determines
which dry operating weight schedule to use for the registration, when more than
one exists in DBM.
The dry operating weight name must match exactly the name stored in the
Carrier & Aircraft > General > Aircraft Information tab, at the registration level,
to work correctly in Flight Management.
Example: Carrier > General > Aircraft Information Tab in DBM (Registration Level)
Rule Criteria
Table: Dry Operating Weight Name Rule Criteria

Market
Destination
Carrier/Aircraft
Subtype
Crew Owner 64 Airline code of the crew owner.


LH - Long-haul
SH - Short-haul
Template Flight
16 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flt No. Range 8 To specify the flight number range, click on and
4
Day of Week Monday and Tuesday).
2

1
STD To the format HH:MM.
Rule Contents
Table: Dry Operating Weight Name Rule Contents
Field Explanation
DOW Operating The DOW Operating (Weight) name.

Name The name must match exactly the DOW/I Name stored in DBM in
the Carrier & Aircraft > Fitted Interior > Dry Operating Weight
tab. Mandatory.
106 Edition 8.5


DOW Operating Name - 'STANDARD' for 6X flights operated by subtype 737-800
DOW.

The Flight Information screen for 6X907 displays the dry operating weight
schedule for 6X-AAA (42100 / 198.00) stored in DBM for the selected Aircraft Dry
Operating Weight.

Dynamic Passenger Weights Rule
Rule Description
This optional rule is used to determine if dynamic passenger weights are to be
used. If this rule is used for a flight, the Flight Management application will
compare the weight of the passengers based on the adults/children/infants (ACI)
option and on the males/females/children/infants (M/F/C/I) option, and use the
lower total weight for the loadsheet calculations.
The passenger weights categories are stored in DBM in the Carrier > General >
Pax Weights tab and the category must include weights for males, females and
adults, for this rule to work correctly in Flight Management.
Example: Carrier > General > Pax Weights Tab in DBM
Rule Criteria
Table: Dynamic Passenger Weights Rule Criteria

Market
Destination
Carrier/Aircraft
Subtype
Fitted Interior The name given to the fitted interior, for example
8
Name 14J/50J/315Y.
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
108 Edition 8.5

Flt No. Range

1
Rule Contents
Table: Dynamic Passenger Weights Rule Contents
Field Explanation
Use Dynamic Select if dynamic passenger weights are to be used.

Passenger Weights

Use Dynamic Passenger Weights check box selected for 6X World market flights.


The weight comparison is displayed in the SI (Supplementary Information)
section of the loadsheet.
Note: In DBM the Carrier > General > Doc Type Rules tab includes an Inc.
Pax Weights Comparison in the Supplementary Information panel. This
check box must be selected for the weight comparison to be displayed
on the loadsheet.
110 Edition 8.5

Final Fuel Release Rule
Rule Description
This rule is used to determine if Fuel Monitoring Message (FMM) data is required,
before the fuel status can be set to Final.
It also controls the amount by which the reported fuel figure can exceed the total
fuel in tanks figure, before a warning message is displayed.
Rule Criteria
Table: Final Fuel Release Rule Criteria
Departure Airport 0 The market of the departure airport. Mandatory.

Arrival Airport 0 The market of the arrival airport. Mandatory.
1

Rule Contents
Table: Final Fuel Release Rule Contents
Field Explanation
Fuel Release and FMM Select this check box if Fuel Monitoring Message data is
Required required before the fuel status can be set to Final.
Reported Vs Actual Fuel The maximum amount that the reported fuel figure can
Variation Threshold exceed the total fuel in tanks figure.
Note: The reported fuel figure must be equal to or
greater than the total fuel in tanks figure.
112 Edition 8.5

Forecast ZFW Calculation Rule
Note: This rule was previously named the Actual Weights for FZFW
Calculation rule.
Rule Description
This rule contains settings used to calculate the FZFW (Forecast Zero Fuel
Weight) and to determine the behaviour of the ZFW Figures window in Flight
Management.
This rule is used if the Load Control Status is LO (load control open).
Rule Criteria
Table: Forecast ZFW Calculation Rule Criteria
Operating Carrier 0
Market
Destination
Flight No. Range 8 To specify the flight-number range, click on to select

LH - Long-haul
SH - Short-haul
Template Flight
2 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
1

Rule Contents
Table: Forecast ZFW Calculation Rule Contents
Field Explanation
Conditions to use actual weights

Internal cargo release status Select to use the actual weights if the internal cargo
final release status is Final.
External cargo release Select to use the actual weights if the external cargo
status final release status is Final.
Forecast ULD tare weight

Add ULDs not created by For containerised flights only.
external cargo system When selected, an additional field Inc. Ext. ULD Tare
is added to the forecast and current zero fuel weights in
the ZFW Window in Flight Management.
The Inc. Ext. ULD Tare field displays the ULD tare
weights received from the external cargo system, and is
updatable in the Forecast ZFW panel.
See Example Rule 2 in Example Business Rules and
Impact on Flight Management on page 115 for more
information.
114 Edition 8.5

Field Explanation
Forecast ZFW by destination

Enable forecast figures by When selected, the behaviour of the ZFW Figures
destination window is as follows:
The Load Controller cannot make updates to
cargo, mail, courier and ULD tare weights in the
ZFW Figures window, but can make updates to
the ZFW Adjustments value.
The ZFW Figures window includes the Payload
by Destination button.
Clicking on the Payload by Destination button
displays a secondary window, from where the Load
Controller can update forecast-joining weights by
destination for the flight leg.
See Example Rule 3 in Example Business Rules and
Impact on Flight Management below for more
information.
Example Business Rules and Impact on Flight Management
Example Rule 1:
For flights impacted by the rule, the actual cargo figures are used to calculate the
forecast zero fuel weight if the internal and the external cargo release status is
Final.

Example Rule 2:
For flights impacted by the rule, the Inc. Ext. ULD Tare field in the ZFW Window
in Flight Management displays the ULD tare weights received from the external
cargo system, and is updatable in the Forecast ZFW panel.
The ULD Tare field includes the tare weight of ULDs received from the external
cargo system and those created in Flight Management, and cannot be updated.
Image: ULD Tare Weights on the ZFW Figures Window
116 Edition 8.5

Example Rule 3:
For flights impacted by the rule, the Load Controller cannot make updates to
cargo, mail, courier and ULD tare weights in the ZFW Figures window, and can
only update the Adjustments field in this window.
The ZFW Figures window includes the Payload by Destination button.
Clicking on the Payload by Destination button displays a secondary window,
from where the Load Controller can update forecast cargo, mail, courier and ULD
tare weights by destination for the flight leg.
Image: Payload by Destination Button in the ZFW Figures Window

Image: Secondary ZFW Figures Window, from the Payload by Destination Button
118 Edition 8.5

Forecast ZFW Change Rule

Rule Description
This optional rule determines whether a forecast zero fuel weight (FZFW)
message is sent automatically or manually, when the forecast zero fuel weight
change parameters are exceeded.
When a change to a FZFW exceeds the FZFW Change Amount, and the time
since the last FZFW message was sent exceeds the FZFW Change Time, an
updated FZFW is sent.
The rule can also be used to extend the monitoring of ZFW calculation until the
final loadsheet is issued.
Rule Criteria
Table: Forecast Zero Fuel Weight Change Rule Criteria

Market Destination 0 The market of the flight destination. Mandatory.
The template flight type code:
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
To specify the flight number range, click on and

Flight No. Range 2 select the Flight Group Keyword or the Flight Range
(s).
Effective From The starting and ending effective date of this row in
1
Effective To the format DDMMMYY.

Example: Forecast Zero Fuel Weight Change Rule
Rule Contents
Table: Forecast Zero Fuel Weight Change Rule Contents
Field Explanation
Send FZFW - Select to send a forecast zero fuel weight message

automatically automatically.
Note: Selecting this check box disables the Prompt check
box, and enables the associated parameter fields.
Send FZFW - prompt Select to send a prompt to the Load Controller when the ZFW
parameters have been exceeded.
Note: Selecting this check box disables the Automatically
check box, and enables the associated parameter
fields.
FZFW Change When selected, forecast ZFW monitoring continues until the
Monitoring at Final final loadsheet has been issued.
Fuel When unselected, forecast ZFW calculations monitoring stops
when fuel figures are finalised.
FZFW Change Enter the amount by which the zero fuel weight must change
Weight Parameter before an updated forecast zero fuel weight message, or a
prompt, is sent.
FZFW Change Time Enter a number of minutes.
Parameter (min) If the FZFW Change Weight defined in the field above is
exceeded for this number of minutes, an updated forecast zero
fuel weight message, or a prompt, is sent.
120 Edition 8.5


In the following rule, a FZFW prompt is displayed to the Load Controller when the
change of FZFW exceeds 1,000 kilos for longer than 10 minutes.

Fuel CG Targeting Processing Rule
Rule Description
CG Targeting functionality is used for A380 aircraft.
This rule stores parameters that control how aircraft CG Targeting fuel processing
is managed in Flight Management.
Related Rules
The following rules are used for processing fuel for the A380 aircraft:
Predicted ZFW Fuel Split Rule on page 174.
ACARS Fuel Status Request Frequency Rule on page 184.
Fuel CG Targeting Processing Rule above.
The Inhibit final loadsheet creation if Fuelling Status not Complete
option in the Inhibit Final Loadsheet Creation Rule on page 287.
Rule Criteria
Table: Send CG Targeting Parameters Rule Criteria
Mandatory.
Operating Carrier 0
Mandatory.
Market Origin 0
Market Mandatory.
0
Aircraft Subtype The aircraft subtype, as defined in DBM.
16
Example: A380-800
Registration 4
Flight No. Range
1 format DDMMMYY.
Effective To
122 Edition 8.5

Rule Contents
Table: Fuel CG Targeting Processing Rule Contents
Field Explanation
Send CG Targeting Parameters

These parameters apply to the CG Targeting parameters sent to the aircraft.
Include pre-selected fuel quantity When selected, the Pre-selected Fuel Quantity is
included in the CG Targeting parameters sent to
the aircraft.
The Pre-selected Fuel Quantity is the total fuel in
tanks, with an optional fuel reduction (see the
Apply Fuel Reduction field below).
Apply fuel reduction This field becomes available when the Include Pre-
selected Fuel Quantity is selected.
When selected, the fuel reduction specified for the
flight in the Fuel Reduction Rule on page 133 is
deducted from the Pre-selected Fuel Quantity.
Inhibit Send CG Targeting CG Targeting parameters cannot be sent to the
Parameters if Load Control aircraft, either manually, or triggered via an event,
Status is Open (status LO) when the selected conditions are met.
Inhibit Send CG Targeting An error message is displayed to the Load
Parameters if ACARS Preliminary Controller, and the CG Targeting parameters are
Loadsheet is Sent not sent.
Inhibit Send CG Targeting

Parameters when Final
Loadsheet is Sent
Inhibit Fuel Status Request When selected, Flight Management does not send
the Fuel Status Request message when the CG
Targeting parameters are sent.

Field Explanation
When Flight Management sends the CG Targeting

Inhibit negative ACARS Fuel
Parameters in the Fuel Data Submission message
Data Command if ACARS Fuel
(FDASUB) to the aircraft, it expects a Fuel Data
Data Acknowledgement is not
Acknowledgement message (FDAACK) before a
received
timeout period.
By default, if the FDAACK message is not received
before the timeout period, Flight Management
sends a negative Fuel Data Command message
(FDACOM=0) to the aircraft.
When selected, this option prevents Flight
Management from sending the negative Fuel Data
Command (FDACOM) message to the aircraft if
the FDAACK message is not received before the
timeout period.
If this occurs, a notification is sent to the Load
Controller:
No ACARS response for ACARS Fuel Submission
(CG Targeting Parameters).
Fuel data messages sent to and received from the
aircraft, and notifications sent to the Load
Controller, are recorded in the flight history.
Receive Fuel on Board Figures
These parameters apply to messages received by Flight Management from the aircraft:
Fuel Status Report Message.
Fuel End Message.
Fuel Transfer End Message.
Fuel Transfer Interrupt Message.
Update fuel quantity in Trim Tank When selected, only the trim tank fuel figure
only received from the aircraft is updated in Flight
Management.
Process fuel figures automatically By default, Flight Management sends a very high-
if Fuel Status is Final priority message to the Load Controller when fuel
figures are received from the aircraft, and the Fuel
Figure Status is Final. The Load Controller must
accept or reject the fuel figures to update the fuel
figures in Flight Management.
When selected, if fuel figures are received after the
Fuel Figure Status has been set to Final, a
medium-priority message is displayed to the Load
Controller, and the figures are automatically
updated in Flight Management.
Retain fuel status if Fuel Status is By default, Flight Management sets the Fuel
Final Figure Status to Provisional each time new fuel
figures are received, and the Load Controller must
then set the Fuel Figure Status to Final.
When selected, if the Fuel Figure Status has
already been set to Final, the fuel status remains
Final when new fuel figures are received by Flight
Management.
124 Edition 8.5

Field Explanation
Send Fuel Transfer if the aircraft By default, the Request Fuel Transfer button on
is out of trim at TOW the Send CG Targeting Parameters window (Fuel
screen) is enabled when the aircraft is out of trim
at takeoff weight and the fuelling status is
Complete.
The Load Controller can make a manual request
for fuel transfer for CG Targeting by clicking on the
Request Fuel Transfer button.
When selected, and the aircraft is out of trim at
takeoff weight and the fuelling status is Complete:
Flight Management automatically sends a fuel
transfer message to the aircraft.
A notification is sent to the load controller
when the fuel transfer message is sent.
The Request Fuel Transfer button on the
Send CG Targeting Parameters window
remains enabled for a manual request for fuel
transfer.


When the Load Controller attempts to send the CG Targeting parameters after
the ACARS preliminary loadsheet has been sent, the following message is
displayed to the Load Controller, and the parameters are not sent:
'CG targeting parameters cannot be sent after ACARS Preliminary Loadsheet
is sent.'
When fuel on board figures are received by Flight Management from the aircraft,
and the fuel figure status is already set to Final, the Load Controller receives a
medium-priority message about the new fuel figures, and the fuel figure status
remains set to Final with the new fuel on board figures.
126 Edition 8.5

Fuel Change Tolerance Rule
Rule Description
The main purpose of this rule is to reject large variations when reporting fuel
figures in an external ramp system. For example, the user of the external ramp
system may enter 10,000 instead of 1000.
When fuel figures are received from the external system, Flight Management
checks the change tolerance (in weight or percentage) of the figures received
against the fuel figures stored in Flight Management. If the received fuel figures
are within the tolerance defined in the rule, the system updates the fuel figures in
Flight Management.
If the received figures exceed the tolerance defined in the rule, Flight
Management rejects the update, and an error condition is sent back to the
external system. In this case, the fuel figures must be corrected in the external
system and resent to Flight Management.
A check is made on trip fuel, taxi fuel, and useable fuel figures.
Rule Criteria
Table: Fuel Change Tolerance Rule Criteria
Operating Carrier Mandatory.

0
Mandatory.
Market Origin 0
Market Mandatory.
0
Template Flight Select from the following code:
Type LH - Long-haul
SH - Short-haul
16 CF - Charter
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
2 format DDMMMYY.
Effective To

Rule Contents
Table: Fuel Change Tolerance Rule Contents
Field Explanation
By % Select to define the fuel change tolerance by percentage or

weight units.
By Weight
Trip Fuel Tolerance The fuel change tolerance allowed, for each type of fuel
figure.
Taxi Fuel Tolerance
Examples: 10 (when % is selected), 1000 (when weight is
Useable Fuel selected).
The fuel tolerance is defined by percentage. The trip and useable fuel figures
received from the external ramp system can vary by up to 25%, and the taxi fuel
by up to 100%.
128 Edition 8.5

Fuel Density Rule

Rule Description
This optional rule determines which fuel density is to be used for a departure,
based on the market or departure port and terminal.
The information from this rule overrides the Default Fuel Density that is specified
in DBM in the Carrier > Detail tab.
Example: Carrier > General > Detail Tab in DBM
Related Rules
This rule can be used in conjunction with Fuel Density Update Rule on page 131,
which permits a Load Controller to update the fuel density for a departure.
Rule Criteria
Table: Fuel Density Rule Criteria

Market 0 The market of the flight origin. Mandatory.
Crew Owner 4 The two-character code of the crew owner.
Terminal 2 The airport terminal of the flight departure.

1

Rule Contents
Table: Fuel Density Rule Contents
Field Explanation
Fuel Density The Fuel Density to be used.

Kg/L
Ibs/US Gal
Mandatory.

Fuel density of 0.79 kg/l for 6X flights departing from LHR.

On the Fuel screen, the fuel density set to 0.790 kg/l based on the Port/Terminal,
LHR.
130 Edition 8.5

Fuel Density Update Rule

Rule Description
This optional rule determines whether a Load Controller is allowed to manually
update the fuel density for a flight.
A manually updated fuel density overrides the default fuel density that is stored in
the DBM in the Carrier > General > Details tab or the fuel density stored in the
Fuel Density Rule.
Related Rules
This rule can be used in conjunction with the Fuel Density Rule, which sets the
fuel density based on the market or departure port and station.
Rule Criteria
Table: Fuel Density Update Rule Criteria
Operating Airline 0 The two-character carrier code. Mandatory.

Market
Destination
select the Flight Group Keyword or the Flight Range(s).
Rule Contents
Table: Fuel Density Update Rule Contents
Field Explanation
Fuel Density Select this check box if the Load Controller is allowed to update the
Update Allowed fuel density. Mandatory.


Fuel density updates allowed for 6X LHR market origin flights.
Example: Fuel Screen - Fuel Density Panel
If this rule is created for a flight leg and the check box is selected, the Manually
Updated check box on the Fuel screen can be selected and the fuel density
updated. The date and time of the manual update is displayed.
If this rule is not created for a flight leg, the Manually Updated check box on the
Fuel screen cannot be selected.
132 Edition 8.5

Fuel Reduction Rule
Rule Description
This rule defines a fuel reduction percentage or a value that is applied to fuel
figures when the fuel status is Provisional.
The fuel reduction is applied to the fuel figures when the fuel status is Provisional,
Provisional Standby Truck, or Provisional Partial Fuelling.
Related Rule
If the fuel status is not included in the incoming fuel message, it is derived from
the Fuel Status Rule on page 140.
Rule Criteria
Table: Fuel Reduction Rule Criteria
Mandatory.
Market Origin 0
Market Mandatory.
0
Carrier/Aircraft The aircraft subtype, as defined in DBM.
16
Subtype
Flight No. Range
Type LH - Long-haul
SH - Short-haul
4 CF - Charter
DF - Domestic
SF - Shuttle
CO - Cargo
1 format DDMMMYY.
Effective To

Rule Contents
Table: Fuel Reduction Rule Contents
Field Explanation
Provisional 1. From the drop-down menu, select the fuel change

tolerance by percentage, value or null.
Provisional Standby 2. Enter the fuel reduction value in the associated field.
Truck - For a percentage, the associated field must contain
Provisional Partial the fuel reduction percentage amount. For example,
Fuelling 5 (%).
- For a value, the associated field must contain the
fuel reduction value amount. For example, 200
(kgs).
A reduction is not applied to the fuel figures if the value in
drop-down menu is blank.
In this example, when the fuel status is Provisional, the fuel reduction value is
5%. When the fuel status is the Provisional Standby Truck, the fuel reduction
value is 200 kgs. When the fuel status is Provisional Partial Fuelling, the fuel
reduction value is 200 kgs.
134 Edition 8.5


Fuel figures are displayed on the Fuel screen.
Standard Fuel Distribution

The fuel reduction defined in the rule is applied to the following fuel figures:
Total volume
Total fuel in tanks
Usable fuel
Taxi fuel
Takeoff fuel
Non-Standard or Modified Standard Fuel Distribution

The fuel reduction defined in the rule is applied to the following fuel figures:
Total volume
Total fuel in tanks
Usable fuel
Taxi fuel
Takeoff fuel
Trip fuel

Fuel Standard Distribution Name Rule

Rule Description
This rule determines the default fuel standard distribution, if more than one exists
in DBM for an aircraft subtype or registration. If more than one fuel standard
distribution is defined in DBM, this rule is mandatory.
The fuel standard distribution name must match exactly the name stored in the
Carrier & Aircraft > Fuel > Standard Distribution tab, at the subtype or
registration level to work correctly in Flight Management.
Example: Carrier & Aircraft > Fuel > Standard Distribution Tab in DBM
Rule Criteria
Table: Fuel Standard Distribution Name Rule Criteria
Carrier 0 The two-character carrier code. Mandatory

Carrier/Aircraft
Subtype
Market
Destination
The registration number of the specific aircraft, for example,
Registration 1
6X-XYZ.
136 Edition 8.5

Rule Contents
Table: Fuel Standard Distribution Name Rule Contents
Field Explanation
The Fuel Standard Distribution name, exactly as stored in the

Fuel Standard Fuel Standard Distribution name in DBM in the Carrier &
Distribution Name Aircraft > Fuel > Standard Distribution tab at the subtype level.
Mandatory.

Fuel standard distribution name - ' WINGS+CENTRE & HST & AUX ' for 6X
World market flights for subtype 74E.

Default standard fuelling option set to WINGS+CENTRE & HST & AUX on the
Fuel screen.

Fuel Retention in Tank Rule
Rule Description
This rule defines which flights are eligible for the Retain Fuel in Tank option when
the Load Controller modifies the Standard Fuel Distribution settings on the Fuel
screen.
The standard fuel distributions for an aircraft are defined in DBM.
Example: Carrier & Aircraft > Fuel > Standard Distribution - Ramp Fuel Tab in DBM
Rule Criteria
Table: Fuel Retention in Tank Rule Criteria

Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 4
Flight No. Range
1 format DDMMMYY.
Effective To
138 Edition 8.5

Rule Contents
Table: Fuel Retention in Tank Rule Contents
Field Explanation
Allow Retain Fuel in When selected, the Retain Fuel in Tank option is displayed
Fuel Tank when the Load Controller modifies the Standard Fuel
Distribution settings

The Allow Retain Fuel in Tank field is selected.

The Retain Fuel in Tank column is displayed for the Standard Fuel Distribution on
the Fuel screen.

Fuel Status Rule
Rule Description
This rule is used in the context of fuel saving processes. For example, an airline
may decide to carry out partial fuelling, or make a standby refuelling truck
available for fuel adjustments at the last minute.
This rule determines the fuel status of a flight, if the fuel figure status is not
received in the fuel message from the external fuel system.
Standby Truck and Partial Refuelling are sub-statuses of the Provisional fuel
status, and are used to communicate information to ground staff involved in the
refuelling process.
Rule Criteria
Table: Fuel Status Rule Criteria
Mandatory.
Market Origin 0
Market Mandatory.
0
16
Subtype
Flight No. Range
Type LH - Long-haul
SH - Short-haul
4 CF - Charter
DF - Domestic
SF - Shuttle
CO - Cargo
1
format DDMMMYY.
140 Edition 8.5

Rule Contents
Table: Fuel Status Rule Contents
Field Explanation
Fuel Status Select from the drop-down menu:

Provisional
Provisional, Standby Truck
Provisional, Partial Fuelling
Final
In this example, the system sets the fuel status to Provisional - Partial Fuelling, if
the fuel figure status is not received in the fuel message from the external fuel
system.

The fuel status is displayed on the Fuel screen:

Ideal Trim Area Rule

Rule Description
This rule has two purposes:
It defines an ideal trim area on the Centre of Gravity (CG) graph on Flight
Management screens. This area is displayed in light green on the graph, and
can help the Load Controller to produce a more fuel-efficient trim.
The ideal trim information from this rule is used in the Autoload process.
Autoload respects the rules defined in the Autoload theme, while trying to
respect the target ZFW %MAC or range. When several load distributions are
possible for an Autoload them, the distribution closest to the ideal trim is
chosen.
Rule Criteria
Table: Ideal Trim Area Rule Criteria

Carrier/Aircraft
Subtype
The template flight type code.
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Market
Destination
Day of Week 8
1
142 Edition 8.5

Rule Contents
Table: Ideal Trim Area Rule Contents
Field Explanation
ZFW Range
From The lowest and highest zero fuel weight for the applicable
weight range. Mandatory.
To
ZFW% (Chord Type) Range
From The forward (FWD) and aft (AFT) zero fuel weight % chords
for the applicable weight range.
To
This field is mandatory if no ZFW% (Chord Type) Ideal Target
data is present.
ZFW% (Chord Type) The ideal zero fuel weight % chord for the applicable weight
Ideal Target range.
This field is mandatory if no ZFW% (Chord Type) Range data
is present.


Ideal ZFW trim data:

The ideal trim area displayed on the CG graph, and called during the Autoload
process.
Example: Centre of Gravity Graph
144 Edition 8.5

Loadsheet Tolerance Rule
Airline-specific functionality activation is required for this feature.
Rule Description
This rule stores the final loadsheet tolerance values data, which were previously
stored in DBM in the Carrier & Aircraft > General > Aircraft Information tab.
This data is used to determine if any of the values have been exceeded between
the issuance of the most recent provisional or preliminary loadsheet and the final
ACARS or radio loadsheet. If any of the limits have been exceeded a Significant
Change statement will be added to the final loadsheet.
Rule Criteria
Table: Loadsheet Tolerance Rule Criteria
Operating Carrier 0
Market
Destination
Flight No. Range
1

Rule Contents
Table: Loadsheet Tolerance Rule Contents
Field Description
Negative Positive
ZFW Tolerance Change The amount the zero fuel The amount the zero fuel
Amount weight can be reduced weight can be increased
before a significant change before a significant change
is identified. is identified.
ZF(Chord Type) Tolerance The amount the zero fuel The amount the zero fuel
Change Amount weight chord type can be weight chord type can be
reduced before a increased before a
significant change is significant change is
identified. identified.
TOW Tolerance Change The amount the takeoff The amount the takeoff
Amount weight can be reduced weight can be increased
TO(Chord Type) Tolerance The amount the takeoff The amount the takeoff
Change Amount weight chord type can be weight chord type can be
reduced before a increased before a
significant change is significant change is
identified. identified.
STAB Tolerance Change The amount the stabiliser The amount the stabiliser
Amount setting can be reduced setting can be increased
Note: All the fields are optional, but at least one field must be populated to
create the rule.
In this example, if the zero fuel weight or takeoff weight is reduced by more than
5,000 kgs or increased by more than 1,000 kgs, then a Significant Change
message is added to the final ACARS loadsheet.
If the zero fuel weight chord type or takeoff weight chord type is reduced by more
than 2 units, or increased by more than 2 units then a Significant Change
message is added to the final ACARS loadsheet.
146 Edition 8.5

If the stabiliser setting is reduced by more than 0.5 units, or increased by more
than 0.5 units then a Significant Change message is added to the final ACARS
loadsheet.
Example: Significant Change Message

Passenger Weights Rule

used instead.
Rule Description
This rule is mandatory, except if the IATA Service Type is Cargo Operation, when
it is not required. The rule defines the passenger weights category stored in DBM
in the Carrier > General > Pax Weights tab.
Example: Carrier > General > Pax Weights Tab in DBM
If the Passenger Gender Type Weights rule is set to MFCI, the Male, Female,
Child and Infant weights are used in any weight calculations for the checked-in
passengers.
If the Passenger Gender Type Weights rule is set to ACI, the Adult, Child and
Infant weights are used in any weight calculations for the checked-in passengers.
Related Rules
This rule works in conjunction with the Passenger Gender Type Weights rule,
which determines which of the weights are used from the relevant passenger
weights category, either MFCI or ACI. See Passenger Gender Type Weights Rule
on page 325.
The Passenger Weights rule determines which passenger weights category is
used for a flight.
148 Edition 8.5

Rule Criteria
Table: Passenger Weights Rule Criteria

Market
Destination
Crew Owner 128 Airline code of the crew owner.
The Aircraft Type code, taken from the relevant ACV

Aircraft Type 64 for the aircraft, as defined in Alta Inventory. Example
74A.
LH - Long-haul
SH - Short-haul
Template Flight
32 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flt No Range 16 To specify the flight number range, click on and

Registration 8
example, 6X-XYZ.
Carrier/Aircraft
Subtype
Day of Week 2
1
Example: Passenger Weights Rule Screen

Rule Contents
Table: Passenger Weights Rule Contents
Field Explanation
The Weights Category name.

Weights
Category The name must match exactly the Pax Weights name stored in
DBM in the Carrier > General > Pax Weights tab. Mandatory.

Passenger weights category XYB STD to be used for world market flights for
carrier 6X.
Example: Business Rule for 6X World Market Flights

Passenger weight category XYB STD is used to calculate the total weight of
passengers (11050 kgs) which is displayed in the Passenger/Cabin Bag totals on
the loadsheet.
In this example, the passenger weights for adults, children and infants (ACI) have
been used. The totals (137/3/1) are displayed in the Passenger/Cabin Bag totals
on the loadsheet.
Example: Partial Loadsheet - 6X117
Note: The weight of passengers may vary according to their class of travel.
150 Edition 8.5

Passenger Non-Standard Weights Rule

Rule Description
Passengers with non-standard weights are heavier or lighter than standard
passenger weights. Examples are rugby players (heavier) or ballet dancers
(lighter).
This business rule defines the categories of non-standard passengers that are
available to the Load Controller for a flight, and the weight adjustments (plus or
minus) to apply to each gender of a non-standard passenger. It also sets a
minimum number of non-standard passengers there must be on a flight before
the weight adjustments are applied.
The Load Controller enters the number and gender of the non-standard
passengers manually from the Non-standard Passenger Weights window,
available from the Passenger screen in Flight Management.
Flight Management takes the non-standard passenger weights into account when
calculating weights and balance of the aircraft.
of the operating carrier.
Note: To activate the Location Types Cabin Section and Class on the Non-
standard Passenger Weights window in Flight Management, you must
create a curtailment on the Centre of Gravity envelope for non-standard
weight passengers. Refer to the Carrier & Aircraft > CG Data >
Curtailment Rules tabs described in the DBM User Guide.
Related Rules
The Passenger Weights Rule on page 148 defines which set of standard
passenger weights stored in DBM applies to a flight.
Rule Criteria
Table: Flight Leg Operating Data Rule Criteria
Operating Carrier 0 Mandatory.

Mandatory.
Market Origin 0
Mandatory.
Market Destination 0
The market of the flight destination.
Crew Owner 8388608
Aircraft Type The Aircraft Type code, taken from the relevant
1048576 ACV for the aircraft, as defined in Alta Inventory.
Example 74A.


LH - Long-haul
SH - Short-haul
Template Flight
131072 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
16384 and select the Flight Group Keyword, or Flight
Ranges.
Registration 2048
Day of Week 32
Effective From The starting and ending effective date of this row,
4 in the format DDMMMYY.
Effective To
Rule Contents
152 Edition 8.5

Table: Rule Contents
Field Explanation
Minimum total non-standard The number of non-standard weight passengers

weight passengers for that must be defined on a flight before the weight
adjustments to apply adjustments are applied.
Non-standard weight passenger Click on New Row to define a non-standard weight
type passenger type, then enter the name in this field.
The name is displayed to the Load Controller in a
drop-down list on the Non-standard Passenger
Weight window in Flight Management.
Add new rows and data for each type of non-
standard passenger.
M, F, C, I, A The weight adjustment per male, female, child,
infant or adult passenger.
Enter a positive value to increase the standard
passenger weight for this type of passenger.
Example: 10 to increase the weight by 10 kg.
Enter a negative value to decrease the standard
passenger weight for this type of passenger.
Example: -8 to decrease the weight by 8 kg.
Note: Flight Management never sets a non-
standard passenger's weight to a
negative value. If you decrease the
weight by more than the passenger's
standard weight, Flight Management
sets the passenger weight to zero.

In the following rule, a non-standard passenger weight adjustment has been
defined for sportsmen and light children. There must be at least five non-standard
passengers on a flight before the weight adjustments are applied.


The Load Controller clicks on Non-Standard Weight Pax on the Passenger
screen in Flight Management, and enters the number of non-standard
passengers on the flight, and where they are seated in the aircraft.
In the example below, the Load Controller has entered eight male sportsmen
seated in J class, cabin section 0C, and 12 light children seated in cabin Y, cabin
section 0D. The minimum number of non-standard weight passengers is
exceeded, therefore Flight Management applies the weight adjustments from the
business rule in weights and balance calculations.
The option CABIN SECTION for the Location Type is available on this window
because a curtailment has been set for non-standard weight passengers on the
Carrier & Aircraft > CG Data > Curtailment Rules tab in DBM.
154 Edition 8.5

Pantry Code Rule

used instead.
Rule Description
This rule is mandatory for basic weight operating type flights. It determines the
pantry code for a flight if more than one exists in DBM for a fitted interior.
Pantry Codes are stored in DBM in the Carrier & Aircraft > Fitted Interior >
Pantry Weight & Index tab, or in the Carrier & Aircraft > Fitted Interior >
Pantry Distribution tab.
Example: Carrier & Aircraft > Fitted Interior > Pantry Weight & Index Tab in DBM
Example: Carrier & Aircraft > Fitted Interior > Pantry Distribution Tab in DBM
This rule sets the Pantry Code indicator in the Departure Plan Data panel of a
departure plan simulation. See Departure Plan Simulation on page 365.
Rule Criteria
Table: Pantry Code Rule Criteria

256
Subtype
The name given to the fitted interior in DBM.
Fitted Interior Name 128
Example: 14J/50J/315Y.
Saleable The saleable configuration of the flight, as sent by

64
Configuration Alta Inventory. Example: C54M120.
The registration number of the specific aircraft.

Registration 32
Example: 6X-XYZ.


LH - Long-haul
SH - Short-haul
Template Flight Type 16 CF - Charter
DF - Domestic
SF - Shuttle
CO - Cargo

Flight No. Range 8 select the Flight Group Keyword or the Flight Range
(s).
4
2
STD From The starting and ending standard time of departure

1
STD To in the format HH:MM.
Rule Contents
Table: Pantry Code Rule Contents
Field Explanation
The pantry code name or code.

Pantry codes can be defined in DBM for aircraft fitted interiors in
Pantry Code both the Pantry Weight & Index and Pantry Distribution tabs.
If the same code exists for both tabs, the most recent one is used.
Mandatory.
156 Edition 8.5


Pantry code A for 6X World market flights operated by subtype 74E with fitted
interior name of F14/J70/W30/M177.

The default pantry code A and its pantry distribution is displayed on the Pantry
DOW Buildup window in Flight Management.

Pantry Food Content No Uplift Rule
Rule Description
This rule is used to identify flights that do not uplift food content for the pantry, as
part of the process where a flight carries extra food content for subsequent
(return or onward) flights.
Example:
Flight 6X001: AMS LHR
Flight 6X002: LHR AMS
There is no food content loaded at LHR. Flight 6X001 uplifts additional food
content at AMS for flight 6X002 departing from LHR.
Note: When an update to the Pantry Food Content No Uplift rule impacts
existing flights, Flight Management updates the pantry figures of those
flights and any subsequent flights, up to load control status LSF.
Related Rules
Aircraft Schedule Rule on page 79, to identify subsequent flights.
Pantry Food Content Weight Rule on page 161, to determine the weight of
food to add to the first flight.
Rule Criteria
Table: Pantry Food Content No Uplift Rule Criteria

Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 4
Flight No. Range
1 format DDMMMYY.
Effective To
158 Edition 8.5

Rule Contents
Table: Pantry Food Content No Uplift Rule Contents
Field Explanation
No Uplift of Pantry Select to identify flights that do not uplift any food.
Food Content

The identified flights do not uplift food content.

Flight Management calculates the food content weight for a flight based on the
definitions in the Pantry Food Content Weight Rule on page 161. It then
determines whether there are any subsequent flights, based on the definitions in
the Aircraft Schedule Rule on page 79. It then checks whether the subsequent
flights do not uplift food content, as defined in this rule.
When a flight that is defined as a subsequent flight does not uplift food content,
the system calculates the food content weight required, and adds it to the first
flight. Flight Management notifies the load controller of the situation, and that
pantry figures may need to be adjusted.
Example message:
Pantry Food Content Entered must take into account the following flights that will
not uplift food: 6X002 12MAY12 LHR AMS

The load controller can make adjustments, if required, on the Pantry window.
160 Edition 8.5

Pantry Food Content Weight Rule
Rule Description
This rule defines the weight of the pantry food content per passenger and per
class. When this rule is used, the weight of the food is added to the weight of the
pantry as defined in DBM.
The weight of the pantry (excluding the food weight), the pantry distribution, and
the galley names, are stored in DBM.
Example: Carrier & Aircraft > Fitted Interior > Pantry Weight & Index Tab in DBM
Example: Carrier & Aircraft >Fitted Interior > Pantry Distribution Tab in DBM
Example: Carrier & Aircraft > Fitted Interior > Interior Locations Tab in DBM
Related Rules
When a flight carries food for a return or onward flight that does not uplift food,
the following business rules must also be defined:
Pantry Food Content No Uplift Rule on page 158, to identify which flights do
not uplift food.

Rule Criteria
Table: Pantry Food Content Weight Rule Criteria

Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 64
Fitted Interior
32
Name
STD From 16 Standard departure times.
STD To 8
Flight No. Range
LH - Long-haul
SH - Short-haul
Template Flight
2 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
1 format DDMMMYY.
Effective To
162 Edition 8.5

Rule Contents
Table: Pantry Food Content Weight Rule Contents
Field Explanation
Pantry Food Content Expected to Board (ETB) or Booked passenger figures.

Based on: Select from the drop-down list.
Pantry food weight is the number of passengers per class
multiplied by the food weight per passenger/class.
Food Meal Weights per Class
Class Click on New Row, and enter each class of service available
for the flight.
Examples: Y, J, C.
Food Meal Weight The weight of the food component only, for each passenger
in the class of service.
Example: 2.5.
Interior Locations per Class
Class Click on New Row, and enter each class of service available
for the flight.
Interior Location Type Select the valid pantry location of the food weights per class,
from the drop-down menu. Example: Galley.
Interior Location Name Enter the exact location name of the galley from the Carrier
& Aircraft > Fitted Interior > Interior Locations tab in
DBM, where the food weight will be loaded.
To distribute the food weights for the same class of service
over several locations, create a row for each galley location,
and enter the same class code on each line. Example:


In the rule below, food weights are calculated on Expected to Board (ETB)
figures, with 2 kilos of food weight per passenger in C class and 1 kilo per
passenger in M class.

The ETB figures for a flight are as follows:
164 Edition 8.5

The Pantry Distribution panel in the Pantry window displays the fixed and food
weights in separate columns. The fixed weight is derived from the Interior
Locations tab in DBM, and the food content weight is derived from the business
rule.
The load controller can manually update this table if required.

If the current flight has to uplift food for subsequent flights, a notification is sent to
the load controller that subsequent flight legs must be taken into consideration for
pantry.

Potable Water No Uplift Rule
Rule Description
This rule is used to determine if no potable water is to be uplifted on a flight, as
part of the process where a flight carries extra potable water for subsequent
(return or onward) flights.
Example:
Flight 6X001: AMS LHR
Flight 6X002: LHR AMS
There is no potable water loaded at LHR. Flight 6X001 uplifts additional potable
water at AMS for flight 6X002 departing from LHR.
Note: When an update to the Potable Water No Uplift rule impacts existing
flights, Flight Management updates the potable water figures of those
flights and any subsequent flights, up to load control status LSF.
Related Rules
Potable Water Weight Rule on page 169, to determine the weight of potable
water to add to the first flight.
Rule Criteria
Table: Potable Water No Uplift Rule Criteria

Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 4
Flight No. Range
1 format DDMMMYY.
Effective To
166 Edition 8.5

Rule Contents
Table: Potable Water No Uplift Rule Contents
Field Explanation
No Uplift of Potable Water Select this check box if no potable water is to be uplifted.
In this example no potable water is to be uplifted on flights 9S001 to 9S100,

subtype 733 departing from LHR.

Flight Management calculates the potable water weight for a flight based on the
definitions in the Potable Water Weight Rule on page 169. It then determines
whether there are any subsequent flights, based on the definitions in the Aircraft
Schedule Rule on page 79. It then checks whether the subsequent flights do not
uplift potable water, as defined in this rule.
When a flight that is defined as a subsequent flight does not uplift potable water,
the system calculates the potable water weight required, and adds it to the first
flight. Flight Management notifies the load controller of the situation, and that
potable water figures may need to be adjusted.
Example message:
Potable Water Entered must take into account the following flights that will not
uplift potable water: 6X002 12MAY12 LHR AMS

The load controller can make adjustments, if required, on the Potable Water
Dialog window, by selecting the Manually Updated check box.
168 Edition 8.5

Potable Water Weight Rule
Rule Description
This rule determine the default potable water is to be loaded on the aircraft,
based on the number of passengers, and by weight or tank resolution.
This rule is used in conjunction with the Carrier & Aircraft > SWA > Potable
Water Distribution tab in DBM.
Example: Carrier & Aircraft > SWA > Potable Water Distribution Tab in DBM
Related Rules
When a flight carries potable water for a return or onward flight that does not uplift
potable water, the following business rules must also be defined:
Potable Water No Uplift Rule on page 166, to identify which flights do not
uplift potable water.

Rule Criteria
Table: Potable Water Weight Rule Criteria

Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 32
STD From 16 Standard departure times
STD To 8
Flight No. Range
LH - Long-haul
SH - Short-haul
Template Flight
2 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
1 format DDMMMYY.
Effective To
170 Edition 8.5

Rule Contents
Table: Potable Water Weight Rule Contents
Field Explanation
The passenger figures to be used to calculate the potable

water requirements.
Potable Water based Select from drop-down menu:
on:
ETB (estimated to board)
Booked
Potable Water Weights
Min Pax The minimum number of passengers in the range.
Max Pax The maximum number of passengers in the range.
Water Weight The weight of potable water to be loaded.
The method of adding potable water to the aircraft.
Select from drop-down menu:
Weight - by the weight of potable water.
Potable Water by: Resolution - by a fraction of the tank volume to be
loaded.
Note: The potable water weight or resolution data must
be defined in the Carrier & Aircraft > SWA >
Potable Water Distribution tab in DBM.
Before what activity is a calculation of potable water
requirements made.
Dynamic Calculation of Select from drop-down menu:
Potable Water before:
FZFW (Forecast Zero Fuel Weight)
Water Tank Order

Potable water is defined by weight:

For the flights impacted by the rule, the following data is used to calculate the
amount of potable water to be loaded on the aircraft, based on the booked
passenger figures:
650 kgs of potable water is loaded if the booked passenger figure is between
0 and 75.
1300 kgs of potable water is loaded if the booked passenger figure is
between 76 and 150.
between 151 and 225.
between 226 and 300.
Flight Management calculates the weight of potable water to be loaded before the
Forecast Zero Fuel Weight message is sent.

The Total Water value is by Weight in the Potable Water Dialog window, based
on a booked figure between 0 and 75.
Example: Potable Water Dialog Window
Note: The Index value, and the values displayed in the Resolution field, are
taken from the DBM Potable Water Distribution tab.
172 Edition 8.5

Example: Carrier & Aircraft > SWA > Potable Water Distribution Tab in DBM

Predicted ZFW Fuel Split Rule

Rule Description
This rule is used for aircraft using the CG Targeting functionality; for example the
A380.
It is used to calculate an initial fuel split based on the predicted zero fuel weight
and percentage MAC. This allows the aircraft fuelling to commence before the
estimated ZFW and percentage MAC are known.
The ZFW default value is used until an EZFW calculation has been performed,
and the ZFW%MAC default value is used until an Approve Distribution has been
performed.
Related Rules
The following rules are used for fuel processing of the A380:
Predicted ZFW Fuel Split Rule above.
ACARS Fuel Status Request Frequency Rule on page 184.
Fuel CG Targeting Processing Rule on page 122.
The Inhibit final loadsheet creation if Fuelling Status not Complete
option in the Inhibit Final Loadsheet Creation Rule on page 287.
Rule Criteria
Table: Predicted ZFW Fuel Split Rule Criteria

Market
Destination
Carrier/Aircraft The aircraft subtype, as defined in DBM. Mandatory.
0
Subtype
Flt No Range 1 To specify the flight number range, click on and

174 Edition 8.5

Rule Contents
Table: Predicted ZFW Fuel Split Rule Contents
Field Explanation
ZFW Enter the default zero fuel weight. Mandatory.

ZFW %MAC Enter the default zero fuel weight percentage MAC. Mandatory.

Ramp Tolerance Limits Rule
Rule Description
This optional rule determines whether a load distribution can be automatically
approved following changes to the deadload received from an external ramp
system, or entered by the ramp agent.
When ramp figures are received, the system compares the deadload weights,
and the chord or index trim values for zero fuel weight, takeoff weight, and
landing weight, with the current values for the flight.
If the changes received from the ramp are within the limits stored in the rule, the
system automatically attempts to approve the updated distribution.
If the Ramp Tolerance Limits rule is not used, change tolerances for deadload
weight figures supplied by the ramp are stored in DBM.
Example: Carrier & Aircraft > AC Sub Type Rules Tab in DBM
Rule Criteria
Table: Ramp Tolerance Limits Criteria

0
Mandatory.
Market Origin 0
Market Mandatory.
0
Type LH - Long-haul
SH - Short-haul
16 CF - Charter
DF - Domestic
SF - Shuttle
CO - Cargo
176 Edition 8.5

Flight No. Range

2 format DDMMMYY.
Effective To
The following rule content window is displayed, based on the search criteria, and
the option you select in the Trim Tolerances panel:
Example: Ramp Tolerance Limits Rule Weight Tolerances Only
Example: Ramp Tolerance Limits Rule Trim by Chord Type

Example: Ramp Tolerance Limits Rule Trim by Index Unit
Rule Contents
Table: Ramp Tolerance Limits Rule Contents
Field Description
Trim Tolerances Panel

None Select this option button if changes to the trim are to be
ignored.
Chord Type Select this option button if the system makes a
comparison of trim tolerance values using the chord
values.
Index Unit Select this option button if the system makes a
comparison of trim tolerance values using index unit
values.
Trim Tolerances by Chord type
ZF (Chord Type) Increase The tolerance limit for an increase or decrease in the
Tolerance Limit zero fuel weight chord.
ZF (Chord Type) Decrease
Tolerance Limit
TO (Chord Type) Increase The tolerance limit for an increase or decrease in the
Tolerance Limit takeoff weight chord.
TO (Chord Type) Decrease
Tolerance Limit
LD (Chord Type) Increase The tolerance limit for an increase or decrease in the
Tolerance Limit landing weight chord.
LD (Chord Type) Decrease
Tolerance Limit
178 Edition 8.5

Field Description
Trim Tolerances by Index

ZF Index Increase Tolerance The tolerance limit for an increase or decrease in the
Limit zero fuel weight index.
ZF Index Decrease
Tolerance Limit
TO Index Increase Tolerance The tolerance limit for an increase or decrease in the
Limit takeoff weight index.
TO Index Decrease
Tolerance Limit
LD Index Increase Tolerance The tolerance limit for an increase or decrease in the
Limit landing weight index.
LD Index Decrease
Tolerance Limit
Weight Tolerances Panel
Deadload Weight Increase The tolerance limit for an increase or decrease in the
Tolerance Limit deadload weight.
Deadload Weight Decrease
Tolerance Limit
In the rule above, the following ramp tolerance limits apply:

Zero fuel weight index - increase or decrease limit of 5 index units.
Takeoff weight index - increase or decrease limit of 7 index units.
Landing weight index - increase or decrease limit of 5 index units.
Deadload weight - increase or decrease of 1,000 weight units (kilos or
pounds).


If any of the limits set in the rule are exceeded, the system resets the Load
Control status to LL, which means that the Load Controller must approve the
updated distribution.
If none of the limits are exceeded, the system automatically attempts to approve
the updated distribution.
180 Edition 8.5

Taxi Fuel Rule

Rule Description
This mandatory rule is required if more than one taxi fuel category exists for a
carrier.
The taxi fuel category must match exactly the name stored in DBM in the Carrier
> General > Taxi Fuel tab, to work correctly in Flight Management.
Example: Carrier > General >Taxi Fuel Tab in DBM
Rule Criteria
Table: Taxi Fuel Rule Criteria

The Aircraft Type code, taken from the relevant ACV for
Aircraft Type 0 the aircraft, as defined in Alta Inventory. Example 74A.
Mandatory.
Aircraft
Subtype
LH - Long-haul
SH - Short-haul
Template Flight
1 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Market
Destination

Rule Contents
Table: Taxi Fuel Rule Contents
Field Explanation
Enter the Taxi Fuel Category name.

Taxi Fuel Category The name must match exactly the Taxi Fuel Category name
stored in DBM in the Carrier > General > Taxi Fuel tab.
Mandatory.

Taxi fuel category 6X LARGE for 6X flights operated by aircraft type 744 and
subtype 74E.

Total Fuel on the Fuel screen: taxi fuel set to 1,500 kgs.
Example: Fuel Screen - Total Fuel Panel
182 Edition 8.5

Chapter 8
Administrator Rules
Information about the Administration rules is included in this section.

For general information about starting the Business Rules application and using
the Menus and buttons, see Understanding Rule Content Windows on page 27.
For information about Engineering rules, see Engineering Rules on page 69.

ACARS Fuel Status Request Frequency Rule

Rule Description
This rule is used for aircraft types using CG Targeting functionality; for example
the A380. It determines the frequency of the ACARS Fuel Status Request
message, which is sent by Flight Management to the aircraft to monitor the
fuelling status.
The Fuel Status Request message is sent before and after the receipt of the Fuel
End Message. Flight Management sends a Fuel Status Request to the aircraft,
which responds with a Fuel Status Report.
Related Rules
The following rules are used for fuel processing of the A380:
Predicted ZFW Fuel Split Rule on page 174.
ACARS Fuel Status Request Frequency Rule above.
Fuel CG Targeting Processing Rule on page 122.
The option Inhibit final loadsheet creation if Fuelling Status not
Complete in the Inhibit Final Loadsheet Creation Rule on page 287.
Rule Criteria
Table: ACARS Fuel Status Request Frequency Rule Criteria

Carrier/Aircraft The aircraft subtype, as defined in DBM. For example,
0
Subtype A380-800. Mandatory.
16
example 6X-XYZ.
Flight Group
8 To specify the flight number range, click on to
select the Flight Group Keyword or the Flight Range.
4
2

1 the format HH:MM.
STD To
184 Edition 8.5

Chapter 8 Administrator Rules
Rule Contents
Table: ACARS Fuel Status Request Frequency Rule Contents
Field Explanation
ACARS Fuel Status Request The number of minutes between Fuel Status
frequency prior to receiving the Fuel Request messages before the Fuel End
End Message (mins) message is received.
Mandatory.
ACARS Fuel Status Request The number of minutes between Fuel Status
frequency after receiving the Fuel Request messages after the Fuel End
End Message (mins) message is received.
Mandatory.

Fuel Status Request frequency set to every 30 minutes before and every 10
minutes after the Fuel End Message is received, for 6X World market flights with
aircraft subtype A380.

The Fuel Status Request and Fuel Status Report messages are not visible to the
Load Controller. Flight Management uses these messages to monitor the fuel
status on the aircraft.

ACARS Header Rule

Rule Description
This rule determines which ACARS documents should have an ACARS header,
and which text elements should be included in the header.
The business rule is mandatory for all ACARS messages used. If the rule is not
set-up, then the ACARS messages will contain no header information.
Rule Criteria
Table: ACARS Header Rule Criteria
Operating Carrier The two-character operating carrier code.

0
Mandatory.
ACARS Document The ACARS document code. Mandatory.
Type 0
See Document and Message Types on page 376.
Aircraft Subtype 4 The aircraft subtype, as defined in DBM
Flight Group
1
186 Edition 8.5

Rule Contents
Table: ACARS Header Rule Contents
Field Explanation
ACARS Header Indicator Select this check box if the specified document is to
have an ACARS header.
ACARS Header Information
Standard Message Identifier The carrier-specific 3-character code to be used in the
ACARS header.
Text Element Identifiers Select the check box to include the following data in
the header:
AN = Aircraft Number - Aircraft Registration or Tail
Number.
FI = Flight Identification - Flight number.
MA = Message Assurance - Message sequence
number.
GL = Geographical Location - Location code.
AP = Airport - Departure airport code

ACARS Response Notification Rule

Rule Description
This rule determines the priority to be assigned to certain ACARS message
acknowledgments.
Rule Criteria
Table: ACARS Response Notification Rule Criteria
Operating Carrier 0 The two-character operating carrier code. Mandatory.

Domain 8 The name of the domain.
Flight No. Range
1
188 Edition 8.5

Rule Contents
Table: ACARS Response Notification Rule Contents
Field Message Priority
ACARS message acknowledgement type: Select the priority for each message
ACARS RDO (request downlink) from the drop-down menu:
ACARS Preliminary Load Information None
Final Brief ACARS Loadsheet Low Priority
Final Extended ACARS Loadsheet Medium Priority
ACARS Preliminary Loadsheet High Priority
ACARS Notoc Very High Priority
ACARS Timeout

Approve Distribution Rule

Note: In July 2016 the Inhibit Approval of Distribution rule will be renamed
Approve Distribution rule.
Rule Description
This rule is called at Approve Distribution, and determines the conditions when a
load distribution cannot be approved. For example, when the cargo status is
provisional.
Related Rules
Process External Cargo Feed Message Rule on page 327 controls the cargo
release status.
Autoload Distribution Options Rule on page 196 can be used to enforce no-fit
visibility from the door in the Autoload process.
Rule Criteria
Table: Approve Distribution Rule Criteria

Market
Destination
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No.
1
190 Edition 8.5

Rule layout with activation (Autoload Cycle 3):
Rule Contents
Table: Approve Distribution Rule Contents
Field Explanation
Internal Cargo Status Select to inhibit Approve Distribution if the internal cargo
Provisional status is provisional.
External Cargo Status Select to inhibit Approve Distribution if the external cargo
For containerised aircraft.
No-Fit Not Visible
from Door Select to inhibit Approve Distribution if no-fit container
positions are not visible from the door of the aircraft.
A no-fit position is a containerised bay or pallet position that
does not contain a ULD.
Visible from the door means that a ULD can be loaded from
the door to the available ULD groups without moving any
other ULD.
Unoccupied bay/pallet positions of the following types are
allowed in the load distribution:
Positions set to No-Fit manually by the Load
Controller.
Ramp-cleared unoccupied positions.
Unserviceable or unavailable positions.
Note: Unoccupied pallet positions are excluded from
the no-fit visibility enforcement.

For flights impacted by the rule, approval of distribution is inhibited if the external
cargo status is Provisional.
If Approve Distribution is attempted, the following error message is displayed:
Approve distribution cannot be performed. The External Cargo status is
incomplete.
192 Edition 8.5

Autoload Bulk Mixing Rule

Rule Description
This rule determines the mixing of different sub-commodity types in the bulk holds
of the aircraft during Autoload.
Related Rules
The Autoload Theme Name Rule on page 199 determines the default Autoload
theme, when several have been defined in DBM for the aircraft subtype.
Rule Criteria
Table: Autoload Bulk Mixing Rule Criteria

Mandatory.
Market Origin 0
Market Mandatory.
0
Aircraft Subtype 0 Mandatory. The aircraft subtype, as defined in DBM.
Registration 16
Flight No. Range
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Day of Week 2
and Tuesday).
1 format DDMMMYY.
Effective To

Rule Contents
Table: Autoload Bulk Mixing Rule Contents
Field Explanation
No mixing by default If this field is not selected, Autoload disregards

all mixing rules to find a valid load distribution.
When selected, Autoload consults the other
fields in this business rule to determine which
commodities and sub-commodities can be mixed
in bulk holds.
Note: You must select this field in order to
enter values in the remaining fields.
Try to locate all load in the Autoload tries to locate all load, or all baggage
same hold commodities, in the same hold, referring to the
Try to locate all baggage list of sub-commodities that can be mixed, as
commodities in the same hold defined in the table below.
Sub-commodities which are allowed to be mixed if necessary

Sub-commodities A list of sub-commodities that Autoload can mix in the
same hold, if necessary.
Enter the sub-commodity codes. separated by
commas. Enter a commodity code followed by an
asterisk (*) to indicate all sub-commodities for a
commodity type. Example: B*.
Except A list of sub-commodities that must not be included in
the allowed sub-commodities for mixing in the same
hold.
Destination Double-click to display a drop-down list, and select the
number of destinations (flight legs) that apply, or select
ALL.
194 Edition 8.5


In the example above, Autoload firstly tries not to mix different sub-commodity
types in the same hold. However, where mixing is necessary to locate the load,
Autoload refers to the table to determine which sub-commodities can be mixed in
a bulk hold.
For example, all baggage sub-commodities (B*) can be mixed, except for BP,
which cannot be mixed. Mail (M) and Express Cargo (CX) can be mixed.

Autoload Distribution Options Rule

Rule Description
This rule stores options used in the Autoload process.
Related Rules
No-fit visibility from the door can be enforced at Approve Distribution using the
Inhibit Approval of Distribution Rule on page 281.
Rule Criteria
Table: Autoload Distribution Options Rule Criteria
Mandatory.
Operating Carrier 0
Mandatory.
Market Origin 0
Market Mandatory.
0
Flight No. Range
The template flight type code. Select from the following:
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Day of Week 2
1 format DDMMMYY.
Effective To
196 Edition 8.5

Rule Contents
Layout with activation:
Table: Autoload Distribution Options Rule Contents
Field Description
Auto Approve When selected, Flight Management attempts to automatically

Distribution approve distribution following the Autoload load distribution
process.
Autoload can be initiated by the Load Controller, or triggered
as an activity on the Event Scheduler.
If any distribution errors are present, the system displays a
high priority message to the Load Controller.
Enforce No-Fit
Visibility from the Door A no-fit position is a containerised bay or pallet position that
'Visible from the door' means that a ULD can be loaded from
the door to an available position without moving any other
ULD.
When selected, Autoload ensures that no-fit positions are
visible from the door of the aircraft.
Bay/pallet positions of the following types do not have to be
visible from the door:
Positions set to No-Fit manually by the Load Controller.
Note: Unoccupied pallet positions are excluded from the
no-fit visibility enforcement.


For the flights impacted by the business rule setting below, the Autoload process
attempts to automatically perform Approve Distribution after locating the
deadload.
198 Edition 8.5

Autoload Theme Name Rule

Rule Description
This rule is used to determine which Autoload theme is chosen to distribute the
load when the Autoload process is used.
When more than one Autoload theme is defined in DBM, and when only one
Autoload theme is entered into the rule:
The theme in the rule is highlighted as the default in the Autoload drop-down
menu on the Load Distribution screen for the Load Controller
The theme is used when Autoload is run as an activity.
When more than one Autoload theme is defined in DBM, but you do not create
this rule:
The Load Controller must manually select an Autoload theme from the
Autoload drop-down menu on the Load Distribution screen.
When Autoload is run as an activity, and no rule exists, an error is displayed
and Autoload does not complete.
You can enter up to four Autoload theme names in the rule. See Preferred Theme
Comparison, below.
Dependencies
The Autoload theme names entered in the rule must match exactly the
Autoload theme names stored in DBM in the Autoload >Theme-General tab.
Example: Autoload > Theme-General Tab in DBM
To use the Preferred Theme Comparison feature, you must enter values in
the Coefficient fields in the Distribution Comparison panel of the
Autoload > Theme - Distribution General tab in DBM. See the DBM User
Guide for more information.
Example: Autoload > Theme-Distribution General Tab in DBM

Preferred Theme Comparison

You can enter up to four Autoload theme names in the business rule, and order
them by priority.
When Autoload is triggered as an activity, and data is correctly defined in the
Distribution Comparison panel of the Autoload >Theme- Distribution General tab
in DBM, the system performs a comparison of the Autoload themes, and
nominates the one that returns the best distribution as the Preferred Theme.
Preferred Theme is displayed as the default in the Autoload drop-down menu,
before the available themes, on the Load Distribution screen. If the Load
Controller selects Preferred Theme, the Autoload processing is the same as
when triggered by an activity.
Rule Criteria
Table: Autoload Theme Name Rule Criteria

Carrier/Aircraft
Subtype
LH - Long-haul
SH - Short-haul
Template Flight
8 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Market
Destination
Day of Week 2
1
200 Edition 8.5

Rule Contents
Table: Autoload Theme Name Rule Contents
Field Explanation
Priority Each line has a priority.

To enter one Autoload theme, enter the Autoload theme name on the
first line only. This has the priority 1.
To enter additional Autoload themes, click on New Row to enter
another priority and theme name.
You can enter up to four themes, and order them by priority for the
Preferred Theme processing (described above).
Autoload The Autoload theme name to be used.
Theme Name The name must match exactly the name that exists in DBM in the
Autoload > Theme - General tab for the aircraft subtype.

Autoload theme 6X BagsFwd - 1Leg to be used as the default Autoload theme.


Autoload theme 6X BagsFwd - 1Leg is displayed as the default Autoload theme
on the Load Distribution screen, and is highlighted in the Autoload drop-down
menu.
When several Autoload themes are listed in the rule, the Autoload drop-down
menu on the Load Distribution screen displays Preferred Theme before the list
of themes, as shown below:
202 Edition 8.5

Baggage Classification Rule

Rule Description
This optional rule is used to determine which baggage classification category
defined in DBM is to be used on a flight leg.
Baggage classification categories are stored in DBM in the Carrier >Commodity
Subtype tab, under Commodity Type Code B, for those carriers using the
Transfer Baggage Extra functionality.
The Baggage Commodity in DBM controls which types of baggage commodities
are created.
Example: Carrier > Commodity Subtype Tab in DBM
Rule Criteria
Table: Baggage Classification Rule Criteria

Market
Destination
LH - Long-haul
SH - Short-haul
Template
8 CF - Charter
Flight Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight Group 16 To specify the flight number range, click on and select
Day of Week 4
and Tuesday).
1

Rule Contents
Table: Baggage Classification Rule Contents
Field Explanation
Baggage Classification Category Enter the relevant baggage classification name,

exactly as stored in DBM in the Carrier >
Commodity Subtype tab under Commodity Type
Code B.
For example, LONGHAUL.
For all 6X World Market flights using the LH template the LONGHAUL baggage
classification category is used.
204 Edition 8.5

Baggage Commodity Creation Rule

Rule Description
This optional rule is used to determine how a selected baggage commodity is to
be handled by capacity calculation.
Capacity calculation creates the selected commodity as a containerised or bulk
item, indicates the rest location, and determines whether commodity mixing is
allowed.
Rule Criteria
Table: Baggage Commodity Creation Rule Criteria

Market
Destination
Baggage
The baggage commodity. Example, BF, BJ, BY.
Commodity 0
Mandatory.
Subtype
LH - Long-haul
SH - Short-haul
Template
16 CF - Charter
Flight Type
DF - Domestic
SF - Shuttle
CO - Cargo
Aircraft
Subtype
Day of Week 2 Example: 12 (for Monday and Tuesday).
Registration 4
1

Rule Contents
Table: Baggage Commodity Creation Rule Contents
Field Explanation
Minimum no. of The minimum number of baggage pieces, for the selected baggage
baggage pieces commodity type, which are required to create a container.
Allow Mixing Select if the baggage commodity can be mixed with other baggage
commodities.
Note: If a Baggage Segregation rule exists for the flight,

the mixing requirements are taken from the
Baggage Segregation rule, and the setting in this
field is irrelevant.
Bulk Select if the commodity is to be created as a bulk item.

Rest Select from:
ULD - to add the rest indicator to a ULD item.
BULK - to add the rest indicator a BULK item.
For All 6X World Market flights, capacity calculation will create a container if there
are 10 or more BF commodity bags on a flight leg. The rest indicator is attached
to the container.
206 Edition 8.5

Baggage Segregation Rule

Rule Description
This rule is required if a non-default baggage segregation is required for the
capacity calculation process. The default baggage segregation is by commodity
and destination with topping up allowed. Topping up means that a container can
be topped up with more bags when at a transit port.
This rule is also used if capacity calculation is required to create a sort container
for a flight. A sort container contains mixed baggage commodities that cannot be
accommodated in the allocated containers, due to, for example, extra pieces or
large baggage.
The Baggage Segregation rule determines the type of baggage segregation or
mixing to be used on a flight.
A baggage commodity code is one or two characters, and is defined in the
Carrier > Commodity Subtype tab in DBM, for Commodity Type B (Baggage).
Related Rules
This rule works in conjunction with the following rules:
ULD Capacity Rule on page 351, which controls the amount of baggage to be
allocated to each baggage ULD.
Baggage Commodity Creation Rule on page 205, which indicates the
minimum number of pieces to create a baggage container.
Rule Criteria
Table: Baggage Segregation Rule Criteria
Operating The two-character carrier code. Mandatory.

0
Carrier
Market
Destination
Flight No.
4 To specify the flight number range, click on and select
Range
2
and Tuesday).
1

Layout 1, baseline:
Layout 2, with activation:
208 Edition 8.5

Layout 3, with activation:
Rule Contents
Table: Baggage Segregation Rule Contents
Field Explanation
Sort Container Select to include a sort container when running

Capacity Calculation.
Note: Selecting Sort Container on its own is valid.
No Topping Up If selected, the container cannot be topped up with
more bags when in transit.
Note: Selecting No Topping Up on its own is valid.
However, it cannot be selected when you
select one of the Mix options below.
Select only one Mix option, as described below. Optional.
Mix Commodity Rest Only Mix the rest locations only for the specified baggage
commodities into one or more containers.
If the sum of the number of pieces for the rest locations
is less than the maximum capacity, as defined in the
ULD Capacity rule, only one mixed ULD is created.
The minimum number of baggage pieces defined in the
Baggage Commodity Creation rule is not taken into
account for the mixing of rest locations.
If the base commodity does not exist for the flight,
mixing does not occur.
Destinations are not mixed.
Mix Commodity Only Create a mixed container with the selected
commodities.
The base commodity ULDs will be created according to
the ULD Capacity rule. If the last base commodity ULD
contains less than the default number of pieces, the
mix commodity will be added to this ULD, up to the
default number of pieces to create a mixed ULD.
Destinations will not be mixed.
Mix Commodity and Mix the commodities defined in the table, regardless of
Destination destination.

Field Explanation
Mix All Rest Commodities This functions in the same way as Mix Commodity Rest
Only described above. However, there is no concept of
base commodity, and mixing occurs for any of the
commodity types defined in the row in the table.
See the example for Layout 3, below.
Base Commodity / Mix Commodity Table - Layouts 1 and 2

In the table, specify which baggage sub-commodities can be mixed.
To add a row in the table, click on New Row. The system reads the table from
the top downwards. Use the Move Up and Move Down buttons to order the
lines.
The baggage commodity specified as the Base Commodity in the rule is the
primary commodity for the ULD.
If a commodity is defined in the table as a Base Commodity, you cannot also
define it as a Mix Commodity.
You cannot duplicate commodities. For example, if the table has a Base-Mix
entry of M-P, an entry of P-M is considered as a duplicate.
Example: Base & Mix Commodity Table
In the above example, baggage commodities BJ and BY can be mixed with BP.
The system reads the table from the top downwards: BJ is mixed with BP first.
Then, BY is mixed with BP.
Note: If the base commodity does not exist for the flight, mixing does not
occur.
210 Edition 8.5

Commodity Table, Layout 3

When the Mix All Rest Commodities option is selected, the concept of Base
Commodity and Mix Commodity is no longer used.
The Rest Location for the baggage commodities on the same line can be mixed.
Enter the codes separated by a comma.
Example: Mix All Rest Commodities
In the above example, the rest location for baggage commodities BJ, BW, and
BC can be mixed. Each commodity does not have to exist for mixing to occur.
The rest location for baggage commodities BB and BY can be mixed.
To add a row in the table, click on New Row. The system reads the table from
the top downwards. Use the Move Up and Move Down buttons to order the
lines.

Following the capacity calculation process, baggage commodities are displayed
on the Deadload screen.
Mixed baggage commodities are displayed with Commodity MIXED, and can be
expanded to display the individual baggage commodity types.

Baggage Statistics Override Rule

Rule Description
This rule is used to override the baggage statistical data stored in the Stats/Hist
> Pax & Bag Statistics tab in DBM.
The values stored in this rule are used when calculating the planned baggage
pieces and weight.
Related Rules
This rule is not read if baggage statistics are activated in the Selected
Passenger and Baggage Statistics Rule on page 336.
This rule can be used in conjunction with the WWF Override Rule on page
363.
Rule Criteria
Table: Baggage Statistics Override Rule Criteria

Departure Airport 0 The market of the flight origin. Mandatory.
Arrival Airport 0 The market of the flight destination. Mandatory.
To specify the flight group or flight number range, click
Flight Group 16 on and select the Flight Group Keyword or the
Flight Range(s).
LH - Long-haul
SH - Short-haul
Template Flight
8 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Day of Week 4
1
212 Edition 8.5

Rule Contents
Table: WWF Baggage Statistics Rule Contents
Field Explanation
Baggage Commodity The baggage sub-commodity, as defined in the Commodity

Subtype. Subtype tab in DBM for commodity type B (baggage).
Example: F,J,Y.
Avg Pieces The average number of baggage pieces per passenger.
Avg Weight The average weight of each baggage piece per passenger.
For flights impacted by the rule, the system uses the following values to calculate
the planned baggage pieces and weight:
For commodity F - 1.5 pieces per passenger at an average weight of 24.0
kilos.
For commodity J - 1.2 pieces per passenger at an average weight of 20.0
kilos.
For commodity Y - 1.0 pieces per passenger at an average weight of 18.0
kilos.

Baggage Type Rule

used instead.
Rule Description
This mandatory rule is required for flight creation, unless the IATA service type is
defined in the IATA Service Type Rule on page 276 as a cargo operation. This
rule specifies whether the baggage type for the flight is PO (Pieces Only), PW
(Pieces and Weight) or GW (Gross Weights).
Related Rules
This rule works in conjunction with the Baggage Weights rule, if the PO (Pieces
Only) option is required.
The Baggage Weights rule determines the baggage weights category to be used
for a pieces only flight when more than one category exists in DBM for the carrier.
See Baggage Weights Rule on page 81.
Rule Criteria
Table: Baggage Type Rule Criteria

Market
Destination
Flight No. 8
To specify the flight number range, click on and select
Range the Flight Group Keyword or the Flight Range.
2
Day of Week 1
and Tuesday).
214 Edition 8.5

Rule Contents
Table: Baggage Type Rule Contents
Field Explanation
Baggage Type Enter the Baggage Type:

PO - for pieces only.
PW - for pieces and weight.
GW - for gross weights.
Mandatory.

6X World market flights set to PW (Pieces and Weight).

Baggage type indicator PW (pieces and weight) in the status bar on Flight
Management screens.
Example: Flight Management - Status Bar

Cargo Delivery Sequence Rule

Rule Description
This rule determines which types of unit load devices (ULDs) and commodity
types on a containerised flight are processed to calculate the delivery order of the
ULDs to the aircraft for ease of loading.
The system calculates and stores the cargo delivery sequence each time a new
version of the LIR is issued. A Cargo Delivery Sequence (CDS) message can be
generated, to inform the cargo department of the sequence to deliver the ULDs to
the aircraft.
Cargo Delivery Sequence Calculation

For single lane loading, the system calculates the sequence order starting from
the back of the forward hold to the door, excluding the position at the door, then
from the front of the forward hold to the door. The sequence order continues from
the front of the aft hold to the door, excluding the position at the door, then from
the rear of the aft hold to the door.
Example:
AFT HOLD FORWARD HOLD
9 10 11 8 7 1 2 3 6 5 4
Door Door
For dual lane loading, the system calculates the sequence order by pairs left and
right, starting from the left side, from the back of the forward hold to the door,
excluding the position at the door, then from the front of the forward hold to the
door. The sequence order continues from the front of the aft hold to the door,
excluding the position at the door, then from the rear of the aft hold to the door.
Example:
11 13 15 9 7
1 2 3 6 5 4
12 14 16 10 8
Door Door
If the door is configured to expand upon more than one position, the sequence
order is calculated as follows :
8 9 11 10 7 1 2 3 6 5 4
216 Edition 8.5

Rule Criteria
Table: Cargo Delivery Sequence Rule Criteria
Operating Carrier 0 The two-character code for the airline. Mandatory.

Flight No. Range
Effective From The starting and ending effective date of this row, in
1 the format DDMMMYY.
Effective To
Rule Contents
Table: Cargo Delivery Sequence Rule Contents
Field Explanation
ULD Type The 3-character ULD code, as defined in the Carrier/General/ULD

Type tab in DBM. Example: AKE. Mandatory.
Commodity The commodity or commodity and sub-commodity code, as defined
in the Carrier > General > Commodity Subtype tab in DBM.
Examples: C, CX.
Enable Select to enable cargo delivery sequencing for the selected ULD
Sequencing and commodity type.


Cargo delivery sequence processing is enabled for commodity type C (cargo) on
ULD types AKE and PMC.

Example of a Cargo Delivery Sequence message, with ULD types PMC and AKE
enabled for sequencing.
CARGO DELIVERY SEQUENCE
FLIGHT DATE ORIGIN DESTINATION ETD REGO ACFT LOC

6X188 28MAY12 LHR HKG 1400 6XABC
TIME SENT 1100 UTC

LOAD CONTROLLER NAME D HUNT PH :
ISSUE NUMBER 6
+++++++++++++ LOWER DECK ++++++++++
+++++++++++++ FORWARD +++++++++++++
1 PMC44446X
2 PMC33336X
3 PMC22226X
4 PMC11116X
5 AKE49686X
6 AKE97336X
7 AKE12106X
+++++++++++++ AFT +++++++++++++++++
SI
218 Edition 8.5

Commodity Conversion Threshold Rule
Rule Description
The purpose of this rule is to identify transfer cargo commodities with a short
ramp turnaround, and identify them in Flight Management with a special
commodity code.
The transfer time included in the external cargo feed is compared to a threshold
time in minutes defined in the rule. If the transfer time is equal to or less than the
time defined in the rule, the commodity code is modified to a quick ramp transfer
code, in order to benefit from special attention from the Load Controller, such as
being located near the aircraft door.
Rule Criteria
Table: Commodity Conversion Threshold Rule Criteria
Operating Carrier 0
Mandatory.
Market Origin 0
Mandatory.
Outbound Terminal 16
Departure Time From Format 12:00
4
Departure Time To
Effective To

Rule Contents
Table: Commodity Conversion Threshold Rule Contents
Field Explanation
Inbound Carrier 2-character carrier code. Example: 6X

Inbound Flight Number Number of the inbound flight. Example: 123.
Input Commodity The commodity code to process in the cargo feed.
Threshold Time The number of minutes used to determine whether a
commodity code should be changed. The new
commodity code is applied when the transfer time is
less than or equal to this number of minutes.
New Commodity The commodity code to be used for quick ramp
transfer cargo, when the threshold time applies.
Example: CQ
You cannot enter a baggage commodity or a crew
baggage commodity (starting with B or D).

In the first line of the rule below, when the commodity code C (cargo) is present in
the external cargo feed for 6X flights identified in the rule criteria, and the
connecting time is 90 minutes or less, the commodity code is changed from C to
CQ on the connecting flight.
220 Edition 8.5


The load controller can identify short connection cargo due to the commodity
code CQ, and locate it appropriately on the load distribution.

Create Hub Containers Rule
Rule Description
A hub container is a baggage container created for a specific onward flight, if
sufficient transfer baggage is expected for that flight.
This rule determines whether sufficient transfer baggage exists for an onward
flight to create a hub container.
For hub container functionality, a hub container baggage commodity must be
defined in the Hub Baggage Commodity field in DBM.
Example: Carrier & Aircraft >General >Commodity Subtype in DBM
Related Rules
This rule works in conjunction with the following rules in the during the Capacity
Calculation process:
Baggage Classification Rule on page 203.
Maximum Baggage ULD Rule on page 303.
Rule Criteria
Table: Create Hub Containers Rule Criteria

Market
Destination
Aircraft
Subtype
Flt No Range 32 To specify the flight number range, click on and select
222 Edition 8.5


LH - Long-haul
SH - Short-haul
Template
8 CF - Charter
Flight Type
DF - Domestic2
SF - Shuttle
CO - Cargo
Day of Week 4
and Tuesday).
2
Rule Contents
Table: Create Hub Containers Rule Contents
Field Explanation
Minimum Enter the minimum number of transfer bags required before a hub
Number of Bags container is created.
Mandatory.

At least 10 transfer bags for a specific onward flight before a hub container is
created for that flight.
224 Edition 8.5

Deadload Uplift Offload Message Parameter

Selection Rule
Rule Description
This rule is valid for the Deadload Uplift/Offload Message (DUO) document or
message type only.
Using this rule, you define the parameter codes, the type of commodity and
whether the offload is due to a disruption or a regular offload. This allows you to
route the DUO message according to the type of offload and commodity.
Note: There is no relationship between this rule and the offload reason codes
defined in the Carrier > General > Offload Reasons tab in DBM.
Related Rules
The parameters you define in this rule are used to route the DUO document or
message in the following rules:
Rule Criteria
Table: Deadload Uplift/Offload Message Parameter Selection Rule Criteria
Operating The two-character carrier code. Mandatory.

0
Carrier
Market
Destination
2
Terminal routed.
Inbound The arrival airport terminal where the document is routed.
2
Terminal
1

Rule Contents
Table: Deadload Uplift/Offload Message Parameter Selection Rule Contents
Field Explanation
Action The action that caused the offload.

Select from the drop-down list:
DSRP Disruption. Flight leg cancelled or routed to an
alternative destination.
OFF All types of offload, except those covered by a disruption
(action DSRP).
Blank All types of offload, including disruptions.
Commodity The commodity, or commodity and sub-commodity type, as defined
in Carrier > General > Commodity Subtype in DBM.
Examples: C, CM, M, MX.
You must enter a value in at least one of the Action or Commodity
fields.
Parameter The code you wish to define, to be used in the Documentation Type
Facility Routing and Outbound Teletype Message Delivery rules, up
to 10 characters. Mandatory.
226 Edition 8.5


In the example below, three parameters have been defined:
Parameter CDIS defines a DUO message for offloads due to disruptions for
cargo (commodity type C).
Parameter COFF defines a DUO message for offloads due to regular offloads
for cargo (commodity type C).
Parameter CALL defines a DUO message for offloads due to all types of
offloads for cargo (commodity type C).

Using the Documentation Type Facility Routing and Outbound Teletype Message
Delivery rules, you can route the DUO message according to the type of offload
and the type of commodity offloaded. For example, DUO messages that include
offloaded cargo can be sent to the email address of the cargo agent.

DG/SL Conflicts Rule

Rule Description
This rule defines for a DG/SL code, class, sub-class or DG/SL group:
Preferred and prohibited locations.
Maximum weights per location.
Conflicts.
Adjacency checks with other DG/SL types.
Adjacency checks are performed on containerised aircraft only, to ensure that
ULDs containing conflicting DG/SL items are not placed in adjacent positions.
Note: Adjacency checks do not apply to adjacent ULDs types that are
defined as closed in the Carrier > General > ULD Type tab in
DBM.
Example: Carrier > General > ULD Type in DBM
To use a DG/SL group in the rule, you must first create the DG/SL group in the
Carrier > General > DGSL Groups tab in DBM.
If any DG/SL conflicts defined in the rule are found on a flight, Flight Management
displays a warning message to the Load Controller. Mandatory conflicts must be
resolved, and advisory conflicts must be acknowledged.
Related Rules
The following rules also relate to DG/SL checks on a flight:
DG/SL Maximum TI Rule on page 234.
DG/SL TI Maximum Height Rule on page 239.
228 Edition 8.5

Rule Criteria
Table: DG/SL Conflicts Rule Criteria
Operating Carrier 0 Airline code.

Market Origin 0 Mandatory. The market of the flight origin.
Market
0 Mandatory. The market of the flight destination.
Destination
Registration 4
Flight No. Range
1 format DDMMMYY.
Effective To
Rule Contents

Table: DG/SL Conflicts Rule Contents
Field Explanation
Code/(Sub)Class/ A DG/SL code, class, sub-class or group to which the

Group conflicts apply.
DG/SL codes, classes and sub-classes must be defined in
the Carrier > General > DGSL Codes tab in DBM.
DG/SL groups must be defined in the Carrier > General >
DGSL Groups tab in DBM.
Click on New Row to enter a code.
Code/(Sub)Class/ The DG/SL to which the conflicts apply.
Group (middle panel) This field is displayed when you click on the
Code/(Sub)Class/Group field in the left panel of the screen.
Preferred Locations One or several preferred locations for the DG/SL selected,
separated by a comma.
Examples: CPT1,CPT2,52,HOLD-AFT,11L.
Prohibited Locations One or several prohibited locations for the DG/SL selected,
separated by a comma.
Examples: CPT1,CPT2,52,HOLD-AFT,11L
You cannot enter the same location in the Preferred
Locations and Prohibited Locations fields.
Maximum weight per location applies to the DG/SL selected in the
Code/(Sub)Class/ Group field.
Location Click on New Row, then enter a location.
Example: CPT3.
Max Weight The maximum weight of the selected DG/SL in the location.
Adjacency Checks applies to the DG/SL selected in the Code/(Sub)Class/Group
field.
DGSL Code Click on New Row, then enter a DG/SL code for which
adjacency checks must be performed.
Example: ICE.
Conflicts defines which DG/SLs conflict with the DG/SL selected in the
Code/(Sub)Class/Group field.
Conflicting Click on New Row, then enter a DG/SL, class, sub-class or
Code/(Sub)Class/ DG/SL group code for which a conflict applies.
Group Example: ICE.
Location The location of the aircraft where the conflict applies.
Example: AIRCRAFT, HOLD-FWD, ULD, 52.
Mandatory.
Max Weight The maximum weight of the DG/SL in the specified location.
Advisory If not selected, the DG/SL conflict is a mandatory conflict.
When selected, the DG/SL conflict is an advisory conflict.
To create an advisory conflict alert only for the DG/SL
selected in the Code/(Sub)Class/Group field, leave the
Conflicting Code/(Sub)Class/Group field blank, and select
this field.
Note: The DG/SLs in the Code/(Sub)Class/Group table are displayed in

alphabetical order when you save the business rule.
230 Edition 8.5

The settings apply to the DG/SL code RNG (non-flammable, non-toxic gas).
The preferred location for RNG is bay/pallet position 11.

Maximum weights are defined for locations CPT3 and bay/pallet position 11.
Adjacency checks are performed with DG/SL codes BED (stretcher) and LHO
(human organs).
A list of DG/SL codes that conflict with RNG, in a particular location, and for a
maximum weight.
The conflicts with ICE, AVX and EAT are advisory conflicts. The conflicts with AVI,
BEH, MAE and BED are mandatory conflicts.


Load Distribution screen - example 1:
An icon is displayed when DG/SL conflicts exist on the flight an error icon for
mandatory conflicts, and a warning icon for advisory conflicts.
The load controller has selected to display mandatory conflicts.
The system displays the DG/SL conflict.

In this example, HUM (human remains) conflicts with AVI (live animal) in
bay/pallet position 45L.
The load controller must separate the DG/SLs to resolve this conflict, because it is
a mandatory conflict.
232 Edition 8.5

Load Distribution screen - example 2:
An icon indicates that DG/SL conflicts exist on the flight.
The load controller has selected to display advisory conflicts.
The system displays the DG/SL conflict.

In this example, AVI (live animal) conflicts with ICE (dry ice) in bay/pallet position
45L.
The load controller must select the Acknowledged check box and click on
Update, but separation of the DG/SLs is not mandatory.

DG/SL Maximum TI Rule

Rule Description
This rule defines, for an aircraft subtype, the maximum transport index (TI) of
DGSL deadload for a location in the aircraft, and the maximum transport index for
the aircraft.
Related Rules
The following rules also relate to DGSL checks on a flight:
DG/SL Conflicts Rule on page 228.
DG/SL TI Maximum Height Rule on page 239.
Rule Criteria
Table: DGSL Maximum TI Rule Criteria
Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 4
Flight No. Range
1 format DDMMMYY.
Effective To
Rule Contents
234 Edition 8.5

Table: DGSL Maximum TI Rule Contents
Field Explanation
Max T.I. The maximum transport index for the entire aircraft the
sum of the transport index for all DGSLs in the aircraft.
Location Type Select from the drop-down list:
Hold
Bay
Compartment
Location The hold, bay or compartment number.
Max T.I. The maximum transport index for the selected location.

In the example below, the DGSL with code RRE (radioactive material) exceeds
the maximum transport index for compartment 1. A message is displayed on the
Load Distribution screen. The load controller cannot approve distribution if the
transport index is exceeded.

DG/SL Notification Rule
Rule Description
This rule determines under what conditions the Load Controller receives a
notification when there are modifications to DG/SLs on a flight which occur after
the first reception of the cargo and passenger feeds, and up to the flight
departure.
For example, the Load Controller may only wish to receive notifications of DG/SL
modifications if the NOTOC has been issued, meaning a new NOTOC will be
required.
Modifications to a DG/SL that trigger a notification can be manual changes in
Flight Management, or updates received automatically from an external system,
including the check-in system.
Modifications to DG/SLs that trigger a notification include:
DG/SLs are added to the flight.
Changes are made to any of the fields related to an existing DG/SL, even
those not included in the NOTOC.
A DG/SL is moved in the load distribution.
A DG/SL is offloaded.
The notification to the Load Controller is as follows:
Dangerous Goods/Special Load information has been updated, a new NOTOC
will be required.
Rule Criteria
Table: DG/SL Notification Rule Criteria
Operating Carrier 0 Airline code. Mandatory.

Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 8
Flight No. Range
1 format DDMMMYY.
Effective To
236 Edition 8.5

Rule Contents
Table: DG/SL Notification Rule Contents
Field Explanation
Notification for Selected DG/SL

Notify Load Controller for all When selected, the Load Controller receives a
DG/SL updates notification of changes on all types of DG/SL, even
those not required for the NOTOC, according to
the conditions selected in the Notify Load
Controller panel.
Notify Load Controller for DG/SL When selected, the Load Controller receives a
updates which are mandatory on notification of changes of DG/SL that are defined in
NOTOC DBM on the DG/SL Codes tab as required for the
NOTOC, according to the conditions selected in
the Notify Load Controller panel.
Notify Load Controller
NOTOC not issued When selected, the Load Controller receives a
notification of DG/SL changes even if a NOTOC
document has not yet been issued for the flight.
Provisional NOTOC issued When selected, the Load Controller receives a
notification of DG/SL changes only if a provisional
NOTOC document has been issued for the flight.
Final NOTOC issued When selected, the Load Controller receives a
notification of DG/SL changes only if a final
NOTOC document has been issued for the flight.


For flights impacted by the rule above, the Load Controller receives the following
notification when a modification is made to a DG/SL that is required for the
NOTOC, after a provisional or final NOTOC has been issued:
Dangerous Goods/Special Load information has been updated, a new NOTOC
will be required
238 Edition 8.5

DG/SL TI Maximum Height Rule

Rule Description
This rule defines the maximum permitted height and transport index (TI) of
DG/SLs in an aircraft location, to ensure vertical separation of radioactive
material from the passenger deck.
When this rule is used, the DG/SL code defined in DBM must include the
transport index and height as mandatory items, to ensure that the Load Controller
enters these values into Flight Management for the DG/SL.
Example: Carrier > General > DGSL Codes Tab in DBM
For any specified location in the aircraft (aircraft, deck, hold, compartment or
bay/pallet position), that contains at least one DG/SL with a transport index and
height specified, Flight Management makes the following checks and displays a
warning message when the settings in the rule are exceeded.
The height of a DG/SL with a transport index must not exceed the maximum
height allowed for that aircraft location, or the transport index must not
exceed the value allowed for the DG/SL's height.
The sum of the transport index of all DG/SLs in the aircraft location must not
exceed the transport index allowed for the tallest DG/SL in the aircraft
location.
Related Rules
The following rules also relate to DG/SL checks on a flight:
DG/SL Conflicts Rule on page 228.
DG/SL Maximum TI Rule on page 234.

Rule Criteria
Table: DG/SL TI Maximum Height Rule Criteria
Operating Carrier 0 The carrier code.

Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 4
Flight No. Range
1 format DDMMMYY.
Effective To
Rule Contents
240 Edition 8.5

Table: DG/SL T.I. Maximum Height Rule Contents
Field Explanation
Locations (table) In the Locations table, click on New Row.

Enter an aircraft location to which the height limits apply,
using the following formats:
AIRCRAFT
DECK-xxx
HOLD-xxx
Where xxx is the name of the deck or hold, as defined in
the Carrier & Aircraft > Holds > Deck, Holds & Doors
tab in DBM.
CPTx
Where x is the number of the compartment, as defined in
the Carrier & Aircraft > Holds > Compartments tab in
DBM.
Bay/pallet position
As defined in the Carrier & Aircraft > Holds >
Bay/Pallet Positions tab in DBM.
Examples:
AIRCRAFT
DECK-Lower
HOLD-Aft
CPT1
12L
Locations (field) The aircraft location code to which the height and transport
index limits apply.
Note: This field is precompleted when you select on a
location in the Locations table and press Tab.
Height In the Height/T.I. table, click on New Row.
T.I. Enter the height of the DG/SL and the maximum transport
index for the specified height.
Note: The height is not related to a measurement unit,
such as centimetres or inches. Flight Management
checks the value in the Height field for the DG/SL
on the Deadload Details screen, and compares it
to this value.
Repeat for all the TI ranges for this location in the aircraft.
Note: In the Locations table, define each location in the aircraft that has
requirements for DG/SL TI maximum height.


The rule below defines the maximum transport index by height of DG/SL for each
of the five compartments of the aircraft.
For compartment 2 (selected in the Locations table), the system first determines
the highest height allowed for DG/SLs with TI.
It then calculates the sum of all the TIs in the compartment. For DG/SLs up to a
height of up to 20, a maximum TI of 7 is allowed. For DG/SLs with a height above
20 and up to 30, a maximum TI of 6 is allowed, and so on. The maximum height
of a DG/SL in this compartment is 80, and it can have a maximum TI of 1.

Flight Management checks for each location defined in the rule that the transport
index or maximum height of the DG/SL is not exceeded.
If there is more than one DG/SL with a transport index in the same location, the
system checks that the sum of all transport indexes is not exceeded, based on
the transport index allowed for the highest DG/SL in the location.
Error messages are displayed to the load controller on the Load Distribution
screen. For example:
If the maximum height of a DG/SL with a transport index for the aircraft
location is exceeded:
If the DG/SL exceeds the maximum transport index allowed for the aircraft
location:
If the sum of the transport indexes in the aircraft location exceeds the
transport index allowed for the tallest DG/SL in that location:
242 Edition 8.5

Document Type Facility Routing Rule

Rule Description
This mandatory rule defines the print location to which the selected document
type is to be routed. The system validates that the facility categories and the
facility ID are valid targets for these locations for print output. Keywords can be
used to determine the facility category and ID.
The document types are stored in DBM in the Carrier > General > Doc Type
Rules tab.
Example: Carrier > General > Doc Type Rules Tab in DBM
For a list of codes see Document and Message Types on page 376.
Related Rules
For the Deadload Uplift/Offload (DUO) Message only, the Deadload Uplift
Offload Message Parameter Selection Rule on page 225 is used to define a
parameter to route the DUO message according to offload type and
commodity type.
The Outbound Teletype Message Originator Rule on page 319 defines the
originator address of teletype messages per document type.

Rule Criteria
Table: Document Type Facility Routing Rule Criteria
Operating The two-character carrier code.

Carrier Mandatory.
0 In a ground handling solution, when the rule is created in
the reference data of the ground handling organisation, you
can optionally enter ALL to represent all handled airlines.
Market
Destination
The aircraft subtype, as defined in DBM.
Aircraft 32
Subtype
16
Terminal routed.
Inbound The arrival airport terminal where the document is routed.
8
Terminal
Document/ The three-letter code of the document to be printed, for
Message example, LIR. These codes are stored in DBM in Carrier >
Type General > Doc Type Rules. Mandatory.
Note: You can enter only one document/message type
code per rule.
0
For a list of codes see Document and Message Types on
page 376.
Note: It is also possible to specify any of the Customer
Management pre-defined lists and Onboard
Service lists.
Flight No.
Used for the DUO Deadload Uplift/Offload Message only.
Document Enables you to specify when the DUO message is sent,
Parameter according to the type of offloaded commodity, and whether
the offload is due to a disruption, or is a regular offload.
16
The document parameter you enter must be defined in the
Deadload Uplift Offload Message Parameter Selection rule.
For more information see Deadload Uplift Offload Message
Parameter Selection Rule on page 225.
LH - Long-haul
SH - Short-haul
Template
2 CF - Charter
Flight Type
DF - Domestic
SF - Shuttle
CO - Cargo
Effective
1 The starting and ending effective date of this row, in the
From
format DDMMMYY.
Effective To 1
244 Edition 8.5

Rule Contents
The rule contents section contains a table and a separate row is needed for each
print location type. For example if a document needs to be printed to a fax
number and to a full location (A/LHR/T/2/GTE/1) then two rows are needed: one
for the fax number and one for the full location.
To add a row in the table below the current row, click on the New Row button. To
delete a selected row, click on the Delete Row button.
Table: Document Type Facility Routing Rule Contents
Field Explanation
Dep (Departure) Select this check box if the document is to be printed at the
Port/Term departure port or terminal. This is an optional check box.
See Note 1.
Arr (Arrival) Select this check box if the document is to be printed at the arrival
Port/Term port or terminal. This is an optional check box.
See Note 1.
A/C Discrim The airport or city discriminator. Select from the drop-down menu.
- A - Airport
- C - City
This is an optional field.
See Note 2.
Airport/City The airport or city code. This is a conditional field.
See Note 2.
T/B Discrim The terminal or building discriminator. Select from the drop-down
menu.
- T - Terminal
- B - Building
This is an optional conditional field.
See Note 2.
Term/Build The terminal or building code. This is an optional conditional field.
See Note 2.
Facility The category of document printer. For example, GTE (Gate). This is
Category a conditional field.
See Note 1 and Note 2.
Facility ID The ID of the document printer. For example, A21. This is an
optional conditional field.

Field Explanation
PRT Owner The printer owner. Select from the drop-down menu.
FM GH - Flight Management Ground Handler
CM GH - Customer Management Ground Handler
OP - Operating Carrier
This is a conditional field.
Keyword The location keyword. Select from the drop-down menu.
ACLOCN - Aircraft Location
GALOCN - Gate Location
ACLOCN+R - Aircraft Location with re-routing to the Gate
Location if the Aircraft Location does not exist.
This is an optional field. See Note 3.
Mandatory Optional.
See Note 3.
ACARS Optional.
Select this check box to send the document via ACARS.
See Note 3.
Local Copy Optional.
Select this check box to send the document to a local printer.
See Note 4.
Fax Optional.
Enter the fax number to which the document is to be sent.
See Note 4.
Email Optional.
Select this check box to send the document to an email address.
See Note 4.
Note 1: If you use the Dep Port/Term option or Arr Port/Term option, the
following fields must be completed:
- Facility Category
- Facility ID (optional)
- PRT Owner
All other fields are disabled.
Note 2: If you use the A/C Discrim option, the following fields must be
completed:
- Airport/City
- T/B Discrim (optional)
- Term/Build (optional)
- Facility Category
- Facility ID (optional)
- PRT Owner
All other fields are disabled.
246 Edition 8.5

Note 3: If you use the Keyword or ACARS option, the Mandatory check box can
also be used. All other fields are disabled.
Note 4: If you use any of the Local Copy, Fax or Email options, all other fields
are disabled.

Document type FEA (ACARS Final Loadsheet (Extended) to be sent to aircraft
location (ACLOCN), ACARS and Local Copy for 6X World market flights.

ACARS Final Loadsheet (Extended) to be sent to aircraft location (Gate), aircraft
and local copy.
Example: Flight Management - Documents Screen

Domain Rule
Rule Description
This mandatory rule is used for all flights with a Weight and Balance element, to
specify the Load Control domain to which a flight belongs.
Note: In a ground handling solution, this rule must be defined in the reference
data of the ground handling organisation. See The Domain Rule in a
Ground Handling Solution below.
The domain owner and name must match exactly the domain owner and name
stored in the Staff > Domains tab in the DBM to work correctly in Flight
Management.
Example: Staff > Domains Tab in DBM
The Domain Rule in a Ground Handling Solution

When the Flight Management ground handling functionality has been activated,
two scenarios can apply.
Scenario A: If the Ground Handling rule has not been created, the system refers
to the Domain rule in the reference data of the operating carrier. The domain
owner can be set to any organisation.
Scenario B: If the Ground Handling rule has been created, the system refers to
the Domain rule in the reference data of the ground handling organisation. The
domain owner of a flight defined in the Domain rule must match the ground
handling organisation defined in the Ground Handling rule, as shown in the
example below.
248 Edition 8.5

Example: Operating Carrier 8Z and Ground Handler 6X for flights from NCE
Ground Handling Rule defines 6X as ground handler for 8Z flights departing
from NCE.
Domain Rule assigns 8Z flights from NCE to 6X's NCE LCO domain.

Rule Criteria
Table: Domain Rule Criteria
Operating The two-character code for the operating airline.

Carrier Mandatory.
0 In a ground handling solution, when the rule is created in
the reference data of the ground handling organisation,
you can optionally enter ALL to represent all handled
airlines.
Market
Destination
64 The two-character code for the crew organisation.

Crew Owner
Flight No. Range
16
Subtype
8
example, 6X-XYZ.
4
and Tuesday).
2 format HH:MM.
STD To
1
250 Edition 8.5

Rule Contents
Table: Domain Rule Contents
Field Explanation
Domain Owner The two-character code of the owner organisation of the domain.
For a non-handled airline, the airline's own code.
In a ground handling solution, the code of the ground handling
organisation. It must match the ground handling organisation
defined by the operating airline in the Ground Handling rule.
The domain owner must always match exactly the domain owner
stored in the Staff > Domains tab in DBM.
Domain Name The name of the domain, for example, AMA LHR.
The domain name must match exactly the domain name stored in
the Staff > Domains tab in DBM. Mandatory.

Carrier 6X flight 6028 to be handled in Flight Management under the domain
AMA LHR owned by 1A.


Domain set to 1A-AMA LHR on the Departure Plan Details screen for flight
6X6028.
Example: Flight Management - Departure Plan Details Screen
252 Edition 8.5

Dynamic Capacity Calculation Rule
Rule Description
This rule determines whether the capacity calculation is to be automatically
updated when this rule is called by the Update Passenger Information or Get
Passenger Details use cases.
Note: Dynamic capacity calculation is not performed for flights with the Gross
Weights (GW) baggage type.
Rule Criteria
Table: Dynamic Capacity Calculation Rule Criteria

Flight Group
4
1
Rule Contents
Table: Dynamic Capacity Calculation Rule Contents
Field Explanation
Dynamic Capacity Calculation Select this check box if a dynamic capacity

calculation is required.

Equipment Configuration Rule

Rule Description
This rule defines equipment commodities that are automatically created during
the flight creation process, when the rule definitions, such as destination and ULD
type, are valid for the flight. The equipment commodities are created with
commodity code E and estimated weights. Depending on the rule setting, the
equipment commodity can be included in the dry operating weight (DOW) and dry
operating index (DOI), or can be included in the traffic load.
The estimated weights must be finalised during the load control or ramp process.
If estimated weights exist at Approve Distribution, a high priority message is
displayed to the Load Controller. The Load Controller can modify the equipment
commodity in Flight Management.
Rule Criteria
Table: Equipment Configuration Rule Criteria
Mandatory.
Carrier 0
The two-character code of the operating carrier.
Mandatory.
Market Origin 0
Market Mandatory.
0
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
1 format DDMMMYY.
Effective To
254 Edition 8.5

Rule Contents
Table: Equipment Configuration Rule Contents
Field Explanation
Enable Equipment Select to activate the creation of equipment commodities

Autocreation (commodity code E) during the flight creation process.
Equipment
These fields are enabled when the Enable Equipment Autocreation checkbox is
selected.
Click on New Row to enter data into these fields.
Description A description of the equipment commodity. Mandatory.
Destination The 3-letter city or airport codes of the destination.
If not entered, the equipment commodity is created for all
destinations.
Optional.
Net Weight Weight of the equipment.
This weight is set to Estimated in the Deadload screen in
Flight Management.
Mandatory.
Load Type Select from the drop-down list.
Example: ULD, Bulk, Barrow (or barrow code as defined in
the Carrier Parameters tab in DBM).
Mandatory.
ULD Type Mandatory when the Load Type field is ULD or Barrow.
Example: AKE.
Location The location of the equipment commodity on the aircraft,
used to locate the commodity. Optional.

Field Explanation
Include in Traffic Load Select to include the weight of the commodity in the Traffic
Load of the flight.
If not checked, the commodity is included in the dry operating
weight (DOW) and dry operating index (DOI) of the flight.
Included DGSL
To include any DS/SLs in the Equipment commodity, click on New Row below the
Included DGSL panel. Enter the code and weight of the DG/SL. The weight is included
in the net weight of the equipment commodity.
Note: If the DGSL code is not valid, the flight creation process does not fail. The
equipment commodity is created, but without the DGSL code. The weight of
the DGSL is removed from the net weight of the commodity.

The following rule defines two equipment commodities: one for Flight Spares of
200 kg, one for Breathing Apparatus of 20 kg (with 10 kg DG/SL), both to be
loaded in the bulk hold. The Include in Traffic Load fields are not checked,
therefore the weight of both equipment commodities are to be included in the
DOW/DOI of the flight.

The E (equipment) commodities for Flight Spares of 200 kg and Breathing
Apparatus of 20 kg are automatically created, and included in the dry operating
weight. The E commodities are displayed on the Deadload screen, with the Est
(estimated weight) indicator selected.
256 Edition 8.5

Express Cargo Commodity Rule
Rule Description
This rule is used to determine which sub-commodities of cargo should be
considered as express cargo. It is displayed in a separate field, Inc. Express
Cargo, on the Zero Fuel Weight screen in Flight Management.
If this rule is not created, the Inc. Express Cargo field will not be displayed for the
flight leg.
Rule Criteria
Table: Express Cargo Commodity Criteria
Mandatory.
Market Origin 0
Market Mandatory.
0
LH - Long-haul
SH - Short-haul
Template
2 CF - Charter
Flight Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight Nb To specify the flight number range, click on and select

4
1

Rule Contents
Table: Express Cargo Commodity Rule Contents
Field Description
Cargo Sub Commodity (C) Mandatory.

Enter the cargo sub-commodity to be considered as
express cargo.
Default Weight Optional.
Enter the default weight of this sub-commodity to be
created for a flight leg.
258 Edition 8.5


For All 6X World Market flights, the cargo sub-commodity X is displayed as
express cargo with a default value of 500 kgs. This field can be updated by the
Load Controller.
Example: Express Cargo Field on the Zero Fuel Weight Screen

Flight Departed Status Rule

Rule Description
This rule determines whether the general status of a flight is set to General
Departed (GD) when the ATD Off Blocks or the ATD Airborne movement
message is received by Flight Management.
Note: An ATD Off Blocks message is mandatory, whereas an ATD Airborne
message is optional.
Rule Criteria
Table: Flight Departed Status Rule Criteria
Mandatory.
Market Origin 0
Market Mandatory.
0
Flight Group
Registration 2
LH - Long-haul
SH - Short-haul
Template Flight
1 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
1 format DDMMMYY.
Effective To
260 Edition 8.5

Rule Contents
Table: Flight Departed Status Rule Contents
Field Explanation
Flight General Status Select which type of ATD received by Flight Management
set to Departed when: sets the general status of a flight to Departed (GD)
ATD Off Blocks
ATD Airborne

The ATD times received are displayed in the Departure Control screen.
In the example business rule above, the flight's general status is set to GD
(General Departed) when an ATD Airborne movement message is received, but
not when an ATD Off Blocks is received.

If an ATD Off Blocks is received without an ATD Airborne for a flight, and the rule
is set up to set the General status to GD when an ATD Airborne is received,
Flight Management stores the ATD Off Blocks time in the Departure Plan, but
does not set the General status to Departed.
If the Load Control status is not LSF (loadsheet finalised), LX (load control
cancelled) or LI (load control ignored) when the ATD is received, Flight
Management sends a medium priority message to the Load Controller.
Example:
An ATD Off Blocks of [time] has been received. Load Control status is not LSF.
262 Edition 8.5

Flight Departure Minimum Status Required Rule

Rule Description
This rule determines the minimum boarding status a flight must have before its
general status can be set to Flight Departed (GD).
It is used, for example, to ensure that customers who have not boarded a flight do
not have their e-ticket status set to Flown when the flight has departed.
If the flight's boarding status is not Closed (BC) or Ignored (BI), this business rule
is checked when a request to set the flight's general status to Departed is
received from:
An external operations system.
A disruption message from Alta Inventory.
A manual update of the flight status and ADT in the Departure Control or
Customer Management applications.
If the boarding status of the flight is lower than the status defined in the business
rule, then the request is rejected, and an error message is displayed. A high
priority notification is also sent to the Load Controller.
Rule Criteria
Table: Flight Departure Minimum Status Required Rule Criteria
Operating Airline 0
Market
0 Mandatory. The market of the flight destination.
Destination
Flight No. Range
Departure
8
Terminal
Enter one of the following codes:
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Day of Week 2
1 format DDMMMYY.
Effective To

Rule Contents
Field Description
Minimum Boarding Status No Check

The boarding status of the flight is not
checked.
Open
The boarding status of the flight must be Open
(BO) or Closed (BC) before the general status
can be set to Departed (GD).
Closed
The boarding status of the flight must be
Closed (BC) before the general status can be
set to Departed (GD).

In the following rule, the flights impacted by the rule must have a boarding status
of Closed (BC) before the general flight status can be set to Departed (GD).
264 Edition 8.5


If the Load Controller attempts to set the flight general status to Departed and
enter an ATD in the Departure Control application, the request is rejected and an
error is returned. A high priority notification is also sent to the Load Controller.
Impact on Customer Management

The boarding status must be set to Closed (BC) in Customer Management before
the flight general status can be set to Departed (GD).
When boarding has been closed in Customer Management, BOARDED is
displayed in the Flight Status column of the Flight List screen.

Flight Event Notification Data Rule
Rule Description
This rule determines which flight events in Flight Management (FM) or Customer
Management (CM) trigger a DCS event notification message to be sent to an
external system
Related Rules
The address to which the event notification is sent is stored in the Flight Event
Notification System field in the Out of Scope System Address Rule on page 322.
Rule Criteria
Table: Flight Event Notification Data Rule Criteria

Market
Destination
Event Type The three-letter code for the flight event.
For example, LLO - Load Control Status Open.
0 Mandatory.
Refer to the flight event codes listed in Departure
Control Event and Activity Codes on page 377 for a
list of codes.
IATA Service The IATA service type code. Example: J for a
8
Type passenger flight.
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
1
266 Edition 8.5

Rule Contents
Table: Flight Event Notification Data Rule Contents
Field Explanation
Event Occurred Select to trigger a DCS event notification message to be

sent to an external system when the event (defined in the
Event Type field of the rule) occurs for the flight.

Flight Handling Type Rule

Rule Description
This mandatory rule specifies whether a flight is handled in Alta for Flight
Management, Customer Management, or both.
You can also specify whether the flight is linked to an external system for the non-
Alta managed part of the flight, if appropriate.
Rule Criteria
Table: Flight Handling Type Rule Criteria

Market
Destination
ACV 16 Aircraft configuration version.
Flight No. To specify the flight number range, click on and select
8
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Types
DF - Domestic
SF - Shuttle
CO - Cargo
2
Day of Week 1 The days that this row applies to, such as 12 (for Monday
and Tuesday).
268 Edition 8.5

Rule Contents
Table: Flight Handling Type Rule Contents
Field Explanation
Alta Departure Control

Weight Select to specify that this flight is handled in Alta Departure Control for
and Flight Management.
Balance
Check In Select to specify that this flight is handled in Alta Departure Control for
Customer Management.
Other Systems
Weight Select to specify that the flight is handled in an external system for weight
and and balance, then enter the system address of the external system.
Balance Optional. If you select this check box the system address is mandatory.
Check In Select to specify that the flight is handled in an external system for check-in,
then enter the system address of the external system.
Optional. If you select this check box the system address is mandatory.


Flight to be handled in Alta Departure Control - Flight Management and
Customer Management. Weight and Balance and Check In check boxes both
selected.

Load Control Open status (LO) and Acceptance Open status (AO) on the Shift
Summary screen.
Note: If the flight was Check-in only the Load Control status would be LI
(Load Control Ignored).
If the flight was Weight and Balance only the Acceptance status would
be AI (Acceptance Ignored).
Example: Flight Management - Shift Summary
270 Edition 8.5

Forecast ZFW Dependency Rule
Rule Description
This rule determines whether booked passenger figures, the external cargo feed,
or both of these, must have been received before Flight Management sends the
first forecast zero fuel weight (FZFW) to an external flight planning system, when
Send Forecast Zero Fuel Weight is an activity triggered in the departure plan. If
the figures have not been received, the FZFW is not sent, and a notification is
sent to the Load Controller.
Note: The rule is also applied if the Load Controller clicks on the Send
Forecast Zero Fuel Weight activity to trigger it.
The rule applies to the first edition of the FZFW only. It is ignored for subsequent
editions, and when the Load Controller manually sends the forecast ZFW from
the Zero Fuel Weight window in Flight Management.
Related Rules
If set in the rule criteria, the IATA service type code must match the code defined
for the flight in the IATA Service Type Rule on page 276.
Rule Criteria
Table: Forecast ZFW Dependency Rule Criteria
Mandatory.
Operating Carrier 0
Mandatory.
Market Origin 0
Market Mandatory.
0
Registration 16
IATA Service The IATA service type, as defined in the IATA Service
8
Type Type rule.


LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
1 format DDMMMYY.
Effective To
Rule Contents
Table: Forecast ZFW Dependency Rule Contents
Field Explanation
Check if Passenger Figures When selected, booked passenger figures must

Feed is Received exist before the first edition of the Send Forecast
Zero Fuel Weight activity can be triggered in the
departure plan.
Check if External Cargo Figures When selected, an external cargo feed must have
Feed is Received been received before the first edition of the Send
Forecast Zero Fuel Weight activity can be triggered
in the departure plan.
272 Edition 8.5


In the rule below, booked passenger figures must exist before the first edition of
the Send Forecast Zero Fuel Weight activity can be triggered in the departure
plan. The system does not check whether the external cargo feed has been
received.

If the passenger figures feed has not been received, and the first edition of Send
Forecast Zero Fuel Weight is triggered from an activity in the departure plan, the
Load Controller receives the following high priority message:
Sending of FZFW has been requested but cannot be sent. Passenger figures
have not been processed for the flight leg.
The FZFW is not sent.

Ground Handling Document Format Rule
Rule Description
This rule determines whether the carrier document format or the ground handler
document format is to be used, where applicable.
Note: This rule is called from the reference data of the ground handling
organisation.
Related Rules
This rule works in conjunction with the Ground Handling Rule on page 66, which
determines the handling organisation or carrier responsible for a ground handled
flight.
Rule Criteria
Table: Ground Handling Document Format Rule Criteria

Mandatory.
Operating Carrier 0
You can optionally enter ALL to represent all handled
airlines.
Market
Destination
Document Type The 3-letter code of the document to be printed, for
64 example, FLS. These codes are stored in DBM in the
Carrier section under Doc Type Rules.
Flight No. Range
16
Terminal routed.
4
2 the format HH:MM.
STD To
1
274 Edition 8.5

Rule Contents
Table: Ground Handling Document Format Rule Contents
Field Explanation
Ground Handler Format Select one of the option buttons to determine which
organisation 's format is used for creating Flight
Operating Carrier Format Management documents and messages.

In the following business rule, the ground handling organisation 6X has defined
that all the flights it handles for 8Z departing from NCE airport are created using
the document or message format of airline 8Z.

IATA Service Type Rule

Rule Description
The IATA Service Type rule determines which IATA Service Type category
(passenger or cargo only) applies to a flight, and validates the IATA service type
sent by Alta Inventory.
The IATA service type is mandatory for flights in Alta Departure Control. If the
rule does not exist, flights default to the passenger service type if no rule is
present.
Related Rules
This rule works in conjunction with the Template Flight Type rule to determine the
Template Flight Type for a flight based on the IATA Service Type, if applicable.
See Template Flight Type Rule on page 349.
Rule Criteria
Table: IATA Service Type Rule Criteria

The IATA service type code. For example, J for a
IATA Service Type 0
passenger flight. Mandatory.
Rule Contents
Table: IATA Service Type Rule Contents
Field Explanation
IATA Service Type Category Select from the drop-down menu:

Passenger Flight
Cargo Operation Only Flight
Mandatory.
276 Edition 8.5


IATA Service Type 'J' set as 'Passenger Flight' on 6X flights.

Inhibit ACARS Preliminary Loadsheet Creation

Rule
Rule Description
This rule determines whether an ACARS preliminary loadsheet can be issued,
based on baggage variation acknowledgement, onload finalised status, fuel
status, and with activation, acceptance status.
Related Rules
You can also inhibit the provisional or final loadsheet creation for a flight using the
following rules:
Inhibit Provisional Loadsheet Creation Rule on page 293.
Inhibit Final Loadsheet Creation Rule on page 287.
Rule Criteria
Table: Inhibit ACARS Preliminary Loadsheet Creation Criteria
Operating Carrier 0 Mandatory. The two-character carrier code.

Market Mandatory.
0
Flight No. Range
LH - Long-haul
SH - Short-haul
Template Flight
8 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Terminal 4
1 format DDMMMYY.
Effective To
278 Edition 8.5

Rule Contents
Table: Inhibit ACARS Preliminary Loadsheet Creation Rule Contents
Field Description
Select the check boxes to inhibit the issue of a ACARS provisional loadsheet for the
following:
Inhibit if Baggage Variation A baggage variation is a difference between the
not acknowledged baggage values provided by the check-in application
and the final baggage values recorded in Flight
Management, because the number of accepted bags
from check-in does not match the number recorded by
the ramp agent.
In Flight Management, the load controller can enter
and acknowledge a baggage variation from the
Baggage Variation window, available from the
Accepted Traffic Load window or the Passenger
screen.
Inhibit if Onload not finalised The onload status is set to finalised by the check-in
agent in Customer Management, after acceptance has
been finalised, and onload passengers have been
confirmed.
If the link to check-in is down, the load controller can
set the onload status to Final in Flight Management on
the Manual Passenger Entry window, available from
the Passenger screen.
Onload Finalised status ensures that all onloaded
passengers are taken into account in the preliminary
loadsheet, for greater accuracy of the fuel order.

Field Description
Inhibit on Fuel Figure Status Select to inhibit for any of the following fuel statuses:
Historical
Provisional
Final
Inhibit on Acceptance Status Select to inhibit for any of the following acceptance
statuses:
Ignored (AI)
Not Open (AN)
Open (AO)
Gate Only (AG)
Closed (AC)
Finalised (AF)
Suspended (AS)

In the rule below, an ACARS preliminary loadsheet cannot be produced if the
onload status is not finalised, or if the fuel figure status is historical.

If the load controller or an activity tries to produce an ACARS provisional
loadsheet when fuel figures are Historical, an error message is displayed, and
the activity fails. For example:
ACARS Preliminary Loadsheet cannot be produced when Fuel Figure Status =
Historical.
280 Edition 8.5

Inhibit Approval of Distribution Rule

Note: In July 2016 the Inhibit Approval of Distribution rule will be renamed
Approve Distribution rule.
Rule Description
This rule is called at Approve Distribution, and determines the conditions when a
load distribution cannot be approved. For example, when the cargo status is
provisional.
Related Rules
Process External Cargo Feed Message Rule on page 327 controls the cargo
release status.
Autoload Distribution Options Rule on page 196 can be used to enforce no-fit
visibility from the door in the Autoload process.
Rule Criteria
Table: Approve Distribution Rule Criteria

Market
Destination
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No.
1

Rule layout with activation (Autoload Cycle 3):
Rule Contents
Table: Approve Distribution Rule Contents
Field Explanation
Internal Cargo Status Select to inhibit Approve Distribution if the internal cargo
External Cargo Status Select to inhibit Approve Distribution if the external cargo
No-Fit Not Visible
from Door Select to inhibit Approve Distribution if no-fit container
positions are not visible from the door of the aircraft.
A no-fit position is a containerised bay or pallet position that
Visible from the door means that a ULD can be loaded from
the door to the available ULD groups without moving any
other ULD.
Unoccupied bay/pallet positions of the following types are
allowed in the load distribution:
Positions set to No-Fit manually by the Load
Controller.
Note: Unoccupied pallet positions are excluded from
the no-fit visibility enforcement.
282 Edition 8.5

For flights impacted by the rule, approval of distribution is inhibited if the external
cargo status is Provisional.
If Approve Distribution is attempted, the following error message is displayed:
Approve distribution cannot be performed. The External Cargo status is
incomplete.

Inhibit EOP Creation Rule
Rule Description
The end of procedure (EOP) message is sent by Flight Management to the
cockpit to inform the crew that operations on the ground are closed and finalised.
The airline must be using the enhanced Last Minute Change (LMC) procedure,
and no longer be in LMC mode.
An EOP message is sent when the flight has the following statuses:
Table: Requirements for the EOP Message
Flight Status or Condition Must Be
Load Control LSF (loadsheet finalised)

Ramp RF (ramp finalised)
Fuel Figures Final
Acceptance AC (acceptance closed)
Or:
AF (acceptance finalised)
Depending on the setting in the Inhibit EOP Creation
business rule.
Boarding Boarding closed, or passenger figures have been
manually finalised.
In addition:
The Captain's Validation (VAL) Message has been received for the latest
version of the Final Loadsheet.
No previous End of Procedure message has been sent for the current edition
of the Final Loadsheet.
If set in the Shift Summary Layout business rule, the Shift Summary views can
display the transmission status, and time the End of Procedure message was
sent.
Related Rules
In the Shift Summary Layout Rule on page 339, you can choose to display the
EOP Sent status on the Shift Summary views in Flight Management.
284 Edition 8.5

Rule Criteria
Operating Carrier
Market Origin
Market Destination
Select from the following:
LH - Long-haul
SH - Short-haul
Template Flight
2 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
Effective To
Rule Contents
Field Explanation
Inhibit EOP creation at... When selected, the EOP message can only be
Acceptance Closed (AC) created when the flight's acceptance status is AF
(acceptance finalised).
The EOP cannot be created at Acceptance Closed
(AC).


For the flights impacted by the rule, the EOP message can only be created when
the flight's acceptance status is AF (acceptance finalised).
286 Edition 8.5

Inhibit Final Loadsheet Creation Rule
Rule Description
This rule determines the conditions when a final loadsheet cannot be created for
a flight.
Related Rules
The Fuel Density Rule on page 129, for the fuel density applied to a flight from
the business rule.
The default fuel density for an airline is stored in DBM.
Example: Carrier > General >Detail Tab in DBM
Rule Criteria
Table: Inhibit Final Loadsheet Creation Rule Criteria

0
Mandatory.
Market Origin 0
Market Mandatory.
0
Template Flight LH - Long-haul
Type SH - Short-haul
CF - Charter
16
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
8 Click on and select the Flight Group Keyword or the
Flight Range.

2 format DDMMMYY.
Effective To
Rule Contents
Table: Inhibit Final Loadsheet Creation Rule Contents
Field Explanation
Inhibit final loadsheet creation if The load controller cannot create a final loadsheet
fuel density is carrier default if the fuel density for a flight has been derived from
the carrier default stored in DBM.
If the fuel density for a flight has been derived from
the Fuel Density rule, or if the load controller has
manually updated the fuel density, the final
loadsheet can be issued.
Inhibit final loadsheet creation if The load controller must acknowledge any
baggage variation is not baggage variations before issuing a final
acknowledged loadsheet.
Refers to CG Targeting parameters, for example,
Inhibit final loadsheet
for the A380 aircraft.
creation if Fuelling Status not
Complete The load controller cannot create a final loadsheet
if the CG Targeting parameters fuelling status is
not Complete.
Inhibit final loadsheet for the following selected statuses:
Ramp Status The load controller cannot create a final loadsheet
when the flight has any of the selected statuses.
Acceptance Status
Boarding Status
288 Edition 8.5


In the following rule, the load controller cannot create a final loadsheet if the fuel
density has been derived from the carrier's default fuel density stored in DBM. In
addition, the final loadsheet cannot be created unless the ramp status is
Provisional (RP) or Final (RF).

When the flight meets any of the conditions selected in the rule to inhibit the final
loadsheet, and the load controller attempts to issue a final loadsheet manually,
the error message is displayed on the current screen.
When the final loadsheet is triggered from an activity, the load controller receives
a very high priority message.
For example, the error message for fuel density is:
Creation of final loadsheet is not allowed when the current fuel density source
is the carrier default.
When the Inhibit final loadsheet creation if Fuelling Status not Complete option is
selected in the rule (A380 aircraft), the CG Targeting fuelling status must be set
to Complete (either manually or automatically) before the final loadsheet can be
issued.
The CG Targeting Parameters window, available from the Fuel screen in Flight
Management:

Inhibit Load Instruction Report Creation Rule
Rule Description
This rule determines what the Cargo Release Status must be before the load
controller can create the Loading Instruction Report (LIR).
Rule Criteria

Market
Destination
Type LH - Long-haul
SH - Short-haul
2 CF - Charter
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
1 format DDMMMYY.
Effective To
290 Edition 8.5

Rule Contents
Table: Inhibit Load Instruction Report Creation Rule Contents
Field Explanation
External Cargo Release The cargo release status must be Cargo Final
External before the load controller can create the LIR.
Internal Cargo Release The cargo release status must be Cargo Final
Internal before the load controller can create the LIR.

Both external and internal cargo release are selected.


The cargo status menu for the load controller is as follows:
The cargo release status displayed on the status bar is as follows:
The load controller can now create the LIR.
292 Edition 8.5

Inhibit Provisional Loadsheet Creation Rule

Rule Description
This rule determines whether a provisional loadsheet can be issued, based on
the fuel status of the flight.
Related Rules
This rule can be used in conjunction with theInhibit ACARS Preliminary
Loadsheet Creation Rule on page 278.
Rule Criteria
Table: Inhibit Provisional Loadsheet Creation Criteria

Market
Destination
LH - Long-haul
SH - Short-haul
Template Flight
8 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Terminal 4 The departure terminal of the flight leg.
1

Rule Contents
Table: Inhibit Provisional Loadsheet Creation Rule Contents
Field Description
Inhibit on Fuel Figure Status Select from the following to inhibit the issue of a
provisional loadsheet for the selected fuel status.
Historical
Provisional
Final
For all flights impacted by the rule, a provisional loadsheet cannot be issued if the
fuel status is Historical.
If you try to produce a provisional loadsheet the following error message is
displayed:
Provisional Loadsheet cannot be produced when Fuel Figure Status = Historical.
294 Edition 8.5

Last Minute Change Threshold Limits Rule
Rule Description
This rule is available to carriers who subscribe to the Last Minute Change
functionality.
It allows you to define weight and trim thresholds for last minute changes, and
determine what happens when last minute changes reach or exceed the limits
defined.
Rule Layout 1
When using layout 1, the rule determines the procedure for LMC Documents (if
used), or the procedure for supplementary information in the final loadsheet.
Rule Layout 2
When using layout 2, the rule determines the type of supplementary information
to be added to the final loadsheet if last minute changes have been made.
Related Rules
If the LMC Document is automatically generated (rule layout 1 only), its routing
must be defined in the Document Type Facility Routing rule. See Document Type
Facility Routing Rule on page 243.
For airlines using the LMC Variation window from the Passenger screen, the
Manual Last Minute Change Rule on page 300 must also be defined.
Rule Criteria
Table: Last Minute Change Threshold Limits Rule Criteria
Mandatory.
Market Origin 0
Market Mandatory.
0
Flight No. Range
1 format DDMMMYY.
Effective To

One of the following rule content windows is displayed, based on the search
criteria and activation:
Rule Layout Layout 1
Rule Layout Layout 2

Note: In the future, this layout will be replaced by layout 1.
Rule Contents
Table: Last Minute Change Threshold Limits Rule Contents
Field Description
Enable LMC Procedure Select this check box to activate the LMC procedure.
For Rule Layout 2:
Selecting this check box activates the LMC procedure as
described for layout 1 in the field Use LMC Data in Final
Loadsheet SI Text, below.
296 Edition 8.5

Field Description
Rule Layout 1
Use LMC Data in Final Note: Do not select this field if your airline uses LMC
Loadsheet SI Text Documents.
If the last minutes changes are above the minimum
values and below the maximum values, the LMC
Supplementary Information is appended to the current
edition of the Final Loadsheet under the heading LMC TO
L/S EDNO X.
If the last minutes changes are above the maximum
values, the LMC Supplementary Information is appended
to a new edition of the Final Loadsheet under the heading
L/S REVISED.
Auto-generate LMC If the last minutes changes are above the minimum
Documents values and below the maximum values, the system
automatically creates an LMC document, and routes it
according to the definition in the Document Type Facility
Routing rule.
Use Confirmation / End of Select to send either a confirmation or end of procedure
procedure message message back to ACARS as part of the LMC process
following a VAL ACARS message to FM.
Check Min Thresholds Determines whether FM checks minimum threshold limits
against current LMC against the current edition of the Final Loadsheet, or
Document against the current edition of the LMC Document (if one
exists).
If selected, the system compares minimum limits against
the data used to create the current edition of the LMC
Document.
If no LMC Document exists, the system checks against
the current edition of the Final Loadsheet.
If not selected, the system compares minimum limits
against the data used to create the current edition of the
Final Loadsheet.
Threshold Limits Layouts 1 and 2
The minimum and maximum LMC values for changes to
the weights and indexes listed.
Note: Deselect the check boxes of each threshold limit that is not required.
Total Change to Basic Basic weight and basic index.
Weight
Total Change to Basic
Index
Total Change to DOW Dry operating weight (DOW) and dry operating index
(DOI).
Total Change to DOI
Total Change to TOW Takeoff weight (TOW) and takeoff index (TOI).
Total Change to TOI
Total Pax Change The number of passengers on the flight.
Total Fuel Weight Change Total fuel weight.

Field Description
Threshold Limits Layout 1

The minimum and maximum LMC values for changes to:
Total Change to MACTOW MAC (Mean Aerodynamic Chord) takeoff weight.
Takeoff Fuel Weight Takeoff fuel weight.
Change
Trip Fuel Weight Change Trip fuel weight.
Note: The Minimum default value for all fields is zero.
Example Business Rule - Layout 1
In the example above, the airline is working with LMC Documents. Threshold
limits have been defined for all types of weight checks for last minute changes.
Example Business Rule - Layout 2
In the example above, all the minimum values have been left at zero and, for
example, the maximum weight for the total change to the takeoff weight is set to
2000 and takeoff index to 5.0. The maximum total passenger change is set to 10.
If the last minute changes are above the minimum values and below the
maximum values, the LMC Supplementary Information is appended to the current
edition of the Final Loadsheet under the heading LMC TO L/S EDNO X.
298 Edition 8.5

Example LMC Supplementary Information messages:
Example: LMC Supplementary Information Message (1)
If the last minutes changes are above the maximum values, the LMC
Supplementary Information is appended to a new edition of the Final Loadsheet
under the heading L/S REVISED.
Example: LMC Supplementary Information Message (2)

When a flight is in LMC mode, LMC is displayed on the status bar.
Example: Status Bar with LMC Mode

Manual Last Minute Change Rule
Rule Description
This rule is used for airlines that use Last Minute Change functionality, to activate
the LMC Variation button on the Passenger screen in Flight Management, which
allows the Load Controller to make last minutes changes to the passenger and
baggage figures.
Manual LMC mode does not allow changes or updates from the Customer
Management application. However, the Load Controller can revert back to
Customer Management to receive the passenger and baggage figures, if
required.
Any weight and balance changes made to a flight in Flight Management such
as number of passengers, takeoff weights or index, or fuel weights after the first
Final Loadsheet, are compared against threshold values defined in the Last
Minute Change Threshold Limits rule. Depending on the LMC weight and trim
limits, either a Final Loadsheet with LMCs, or a full new Final Loadsheet can be
manually created by the Load Controller.
Related Rules
LMC thresholds for weights and trim changes are defined in the Last Minute
Change Threshold Limits Rule on page 295.
Rule Criteria
Table: Manual Last Minute Change Rule Criteria
Mandatory.
Operating Carrier 0
Mandatory.
Market Origin 0
Market Mandatory.
0
Flight No. Range
1 format DDMMMYY.
Effective To
300 Edition 8.5

Rule Contents
Table: Manual Last Minute Change Rule Contents
Check Box Description
Allow Manual LMC Select this check box to allow the load controller to put the
flight into manual last minute change mode in the LMC
Variation window, available from the Passenger screen.
Manual last minute changes are permitted.


The LMC Variation button is activated on the Passenger screen:
In the Last Minute Change window, the Load Controller can select the Allow
LMC check box.
Example: Allow LMC Check Box
When a flight is in LMC mode, LMC is displayed on the status bar.
Example: Status Bar with LMC Mode
See Last Minute Change Threshold Limits Rule on page 295 for an example of
the LMC information in Supplementary Information in the final loadsheet.
302 Edition 8.5

Maximum Baggage ULD Rule

Rule Description
This optional rule is used to determine the maximum number of baggage ULDs to
be created for a flight leg.
Related Rules
This rule is considered during capacity calculation in conjunction with the
following rules:
Baggage Classification Rule on page 203.
Baggage Segregation Rule on page 207.
Rule Criteria
Table: Maximum Baggage ULD Rule Criteria

Market
Destination
Aircraft
Subtype
Day of Week 4
and Tuesday).
1

Rule Contents
Table: Maximum Baggage ULD Rule Contents
Field Explanation
Maximum Number of Baggage ULDs Enter the number of ULDs.
For all 6x World Market flights operating with aircraft subtype 744 the maximum
number of baggage ULDs will be 10.
304 Edition 8.5

Notification Priority Rule
Rule Description
This rule allows you to override the default priority of notification messages sent
to the Load Controller from the Messenger application following an event related
to a flight.
Optionally, you can define the priority of the notification by load control status.
Rule Criteria
Table: Notification Priority Rule Criteria

Mandatory.
The identifier of the notification you wish to configure.
Notification ID 0 Example: 15381.
For a description of how to find the notification IDs, see
Notification IDs in the Flight Management Specifications
on page 307.
Market Origin The market of the flight origin.
Market 128
Destination
Domain 64 The load control domain name.
Registration 16
LH - Long-haul
SH - Short-haul
Template Flight
8 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
2
and Tuesday).
1 format DDMMMYY.
Effective To

Rule Contents
Rule Content panel when the Configure by Load Control Status field is selected:
Table: Notification Priority Rule Contents
Field Explanation
Configure by Load Control Status Select to define the priority of the selected
message at each load control status.
Leave this field unselected to define the priority of
the message for all load control statuses.
Notification Priority Select from the drop-down list the message priority
(when Configure by Load Control to override the default priority.
Status is not selected) Priority at LO (load control open)
Notification Priority by Load Priority at LL (load control closed, approve
Control Status distribution required)
(when Configure by Load Control Priority at LC (load control closed, approve
Status is selected) distribution complete)
Priority at LSF (loadsheet finalised)
See the Message Priority table below for the
impact of overriding the default message priority.
306 Edition 8.5

Table: Message Priority
Message Priority Impact on the Notification
Very High Displayed to the load controller in a pop-up window.

High Displayed in a pop-up window when the load controller
is working on the flight.
Medium Displayed to the load controller in the Messenger
Low panel.
None Will not be sent or displayed to the load controller.
Notification IDs in the Flight Management Specifications

The Flight Management specifications, which are available from the Alta DCS
Flight Management product information pages on the internet, include the
notification IDs for all notifications.
Example: Extract from a Flight Management Specification
The identifier, that you must enter in the Notification ID field of the rule.
Note: Ensure that you enter the ID of a notification, and not of a message.
The notification text, followed by any variable data, if appropriate.
If a notification is defined as Interactive by default, the Load Controller must

acknowledge it.
However, if you define an interactive notification with a High, Medium or Low
priority in the rule, it will no longer be defined as interactive, and will not require
acknowledgement.
The default priority for this notification.

The default is used by Flight Management when the Notification Priority rule is not
defined for a flight, load control status, and Notification ID.
VH (very high), H (high), M (medium), L (low).


In the rule below, the default notification setting for notification ID 26765 has been
defined with a different priorities, according to the load control status of the flight.

The notification with ID 26765 is displayed to the Load Controller with different
priorities (low, high, medium and very high) according to the load control status of
the flight.
For example, at LSF (loadsheet finalised), the notification is Very High priority,
and is displayed to the load controller in a pop-up window.
308 Edition 8.5

NOTOC Emergency Number Rule

Rule Description
This rule enables an emergency telephone number to be specified for inclusion
on the Notification to Captain (NOTOC) document. This rule is required if a
NOTOC is required.
Rule Criteria
Table: NOTOC Emergency Number Rule Criteria
Operating Carrier 0 The two-character code for the airline. Mandatory.

Flight No. Range
1 To specify the flight number range, click on to select
Rule Contents
Table: NOTOC Emergency Number Rule Contents
Field Explanation
NOTOC Enter the Notification to Captain (NOTOC) Emergency Number.

Emergency The first box is for the country code, the second for the area code, and
Number the third for the number.
The number field is mandatory.
Description Enter an optional description for this emergency number.


Emergency number 44 208 89900000 set for 6X World market flights.

Emergency contact telephone number appears at the bottom of the NOTOC.
Example: Flight Management - NOTOC for 6X117
310 Edition 8.5

Offload Reasons Rule
Rule Description
This rule defines a list of reasons available to the Load Controller when offloading
deadload in Flight Management. For each offload reason, the comments section
in the Offload dialogue box can be set to optional or mandatory.
In addition, the use of a specific offload reason on a flight can prevent the
Deadload Uplift/Offload message (DUO) from being sent when the flight has
departed (the flight status is GD - General Departed).
Note: When this feature is active, the Carrier > Offload Reasons tab is
removed from DBM.
Rule Criteria
Table: Offload Reasons Rule Criteria
Operating Carrier 0 Airline code.

Mandatory.
Market Origin 0
Market Mandatory.
0
Flight No. Range
1 format DDMMMYY.
Effective To

Rule Contents
Table: Offload Reasons Rule Contents
Field Explanation
Enable Offload Reasons Select to enable the Offload Reason feature.

Offload Reasons
Code A 4-character code, to represent the offload
reason.
The code is included in the DUO message, but is
not visible to the Load Controller on the Offload
dialogue box.
Description A description of the offload reason, up to 30
characters.
The description is included in a drop-down menu
for the Load Controller to select from when
offloading deadload.
The offload description is included in the DUO
message.
Mandatory Comments When selected, the Load Controller must enter a
comment in addition to selecting an offload reason.
The comments entered by the Load Controller are
included in the DUO message.
Inhibit DUO at GD Used to prevent the DUO message from being
sent when the flight status is set to GD (General
Departed).
When selected, and the offload reason has been
used on a flight, a message is sent to the Load
Controller when the DUO message cannot be sent.
Note: You can create up to 40 offload reasons. Click on New Row to enter
multiple lines in the Offload Reasons table. Use the Move Up and
Move Down buttons to order the offload reasons in the order you want
them to display to the Load Controller.
312 Edition 8.5


In the following rule, six offload reasons have been defined. Two of the reasons
(Aircraft Change and Damaged Unit) require the Load Controller to enter
mandatory comments when selecting that offload reason. In addition, the Aircraft
Change offload reason prevents the DUO from being sent.

For the flights defined in the business rule, when the Load Controller offloads a
commodity on the Deadload or Load Distribution screen, the Offload dialogue
box is displayed. The offload reasons in the drop-down menu are defined in the
rule.

The Comments field is optional, except for the reasons with the Mandatory
Comments field selected. For example:
314 Edition 8.5

Outbound Teletype Message Delivery Rule

Rule Description
This rule specifies the teletype addresses to which the selected Flight
Management message type, such as CPM and LDM, is to be sent.
Some of the message types are dependent on the arrival port, such as the CPM
and LDM, and will contain specific teletype addresses for the relevant arrival port.
Some of the message types are dependent on the departure port, such as the
SLS and UCM, and will contain specific teletype addresses for the relevant
departure port.
All message types may also contain specific teletype addresses for a carrier's
headquarters, central control centre, or computer system.
Related Rules
For the Deadload Uplift/Offload (DUO) Message only, the Deadload Uplift
Offload Message Parameter Selection Rule on page 225 is used to define a
parameter to route the DUO message according to offload type and
commodity type.
The Outbound Teletype Message Originator Rule on page 319 defines the
originator address of teletype messages per document type.
Rule Criteria
Table: Outbound Teletype Message Delivery Rule Criteria
Operating Carrier The two-character carrier code.

Mandatory.
0 In a ground handling solution, when the rule is
created in the reference data of the ground handling
organisation, you can optionally enter ALL to
represent all handled airlines.
The teletype message identifier code. For example:
CPM - Container Pallet Message.
These codes are located in DBM in Carrier >
Teletype Message General > Doc Type Rules.
0
Identifier
For a list of codes, see Document and Message
Types on page 376.
Mandatory.

Used for the DUO (Deadload Uplift/Offload) message

Message only.
Parameter
Enables you to specify when the DUO message is
sent, according to the type of offloaded commodity,
and whether the offload is due to a disruption, or to a
32 regular offload.
The document parameter you enter here must be
defined in the Deadload Uplift Offload Message
Parameter Selection rule.
For more information, see Deadload Uplift Offload
Message Parameter Selection Rule on page 225.
Outbound Terminal The departure airport terminal where the document is
8
routed.
Inbound Terminal The arrival airport terminal where the document is
8
routed.
Flight No. Range
2
Effective To
316 Edition 8.5

Rule Contents
Table: Outbound Teletype Message Delivery Rule Contents
Field Explanation
Outbound Teletype Message Delivery Panel (Mandatory)

Priority The teletype message priority code. Select from the drop-down
menu:
QD - priority 4 - deferred delivery
QK - priority 3 - normal delivery
QU - priority 2 - high priority
QX - priority 1 - urgent, high priority
Mandatory.
Recipients The teletype addresses to which the message is to be sent.
To add a row in the table below the current row, click on the New
Row button.
To delete a selected row, click on the Delete Row button.
Note: A maximum of 16 addresses can be added for each
message type.
Mandatory.
Sender Teletype Address Panel (Optional)
Note: The information in this panel can now be entered in the new Outbound
Teletype Message Originator Rule on page 319, and takes precedence over
the values entered here. This panel will be removed in the future following a
Product Management announcement, and the originating address will be
stored in the new rule only.
Use Departure Port Select this check box if the departure port of the flight is to be
used in the originating address of the message. For example,
LHRKM6X.
The default departure port is MUC.
Office Function Enter the two-character office function code to be used in the
(Optional) originating address of the message. For example, LHRKL6X.
The default office function code in the production system is KM.
Double Sign Select this check box if the operating carrier code is to be used
as well as the handling carrier code in the originating address of
the message.


LDM (Load Message) teletype message to be sent at QD priority to JFKLC6X
and JFKPL6X for 6X flights to JFK.

The TTY Addresses panel displays the addresses to which the LDM is to be sent.
Note: The TTY Address check box is automatically selected and the TTY
Address field displays to indicate that a list of addresses
is present.
Example: Flight Management - Documents Screen
318 Edition 8.5

Outbound Teletype Message Originator Rule

Rule Description
This rule defines the originator address for outbound teletype messages.
Prior to the creation of this rule, the TTY originator address was defined in the
Sender Teletype Address panel in the Outbound Teletype Message Delivery
Rule on page 315. When the Outbound Teletype Message Originator rule is
defined, it takes precedence over the TTY originator address set in the
Outbound Teletype Message Delivery rule.
Related Rules
The Outbound Teletype Message Delivery Rule on page 315 defines the delivery
addresses for TTY messages.
Rule Criteria
Table: Outbound Teletype Message Originator Rule Criteria

Mandatory.
Operating Carrier 0 In a ground handling solution, when the rule is
created in the reference data of the ground handling
organisation, you can optionally enter ALL to
represent all handled airlines.
Mandatory.
Market Origin 0
Mandatory.
Teletype Message The Flight Management teletype message identifier
Identifier code. For example: CPM - Container Pallet Message.
These codes are located in DBM in Carrier > General
2048 > Doc Type Rules.
For a list of codes, see Document and Message
Types on page 376.
Mandatory.
Message Used for the DUO (Deadload Uplift/Offload) message
Parameter only.
Enables you to specify when the DUO message is
sent, according to the type of offloaded commodity,
and whether the offload is due to a disruption, or due
512 to a regular offload.
The document parameter you enter here must be
defined in the Deadload Uplift Offload Message
Parameter Selection rule.
For more information, see Deadload Uplift Offload
Message Parameter Selection Rule on page 225.

Outbound Terminal 32
Inbound Terminal 32
Flight No. Range
Day of Week 2
Effective To
Rule Contents
Table: Outbound Teletype Message Originator Rule Contents
Field Explanation
Originator The 7-character alphanumeric TTY originator

address.
For example, LHRKM6X.
The characters KM in positions 4-5 identify the
production system.
The last two characters are the originator's carrier
code.
Double sign Select if the operating carrier code is to be used as
well as the handling carrier code in the originating
address of the message.
For example, to apply correct billing of messages
by SITA.
Carrier code Optional, and only available when the Double sign
field is selected.
The carrier code to be used as the double sign.
If left blank, the operating carrier code is used for
the double sign.
320 Edition 8.5


The originator of the message type and flights selected in the rule is LHRKM6X.
The double sign of the operating carrier is used to ensure correct billing by SITA
of ground handled flights.

Out of Scope System Address Rule

Rule Description
This rule is required if an external system is to be targeted for certain messages,
for example a cargo or flight planning system.
Rule Criteria
Table: Out of Scope System Address Rule Criteria

Aircraft Available with activation. The aircraft subtype, as

4
Subtype defined in DBM.
Flight Nb Range
0 select the Flight Group Keyword or the Flight Range.
Mandatory.
Subject to activation, this field is optional with a
2
weighting of 2
4 Crew owner airline code.

Crew Owner
Effective From The starting and ending effective dates of this row in
Effective To
322 Edition 8.5

Rule Contents
Table: Out of Scope System Address Rule Contents
Field Explanation
Capacity Control The name or system address of the external system used
for capacity control, instead of the capacity calculation
feature in Flight Management.
FZFW Address The name or system address of the external system used
for the flight planning.
Dangerous Goods The name or system address of the external system where
notification at departure a dangerous goods notification can be sent at departure.
Dangerous Goods The name or system address of the external system where
notification at arrival a dangerous goods notification can be sent at arrival.
FM Data Warehouse The name or system address of the external system used
for the flight management data warehouse.
ACARS Address The address of the ACARS system.
Flight Event The name or system address to which the flight image is
Notification System sent, triggered by the events defined in the Flight Event
Notification business rule.
Crew The system address of an external crew system.
Pantry The system address of an external pantry system.
Create Load The system address for the Create Load Downline
Downline Address message.
The Create Load Downline message contains container and
pallet information, plus additional data such as crew and fuel
figures. .
Load and Trim Data The system address for the Load and Trim Data Final (LTF),
Load and Trim Data Provisional (LTP) loadsheets in XML
format.
NOTOC Data The system address for the NOTOC documents in XML
format.
Note: All fields are optional, but at least one field is necessary to create this
rule.

Parallel Run Rule

Rule Description
The purpose of this rule is to manage the migration of an airline from its current
system to Flight Management and to identify flights which are used in a parallel
run.
For these types of flights, no documents or messages are generated from Flight
Management to external systems, because the airline's current system is still the
master.
Rule Criteria
Table: Parallel Run Rule Criteria

Market
Destination
Flight No. Range
2

Day of Week 1
Rule Contents
Table: Parallel Run Rule Contents
Field Explanation
Activated for parallel run Select to activate the parallel run functionality.
324 Edition 8.5

Passenger Gender Type Weights Rule

Rule Description
This mandatory rule determines the passenger gender weight type to be used on
a flight.
Note: If the template flight type is Cargo Operation, this rule is not required.
Related Rules
This rule works in conjunction with the Passenger Weights rule to determine the
passenger weights category and passenger weights to be used for each
passenger type or gender.
The Passenger Weights rule determines which passenger weights category is
used for a flight. See Passenger Weights Rule on page 148.
The Passenger Gender Type Weights rule determines which of the passenger
weights are used from the relevant passenger weights category, either MFCI or
ACI.
Rule Criteria
Table: Passenger Gender Type Weights Rule Criteria

Market
Destination
LH - Long-haul
SH - Short-haul
Template Flight
2 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo

Rule Contents
Table: Passenger Gender Type Weights Rule Contents
Field Explanation
Passenger Gender Enter the Passenger Gender Weight Type:

Weight Type
ACI (Adult, Child, Infant)
MFCI (Male, Female Child, Infant)
Mandatory.

Passenger gender type 'ACI' for 6X world market international flights.

The passenger weights for adults, children and infants (ACI) have been used and
the passenger totals (137/3/1) are displayed in the Passenger/Cabin Bag totals
on the loadsheet.
Example: Passenger/Cabin Bag Totals - 6X117
Passenger weight category XYB STD is used to calculate the total weight of
passengers (11050 kgs) which is displayed in the Passenger/Cabin Bag totals on
the loadsheet.
Example: Partial Loadsheet - 6X117
Note: The weight of passengers may vary according to their class of travel.
326 Edition 8.5

Process External Cargo Feed Message Rule
Rule Description
This optional rule is used to inhibit the processing of the final external cargo feed
message if the load control status is LC (load control closed) or LL (load control
closed, approve distribution required).
A message is sent to the Load Controller giving him the option to accept or reject
the cargo feed message.
Related Rules
This rule can be used in conjunction with the Inhibit Approval of Distribution Rule
on page 281, which controls Approve Distribution, based on the cargo status.
Rule Criteria
Table: Process External Cargo Feed Criteria

Market
Destination
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
1

Rule Contents
Table: Process External Cargo Feed Message Contents
Field Explanation
Internal Cargo Release Select to stop the processing of the external cargo feed
Status Final message, if the internal cargo release status is Final.
External Cargo Release Select to stop the processing of the external cargo feed
Status Final message, if the external cargo release status is Final.
Load Control Status - LL Select to stop the processing of the external cargo feed
message, if the load control status is LL.
Load Control Status - LC Select to stop the processing of the external cargo feed
message, if the load control status is LC.
For all 6X World Market flights using the LH (long-haul) template the external
cargo feed message is not processed if:
The internal cargo status is Final.
The external cargo status is Final.
The load control status is LL.
328 Edition 8.5

If the external cargo feed message is not processed a very high priority message
is displayed to the Load Controller as follows:
A deadload weight statement has been received from the cargo system. Do you
wish to accept these modifications?
Followed by the details:
1. Deadload details to be changed
2. Request originator
The Load Controller can accept or reject the cargo feed message.

Process External Crew Message Rule
Rule Description
This rule controls the processing of external crew messages when performing a
manual update to the crew figures in Flight Management.
Rule Criteria
Table: Process External Crew Message Rule Criteria

Market
Destination
1
330 Edition 8.5

Rule Contents
Table: Process External Crew Message Rule Contents
Field Explanation
If Crew Figures have a status of Manually Updated

Process External Crew Message - Select to process the external crew message and
Automatically update the data automatically.
Process External Crew Message - Select if the Load Controller has to accept or
Prompt reject the external crew message.
Ignore Select to ignore the external crew message.
Note: If the crew figures have not been manually updated this business rule is
ignored, and the external crew message is processed.
For all flights impacted by the rule, a very high priority message is displayed to
the Load Controller, as follows:
Crew figures have been received from the external system. Do you wish to
accept these modifications?
Followed by the details:
- Crew figures to be changed
The Load Controller can chose to accept or reject the external crew message.

Radio Frequency Rule

Rule Description
This optional rule determines the radio frequency to be used by the flight deck
crew to contact the Load Controller at the departure port.
The frequency defined in the rule will be printed on the loadsheet, if required by
the settings in DBM in the Carrier > General > AC Sub Type Rules tab.
Example: Carrier & Aircraft > General > AC Sub Type Rules
Rule Criteria
Table: Radio Frequency Rule Criteria

Market 0 The market of the flight origin. Mandatory.
Terminal 2 The airport terminal of the flight departure.
1
332 Edition 8.5

Rule Contents
Table: Radio Frequency Rule Contents
Field Explanation
Radio Frequency The radio frequency to be used. Mandatory.

Radio frequency 123.45 MHz to be used to contact the Load Controller.

Radio frequency 123.45 (MHz) displayed on the loadsheet.

Ramp Final Clearance Rule
Rule Description
This optional rule is used to control the issuance of final ramp clearance by a
ramp agent, after changes are made to the Load Distribution.
Rule Criteria
Table: Ramp Final Clearance Rule Criteria

Market
Destination
1
334 Edition 8.5

Rule Contents
Table: Ramp Final Clearance Rule Contents
Field Explanation
Confirm Load Select to display the Ramp Confirmation screen when

weight tolerances are exceeded.
Authorise Load Select if the Ramp Agent is required to enter a password
before confirming the changes.
Auto-generate LDR Select to generate the LDR (Loading Report Document)
Document automatically.
Ramp Final Tolerance Enter the weight limit, above which ramp confirmation is
required.
Confirm Ramp Clearance Enter the text to be displayed on the Ramp Clearance
Dialog Text Confirmation panel and on the LDR.

Selected Passenger and Baggage Statistics Rule
Rule Description
This rule defines one or several date periods that are used by Flight Management
to calculate:
ETB (expected to board) passenger figures, displayed on the Passenger
screen in Flight Management.
To Come Baggage Pieces/Weight Average, displayed on the Planned
Baggage window, from the Passenger screen in Flight Management.
Historical average baggage weights, displayed on the Zero Fuel Weight
window in Flight Management.
Using this rule allows seasonality to be included or excluded from the statistical
calculations, to enable a more accurate prediction of expected passengers and
baggage.
Note: You must ensure that the History Sample Size on the Carrier > Detail
tab in DBM is set correctly to retrieve the desired sample of flights to
work with the dates you define in this rule.
Without this rule in place for a flight, the default statistical data is used:
Historical data per flight-route-day of the week, based on the historical
sample size stored in DBM.
Or:
A fixed value retrieved from the WWF Override Rule (for passenger numbers)
or from the Baggage Statistics Override Rule (for bags).
Related Rules
The rules below relate to flight statistics. However, the Selected Passenger and
Baggage Statistics rule is called before these rules, and takes precedence if they
are also defined.
WWF Override Rule on page 363.
336 Edition 8.5

Rule Criteria
Operating Carrier 0
Mandatory.
Market Origin 0
Market Mandatory.
0
Flight Group
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Day of Week 2
1 format DDMMMYY.
Effective To
Rule Contents

Field Explanation
Baggage Stats from Selected Select to activate the table below.

Flights
Flight Date(s) From and To Click on New Row.
Select the From and To dates to use for baggage
statistics for the flights impacted by this rule.
WWW from Selected Flights Select to activate the table below.
Flight Date(s) From and To Click on New Row.
Select the From and To dates to use for What
Went Factor (WWF) statistics for the flights
impacted by this rule.

In the example above, the date periods for calculating baggage statistics and the
What Went Factor are set to exclude certain seasonal busy periods over the last
two years.
The WWF is not activated in this rule, therefore the WWF is derived from the
default process.
338 Edition 8.5

Shift Summary Layout Rule

Rule Description
This rule determines the order in which optional status information is displayed on
the Shift Summary Event Scheduler and Shift Summary Status views in the Load
Control and Load Control Supervisor applications.
Rule Criteria
Type of data
Label shown in the column header on the Shift Summary view.

With activation, additional fields can be chosen for the Shift Summary views.
Table: Shift Summary Layout Rule Criteria
Domain The two-character airline or organisation code for the

0
Organisation domain.
Domain Name 2 The name of the domain.
1
Rule Contents
Table: Shift Summary Layout Rule Contents
Panel Name Description
Status View Enter a sequential number, beginning at 1, in each field

that you want to display on the Shift Summary Status
View. The number determines the order on the Shift
Summary.
Leave blank the fields that you do not want to appear
on the Status View screen.
Status & Event Scheduler Enter a sequential number, beginning at 1, in each field
View that you want to display on the Shift Summary Event
Scheduler View. The number determines the order on
the Shift Summary.
Leave blank the fields that you do not want to appear
on the Event Scheduler View screen.
Note: The column order values must include the number 1, and numbers may
not be omitted. For example, if you wish to number 4 items, 1, 3, 4, 2 is
a valid column order, whereas, 2, 15, 8, 5 is invalid.
340 Edition 8.5


The optional status information columns are displayed in the order specified in
the business rule.
Example: Shift Summary - Status View

Example: Shift Summary - Scheduler View
342 Edition 8.5

SK/SSR Total Volume Rule
Rule Description
This rule determines the minimum volume of bags with a special service code
(SK keyword or SSR code) to create a ULD, and the maximum volume of bags
with a special service code to include in a ULD.
The default for Deadload Volume Units (cubic metres or cubic feet) is set in DBM
on the Carrier > General > Detail tab.
Example: Carrier > General > Detail Tab in DBM: Default Volume Units
& Bag Densities
The conversion from a special service code (SK keyword or SSR code) in
Customer Management to a DG/SL code in Flight Management is set in the
Carrier > General > SSR Codes tab.
Example: Carrier > General > SSR Codes Tab in DBM

Rule Criteria
Table: SK/SSR Total Volume Rule Criteria

Baggage Commodity Mandatory.
Subtype 0
The baggage subtype. Example: Y.
Flight No. Range
2 and select the Flight Group Keyword or the
Flight Range(s).
Effective From The starting and ending effective date of this
1 row, in the format DDMMMYY.
Effective To
Rule Contents
Table: Supplementary Information Rule Contents
Field Explanation
Baggage Commodity The minimum volume of bags with a special service

Subtype Minimum Volume code (SK keyword or SSR code in Customer
Management) to create a ULD.
Baggage Commodity The maximum volume of bags with a special service
Subtype Maximum Volume code to include in a ULD.
344 Edition 8.5


SK and SSR items received from Customer Management are translated into a
DG/SL code using the airline's settings in the DBM Carrier > General > SSR
Codes tab. In Flight Management the corresponding DG/SL code is displayed on
the Deadload screen and Deadload Details window.
For baggage commodity subtype Y, a baggage commodity ULD is created for ten
units of volume for bags with a special service code, and can contain up to 50
units of volume for bags with a special service code.
Any units of volume for bags with a special service code below the minimum are
included in the bulk hold.

Supplementary Information Rule
Rule Description
This rule defines which type of information is included in the Supplementary
Information section of a Flight Management document or message.
You must set up a rule for each type of document or message where you want to
add supplementary information.
The document and message types are stored in DBM in the Carrier > General >
Doc Type Rules tab.
Example: Carrier > General > Doc Type Rules Tab in DBM
For a list of document and message codes, see Document and Message Types
on page 376.
Rule Criteria
Table: Supplementary Information Rule Criteria

0
Mandatory.
Market Origin 0
Market Mandatory.
0
346 Edition 8.5

Document/ Mandatory.
Message Type The three-letter code of the document to be printed.
Example: LIR.
0
The codes are stored in DBM in the Carrier > Doc Type
Rules tab.
See Document and Message Types on page 376.
Flight No. Range
1 format DDMMMYY.
Effective To
Rule Contents

Table: Supplementary Information Rule Contents
Field Explanation
Include Select to include the option in the document defined in the

rule criteria.
Option Information from the flight leg that can be included in the
document.
Examples: Captain Name, Pantry Code.
Configuration Mandatory when you select the Commodity option.
Enter the commodity codes you want to include in the
document, separated by commas.
Example: BJ, BY
Free Text Mandatory when you select the option Free Text.
Text to be displayed in the SI field.
End of Document Text Text to be displayed at the end of the document.
When you include several options in a document, click on the Move Up and
Move Down buttons to determine the order in which the information will appear in
the document or message.

Fields to be included in the Supplementary Information (SI) field of the document:

Information in the Supplementary Information (SI) field of the document:
348 Edition 8.5

Template Flight Type Rule

Rule Description
This mandatory rule identifies the applicable template type, such as long-haul or
charter, and is required for all flights except those identified as cargo operation in
the IATA Service Type Rule on page 276. Each plan template has several sets of
timings, and the set applied depends on the flight type determined by this rule.
The Template Flight Types are stored in the Plan Template Management
application.
Example: Departure Plan Template Screen
Related Rules
This rule works in conjunction with the IATA Service Type Rule on page 276 to
determine the Template Flight Type for a flight based on the IATA Service Type,
if applicable.
Rule Criteria
Table: Template Flight Type Rule Criteria

Market
Destination
IATA Service The IATA service type code. For example, J is for a
1
Type passenger flight.

Rule Contents
Table: Template Flight Type Rule Contents
Field Explanation
Template Flight Type Enter the flight type from one of the following:
LH Long-haul
SH Short-haul
CF Charter Flight
DF Domestic Flight
SF Shuttle Flight
CO Cargo Operation
Mandatory.

The data in the Process Time and Reference columns is based on the Template
Flight Type (Long-haul) from the relevant Departure Plan Template.
Example: Departure Plan Details Screen - 6X117
350 Edition 8.5

ULD Capacity Rule

Rule Description
This rule is mandatory for containerised flights during baggage Capacity
Calculation. It determines the type of ULD to use, and the number of baggage
pieces to allocate to each ULD.
With activation of the ULD Stock Control feature, this rule is also called during
the Autoload process.
The ULD category and type entered in this rule must match exactly the category
and type stored in the Carrier > General > ULD Capacity tab in DBM to work
correctly in Flight Management.
Example: Carrier > General > ULD Capacity Tab in DBM
This DBM tab stores the maximum and the default number of pieces of baggage
for the ULD category and type.
Related Rules
This rule works in conjunction with the Baggage Segregation rule to create the
Capacity Calculation. The Baggage Segregation rule determines the type of
baggage segregation to be used on a flight, for example by class or category and
destination. See Baggage Segregation Rule on page 207.
The ULD Capacity rule controls the amount of baggage to be allocated to each
baggage ULD.
Rule Criteria
Table: ULD Capacity Rule Criteria

16
Subtype
Flight No. Range

4
LH - Long-haul
SH - Short-haul
Template Flight
2 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
1
Rule Contents
Table: ULD Capacity Rule Contents
Field Explanation
ULD Category The ULD category to use for this row. Example INT. Mandatory.
ULD Type The ULD type to use for this row. Example AKE. Mandatory.

ULD Category INT (International) and ULD Type AKE for 6X World Market
Flights.
The default capacity for this category and type is 40 pieces.
352 Edition 8.5


In the Capacity Calculation window, ULDs AKE56X* and AKE66X* are created
with the default value of 40 pieces of baggage.

ULD Stock Control Rule
Rule Description
This rule defines the number and type of ULDs that a containerised flight should
carry.
When Autoload is used, empty ULDs are created automatically to meet the ULD
requirements defined in the rule.
The Load Controller can display or modify the ULD stock control requirements for
a flight from the Load Distribution window. The system notifies the Load
Controller at Approve Distribution if these requirements have not been met.
Related Rules
The ULD Capacity Rule on page 351 defines the ULD type that applies to a flight.
Rule Criteria
Table: ULD Stock Control Rule Criteria

Mandatory.
Market Origin 0
Market Mandatory.
0
LH - Long-haul
SH - Short-haul
Template Flight
32 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Registration 8
Flight No. Range
STD 2 The starting and ending Standard Time of Departure.
1 format DDMMMYY.
Effective To
354 Edition 8.5

Rule Contents
Table: ULD Stock Control Rule Contents
Field Explanation
Fill All Possible Positions Used for Autoload.

If selected, Autoload attempts to fill all unused ULD
positions with empty ULDs, of the type or types defined
in the ULD Types panel.
Minimum Number of ULDs The minimum number of ULDs to be located on the
aircraft.
Target Number of ULDs This field is only available if Fill All Possible Positions
is not checked.
The target number of ULDs on the aircraft, including
empty ULDs.
ULD Types
Types The ULD types that are counted to calculate whether
the minimum or target number of ULDs have been
located for deadload.
The ULD types that can be automatically created as
empty ULDs and located on the flight.
The ULD types you enter must be:
Valid for the aircraft subtype, as defined in the
Carrier & Aircraft > General > Valid ULDs tab in
DBM.
Defined for the flight in the ULD Capacity rule.
Examples: AKE, AKH.
Click on New Row to enter a ULD type.


In the following example, a minimum of two ULDs are required on the selected
flights, and the target number of ULDs is four. The AKH ULD type is used to
count the ULDs on the flight.

The ULD Stock Control button is active on the Load Distribution screen in
Flight Management.
The ULD Stock Control window is populated with data from the business rule.
If Autoload is used, and the minimum or target number of ULDs are not created
for deadload, the system creates empty ULDs (with commodity type X) to the
next destination of the flight.
The Unlocated Load panel on the Load Distribution screen displays empty
ULDs, with commodity code X.
356 Edition 8.5

UWS/NTM Message Processing Rule

Rule Description
This rule determines how UWS (ULD/Bulk Weight Signal) and NTM (NOTOC
Message) messages received from an external cargo system are processed by
Flight Management.
of the operating carrier.
Rule Criteria
Table: UWS/NTM Message Processing Rule Criteria

Market
Destination
Flight No. Range
Day of Week 4
2 format DDMMMYY.
Effective To
Rule Contents

Field Explanation
UWS (ULD/bulk Weight Signal)

Process multiple final UWS Used when Flight Management receives a final
UWS message, and a final UWS message has
already been received and processed.
If the load control status is LO, the message is
processed and stored automatically. The data in
the new UWS message replaces the old one.
If the load control status is LL or LC, the Load
Controller receives a very high priority message
and must accept or reject the new UWS message.
If the Load Controller accepts the message, the
new final UWS message replaces the old one and
is stored.
If not selected, Flight Management cannot process
multiple final UWS messages.
Send UWS reject notifications When selected, the Load Controller receives a
medium priority message when an UWS message
is rejected, for example for an invalid message
format, or an invalid flight, load control, or ramp
status.
The reason for the reject is stated in the message.
Store processed UWS only When selected, only processed UWS messages
are stored in Flight Management. Rejected UWS
messages are not stored.
All stored UWS messages can be displayed by the
Load Controller.
NTM (NOTOC Message)
Process multiple NTM Used when Flight Management receives a NTM
that matches a UWS message, and an NTM has
already been received and processed for this UWS
message.
If the load control status is LO, the NTM is
processed and stored automatically. The data in
the new NTM replaces the old one.
If the load control status is LL or LC, the Load
Controller receives a very high priority message
and must accept or reject the new NTM.
If the Load Controller accepts the message, the
new NTM replaces the NTM of the UWS message,
and is stored.
If not selected, Flight Management cannot process
multiple NTMs for the same UWS message.
Send NTM reject notifications When selected, the Load Controller receives a
medium priority message when a NTM is rejected,
for example for an invalid message format, or an
invalid flight, load control, or ramp status.
The reason for the reject is stated in the message.
Store processed NTM only When selected, only processed NTMs are stored
in Flight Management. Rejected NTMs are not
stored.
All stored NTMs can be displayed by the Load
Controller.
358 Edition 8.5


Flight Management accepts multiple final UWS messages, and multiple NTMs,
from the external cargo system. When the load control status is LL or LC, the
Load Controller is asked to accept or reject the new final UWS or new NTM in a
high-priority message.
All UWS and NTM messages that were processed successfully are stored in
Flight Management, and can be displayed by the Load Controller. The UWS
message is displayed by clicking on the Ext. Cargo Hist button on the Deadload
screen. The NTM is displayed from the Documents screen.
The Load Controller is not notified of UWS messages or NTMs that are rejected.

WWF Limits Rule

Rule Description
This optional rule determines which What Went Factor (WWF) values are to be
considered when calculating an historical WWF for a flight.
The Want Went Factor (WWF) is calculated by comparing the booked passenger
figures with the accepted passenger figures. The WWF is used by Flight
Management to calculate the Expected to Board (ETB) passenger figures.
WWF values outside the minimum and maximum range are considered as
spikes, possibly caused by disruption to a particular flight, and will be ignored in
historical WWF calculations.
Rule Criteria
Table: WWF Limits Rule Criteria

Market
Destination
Flight Range(s).
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Day of Week 2
Effective From The starting effective date of this row in the format
1
Effective To DDMMMYY.
360 Edition 8.5

Rule Contents
Table: WWF Limits Rule Contents
Field Explanation
Commercial WWF - Min: The minimum WWF, for commercial passengers, to be

included in historical calculations.
Commercial WWF - The maximum WWF, for commercial passengers, to be
Max: included in historical calculations.
Subload WWF - Min: The minimum WWF, for subload passengers, to be included
in historical calculations.
Subload WWF - Max: The maximum WWF, for subload passengers, to be included
in historical calculations.

The WWF range for commercial passengers between 0.8 (80%) and 1.2 (120%)
and the WWF range for subload passengers between 0.5 (50%) and 1.5 (150%).
Any WWF factor outside this range will be ignored.


The Flight Management application uses the WWF to calculate the Expected to
Board (ETB) passenger figures, displayed on the Passenger screen.
362 Edition 8.5

WWF Override Rule

Rule Description
This rule is used to override the WWF statistical data stored in DBM in the
Stats/Hist > Pax & Bag Statistics tab.
The values stored in this rule are used when calculating the ETB (Expected to
Board) passenger figures.
Related Rules
This rule can be used in conjunction with Baggage Statistics Override Rule on
page 212.
This rule is not used by Flight Management if the Selected Passenger and
Baggage Statistics Rule on page 336 exists for the flight, and WWF from
Selected Flights is activated in the rule.
Rule Criteria
Table: WWF Override Rule Criteria
Operating Carrier 0
Departure Airport 0 The market of the flight origin. Mandatory.
Arrival Airport 0 The market of the flight destination. Mandatory.
Flight Range(s).
LH - Long-haul
SH - Short-haul
Template Flight
8 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Day of Week 4
1

Rule Contents
Table: WWF Override Rule Contents
Field Explanation
Class Code The passenger class code. For example, F,J,M, Y. Optional.
Pax Type The passenger type. Select from the drop-down menu:
Commercial
Subload
What Went Factor The What Went Factor to be used for this type and class of
(WWF) passenger.
For flights impacted by this rule, the WWF used to calculate the ETB for C class
passengers is 0.8. For all other commercial passengers, it is 0.9. For subload
passengers in any class, the WWF is 0.75.
364 Edition 8.5

Chapter 9
Departure Plan Simulation
Departure Plan Simulation displays information derived from business rules data
about a specific flight.
You can use Departure Plan Simulation to:
Understand which business rules are applied for a specific flight.
Display the values a flight has acquired from the business rules applied.
Troubleshoot when a flight has failed to create.
Find out when business rules data are missing.
Validate business rules setup.

How to Simulate a Flight

1. Select Departure Plan Simulation from the File menu in Alta
Administration.
The system displays the Departure Plan Simulation window.
2. Enter the flight number.
3. In the Port field, enter the departure port in the first row, and the destination
port in the second row.
4. Enter the remaining flight criteria, as described in the table below.
5. Click on Simulate.
If you leave any of the mandatory fields blank, the following error response is
displayed when you click on Simulate:
Departure Port, Arrival Port, Departure Date, STD, Aircraft Type, IATA Service
Type, Fitted Config, Saleable Config, ACV and Saleable Config Code are
required.
Example: Departure Plan Criteria (ACV 74K)
Table: Departure Plan Criteria Panel
Note: All fields are mandatory, except Terminal and Registration.
Field Description
Flight Number Example: 6X17

Port The departure port in the first row, the destination port in the
second row. Example: LHR and SIN.
To add an additional flight leg, click on Insert Row.
Optional. Departure port terminal. Example: 5.
Terminal
Departure Date The local day and date of departure. Example: Wed 10Aug11.
Double click on the calendar icon to select the date in the correct
format.
STD Scheduled time of departure. Example: 22:35
IATA Service Example: J
Type The two main IATA service types available for use are:
Passenger Operation flights (J)
Cargo Operation flights
You can display IATA service type codes when creating a flight
period in Alta Inventory.
366 Edition 8.5

Chapter 9 Departure Plan Simulation
Field Description
Aircraft Type The aircraft type code, as stored in Alta Inventory. Example: 744.
Registration Optional. The aircraft registration, as stored in DBM.
Example: 6X-YGB.
ACV The aircraft configuration version, as stored in Alta Inventory.
Example: 74K.
Fitted Config The fitted configuration of the aircraft type, as stored in Alta
Inventory.
Example: F14J38W36M263.
Note: The format is the one stored in Alta Inventory, without
slashes (/).
Saleable Config The 3-character saleable configuration code, stored in Alta
Code Inventory, and in the Code field on the Saleable Configuration
tab in DBM for the aircraft subtype.
Example: B10.
Saleable Config The saleable configuration, as stored in Alta Inventory.
Example: F14J38W36M263.
Note: The format is the one stored in Alta Inventory, without
slashes (/).
Example: List of Periods (option 1) in Alta Inventory (ACV 74K)

Example: Aircraft Library Data (option 3) in Alta Inventory (ACV 74K)
Departure Plan Simulation Screen

Example: Departure Plan Simulation Result
368 Edition 8.5

Chapter 9 Departure Plan Simulation
Table: Business Rule Data
Field Description
Rule Name Business rule name.

Data Name Field in the business rule.
Data Value Value applied to this flight for this field.
For active flight business rules, if no rule has been
established for this flight, this field displays:
Warning: Rule not found
Rule Ref The rule is taken from the business rule in the
reference data of the carrier listed in this field.
This is useful for ground handling scenarios.
Rule Used Y Data is taken from the business rule.
N Data is not retrieved from a business rule.
For example, when:
There is only one value stored in DBM.
You have entered this value in the departure plan
simulation criteria, such as the fitted interior name.
Flight Create Business Rules

This tab displays the flight data retrieved by each business rule at flight create.
The data does not change for this flight if you subsequently update the business
rule.
If a business rule is missing for the flight, the Flight Create Business Rules table
contains all values retrieved up to the point of failure, and an error message is
displayed at the top of the Departure Plan Simulation window.

Active Flight Business Rules

This tab displays the flight data retrieved by each active business rule associated
to the flight. These are rules that you can update after flight create to change the
data associated to the flight.
Departure Plan Templates

This tab displays the departure and arrival plan template paths associated to the
departure plan.
370 Edition 8.5

Appendix A
Reference Information
This appendix contains the following information:

Service Type Codes below.
Country Codes below.
Region Codes on page 375.
Document and Message Types on page 376.
Departure Control Event and Activity Codes on page 377.
When Are Rules Called? on page 386.
Service Type Codes

Code Description
SH Short-haul
LH Long-haul
DF Domestic Flight
CF Charter Flight
SF Shuttle Flight
CO Cargo
Country Codes
Code Country Code Country
AD Andorra LB Lebanon
AE United Arab Emirates LC Saint Lucia
AF Afghanistan LI Liechtenstein
AG Antigua Barbuda LK Sri Lanka
AI Anguilla LR Liberia
AL Albania LS Lesotho

AM Armenia LT Lithuania
AN Dutch Antilles LU Luxembourg
AO Angola LV Latvia
AQ Antarctica LY Libya
AR Argentina MA Morocco
AS American Samoa MC Monaco
AT Austria MD Moldova
AU Australia ME Montenegro
AW Aruba MG Madagascar
AZ Azerbaijan MH Marshall Islands
BA Bosnia Herzegovina MK Macedonia
BB Barbados ML Mali
BD Bangladesh MM Myanmar
BE Belgium MN Mongolia
BF Burkina Faso MO Macau
BG Bulgaria MP Mariana Islands
BH Bahrain MQ Martinique
BI Burundi MR Mauritania
BJ Benin Peoples Republic MS Montserrat
BM Bermuda MT Malta
BN Brunei MU Mauritius
BO Bolivia MV Maldives
BR Brazil MW Malawi
BS Bahamas MX Mexico
BT Bhutan MY Malaysia
BV Bouvet Island MZ Mozambique
BW Botswana NA Namibia
BY Belarus NC New Caledonia
BZ Belize NE Niger
CA Canada NF Norfolk Island
CC Cocos Islands NG Nigeria
CD Democratic Republic of Congo NI Nicaragua
CF Central African Republic NL Netherlands
CG Congo NO Norway
CH Switzerland NP Nepal
CI Ivory Coast NR Nauru
CK Cook Islands NU Niue
CL Chile NZ New Zealand
372 Edition 8.5

Appendix A Reference Information
CM Cameroon OM Oman
CN China PA Panama
CO Colombia PE Peru
CR Costa Rica PF French Polynesia
CU Cuba PG Papua New Guinea
CV Cape Verde PH Philippines
CX Christmas Island PK Pakistan
CY Cyprus PL Poland
CZ Czech Republic PM Saint Pierre and Miquelon
DE Germany PN Pitcairn Islands
DJ Djibouti PR Puerto Rico
DK Denmark PS Palestine
DM Dominica PT Portugal
DO Dominican Republic PW Palau Islands
DZ Algeria PY Paraguay
EC Ecuador QA Qatar
EE Estonia RE Reunion
EG Egypt RO Romania
EH Western Sahara RS Serbia
ER Eritrea RU Russia
ES Spain RW Rwanda
ET Ethiopia SA Saudi Arabia
FI Finland SB Solomon Islands
FJ Fiji SC Seychelles
FK Falkland Islands SD Sudan
FM Micronesia SE Sweden
FO Faroe Islands SG Singapore
FR France SH Saint Helena
GA Gabon SI Slovenia
GB Great Britain SJ Svalbard and Jan Mayen Islands
GD Grenada SK Slovakia
GE Georgia SL Sierra Leone
GF French Guiana SM San Marino
GH Ghana SN Senegal
GI Gibraltar SO Somalia
GL Greenland SR Suriname
GM Gambia ST Sao Tome and Principe
GN Guinea SV El Salvador

GP Guadeloupe SY Syria
GQ Equatorial Guinea SZ Swaziland
GR Greece TC Turks and Caicos Islands
GS South Georgia TD Chad
GT Guatemala TG Togo
GU Guam TH Thailand
GW Guinea Bissau TJ Tajikistan
GY Guyana TK Tokelau Islands
HK Hong Kong TL Timor-Leste
HN Honduras TM Turkmenistan
HR Croatia TN Tunisia
HT Haiti TO Tonga
HU Hungary TR Turkey
ID Indonesia TT Trinidad and Tobago
IE Republic of Ireland TV Tuvalu
IL Israel TW Taipei
IN India TZ Tanzania
IQ Iraq UA Ukraine
IR Iran UG Uganda
IS Iceland UM Pacific Islands
IT Italy US United States of America
JM Jamaica UY Uruguay
JO Jordan UZ Uzbekistan
JP Japan VA Vatican
KE Kenya VC Saint Vincent
KG Kyrgyzstan VE Venezuela
KH Cambodia VG British Virgin Islands
KI Kiribati VI US Virgin Islands
KM Comoros VN Vietnam
KN Saint Kitts and Nevis VU Vanuatu
KP North Korea WF Wallis and Futuna Islands
KR South Korea WS Samoa
KW Kuwait YE Yemen
KY Cayman Islands YT Mayotte
KZ Kazakhstan ZA South Africa
LA Laos ZM Zambia
ZW Zimbabwe
374 Edition 8.5

Appendix A Reference Information
Region Codes
Region Code Description Country Codes Included in the Region
AFRIC AFRICA AO, BF, BI, BJ, BW, CD, CF, CG, CI, CM, CV,
DJ, DZ, EG, EH, ER, ET, GA, GH, GM, GN, GQ,
GW, KE, LR, LS, LY, MA, MG, ML, MR, MW, MZ,
NA, NE, NG, RW, SD, SL, SN, SO, ST, SZ, TD,
TG, TN, TZ, UG, ZA, ZM, ZW
ASIA ASIA BD, BT, CN, IN, JP, KP, KR, LK, MN, NP, PK,
TW, XU
ATLAN ATLANTIC BM, FK, SH
AUSTL AUSTRALASIA AS, AU, CK, FJ, KI, NC, NF, NU, NZ, PG, SB,
TO, TV, VU, WS
CAMER CENTRAL BZ, CR, GT, HN, MB, NI, PA, SV
AMERICA
CARIB CARIBBEAN AG, AI, AN, AW, BB, BS, CU, DM, DO, GD, GP,
HT, JM, KN, KY, LC, MQ, MS, PR, TC, TT, VC,
VG, VI
EEURO EASTERN AL, BA, BG, CZ, EE, HR, HU, LT, LV, MK, PL,
EUROPE RO, SK
EURAS EURO-ASIA AM, AZ, BY, GE, KG, KZ, MD, RU, TJ, TM, TR,
UA, UZ
EUROP EUROPE AD, AT, BE, CH, CY, DE, DK, ES, EU, FI, FO,
FR, GB, GI, GL, GR, IE, IS, IT, LI, LU, MC, ME,
MT, NL, NO, PM, PT, RS, SE, SI, SM, VA
IOCEA INDIAN OCEAN CC, CX, KM, MU, MV, RE, SC, YT
MEAST MIDDLE EAST AE, AF, BH, IL, IQ, IR, JO, KW, LB, OM, PS, QA,
SA, SY, YE
NAMER NORTH CA, CB, MX, US
AMERICA
PACIF PACIFIC AQ, FM, GU, MH, MP, NR, PF, PH, PW, TK, UM,
WF
SAMER SOUTH AR, BO, BR, CL, CO, EC, GF, GY, PE, PY, SR,
AMERICA UY, VE
SEASI SOUTH EAST BN, HK, ID, KH, LA, MM, MO, MY, SG, TH, TL,
ASIA VN

Document and Message Types

Note: The document and message types available for an airline can vary.
Check the Carrier > General > Doc Type Rules tab in DBM for a list of
document types available for your airline.
Graphical Document Type
Document Name Code
Graphical LIR GLR
Non-graphical Document Types
Document Name Code
ACARS Actual ZFW Document AZF

ACARS Final Loadsheet (Brief) FBA
ACARS Final Loadsheet (Extended) FEA
ACARS Final NOTOC NOA
ACARS Final NOTOC Brief NBA
ACARS Preliminary Load Information Message PIA
ACARS Free Text Message AFF
ACARS Preliminary Loadsheet PLA
Baggage Allotment Document BAL
Baggage Requirements Document BGD
Capacity Calculation Document CCD
Cargo Delivery Sequence Message CDS
Cargo Offer CGO
Common Briefing Document BCO
Container Pallet Message CPM
Deadload Uplift/Offload Message DUO
Final Cargo Summary FCS
Final Fuel Figures FFF
Final Loadsheet FLT
Final NOTOC All NOF
Final NOTOC Joining NJF
Final NOTOC Transit NTF
Forecast Zero Fuel Weight FZW
Fuel Monitoring Message FMM
Fuel Order Document FOD
Last Minute Change Document LMC
Load and Trim Data Final LTF
376 Edition 8.5

Document Name Code
Load and Trim Data Provisional LTP

Load Instruction Report LIR
Load Message LDM
Loading Report LDR
Offloading Instruction Report OIR
Operations Control Dangerous Goods Advice DGA
Provisional Loadsheet PLS
Provisional NOTOC All NAP
Provisional NOTOC Joining NJP
Provisional NOTOC Transit NTP
Radio Final Loadsheet FLR
Revised ZFW Document RZF
Statistical Load Summary SLS
ULD Control Message UCM
Water Tank Order WTO
Departure Control Event and Activity Codes

Table: Alta Departure Control Event Codes
EVENT TYPE Event Code FM / CM
ACCEPTANCE STATUS: ACCEPTANCE CLOSED. AAC FM/CM

ACCEPTANCE STATUS: ACCEPTANCE FINALISED. AAF FM/CM
ACCEPTANCE STATUS: ACCEPTANCE AT GATE ONLY. AAG FM/CM
ACCEPTANCE STATUS: ACCEPTANCE OPEN. AAO FM/CM
ACCEPTANCE STATUS: ACCEPTANCE SUSPENDED. AAS FM/CM
FITTED CONFIGURATION UPDATE (AIRCRAFT CONFIGURATION ACV FM/CM
VERSION).
FLIGHT TIMING CHANGE: ADV UPDATE. ADV FM/CM
ACARS FREESEATING MESSAGE PROCESSED. AFS FM
LOAD CONTROLLER ALLOCATION. ALC FM
FLIGHT TIMING CHANGE: ATA UPDATE. ATA FM/CM
FLIGHT TIMING CHANGE: ATD OFF-BLOCKS UPDATE. ATD FM/CM
FLIGHT TIMING CHANGE: ATD AIRBORNE (WHEELS UP) UPDATE. ATW FM/CM
CHANGE (INCREASE OR DECREASE) IN TOTAL NUMBER OF BAG FM
BAGGAGE/CREW BAGGAGE ULDS.
BOARDING STATUS: BOARDING CLOSED. BBC FM/CM
FIRST PASSENGER BOARDED. BBI CM

BOARDING STATUS: BOARDING OPEN. BBO FM/CM

BOARDING STATUS: BOARDING SUSPENDED. BBS FM/CM
COMMON BRIEFING DOCUMENT ISSUED. BCO FM
BOARDING GATE ASSIGNED. BGA FM/CM
BOARDING GATE CHANGED. BGC FM/CM
BAGGAGE REQUIREMENTS DOCUMENT ISSUED. BGD FM
BOARDING STATUS: BOARDING NOT OPEN. BNO FM/CM
BAGGAGE STATUS CHANGED TO CLOSED. BSC CM
BAGGAGE STATUS CHANGED TO FINALISED. BSF CM
BAGGAGE STATUS CHANGED TO OPEN. BSO CM
CAPACITY CALCULATION DOCUMENT ISSUED. CCD FM
EXTERNAL CARGO FINAL. CCO FM
CARGO DELIVERY SEQUENCE DOCUMENT ISSUED. CDS FM
CARGO OFFER ISSUED. CGO FM
EXTERNAL CARGO PROVISIONAL. CIN FM
DISRUPTION STATUS CHANGE: NEW STATUS FLIGHT CNL CM
CANCELLED.
NOTIFY TO PROCESS FINAL COM (CATERING ORDER MESSAGE). COF FM/CM
SALEABLE CONFIGURATION UPDATE. CON FM
CONTAINER PALLET MESSAGE ISSUED. CPM FM
FLIGHT ROUTING UPDATE: ALTERNATE DESTINATION STOP. DAD FM/CM
FLIGHT ROUTING UPDATE: ADDED STOP. DAS FM/CM
FLIGHT ROUTING UPDATE: CANCEL STOP. DCS FM/CM
DISRUPTION STATUS CHANGE: NEW STATUS FLIGHT DFX CM
SUSPENDED (FLIX).
OPERATIONS CONTROL DANGEROUS GOODS ADVICE ISSUED. DGA FM
DISRUPTION STATUS CHANGE: NEW STATUS FLIGHT DIVERTED. DIV CM
DISRUPTION STATUS CHANGE: NEW STATUS LEG SUSPENDED. DLX CM
DOMAIN CHANGE. DOM FM
DEADLOAD UPLIFT OFFLOAD MESSAGE ISSUED. DUO FM
EXTERNAL CAPACITY CALCULATION RECEIVED. ECR FM
EXTERNAL FUEL FIGURES PROCESSED. EFF FM
END OF PROCEDURE MESSAGE ISSUED. EOP FM
AIRCRAFT TYPE UPDATE. EQT FM/CM
FLIGHT TIMING CHANGE: ETA UPDATE. ETA FM/CM
FLIGHT TIMING CHANGE: ETD UPDATE. ETD FM/CM
ACARS FINAL LOADSHEET (BRIEF) ISSUED. FBA FM
FLIGHT CREATE. FCR FM/CM
378 Edition 8.5

DISRUPTION STATUS CHANGE: NEW STATUS FLIGHT DELAYED. FDL CM

FLIGHT FM-CM LINK UP. FDU FM
ACARS FINAL LOADSHEET (EXTENDED) ISSUED. FEA FM
REQUEST ESTIMATES FROM EXTERNAL CARGO SYSTEM FES FM
FINAL FUEL FIGURES DOCUMENT ISSUED. FFF FM
FLIGHT FM-CM DOWN. FLD FM
RADIO FINAL LOADSHEET ISSUED. FLR FM
FINAL LOADSHEET ISSUED. FLT FM
FUEL MONITORING MESSAGE RECEIVED. FMM FM
FUEL FIGURES MANUALLY UPDATED. FMU FM
ACARS FUEL RELEASE MESSAGE RECEIVED. FRA FM
FUEL STATUS CHANGES TO FINAL. FSF FM
FUEL STATUS CHANGES TO HISTORICAL. FSH FM
FUEL STATUS CHANGES TO PROVISIONAL. FSP FM
PROVISIONAL PARTIAL FUELLING, PROVISIONAL STANDBY
TRUCK.
FZFW SENT. FZF FM
GENERAL STATUS: GENERAL STATUS DEPARTED. GGD FM/CM
GENERAL STATUS: GENERAL STATUS LOCKED. GGL FM/CM
GENERAL STATUS: GENERAL STATUS OPENED. GGO FM/CM
GENERAL STATUS: GENERAL STATUS SUSPENDED. GGS FM/CM
GENERAL STATUS: GENERAL STATUS CANCELLED. GGX FM/CM
GRAPHICAL LIR ISSUED. GLR FM
REQUEST HANDOVER CHECKLIST. HCL FM
INBOUND CREATE LOAD DOWNLINE MESSAGE PROCESSED. ICL FM
INBOUND CPM PROCESSED. ICP FM
INBOUND LDM PROCESSED. ILD FM
LOAD MESSAGE ISSUED . LDM FM
LOAD INSTRUCTION REPORT ISSUED. LIR FM
LOAD CONTROL STATUS: CONTROL STATUS CLOSED LLC FM/CM
APPROVE DISTRIBUTION COMPLETED.
LOAD CONTROL STATUS: LOAD CONTROL STATUS CLOSED - LLL FM/CM
APPROVE DISTRIBUTION REQUIRED.
LOAD CONTROL STATUS: LOAD CONTROL STATUS OPEN. LLO FM/CM
LOAD CONTROL STATUS: LOAD CONTROL STATUS CANCELLED. LLX FM/CM
LMC DOCUMENT ISSUED. LMC FM
LOAD CONTROL STATUS: LOAD CONTROL STATUS LOAD SHEET LSF FM/CM
FINALISED LOADSHEET IS SENT.
LOAD AND TRIM DATA FINAL ISSUED. LTF FM

LOAD AND TRIM DATA PROVISIONAL ISSUED. LTP FM

DISRUPTION STATUS CHANGE: NEW STATUS MANUAL ACTION. MAN CM
BCO MESSAGE MAS (MESSAGE ASSURANCE) RECEIVED. MBC FM
ACARS BRIEF MAS (MESSAGE ASSURANCE) RECEIVED. MBL FM
ACARS EXTENDED LOADSHEET MAS (MESSAGE ASSURANCE) MEL FM
RECEIVED.
LOAD AND TRIM DATA FINAL MAS (MESSAGE ASSURANCE) MLF FM
RECEIVED.
LMC DOCUMENT MAS (MESSAGE ASSURANCE) RECEIVED. MLM FM
LOAD AND TRIM DATA PROVISIONAL MAS (MESSAGE MLP FM
ASSURANCE) RECEIVED.
NOTOC DATA FINAL MAS (MESSAGE ASSURANCE) RECEIVED. MNF FM
ACARS NOTOC MAS (MESSAGE ASSURANCE) RECEIVED. MNM FM
NOTOC DATA PROVISIONAL MAS (MESSAGE ASSURANCE) MNP FM
RECEIVED.
ACARS PRELIMINARY LOADSHEET MAS (MESSAGE ASSURANCE) MPL FM
RECEIVED.
PROVISIONAL NOTOC ALL DOCUMENT ISSUED. NAP FM
DISRUPTION STATUS CHANGE: NEW STATUS NOT DISRUPTED. NDI CM
NOTOC DATA FINAL ISSUED. NDF FM
NOTOC DATA PROVISIONAL ISSUED. NDP FM
FINAL NOTOC JOINING DOCUMENT ISSUED. NJF FM
PROVISIONAL NOTOC JOINING DOCUMENT ISSUED. NJP FM
ACARS FINAL NOTOC ISSUED. NOA FM
FINAL NOTOC ALL DOCUMENT ISSUED. NOF FM
FINAL NOTOC TRANSIT DOCUMENT ISSUED. NTF FM
EXTERNAL NTM PROCESSED. NTM FM
PROVISIONAL NOTOC TRANSIT DOCUMENT ISSUED. NTP FM
NOTOC SUMMARY ISSUED. NTS FM
OFFLOAD OF DEADLOAD. OFF FM
OPERATIONAL FLIGHT PLAN RECEIVED. OFP FM
OFFLOADING INSTRUCTION REPORT ISSUED. OIR FM
ONLOAD STATUS: ONLOAD STATUS FINALISED. OSF FM/CM
ONLOAD STATUS: ONLOAD STATUS NOT FINALISED. OSN FM/CM
ACARS PRELIMINARY LOADSHEET ISSUED. PLA FM
PROVISIONAL LOADSHEET ISSUED. PLS FM
RAMP AGENT ALLOCATED. RAA FM
RAMP AGENT ALLOCATION UPDATE. RAU FM
COMMON BRIEFING DOCUMENT REJECTION RECEIVED. RBC FM
ACARS BRIEF LOADSHEET REJECTION RECEIVED. RBL FM
380 Edition 8.5

ACARS RDO RECEIVED. RDO FM

ACARS LOADSHEET REFUSAL RECEIVED. REF FM
REGISTRATION UPDATE. REG FM/CM
ACARS EXTENDED LOADSHEET REJECTION RECEIVED. REL FM
DEPARTURE PLAN ACTIVITY: GATE ACCEPTANCE RGA FM/CM
RESCHEDULED .
ACARS LMC DOCUMENT REJECTION RECEIVED. RLM FM
ACARS NOTOC REJECTION RECEIVED. RNM FM
ACARS PRELIMINARY LOADSHEET REJECTION RECEIVED. RPL FM
RAMP STATUS: RAMP FINALISED. RRF FM
RAMP STATUS: RAMP OPEN. RRO FM
RAMP STATUS: RAMP PROVISIONAL. RRP FM
RAMP STATUS: RAMP SUSPENDED. RRS FM
RAMP STATUS: RAMP CANCELLED. RRX FM
ACCEPTED FROM STANDBY LIST UPDATED. SBA CM
STANDBY PASSENGER LIST UPDATED. SBL CM
CREATE LOAD DOWNLINE MESSAGE ISSUED. SCL FM
STATISTICAL LOAD SUMMARY ISSUED. SLS FM
SEAT RE-PLAN: DUE TO CONFIG / EQUIPMENT CHANGE. SMP CM
FLIGHT TIMING CHANGE: STA UPDATE. STA FM/CM
FLIGHT TIMING CHANGE: STD UPDATE. STD FM/CM
AIRCRAFT SUBTYPE UPDATE. SUB FM/CM
BCO MESSAGE TIMEOUT. TBC FM
ACARS BRIEF LOADSHEET TIMEOUT. TBL FM
ACARS EXTENDED LOADSHEET TIMEOUT. TEL FM
LMC DOCUMENT TIMEOUT. TLM FM
ACARS NOTOC TIMEOUT. TNM FM
ACARS PRELIMINARY LOADSHEET TIMEOUT. TPL FM
ULD CONTROL MESSAGE ISSUED. UCM FM
LOAD CONTROLLER UNALLOCATION. ULC FM
EXTERNAL UWS PROCESSED. UWS FM
ACARS LOADSHEET VALIDATION RECEIVED. VAL FM
ACARS ACTUAL ZFW MESSAGE ISSUED. ZFA FM

Table: Alta Departure Control Activity Codes
Activity Code Description
ACA Send Operating Crew APIS Arrival.

ACD Send Operating Crew APIS Departure.
ADP Archive Departure Plan.
AIA Send Batch Regulatory Message Arrival.
AID Send Batch Regulatory Message Departure.
APA Send APIS Arrival.
APD Send APIS Departure.
AQQ Send Batch AQQ PAXLIST Message.
ASB Trigger BPPR Synchronization.
AZF Send ACARS Actual ZFW Document.
BAL Send Baggage Allotment Document.
BCO Send Common Briefing.
BGD Send Baggage Requirements Document.
BLP Prompt for Boarding Location.
BMM Send Teletype Baggage Manifest Message.
BSP Print BSP Onboard List.
BTM Generates Teletype BTM.
CAP Prompt to Close Acceptance.
CAT Send Catering Figures.
CBP Trigger Prompt To Close Boarding.
CCA Compute Capacity.
CCD Send Capacity Calculation Document.
CCF Check Catering Figures.
CCM Send Close-out Messages (CCM).
CCP Check for Container Pallet Message (CPM).
CDI Autoload.
CEC Check for External Capacity Estimation.
CFF Check for Fuel Figures.
CFP Prompt for Catering Figures.
CGO Send Cargo Offer.
CGS Clean up guaranteed seats (CGS).
CGT Send CG Targeting Parameters.
CHT Print Customers Checked in By Telephone.
CHW Print Customers Checked In by Web.
CIB Cancel Inactive Bags.
CLD Check Load Message.
CLP Close Acceptance.
382 Edition 8.5

COF Notify Process Final Catering Order Message.

CPM Send Container Pallet Message (CPM).
CSM Print CSM Onboard List.
CSP Clean Up Standby Products.
DAL Print Disassociated E-Ticket List.
DGA Send Ops Control Dangerous Goods Advice.
DUO Send Deadload Uplift Offload Message.
ESN Print ESN Onboard List.
ESP Print ESP Onboard List.
ETL Send Electronic Ticket List.
FBA Send Final Loadsheet via ACARS (Brief).
FCF Trigger Customer Product Record Feed (CPR).
FCM Send Teletype Baggage Flight Close Message.
FCP Send Close-out Regulatory Message.

FCR Print Flight Coupon Reconciliation.
FEA Send Final Loadsheet via ACARS (Extended).
FES Return Final E-Ticket Coupon Status.
FFF Send Final Fuel Figures Document.
FIP Finalise Acceptance.
FLN Print Failed Link Customers.
FLR Send Radio Final Loadsheet.
FLT Send Final Loadsheet.
FMM Send Fuel Monitoring Message.
FOD Send Fuel Order Document (FOD).
FOM Send Teletype Baggage Flight Open Message.
FQQ Print FQTV List with CLQF Tier.
FQT Print FQTV List.
FST Send Fuel Status Request.
FTF Terminate Flight CPR Feed.
GAP Gate Acceptance.
GHW Create Handler Warehouse Feed.
GLR Send Graphical Loading Instruction Report.
GOI Send Graphical Offloading Instruction Report.
GPR Generic Print Request.
GRP Print Group List.
GRS Print GRS Onboard List.
HAJ Print Hajj Manifest.

HCL Request Handover Checklist.

ICA Print ICA Onboard List.
IDM Send Industry Discount Message.
IFM Send Interline Fallback Message (IFM).
JSA Trigger Jumpseat Authorisation Process.
LDM Send Load Message (LDM).
LDR Send Loading Report (LDR).
LIR Send Load Instruction Report (LIR).
MAC Trigger Get Mass Airport Control.
MEA Print Meal List.
MEL Print Matched E-Ticket.
MFC Perform Mass Customer Fraud Check.
MSL Send Blockspace Marketing Statistical Summary.
NAP Send All Provisional NOTOC.
NBA Send ACARS Final NOTOC Brief.
NEL Print Not Eligible to Board List.
NJF Send Joining Final NOTOC.
NJP Send Joining Provisional NOTOC.
NOA Send ACARS NOTOC.
NOF Send All Final NOTOC.
NTF Send Transit Final NOTOC.
NTP Send Transit Provisional NOTOC.
NTS NOTOC Summary
OAP Prompt to Open Acceptance.
OAW Create Airline Warehouse Feed.
OBP Trigger Prompt to Open Boarding.
OCP Prompt to Commit Onload.
OIR Send Offloading Instruction Report (OIR).
OPP Open Acceptance.
PAT Perform Auto Transfer.
PCC Prompt Catering Closed.
PCI Process Pre-checked in Passengers Acceptance.
PIA Send ACARS Preliminary Load Information Message.
PIL Send Purser Information List.
PIM Send Seating Pictorial.
PLA Send ACARS Preliminary Loadsheet.
PLB Prompt Last Board Time.
PLS Send Provisional Loadsheet.
384 Edition 8.5

PSB Process Special Baggage List to Messenger.

PSM Send Passenger Service Message (PSM).
PTM Send Passenger Transfer Message (PTM).
RAP Prompt to Resume Acceptance.
RCF Request Crew Figures From External System.
RCR Remove Chargeable Seat Restriction.
REC Check for External Cargo Figures.
RES Request Estimates from External Cargo System.
RFS Repeating Send Final Fuel Status Request.
RMG Retrieve Gate Memos.
RML Retrieve Pre-Flight Memos.
RMO Retrieve In-Flight Memos.
RPF Request Pantry Figures From External System.
RZF Send Revised FZFW Document.
SAF Send Audit and Flight Information.
SBI Send Baggage Information to BRS.
SCL Send Create Load Downline Message.
SCS Send Customer Screening Message.
SEZ Send Forecast Zero Fuel Weight (FZFW).
SFC Send Pax and Bag Counts by Cabin.
SLS Send Statistical Load Summary Message.
SOM Send Seat Occupied Message (SOM).
SPI Print SPI Onboard List.
SPU Print SPU Onboard List.
SRS Print SRS Onboard List.
SUB Send CG Targeting Parameters.
TBF Trigger Baggage Finalisation.
TOB Trigger Open Baggage.
TPL Send Ticketless Product List.
TPM Send Teletype Passenger Manifest (TPM).
UCM Send Unit Load Device Control Message.
UEL Print Unmatched E-Ticket.
UER Print Unassociated E-TKT Due to Database Error.
UST Print UST List.
VAL Print Loadsheet Electronic Signature (Captain's Loadsheet
Validation Message).
VLR Send Vertical Graphical Loading Instruction Report.
VPM Send Valet Parking Message (VPM).

WTO Send the Water Tank Order.
When Are Rules Called?

This section describes when a business rule is called in Flight Management.
For example, when a rule is called at flight create in the Departure Control
system, the data affecting a flight is not updated if you subsequently change the
business rule.
Other rules are called at different stages of the life cycle of a flight. If you change
the rule before the flight calls the rule, the flight is impacted.
Currently, this section only lists the rules that are called at flight create and
disruption.
Table: Flight Management Rules Called at Flight Create and Disruption
Rule Flight Create Flight Disruption
Added No added
stops stops
Aircraft Basic Weight Name Rule on page 70. Y Y Y

Aircraft Maximum Weights Name Rule on page 76. Y Y Y
Baggage Type Rule on page 214. Y Y Y
Baggage Weights Rule on page 81. Y Y Y
Carrier/Aircraft Subtype Fitted Interior Rule on page 84. Y Y Y
Carrier/Aircraft Subtype Rule on page 87. Y Y Y
Crew Baggage Weights Rule on page 90. Y Y Y
Crew Distribution Rule on page 95. Y Y Y
Crew Weights Rule on page 99. Y Y Y
Domain Rule on page 248. Y Y Y
Dry Operating Weight Name Rule on page 105. Y Y Y
Dynamic Passenger Weights Rule on page 108. Y Y Y
Equipment Configuration Rule on page 254. Y
Express Cargo Commodity Rule on page 257. Y Y
Flight Departed Status Rule on page 260. Y Y Y
Flight Event Notification Data Rule on page 266. Y Y Y
Flight Handling Type Rule on page 268. Y Y
Fuel Density Rule on page 129. Y Y
Fuel Retention in Tank Rule on page 138. Y Y Y
Fuel Standard Distribution Name Rule on page 136. Y Y Y
Ground Handling Rule on page 66. Y Y
386 Edition 8.5

Rule Flight Create Flight Disruption
Added No added
stops stops
IATA Service Type Rule on page 276. Y Y

Ideal Trim Area Rule on page 142. Y Y
Inhibit Final Loadsheet Creation Rule on page 287. Y Y
Manual Last Minute Change Rule on page 300. Y Y Y
Notification Priority Rule on page 305. Y Y
Out of Scope System Address Rule on page 322. Y Y Y
Outbound Teletype Message Delivery Rule on page Y Y
315.
Pantry Code Rule on page 155. Y Y Y
Passenger Gender Type Weights Rule on page 325. Y Y Y
Passenger Weights Rule on page 148. Y Y Y
Potable Water Weight Rule on page 169. Y Y Y
Predicted ZFW Fuel Split Rule on page 174. Y Y Y
Selected Passenger and Baggage Statistics Rule on Y Y
page 336.
Taxi Fuel Rule on page 181. Y Y Y
Template Flight Type Rule on page 349. Y Y
ULD Capacity Rule on page 351. Y Y Y

Index
DG/SL Notification, 236

A DGSL Conflicts, 228
DGSL Maximum TI, 234
ACARS, 145, 184, 186, 188, 278
DGSL TI Maximum Height, 239
Activity codes, 382
Documentation Type Facility Routing, 243
Adjacency checks, 228
Domain, 248
Administrator Rules, 183
Dry Operating Weight Change, 102
Advisory conflicts, 230
Dry Operating Weight Name, 105
Audience, 1
duplicating, 41
Autoload, 199
Dynamic Capacity Calculation, 253
Dynamic Passenger Weights, 108
B engineering, 69
Baggage Equipment Configuration, 254
classification, 203 Express Cargo Commodity, 257
commodity creation, 205 Final Fuel Release, 111
segregation, 207 Final Loadsheet Creation, 287
statistics override, 212 Flight Departed Status, 260
type, 214 Flight Departure Minimum Status Required,
weights, 81 263
Business Rules Flight Event Notification Data, 266
ACARS Fuel Status Request Frequency, 184 Flight Handling Type, 268
ACARS Header, 186 flight matching examples, 24, 25
ACARS Response Notification, 188 Forecast Zero Fuel Weight Change, 119
Actual Weights for FZFW Calculation, 113 Forecast ZFW Dependency, 271
administrator, 183 Fuel CG Targeting Processing, 122
Aircraft Basic Weight Name, 70 Fuel Change Tolerance, 127
Aircraft Limitations Message Priority, 72 Fuel Density, 129
Aircraft Maximum Weights Name, 76 Fuel Density Update, 131
application of, 22 Fuel Reduction, 133
Autoload Bulk Mixing, 193 Fuel Retention in Tank, 138
Autoload Distribution Options, 196 Fuel Standard Distribution Name, 136
Autoload Theme Name, 199 Fuel Status, 140
Baggage Classification, 203 Ground Handling, 66
Baggage Commodity Creation, 205 Ground Handling Document Format, 274
Baggage Segregation, 207 IATA Service Type, 276
Baggage Statistics Override, 212 Ideal Trim Area, 142
Baggage Type, 214 Inhibit ACARS Preliminary Loadsheet
Baggage Weights, 81 Creation, 278
Cargo Delivery Sequence, 216 Inhibit Approval of Distribution, 190, 281
Carrier/Aircraft Subtype, 87 Inhibit EOP Creation, 284
Carrier/Aircraft Subtype Fitted Interior, 84 Inhibit Load Instruction Report Creation, 290
Commodity Conversion Threshold, 219 Inhibit Provisional Loadsheet Creation, 293
comparing, 40 Last Minute Change Threshold Limits, 295
Create HUB Containers, 222 Loadsheet Tolerance, 145
creating, 31 mandatory rules, 61
Crew Baggage Weights, 90 Manual Last Minute Change, 300
Crew Distribution, 95 market pair priority, 23
Crew Weights, 99 Maximum Baggage ULD, 303
Deadload Uplift Offload Message Parameter Notification Priority, 305
Selection, 225 NOTOC Emergency Number, 309
deleting, 35 Offload Reasons, 311

Out of Scope System Address, 322 flight groups, 53

Outbound Teletype Message Delivery, 315 markets, 10
Outbound Teletype Message Originator, 319 DOW, 105
overview, 21 Duplicating
Pantry Code, 155 business rules, 41
Pantry Food Content No Uplift, 158 markets, 14
Pantry Food Content Weight, 161
Parallel Run, 324 E
Passenger Gender Type Weights, 325
Passenger Non-Standard Weights, 151 End of procedure message (EOP), 284
Passenger Weights, 148 Event codes, 377
Potable Water No Uplift, 166
Potable Water Weight, 169 F
Predicted ZFW Fuel Split, 174
printing, 47 Fitted interior, 84
Flight groups
Process External Cargo Feed Message, 327
creating, 55
Process External Crew Message, 330
Radio Frequency, 332 definition, 7, 53
Ramp Final Clearance, 334 deleting, 57
displaying, 53
Ramp Tolerance Limits, 176
displaying history, 59
Selected Passenger and Baggage Statistics,
336 managing, 53
Shift Summary Layout, 339 updating, 57
Fuel
SK/SSR Total Volume, 343
change tolerance, 127
Supplementary Information, 346
Taxi Fuel, 181 density, 129, 131, 287
Template Flight Type, 349 final release, 111
forecast ZFW, 119
ULD Capacity, 351
predicted ZFW fuel split, 174
ULD Stock Control, 354
updating, 33 reduction, 133
UWS/NTM Message Processing, 357 standard distribution, 136
status, 140
verifying, 51
taxi, 181
viewing a market, 38
viewing flight usage, 39
WWF Limits, 360 H
WWF Override, 363 History, 45
C I
Cargo Release Status, 114 Ideal trim area, 142
CG Targeting, 122, 287 Introduction, 5
Comparing business rules, 40
Country codes, 371
Creating L
business rule, 31 Last Minute Change, 295
flight groups, 55
markets, 12
Crew
M
baggage, 90 Mandatory conflicts, 230
distribution, 95 Mandatory rules, 61
weights, 99 Markets
closing the display, 12
creating, 12
D deactivating, 17
Deactivating markets, 17 definition, 7
Deleting displaying, 10
business rules, 35 duplicating, 14
flight groups, 57 expanding the display, 11
Departure Control activity codes, 382 history, 18
Departure Control event codes, 377 market definition examples, 9
Departure Plan Simulation, 51, 366 market pairs, 9
introduction, 365 reactivating, 17
DGSL updating, 15
conflicts, 228 Maximum TI, 234
maximum height, 239
maximum TI, 234
Displaying
390 Edition 8.5

Index
P U
Pantry Updating
code, 155 business rules, 33
food weight, 161 flight groups, 57
no uplift of food, 158 markets, 15
Potable water
no uplift, 166 V
weight, 169
Printing a business rule, 47 Verifying a business rule, 51
Viewing
business rule flight usage, 39
R business rule market, 38
Ramp
final clearance, 334 W
tolerance, 176
Reactivating markets, 17 Weights
Rules aircraft maximum, 76
splitting, 43 baggage, 81
crew, 99
crew baggage, 90
S dynamic passenger, 108
Service type codes, 371 passenger gender type, 325
Simulation passengers, 148
departure plan, 366 Window
create rule, 28
T search rule, 27
Transport index, 234

Amadeus Altea Administration Flight Management Business Rules UG May2016

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Amadeus Altea Administration Flight Management Business Rules UG May2016

Uploaded by

Copyright:

Available Formats

Amadeus Alta

2016 Amadeus s.a.s.

Amadeus Learning Services

Before You Start ..................................................................................... 1

2016 Amadeus s.a.s. - All Rights Reserved i

Potable Water No Uplift Rule............................................................ 166

2016 Amadeus s.a.s. - All Rights Reserved iii

Outbound Teletype Message Originator Rule ................................... 319

Purpose of This Document

Functionality that can be activated upon request is indicated in this document

Related Reference Material

Note: Information on the following functions is available in online help format

2016 Amadeus s.a.s. - All Rights Reserved learning@amadeus.com 1

Latest Version of This Document

For Airline and Ground Handler Agents:

For Airline Supervisors and Helpdesk Agents:

For Ground Handler Supervisors and Helpdesk Agents:

Feedback on This Document

What's New in This Document

New Business Rules

Activation Business Rule

Y DG/SL Notification Rule on page 236.

Modified Business Rules

Activation Business Rule

Y Additional fields in the Fuel CG Targeting Processing Rule on page 122.

Activation Business Rule

2016 Amadeus s.a.s. - All Rights Reserved learning@amadeus.com 3

Introduction to Business Rules

Flight Management Business Rules Called by Customer

2016 Amadeus s.a.s. - All Rights Reserved learning@amadeus.com 5

Starting the Business Rules Application

Example: Alta Administration File Menu

The Amadeus Business Rules menu contains the following options:

Table: Reference to Menu Options Description

This Menu Option: Is Described in:

Market Management Managing Markets on page 9.

Market Pair Rules

2016 Amadeus s.a.s. - All Rights Reserved learning@amadeus.com 7

What Are Markets and Market Pairs?

Examples of Market Definitions

Market Name Level Definition Explanation

OTHERFRANCE Country +FR-PAR All airports in country FR

2016 Amadeus s.a.s. - All Rights Reserved learning@amadeus.com 9

Displaying Existing Markets

Example: Search Markets Screen

Table: Search Markets Fields

Example: Market Management Screen

How to Expand the Market Display

2016 Amadeus s.a.s. - All Rights Reserved learning@amadeus.com 11

Example: Expanded Market Screen

How to Close the Market Display

Example: Create Market Screen

Table: Create Market Fields

Name The unique name of the market.

Example: New Market Including Two Country Elements

2016 Amadeus s.a.s. - All Rights Reserved learning@amadeus.com 13

Example: New Market Excluding One Airport Element

How to Duplicate a Market

Example: Duplicate Market Screen

Example: Update Market Screen

2016 Amadeus s.a.s. - All Rights Reserved learning@amadeus.com 15

Example: Updated Market Screen

Deactivating and Reactivating Markets

How to Deactivate a Market