This guide contains information about how to:
There are currently three different ways to register that a ULD is changing status.
The Enter ULD page is where you confirm that ULD you are registering has the correct information.
Currently, there are five different statuses in ULD Tracker:
Important notes:
In Scan ULD you can quickly acquire the ID of the ULD by using the device’s camera to take an image of the ULD’s ID. This image is then processed to see if the ID is readable.
At the bottom of the page the user has three buttons to select from:
If the ID in the image is readable the user is transferred to the Enter ULD page, where the ID is prefilled. If the ID is only able to be partially read, for example, if the first two letters are missing, the user will then be notified that the ID is not valid, and unable to proceed until it has been completed.
If the ID was not readable, the user is shown the image and asked if they wish to try again, or give up and enter the ID manually.
In Read Barcode it is possible to scan barcode and QR code tags, and thereby find the ULD through the tag. It is a requirement to work that there is a tag of the relevant type, with the correct ID, associated with the ULD. If a tag is found, the user will be transferred to the Enter ULD page, with the ULD ID replaced with the tag ID.
You can track which ULDs are connected to which Flight Number by clicking on the Set Flight Number button, as shown below.
This will take you to the Flight Number Management screen, as seen below. Here, you can enter a Flight Number which will then be allocated to all ULDs scanned by this device.
To start using a Flight Number, you first type it into to field and press update, if another colleague is already working with the same Flight Number you will be able to see the ULDs they have already allocated. When you are finished allocating ULDs to that particular Flight Number, you can press the Clear button to clear the screen, or simply type in a new Flight Number and press the Update button.
If a Flight Number has been selected, it will appear on the Enter ULD screen, as seen below, to indicate that newly scanned ULDs will be allocated this Flight Number.
Important notes:
You can stack ULD’s clicking on the Set Flight Number button, as shown below. Using stacks of ULDs enables you to easily scan a single ULD in the stack, and update the whole stack without scanning each individually.
This will take you to the ULD Stack Management screen, as seen below, where you can either find and continue stacking using an already existing stack, create a new stack, see existing stacks or return to the Dashboard.
When you no longer need to add additional ULDs to the stack, you can click the Manage Stack button on the Dashboard again.
When you are working with a stack, and return to the ULD Stack Management page, you are shown information about the current stack:
You also have the option of either clicking the Disassemble button or the Finish button. Clicking the Disassemble button will prompt the user and ask if they are sure they wish to disassemble the stack and thereby removing all connections between each element of the stack.
Clicking the Finish button, simply means you are finished stacking using the current stack.
Important notes:
The ULD Tracker, together with ULDRadar, simplifies logistics behind stock controls by automating many of the associated tasks. With the app, you can view a list of all airlines with stocked ULDs at your location and how many are currently in stock.
The app provides a color-coded status for each stock control
message, as follows:
As long as
the stock control has not been approved it can be continually adjusted,
otherwise a new stock control needs to be initiated.
You can
start a new stock control for any airline by clicking on the inspection button on
the left of the screen, this will prompt you first, before beginning a new
stock control. Once a new stock control has been started, every ULD that is
currently registered as being in stock and used by that airline will be shown,
as seen below:
The following
is an explanation of what each part is used for:
The primary way to conduct stock control using the ULD Tracker app, is to scan each ULD on stock, which helps you find ULDs that have not been registered correctly, or not registered at all, and add them to the list immediately, or display which ULDs have not been found on among your stock.
If an ULD is, for one reason or another, not found in your stock, you can still approve the stock control, though this will update the missing ULDs status to missing, so you can handle that issue separately.
It is important to note:
It is important
to note:
The ULD
Tracker app allows you to receive incoming ULD Control Messages (UCM) to
help manage ULDs that are arriving. These messages can help you confirm whether
the arriving ULDs are correct, and identify any missing or incorrectly sent
ULDs.
Before the
UCM’s can be handled through the ULD Tracker app, a small amount setup is
needed:
UCM
{FlightNo}/{Date}.{FlightRegNo}.{Location}
IN
{UldId}
The
following is an explanation of each component in the format, and what it means.
For example, the following UCM is designated for the CCC ground handler:
UCM
AA1111/01JAN.AABBB.CCC
IN
.PAG00000AA.PAG00001AA.PAG00002AA
.PAG00003AA.PAG00004AA
This page
shows a list of the UCMs, with appropriate information:
By clicking
on the inspect button, you can see the IDs of the ULDs, as well as if they have
been received.
There are
two buttons at the bottom of the screen:
When a flight number associated with UCM is set, you can see how many ULDs are expected and how many have already been scanned by clicking on the overview button, as seen below:
This will show you a page with a list of the expected and
active ULDs. The ULDs move from being expected to active once they are
registered as inbound, as seen
below:
Overall, the ULD Control feature simplifies the process of managing incoming ULDs by providing a clear overview of expected and active ULDs, allowing you to efficiently keep track of your inventory and avoid potential issues.
· {FlightNo} is the flight number
· {Date} is the current date, shortened to the DDMMM format, such as 01JAN.
· {FlightRegNo} is the airplanes registration number
· {Location} is the location key, matching your ground handler.
· {UldId} is the ID(s) for the arriving ULD(s).
o If no ULD’s are expected it is written as ‘.N’. Thereby denoting that no ULD’s are expected, and preventing the empty UCM from being shown in the ULD Tracker.
o If one or more ULDs are expected, it is written in ‘.XXXYYYYYZZ’, with each repeating ID being added onto the last, with a newline after each third ID.
For example, the following UCM is designated for the CCC ground handler:
UCM
AA1111/01JAN.AABBB.CCC
IN
.PAG00000AA.PAG00001AA.PAG00002AA
.PAG00003AA.PAG00004AA