Trial Requirements v1.4

INFLIGHT CATERING
TRIAL Requirements
1/48
Document Status
REVISION
Version Date IATA StB - Authors Notes
1.0 19.04.2007 Nicolas Bondarenco, Initial Version
RFID Deputy Manager
Benoit Pilon, Manager
Airport & Inflight Services
1.1 11.05.2007 Nicolas Bondarenco Add of Handheld scanner screen
functionalities & data structure & data
management process
Update document after Meeting with KLC
and KCS
Reviewed by KLM Catering Notes
Services
- 16.05.2007 Fred Damler Reviewed & validated
Annemieke Heintges
Reviewed KLM Cityhopper Notes
- 16.05.2007 Laslo Zimonyi Reviewed & validated
1.2 11.06.2007 Nicolas Bondarenco Add of the Executive Summary Chapter to
improve the RFID inflight project process
readability
1.3 15.08.2007 Nicolas Bondarenco Add of new requirements due to the add of
additional fixed tracking points:
FR 14.3, FR 14.4, FR14.5, FR110, FR111,
FR 34.2, FR 34.3, FR 48.2, FR 48.3, FR
48.4
Add of the ‘’Washed / Not washed’’ status
(in chapters 3.1 and 5)
Change BDX for Bordeaux to the right ACI
code: BOD
Update chap 7: add of two fixed readers
1.4 04.12.2007 Nicolas Bondarenco Increase number of trolley tags to 2500 in
7.1
REFERENCE DOCUMENTS
ID Title IATA StB - Authors Notes
1 Inflight Catering Nicolas Bondarenco, This document contains all the process
Process Analysis and Benoit Pilon, Manager description and user requirements
User Requirements – (prioritized)
V1.1 – 27 March 2007
2 Minutes of Meeting, Task Nicolas Bondarenco, This document contains the minutes of
Force Benoit Pilon, Manager meeting of the inflight Task Force –
Geneva 22 March 2007. The Inflight
Catering Process Analysis and User
Requirements document has been
reviewed and requirements prioritized.
2/48
Glossary of Terms
Stakeholder Physical Location Type of product

Airline HQ N/A
Repair Facility U/S trolley repair
Warehouse Serviceable trolleys
Aircraft All
Caterer Catering Facility
Kitchen Food
Commissary Non-food, non-bonded items
Bonded Facility Bar and Duty Free items
Equipment Store Serviceable food trolleys
Duty Free Supplier Bonded Facility Duty Free items, if outsourced
Repair Supplier Repair Facility U/S trolley repair, if outsourced
Definitions:
Catering Equipment: All rotable equipment used for catering; including trolleys, carriers, ovens, coffee
makers, etc.
Trolley: Container on wheels (trolley, cart, etc.)
Carrier: Container carried by hand (carrier, stowage unit, box, etc.)
Galley: Infrastructure on board aircraft into which trolleys and carriers are inserted.
In this document, the word trolley is used to identify both trolley and carrier. However, a decision will be
made as to whether RFID technology should apply first to trolleys, and then to carriers, or to both at the
same time.
Catering Facility sites code:

AMS: Amsterdam, The Netherlands
BOD: Bordeaux, France
VIE: Vienna, Austria.
3/48
Table of contents
1. Executive Summary ............................................................................................................................ 5
2. Project Objectives & Scope................................................................................................................ 6
2.1. Project Objectives ................................................................................................................................6
2.2. Project Scope.......................................................................................................................................6
2.3. Process scope .....................................................................................................................................7
2.4. RFID tracking points along catering processes...................................................................................8
3. List of required data ............................................................................................................................ 9
3.1. Data scope...........................................................................................................................................9
3.2. Handheld Scanner Device – Screen Design .....................................................................................10
4. Trial Functional Requirements......................................................................................................... 11
4.1. Initialization & Management Requirements .......................................................................................11
4.1.1. Manage Catering Equipment Asset............................................................................................11
4.1.2. Determine Catering Equipment Requirements ..........................................................................16
4.2. Operational Requirements.................................................................................................................17
4.2.1. Ensure Daily Catering Equipment Requirements.......................................................................17
4.2.2. Build Trolleys at AMS .................................................................................................................18
4.2.3. Prepare and Load Trolleys onto Trucks .....................................................................................20
4.2.4. Receive Trolleys .........................................................................................................................21
4.2.5. Receive U/S Trolleys (at AMS only) ...........................................................................................23
4.2.6. Clean Food Trolleys ...................................................................................................................24
4.2.7. Inspect Trolleys ..........................................................................................................................25
4.2.8. Ship U/S Trolleys ........................................................................................................................26
4.2.9. Destroy non repairable Trolleys .................................................................................................27
4.2.10. Return Repaired Trolleys............................................................................................................28
5. Data Structure & Management ......................................................................................................... 30
5.1. Data Management process................................................................................................................30
5.1.1. Data description..........................................................................................................................30
5.1.2. Step 0: Receive trolleys for initialization at AMS ........................................................................31
5.1.3. Step 1: Clean Food trolleys ........................................................................................................32
5.1.4. Step 2: Inspect trolleys at AMS / FR 51 .....................................................................................33
5.1.5. Step 3: Build trolleys at AMS (for BOD) / FR 14.1......................................................................34
5.1.6. Step 4: Prepare and load trolleys onto trucks at AMS (for BOD) / FR 34.1 ...............................35
5.1.7. Step 5: Receive trolleys from AMS at BOD / FR 44 ...................................................................36
5.1.8. Step 6: Build trolleys from BOD to AMS.....................................................................................37
5.1.9. Step 7: Receive trolleys at AMS from BOD – closed loop .........................................................38
5.1.10. Step 8: Ship U/S trolleys to Maintenance Facility.......................................................................39
5.1.11. Step 9: Condemn the trolley .......................................................................................................40
5.1.12. Step 10: Return repaired trolleys to AMS...................................................................................41
5.1.13. Step 11: Cancel trolleys that have already been assigned to a flight ........................................42
6. Technical Requirements................................................................................................................... 43
7. Equipment Requirements................................................................................................................. 45
7.1. RFID equipment.................................................................................................................................45
7.2. Information System equipment ..........................................................................................................45
7.3. Tag Installation...................................................................................................................................45
8. Annex 1 – Global User Requirements – Trial Requirements Traceability Matrix ....................... 46
8.1. Traceability Matrix..............................................................................................................................46
4/48
1. Executive Summary
This document (in orange in the following picture) is the third report that is part of the IATA inflight project. It
describes in details all the requirements that will be taken into account in the Trial. It has been used as a
core document to invite and get proposals from suppliers.
With IATA, KLM Catering Services and KLM Cityhopper will conduct a trial that will be kicked off in July.
Three Caterer facilities should be used in the trial: KLM Catering Services in Amsterdam as the main facility
will be equipped with reader(s) and handheld scanners while the two other Catering facilities (in Bordeaux
and in Vienna) will be equipped with RFID handheld scanners only.
Process Description Deliverables
Identify high • Initial IATA view on the potential benefits of the use of High Level
level potential RFID in Inflight Business Case
benefits
• Description of the detailed processes and main operational

