Proposal

Amadeus Workstation Identifiers

DEV/AIR/CMD/AMD/PDM
V4.0
September 2009

Amadeus s.a.s
485, Route du Pin Montard-Les Bouillides
B.P. 69
06902 Sophia Antipolis - Cedex
France

Amadeus Confidential Information:

Unauthorized use and disclosure strictly forbidden
©2008 - Amadeus s.a.s - All Rights Reserved.
Revision History
Title: Airport Workstation Identifiers
Document type: Proposal
Authors: Sophie De Denaro, Benoit Lemarchand, Stephane Monbel, Joel
Cordesses, Roddom Gibbs
Version: 4.0
Date: September, 2009

Document History

Version Date Prepared Reviewed/ Comment

Approved
4.0 24SEP09 S. De Denaro - 3 new Controlling authorities added: 0SA
(TR 03087618), 0XI (WO 03367860), 1AU
(WO 03445061)
- The special character ‘/’, ‘-‘ and ‘_’ are
supported in the
UniqueIdentifierInControllingAuthority
(Structure 2)
- Location category ‘RAM’ for Ramp is
replaced by ‘RMP’ (PTR 03024252)
- The Site Type is not optional any longer but
mandatory now in full locations
3.9 09MAR09 S. De Denaro - 1 Controlling authority added: 0NC (WO
02759008)
3.8 24OCT08 S. De Denaro C. Lauribe - Updated with customer feedbacks received
on 10JUL08
- Location category ‘RAM’ for Ramp is
replaced by ‘RMP’
- Examples of command lines amended with
other parameters
- “provider” occurrences by “Controlling
Authority”
- 10 Controlling authorities added: 0VA, 0CC,
0FJ, 0IE, 0FQ, 0NF, 0OT, 0NC, 0LY, and 0TL
(WO 02954530, WO 02759008)
3.7 20JUN08 S. De Denaro - 1 Controlling authority added: 0CS for CUSS
- Full Location data terminology redefined
3.6 17SEP07 S. De Denaro Updated with cunstomer feedbacks received
on 10AUG07
3.5 01AUG07 S. De Denaro B. Lemarchand - Added 3 Controlling authorities: 1A, 0GT
J. Bruguier and 0TS
Y. Ginestet - Added 4 location categories: BMD, CRW,
MVC and TRN
- Location data description updated
3.4 29SEP06 B. Lemarchand Updated to include last customer feedbacks
3.3 17AUG06 J. Cordesses Full Location updates.
3.2 15JUN06 B. Lemarchand Updated following customers feedbacks.
3.1 8FEB06 B. Lemarchand Replaced _ by / as field separator.
3.0 6JAN06 B. Lemarchand P. Dor Finalized generic version.
 2.9 20DEC05 B. Lemarchand Changed controlling authority format to
reduce it to 3 characters and conform to
ASYD298.
2.8 14DEC05 J. Cordesses P. Dor Added reference to Full Location description
in Device Pooling Proposal.
2.7 01DEC05 B. Lemarchand P. Dor Added controlling authority as field of
workstation ID.
2.6 18NOV05 B. Lemarchand P. Dor Integrated feedbacks.
2.5 19OCT05 B. Lemarchand P. Dor Replaced “Print Emulator” occurrences by
“Application”. Added sentence clarifying
responsibility of provider in section 1.6.
2.4 17OCT05 J. Cordesses Misc updates to be in line with last Printing
solution.
2.2 05OCT05 S. Monbel Last clarification on field length in the WID +
Get back the complete list of full location set
on all the machines is required.
2.1 30SEP05 B. Lemarchand Detailed extraction of workstation ID
Added more details on workstation ID format
and made local identifier unique in airport.
2.0 16JUN05 Joel Cordesses Updates following feedback
1.6 24MAY05 Roddom Gibbs Final document
1.5 21MAY05 B. Lemarchand Extraction of Workstation ID rewritten
1.4 19MAY05 Joel Cordesses Definite proposal for Workstation ID
1.3 17MAY05 Roddom Gibbs Include feedback from Stephane Monbel,
Benoit Lemarchand and David Axelrod
1.2 16MAY05 Joel Cordesses Added : TID Dispenser requirements +
Document history
1.1 13MAY05 Roddom Gibbs Revised version
1.0 12MAY05 Roddom Gibbs Initial version

Related Documentation

Document Name Description

Altéa Physical Device Handling Solution High-level overview of the Amadeus Printing
(APDHS). Solution.
TID Dispenser Proposal Overview of the TID Dispenser and its
relationships with all actors involved in the
Amadeus PDH Solution
Table of Contents

