How to achieve Automation in Load Control (Part 3 of 7)
On an everyday basis the Load Controller executes many leg handling tasks that can be easily processed automatically. Please read in this blog why and how.
Welcome back to part three of my blog sequence “How to achieve Automation in Load Control”
In my last blog, I wrote about how ideally “Automated Shift Management on the day of operations” can help airlines managing larger numbers of Load Controllers during their shifts. The next automation driver for Load Control that I identified is the following one:
- Automation of (repetitive) Flight Handling Tasks / Procedures
Automated Flight Handling Tasks / Procedures
In order to create the load sheet and the load plan (or the loading instruction) the Load Controller executes many leg handling tasks or procedures on an everyday basis that - because they are repetitive - can be easily processed automatically. This will relieve him from these repetitive tasks and he can focus on the relevant management of load control exceptions resulting from operational deviations.
About what kind of repetitive tasks am I talking about?
Four selected examples are:
- Automatic Pax and Bag Weight Generation: Here Pax and Bag weight tables are automatically assigned to a flight for fuel saving reasons. Example: Pax weights might differ for flights within Europe (= use of standard pax weight tables) and Japan (= Passenger averagely will weigh less). Or you decide that during summer people generally wear less clothes and therefore have less weight. The user doesn´t have to choose them from any list or drop down menu manually as the pax weight will be assigned automatically for each flight.
- Automatic Pantry/Galley Code Assignment: A certain Pantry Code or the Galley code will be assigned automatically to any chosen flight. This allows the automated adjustment of weights considering that on some flights only drinks are served as on others a tray service is provided. As a result fuel can be saved as well.
- Automatic Potable Water Assignment: A preconfigured potable water value is automatically assigned to the flight leg for fuel saving reasons, taking into consideration that the amount of potable water can be reduced for short (domestic) flights or due to the booking situation.
- Automatic use of historical data: If desired, a system shall allow to automatically use the history data base for bags, cargo mail and EIC for the most accurate EZFW estimation.
Of course the configuration of such flight handling tasks in a load control system shall allow the user to stay fully flexible. This can be achieved by providing Load Control users or system administrators to be very specific under which circumstances exactly specific automation rules shall apply, such as for a:
- single flight number (only),
- commercial area,
- departure airport,
- arrival airport,
- certain city pair,
- specific aircraft owner,
- distinction between a domestic, continental or intercontinental flight,
- specific season (winter, summer or other pre-defined),
My advice is therefore that it is important for airlines to check such configuration options within their Load Control system, when automation is one of their main business objective.
For the next part of my blog sequence “How to achieve Automation in Load Control” I will share my ideas about the following two topics can contribute:
- Automated Background Checks including automated alerting warning mechanisms
- Automated Messaging
Until then I very look forward to hearing your feedback about this blog. Please stay tuned.
Michael Muzik Linked In Profile:
For the other blogs of this serial please click here: