them out and show some examples how the XML
files and the newly achieved paperless transactions
affect the work in airports:
Order to Caterer: Current flight plans and orders
from the airline to the caterer are sent weekly and
via e-mail. The caterer then enters the data into his
individual software and has to assign e.g. order to
flights manually. The newly developed structures
provide the caterer with the ability to receive orders
directly and without media disruptions from the
airport and airline system into the caterer system. All
the necessary assignments can then be done
automatically.
Freight List at On-board Server: Currently, the
freight list and the trolley inventory are matched
manually and the sales volume is recorded as a
paper-based list or on a USB device. The XML
structure makes it possible that the freight list now
can be transferred to the server on board. When the
RFID-tagged trolleys are loaded into the aircraft, a
reader sends the loading information from the tag to
the server and the freight list and the real content of
the trolleys can be matched by the system.
Precise Transfer of Trolleys: The new XML
structures allow a precise transfer of trolleys
beginning at the ramp of the caterer. The operator of
the highloader receives the data in form of the
transfer order and can identify the trolleys with the
help of the RFID tags. Mistakes in the correct trolley
to flight assignment are now prevented.
3.4 RFID Tag Structure
Besides the structure of the distributed electronic
XML files as a replacement for paper-based lists, the
configuration of the content of the RFID tags is
another important challenge for standardising the
data flow in the whole catering process. The project
uses a 96-bit UHF RFID transponder for every
transport container and the high-value items (e.g.
expensive duty-free goods) which are also equipped
with an RFID tag. This allows the widest range of
possibilities for implementation (e.g. because of the
low price and high range). The following elements
are part of the RFID structure used in the project
(the complete structure is not shown due to the
limited space):
Five bits are reserved for the type of container (e.g.
trolley, item, and bag). Thirty bits contain the unique
ID of the trolley. Two bits are reserved for the code,
if the trolley has to be maintained or not. Further
elements of the structure are the last maintenance
date, the type of the trolley content, if the trolley
remains in the aircraft or not, information concer-
ning duty and additional information.
3.5 Event-driven Monitoring
Dashboard
Finally, after we have shown the way we integrated
the systems and the data between the participants,
we want to show how to visualize the whole
transaction cycle.
All the relevant objects identified by the central
RFID middleware need to be illustrated and
analysed in a monitoring dashboard. One of the main
requirements is the customisation to the highly
individual processes. Due to this fact, it is not
possible to develop a standard dashboard. For an
individual configuration, the knowledge about all the
relevant performance indicators of the process is
necessary. With the help of these performance
indicators, the project team developed a monitoring
dashboard for the tracking and tracing of the trolleys
covering the whole catering process. This increases
transparency, and several potentials for optimisation
can now be discovered. If there are any bottlenecks
or high deviations of the performance indicators
from the expected values, warnings are displayed
immediately in order to improve the reaction time
along the process.
The target users for such a monitoring dashboard
are airlines interested in a transparent catering
process as well as caterers focussing on a
visualisation of their own processes. For both
parties, different dashboard views are available.
For the development of such a monitoring
dashboard application, we used the commercial
software Progress Apama (cf.
http://web.progress.com/de-de/apama/index.html)
which is based on a complex event processing (CEP)
engine and additionally includes modelling and
execution of an event-driven dashboard. This CEP
platform is specialised for the analysis of a multitude
of events with very low latency. It can react to these
events immediately by using specified event
processing rules and can visualise relevant metrics in
a web-based dashboard. An event in the context of
the project for example is the transit of a trolley
through a gate or an alert which is generated by the
system and shall be visualised in the dashboard. In
contrast to traditional software architectures, an
event-driven architecture is used because of the
capability to react in real-time and a high
performance in processing multiple events.
In the scope of the project Fraunhofer IAO has
published a market overview with different CEP-
tools (cf. Vidackovic, Renner, Rex, 2010). CEP is
INTEGRATION OF VARIOUS IT SYSTEMS AND SENSOR INFORMATION FOR THE HANDLING OF
RFID-ENABLED CATERING GOODS IN THE AVIATION DOMAIN
95