Process
Inflight Project Process Description
Identify issues encountered issues

• Identification and prioritization of the stakeholder needs for Analysis and
and define
an RFID solution applied to inflight, peer reviewed by the User
needs
inflight task force. Requirements
• The elements of the user requirements to be tested in the

Describe and trial, along with which party will provide what element of Trial
set up a trial the trial. Requirements
Select • The technology to be carried forward to trial based upon Technology

Technology tests and peer opinion for the use of RFID Report
• The results of the trial applied to the inflight processes as

Evaluate with well as technology performance results. Mainly focused on Trial Results
trials trolleys management and maintenance with some Report
technology tests for trolley contents.
Detail cost & • A report on the detailed business case for RFID on
catering trolleys, supported by realistic costs from the Detail Business
benefits
industry and returns on investment from airlines. Case
analysis
Develop a • A new Recommended Practice to be included in future Recommended

Recommend JPSC manuals Practice
Practice
5/48
2. Project Objectives & Scope
2.1. Project Objectives
IATA leads the Airline industry to Simplify the Business by moving forward and facilitating the
implementation of five key projects (e-ticket, BCBP, CUSS, RFID and e-freight). Delivering these projects is
of paramount importance to the industry.
As part of IATA's Simplifying the Business programme, IATA is leading RFID for the aviation industry in
baggage, inflight, turnaround, cargo and management of parts.
IATA launched in January 2007 inflight activities to identify the appropriate technologies to maximise the
business benefit of auto-id in the inflight space and analyse in detail what RFID could bring to Airlines and
Caterers in the management of trolleys and stowage units, their maintenance, and the management of
contents.
IATA is now launching with KLM Cityhopper and KLM Catering Services the RFID Trial. The main objectives
of this trial will be to:
Validate the technology performance (read rate, reading range, thermic shock resistance, etc.)
and identify potential issues
Analyse business performance (inventory, trolley location per facility and level of stock, number of
trolley cycles, turnaround time) and defined the needs.
The results will be used to develop the detailed business case.
2.2. Project Scope

Involved Stakeholders
With IATA, KLM Catering Services and KLM Cityhopper will conduct a trial that will be kicked off in July.
Three Caterer facilities should be used in the trial: KLM Catering Services in Amsterdam as the main facility
will be equipped with reader(s) and handheld scanners while the two other Catering facilities (in Bordeaux
and in Vienna) will be equipped with RFID handheld scanners only.
The RFID suppliers are contacted to obtain their support in identifying RFID solution as well as providing
and installing RFID equipment.
The IT suppliers are contacted to get their support in developing a basic reporting interface system to gather
and record data in a database for further analysis.
IATA invites suppliers to form partnerships in order to deliver an optimum solution.
IATA will promote the trial and their preferred partners at a worldwide level. The results will be
communicated to Airlines at CEO level and IATA will communicate broadly on conferences and other
special events, subject to the agreement of the parties involved. All communication as a result of the trial
must be supplied to IATA for approval.
Equipment shall be returned to suppliers at the end of the trial, in as near to supplied condition as possible
subject to wear and tear.
6/48
RFID Technology
The recommended RFID technologies for the Trial are the LF, HF and UHF passive RFID technology
solutions. IATA will conduct off-site technology tests to ensure compliance with basic requirements such as
reading through a wide doorway and ease of handheld use (no bending, stretching needed). The final
technologies will then be progressed for trial.
Trolleys to be equipped
KLM Cityhopper owns around 1,200 trolleys that shall be equipped with an encapsulated RFID tag.
It will also include a test to read trolley contents to get experience about reading performance.
Timing
The trial should last 2 months, starting when all trolleys are equipped with RFID tags.
2.3. Process scope

In Blue: covered or partly covered by the Trial
In Red: not covered
Operate Inflight Service Activities
Pre-flight In-flight Post-flight
Move Clean Food Store

Ensure Daily Build Trolleys Load Deliver
Trolleys Operate Trolleys Food
Catering Trolleys Trolleys Offload Receive Inspect Trolleys
Re-build Return Duty to on Ship Duty
Equipment onto to Trolleys Trolleys Trolleys
Duty Free Free Trolleys Staging Board Free Trolleys
Requirements Trucks Aircraft
Trolleys to Caterer Area to Duty Free
Manage and Track
Measure, Analyse and Improve
Maintain
Maintain Catering
Catering Equipment
Equipment
Define the
Maintain & Repair Manage &
Maintenance & Repair
Catering Equipment Track
Programme
Define the • Repair U/S Trolleys Returned Measure,
Ship U/S
Maintenance & • Destroy non repairable Repaired Analyse
Trolleys
Repair Programme Trolleys Trolleys and Improve
Important remark: as the trolleys will not be scanned after they have been washed we will only get
serviceable trolleys as being in the Catering Facility and not the exact number of ‘’serviceable and washed’’
trolleys for the trial.
7/48
2.4. RFID tracking points along catering processes
Process ID Tracking Points
ID ID
ID Move ID ID Clean ID ID Store
Trolleys Operate Food Trolleys Food
Maintain
Maintain Catering
Catering Equipment
Equipment
Define the
Programme
Define the
ID • Repair U/S Trolleys
ID Returned Measure,
Ship U/S
Trolleys
ID RFID fixed antenna reading in Schiphol KCS Facility
ID RFID handheld - manual reading in Schiphol KCS Facility and Schiphol Repair Facility
ID RFID handheld - manual reading outstation
Remark:
As KLM City Hopper does not have Duty Free trolleys, the reader shall keep in mind that in Chapter 4
whatever it is specified for the Trolley Content Type (‘’ALL’’ or ‘’Except DF’’) it means in this trial project the
same. For another airline who owns Duty Free trolleys, it shall be checked in details (out of scope here).
8/48
3. List of required data
3.1. Data scope
In Green: data on tag
In orange: data in system. Data on tag are in system too.
•• Unique
Unique Trolley
Trolley IDentifier
IDentifier UTID
UTID that
that
incorporates:
incorporates:
Trolley
Trolley
-- Trolley
Trolley Operator
Operator
-- Owner
Owner Part
Part Number
Number
Identification
Identification -- Manufacturer
Manufacturer Serial
Serial Number
Number
•• Trolley
Trolley Owner
Owner
•• Trolley
Trolley Type
Type
(KSSU,
(KSSU, ATLAS,
ATLAS, other)
other)
•• Trolley
Trolley Usage
Usage
-- Food
Food
Trolley
Trolley -- Non
Non Food
Food
Beverages
Beverages
Information
Information Dry
Dry stores
stores
•• Trolley
Trolley Size
Size
-- Full
Full size
size
-- Half
Half size
size
Operational
Operational Status
Status Location
Location Status
Status
•• Serviceable
Serviceable •• Catering
Catering
Trolley
Trolley -- Assigned
Assigned to to flight
flight number
number // date
date -- Kitchen:
Kitchen:
-- Not
Not assigned
assigned to to flight
flight number
number // date AMS
AMS
Status
Status •• Unserviceable
date AND BOD
BOD
Date / Time recorded Unserviceable (U/S) (U/S)
Date / Time recorded -- identified VIE
VIE
each time there is a identified U/S
U/S on-board
on-board first
first
each time there is a -- identified •• Maintenance
Maintenance
status change identified U/S
U/S on-ground
on-ground only
only
status change •• Condemned
Condemned
•• Washed
Washed // NotNot washed
washed
Data definition:
Unique Trolley Identifier - UTID: a way to uniquely identify a trolley
Trolley Usage: note that sometimes for example a duty free trolley will be used for food if short
food trolleys. However it is not planned to change the trolley usage during the trial.
Owner Part number = a trolley type + trolley size + a usage + an owner
Trolley Operational Status - Tree Analysis Description
Not
Notassigned
assigned
Serviceable
Serviceable Not
Notready
ready
Assigned
Assigned
Ready
Ready
Remark: The status ‘’Not ready’’ and ‘’Ready’’ is not supported by the trial.
9/48
3.2. Handheld Scanner Device – Screen Design
To support functionalities to be developed in the handheld scanner, each functionality and required data are
described in using the following screen design:
<< - >> FUNCTION MENU