1. Introduction ...........................................................................................................................3

2. TID Dispenser Requirements ................................................................................................3

2.1 TID Dispenser Definition.......................................................................................................3

2.2 Requirements.......................................................................................................................3
3. Workstation Identifier Description........................................................................................3

3.1 Workstation Identifier Structure 1..........................................................................................3

3.2 Workstation Identifier Structure 2..........................................................................................3
3.3 Description of Workstation Identifier Fields ...........................................................................3
4. Deployment Phase.................................................................................................................3

5. Extraction of Workstation Identifier......................................................................................3

5.1 Command Line Structure 1...................................................................................................3

5.2 Command Line Structure 2...................................................................................................3
5.3 Command Line Examples ....................................................................................................3
6. Annexes .................................................................................................................................3

6.1 Data Format.........................................................................................................................3

6.2 Full Location – Complementary information..........................................................................3
1. Introduction
The applications using the Amadeus Physical Device Handling solution (Altéa DC CM & FM systems,
Amadeus Print Emulator for example) require that each workstation has a unique identifier for the
following purposes:

1. To facilitate the dispensing of Terminal Identifiers (TIDs), used as addresses to target

printers.
Requirement: Each workstation to have unique ID.

2. To identify the location of the device.

Requirement: Each workstation to have an Airport or City Code, a Terminal or a Building
Code, Category, Index as described in section 3 below.

2. TID Dispenser Requirements

2.1 TID Dispenser Definition

The TID Dispenser is part of the Amadeus Device Server. Upon request of the Application, the TID
dispenser allocates and sends TIDs. Upon request of the Amadeus Document Server, the TID
dispenser sends device configurations.

2.2 Requirements
The TID Dispenser requires that each workstation benefits of a unique Identifier and location
information.

The Workstation Identifier, including the unique identifier and the physical location, are read on the
workstation by the Application, and then provided to the TID Dispenser (see complete flows in the TID
Dispenser Proposal for further information)

The Workstation Identifier and physical location are used by LSS and TID Dispenser:
To retrieve the Office ID of the workstation.
To retrieve the Configuration of the workstation in fixed TID devices
To create/retrieve/update the configuration of the workstation (auto-registered devices)
To administrate sets of devices.

The TID Dispenser requires:

The Identifier of each workstation to be unique in the world per organization.
The Full Location to be available on each workstation.
These two requirements are part of the Workstation Identifier (unique Id + full location) solution.
Deploying the Workstation Identifier on each workstation will thus provide the two required
information.
3. Workstation Identifier Description
The Amadeus Workstation Identifier can follow 2 distinct structures:
Either, the Workstation Identifier is composed of the following fields:
- the Controlling Authority
- the Full Location data
- and the LocalIdentifier
Or, the Workstation Identifier is made of 2 fields:
- the Controlling Authority
- and UniqueIdentifierInControllingAuthority

The proposed structures impose no constraint between airlines. As a consequence, two airlines may
use identical workstation identifiers.

Both structures fulfill the two requirements from the TID Dispenser:
The workstation Identifier is unique in the world for a given airline.
The Full Location (Location Type + Location Code + Site Type + Site Code + Location
Category Code + Location Category Index) is provided to the TID Dispenser in both
structures:
o Either it can be extracted from the workstation identifier by the Application in the first
structure. Refer to the chapter Extraction of Workstation Identifier for further
information about the extraction.
o Or it is provided as an independent field with the Workstation Identifier defined with
the second structure.

Note:
The structure of Workstation Identifiers is not checked in the Amadeus Physical Handling Solution.
This document only provides some recommendations with the definitions of these identifiers at
deployment time.
However, it is important to respect the various rules to define full locations in both structures below as
these data will be used and checked by the TID Dispenser at workstation and device registration time.

3.1 Workstation Identifier Structure 1

This structure is defined as follows:
ControllingAuthority/LocationType/LocationCode/SiteType/SiteCode/LocationCategoryCode/Location
CategoryIndex/LocalIdentifier

“/” is used as separator between the fields.

Location data inside the Workstation Identifier follow the structure of the Full Location described in the
TID Dispenser Proposal.

Examples:
The Workstation Identifier “XS/A/SYD/T/1/GTE/1/3” refers to a workstation in SYD airport at terminal 1
on Gate 1.

Case of Airports
Multi terminals Mono terminals

XS/A/SYD/T/1/GTE/1/1 0RE/A/NOU/T//GTE/1/1
XS/A/SYD/T/1/GTE//1 0RE/A/NOU/T//GTE//1
XS/A/SYD/T/1///1 0RE/A/NOU/T////1

Case of Cities

