Documente Academic
Documente Profesional
Documente Cultură
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
Published by:
May 2016
Table of Contents
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
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
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
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
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
2 Edition 8.5
Before You Start
Other Changes
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.
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.
6 Edition 8.5
Chapter 1 Introduction to Business Rules
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.
Managing Markets
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.
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.
To change your search criteria, click on New Search in the Search Criteria
frame at the top of the 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.
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
Chapter 2 Managing Markets
Field Explanation
3. When you have entered a new market element type and code, click on
Include to add it to the market.
4. To exclude an element, enter the element type and code in the Type and
Code fields, then click on Exclude.
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.
14 Edition 8.5
Chapter 2 Managing Markets
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
1. In the Market Management screen, select the market in the tree view.
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.
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.
16 Edition 8.5
Chapter 2 Managing Markets
Field Explanation
18 Edition 8.5
Chapter 2 Managing Markets
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.
Managing Rules
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.
The following table shows the weights used in the Outbound Teletype Message
Delivery rule.
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.
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:
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:
Version 1
Market Pair M3-M1 Baggage Details Required
Flight No. Range 8X1-9 Hold: Weight
Day of Week 12345 Cabin: Weight
Version 2
Market Pair M3-M2 Baggage Details Required
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:
24 Edition 8.5
Chapter 3 Managing Rules
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.
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:
Version 1
Market Pair M3-M1 Baggage Details Required
Flight No. Range 8X1-9 Hold: Weight
Day of Week 12345 Cabin: Weight
Version 2
Market Pair M3-M2 Baggage Details Required
Flight No. Range 8X1-99 Hold: Weight
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.
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
Chapter 3 Managing Rules
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:
If you click Create or press Enter, the Create Rule window appears.
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
Chapter 3 Managing Rules
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.
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
Chapter 3 Managing Rules
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.
32 Edition 8.5
Chapter 3 Managing Rules
Updating Rules
How to Update a Rule
1. In the rule screen, select the rule you want to update from the list.
2. Click on Update.
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.
34 Edition 8.5
Chapter 3 Managing Rules
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.
2. Click on Delete.
A confirmation message appears.
36 Edition 8.5
Chapter 3 Managing Rules
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.
38 Edition 8.5
Chapter 3 Managing Rules
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.
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.
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
Chapter 3 Managing Rules
Duplicating Rules
How to Duplicate a Rule
1. In the rule screen, select the rule you want to duplicate from the list.
2. Click on Duplicate.
3. In the Duplicate screen, make any changes you require for your new rule.
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.
42 Edition 8.5
Chapter 3 Managing Rules
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.
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
Chapter 3 Managing Rules
You can enter the following information to search for rule history.
Field Explanation
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
Chapter 3 Managing Rules
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.
Field Description
48 Edition 8.5
Chapter 3 Managing Rules
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.
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.
In this example, the tag FRANCE has been found in two versions of the rule.
50 Edition 8.5
Chapter 3 Managing Rules
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.
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.
This field is mandatory.
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.
This field is optional.
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.
54 Edition 8.5
Chapter 4 Managing Flight Groups
To change your search criteria, click on New Search in the Search Criteria
frame at the top of the screen.
Field Explanation
Reference data airline The 2-character code of the airline that owns the flight
groups, which is your own airline.
This field is mandatory.
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.
This field is mandatory.
Flight group description The free-flow text description of the flight group.
This field is optional.
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.
4. To delete a flight or flight range that you have added, click on it, then click on
Delete.
5. Click on Save.
56 Edition 8.5
Chapter 4 Managing Flight Groups
- 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.
58 Edition 8.5
Chapter 4 Managing Flight Groups
Field Explanation
Field Explanation
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.
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.
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
64 Edition 8.5
Chapter 6 Ground Handling Rules
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
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
Field Explanation
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.
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
70 Edition 8.5
Chapter 7 Engineering Rules
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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
Chapter 7 Engineering Rules
Example: Carrier & Aircraft > CG Data > WT/CG Limit Buffer Tab in DBM
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
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 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.
Day of Week The days that this row applies to, such as 12 (for Monday
4
and Tuesday).
The following rule content window is displayed, based on the search criteria:
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'
(Message) Priority when
Limit Exceeded at 'LC'
(Message) Priority when
Limit Exceeded at 'LF'
(Message) Priority when
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.
(Message) Priority when
WT/CG Buffer Limit
Breached at 'LL'
(Message) Priority when
WT/CG Buffer Limit
Breached at 'LC'
74 Edition 8.5
Chapter 7 Engineering Rules
Field Explanation
For all 6X World Market flights operating with aircraft subtype 74K the message
priority is set for each Load Control status.
If the message is sent with very high or high priority, a warning message is
displayed.
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
76 Edition 8.5
Chapter 7 Engineering Rules
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
78 Edition 8.5
Chapter 7 Engineering Rules
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
Market Mandatory.
0
Destination The market of the flight destination.
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
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
The following rule content window is displayed, based on the search criteria:
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:
In this example, flight 9S123, when operated by aircraft subtype 733, also
operates the 9S124, which departs on the following day (+1).
80 Edition 8.5
Chapter 7 Engineering Rules
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.
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
Flight No. Range 16 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range (s).
The registration number of the specific aircraft, for
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).
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
82 Edition 8.5
Chapter 7 Engineering Rules
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
Flight No. Range 4 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range (s).
84 Edition 8.5
Chapter 7 Engineering Rules
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
86 Edition 8.5
Chapter 7 Engineering Rules
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
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.
The days that this row applies to, such as 12 (for Monday
Day of Week 4
and Tuesday).
Effective
From The starting and ending effective date of this row in the
2
format DDMMMYY.
Effective To
STD From The starting and ending standard time of departure in the
1
STD To format HH:MM.
The following rule content window is displayed, based on the search criteria:
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
Chapter 7 Engineering Rules
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
Chapter 7 Engineering Rules
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
Flight No. Range 2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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
Chapter 7 Engineering Rules
If activated, the Rule Content panel displays the following additional fields.
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).
When the rule defines that crew baggage is received from the check-in system.
94 Edition 8.5
Chapter 7 Engineering Rules
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.
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
The following rule content window is displayed, based on the search criteria:
96 Edition 8.5
Chapter 7 Engineering Rules
Rule Contents
Field Explanation
98 Edition 8.5
Chapter 7 Engineering Rules
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.
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
Flight No. Range 2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range (s).
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
The BW & BI Modification Allowed setting in DBM determines whether the Load
Controller can modify the Basic Weight and Basic Index values.
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.
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 0 The aircraft subtype, as defined in DBM. Mandatory.
Registration 4
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
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).
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.
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
Flt No. Range 8 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range (s).
The days that this row applies to, such as 12 (for
4
Day of Week Monday and Tuesday).
Effective From The starting and ending effective date of this row in the
2
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Flight No. Range 2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range (s).
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
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.
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).
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Operating Carrier 0
Market Origin 0 The market of the flight origin. Mandatory.
Market
0 The market of the flight destination. Mandatory.
Destination
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
Field Explanation
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.
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: Secondary ZFW Figures Window, from the Payload by Destination Button
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
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 The aircraft subtype, as defined in DBM.
16
Example: A380-800
Registration 4
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
Field Explanation
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.
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.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 32 The aircraft subtype, as defined in DBM.
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
8 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Ranges.
Effective From The starting and ending effective date of this row, in the
2 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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%.
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
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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
Flight No. Range 1 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range(s).
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
Fuel Density Select this check box if the Load Controller is allowed to update the
Update Allowed fuel density. Mandatory.
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.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
Mandatory.
Market Origin 0
The market of the flight origin.
Market Mandatory.
0
Destination The market of the flight destination.
Carrier/Aircraft The aircraft subtype, as defined in DBM.
16
Subtype
Flight No. Range
8 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Ranges.
Template Flight Select from the following code:
Type LH - Long-haul
SH - Short-haul
4 CF - Charter
DF - Domestic
SF - Shuttle
CO - Cargo
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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.
Example: Carrier & Aircraft > Fuel > Standard Distribution Tab in DBM
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 16 The aircraft subtype, as defined in DBM.
Registration 4
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
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
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Mandatory.
Market Origin 0
The market of the flight origin.
Market Mandatory.
0
Destination The market of the flight destination.
Carrier/Aircraft The aircraft subtype, as defined in DBM.
16
Subtype
Flight No. Range
8 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Ranges.
Template Flight Select from the following code:
Type LH - Long-haul
SH - Short-haul
4 CF - Charter
DF - Domestic
SF - Shuttle
CO - Cargo
Effective From The starting and ending effective date of this row, in the
1
format DDMMMYY.
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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.
Rule Criteria
Flight No. Range 16 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range (s).
The template flight type code.
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Market Origin 0 The market of the flight origin. Mandatory.
Market
0 The market of the flight destination. Mandatory.
Destination
The days that this row applies to, such as 12 (for
Day of Week 8
Monday and Tuesday).
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
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.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Operating Carrier 0
Market Origin 0 The market of the flight origin. Mandatory.
Market
0 The market of the flight destination. Mandatory.
Destination
Aircraft Subtype 0 The aircraft subtype, as defined in DBM. Mandatory.
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range (s).
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
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
before a significant change before a significant change
is identified. is identified.
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
before a significant change before a significant change
is identified. is identified.
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.
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.
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.
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.
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: The weight of passengers may vary according to their class of travel.
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
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 8 The aircraft subtype, as defined in DBM.
Registration 4
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
No Uplift of Pantry Select to identify flights that do not uplift any food.
Food Content
The load controller can make adjustments, if required, on the Pantry window.
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:
Aircraft Schedule Rule on page 79, to identify subsequent flights.
Pantry Food Content No Uplift Rule on page 158, to identify which flights do
not uplift food.
Rule Criteria
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 128 The aircraft subtype, as defined in DBM.
Registration 64
Fitted Interior
32
Name
STD From 16 Standard departure times.
STD To 8
Flight No. Range
4 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
2 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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.
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
Aircraft Schedule Rule on page 79, to identify subsequent flights.
Potable Water Weight Rule on page 169, to determine the weight of potable
water to add to the first flight.
Rule Criteria
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 8 The aircraft subtype, as defined in DBM.
Registration 4
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
No Uplift of Potable Water Select this check box if no potable water is to be uplifted.
The load controller can make adjustments, if required, on the Potable Water
Dialog window, by selecting the Manually Updated check box.
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:
Aircraft Schedule Rule on page 79, to identify subsequent flights.
Potable Water No Uplift Rule on page 166, to identify which flights do not
uplift potable water.
Rule Criteria
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 64 The aircraft subtype, as defined in DBM.
Registration 32
STD From 16 Standard departure times
STD To 8
Flight No. Range
4 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
2 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
1950 kgs of potable water is loaded if the booked passenger figure is
between 151 and 225.
2600 kgs of potable water is loaded if the booked passenger figure is
between 226 and 300.
Flight Management calculates the weight of potable water to be loaded before the
Forecast Zero Fuel Weight message is sent.
Note: The Index value, and the values displayed in the Resolution field, are
taken from the DBM Potable Water Distribution tab.
Example: Carrier & Aircraft > SWA > Potable Water Distribution Tab in DBM
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
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 32 The aircraft subtype, as defined in DBM.
Template Flight Select from the following code:
Type LH - Long-haul
SH - Short-haul
16 CF - Charter
DF - Domestic
SF - Shuttle
CO - Cargo
The following rule content window is displayed, based on the search criteria, and
the option you select in the Trim Tolerances panel:
Rule Contents
Field Description
Field Description
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
Administrator Rules
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
The following rule content window is displayed, based on the search criteria:
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.
Rule Criteria
The following rule content window is displayed, based on the search criteria:
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
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
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
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
The following rule content window is displayed, based on the search criteria:
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
Provisional status is provisional.
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.
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
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 0 Mandatory. The aircraft subtype, as defined in DBM.
Registration 16
Flight No. Range
8 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
The days that this row applies to, such as 12 (for Monday
Day of Week 2
and Tuesday).
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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
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 16 The aircraft subtype, as defined in DBM.
Flight No. Range
8 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
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
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Description
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.
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.
Rule Criteria
Flight No. Range 16 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
The template flight type code:
LH - Long-haul
SH - Short-haul
Template Flight
8 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Market Origin 4 The market of the flight origin.
Market
4 The market of the flight destination.
Destination
The days that this row applies to, such as 12 (for
Day of Week 2
Monday and Tuesday).
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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:
Rule Criteria
Flight Group 16 To specify the flight number range, click on and select
the Flight Group Keyword or the Flight Range.
The days that this row applies to, such as 12 (for Monday
Day of Week 4
and Tuesday).
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
For all 6X World Market flights using the LH template the LONGHAUL baggage
classification category is used.
Rule Criteria
Flight Group 32 To specify the flight number range, click on and select
the Flight Group Keyword or the Flight Range.
Aircraft
8 The aircraft subtype, as defined in DBM.
Subtype
Day of Week 2 Example: 12 (for Monday and Tuesday).
Registration 4
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
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.
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.
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
The following rule content window is displayed, based on the search criteria:
Layout 1, baseline:
Rule Contents
Field Explanation
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.
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.
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.
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
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
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
Flight No. 8
To specify the flight number range, click on and select
Range the Flight Group Keyword or the Flight Range.
Effective From The starting and ending effective date of this row in the
2
Effective To format DDMMMYY.
The days that this row applies to, such as 12 (for Monday
Day of Week 1
and Tuesday).
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Operating Carrier 0
Mandatory.
Market Origin 0
The market of the flight origin.
Mandatory.
Market Destination 0
The market of the flight destination.
Outbound Terminal 16
Aircraft Subtype 8 The aircraft subtype, as defined in DBM.
Departure Time From Format 12:00
4
Departure Time To
Effective From The starting and ending effective date of this row, in
2 the format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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.
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
Flt No Range 32 To specify the flight number range, click on and select
the Flight Group Keyword or the Flight Range.
The following rule content window is displayed, based on the search criteria:
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.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Related Rules
The parameters you define in this rule are used to route the DUO document or
message in the following rules:
Document Type Facility Routing Rule on page 243.
Outbound Teletype Message Delivery Rule on page 315.
Outbound Teletype Message Originator Rule on page 319.
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Rule Criteria
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
The settings apply to the DG/SL code RNG (non-flammable, non-toxic gas).
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.
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 must select the Acknowledged check box and click on
Update, but separation of the DG/SLs is not mandatory.
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
Mandatory.
Market Origin 0
The market of the flight origin.
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 0 Mandatory. The aircraft subtype, as defined in DBM.
Registration 4
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
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.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 16 The aircraft subtype, as defined in DBM.
Registration 8
Flight No. Range
4 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 0 Mandatory. The aircraft subtype, as defined in DBM.
Registration 4
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
Note: In the Locations table, define each location in the aircraft that has
requirements for DG/SL TI maximum height.
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:
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
The following rule content window is displayed, based on the search criteria:
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.
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.
See Note 1 and Note 2.
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.
See Note 1 and Note 2.
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.
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.
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: 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
The following rule content window is displayed, based on the search criteria:
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.
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
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
Rule Criteria
Mandatory.
Carrier 0
The two-character code of the operating carrier.
Mandatory.
Market Origin 0
The market of the flight origin.
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 8 The aircraft subtype, as defined in DBM.
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Flight No. Range
4 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Mandatory.
Market Origin 0
The market of the flight origin.
Market Mandatory.
0
Destination The market of the flight destination.
Select from the following code:
LH - Long-haul
SH - Short-haul
Template
2 CF - Charter
Flight Type
DF - Domestic
SF - Shuttle
CO - Cargo
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Description
Rule Criteria
Mandatory.
Market Origin 0
The market of the flight origin.
Market Mandatory.
0
Destination The market of the flight destination.
Flight Group
8 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Aircraft Subtype 4 The aircraft subtype, as defined in DBM.
Registration 2
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
1 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
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
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.
Rule Criteria
Operating Airline 0
Market Origin 0 Mandatory. The market of the flight origin.
Market
0 Mandatory. The market of the flight destination.
Destination
Flight No. Range
16 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
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
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Description
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
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
Rule Criteria
Flight No. To specify the flight number range, click on and select
8
Range the Flight Group Keyword or the Flight Range.
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
4 CF - Charter
Types
DF - Domestic
SF - Shuttle
CO - Cargo
Effective From The starting and ending effective date of this row in the
2
Effective To format DDMMMYY.
Day of Week 1 The days that this row applies to, such as 12 (for Monday
and Tuesday).
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
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.
Registration 16
IATA Service The IATA service type, as defined in the IATA Service
8
Type Type rule.
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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
The following rule content window is displayed, based on the search criteria:
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.
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
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 32 The aircraft subtype, as defined in DBM.
Flight No. Range
16 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
8 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Terminal 4
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
The following rule content window is displayed, based on the search criteria:
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)
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
The following rule content window is displayed, based on the search criteria:
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
Provisional status is provisional.
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.
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:
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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.
Rule Criteria
Operating Carrier
Market Origin
Market Destination
Aircraft Subtype 4 The aircraft subtype, as defined in DBM.
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
8 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in
1 the format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
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).
Rule Description
This rule determines the conditions when a final loadsheet cannot be created for
a flight.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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.
Rule Criteria
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 32 The aircraft subtype, as defined in DBM.
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.
Effective From The starting and ending effective date of this row, in the
2 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
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
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:
Rule Description
This rule determines what the Cargo Release Status must be before the load
controller can create the Loading Instruction Report (LIR).
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Rule Contents
The following rule content window is displayed, based on the search criteria:
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.
Related Rules
This rule can be used in conjunction with theInhibit ACARS Preliminary
Loadsheet Creation Rule on page 278.
Rule Criteria
Flight No. Range 16 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
Select from the following code:
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.
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
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.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
Mandatory.
Market Origin 0
The market of the flight origin.
Market Mandatory.
0
Destination The market of the flight destination.
Aircraft Subtype 4 The aircraft subtype, as defined in DBM.
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
One of the following rule content windows is displayed, based on the search
criteria and activation:
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.
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
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.
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.
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.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Related Rules
LMC thresholds for weights and trim changes are defined in the Last Minute
Change Threshold Limits Rule on page 295.
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 4 The aircraft subtype, as defined in DBM.
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
The following rule content window is displayed, based on the search criteria:
Rule Contents
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.
In the Last Minute Change window, the Load Controller can select the Allow
LMC check box.
See Last Minute Change Threshold Limits Rule on page 295 for an example of
the LMC information in Supplementary Information in the final loadsheet.
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.
Baggage Statistics Override Rule on page 212.
Rule Criteria
Flight Group 8 To specify the flight number range, click on and select
the Flight Group Keyword or the Flight Range.
The days that this row applies to, such as 12 (for Monday
Day of Week 4
and Tuesday).
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
For all 6x World Market flights operating with aircraft subtype 744 the maximum
number of baggage ULDs will be 10.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Rule Contents
The following window is displayed, based on the search criteria:
Rule Content panel when the Configure by Load Control Status field is selected:
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.
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.
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Market Mandatory.
0
Destination The market of the flight destination.
Flight No. Range
4 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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.
The Comments field is optional, except for the reasons with the Mandatory
Comments field selected. For example:
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
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
Related Rules
The Outbound Teletype Message Delivery Rule on page 315 defines the delivery
addresses for TTY messages.
Rule Criteria
Outbound Terminal 32
Inbound Terminal 32
Flight No. Range
8 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Day of Week 2
Effective From The starting and ending effective date of this row, in
1 the format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
Rule Criteria
Flight Nb Range
To specify the flight number range, click on and
0 select the Flight Group Keyword or the Flight Range.
Mandatory.
Subject to activation, this field is optional with a
2
weighting of 2
The following rule content window is displayed, based on the search criteria:
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.
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.
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
Activated for parallel run Select to activate the parallel run functionality.
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
Flight No. Range 1 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: The weight of passengers may vary according to their class of travel.
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
Flight No. Range 2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule 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.
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.
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
Flight No. Range 4 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Example: Carrier & Aircraft > General > AC Sub Type Rules
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
Rule Criteria
Flight No. Range 2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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.
Baggage Statistics Override Rule on page 212.
WWF Override Rule on page 363.
Rule Criteria
Operating Carrier 0
Mandatory.
Market Origin 0
The market of the flight origin.
Market Mandatory.
0
Destination The market of the flight destination.
Flight Group
8 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
Select from the following code:
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 and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Type of data
With activation, additional fields can be chosen for the Shift Summary views.
Rule Contents
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.
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.
Rule Criteria
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
Rule Description
This rule defines which type of information is included in the Supplementary
Information section of a Flight Management document or message.
Note: In a ground handling solution, this rule is called from the reference data
of the ground handling organisation.
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
Market Mandatory.
0
Destination The market of the flight destination.
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.
Aircraft Subtype 8 The aircraft subtype, as defined in DBM.
Flight No. Range
2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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.
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
Flight No. Range 2 To specify the flight number range, click on and
select the Flight Group Keyword or the Flight Range.
IATA Service The IATA service type code. For example, J is for a
1
Type passenger flight.
The following rule content window is displayed, based on the search criteria:
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.
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.
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
Day of Week The days that this row applies to, such as 12 (for
4
Monday and Tuesday).
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
2 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
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.
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
Market Mandatory.
0
Destination The market of the flight destination.
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
32 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
Aircraft Subtype 16 The aircraft subtype, as defined in DBM.
Registration 8
Flight No. Range
4 To specify the flight number range, click on and
select the Flight Group Keyword, or Flight Ranges.
STD 2 The starting and ending Standard Time of Departure.
Effective From The starting and ending effective date of this row, in the
1 format DDMMMYY.
Effective To
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
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.
Rule Criteria
Rule Contents
The following window is displayed, based on the search criteria:
Field Explanation
Rule Criteria
The following rule content window is displayed, based on the search criteria:
Rule Contents
Field Explanation
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
Operating Carrier 0
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).
Select from the following code:
LH - Long-haul
SH - Short-haul
Template Flight
8 CF - Charter
Type
DF - Domestic
SF - Shuttle
CO - Cargo
The days that this row applies to, such as 12 (for
Day of Week 4
Monday and Tuesday).
Effective From The starting and ending effective date of this row in the
1
Effective To format DDMMMYY.
The following rule content window is displayed, based on the search criteria:
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.
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.
Field Description
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 (/).
Field Description
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.
Reference Information
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
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
Region Codes
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
Added No added
stops stops
Added No added
stops stops
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
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