Trolley ID: KLC PS2804 KC0102A93 Trolley
Trolley UTID
UTID read
read by
by the
the handheld
handheld reader
reader
01 - Record Entering Catering Facility List
List of
of available
available functionalities
functionalities
02 - 01 -
03 - 02 -
04 -
03 -
05 -
04 -
06 -
…-
07 -
…-
A B C D E F G H
I J K L M N O P
Q R S T U V W X
Y Z
7 8 9
Del
4 5 6
1 2 3
0 Space
10/48
4. Trial Functional Requirements
4.1. Initialization & Management Requirements
4.1.1. Manage Catering Equipment Asset
Trolley
Description Content
Type
Process Manage Catering Equipment Asset
UR 01 Identify each trolley as a unique asset ALL
For each trolley entering through the door equipped with the fixed RFID
reader, trigger a BIP alarm when the trolley is equipped with an RFID
FR 01.1 ALL
encapsulated tag. This will tell which trolleys have not yet been equipped
with an RFID encapsulated tag.
Encode tag with a unique trolley identifier UTID that will enable to identify each
trolley with:
Trolley operator (KLC by default)
FR 01.2 ALL
Owner Part number (Trolley type + Trolley size + Trolley usage + Trolley
owner). The Trolley owner is KLC
Serial number
FR 01.3 Complete data trolley set up process by loading manually data in system ALL
Stakeholder Role
Airline
To install and write on tag the UTID (Select the functionality 00, select 01.1 and load
Owner Part Number, select 01.2 and load Manufacturer Serial Number, validate) for
Caterer all the trolleys. Default operator will be KLC.
To load trolley information into the system (FR 01.3)
To start the trolley tracking
To be present during the first days of the preparation process (installation, test tag
IATA
and system information readiness)
To supply encapsulated tags
To test tag position and readiness on trolley (on some trolleys)
RFID Supplier
To validate tag position
To train the caterer on how to install and encode tags and how to do test readiness
To develop and test FR01.1
IT Supplier To design, develop and test interface & functionality to download handheld data (FR
01.2 and FR 01.3) in the database file
Handheld Scanner - Functionality Description Approach
11/48
Trolley
Description Content
Type

Trolley ID: 000 000000 000000000
Record
Record the
the following
following data:
data:
00 - Initialize and encode trolley tag •• UTID
UTID
01.1 - Enter Owner Part Number •• Date
Date and
and Time
Time
01.2 - Enter Serial Number •• Location
Location
03 -
Proposal
Proposal for
for functionality
functionality coding:
coding:
04 - •• The
The trolley
trolley Operator
Operator isis set
set by
by default
default
05 - to
to KLC
KLC toto save
save time
time in
in the
the manual
manual
06 - process
process
07 -
In
In system
system
A B C D E F G H •• See
See Data
Data Management
Management Process
Process
I J K L M N O P chapter
chapter for
for details
details
Q R S T U V W X
Y Z
7 8 9
Del
4 5 6
1 2 3
0 Space
Decision to be made
FR 01.3 functionality: to be discussed between the IT supplier and the Caterer
Operating Mode & Rule
The ‘’Serviceable’’ operational status is set by default, at the first identification (when tagging trolley for
the first time)
The ‘’Not assigned to a flight number/date’’ status linked to ‘’Serviceable’’ is set by default, at the first
identification (when tagging trolley for the first time).
12/48
Trolley
Description
Content Type
Record chronological trolley data / information (date, time, location status,
UR 02 ALL
operational status)
Record in the system (see 4.2.1 for data detailed list) for each trolley
each change of status (operational / location) and timestamp:
Operational status:
Serviceable
o Not assigned to a flight number/date
o Assigned to a flight number/date
FR 02 Unserviceable (identified on board / on ground) ALL
Condemned
Location status:
AMS or BOD or VIE catering facility (entering / leaving)
Maintenance Facility (leaving to / entering from)
Time stamp
Stakeholder Role
Airline
Manual updating - using a handheld scanner - of the following operational status
events, including location, date and time:
Assigned to a flight (see FR 14.1)
Unserviceable (see FR 04)
Caterer
Condemned (when declared as so, after maintenance feedback),
Serviceable (when change from Unserviceable to Serviceable only. See FR 48)
o Not assigned to a flight number/date
o Assigned to a flight number/date
IATA
To track data, the supplier shall provide (see details in chapter 7):
RFID Supplier Fixed readers and handheld scanners at AMS
VIE and BOD: handheld scanners only
To provide and test functionalities and system to download:
Automatically location status (via fixed reader: AMS)
Semi-automatically location status via handheld scanners
IT Supplier
Software on handheld scanner
Manually operational status
Date and time
Decision to be made
Live system accessible at all 3 locations or downloads?
See also FR 04, FR 14.1 and FR 48
13/48
Trolley
Description
Content Type
UR 03 Use chronological trolley data / information ALL
All data will be chronologically saved (at least on a daily basis) in a file
FR 03 that can be downloaded in a database system for post processing ALL
analysis (MS-Access for instance)
Stakeholder Role
Airline
Caterer
IATA
RFID Supplier
To design and test the recording of the data in a way that it can easily be possible to
analyse data
IT Supplier
To develop a basic solution to access data from VIE and BOD and to download them
to get a global and consolidated database at AMS.
Decision to be made
The IT supplier shall propose with KCS an easy and simple solution to import data from handheld
scanners into the system for the 3 catering facilities. This includes a simple and not costly solution to
import data from BOD and VIE to AMS Catering Facility for daily data consolidation purpose.
14/48
Trolley
Description
Content Type
Use U/S trolley status information (date, location, type of damages,
UR 04 ALL
frequencies)
Access in the system for each trolley identified as Unserviceable, date
FR 04 and time and whether it has first been identified on-board or at Catering ALL
Facility
The total number of unserviceable trolleys per day (volume update) is
Remark: ALL
covered by FR 11
Stakeholder Role
Airline To be able to access and analyse data (via KLM Catering Services)
Scan U/S trolley to update trolley status
Caterer
To be able to access and analyse data
IATA To be able to access and analyse data (via KLM Catering Services)
RFID Supplier
To provide and test functionalities to record the U/S data (see details in FR 51 and FR
IT Supplier
52) in system.
Approach
The approach that KLM Cityhopper and KLM Catering Services would like to be adopted:
Use a specific label with an inserted RFID chip that will be used to mark U/S trolley on-board the
aircraft
When a U/S trolley enters the AMS Catering Facility through the door equipped with an RFID
fixed reader, trigger an alarm to inform the Caterer staff.
The alarm shall be different from the one used to identify whether the trolley is already equipped
with an RFID tag or not.