Buildings No buildings

XS/C/SYD/B/QA///1 XS/C/SYD/////1
XS/C/SYD/B/QA/ADM/1/1 XS/C/SYD///ADM/1/1
XS/C/SYD/B/QA/ADM//1 XS/C/SYD///ADM//1

3.2 Workstation Identifier Structure 2

This structure is defined as follows:
ControllingAuthority/UniqueIdentifierInControllingAuthority

With this structure, the Workstation Identifier and the Full Location are provided as two different
pieces of information:
The Workstation Identifier must then conform to the above format
The Full Location must follow the following format which is also described in the TID
Dispenser Proposal:
LocationType/LocationCode/SiteType/SiteCode/LocationCategoryCode/LocationCategoryIndex

3.3 Description of Workstation Identifier Fields

Controlling Authority
Controlling authority is used in both Workstation Identifier structures.

A controlling authority represents the platform name. It is the name of entity responsible to allocate
workstation ID coded on up to 3 alphanumeric characters (special characters excluded, from A-Z and
0-9).
Amadeus will allocate names to be used by each controlling authority to ensure uniqueness of
workstation ID. When possible IATA code on 2 characters will be used to identify platforms else
Amadeus will allocate a three characters code beginning by 0.
Following names are expected to be used until now:
• XS for SITA
• XA for ARINC
• 0RE for RESA
• QF for TELSTRA
• 0XM for AAE
• 0CA for CAMPUS
• 0CC for Macair native platforms
 • 0CS for CUSS
• 0FJ for Air Pacific native platforms
• 0FQ for Brindabella Airlines native platforms
• 0IE for Solomon Airlines native platforms
• 0LY for EL AL native platforms
• 0NC for National Jet native platforms
• 0NF for Air Vanuatu native platforms
• 0UL for ULTRA
• 0GT for Global Telesign
• 0OT for Aeropelican native platforms
• 0SA for South African Airways native platforms
• 0TL for Airnorth native platforms
• 0TS for T-Systems
• 0VA for V Australia native platforms
• 0XI for AirIT
• 1A for Amadeus s.a.s.
• 1AU for Amadeus Reservation Desktops (using the ‘Automatic Update’ Amadeus tool)
Names not part of this list must be requested to Amadeus before being used (through Work Orders
opened to Product Definition Middleware team).

Format:
This field is implemented on up to 3 alphanumeric characters (from A-Z and 0-9).
State:
This field is mandatory.

Location Type
Location Type is part of the Workstation Identifier Structure 1.

A single-character (A/C) indicator of whether the position is located in an airport or not. (Examples of
non-airport locations are airline premises, 1A premises, SITA, Telstra, hotels, etc.).

Format:
Discriminator is implemented on 1 alphabetic character.
State:
This field is mandatory (cannot be empty).

Location Code
Location Code is part of the Workstation Identifier Structure 1.

If the previous discriminator is ‘A’, then LocationCode is the standard IATA code for airport.
Example: NCE, SYD, LHR, JFK.

If the previous discriminator is ‘C’, then LocationCode is the IATA 3-char code for the city
Example: LON, NYC, SYD. (Some airports have the same identifiers as the cities they are in, e.g.
SYD. That’s why an explicit discriminator is required.)

Format:
The Location Code is implemented on 3 alphabetic characters (from A-Z).
State:
The field is mandatory (cannot be empty).

Site Type
Site Type is part of the Workstation Identifier Structure 1.
A single-character (‘T’/’B’) indicator of whether the position is located in an airport terminal or in
another type of building.
Format:
The discriminator is implemented on 1 character.
State:
The discriminator is mandatory (cannot be empty).
Code ‘B’ must be used if the value of Location Type is ‘C’.
Code ‘T’ or ‘B’ can be used if the value of Location Type is ‘A’

Site Code
Site Code is part of the Workstation Identifier Structure 1.

If the previous discriminator is ‘T’, then SiteCode is the standard IATA code for terminal number.
Format: It is implemented on up to 2 alphanumeric characters.
Example: 2, 2A, D

If the previous discriminator is ‘B’, then SiteCode is the Amadeus proprietary code for the domain.
Format: It is implemented on up to 3 alphanumeric characters (special characters excluded).
Example: QA – Qantas centre building A.
State:
The code is conditional:
- If the previous discriminator is ‘T’, the code is optional: it is always empty if the airport
is mono-terminal and its terminal has no code.
- If the previous discriminator is ‘B’, the code is mandatory

Location Category Code

Location Category Code is part of the Workstation Identifier Structure 1.

LocationCategoryCode is the category code of the location of the workstation.

