IPS CI-Application Specification.DNATA-1.3.0

Transcription

dnata - IPS CUSS Application
Functional Specification
Version 1.3.0
MATERNA GmbH Information & Communications
Vosskuhle 37 · 44141 Dortmund Germany · Phone : +49 231 5599 00 · www.materna-ips.com
Integrated Passenger Services
This document is protected by copyright.
All rights reserved, including the rights to translation, copies, and reproduction using photomechanical
or electronic systems. Protected trade marks, brand names etc. are not explicitly stated as such in the
text. The lack of such identifiers in no way implies that the terms are not free names as defined by
applicable trade mark and brand name legislation.
Limitation of Liability
The information in this document has been carefully checked and can be considered reliable.
Nevertheless, no guarantee can be given for the accuracy of the information in this document. In
particular, no pledge can be given as to the suitability of the products described here for specific
purposes.
MATERNA retains the right to alter the products and product information specified here. MATERNA
accepts no liability from events arising from the usage of the products described here. Issue of this
document is not accompanied by licenses entitling you to use the listed products, nor products of
MATERNA or of other companies.
MATERNA GmbH
Information & Communications
Vosskuhle 37
44141 Dortmund, Germany
Phone
+49 (231) 55 99-351
Fax
+49 (231) 55 99-359
Email
WEB
[email protected]
http://www.materna-ips.com
Document title:
IPS CUSS Application / Functional Specification
Version:
1.3.0
Document number:
NOT ASSIGNED
Document status:
PROPOSED
Document path:
F:\massai.all\1.Customers\EK\DNATA\Functional Specification\IPS CIApplication Specification.DNATA-1.3.0.doc
© 2012
MATERNA GmbH
IPS CI-Application Specification.DNATA-1.3.0.doc
2
Modification/Change History
Version Date
Author
Description
1.0
11/05/2012
Gehling, Andreas
•
Document Creation
1.0.a
05/06/2012
Gehling, Andreas
•
Corrections and enhancements for the general
process flow and options and the identification
subprocess.
… 08/06/2012
Gehling, Andreas
•
Specifications for FOID selection and input.
11/06/2012
Gehling, Andreas
•
Incorporation of Alroy’s comments from
11/06/2012
12/06/2012
Gehling, Andreas
•
Amended general process flow diagram.
•
Specifications for Select-Flight and SelectPassenger processes.
•
Added comments and corrections from Bala.
•
Added comments and corrections from Volker
and a chapter on General Error Handling
•
14/06/2012
•
Amended screen design for Select Passenger
to display already checked-in passengers.
•
Added new chapters for Help- and Timeout
pop-up windows.
•
Added new chapter on application timeouts.
1.1
14/06/2012
Gehling, Andreas
1.1.1
22/06/2012
Gehling, Andreas
•
18/06/2012
1.2
02/07/2012
Gehling, Andreas
•
Added chapter on system architecture
1.2
04/07/2012
Gehling, Andreas
•
Added chapter on generic- and German APIS.
1.2.1
02/08/2012
Gehling, Andreas
•
Revised APIS and GER APIS sections.
•
Added UMRAH handling
•
Started US APIS definitions
1.2.2
06/08/2012
Gehling, Andreas
•
Incorporation of Alroy’s & Bala’s comments
from 06/08/2012
07/08/2012
Gehling, Andreas
•
Further specification of APIS handling.
08/08/2012
Gehling, Andreas
•
Corrections and incorporation of Alroy’s &
Bala’s comments from 08/08/2012
10/08/2012
Gehling, Andreas
•
Updated General Process flow to cater for
Credit Card Verification after check-in.
© 2012
MATERNA GmbH
3
1.2.3
13/08/2012
Gehling, Andreas
•
Corrections and incorporation of Alroy’s &
Bala’s & Parvez’ comments from 13/08/2012
1.3.0
20/08/2012 …
Gehling, Andreas
•
New section for Fatal Error Popup
•
New section for Credit Card Check and Central
Screen
•
New sections for Seat Change and FQTV
modifications
Open Items
Date
Description
Requested
09/08/2012
For APIS we still need to define
Mandatory items for NextKin and address
which data items are mandatory
input for US APIS.
and must be provided by the passenger before he/she can continue
with the check-in process.
10/08/2012
CC Verification by last 4 digits
Needs definition & integration in the process
14/08/2012
You want to have the scan
passport image process
independent from the APIS
process so that we could ignore
APD elements and always scan
the PP?
Needs clarification.
>> Yes, this will be independent.
e.g. passenger travelling to CMB
on UL does not need APIS but
needs passport image scanned
and stored. For passenger
travelling on KU to KWI may need
APIS and image stored. EK may
need APIS but no image storage.
14/08/2012
© 2012
Cancel/Back button for Scan
Passport Popup
Needs process definition
MATERNA GmbH
4
Table of Contents
1
Functional Specification ............................................................................................. 8
1.1
Basic Requirements....................................................................................................... 8
1.2
General Application Options .......................................................................................... 9
1.3
General Check-in Process........................................................................................... 10
1.3.1
General Error handling ................................................................................................ 11
1.4
Language Selection ..................................................................................................... 12
1.4.1
Initial Language Selection............................................................................................ 12
1.4.2
In Process Language Selection ................................................................................... 15
1.5
Identification Process................................................................................................... 17
1.5.1
Scanning and Reading Devices................................................................................... 18
1.6
Identification via FQTV Number Input ......................................................................... 19
1.6.1
FQTV Program Selection............................................................................................. 19
1.6.2
Manual FQTV Number Input........................................................................................ 21
1.7
Identification via PNR Input ......................................................................................... 23
1.8
Identification via ETKT Number Input .......................................................................... 25
1.9
Identification via Bar-Code Scanning .......................................................................... 27
1.10
Identification by inserting FQTV Cards ........................................................................ 29
1.11
Flight Selection ............................................................................................................ 31
1.12
Passenger Selection .................................................................................................... 33
1.13
APIS Data Capture ...................................................................................................... 36
1.13.1
Generic APIS ............................................................................................................... 38
1.13.2
Reading Passports (UMRAH-, US-, German-, Generic APIS) .................................... 39
1.13.3
German APIS............................................................................................................... 41
1.13.4
UMRAH........................................................................................................................ 45
1.13.5
US APIS....................................................................................................................... 48
1.14
Credit Card Number Check ......................................................................................... 64
1.15
Central Screen (Check-in Status and Modification)..................................................... 66
1.16
Seat Change ................................................................................................................ 68
© 2012
MATERNA GmbH
5
1.17
Frequent Flyer Mileage Registration ........................................................................... 70
1.17.1
FQTV Program Selection............................................................................................. 71
1.17.2
Manual FQTV Number Input........................................................................................ 73
1.18
Passenger Help Popup................................................................................................ 75
1.19
User Timeout Popup .................................................................................................... 77
1.20
Fatal Error Popup ........................................................................................................ 78
2
System Architecture.................................................................................................. 79
2.1
Physical Architecture ................................................................................................... 79
2.1.1
MACS DCS .................................................................................................................. 79
2.1.2
Business Logic Server (Primary) ................................................................................. 80
2.1.3
Business Logic Server (Backup).................................................................................. 80
2.1.4
Database Server (mySQL/ORACLE)........................................................................... 80
2.1.5
Administration Server .................................................................................................. 80
2.1.6
Storage (1000 GB)....................................................................................................... 81
2.1.7
Load Balancer.............................................................................................................. 81
2.1.8
Kiosk Clients ................................................................................................................ 81
2.2
Logical-, Information- and Conceptual Architecture .................................................... 82
2.2.1
Action Provider............................................................................................................. 82
2.2.2
Business Logic............................................................................................................. 83
2.2.3
Business Rules ............................................................................................................ 83
2.2.4
Configuration................................................................................................................ 83
2.2.5
DCS (MACS)................................................................................................................ 85
2.2.6
Kiosk Application ......................................................................................................... 85
2.2.7
Kiosk GUI..................................................................................................................... 85
2.2.8
Mobile GUI (optional) ................................................................................................... 86
2.2.9
WEB GUI (optional) ..................................................................................................... 86
2.2.10
TIMATIC....................................................................................................................... 86
2.2.11
ATLAS.......................................................................................................................... 86
2.2.12
Configuration................................................................................................................ 86
2.2.13
DocGen........................................................................................................................ 87
2.2.14
GCI............................................................................................................................... 87
© 2012
MATERNA GmbH
6
2.2.15
MediaScan ................................................................................................................... 87
2.3
Application Features .................................................................................................... 87
2.4
Technologies................................................................................................................ 88
3
Miscellaneous/To be Completed .............................................................................. 90
3.1
Application Timeouts ................................................................................................... 90
3.1.1
Warnings and Timeouts (Business Logic) ................................................................... 90
3.1.2
General Agreements.................................................................................................... 91
3.2
Passenger Check-in .................................................................................................... 93
3.3
Branding....................................................................................................................... 95
3.4
Common Use - CUSS.................................................................................................. 96
3.5
Clients .......................................................................................................................... 97
3.6
Application Hosting ...................................................................................................... 97
3.7
DCS Systems Support................................................................................................. 97
3.7.1
Direct DCS Connection................................................................................................ 98
3.7.2
DCS Connection via Service Provider ......................................................................... 98
4
Contact Information................................................................................................... 99
© 2012
MATERNA GmbH
7
1
Functional Specification
This Functional Specification (FS) defines the base for the provision of the IPS Checkin application to dnata.
It shall list all requirements for the envisaged solution as they have been discussed
between MATERNA and dnata during the FS meetings and were agreed between the
two parties.
In addition to the documented requirements and features this document shall also list
all deviations from the standard IPS check-in application product as it was originally
defined by Materna.
By approving this document both parties agree the scope of deliveries, implementation work and services listed within this document. Changes to the definitions in this
document shall be handled through separate change requests.
Reference to contract document ….
Please also refer to the latest version of
„General Terms and Conditions for Work and Services of MATERNA GmbH“
1.1
Basic Requirements
The following basic requirements were discussed and agreed during a first workshop
with dnata- and EGIT members in Dubai in week 21/2012.
© 2012
•
Language selection – English / Arabic,
•
FOID – PNR type-in (alpha numeric), ETKT type-in (13 digit numeric), ETKT
barcode scan, FQTV type-in (Own/Partner), FQTV card insert (Own, Partner),
Boarding pass scan, configure turn on/off,
•
Flight Selection (if DUPE flights only),
•
Passenger Selection – group size 5 + infants (configured on MACS, in future evtl.
9 pax), only PNR groups, no ad-hoc groups, new check-in and already checkedin, dnata – staff subload handling???,
MATERNA GmbH
8
1.2
•
APIS – standard, Umrah, German APIS, US APIS, machine-readable scan of
passport, manual input of passport data? (dnata), capture of passport image,
national ID card gcc nationals/countries (dnata), visa image capture (dnata),
•
FQTV addition – Own, partner, type-in, card-read-in, logo, configuration,
•
Seat Selection – Current flight, onward checked-in flight, Seat map
definition/display,
•
Boarding Pass printing – Current, onward, ATB 1 stock, PDF 417 barcode,
•
Baggage tag printing – Current, onward, without weighing, 2 pcs per pax, to be
turned off on day 1, may implement at later day. Configurable,
•
Gate Comment,
•
Reports – xml file output, other airline stats.
General Application Options
The chapter describes the business processes and options supported by the check-in
application. Options not explicitly listed in the following tables are not provided through
the applications business process. Changes and enhancements to the descriptions
below need to be reviewed and will be defined through separate change requests.
Changed requests are not included in the commercial contract and therefore will be
charged separately.
Change requests are integrated in the MATERNA release cycle and shall follow a
defined build process. Change requests have to be defined and specified until an
agreed editorial deadline to get integrated into the envisaged product release.
© 2012
•
The application will be a dnata-branded application showing the (secondary) logo
of the currently handled airline. The layout will be defined in the separate
document [DOCREF].
•
The application is executed as a single instance for all handled airlines. The
application determines the actual branding from the parameters provided by the
CUSS platform.
•
The application connects to the MACS DCS using a dedicated version of the
Generic Check-in Interface (GCI). The implementation of that GCI uses the XML
interface definitions from the document [DOCREF] provided by dnata.
MATERNA GmbH
9
1.3
General Check-in Process
The diagram below depicts the general flow through a passenger’s check-in process
starting with the language selection right after the activation by the CUSS platform.
Picture 1
General check-in
process
© 2012
MATERNA GmbH
10
After successfully finalizing the APIS process for all passengers in a group the
application checks in all passengers on the MACS DCS behind the scene. - All
passengers in specified group then will have a pre-assigned seat.
The application also follows the concept of a central screen where passenger data is
summarized and displayed and from where a passenger (or group of passengers) can
optionally select changing their frequent traveler mileage account or their seat.
If configured passengers are allowed to print baggage tags before the application
prints all required boarding passes for the checked-in persons.
1.3.1
General Error handling
CUSS platform reported errors will be handled and displayed with an appropriate error
message (e.g. error popup). - Dependent on the error severity the application terminates and goes into UNAVAILABLE mode until it detects the absence of the error that
led to its non-availability.
In any case within the check-in process the application tries to finish the check-in
session as far as possible. E.g. the occurrence of a card- or passport reader error
during the printing process will not terminate the check-in process, but the application
prints the remaining documents and goes to UNAVAILABLE once the check-in
session has been finished.
If the application detects that the MACS system is not available for checking in passengers, the application immediately goes into UNAVAIABLE mode. – The actual
session in this case cannot be finished. After the application finds the MACS system
available it returns to the AVAILABLE mode, unless another error situation forces the
application to remain UNAVAILABLE.
TBD: MACS reported errors and their handling…
Items
Specification
Pre-Conditions
Process descriptions
Configuration items
Post-Conditions
Error-Conditions
© 2012
•
No specific error handling required.
•
Refer to paragraph: 1.3.1 General Error handling
MATERNA GmbH
11
1.4
Language Selection
1.4.1
•
Application initially supports English and Arabic languages only. Further languages can be added via the configuration. Language files need to be provided as
an HTML subset that is used by FLASH/FLEX.
•
dnata provides the translations into other languages.
•
Vertical text orientations are not supported.
Initial Language Selection
Picture 2
The language
selection screen
at process start
© 2012
Items
Specification
Pre-Conditions
•
Application is in AVAILABLE state and gets activated by
the CUSS platform.
•
The CUSS platform provides branding information during
activation.
MATERNA GmbH
12
Items
Configuration items
Post-Conditions
© 2012
Specification
•
Default language(s) at process start will always be the
configured default and primary language(s).
•
The application opens/enables the required hardware
devices for document reading through the CUSS
platform allowing advanced passenger to skip the
language selection just be presenting an FOID.
•
Right after activation by the CUSS platform the language
selection is displayed as a regular application screen (not
as a popup).
•
If there’s only one language configured for an airline or
origin the initial language selection is skipped and the
language selection button is hidden from the GUI or will
be displayed as disabled.
•
If the number of selectable languages exceeds the
available screen size the application allows the
passenger to scroll through the horizontal list using
scroll-left and/or scroll-right buttons on the bottom of the
screen.
•
The language selection screen supports a (configurable)
primary- and Arabic language. If Arabic is not configured,
the instruction text will be bottom aligned (same as
Arabic in the picture above).
•
After a configurable timeout or using the Exit button the
application switches back to AVAILABLE. Thereafter the
CUSS CLA is displayed.
•
User Timeout
•
FOID types are configurable per handled airline (device
enabling).
•
Languages are configurable per handled airline.
•
Default language can be configured per origin/airport.
•
Primary language.
•
Arabic language (yes/no)
•
Application will use the selected language until a different
language is selected during the check-in process.
•
Once Arabic has been selected by the passenger the
application switches the screen orientation from ‘left to
right’ to ‘right to left’.
•
If the language is switched from Arabic to any other
language the application switches the screen orientation
from ‘right to left’ to ‘left to right’.
•
Enabled devices remain enabled for FOID selection but
will be closed when the application switches to
MATERNA GmbH
13
Items
Specification
AVAILABLE.
Error-Conditions
© 2012
•
•
MATERNA GmbH
14
1.4.2
In Process Language Selection
Picture 3
The language
selection screen
during the CI
process…
Picture 4
… and when
Arabic was the
previous selected
language.
© 2012
MATERNA GmbH
15
Items
Specification
Pre-Conditions
•
Application is ACTIVE and the initial language selection
was already carried out.
•
At any time and where applicable in the check-in process
the language selection will be displayed as a popupscreen as shown above. Passengers may choose
closing the popup without selecting a language (Close
button).
•
After selecting a language, selecting close or after a
configurable timeout the GUI closes the popup, switches
back to screen below the popup. - The selected language will then be used by the GUI until the passenger
selects a new language.
•
User Timeout
•
Languages are configurable per handled airline.
•
Default language can be configured per origin/airport.
•
Primary language.
•
Arabic language (yes/no)
•
Application will use the selected language until a different
language is selected during the check-in process.
•
Once Arabic has been selected by the passenger the
application switches the screen orientation from ‘left to
right’ to ‘right to left’.
•
If the language is switched from Arabic to any other
language the application switches the screen orientation
from ‘right to left’ to ‘left to right’.
•
•
Configuration items
Post-Conditions
Error-Conditions
© 2012
MATERNA GmbH
16
1.5
Identification Process
Picture 5
The FOID selection screen
Items
Specification
Pre-Conditions
•
Passenger has selected a language for the check-in
process.
•
Scanning and reading devices have been enabled by the
application.
•
Depending on the device configuration for the provided
branding information and device availability (physical and
functional) the application displays the identification
options for the passenger.
•
The passenger then can select an FOID option on the
screen or directly present a 2D bar coded document
(ETKT receipt or boarding pass) to a scanning device.
•
If manual input was selected the application displays the
appropriate input screen.
•
If non-manual input was selected by the passenger the
application displays an animation showing the passenger
how to use the bar code scanner or the card reader.
© 2012
MATERNA GmbH
17
Items
Configuration items
Post-Conditions
Error-Conditions
1.5.1
Specification
•
If the passenger presents a valid document the application tries to identify the passenger or passenger group on
the DCS.
•
User Timeout
•
FOID types are configurable per handled airline.
•
Application requests the passenger to input identification
data either manually or by presenting the appropriate
machine readable identification documents.
•
A user timeout as well as the Exit button will terminate
the check-in process and will put the application into
AVAILABLE state.
•
•
Scanning and Reading Devices
The application uses the following input devices for the above mentioned Forms Of
Identification (FOID’s).
© 2012
•
Only those devices are opened for document insertions that are defined in the
applications configuration.
•
Application uses the card reader device for FQTV cards.
•
Application also uses a bar code scanner for scanning of 2D bar codes.
•
To keep the application out of the PCI-DSS scope the application does not use
any credit cards for identification purposes.
•
For handling of FQTV and Credit Cards (if necessary) the application will only use
the FOID Interface of the CUSS platform. - The application adheres to the restrictions and constraints as they are defined in the CUSS standard.
MATERNA GmbH
18
1.6
Identification via FQTV Number Input
FQTV numbers can also be read from an FQTV card with a magnetic stripe. Cards will
be accepted for the airlines own FQTV program as well as for FQTV programs of
partner airlines.
1.6.1
FQTV Program Selection
Picture 6
The FQTV program selection
popup
© 2012
Items
Specification
Pre-Conditions
•
Passenger has selected manual FQTV number input
from the FOID selection screen.
•
The application disables all reading devices.
•
As the selection of the FQTV program is not optional for
the passenger, passenger have to select the FQTV
program within the above shown popup window.
•
The program can be selected for the airlines own FQTV
program as well as for FQTV programs of partner
MATERNA GmbH
19
Items
Specification
airlines.
Configuration items
Post-Conditions
Error-Conditions
© 2012
•
Popup window will close after FQTV program selection
and FQTV manual input screen is executed.
•
The popup is not displayed if only one FQTV program is
configured for the handled airline.
•
User Timeout
•
FQTV program per handled airline.
•
FQTV partner programs per handled airline.
•
If scrolling is not applicable, scroll buttons (horz./vert.)
will be hidden if specified per configuration.
•
After selection of the FQTV program the application
checks the configuration for selected FQTV program and
continues with the manual FQTV number input.
•
A user timeout terminates the check-in process and sets
the application into AVAILABLE state.
•
•
MATERNA GmbH
20
1.6.2
Manual FQTV Number Input
Picture 7
The manual
FQTV number
input screen
© 2012
Items
Specification
Pre-Conditions
•
Passenger has selected an FQTV program from the
FQTV program selection popup.
•
The application checks the configuration for selected
FQTV program and limits the manual FQTV number
input according to the configured number length.
•
FQTV number can be input manually. The number can
be given for the airlines own FQTV program as well as
for FQTV programs of partner airlines.
•
If configured for numeric input only, the GUI disables the
alpha keyboard from user input.
•
The GUI displays the FQTV program name and the
FQTV program logo for passenger information.
•
The GUI displays the length of the minimal required input
and the length of the current input.
•
Once the minimum required input has been entered by
MATERNA GmbH
21
Items
Specification
the passenger the GUI enables the ‘Continue’ button.
Configuration items
Post-Conditions
Error-Conditions
© 2012
•
User Timeout
•
FQTV program number format (min. length, max. length,
numeric, alphanumeric) per handled airline and/or FQTV
partner.
•
FQTV program logos.
•
•
•
Application executes the identification process via the
GCI on the DCS using the provided FOID information.
•
Touching the Back button, the application switches back
to the FOID selection screen.
•
A user timeout as well as using the Exit button will
terminate the check-in process and will put the
application into AVAILABLE state.
•
•
MATERNA GmbH
22
1.7
Identification via PNR Input
Picture 8
The manual PNR
input screen
Items
Specification
Pre-Conditions
•
Passenger has selected manual reservation code input
•
Reservation code input can be done only with Latin
characters.
•
The application checks the configuration and limits the
manual reservation code input according to the
configured number length.
•
The GUI displays the length of the minimal required
input.
•
Both, numeric- and alpha keyboards are enabled for data
input.
•
© 2012
MATERNA GmbH
23
Items
Specification
Configuration items
•
User Timeout
•
PNR code length per handled airline.
•
PNR code format (numeric/alphanumeric) per handled
airline.
•
•
•
AVAILABLE state.
•
•
Post-Conditions
Error-Conditions
© 2012
MATERNA GmbH
24
1.8
Identification via ETKT Number Input
The ETKT number can also be read from a 2D bar code presented by the passenger.
Picture 9
The manual ETKT
number input
screen
Items
Specification
Pre-Conditions
•
Passenger has selected manual ETKT number input
•
ETKT number input can be done only with Latin
characters.
•
The application checks the configuration and limits the
manual ETKT number input according to the configured
number length.
•
•
Only the numeric keyboard will be enabled for data input.
© 2012
MATERNA GmbH
25
Items
Configuration items
Post-Conditions
Error-Conditions
© 2012
Specification
•
•
User Timeout
•
ETKT number length per handled airline.
•
•
•
AVAILABLE state.
•
•
MATERNA GmbH
26
1.9
Identification via Bar-Code Scanning
Boarding passes with IATA RES 792 compliant 2D bar codes can also be used as
FOID.
Picture 10
Scanning the 2D
bar code animation
Items
Specification
Pre-Conditions
•
Passenger has selected the 2D bar code scanning option
•
The application checks data in the 2D bar code and
determines if the presented document is an ETKT or a
boarding pass.
•
In both cases the application carries out the identification
process as usual.
•
User Timeout.
•
ETKT number identification criteria per airline.
•
Configuration items
Post-Conditions
© 2012
MATERNA GmbH
27
Items
Specification
Error-Conditions
© 2012
•
Using the Close button the passenger can switch back to
the FOID selection.
•
A user timeout will terminate the check-in process and
will put the application into AVAILABLE state.
•
If the bar code data is not recognized as IATA Resolution
792 compliant the application refuses the check-in
request with an appropriate error message.
•
The application checks if the presented boarding pass is
an infant boarding pass and if so, refuses the check-in
request with an appropriate error message.
•
The operating carrier code on the BP is checked against
a station dependent list of airline codes in the
configuration of the application. - If the operating carrier
code cannot be found in the configuration, the check-in
process will be aborted with an appropriate error
message.
MATERNA GmbH
28
1.10
Identification by inserting FQTV Cards
Picture 11
Inserting an
FQTV card animation
Items
Specification
Pre-Conditions
•
Passenger has selected the reading FQTV card option
•
Cards will be accepted for the airlines own FQTV
airlines.
•
The application receives the card data (full FQTV
number) from the CUSS platform and carries out the
passenger identification process.
Configuration items
•
User Timeout
•
FQTV card formats for application accepted cards.
•
•
•
Post-Conditions
© 2012
MATERNA GmbH
29
Items
Error-Conditions
Specification
•
Using the Close button the passenger can switch back to
the FOID selection.
•
A user timeout will terminate the check-in process and
will put the application into AVAILABLE state.
•
If the application cannot detect the inserted card in its
configuration for the current handled airline, the application displays an appropriate error message.
The number of re-insertions/retries is not limited.
© 2012
MATERNA GmbH
30
1.11
Flight Selection
Picture 12
Selecting an
alternative flight
from a MACS
provided flight list.
Items
Specification
Pre-Conditions
•
A passenger or a group of passenger has been
successfully identified on MACS by using one of the
above described FOID’s.
•
Passenger(s) must have multiple segments for the same
booking.
•
MACS can provide alternative flight for this/these
passengers.
•
If provided by MACS the application displays a list of
multiple flights for the passenger.
•
The passenger then selects a flight- or flight segment
from the displayed list.
•
The application informs MACS about the selection and
will work with this new flight assignment.
•
User Timeout
•
Configuration items
© 2012
MATERNA GmbH
31
Items
Specification
Post-Conditions
Error-Conditions
© 2012
•
After the selection the new flight assignment will be used
to retrieve the full passenger details from MACS.
•
Using the Back button the passenger can switch back to
the FOID selection.
•
A user timeout and the use of the Exit button will terminate the check-in process and will put the application into
AVAILABLE state.
•
•
MATERNA GmbH
32
1.12
Passenger Selection
Picture 13
Selecting or deselecting passengers for or from
check-in
Items
Specification
Pre-Conditions
•
A passenger or a group of passenger has been
successfully identified on MACS by using one of the
previous described FOID’s.
•
Passenger of a passenger group must be on the same
PNR.
•
Maximum number of passengers is configurable on
MACS.
•
For single passenger booking retrieval
© 2012
o
The passenger will be auto selected.
o
The scroll button, Select/Deselect Button and
Select/Deselect All Button should be made
invisible.
•
For passenger group retrieval all passengers by default
are unselected.
•
Passengers already checked-in will be displayed with a
MATERNA GmbH
33
Items
Specification
green tick-mark and an additional “Checked-in” text.
The select/deselect buttons for these passengers are
switched off and also the select/deselect all button will
not affect the status of already check-in passengers.
Configuration items
Post-Conditions
© 2012
•
The next flight segment information (flight number, dateand time) out of the actual origin as well as the complete
routing are displayed for the passenger or passenger
group within the routing details area.
•
Infants (< 2 years, information provided by MACS) are
displayed with an infant icon.
•
Infants will always be selected/de-selected together with
the linked adult passenger.
•
Passenger(s) can select or de-select passengers for or
from check-in using the select/deselect buttons attached
to the passenger list.
•
Passenger(s) can select or de-select passengers for or
from check-in using the Select/De-select All Button.
•
Selected passengers are displayed with a green tickmark.
•
Unselected passengers don’t have tick-mark and will not
be checked-in on MACS.
•
When any of passengers in the list is not selected,
pressing the Select/Deselect All Button selects all
passengers in the list.
•
When all the passengers in the list are selected, pressing
the Select/Deselect All Button de-selects all passengers
in the list.
•
The Continue button is only enabled when at least one
passenger in the list is selected for check-in.
•
The application proceeds to APIS Handling for all
selected passengers if APIS required.
•
All selected passengers are checked-in on MACS if no
APIS required.
•
User Timeout
•
Maximum number of passengers to be displayed in the
list.
•
•
If passport scanning is necessary (no APIS on flight) the
application scans the passports and stores the passport
image in a sever-side database.
MATERNA GmbH
34
Items
Error-Conditions
© 2012
Specification
•
After the selection, all selected passengers are
processed for APIS, if required.
•
Using the Back button the passenger can switch back to
the Flight Selection screen if there are any DUPE flights.
•
Using the Back button the passenger can go back to
FOID screen if there are no DUPE flights.
•
A user timeout and the use of the Exit button will terminate the check-in process and will put the application into
AVAILABLE state.
•
If no passenger was found for the presented FOID data,
the application displays an appropriate error message
and thereafter terminates the check-in process and goes
to AVAILABLE mode.
•
MATERNA GmbH
35
1.13
APIS Data Capture
The chapter defines the APIS process with its various sub processes for German-,
US- and UMRA APIS handling.
Picture 14
The distinction of
the various APIS
processes.
Items
Specification
Pre-Conditions
•
© 2012
After passenger retrieval, passengers for whom APIS
data capture is required have an APD element set in the
data returned by MACS.
o
If passenger not checked-in PST = “ ”, then scan
passport (no need to check for SCN value).
o
If passenger checked-in PST = “S” or “C” and
SCN = “ ” , “OLC” or “ITC”, then scan passport.
•
For flights for which the FLI flag contains a ‘U’ UMRAH
handling is carried out.
•
For all other flights either US- or German APIS is
executed, depending on the passenger’s destination.
The application queries the ATLAS service to gather the
MATERNA GmbH
36
Items
Specification
area from the destination code.
Configuration items
© 2012
•
If APIS required, but if it’s not UMRAH, German or US
the application scans passport elements only.
•
For all passengers already checked in, the application
checks if their passports have already been scanned at a
counter or at a kiosk (SCN = “CTR” or SCN = “SSK”), or
if these passengers have checked-in via internet (SCN =
“OLC”).
•
When the passport was already scanned at the counter
or at the kiosk the application proceeds with the next
passenger/infant in the group.
•
If passengers passport wasn’t scanned (SCN = “”) or the
passenger has checked-in via internet, the passport
needs to be scanned at the kiosk and data has to be
send to MACS for processing.
•
If enabled in the configuration, passport is scanned for
not checked-in passengers (if not scanned already) and
a valid image (JPEG) of the presented passport is stored
after verifying it is passport image (hardware check).
•
Depending on the configuration the image file is stored
either on the local kiosk storage or in a server based
database with the following naming convention:
o
Flight Number (AANNNN)
o
Flight Date (NNAAA)
o
Sequence number (NNNN)
o
Kiosk Identification (eg. DXBT1FK01)
o
Transaction Timestamp (HHMMSS)
All following items are configurable per airline/brand/origin
•
UMRA handling (enabled/disabled).
•
US APIS handling (enabled/disabled).
•
GER APIS handling (enabled/disabled).
•
Store passport image (enabled/disabled).
•
Capture Next Kin data (enabled/disabled).
Post-Conditions
•
The appropriate APIS process (UMRA, US, GER) is
executed for all passengers in the passenger group.
Error-Conditions
•
Whenever the required APIS handling (UMRA, US, GER)
is switched off in the configuration, all passengers in the
group are directed to a staffed counter for data collection
•
MATERNA GmbH
37
1.13.1
Generic APIS
Picture 15
Generic APIS
process
© 2012
Items
Specification
Pre-Conditions
•
After passenger retrieval, passengers for whom APIS
data capture is required have an APD element set in the
data returned by MACS but the pre-conditions for
performing US-APIS, German-APIS or UMRAH don’t
apply.
•
The application requests every passenger in a group to
scan his/her passport according to the pre-conditions
and to the descriptions in chapter 1.13.2 Reading
Passports (UMRAH-, US-, German-, Generic APIS)
Configuration items
•
No specific items.
Post-Conditions
•
APIS data is sent to MACS for processing.
Error-Conditions
•
MATERNA GmbH
38
1.13.2
Reading Passports (UMRAH-, US-, German-, Generic APIS)
Picture 16
Capturing
passport data
Items
Specification
Pre-Conditions
•
If passenger not checked-in PST = “ ”, then scan
passport (no need to check for SCN value).
•
If passenger checked-in PST = “S” or “C” and SCN = “ ” ,
“OLC” or “ITC”, then scan passport.
•
The application displays a popup instructing the
passenger to scan his/her passport.
•
The popup shows the name of the passenger for whom
the passport needs to be scanned in its header.
•
Passports for infants must be scanned as well.
•
Passengers have 2 attempts to scan their passports.
•
Touching the NoPassport-button closes the pop-up
displays a final application screen advising the
passenger group to a staffed counter.
•
The numbers of attempts passengers have to scan their
passport. The default value is 2.
Configuration items
© 2012
MATERNA GmbH
39
Items
Specification
•
Post-Conditions
Error-Conditions
© 2012
Passport image storage location options:
o
Store passport image (yes/no)
o
Image location on the server/database, or
o
Image location locally on the kiosk (abs. path)
•
Passport data is transmitted to MACS for processing.
•
If configured the application also reads the passport
image to store it on a server located database or locally
on the kiosk hard disk drive.
•
If the MRZ on the passport cannot be read correctly
within 2 attempts, the check-in process is terminated for
the whole group of passengers and the application
advises all passengers to a staffed counter for document
check and scanning.
•
MATERNA GmbH
40
1.13.3
German APIS
Picture 17
German APIS
sub-process
Items
Specification
Pre-Conditions
•
ATLAS service returned GER for passenger destination.
•
Passengers passport wasn’t scanned (SCN = “”) or the
passenger has checked-in via internet (SCN = “OLC”) or
passenger is an IATCI passenger (SCN = “ITC”).
•
Only if MACS requests VISA data the application
additionally checks the TIMATIC service if any VISA is
required for passengers destination.
© 2012
MATERNA GmbH
41
Items
Specification
•
If TIMATIC also requests VISA data for the given
destination the application displays a screen with an
alpha-numeric keyboard for input of the VISA number
and Country of Issuance.
•
If TIMATIC does not request a VISA the application only
sets the VISA item in MACS (VIS = ”NO”)
Configuration items
•
TIMATIC URL and credentials (username/password) per
airline/brand.
Post-Conditions
•
VISA number and Country of Issuance is transmitted to
MACS for processing.
•
If TIMATIC didn’t request a VISA the VISA item in MACS
is set to No (VIS = ”NO”).
•
In the case TIMATIC cannot be contacted, the application displays an appropriate error message and advises
the passenger group to a staffed counter for document
check. The check-in session will be terminated for the
whole passenger group.
•
Error-Conditions
Picture 18
Manual input of
VISA Number
© 2012
MATERNA GmbH
42
Picture 19
Manual input or
selection of
Issuing Country
© 2012
Items
Specification
Pre-Conditions
•
Both, MACS and TIMATIC requested VISA data for
passenger’s destination and nationality.
•
The passenger enters the VISA number in the VISA
number entry field.
•
When the passenger enters the first character in the
Issuing Country Input field the configurable list of VISA
issuing countries becomes enabled for selection.
•
The countries displayed in the list are restricted to match
the characters in the input field.
•
If the passenger selects a country from the list box, the
country name is placed in the input filed, where it can be
edited by the passenger.
•
The passenger can also complete the country name in
the input field.
•
The Continue-button will be enabled when the entered
VISA number has enough characters and an ISOCountry code can be matched against the country name.
MATERNA GmbH
43
© 2012
Items
Specification
Configuration items
•
Minimum length of VISA number input.
•
List of possible VISA issuing countries.
Post-Conditions
•
VISA number and the ISO Country Code of the VISA
Issuing Country are sent to MACS for further processing.
Error-Conditions
•
•
MATERNA GmbH
44
1.13.4
UMRAH
Picture 20
UMRAH subprocess
Items
Specification
Pre-Conditions
•
Flight item FLI=”U”.
•
UMRAH handling is enabled in the configuration.
•
If the FLI item for a flight in MACS response is “U”, the
application performs the UMRAH questionnaire (see
below description) for all passengers in the group.
•
If MACS also requests APIS handling, then for each
© 2012
MATERNA GmbH
45
Items
Specification
passenger whose passport wasn’t scanned (SCN = “”) or
the passenger has checked-in via internet (SCN =
“OLC”) the passport has to be scanned.
Configuration items
•
As defined under 1.13 APIS Data Capture
Post-Conditions
•
UMRA fact is set for all passengers in the group
performing UMRAH.
Error-Conditions
•
Items
Specification
Pre-Conditions
•
Flight item FLI=”U”.
•
UMRAH handling is enabled in the configuration.
•
The passenger selects YES/NO on the screen.
Configuration items
•
None for the screen.
Post-Conditions
•
UMRA fact is set for the current passenger only when
he/she perform UMRAH.
Picture 21
UMRAH
questionnaire
© 2012
MATERNA GmbH
46
© 2012
Items
Specification
Error-Conditions
•
•
MATERNA GmbH
47
1.13.5
US APIS
Picture 22
US APIS
(overview)
© 2012
Items
Specification
Pre-Conditions
•
ATLAS service returned US/USA for passenger
destination.
•
Passengers passport wasn’t scanned (SCN = “”) or the
passenger has checked-in via internet (SCN = “OLC”) or
MATERNA GmbH
48
Items
Specification
passenger is an IATCI passenger (SCN = “ITC”).
© 2012
•
The application requests the passenger to scan his/her
passport and sends the scanned passport data to MACS
for processing.
•
If enabled per configuration and if Next Kin (a person's
closest living blood relative) data wasn’t captured and
saved earlier during the APIS process the application
requests the passenger to input the appropriate contact
details (phone number and name) and to select if it shall
be used for all passengers in the group.
•
If the application detects from the passport data that the
current passenger is a US citizen, it simply stores “US” in
the appropriate data field (COR) and continues with the
next passenger.
•
If the application detects from the passport data that the
current passenger is not a US citizen, it carries on with
the US Address- or Resident Card Details process.
Configuration items
•
As defined under chapter 1.13 APIS Data Capture.
Post-Conditions
•
All passengers in a group have provided all necessary
APIS details as requested by MACS and/or the
applications business process definition.
Error-Conditions
•
Whenever an error occurs for a passenger during APIS
handling, the whole passenger group is advised to a
staffed dnata-counter to finish APIS data collection there.
•
Refer to paragraph: 1.3.1 General Error handling.
MATERNA GmbH
49
1.13.5.1
US APIS – Input of Next Kin Contact
Picture 23
Input of contact
details
© 2012
Items
Specification
Pre-Conditions
•
Next Kin input is enabled per configuration and data
wasn’t captured and saved earlier during the APIS
process.
•
The application allows the passenger to either
o
skipping the data input using the appropriate
button,
o
entering contact details and select the re-use of
the entered data for all passengers in the group.
•
When the passenger selects the re-use button after data
input the provided data is stored internally and copied
automatically to the details of the next passenger in the
group. - In this case the application doesn’t display this
screen again.
•
The re-use data button only shown for passenger groups
and is disabled by default.
•
The application disables the alpha-keyboard for the
MATERNA GmbH
50
Items
Specification
contact phone number input.
•
The application disables the numeric keyboard for the
contact name input.
•
After touching the continue button the US-APIS process
is continued.
•
Minimum and maximum length of the contact phone
number input.
•
Minimum and maximum length of the contact name
input.
Post-Conditions
•
Application continues with the US APIS process as
defined in this document.
Error-Conditions
•
•
Configuration items
Picture 24
Next Kin input
process
© 2012
MATERNA GmbH
51
1.13.5.2
US APIS – Permanent Resident Card (PRC) Questionnaire
Picture 25
Ask passenger for
a PRC
© 2012
Items
Specification
Pre-Conditions
•
Passenger skipped or finished input of Next Kin Contact
or input of Next Kin Contact was disabled in the
configuration.
•
The application asks the passenger if he/she is a holder
of a Permanent Resident Card (PRC).
•
If the passenger selects NO the application asks the
passenger to manually input his/her destination address
in the US.
Configuration items
•
No specific configuration items.
Post-Conditions
•
Depending on the user input the application continues
with input of PRC number or destination address.
Error-Conditions
•
•
MATERNA GmbH
52
1.13.5.3
US APIS – Permanent Resident Card Number Input
Picture 26
Input PRC
Number
Items
Specification
Pre-Conditions
•
Passenger indicated on the previous popup screen that
he/she is in possession of a Permanent Resident Card
(PRC).
•
The application requests the passenger to input the PRC
number.
Configuration items
•
The required PRC Number length, default length = 9
Post-Conditions
•
The application sets the Country of Residence to
COR=“US” and reports it to MACS.
•
Application continues with the US APIS process as
defined in this document.
•
•
Error-Conditions
© 2012
MATERNA GmbH
53
1.13.5.4
US APIS – Country of Residence and Address Input
Picture 27
Manual input of
address details
© 2012
Items
Specification
Pre-Conditions
•
Passenger indicated on the previous popup screen that
he/she doesn’t have a Permanent Resident Card (PRC).
•
The application requests the passenger to enter address
details and select the re-use of the entered data for all
passengers in the group.
•
After selection of the data field to be filled in the
application shows an appropriate pop-up where the
necessary data can be selected/entered. The pop-up
windows are described further down.
•
When the passenger selects the re-use button after data
input the provided data is stored internally and copied
automatically to the details of the next passenger in the
group. - In this case the application doesn’t display this
screen again.
•
The re-use data button is disabled by default and shown
only for passenger groups.
MATERNA GmbH
54
Items
© 2012
Specification
•
Passenger can select/re-select the input fields in any
order.
•
The Continue-button will be enabled after all necessary
data has been provided by the passenger.
•
The application internally sets the Destination Country to
DCO=“US” and reports it to MACS.
Configuration items
•
No special configuration items needed.
Post-Conditions
•
Application has collected all necessary APIS data and
continues with the US APIS process as defined in this
document.
Error-Conditions
•
•
MATERNA GmbH
55
1.13.5.5
US APIS – Country of Residence (COR) Input
Picture 28
Country of
Residence input
© 2012
Items
Specification
Pre-Conditions
•
Passenger activated COR input in the previous screen.
•
The passenger enters his/her Country of Residence in
the input field.
•
Country Input field the configurable list of countries
becomes enabled for selection.
•
US/United States is not displayed in the selection list,
nor is it accepted through the input field.
•
The countries displayed in the list are restricted to match
•
If the passenger selects a country from the list box, the
country name is placed in the input filed, where it can be
edited by the passenger.
•
The passenger can also complete the country name in
the input field.
MATERNA GmbH
56
Items
© 2012
Specification
•
To avoid misspelling the Continue-button will only be
enabled when the country name in the input field exactly
matches a country name in the configured/displayed list.
•
If the GUI cannot match the country name in the input
field against a name in the selection list the Continuebutton remains/will disabled.
Configuration items
•
List of countries (except US).
Post-Conditions
•
The pop-up reports the input back to the calling screen in
1.13.5.4 US APIS – Country of Residence and Address
Input
Error-Conditions
•
•
MATERNA GmbH
57
1.13.5.6
US APIS – Address or Hotel Input
Picture 29
US Address input
© 2012
Items
Specification
Pre-Conditions
•
Passenger activated the US Address input in the
previous screen.
•
The passenger enters the US Address of his/her
destination address in the input field.
•
The Continue-button will be enabled when the US
Address length matches or exceeds the configured
minimum length.
Configuration items
•
Minimum and maximum length of the US Address input.
Post-Conditions
•
Input
Error-Conditions
•
•
MATERNA GmbH
58
1.13.5.7
US APIS – City Input
Picture 30
US City Name
input
© 2012
Items
Specification
Pre-Conditions
•
Passenger activated the US City input in the previous
screen.
•
The passenger enters the US City name of his/her
destination address in the input field.
•
The Continue-button will be enabled when the US City
name length matches or exceeds the configured
minimum length.
Configuration items
•
Minimum and maximum length of the US City name
input.
Post-Conditions
•
Input
Error-Conditions
•
•
MATERNA GmbH
59
1.13.5.8
US APIS – State Input
Picture 31
US State input
© 2012
Items
Specification
Pre-Conditions
•
Passenger activated the US State input in the previous
screen.
•
The passenger enters the US State of his/her destination
address in the input field.
•
State Input field the configurable list of US States
becomes enabled for selection.
•
The US Sates displayed in the list are restricted to match
•
If the passenger selects a US State from the list box, the
name is placed in the input filed, where it can be edited
by the passenger.
•
To avoid misspelling the Continue-button will only be
enabled when the US State name in the input field
exactly matches a US State name in the configured/
displayed list.
MATERNA GmbH
60
Items
© 2012
Specification
•
If the GUI cannot match the US State name in the input
field against a name in the selection list the Continuebutton remains/will disabled.
Configuration items
•
List of US States.
Post-Conditions
•
Input
Error-Conditions
•
•
MATERNA GmbH
61
1.13.5.9
US APIS – ZIP Code Input
Picture 32
US ZIP Code
input
© 2012
Items
Specification
Pre-Conditions
•
Passenger activated the ZIP Code input in the previous
screen.
•
The passenger enters the ZIP Code of his/her destination address in the input field.
•
The Continue-button will be enabled when the ZIP Code
length matches or exceeds the configured minimum
length.
Configuration items
•
Minimum and maximum length of the ZIP Code input.
Post-Conditions
•
Input
Error-Conditions
•
•
MATERNA GmbH
62
Picture 33
US APIS
(detailed)
© 2012
MATERNA GmbH
63
1.14
Credit Card Number Check
Picture 34
Credit Card
Number input
pop-up
© 2012
Items
Specification
Pre-Conditions
•
After the application executed the check-in validation
script through the GCI, MACS will indicate the credit card
validation requirement for the respective passengers.
•
The passenger inserts the credit card he/she used for the
reservation.
•
The application gets the (masked) credit card number
from the platform and transmits the last for digits to
MACS for verification.
•
Touching the No Credit Card button closes the pop-up
displays a final application screen advising the
passenger group to a staffed counter.
Configuration items
•
No specific items.
Post-Conditions
•
Credit card validation has been carried out for all
passengers requested by MACS.
Error-Conditions
•
MATERNA GmbH
64
Items
Specification
•
© 2012
MATERNA GmbH
65
1.15
Central Screen (Check-in Status and Modification)
Picture 35
Summary of the
check-in status for
all passengers in
a group.
Items
Specification
Pre-Conditions
•
All passengers in a group are checked in and the
application successfully passed the check-in validation
for all passengers.
•
The application displays the current status of all
passengers in a group (seats, itinerary, FQTV) in a
scrollable matrix.
•
A maximum of 4 flight segments will be displayed on the
screen.
•
Passengers can change their seat assignment per flight
segment (if available) using the appropriate buttons for
that flight segment. The application then opens and displays the seat map for the selected flight segment in a
separate screen popup.
o
© 2012
Where seat changes were requested but the
request could not be fulfilled a warning is
displayed which has to be confirmed by any of
MATERNA GmbH
66
Items
Specification
the passengers. - The warning shall be displayed
for the whole passenger group.
o
•
If no FQTV data is available for the passenger, the
passenger can add his FQTV number in a separate
screen pop-up.
•
If FQTV data for a passenger is available, the application
displays the last four digits of the registered FQTV
number.
o
Where FQTV changes were requested but the
request could not be fulfilled by MACS a warning
is displayed which has to be confirmed by the
passenger. - The warning shall be displayed for
the individual passenger.
•
Infants are displayed without any selection option.
•
Infants are listed in right after the adult they’re travelling
with.
•
Using the Continue button continues the check-in
process with the next document print step (baggage tags
and/or boarding passes)
Configuration items
•
No specific items.
Post-Conditions
•
Seats are changed for those passengers that requested
a modification on the pre-assigned seats.
•
FQTV parameters are stored within MACS for those
passengers that requested a modification for their FQTV
data.
•
•
Error-Conditions
© 2012
Seat Change buttons for flight segments for
which a seat map is not available will be shown
as disabled.
MATERNA GmbH
67
1.16
Seat Change
Picture 36
Seat change popup
Items
Specification
Pre-Conditions
•
A passenger selected a Seat button in the Central
Screen.
•
A seat map must be available for the flight segment and
the current travel compartment.
•
Seat maps are displayed for the current travel compartment only.
•
Seat map items which are not seats (galleys, toilets, etc.)
are displayed as spaces.
•
Already occupied seats are not selectable (displayed as
disabled).
•
Only free seats can be selected for a seat change.
•
Exit- and over wing seats are marked respectively.
•
When opening the pop-up the actual seat for the
Selected Passenger is displayed in the upper third of the
© 2012
MATERNA GmbH
68
Items
Specification
visible seat map area.
© 2012
•
Passenger can use the scroll buttons to virtually move
back and forth in the compartment.
•
Scrolling of seats shall be visualized by moving the seats
up/down in the visible area.
•
Passenger can switch between upper- and lower flight
decks if the travel compartment stretches over more than
only one flight deck.
•
If the application handles a passenger group the passenger can select a companion traveler from the passenger
list.
•
A seat can be changed for the currently selected
passenger.
•
If a different passenger is selected from the passenger
list, the current passenger is displayed as a Companion
Passenger; the newly selected passenger then is displayed as the Selected Passenger.
•
Touching the Continue button carries out the requested
seat change on MACS and returns to the Central screen.
•
Using the Back button returns to the Central screen
without modifying the pre-assigned seat.
Configuration items
•
No specific items.
Post-Conditions
•
Seating will be changed on MACS for those passengers
who’ve chosen new that is different from their preassigned seat.
Error-Conditions
•
•
MATERNA GmbH
69
1.17
Frequent Flyer Mileage Registration
Picture 37
FQTV card
insertion popup
Items
Specification
Pre-Conditions
•
A passenger selected a Frequent Flyer Number button in
the Central Screen.
•
An FQTV- and/or Partner FQTV program(s) must be
configured for the currently handled airline brand.
•
Logos of the acceptable FQTV and partner-FQTV
programs are displayed on top of the animation.
•
The passenger inserts and removes his frequent flyer
card as displayed in the animation.
•
After reading the card the application transmits the FQTV
program code and number to MACS for registration.
•
Using the No Card button returns to the Central Screen
without sending anything to MACS.
•
Touching the Manual Input button allows the passenger
to enter his FQTV program and number manually.
© 2012
MATERNA GmbH
70
Items
Specification
Configuration items
•
User Timeout
•
partner.
•
FQTV program logos.
•
•
•
If successful, the FQTV program code and number have
been registered on MACS for the passenger selected in
the Central Screen.
•
Application returns to the Central Screen.
•
•
Post-Conditions
Error-Conditions
1.17.1
FQTV Program Selection
Picture 38
The FQTV program selection
popup
© 2012
MATERNA GmbH
71
Items
Specification
Pre-Conditions
•
Passenger has selected manual FQTV number input in
the FQTV card insertion popup.
•
The application disables all reading devices.
•
As the selection of the FQTV program is not optional for
the passenger, passenger have to select the FQTV
program within the above shown popup window.
•
The program can be selected for the airlines own FQTV
airlines.
•
Popup window will close after FQTV program selection
and FQTV manual input screen is executed.
•
The popup is not displayed if only one FQTV program is
configured for the handled airline.
•
User Timeout
•
•
•
•
After selection of the FQTV program the application
checks the configuration for selected FQTV program and
continues with the manual FQTV number input.
•
Closing the popup returns to the Central Screen.
•
•
Configuration items
Post-Conditions
Error-Conditions
© 2012
MATERNA GmbH
72
1.17.2
Manual FQTV Number Input
Picture 39
The manual
FQTV number
input screen
© 2012
Items
Specification
Pre-Conditions
•
Passenger has selected an FQTV program from the
FQTV program selection popup.
•
The application checks the configuration for selected
FQTV program and limits the manual FQTV number
input according to the configured number length.
•
FQTV number can be input manually. The number can
be given for the airlines own FQTV program as well as
for FQTV programs of partner airlines.
•
If configured for numeric input only, the GUI disables the
alpha keyboard from user input.
•
The GUI displays the FQTV program name and the
FQTV program logo for passenger information.
•
•
MATERNA GmbH
73
Items
Specification
Configuration items
Post-Conditions
Error-Conditions
© 2012
•
Using the Continue button the FQTV program code and
number will be registered on MACS for the passenger
selected in the Central Screen.
•
Touching the Back button the application switches back
to the Central screen.
•
User Timeout
•
partner.
•
FQTV program logos.
•
•
•
After using the Continue button the FQTV program code
and number have been registered on MACS for the
passenger selected in the Central Screen.
•
Application returns to the Central Screen.
•
A user timeout as well as using the Exit button will
terminate the check-in process and will put the
application into AVAILABLE state.
•
•
MATERNA GmbH
74
1.18
Passenger Help Popup
Picture 40
Popup displaying
help information
for the passenger
Items
Specification
Pre-Conditions
•
The GUI enables the Help button when a help text for a
certain screen is configured.
•
Whenever the Help button is enabled for a screen the
passenger can get context related help.
•
Pressing the Help button displays the help popup window
showing context sensitive help information for the
passenger.
•
Touching the Close button hides the popup window and
the GUI displays the screen from which the help popup
was activated.
•
User Timeout from underlying screen
•
Help text per screen and language.
•
Activating the help popup doesn’t change the applications state and therefore always returns to the underlying
screen.
Configuration items
Post-Conditions
© 2012
MATERNA GmbH
75
Items
Error-Conditions
© 2012
Specification
•
A user timeout and the use of the Close button will terminate the help popup and the application returns to the
underlying screen.
•
•
MATERNA GmbH
76
1.19
User Timeout Popup
Picture 41
Popup displaying
timeout information for the passenger
Items
Specification
Pre-Conditions
•
The GUI receives a timeout value for each displayed
screen as described in chapter 3.1 Application Timeouts.
•
Touching the Continue button hides the popup window
and the GUI displays the screen from which the timeout
popup was activated.
Configuration items
•
Timeout values per screen as described in chapter 3.1
Application Timeouts.
Post-Conditions
•
Activating the timeout popup doesn’t change the applications state and therefore usually returns to the underlying
screen.
•
Exceptions from the default behavior are described in
chapter 3.1 Application Timeouts.
•
•
Error-Conditions
© 2012
MATERNA GmbH
77
1.20
Fatal Error Popup
Picture 42
Fatal Error screen
before check-in
process termination
© 2012
Items
Specification
Pre-Conditions
•
The application encountered an error situation from
which it cannot continue the check-in process.
•
Touching the Abort button closes the currently displayed
popup window and terminates the check-in session.
Configuration items
•
Timeout values per screen as described in chapter 3.1
Application Timeouts.
Post-Conditions
•
Currently active check-in session is closed and the
CUSS application goes into AVAILABLE state.
Error-Conditions
•
•
MATERNA GmbH
78
2
System Architecture
2.1
Physical Architecture
Last modified: 28.06.2012 16:05:24
Description of hardware components and their relations making up the environment
for the dnata Check-in business logic, its configuration and administration.
Picture 43
cmp Server Hardware Components
DXB Site 1
Server Hardware
Components
DXB Backup Site
MACS DCS
Serv er Spec:
Application
configuration requires
approx. 10 GB
«use»
•
•
•
2.26 GHz Intel Xeon QuadCore
32 GB Memory
500 GB HDD
«use»
Softw are Spec:
Business Logic Serv er
(Primary)
{1..*}
Database Serv er (mySQL)
{1..*}
Business Logic Serv er
(Backup)
{1..*}
•
•
•
•
LINUX
Tomcat: 7.0.26
Axis2: 1.5.1
Java SE: 1.6.0_26-b03
Serv er Spec:
«trace»
•
•
•
«trace»
8 GB Memory
500 GB HDD
Softw are Spec:
•
Administraion Serv er
MySQL enterprise 5.5
Load Balancer
Load Balancing (Global Site Selector?)
•
•
«trace»
SOAP Header and Session ID
No session hopping
«HT TPS»
Storage (1000 GB)
Serv er Spec:
•
•
•
Kiosk Clients
{1..100}
Softw are Spec:
•
•
•
•
•
2.1.1
4 GB Memory
500 GB HDD
MS Windows Server 2008
RDP for access from
DTM/Materna
Tomcat: 7.0.26
Axis2: 1.5.1
Java SE: 1.6.0_26-b03
MACS DCS
Status: Proposed - Phase: 1.0 - Last modified: 28.06.2012 15:35:58 - Type
© 2012
MATERNA GmbH
79
Is the MACS Departure Control System operated by dnata.
2.1.2
Business Logic Server (Primary)
The primary business logic server hosts and executes the CI applications business
logic and the GCI that builds the interface to the MACS DCS.
2.1.3
Business Logic Server (Backup)
The backup business logic server hosts and executes the CI applications business
logic (BL) and the GCI that builds the interface to the MACS DCS.
In case the primary server fails for any reason this backup server takes over the
execution of the business logic. In case of a take over, the actual executed BLs are
not continued, but need to be reestablished by the passenger.
2.1.4
Database Server (mySQL/ORACLE)
The database server holds the configuration for the check-in business logic as well as
for the graphical user interface (e.g. instruction texts) on the kiosk clients.
The configuration can be managed from the administration server using the IPS
AdminPortal.
2.1.5
Administration Server
Is the access point for certified staff to do administrative work. The administration
server also moves the trace- and log files from the business logic sever to an attached
storage.
Administrative work is carried out using the IPS AdminPortal software.
© 2012
MATERNA GmbH
80
2.1.6
Storage (1000 GB)
A storage holds all the trace- and log files that are moved from the BL servers to it.
The IPS AdminPortal allows searching for certain logs and traces by providing search
criteria like passenger names or PNRs and the like.
2.1.7
Load Balancer
A load balancer manages the IP addresses of the primary- and backup BL servers.
This way the kiosk clients need to be configured to access only one IP address.
If only two BL servers need to be managed the load balancer can also be
implemented through the simple provision of a virtual IP address. In this case real load
balancing doesn't take place, but the virtual IP address simply switches to the backup
server in case the primary server fails.
2.1.8
Kiosk Clients
CUSS kiosk clients allow passengers to carry out a check-in using the kiosk hardware
and the CUSS application.
© 2012
MATERNA GmbH
81
2.2
Logical-, Information- and Conceptual Architecture
This chapter describes the architecture of the application based on its component
definitions and the logical layer in which these components reside.
Picture 44
Application software components
and -layers
2.2.1
Action Provider
«interface»
The business process uses the actionProvider-Interface to communicate to the
different frontends.
© 2012
MATERNA GmbH
82
2.2.2
Business Logic
The business logic of the application executing the application according to the
defined business rules of the customer.
The process is defined using UML state charts. These state charts are used as input
for an SCXML state chart generator.
The resulting state charts are parsed by the business logic workflow engine, so that
changes in the documentation may directly affect applications functionality.
2.2.3
Business Rules
JBOSS Rule Engine processing the compiled rules from the repository.
2.2.4
Configuration
The configuration management is provided through WEB service implementations
allowing a sophisticated management of configuration parameters and also simple
configuration queries, as usually done from an application.
Basically the configuration options can be assigned into separate domains:
2.2.4.1
•
process configuration options
•
operational configuration options
•
customization options
Process configuration options
These are options that control parameters of the business process, such as
•
© 2012
timeouts
MATERNA GmbH
83
•
supported languages
•
screen texts
•
list of allowed carriers
•
etc.
These parameters are accessible via the configuration management tool and may
typically be changed by the customer.
2.2.4.2
Operational configuration options
These are options that control internal parameters, such as
•
addresses/URLs of service implementations
•
mapping of used implementation classes
•
mapping of used business rule sets
•
address of used business logic state chart
•
etc.
These options are partly accessible through the configuration management tool (but
with limited access rights), and are partly defined in configuration files that are part of
specific deployment modules (e.g. state charts).
2.2.4.3
Customization options
These are options that define the basic application behavior, such as
•
business logic work flow (state chart)
•
business rules (rule set files)
•
GUI design (style sheets)
These options are controlled in configuration files that are generated as part of the
build process and are directly contained in the deployment modules.
© 2012
MATERNA GmbH
84
2.2.5
DCS (MACS)
The Departure Control System hosting several airlines as
2.2.6
•
Emirates (EK)
•
Sri Lankan (UL)
•
Garuda Indonesia (GA)
•
Air Algerie (AH)
•
Kuwait Airways (KU)
•
...
Kiosk Application
Kiosk Application is a standard platform adapter for Materna CUSS applications
allowing access to CUSS platforms.
The Kiosk Application is certified for CUSS platforms of
2.2.7
•
IBM,
•
IER,
•
SITA and
•
ARINC
Kiosk GUI
Flash based kiosk GUI for CUSS kiosk applications.
© 2012
MATERNA GmbH
85
2.2.8
Mobile GUI (optional)
HTML based GUI for Mobile phone check-in applications.
2.2.9
WEB GUI (optional)
HTML based GUI for WEB check-in applications.
2.2.10
TIMATIC
IATA Timatic is the industry standard used by airlines and travel agents to be
compliant with border control rules and regulations. Timatic delivers personalized
information based on the passenger's destination, transit points, nationality, travel
document, residence country etc.
2.2.11
ATLAS
A WEB service providing geographical data for countries, areas, airports, 3-letter code
conversation and address completion.
2.2.12
Configuration
Almost all components use the configuration server to query configuration items
necessary to execute the business logic process.
© 2012
MATERNA GmbH
86
2.2.13
DocGen
The IPS document generator creates the required user documents as WEB- and kiosk
boarding passes, baggage tags and also vouchers. Documents are generated based
on document templates.
2.2.14
GCI
The Generic Check-in Interface (GCI) is a common language facility mapping dataand data structure provided by various Departure Control Systems to data structures
internally used by Materna IPS.
2.2.15
MediaScan
The IPS Media Scanner validates data from passenger provided documents like
scanned data from 2D bar coded documents or an MRZ of a presented passport.
2.3
Application Features
Characteristic
Sub-characteristic
Comments
Functionality
Suitability
Application is designed and
implemented after customer
attended workshops and thorough
specification.
Accuracy
Interoperability
Security
Functionality Compliance
Reliability
Maturity
Fault Tolerance
Application is interoperable and
certified for the most important
CUSS platforms.
The application for other customers
checks in approx. 80.000
passengers per day.
Recoverability
Reliability Compliance
Usability
© 2012
Understandability
MATERNA GmbH
Application comes with a graphical
87
Characteristic
Sub-characteristic
Comments
Learnability
dnata branded and easy to use user
touch interface.
Operability
Attractiveness
Usability Compliance
Efficiency
Time Behaviour
Resource Utilisation
Efficiency Compliance
Maintainability
Analysability
Changeability
Stability
A single passenger shall be able to
check-in within 30 seconds.
the application is designed and
specified to handle any number of
airline brands within a single
application instance.
Application can be enhanced easily
and quickly due to its multitier architecture and usage of frameworks
and several distinct WEB services.
The business logic layer is clearly
separated from the presentationMaintainability Compliance
and data layers.
Testability
Adaptability
Variability
Installability
Co-existence
Replaceability
Adaptability Compliance
2.4
The applications business process
can be widely configured and adapted using the JBOSS Drools
environment.
Application will be installed using
certain proven installation scripts for
kiosk- and server installation.
Technologies
Domain
Technology
Comment
Implementation
Kiosk:
The application and the
interface to the DCS will be
implemented using these
technologies
•
Java 1.5
•
Axis2 1.4.1
Server:
Presentation
© 2012
•
Java 1.6
•
Axis2 1.5.1
•
Drools 5.3.0
•
Adobe Flash >= 10.0
•
Flash Builder 4.5.1
MATERNA GmbH
For CUSS application
88
Communication
CORBA in Java 1.4.1
For CUSS interface layer
access
HTTP / HTTPS 3.0.1
Kiosk part of the application
communicates with the business logic on the server using
these basic protocols.
(LAN/WAN)
SOAP in axis 2
(LAN/WAN protocol)
Database Access
JDBC
•
Oracle 10.2.0.3.0
•
MySql 5.1.13
Structured data is transmitted
using the SOAP protocol via
HTTP/HTTPS.
The application and the
interface to the DCS will be
implemented using this
technology.
Servlet Container
Apache Tomcat 7.0.26
The applications business
logic is executed within the
Tomcat Servlet container
CORBA ORB
JacORB 2.3.1
Kiosk part of the application
uses free available JacORB to
communicate with CUSS
platforms.
Relational Database
mySQL 5.5
The application shall uses
mySQL for its configuration.
dnata is responsible for
necessary licensing.
Java Virtual Machine
Sun JDK / JRE
(Versions as above)
Monitoring
JMX
The applications business
logic needs a JAVA runtime
environment for execution.
For server side monitoring.
(Version as JRE)
SNMP V2
© 2012
MATERNA GmbH
For platform and hardware
monitoring on the kiosk.
89
3
Miscellaneous/To be Completed
3.1
Application Timeouts
This description outlines the configuration and usage of the application timeouts for
the dnata check-in application (CI application). For every self service application it is
essential to implement and configure application timeouts in such a way that these
timeouts are easily to understand and support the overall usability.
3.1.1
Warnings and Timeouts (Business Logic)
The dnata CI application supports two types of timeout values used to control timeouts
and the information display on the users screen.
The warning-time defines the time until a warning pop-up is displayed on the screen
to inform the user to continue within the applications workflow. - Whereas the timeout
value defines the time until the application continues handling the timeout (eg. performing a clean-up process).
Both configuration values are defined in seconds and can be changed using the
administration portal.
Picture 45
Example for the
configuration
node
business.default
The configuration items can be found in the configuration node e.g. “business.default”
in the configuration paths:
© 2012
MATERNA GmbH
90
•
mips.server.bl.process.warningTimes
•
mips.server.bl.process.timeouts
These configuration values are used by the business logic in the following way:
•
Nbr. of seconds until popup is displayed: <warningTime>
•
Nbr. of seconds the popup is displayed: <timeout> – <warningTime>
•
Nbr. of seconds until application reacts to the timeout: <timeout>
The following table holds the list of all screen identifiers with their respective default
timeout configurations.
Screen Identifier
3.1.2
warningTime
timeout
error.fatal
0
30
goodbye.kiosk
0
15
identify.kiosk.enterIdData
0
60
identify.screensaver
20
30
modify.display
50
60
print.kiosk.printDocs
20
30
to be completed…
20
30
General Agreements
Several situations can be identified where the same or at least similar timeout
handling can be defined for the application:
Action/Condition
Application Mode/ Behaviour
1. Timeout occurs
within the
identification
process
•
SAM: Application returns to the
ScreenSaver
•
SAM: Application returns to
identification/language selection screen if
a screensaver is not configured.
•
MAM: Application switches to AVAILABLE
(includes initial
language
selection)
© 2012
MATERNA GmbH
Display
Popup?
All No
91
Action/Condition
Application Mode/ Behaviour
Display
Popup?
and therefore back to the CUSS CLA.
2. After
identification
identification/language selection screen.
•
3. Help popup is
displayed
•
Application returns to the underlying
screen.
Yes
4. Language
Selection popup
is displayed
•
Application returns to the underlying
screen.
Yes
5. Goodbye screen
is displayed
•
identification/language selection screen.
All No
•
(e.g. select
flight/select
passenger)
© 2012
All Yes
•
MATERNA GmbH
92
3.2
Passenger Check-in
Option
Description
Advance Passenger
information (APIS)
•
Frequent Flyer Mileage
© 2012
The application supports the following APIS
methods:
o
Standard/MRZ (definition?)
o
German / MRZ & Visa Number/Issuance
(definition?)
o
US MRZ/+++(definition?)
o
Umrah: For certain destinations the application asks the passenger if he’s performing
Umrah. The passengers answer (YES/NO)
is stored in the PCR on MACS. (indication
from MACS!!!)
•
For German APIS the TIMATIC interface will be
used. Usage of the TIMATIC interface can be
switched on/off per configuration.
•
TIMATIC user id and password are configurable per
airline.
•
Passengers are given 2 attempts to scan the MRZ
on their passports. (configurable? -> ask dev!)
•
After the 2 attempt failed, the passenger is
requested to visit a staffed counter.
•
Application also allows for manual input of passport
data. This option is configurable per airline. Default
configuration is ‘switched off’.
•
Application scans images of passports and visas
and stores these images on a specific server (dnata
provides interface?) – Configuration options:
nd
o
Store image (yes/no)
o
Send API (yes/no/default = DCS request)
•
Application also supports reading of national ID
cards of GCC residents (??? – similar concept as for
passports)
•
Supported FQTV programs are configurable per
handled airline. (program codes, minimum and
maximum alphanumeric number input, screen
keyboard layout).
•
Application handles the airlines own FQTV program
as well as the FQTV programs of the airlines partner
programs.
•
FQTV numbers can be added by inserting the
appropriate FQTV card into the card reader, or by
MATERNA GmbH
93
Option
Description
selecting an FQTV program from a configurable list
and typing in the FQTV number manually.
•
The length of the FQTV number can be defined in
the applications configuration.
•
If there’s no configuration for an FQTV program the
application hides the FQTV button from the
modification screen and displays an alternate
instruction.
•
The application allows selecting a seat from a user
friendly seat map display on the screen. The seat
map display follows the data provided by MACS.
•
Seat selection can be done for each individual
passenger in a passenger group.
•
Seat selection is allowed for the current flight as well
as for connecting flights if the passenger is checkedin on the onward flights.
•
A 2D bar coded boarding pass will be printed for
each passenger who has been successfully
checked-in.
•
Boarding passes will be printed for the current flight
segment as well as for all connecting flight
segments.
•
The symbology for the 2D bar code will be PDF417.
•
The paper format of the boarding pass will be ATB1.
•
The application uses server based templates to
generate an AEA data stream from the MACS
provided boarding pass data (XML formatted).
Baggage DropOff Info
•
Baggage Drop-Off information is configurable per
handled airline and origin.
Baggage Tag Printing
•
Baggage tag printing is configurable per handled
airline.
•
Baggage Tag PECTAB can be configured per airline
and origin.
•
Baggage tags will be printed for each passenger
having requested baggage tags and who has been
successfully checked-in.
•
Baggage tags will not have any weight indication or
will be issued with a standard weight. MACS
provides information on baggage. - The weight
option is configurable per airline and per class.
•
The paper format of the baggage tags will be
according to the CUSS definitions (21 inch) or 20
Seat selection/change
Boarding Pass printing
© 2012
MATERNA GmbH
94
Option
Description
inch dnata specifications.
Gate Comment
Reports/Statistics
3.3
•
The application uses server based templates to
generate an AEA data stream from the MACS
provided baggage tag data (XML formatted).
•
Gate comments are configurable per handled airline
(on/off)
•
Exceptions to the above rule can be configured for
specific flights.
•
A comment will be added for each passenger after a
successful new check-in.
•
dnata provides the content.
•
The application provides detailed check-in data on
each passenger in XML format to be processed and
stored by other applications and tools.
•
Materna provides a description of the format and
data elements in the following XSD file [DOCREF].
•
Billing data in XML format is provided by the
MATERAN CUSS platform.
Branding
Option
Requirement Description
Languages
•
English
•
Arabic
Materna provides a set of English
texts used by the application in
FLASH HTML format.
dnata can change and translate the
provided basic texts due to its needs.
The default language can be
set via configuration.
Further languages can be
added via
configuration.
Screen Item Colors
TBD
Can be changed
via FLASH
compiled style
sheets.
User Animations
Materna provides a basic set of
generic animations in blue color for
Almex Express Check-in Kiosks.
Animations and
file names can
be configured
via configuration
Provided animations:
•
© 2012
Configuration
Reading 2DBC documents
MATERNA GmbH
95
Option
•
Reading Identity Card and
Passport
•
Reading Magnetic Cards
•
Printing Boarding Pass
Configuration
Animations are in FLV format.
FQTV Programs
TBD
TBD: Use
different FQTVs
depending on
handled airline.
Document Formats
The application prints boarding
passes in ATB1 format.
TBD:
Templates?
Boarding passes will be created by
the application itself based on data
collected through the check-in
process.
The layout of the boarding passes will
be defined through templates stored
in the applications configuration on
the server.
3.4
Common Use - CUSS
© 2012
Option
CUSS Version Support
•
Version 1.0: NOT Compliant
•
Version 1.1: Compliant
•
•
SITA Certified
Certified on SITA CUSS platform,
Version:
ARINC Certified
Certified on ARINC CUSS platform,
Version:
ARINC/IBM Certified
Certified on ARINC/IBM CUSS
platform, Version:
IER Certified
Certified on IER CUSS platform,
Version:
IBM Certified
Certified on IBM CUSS platform,
Version:
NCR Certified
NOT Certified
MATERNA GmbH
Configuration
Differentiation
via platform
provided
information.
96
Option
CUSS Devices/Interfaces
•
Passport Reader
•
Barcode Reader
•
Magnetic Card Reader
•
General Purpose Printer
•
Baggage Tag Printer
•
Standalone Scale
•
Conveyor
•
FOID Interface
•
Payment Interface
CUSS Payment
3.5
Configuration
As per device
availability and
information from
the platform.
Certain devices
can be switched
off via configuration.
Not in scope
Clients
3.6
Option
WEB Browser
Not in scope
CUSS Kiosks
The application can be installed and
operated on CUSS kiosks and CUSS
platforms under the conditions specified in Chapter 3.4 Common Use CUSS.
Mobile/Smart Phone
Not in scope
Table PC
Not in scope
Counter CI
Not in scope
Configuration
Configuration
may be necessary depending
on installation.
Application Hosting
3.7
Option
Materna Operation Centre
Not in scope
Customer Site Hosting
The applications business logic, its
configuration and the administration
portal will be hosted in dnata’s
operation centre in Dubai.
Configuration
DCS Systems Support
© 2012
MATERNA GmbH
97
3.7.1
Direct DCS Connection
3.7.2
Option
MACS
TBD
Configuration
DCS Connection via Service Provider
Option
Configuration
Not in scope
© 2012
MATERNA GmbH
98
4
Contact Information
Company
Person
Function
MATERNA
Andreas Gehling
Product
Manager
Vosskuhle 37
44141 Dortmund
MATERNA
Phone:
+49 (231) 55 99 351
Mobile:
+49 (157) 011 20 351
E-Mail:
[email protected]
Achim Schmidt
Vosskuhle 37
Key
Account
Manager
44141 Dortmund
© 2012
Phone:
+49 231 55 99 8830
Mobile:
+49 157 011 28 830
E-Mail:
[email protected]
MATERNA GmbH
99
Simplify!

IPS CI-Application Specification.DNATA-1.3.0

Transcription

Similar documents

How the Customer Experience Can Impac

www.Hyslimo.com

KINGSMILL, LONDON NW8 £750,000

luxury transportation

PDF

Untitled - TriaGnoSys

Great Western Railway pdf icon PDF, 1382 Kb

Passenger ship safety since 1912

charter services - Cherrey Bus Lines Inc.

2007 CADILLAC STS-V