Each time a trolley is declared as unserviceable, the Caterer, during the trolley inspection process, shall
scan the trolley with the handheld scanner and shall record in system the following information for the
identified trolley: Unserviceable, location, date, time, first identified as U/S (either on-board or during
ground inspection at Caterer Facility).
15/48
Trolley
Description
Content Type
UR 08 Analyse Trolley cycle ALL
Calculate the number of cycles each serviceable trolley goes through,
FR 08 i.e. how many times “out” of a catering facility (at AMS, BOD and VIE) ALL
assuming it is for a flight.
Stakeholder Role
Airline
Caterer
IATA
RFID Supplier
IT Supplier To provide and test the ‘’trolley - number of cycles’’ functionality
Decision to be made

This functionality will be used once at the end of the trial
4.1.2. Determine Catering Equipment Requirements

Trolley
Description
Content Type
Process Determine Catering Equipment Requirements
Find out how many trolleys are located in each location and by
operational status
UR 11 ALL
Remark: this can be done at any time along the process (planning & real-
time operational activities), by operator, by type of trolley, by size, by
usage, by part number
Calculate the number of trolleys by airline (KLC by default), per part
number, per catering facility (stock):
Number of trolleys entering in Catering Facility
FR 11 Number of trolleys going out the Catering Facility ALL
Stock level: Number of serviceable and not assigned trolleys in
(with operational status) Catering Facility
Number of U/S trolleys (AMS only)
Stakeholder Role
Airline
Caterer Perform stock level check with handheld scanner to prevent drift
IATA
RFID Supplier
To provide the functionality and test the functionality
IT Supplier
The functionality can be run at any time
Decision to be made
16/48
4.2. Operational Requirements

Return Duty to on
Equipment Re-build onto to Trolleys Trolleys Ship Duty Trolleys
4.2.1. Ensure Daily Catering Equipment Requirements

Trolley
Description
Content Type
Process Ensure Daily Catering Equipment Requirements
Trolley flow expectation arriving/leaving Catering Facility (weekly & daily
UR 12 ALL
basis) per airline, type, size, usage, and part number
Provide a daily flight provisioning plan showing how many trolleys are
required:
FR 12.1 ALL
For each flight number / date / scheduled departure (time)
For each Trolley part number
Calculate number of available trolleys (serviceable and not assigned)
FR 12.2 per part number and per Catering Facility at D day (at AMS, BOD and ALL
VIE)
Provide difference between next day’s flight demand and trolley
FR 12.3 availability at each Catering Facility at (D+1) day (at AMS, BOD and ALL
VIE)
Report when amount of trolleys below a specific threshold (value to
be defined). The threshold shall be easily changed to another value.
FR 12.4 ALL
Remark: the functionality shall be run manually once a day and not to
be automated to limit S/W development
Stakeholder Role
Airline
To provide the daily flight provisioning plan in electronic form (file) and in a specific
Caterer format (to be defined) to allow easy connection/merging with trolley tracking data
To run F12.4 based on F12.3
IATA
RFID Supplier
Check daily flight provisioning plan file compatibility with designed structure data
IT Supplier Develop and test the trolley availability check functionality
Develop and test basic interface, if required
Decision to be made
Format and contents of the flight provisioning plan file
17/48
4.2.2. Build Trolleys at AMS
Return Duty to on
Trolley
Description
Content Type
Process Build Trolleys at AMS
Assign trolley from proper airline to a specific flight number / date in the
UR 14 Except DF
system and timestamp
Assign trolley from proper airline (KLM Cityhopper per default) to a
FR 14.1 Except DF
specific flight number / date and timestamp, and load in the system
FR 14.2 Update Trolley stock at each Catering Facility, per part number Except DF
FR 14.3 Obtain per flight number the number of assigned trolleys Except DF
FR 14.4 Obtain the number of flights per day Except DF
FR 14.5 Obtain the total number of assigned trolleys for all flights Except DF
Stakeholder Role
Airline
Assign each serviceable trolley to a specific flight number via the usual procedure and
Caterer
additionally scan the trolley and load data in the system
IATA
Test readiness of the data tag (for a few trolleys).
RFID Supplier Remark: the test of readiness of the data tag can also be supported by the IT supplier
(to be validated)
IT Supplier To provide and test the functionalities

Trolley ID: KLC PS2804 KC0102A93
01 - Record
Record the
the following
following data:
data:
02 - Assign Trolley to a flight number •• UTID
UTID
03 - •• Date
Date and
and Time
Time
04 - •• Flight
Flight number
number
•• Flight
Flight number
number Date
Date
05 -
•• Location
Location
06 -
07 - In
In system
system
See
See Data
Data Management
Management Process
Process chapter
chapter
A B C D E F G H for
for details
details
I J K L M N O P
Q R S T U V W X
Y Z
7 8 9
Del
4 5 6
1 2 3
0 Space
Decision made
18/48
Trolley
Description
Content Type
This activity is only recorded from AMS. To reduce workload for BOD and VIE, staff will only scan
trolleys entering and leaving their facility.
When a trolley is scanned, the location where it is scanned shall be recorded automatically
Trolley
Description
Content Type
Process Build Trolleys at AMS
Assign contents to a trolley (already assigned to a flight number/date) by
UR 16 Except DF
item and quantity in the system and confirm against airline specifications
FR 16 As a test ONLY Except DF
Stakeholder Role
Airline
Tag some items (bar items, meals)
Caterer
Test readiness of all the tags in a trolley
IATA
Provide retail-type tags
RFID Supplier
Help the Caterer to measure performance of the test
IT Supplier
Decision to be made
This requirement will be tested a few times and in Amsterdam KCS Facility only.
There is no need to develop functionality.
none
19/48
4.2.3. Prepare and Load Trolleys onto Trucks
Re-build Return Duty to on
Equipment onto to Trolleys Trolleys Ship Duty Trolleys
Trolley
Description
Content Type
Process Prepare and Load Trolleys onto Trucks
Identify trolleys leaving Catering Facility and timestamp to stop catering
UR 34 ALL
cycle
Identify automatically trolleys leaving AMS Catering Facility and
FR 34.1 ALL
timestamp to stop catering cycle
Identify manually trolleys leaving BOD and VIE Catering Facilities and
FR 34.2 ALL
timestamp to stop catering cycle for each Catering Facility.
Calculate the turnaround time each serviceable trolley goes through at
FR 34.3 ALL
each catering facility (subtraction of ‘’out – in’’ of a catering facility).
Stakeholder Role
Airline
To scan trolleys leaving Catering Facility and timestamp to stop catering cycle. This is
Caterer
done in AMS, BOD and VIE.
IATA
RFID Supplier
To provide and test the FR 34.1 functionality
IT Supplier
To provide and test the FR 34.2 turnaround time functionality