Format: It is implemented on 3 chars.

Here is the exhaustive list of possible categories:

 !  $  
 

 

 
! $   !     
&   &   

 
 
    


  
 

' 
 '    

(
)  !  "#$

!
   !    !
%
    !


  %  

& $
 

The interpretation of each category code is just given here as a rough guide. Category descriptions
are organization dependant. The creation of a new Location Category Code is done by the
organization upon requests (Work Order opened to Product Definition Middleware team).

State:
This field is optional.

Location Category Index

Location Category Index is part of the Workstation Identifier Structure 1.
LocationCategoryIndex is the index number of the location of the workstation.

Format: It is implemented on up to 5 alphanumeric characters (from A-Z and 0-9).

Example: 1, 2, 10 (Gate number), 12E (check-in counter).
State:
This field is conditional: It is optional when the Location Category Code is specified (not
empty). Otherwise, it is always empty.

LocalIdentifier
LocalIdentifier is part of the Workstation Identifier Structure 1.

LocalIdentifier is an identifier of the workstation. It makes the Workstation Identifiers different for
workstations located in the same location.
Format: It is implemented on up to 6 alphanumeric characters (from A-Z and 0-9).
State:
This field is mandatory.

UniqueIdentifierInControllingAuthority
UniqueIdentifierInControllingAuthority is part of the Workstation Identifier Structure 2.

UniqueIdentifierInControllingAuthority is an identifier that must be worldwide unique for the controlling

authority.
Format: It is implemented on up to 31 alphanumeric characters (from A-Z and 0-9). The special
character ‘/’, ‘-‘ and ‘_’ are also allowed.
State:
This field is mandatory.
4. Deployment Phase
The deployment of the Amadeus Workstation Identifiers is supported on the following platforms:
Sita
Arinc
Telstra
Resa
Ultra
Airline specific platforms

The Amadeus Workstation Id will be used by the Application instead of the existing proprietary
workstation identifiers.

5. Extraction of Workstation Identifier

Applications will thus use a start-up script that must provide the workstation ID on command line.
The exact specification of the command line depends on the structure of the workstation identifier
used:
Either the start-up script provides the workstation ID on command line when it is defined with
the Workstation Identifier Structure 1
Or the start-up script provides the workstation ID and the Full Location as two separate pieces
of information on command line when the workstation identifier is defined with the Workstation
Identifier Structure 2.

5.1 Command Line Structure 1

<Application start-up script> --workstationID=<Workstation ID> <Other parameters>

where
<Application start-up script> is the script used to launch the application.
<Workstation ID> is the workstation ID as defined in section 3.1 Workstation Identifier
Structure 1.
<Other parameters> are other potential command line parameters which are defined in the
application user guides. See these guides for further information about these other parameters
(application index, airline code, log directory, etc).

5.2 Command Line Structure 2

<Application start-up script> --workstationID=<Workstation ID> --fullLocation=<Full Location> <Other

parameters>

where
<Application start-up script> is the script used to launch the application.
<Workstation ID> is the workstation ID as defined in section 3.2 Workstation Identifier
Structure 2.
 <Full Location> is the representation of the full location as defined in the section 3.2
Workstation Identifier Structure 2.
<Other parameters> are other potential command line parameters which are defined in the
application user guides. See these guides for further information about these other parameters
(application index, airline code, log directory, etc).

5.3 Command Line Examples

The way the Workstation Identifier is stored on the workstation is dependant on the controlling
authority.
It is strictly under the responsibility of the controlling authority to give the workstation identifier on the
command line as described above.

Examples using Workstation Identifier Structure 1:

PELauncher --workstationID=QF/A/SYD/T/1/GTE/1/3
PELauncher --workstationID=XS/A/NCE/T/1/BMD/10/05
PELauncher --workstationID=XS/A/NCE/T/1/BMD/10/23

Examples using Workstation Identifier Structure 2:

PELauncher --workstationID=QF/WORKSTATION3SYDNEY –fullLocation=A/SYD/T/1/GTE/1
PELauncher --workstationID=XS/WORKSTATION2GATE23NICE –fullLocation=A/NCE/T/1/GTE/23
PELauncher --workstationID=XS/MYWORKSTATION –fullLocation=C/NCE/B/EA
PELauncher --workstationID=0RE/A/TLL/CHECKIN02 --fullLocation=A/TLL/T/1/CKI/2
6. Annexes

6.1 Data Format

This part contains the input and display format of all the fields used.

6.1.1 Data Convention

The conventions that are used to describe the information are detailed in the following table.

Name Name of the data type