01 - Record
Record the
the following
following data:
data:
02 - •• UTID
UTID
03 - Record Leaving Catering Facility •• Date
Date and
and Time
Time
04 - •• Location
Location
05 -
In
In system
system
06 - See
See Data
Data Management
Management Process
Process chapter
chapter
07 - for
for details
details
A B C D E F G H
I J K L M N O P
Q R S T U V W X
Y Z
7 8 9
Del
4 5 6
1 2 3
0 Space
Decision to be made
20/48
Trolley
Description
Content Type
The Turnaround time is covered with trolley data updated by FR 34 and FR 44
4.2.4. Receive Trolleys

Trolley
Description
Content Type
Process Receive Trolleys
Identify trolleys entering the Catering Facility and timestamp to begin
UR 44 ALL
catering cycle
Identify all the trolleys entering the Catering Facility and timestamp to
FR 44 ALL
begin catering cycle
Stakeholder Role
Airline
Identify automatically (at AMS). If necessary, can also be identified manually at AMS
by using a handheld scanner
Caterer
Identify manually (by scanning at BOD and VIE) trolleys entering the Catering Facility
and timestamp to begin catering cycle.
IATA
RFID Supplier
IT Supplier To provide and test data loading functionality

Record
Record the
the following
following data:
data:
01 - Record Entering Catering Facility •• UTID
UTID
02 - •• Date
Date and
and Time
Time
Location
04 -
In
In system
system
05 - See
See Data
Data Management
Management Process
Process chapter
chapter
06 - for
for details
details
07 -
A B C D E F G H
I J K L M N O P
Q R S T U V W X
Y Z
7 8 9
Del
4 5 6
1 2 3
0 Space
Decision to be made
21/48
Trolley
Description
Content Type

22/48
4.2.5. Receive U/S Trolleys (at AMS only)
Trolley
Description
Content Type
Process Receive U/S Trolleys (at AMS only)
See also ‘’Inspect Trolleys’’ process for a full functionality development ALL
When a U/S trolley (with the specific RFID tag label used as an U/S
tag) enters the AMS Catering Facility through the door equipped with
the RFID fixed reader, it shall trigger an alarm to inform the Caterer
FR 51.1 staff. ALL
The alarm shall be different from the one used to identify whether the
trolley is already equipped with an RFID tag or not.
Stakeholder Role
To train / inform cabin crew with the U/S label tagging procedure and aim
Airline
Cabin Crew: to mark the U/S trolleys on-board the aircraft
Caterer Move U/S trolleys to scan them (described in next process ‘’Inspect Trolleys’’)
IATA
Provide a specific label with an inserted RFID chip that will be used to mark U/S
RFID Supplier
trolley on-board the aircraft
Develop and test the functionality that detects U/S trolley and test alarm trigger
IT Supplier
functionality too.
Approach
The approach that KLM Cityhopper and KLM Catering Services would like to be adopted:
Use a specific label with an inserted RFID chip that will be used to mark U/S trolley on-board the
aircraft
When a U/S trolley enters the AMS Catering Facility through the door equipped with an RFID fixed
reader, trigger an alarm to inform the Caterer staff.
23/48
4.2.6. Clean Food Trolleys
Trolley
Description
Content Type
Process Clean Food Trolleys
Identify automatically all the trolleys being washed at the AMS Catering
FR 110 Except DF
Facility and timestamp
Calculate time elapsed between received trolleys (at the AMS Catering
FR 111 Except DF
Facility) and washed trolleys
Stakeholder Role
Airline
Caterer
IATA
RFID Supplier
IT Supplier To provide and test data loading functionality
Decision to be made

24/48
4.2.7. Inspect Trolleys
Trolley
Description
Content Type
Process Inspect Trolleys (at AMS only)
UR 51 Declare trolleys as U/S ALL
For each trolley identified as Unserviceable either on-board or during the
ground inspection, record in system the following data:
FR 51.2 ALL
Unserviceable status, date and time, and whether it has been
identified first on-board or at Catering Facility.
Stakeholder Role
Airline
To scan U/S trolley to update trolley status
Caterer
To record U/S data using a handheld scanner and download data in the system
IATA
RFID Supplier
To provide handheld scanner software capable of recording the required data and
IT Supplier downloading data in system
Test the software and the downloading functionality

01 -
Record
Record the
the following
following data:
data:
02 -
•• UTID
UTID
03 - •• Date
Date and
and Time
Time
04 - Declare U/S Entering Catering Facility •• Location
Location
04.1 - U/S Taq on the Trolley •• And
And whether
whether thethe trolley
trolley has
has been
been identified
identified
04.2 - No U/S Tag on the Trolley as
as Unserviceable
Unserviceable first first on-board
on-board by by the
the
cabin
cabin crew
crew oror at
at Catering
Catering Facility
Facility like:
like:
07 - •• 04.1
04.1 == first
first identified
identified onon board
board as as aa
U/S
U/S tag
tag isis on
on the
the trolley
trolley (selected
(selected
A B C D E F G H case
case like
like in
in this
this example)
example)
•• 04.2
04.2 == no
no U/S
U/S tagtag and
and Trolley
Trolley
I J K L M N O P
declared
declared as as Unserviceable
Unserviceable by by thethe
Q R S T U V W X Caterer
Caterer during
during the the inspection
inspection activity
activity
Y Z
In
In system
system
7 8 9 See
See Data
Data Management
Management Process
Process chapter
chapter for
for
Del
4 5 6 details
details
1 2 3
0 Space

Each time a trolley is declared as unserviceable, the Caterer, during the trolley inspection process, shall
scan the trolley with the handheld scanner and shall record in system the following information for the
identified trolley: Unserviceable, location, date, time, first identified as U/S (either on-board or during
ground inspection at Caterer Facility).
25/48
4.2.8. Ship U/S Trolleys
Maintain
Maintain Catering
Catering Equipment
Equipment
Define the
Programme
Define the • Repair U/S Trolleys Return Measure,
Ship U/S
Trolleys
Trolley
Description
Content Type
Process Ship U/S Trolleys to Repair Facility
Identify U/S trolleys leaving the Catering Facility for Repair Facility and
UR 52 ALL
timestamp to start repair cycle
FR 52 Record Trolley UTID, operational and location status. ALL
Stakeholder Role
Airline
To scan the trolleys with a handheld scanner (true for any trolley leaving the facility
Caterer
without going through outbound docks)
IATA
RFID Supplier
To provide downloading functionality
IT Supplier
Test functionality