Type Type of the data. Possible values are:
- Boolean
- Alphabetic
- Alphanumeric
- Numeric
State State of the data type:
- Mandatory
- Optional
- Conditional
Min Size Data that do not match the minimum size are invalid.
Max Size It is not possible for a data to exceed its maximum
size.
Example Examples of data
6.1.2 Data Description

Name Type State Min Max Example Description/Comments

size size
Controlling Alphanumeric Mandatory 1 3 XS Name of the entity
Authority (special responsible to allocate
characters workstation identifiers
excluded)
Local Identifier Alphanumeric Mandatory 1 6 002 Additional identifier used for
(special the location
characters
excluded)
Location Alphabetic Optional 1 3 GTE Location category
Category Code

Location Alphanumeric Conditional: 1 5 23 or 12E Location index: Index of the

Category Index (special - Optional when location category.
characters the Category is
excluded) specified
- Empty
otherwise
Location Type Alphabetic Mandatory 1 1 A or C Accepted values:
- A for Airport
- C for City
Location Code Alphabetic Mandatory 3 3 LHR Airport code or city code

Site Code Alphanumeric Conditional: 1 2 ‘2’ or ‘2A’ Terminal codes

(special - Optional for or ‘D’
characters terminals
excluded) 1 3 ‘QA’ for Building codes
- Mandatory for Qantas
buildings Building A
Site Type Alphabetic Mandatory 1 1 T or B Accepted values:
- T for Terminal
- B for Building
Unique Alphanumeric Mandatory 1 31 This is an identifier that must
Identifier (special be worldwide unique for the
Controlling characters controlling authority.
Authority excluded but
‘/’, ‘-‘ and ‘_’
are allowed)
6.2 Full Location – Complementary Information
The Full Location corresponds to the physical location of the workstation and is defined by
several parameters: Location Type, Location Code, Site Type, Site code, Location Category Type
and Location Category Index.
Examples:
A / SYD / T / 1 / GTE / 20: Airport Sydney Terminal 1 Gate 20
A / FRA / T / 1 / CKI / 13: Airport Frankfurt Terminal 1 Check In 13
C / NCE / B / 1 / OFF / 9310: City Nice Building 1 Office 9310

 


   


  
 !"#$ %&&'$ ($&) *+, - *.,
 ./$ 01 2  !"#$3 & *+,4 5& 1 $/ &  + -#- ./$6
01 2  !"#$3 & *. ,4 5& 1 $/ &  ." ./$6
7 $ !"#$ . %&&'$ ($&) *! , - *8,
./)
9 01 5$  !"#$ & *+,4 5& 1 $/ & :/-" /
#&&'$ ($& -$ *! , - *8,6
; 01 5$  !"#$ & *.,4 5& 1 $/ & :/-" /
5$ <$ #&&'$ ($ & *8,6
7 $ ./$ . ./)
9 01 5$ 27$ !"#$3 & *! ,4 5& 1 $/ & # / &
 !$-: ./$6
9 01 5$ 27 $ !"#$3 & *8,4 5& 1 $/ & :/-" /
&  8/= ./$6
 .$=-" ./$ >
 .$=-" 0 /$? . ./)
9 01 5$ 2  .$=-"3 & #-$&$4 5& 1 $/ &
#6
9 >5$-@&$4 5& 1 $/ & (/6

Examples:
AB  

C D
  

+E!FE! !5$ -#- !F 5& " $ $-: 6$6 :9
$-: -#-  / 5& $-: 5&  /$6
+E%GHE!E  !5$ -#- %GH 5& " $ $-: 6$6 :9
$-: -#-  / 5& $-: 5&  /$6
+EI+JE 8E 
+EI+JE!E EK! G !5$ -#- 5& " $ $-: / " $
=$
+EI+JE!E EK! GE 
+E F.GE!E EK! GELM
.E F.GE 8EG+
.E F.GE 8EG+E!8N
.E F.GE 8EG+E!8NE 

OD
  

+EI+JE EL
+EI+J !5$ -#- 5&  /& '$@$$ $-:&

Amadeus Workstation Identifiers Page 15 of 16

 / '/=&
+EI+JE 8
+E!FE!E  !5$ -#- !F & :9$-: / & $-:
5&  /$6
+E!FE!E E E 
+E F.GE! !5$ -#- F.G & :9$-:6
+E%GHE! !5$ -#- %GH & :9$-: ' & $-:
5&  /$6
.E F.GE!
.E F.GE!E 
.E F.GE 8
+EI+JE E EK! G !5$ -#- 5&  /& '$@$$ $-:&
/ '/=& / 5& " $ =$
.E F.G

Amadeus Workstation Identifiers Page 16 of 16