01 -
02 -
03 -
04 -
Record
Record the
the following
following data:
data:
05 - Record U/S being sent to Maintenance
•• UTID
UTID
06 - •• Date
Date and
and Time
Time
Location
A B C D E F G H In
In system
system
See
See Data
Data Management
Management Process
Process chapter
chapter
I J K L M N O P for
for details
details
Q R S T U V W X
Y Z
7 8 9
Del
4 5 6
1 2 3
0 Space

26/48
4.2.9. Destroy non repairable Trolleys
Maintain
Maintain Catering
Catering Equipment
Equipment
Define the
Programme
Ship U/S
Trolleys
Trolley
Description
Content Type
Process Destroy non repairable trolleys
ALL
When the trolley is not repairable: to update the trolley status in the
FR 100 ALL
database file
Stakeholder Role
Airline
Update manually the database file in changing the trolley status from unserviceable to
Caterer
condemned
IATA
RFID Supplier
IT Supplier To provide functionality and test functionality.
Decision to be made
The development of this functionality shall be discussed between the Caterer and the IT Supplier as it
can be updated manually in accessing the database file and should happen few times only
The Caterer shall be informed by the Maintenance that the trolley is not repairable, and shall get the
UTID (The Trolley Serial number should be enough. To be checked by the Caterer)
27/48
4.2.10. Return Repaired Trolleys
Maintain
Maintain Catering
Catering Equipment
Equipment
Define the
Programme
Ship U/S
Trolleys
Trolley
Description
Content Type
Process Receive Trolleys
UR 48 Identify repaired trolleys entering the Catering Facility ALL
For each returned repaired trolley (coming from the Maintenance
Facility), record its return date/time and location in the system and
FR 48.1 change its status from Unserviceable to Serviceable. ALL
Again each time a trolley is set to Serviceable, it shall automatically be
set by default to ‘’Not assigned to a flight number/date’’.
Calculate the repaired turnaround time for each repaired trolley
FR 48.2 ALL
(substitution of ‘’out-in’’, between FR48.1 and FR 52
Calculate the number of U/S trolleys identified daily at AMS Catering
FR 48.3 ALL
Facility
Calculate for each trolley how many times it has been sent to the Repair
FR 48.4 ALL
Facility
Stakeholder Role
Airline
Caterer Perform the task
IATA
RFID Supplier
IT Supplier Provide and test functionalities (FR 48.1 and FR 48.2)
28/48
Trolley
Description
Content Type

01 -
02 -
03 -
04 -
Record
Record the
the following
following data:
data:
05 -
•• UTID
UTID
06 - Record Repaired Trolley Entering CF •• Date
Date and
and Time
Time
Location
A B C D E F G H In
In system
system
See
See Data
Data Management
Management Process
Process chapter
chapter
I J K L M N O P for
for details
details
Q R S T U V W X
Y Z
7 8 9
Del
4 5 6
1 2 3
0 Space
Decision to be made

29/48
5. Data Structure & Management
5.1. Data Management process
5.1.1. Data description
Data shall be saved in a file that can be downloadable in MS-Access.
The trolley tracking is detailed step by step along the main process called ‘’Operate inflight Service
activities’’ as well as the ‘’Maintain Catering Equipment’’ process.
The main process closed loop presented here is based on flights between AMS and BOD, AMS and
Maintenance, AMS and other destination than BOD or VIE. The principle remains the same for VIE, except
a change in a code, set to 3 for VIE (see below for explanation).
The first data called ‘’#’’ is optional and shall be discussed/validated by KLC and the IT supplier. The idea is
to use this data for specific analysis on one trolley for instance, instead of using the long UTID data.
Description
# (optional and only for the trial) …= a unique number
UTID …= a UTID
Trolley Operational Airline …= KLC
Owner Part Number …= a Part number
Manufacturer Serial Number …= a Serial number
Trolley Owner …= KLC
Trolley Type …= a trolley type
Trolley Usage …= a Trolley usage
Date …= a date
Time …= a time
None
AMS
Catering Facility
BDX
VIE
Out (= condemned trolley)
Entering / Leaving Catering Facility Entering
Leaving
Condemned
Serviceable / Unserviceable / Condemned Serviceable
Unserviceable
Washed
Washed / Not washed
Not Washed
Assigned
Assigned to a flight / Not Assigned to a flight
Not Assigned
No flight number
Flight number
…= a Flight number
No flight number
Flight number date
…= a Flight number
Not a U/S trolley
Leaving to / Returned from Maintenance Leaving to Maintenance
Returned from Maintenance
Not a U/S trolley
Identified on board / on ground Identified on board
Identified on ground
30/48
5.1.2. Step 0: Receive trolleys for initialization at AMS
Installation of the tags, and initialization of data on tags and data in system. The initialization is done with the
handheld scanner and saved in system.
IN
INSYSTEM
SYSTEM In File / Database
# …
UTID …
Trolley Operational Airline …
Owner Part Number …
Manufacturer Serial Number …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Catering Facility AMS
Cleaning status (Not washed / washed) Not washed
Assigned to a flight / Not Assigned to a flight Not Assigned to a flight
Flight number None
Flight number date None
Leaving to / Returned from Maintenance None
Identified on board / on ground None
31/48
5.1.3. Step 1: Clean Food trolleys
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Cleaning status (Not washed / washed) Washed
Flight number None
32/48
5.1.4. Step 2: Inspect trolleys at AMS / FR 51
Case 1: The trolley remains ‘’Serviceable’’

No specific recording task is required. The activity could be tracked and recorded in system but it does not
seem to have a real added value at that stage, and it would require more work for staff.
When a trolley is declared as not serviceable, the information is recorded and tracked in the system (see
Case 2).
Case 2: The trolley is set to ‘’Unserviceable’’ (U/S)

This task is done with the handheld scanner (and the system).
Unserviceable
Identified on board / on ground
For the following step, go to step 7.
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Serviceable / Unserviceable / Condemned Unserviceable
Flight number None
33/48
5.1.5. Step 3: Build trolleys at AMS (for BOD) / FR 14.1
Return Duty to on
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Assigned to a flight / Not Assigned to a flight Assigned to a flight
Flight number …
Flight number date …
34/48
5.1.6. Step 4: Prepare and load trolleys onto trucks at AMS (for BOD) / FR 34.1
The trolleys are scanned by a handheld reader just before being loaded in the truck.
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Entering / Leaving Catering Facility Leaving
Flight number …
Leaving to / Returned from Maintenance …
35/48
5.1.7. Step 5: Receive trolleys from AMS at BOD / FR 44
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Catering Facility BOD
Cleaning status (Not washed / washed) Washed*
Flight number None
36/48
5.1.8. Step 6: Build trolleys from BOD to AMS
To reduce additional work for BOD and VIE Catering Facility Staff, the Caterer will not assign trolleys to a
flight and will only scan trolleys leaving the Catering Facility.
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Catering Facility BOD
Cleaning status (Not washed / washed) Washed*
Flight number …
37/48
5.1.9. Step 7: Receive trolleys at AMS from BOD – closed loop
This task is done with the fixed reader (and the system).
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Cleaning status (Not washed / washed) Not washed
Flight number None
38/48
5.1.10. Step 8: Ship U/S trolleys to Maintenance Facility
Maintain
Maintain Catering
Catering Equipment
Equipment
Define the
Programme
Ship U/S
Trolleys
The U/S trolleys will leave the AMS KCS Catering Facility by a different door than the one which is equipped
with the fixed RFID reader. This will allow simple tracking and recording system by using the handheld
scanner.
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Serviceable / Unserviceable / Condemned Unserviceable
Flight number None
Leaving to / Returned from Maintenance Leaving to Maintenance
39/48
5.1.11. Step 9: Condemn the trolley
Maintain
Maintain Catering
Catering Equipment
Equipment
Define the
Programme
Ship U/S
Trolleys
The trolley is not reparable and shall be destroyed: Update the Database file manually.
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Catering Facility None
Entering / Leaving Catering Facility Out
Serviceable / Unserviceable / Condemned Condemned
Flight number None
40/48
5.1.12. Step 10: Return repaired trolleys to AMS
Maintain
Maintain Catering
Catering Equipment
Equipment
Define the
Programme
Ship U/S
Trolleys
The returned repaired trolleys to the AMS KCS Catering Facility will enter by a different door than the one
which is equipped with the fixed RFID reader. This will allow simple tracking and recording system by using
the handheld scanner.
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Flight number None
Leaving to / Returned from Maintenance Returned from Maintenance
41/48
5.1.13. Step 11: Cancel trolleys that have already been assigned to a flight
Case 1: An aircraft initially scheduled and assigned to a flight number can be cancelled. This is mainly due
to technical or weather constraints.
The aircraft is replaced by another one, and sometimes by a different type of aircraft. This might impact the
type of required trolleys to be loaded. It such a case it is necessary to cancel the assigned trolleys and
replace them by the adequate type of trolleys.
Case 2: a trolley is broken before being loaded. It needs to be cancelled and replaced by another trolley.
Change Trolley status back to:

‘’Not assigned to a flight’’
Flight number to ‘’None’’
Flight number date to ‘’None’’
For Case 2, add the U/S procedure step (see ‘’step 1: Inspect trolleys at AMS / FR 51’’ chapter).
IN
INSYSTEM
# …
UTID …
Trolley Owner KLC
Trolley Type …
Trolley Usage …
Trolley Size …
Date …
Time …
Flight number None
42/48
6. Technical Requirements
The technical potential solution(s) shall take into account existing constraints.
Durability Climate conditions

From dock to cleaning Thermic shock from –40 to 110 degree Celsius
At Outdoor conditions -40 to +45 degree Celsius
0 to 100% humidity
Sun, rain, snow, dust
At Cleaning area Water / Vapour
Chemicals
At Drying area Airflow
Heat
On board Aircraft Cabin Pressure cycle
Reading Capacity
At Docks Be robust to anti-collision: high volume of trolleys to identify, with
multiple items in each trolley
Mounted to protect tags on trolleys as they are banged around, tipped
over and so forth
Reading Interferences
At Docks Be capable of metal mounting
Be robust to interference and not cause interference to others (lots of
radio frequencies such as Walky talkies, other RF technology in use)
Be robust to anti-collision between readers
Be able to read trolley while moving
Read Range In Locations
Read distance long enough to be read across each dock door
Safety / Security Placement of Reader to prevent damage
In floor, or
Above doors
Safety Radio Frequency Band
Power emitted by reader should comply with local health and safety
legislation
Standard Common platform
Worldwide Standard or Recommended Practice is required
Certification On board Aircraft
Certification for any equipment boarded on aircraft to be obtained
Regulations Radio Frequency Band
Radio frequencies shall be in line with regulation requirements
Other Constraints
Liquid spills Tags shall withstand conditions that are hot, cold, sticky
Security Data Access
Segregation of data by user
Secure read/write capability for RFID Tag – authorised write
Time to respond Wake – Sleep / Read cycle
Tag shall wake, respond within 0.5 second
43/48
Life of Tag
Tags shall be capable of use for a period of a least 7 years without
maintenance
44/48
7. Equipment Requirements
7.1. RFID equipment
2500 tags (encapsulated tags required) for trolley tracking management
300 specific labels with an inserted RFID chip to mark U/S trolley on-board the aircraft
200 retailed type tags for content management
1 Fixed RFID reader (at KLM Catering Services – Amsterdam Facility) at an entering door, and on
the floor.
1 Fixed RFID reader (at KLM Catering Services – Amsterdam Facility) at an exit door, and on the
floor.
1 Fixed RFID reader (at KLM Catering Services – Amsterdam Facility) after trolley cleaning
activity, and on the floor.
4 handheld scanners for AMS Catering Facility (U/S tagging, leaving door, initializing process,
another door)
2 handheld scanners for BOD Catering Facility
2 handheld scanners for VIE Catering Facility
7.2. Information System equipment

4 laptops (1 per Catering Facility and one spare in AMS) (and close to the reader? Theft risk??)
Data Interface (between Reader & laptop) and data loading
Data Volume:
o Maximum size: 1,200 trolleys * 10 changes per day = 12,000 lines of data per day (when all
trolleys are equipped)
7.3. Tag Installation

The tag shall be fixed underneath the trolley, separated from the trolley by an optimum distance to ensure
readability.
45/48
8. Annex 1 – Global User Requirements – Trial Requirements
Traceability Matrix
8.1. Traceability Matrix
The User Requirements in grey are taken into account in the Trial objectives.
The User Requirements in red will not be part of the Trial objectives.
Trolley
# Description Content
Type
Manage Catering Equipment Asset
UR 01 Identify each trolley as a unique asset ALL
Record chronological trolley data / information (date, time, location status, operational
UR 02 ALL
status)
UR 03 Use chronological trolley data / information ALL
UR 04 Use U/S trolley status information (date, location, type of damages, frequencies) ALL
UR 05 Use chronological transfers of responsibilities -
UR 06 Record time spent by trolley in each Catering Zone ALL
UR 07 Calculate Trolley life expectation ALL
UR 08 Analyse Trolley cycle ALL
UR 09 Dashboard consultation for performance analysis ALL
Plan Equipment Retirement
UR 10 Identify trolleys scheduled for retirement ALL
Determine Catering Equipment Requirements
Find out how many trolleys are located in each location and by operational status
UR 11 ALL
Remark: this can be done at any time along the process (planning & real-time
operational activities), by airline, by type of trolley, for stakeholders
UR
Develop Catering Equipment Allotment Plan ALL
11a
Ensure Daily Catering Equipment Requirements
Trolley flow expectation arriving/leaving Catering Facility (weekly & daily basis) per
UR 12 ALL
type, airline, contents
Alarm Notification when available trolley volume is below defined availability
UR 13 ALL
threshold, taking into account acceptable substitution
Build Trolleys
Except
UR 14 Assign trolley from proper airline to a specific flight number / date in the system
DF
Except
UR 15 Write flight number / date to trolley RFID Tag
DF
Assign contents to a trolley (already assigned to a flight number/date) by item and Except
UR 16
quantity in the system and confirm against airline specifications DF
Except
UR 17 Write contents to trolley RFID Tag
DF
Except
UR 18 Assign trolley to a staging area zone in the system
DF
Automatically prepare Customs Docs and Catering Manifest by using data recorded Except
UR 19
in the system DF
Re-build Duty Free Trolleys
Assign Duty Free trolley from proper airline to a specific flight number / date in the
UR 20 DF
system
46/48
Trolley
Type
UR 21 Write flight number / date to Duty Free trolley RFID Tag DF
Assign Duty Free contents to a Duty Free trolley (already assigned to a flight
UR 22 number/date) by item and quantity in the system and confirm against airline DF
specifications
UR 23 Write contents to Duty Free trolley RFID Tag DF
Automatically prepare Customs Docs and Catering Manifest by using data recorded
UR 24 DF
in the system
UR 25 Timestamp to indicate when Duty Free Building ends DF
Return Duty Free Trolleys to Caterer Facility
UR 26 Identify duty free trolleys for a specific airline and flight number / date DF
UR 27 Identify duty free trolleys leaving the Duty Free Supplier Bonded Facility DF
Move Trolleys to Staging Area
UR 28 Identify trolleys entering the Staging Area ALL
UR 29 Consult for a specific flight number/date trolley readiness status (ready, not ready) ALL
UR 30 Ensure all trolleys are ready for a specific flight number/date ALL
Monitor and record temperature inside trolley and trigger alarm before cold chain is
UR 31 FOOD
broken
Except
UR 32 Monitor trolley location and trigger alarm if in the wrong zone of the staging area
DF
Prepare and Load Trolleys onto Trucks
Facilitate trolley sorting to ensure all trolleys are picked up for loading onto
UR 33 ALL
appropriate truck for a specific flight number/date
UR 34 Identify trolleys leaving Catering Facility and timestamp to stop catering cycle ALL
UR 35 FOOD
broken
Deliver Trolleys to Aircraft
UR 36 Identify in which aircraft trolleys are loaded ALL
UR 37 Provide trolley content verification on board ALL
UR 38 Identify where items are located in each galley on board ALL
UR 39 FOOD
broken
Operate Onboard Aircraft
UR 40 Record door opening / closing date for Duty Free trolleys DF
UR 41 Write on RFID Tag status U/S to identify U/S trolleys and record date ALL
UR 42 Ensure that U/S ID can only be cancelled by Maintenance staff ALL
Offload Trolleys from Aircraft
UR 43 Identify from which aircraft trolleys are off loaded ALL
Receive Trolleys
UR 44 Identify trolleys entering the Catering Facility and timestamp to begin catering cycle ALL
UR 45 Identify leftover contents of duty free trolleys entering the Catering Facility DF
UR 46 Identify leftover contents of bar trolleys entering the Catering Facility Bar
UR 47 Identify U/S trolleys entering the Catering Facility ALL
UR 48 Identify repaired trolleys entering the Catering Facility ALL
Clean Food Trolleys
A dedicated tracking point has been added for the trial while no user requirements
were identified
Ship Duty Free Trolleys to Duty Free Supplier’s Bonded Facility
47/48
Trolley
Type
Identify Duty Free trolleys leaving the Catering Facility for Duty Free Supplier Bonded
UR 49 DF
Facility. Timestamp in the system to show start of Duty Free cycle
UR 50 Identify the Duty Free trolleys entering the Duty Free Supplier Bonded Facility DF
Inspect Trolleys
UR 51 Declare trolleys as U/S ALL
Store Food Trolleys
Ship U/S Trolleys to Repair Facility
Identify U/S trolleys leaving the Catering Facility for Repair Facility and timestamp to
UR 52 ALL
start repair cycle
UR 53 Identify U/S trolleys arriving at Repair Facility ALL
Repair U/S Trolleys
UR 54 Record actions performed on each trolley in the system ALL
UR 55 Record material/spares used on each trolley in the system ALL
Record release to service for each trolley in the system and cancel U/S Tag status on
UR 56 ALL
RFID Tag
Return Repaired Trolleys
UR 57 Identify repaired trolleys leaving the Repair Facility and timestamp to end repair cycle ALL
48/48

Trial Requirements v1.4

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Trial Requirements v1.4

Hochgeladen von

Copyright:

Verfügbare Formate

INFLIGHT CATERING

Stakeholder Physical Location Type of product

Catering Facility sites code:

Process Description Deliverables

• Description of the detailed processes and main operational

Identify issues encountered issues

• The elements of the user requirements to be tested in the

Select • The technology to be carried forward to trial based upon Technology

• The results of the trial applied to the inflight processes as

Develop a • A new Recommended Practice to be included in future Recommended

2.2. Project Scope

IATA invites suppliers to form partnerships in order to deliver an optimum solution.

2.3. Process scope

Operate Inflight Service Activities

Pre-flight In-flight Post-flight

Move Clean Food Store

Manage and Track

Measure, Analyse and Improve

Process ID Tracking Points

Operate Inflight Service Activities

ID RFID fixed antenna reading in Schiphol KCS Facility

ID RFID handheld - manual reading outstation

Trolley Operational Status - Tree Analysis Description

<< - >> FUNCTION MENU

<< - >> FUNCTION MENU

Operating Mode & Rule

Operating Mode & Rule

4.1.2. Determine Catering Equipment Requirements

Operating Mode & Rule

Operate Inflight Service Activities

Pre-flight In-flight Post-flight

Move Clean Food Store

4.2.1. Ensure Daily Catering Equipment Requirements

<< - >> FUNCTION MENU

<< - >> FUNCTION MENU

Operating Mode & Rule

4.2.4. Receive Trolleys

<< - >> FUNCTION MENU

Operating Mode & Rule

Operating Mode & Rule

<< - >> FUNCTION MENU

Operating Mode & Rule

<< - >> FUNCTION MENU

Operating Mode & Rule

<< - >> FUNCTION MENU

Operating Mode & Rule

Case 1: The trolley remains ‘’Serviceable’’

Case 2: The trolley is set to ‘’Unserviceable’’ (U/S)

For the following step, go to step 7.

Change Trolley status back to:

Durability Climate conditions

7.2. Information System equipment

7.3. Tag Installation

Das könnte Ihnen auch gefallen