Fuel Tender XML Implementation Guide

Aviation
Fuel Tender
XML Standard
Implementation Guide (v1.1)

International Air Transport Association (IATA) 2016. Page 1 of 35

1 Contents
1 Contents ......................................................................................................................................... 2
2 Introduction .................................................................................................................................... 4
2.1 Purpose and Scope of the Document ................................................................................ 4
2.2 Out of Scope Items ............................................................................................................... 4
2.3 Intended Audience ................................................................................................................ 4
3 Business requirement background ............................................................................................ 4
4 Old Fuel tendering process ......................................................................................................... 4
5 Why Implement the Fuel Tender XML Messages .................................................................... 5
6 Fuel Tender XML Messages ....................................................................................................... 6
7 Messaging Bi Lateral Agreements ............................................................................................. 7
8 Transfer protocols ......................................................................................................................... 7
9 Description of Elements ............................................................................................................... 7
9.1 Nil Values in Schema ........................................................................................................... 7
9.2 Char Encoding ...................................................................................................................... 7
9.3 Repeating Elements ............................................................................................................. 7
10 Date and Time Reference ....................................................................................................... 7
11 Message Types ......................................................................................................................... 8
12 Message Control ....................................................................................................................... 9
12.1 Fuel Tender Invitation .......................................................................................................... 9
12.2 Fuel Tender Bid .................................................................................................................... 9
12.3 Fuel Tender Cancel .............................................................................................................. 9
12.4 Fuel Tender Update ............................................................................................................. 9
12.5 Fuel Tender Bid Decline ...................................................................................................... 9
13 Data flows .................................................................................................................................. 9
13.1 Successful bid with one supplier ........................................................................................ 9
13.2 Successful bid with 2 suppliers and 1 round. Only 1 supplier moves to the second
round 10
13.3 Tender cancelled ................................................................................................................ 10
13.4 Tender update ..................................................................................................................... 11
13.5 Award for two suppliers ..................................................................................................... 11

13.6 Bids declined after two rounds .......................................................................................... 12

13.7 Tender cancel after one round .......................................................................................... 12
14 Use of Codesets ..................................................................................................................... 13
15 Business Information .............................................................................................................. 14
15.1 Bilateral Agreements .......................................................................................................... 14
16 Communication ....................................................................................................................... 14
17 Message Security Standards ................................................................................................ 14
18 Schema Validation .................................................................................................................. 14
19 Schema Management ............................................................................................................ 15
Appendix A Versioning methodology ........................................................................................... 16
Appendix B Schema Changes history .......................................................................................... 17
Appendix C .......................................................................................................................................... 18
Fuel Tender Invitation .................................................................................................................... 18
Fuel Tender Bid .............................................................................................................................. 20
Fuel Tender Update ....................................................................................................................... 25
Fuel Tender Bid Award .................................................................................................................. 28
Fuel Tender Bid Decline ................................................................................................................ 29
Fuel Tender Cancel ........................................................................................................................ 30
Fuel Tender Accept Award ............................................................................................................ 30
Fuel Tender New Round ............................................................................................................... 34
Fuel Tender Response .................................................................................................................. 35


2 Introduction
The Tender XML Standard was developed by the Aviation Fuel Tender XML Working Group, comprised
of airlines, fuel suppliers and IT vendors and was approved for industry adoption by the IATA
Commercial Fuel Group in May 2016. This implementation guide is intended to help those who plan
to use the Tender XML Standard with the essential information required when developing technical
solutions and guidance on the use of the messages. It also provides background information and how
best to use the standard effectively.
2.1 Purpose and Scope of the Document

This document contains the guidelines and procedures for the use of the Tender XML Standard
in the communications between airlines and suppliers.
2.2 Out of Scope Items

Packages are not supported.
2.3 Intended Audience

This document is intended to be used by all the companies that want to implement the Tender
XML Standard in their products.
3 Business requirement background

The airlines and their fuel suppliers since 2005 have been engaged in establishing and implementing
standards for the exchange of fuel activity related messages. IATA has facilitated these E-Fueling
processes and is committed to the development and maintenance of the fuel data exchange standards.
While the three standards required for order (pre-flight), delivery (transaction) and the invoice
standards are now in place a gap exists in the area of tender and bid forms. As a result currently,
airlines send their Fuel Tender RFPs in various formats via e-mail or through various different fuel
management systems. Offers are subsequently received from suppliers in various formats which then
have to be uploaded manually into spreadsheets or into different management systems. This not only
time consuming but leaves itself to human errors.
4 Old Fuel tendering process

The current fuel tendering process is manual and consequently inefficient. Some flaws include:

Fuel tender RFPs are done using various formats
Offers from suppliers are provided in various formats
Feeding the bid data into fuel management systems is manual, time consuming and prone to
errors
Lack of standardized and transparent pricing categories
Normalization of offers is prone to error and time consuming

The lack of standardized nomenclature that flows from bid to tender to contract to invoice
5 Why Implement the Fuel Tender XML Messages

XML enables simple processing of information to take place, and the task of ''parsing'' the information
(putting it into a form that is usable by the receiving device) is obsolete. Once a message is created in
XML, any device in an enterprise (or wider environment if the same information structure is adopted
extensively) can carry out their work simply, without having to reinterpret the message from scratch.
XML is also inherently protected against becoming obsolescent, because the structure allows for
extension, when new practices require new information to be carried.

6 Fuel Tender XML Messages

To accommodate the fuel tendering process with a digital information exchange standard, the manual
process (e.g. through email and phone calls) has been modelled as the following process flow diagram.

The following messages are in place to accommodate the process:
FuelTenderInvitation The tender invitation message from airline to supplier
FuelTenderBid- The bid response message from supplier to airline
FuelTenderUpdate Update the tender from airline to supplier
FuelTenderBidAward Award a bid from airline to supplier
FuelTenderBidDecline Decline a bid from airline to supplier
FuelTenderCancel Cancel a tender from airline to supplier
FuelTenderAcceptAward Accept award from supplier to airline
FuelTenderNewRound Notify a new round from airline to supplier

FuelTenderResponse Acceptance/rejection message response for synchronous calls
7 Messaging Bi Lateral Agreements

Each time the Fuel Tender data standard is used it is recommended and encouraged that the two
parties involved set up and use a bilateral agreement. The objective of the bilateral agreement is to
define the expectation the two parties have from the interface, in terms of data, performance,
protocol, etc. It will be an important tool when testing the implementation and in the maintenance of
the interface. It will enable those designing and implementing the interface to record how it operates
in this particular deployment.
The bilateral agreement does not replace the schema but can be used alongside, as part of or instead
of an Interface Control or Definition document.
It is suggested that a Confidentiality Agreement is also signed between the parties to protect each
others interests.
8 Transfer protocols
For the transfer of the XML documents there the SOAP protocol is one of the common options that can
be used. Other examples include the FTP (File Transfer Protocol) and HTTP (Hypertext Transfer
Protocol).
9 Description of Elements
Please refer to Appendix C for the complete list of data elements.
9.1 Nil Values in Schema

Nil values will always be interpreted as missing data in the schema.
9.2 Char Encoding

The encoding used is UTF-8.
9.3 Repeating Elements

Location
AirlinesVolume
ProductFee
Tax
TaxOnTax
10 Date and Time Reference

The dateTime data type is used to specify a date and a time.

The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where:
YYYY indicates the year

MM indicates the month
DD indicates the day
T indicates the start of the required time section
hh indicates the hour
mm indicates the minute
ss indicates the second
11 Message Types
FuelTenderInvitation The tender invitation message from airline to supplier
FuelTenderBid- The bid response message from supplier to airline
FuelTenderUpdate Update the tender from airline to supplier
FuelTenderBidAward Award a bid from airline to supplier
FuelTenderBidDecline Decline a bid from airline to supplier
FuelTenderCancel Cancel a tender from airline to supplier
FuelTenderAcceptAward Accept award from supplier to airline
FuelTenderNewRound Notify a new round from airline to supplier
FuelTenderResponse Acceptance/rejection message response for synchronous calls

All the messages are defined by the IATA Fuel Tender.xsd

12 Message Control
The Tender schema includes a message type (FuelTenderResponse) which can be used as part of an
overall mechanism to control the flow of messages, by implementing a request response sequence.
The use of these message type is optional, but their inclusion in the Tender schema gives implementers
the flexibility to specify a message control mechanism which best fits the characteristics of the systems
exchanging information.
12.1 Fuel Tender Invitation

A tender with the same identification is not accepted. A different version (Tender Version) for the same
tender needs to be submitted.
12.2 Fuel Tender Bid

A bid with the same identification is not accepted. A different version (Bid Version or
BidVersionSeqSync ) for the same tender needs to be submitted. The last version ordered by
BidVersionSeqSync is always considered.
12.3 Fuel Tender Cancel

It is only permitted if no location has been awarded.
12.4 Fuel Tender Update

It is only permitted if no location has been awarded.
12.5 Fuel Tender Bid Decline

It is permitted only if the bid was not awarded.
13 Data flows
Below are several simple use cases and the associated data flows and message types used. These
are meant as basic examples and are certainly not the only integration patterns possible.
13.1 Successful bid with one supplier

13.2 Successful bid with 2 suppliers and 1 round. Only 1 supplier moves to the second round

13.3 Tender cancelled

13.4 Tender update
13.5 Award for two suppliers

13.6 Bids declined after two rounds
13.7 Tender cancel after one round

14 Use of Codesets
When exchanging data with other parties, it is important to use a standard codeset to ensure each
party is referring to the same thing e.g.
Unit Type Code LT as a refers to Litres and KG refers to Kilograms

Customer Code AA refers to American Airlines and LH refers to Lufthansa
Aircraft Code 747 refers to a Boeing 747
Airport Code LHR refers to London Heathrow and LAX refers to Los Angeles International
Currency Code USD refers to US Dollars and NOK refers to Norwegian Krone
If such codeset references are not enforced, it can lead to a many issues between all parties exchanging
data using this method.
To ensure a particular set codes are used, this standard provides a default codeset. This codeset is
referred to in the schema and will ensure that there is no a match between what has been entered
into a specific field and the codeset, validation will fail.
The spreadsheet reference guide IATA Fuel Code Directory xxx.xlsx contains all codesets and can be
referenced to provide additional information about what each code means (as detailed above in the
bullet point list).
The Fuel Standards group has tried to cater for most eventualities in the codeset, so most of the data
requirements should be catered for. However, there may be situations where a particular customer
or supplier does not exist, or a new airport has been built, but it does not exist in the standard.
If this is the case, the Fuel Standards Group should be contacted with a request to add the code. The
group will be responsible for confirming that the code does not exist and if this is the case, adding it
and releasing an updated codeset (which will be referenced as a new version).

15 Business Information
15.1 Bilateral Agreements

Each time the Tender schema is used it is recommended and encouraged that the two parties involved
set up and use a bilateral agreement. The objective of the bilateral agreement is to define the
expectation the two parties have from the interface, in terms of data, performance, protocol, etc. It
will be an important tool when testing the implementation and in the maintenance of the Tender
interface. It will enable those designing and implementing the Tender interface to record how it
operates in this particular deployment. The bilateral agreement does not replace the schema but can
be used alongside, as part of or instead of an Interface Control or Definition document. Appendix B
sets out the topics that could be included in a bilateral agreement. The actual contents of the
agreement may differ for each implementation and will be defined and agreed by the two parties
implementing the Tender interface. It is suggested that a Confidentiality Agreement is also signed
between the parties to protect each others interests.
16 Communication
The Tender standard defines the message data content and high level message control in XML
schemas. It does not define the underlying communication protocols used to transport the message.
Selection of the communication protocol depends on the data exchange requirements such as:
Expected reliability
Guaranteed message delivery
Sensitivity to message duplication
Scalability
17 Message Security Standards

Different security measures can be incorporated in a data exchange. Each measure will cover a certain
security concern. Some of the security concerns that should be considered in a data exchange are:
Authenticity
Integrity
Availability
Confidentiality
Non repudiation
Message security is outside the scope of the Fuel Tender data standard, but should be agreed and
documented in the bilateral agreement between the interfacing parties.
18 Schema Validation
The messages is validated with attached IATA Fuel Tender.xsd

19 Schema Management
The management, maintenance, change requests, and development of the Fuel Tender XML standard
is governed by the Fuel Data Standards Working Group.

Appendix A Versioning methodology

The overall objective of the Group is to maintain the standard as stable as possible. Three categories
of changes can be implemented.

Each of them will require a different level of approval before they are implemented.

Changes to the schema:
Minor change: Changing a comment - will be at IATAs discretion
Medium change: Additions to the schema that are optional - will be agreed by the standards
group
Major change: Removing fields or making structural changes - will be agreed by the group

Fuel Code Directory:
Minor change: Adding a code to an existing list within the code directory will be done by IATA
following consultation with the relevant technical working groups.
Medium change: Adding a new code list to the directory - will be agreed by the standards
group
Major change: Removing a code and/or a code list from the directory -will be agreed by the
standards group

The fuel code directory versioning is independent from the versioning of the schemas using the fuel
code directory. Parties should change the SchemaLocation in the schema file defining the message
standard, since the filename of the Fuel Code Directory contains the version of the directory. No new
schema will be issued following a change of the Fuel Code Directory.

For each change or group of changes approved by the Group, the version of the standard will be
updated accordingly.

Version Convention:
Minor version changes - increase the second position after the dot (V1.0.X)
Medium version changes - increase the first position after the dot (V1.X.0)
Major version changes - change the first position before the dot (VX.0.1)

The Group recognizes the latest major version of the Standards and the previous major version of the
Standards. Only the most recent medium or minor versions of the latest and previous major versions
are supported. Only the most recent version of a standard is eligible for a schema change. For older
supported versions, only the documentation may be updated.


Appendix B Schema Changes history

Version Description of Change Author Date
0.1 Initial draft Stefan Casapu 16.10.2015

0.2 Review of the bid and index proposal Stefan Casapu 24.11.2016
0.3 Final solution to the index identification Stefan Casapu 22.04.2016
0.4 Merger of the shemas Stefan Casapu 05.07.2016
0.5 Contribution to the business aspects Shakti Chopra 20.07.2016
0.6 Contribution to the business aspects Lasantha Subasinghe 20.07.2016
0.7 Contribution to the business aspects Houman Goudarzi 20.07.2016
0.8 Revised proces flow diagram Casapu Stefan 09.07.2016
Expanded transfer protocols
Created data flow diagrams
Created section on bilateral agreements and
communication
0.9 Created section on use of codesets Mark Johnson 09.07.2016
1.0 Consolidation of contributions Houman Goudarzi 10.07.2016
1.1 Minor edits Casapu Stefan 11.08.2016
1.2 Minor edits Houman Goudarzi 17.08.2016


Appendix C
Fuel Tender Invitation

Level Element Description Validation Mandatory
0 FuelTenderInvitation Root Y
1 TenderHeader Y
2 TenderIdentification Identification of the tender Y
3 TenderCode Identifying code of tender, unique in Char[20] Y

combination with TenderHolderCode
3 TenderName Name of tender Char[100] N
3 TenderHolderCode ICAO code of airline Char[5] Y
3 TenderHolderName Name of tender holder company Char[100] N
3 TenderVersion Version of the tender Number Y
2 TenderType Type of the tender(Product or Service) Char[2] Y
2 TenderHolderContact Y
3 Contact Y
4 ContactPerson Name of contact person for tender Char[200] Y
4 Email E-Mail of contact person for tender Char[100] Y
4 Phone Work phone of contact person for tender Char[50] N
2 BiddingPeriod N
3 From Start of tender bidding period Date Y
3 To End of tender bidding period Date Y
2 Attention Additional person involved in tender Char[200] N
2 Comments Additional comments Char[4000] N
1 TenderLocations List of tender locations Y
2 TenderLocation Tender invitation for a location Y
3 LocationHeader Y
4 LocationCodeIATA IATA code of airports + IATA code of Char[3] N

OffAirportLocation
4 LocationCodeICAO ICAO code of airports Char[5] Y
4 AdHoc Flag that specified if the location is an Char[1] N

alternative landing location
3 AgreementPeriod Y
4 From Start of contract period Date Y
4 To End of contract period Date Y
3 AirlinesVolumes List of airlines included in tender Y
4 AirlinesVolume/TotalVolume Y

5 AirlineCode The airline for which the tender takes place Char[3] Y
at the current location
5 Volume Volume needed for the airline Number Y
5 UOM Unit in with the Char[3] Y
4 PeriodType Period of tender volume Char[1] N
3 ProductServices Product definition N
4 FuelProduct Code of fuel product Char[200] Y
4 TaxType Product tax type Char[3] N
4 FuelSpecification ASTM Standard Specification D1655 for Char[100] Y

Aviation Turbine Fuels Jet A /Jet A-1 latest
issue
4 IATAServiceLevel Requested IATA Service level 1 4 Char[1] N
4 DeliveryPoint Delivery point of fuel Char[3] Y
4 OperatingHours Range of operating hours Char[100] N
4 RefuelerCompanyCode Code of refueler company Char[5] N
4 TitleTransfer Point where the owner of the fuel changes Char[100] N

i.e at wing, at flange of the pipe
4 IndexConversion Y
5 Density Density of fuel Number N
5 DensityWeightUnit Density weight unit Char[3] N
5 DensityVolumeUnit Density volume unit Char[3] N
5 FromUnit From unit for conversion of index values Char[3] Y
5 ToUnit To unit for conversion of index values Char[3] Y
5 Operator Operator of conversion Y
5 Factor Conversion factor Number Y
3 Payment N
4 OpenInvoice Payment terms for open invoice contract
5 PaymentTerms Number of days between payment Number Y

reference date and payment
5 PaymentReferenceDateType Indicator of date to be used for as baseline Char[3] Y

for invoice due date calculation
5 InvoiceFrequency Frequency of invoices Char[4] Y
5 InvoiceType The type of invoice Char[10] N
4 Prepayment Payment terms for prepayment

5 NumberOfDaysPrepaid EXAMPLE: Prepayment on Friday for Number Y

deliveries on Sunday-Saturday; Number of
days prepaid: 7 (Sun - Sat)
5 PaymentFirstDeliveryDate Payment date vs first delivery date: 2 Number Y

(Friday to Sunday = 2 days)
5 PaymentFrequency same as invoice frequency for credit terms Char[4] Y

= prepayment
5 Amount Amount paid Number Y
4 PaymentCurrency IATA currency code Char[3] Y
4 PricingUnit IATA unit code Char[3] Y
4 MethodOfPayment Method of payment Char[2] N
4 GuaranteesDepositsRequired Indicator If any bank guarantees or money Char[1] N

deposits are requested.
4 ExchangeRate Y
5 FinancialSource Code of exchange rate financial source Char[20] Y
5 AverageingMethod Exchange rate averaging period code Char[4] Y
5 AveragingOffset Exchange rate offset code Char[3] Y
3 ProductPricing N
4 Index Product pricing in case pricing method is N

Index
5 IndexProvider Index provider code Char[20] Y
5 IndexProviderCode Index providers Internal index code Char[100] Y
5 AveragingMethod Index averaging method Char[4] Y
5 AveragingOffset Index averaging offset Char[3] Y
4 Market Product pricing in case pricing method is N

Market
5 Rate Product price rate Number Y
5 Currency Product price currency Char[3] Y
5 Unit Product price unit Char[3] Y
5 SourceType Source type of the product price Char[1] Y
5 SourceName Source name Char[200] N
Fuel Tender Bid

0 FuelTenderBid Root Y
1 BidTenderHeader Y


2 BidderCode IATA bidder code Char[3] Y
2 BidderName Bidder name Char[100] Y
2 BidderContact Y
3 Contact Y
1 Bids List of tender bids Y
2 Bid Bid description Y
3 BidIdentification Y
4 BiddingRound The round of negotiations Number Y
4 BidVersion The version of the bid Char[1] Y
4 BidVersionSeqSync Synchronization mark to determine the last Number Y

technical version of the bid
4 LocationHeader Y

OffAirportLocation

3 BidData Y
4 BidHeader The bid header Y
5 AgreementPeriod Y
5 BidValidityPeriod N
6 From The date of the offer Date N
6 To The end date for the offer Date N
5 BidVolumeMeasurement Volume measurement(Gross/Net) Char[2] N
5 PercentageOfTenderVolume The percentage of total volume covered Number N
5 VolumeTolerance The accepted tolerance Number N

5 BidderBidCode Internal code of the vendor Char[200] N
6 AirlineCode The airline for which the tender takes place at Char[3] Y
the current location
4 ProductServices Product definition Y

Aviation Turbine Fuels Jet A /Jet A-1 latest issue
5 TitleTransfer Point where the owner of the fuel changes i.e Char[100] N
at wing, at flange of the pipe
5 IndexConversion Y
4 Payment Y
6 PaymentTerms Number of days between payment reference Number Y

date and payment

6 PaymentReferenceDate Indicator of date to be used for as baseline for Char[3] Y

invoice due date calculation
6 NumberOfDaysPrepaid EXAMPLE: Prepayment on Friday for deliveries Number Y

on Sunday-Saturday; Number of days
prepaid: 7 (Sun - Sat)
6 PaymentFirstDeliveryDate Payment date vs first delivery date: 2 (Friday to Number Y

Sunday = 2 days)
6 PaymentFrequency same as invoice frequency for credit terms = Char[4] Y

prepayment

Values : Y, N
5 ExchangeRate Y
4 ProductPricing Y
5 Index Product pricing in case pricing method is Index Y
5 Market Product pricing in case pricing method is Y

Market
4 ProductsFees Y
5 ProductFee Y

6 SortID internal ID for price category to be referenced Number Y

by dependent Tax records
6 ItemProductID Product and Fee code Char[5] Y
6 Price Y
7 PricingUnitRateType Rate type Char[2] Y
7 PricingUnitRate Price of product or fee Number Y
7 PricingCurrencyCode Currency of price Char[3] Y
7 PricingUOM Unit of price Char[3] Y
6 ExchangeRate N
7 FinancialSource financial source of exchange rate Char[20] Y
7 AveragingPeriod Averaging Period Char[4] Y
7 AveragingOffset Averaging Offset Char[3] Y
6 Explanation Additional information Char[4000] N
6 Restrictions N
7 Scope Item to which the restriction/condition relates Char[2] Y
7 Operator Value of restriction/condition depending on Char[1] Y

the value in scope
7 Value1 Value of restriction/condition depending on Char[100] N

the value in scope

the value in scope
7 UOM Unit code in case restriction/condition refers to Char[3] N

a volume or time.
6 Taxes Container for taxes N
7 Tax Definition of tax N
8 SortID internal ID for tax component to be referenced Number Y

by dependent Tax on Tax records
8 TaxType Tax code Char[3] Y
8 TaxCategoryCode Tax Category Code Char[1] Y
8 Price Y
8 ExchangeRate N

8 TaxExemptible Some taxes must be charged, unless the airline Char[1] N

provides an exemption certificate. This item
indicates that a tax is potentially exemptible.
8 TaxOnTaxes Container for tax on taxes N
9 TaxOnTax Definition of tax on tax N
10 SortID internal ID for tax component to be referenced Number Y

by dependent Tax on Tax records
10 Price
10 ExchangeRate N
10 TaxExemptible Some taxes must be charged, unless the airline Char[1] N

provides an exemption certificate. This item
indicates that a tax is potentially exemptible.

Fuel Tender Update

0 FuelTenderUpdate Root Y
1 TenderHeaderUpdate Y

2 TenderHolderContact Y
3 Contact Y

2 BiddingPeriod N
1 TenderLocations List of tender locations Y
2 TenderLocation Tender invitation for a location Y
3 LocationHeader Y

OffAirportLocation

3 AgreementPeriod Contract Period Y
3 ProductServices Product definition N

issue
4 OperatingHours Range of operating hours Number N
4 TitleTransfer Point where the owner of the fuel changes i.e Char[100] N
at wing, at flange of the pipe

4 IndexConversion Y
3 Payment N
5 PaymentTerms Number of days between payment reference Number Y

date and payment
5 PaymentReferenceDate Indicator of date to be used for as baseline Char[3] Y


5 PaymentFirstDeliveryDate Payment date vs first delivery date: 2 (Friday Number Y

to Sunday = 2 days)

prepayment

Values : Y, N
4 ExchangeRate Y
3 ProductPricing N


Index

Market
Fuel Tender Bid Award

0 FuelTenderBidAward Root Y

1 AwardedBids Y
2 AwardedBid Y

4 LocationHeader Y

OffAirportLocation


3 AwardedVolume Y
4 PercentageOfTenderVolume Percentage covered by the bid from the Number Y

total volume in the tender
Fuel Tender Bid Decline

0 FuelTenderBidDecline Root Y
2 TenderCode Identifying code of tender, unique in combination with Char[20] Y

TenderHolderCode
1 DeclinedBids Y
2 DeclinedBid Y
4 BidVersionSeqSync Synchronization mark to determine the last technical Number Y

version of the bid
4 LocationHeader Y
5 LocationCodeIATA IATA code of airports + IATA code of OffAirportLocation Char[3] N
5 AdHoc Flag that specified if the location is an alternative Char[1] N

landing location

Fuel Tender Cancel

0 FuelTenderCancel Root Y
2 TenderCode Identifying code of tender, unique in combination Char[20] Y

with TenderHolderCode
Fuel Tender Accept Award

0 FuelTenderAcceptAward Root Y

1 AcceptedBids Y
2 AcceptedBid Y

4 LocationHeader Y

OffAirportLocation

3 BidData Y
4 BidHeader The bid header Y
5 AgreementPeriod Y

5 BidValidityPeriod N
6 From The date of the offer Date N
6 To The end date for the offer Date N
5 BidVolumeMeasurement Volume measurement(Gross/Net) Char[2] N
5 PercentageOfTenderVolume The percentage of total volume covered Number N
5 VolumeTolerance The accepted tolerance Number N
5 BidderBidCode Internal code of the vendor Char[200] N
4 ProductServices Product definition Y

issue
5 TitleTransfer Point where the owner of the fuel changes Char[100] N

i.e at wing, at flange of the pipe
5 IndexConversion Y

4 Payment Y
6 PaymentTerms Number of days between payment Number Y

reference date and payment
6 PaymentReferenceDate Indicator of date to be used for as baseline Char[3] Y


6 PaymentFirstDeliveryDate Payment date vs first delivery date: 2 (Friday Number Y

to Sunday = 2 days)

prepayment

Values : Y, N
5 ExchangeRate Y
4 ProductPricing N

Index

Market

4 ProductsFees Y
5 ProductFee Y
6 SortID internal ID for price category to be Number Y

referenced by dependent Tax records
6 ItemProductID Product and Fee code Char[5] Y
6 Price Y
6 ExchangeRate N
6 Explanation Additional information Char[4000] N
6 Restrictions N
7 Scope Item to which the restriction/condition Char[2] Y

relates
7 Operator Value of restriction/condition depending on Char[1] Y

the value in scope

the value in scope

the value in scope
7 UOM Unit code in case restriction/condition refers Char[3] N

to a volume or time.
6 Taxes Container for taxes N
7 Tax Definition of tax N
8 SortID internal ID for tax component to be Number Y

referenced by dependent Tax on Tax records
8 Price Y

8 ExchangeRate N
8 TaxExemptible Some taxes must be charged, unless the Char[1] N

airline provides an exemption certificate.
This item indicates that a tax is potentially
exemptible.
8 TaxOnTaxes Container for tax on taxes N
9 TaxOnTax Definition of tax on tax N
10 SortID internal ID for tax component to be Number Y

referenced by dependent Tax on Tax records
10 Price
10 ExchangeRate N
10 TaxExemptible Some taxes must be charged, unless the Char[1] N

airline provides an exemption certificate.
This item indicates that a tax is potentially
exemptible.

Fuel Tender New Round

0 FuelTenderNewRound Root Y
2 TenderCode Identifying code of tender, unique in combination Char[20] Y

with TenderHolderCode

2 BiddingRound The round of the tender Number Y
2 BiddingPeriod N
Fuel Tender Response

0 FuelTenderResponse Root Y
1 Response Message status ACCEPTED, REJECTED. Char[100] Y
1 ErrorDescription Error Description Char[4000] Y

Fuel Tender XML Implementation Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Fuel Tender XML Implementation Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Aviation

International Air Transport Association (IATA) 2016. Page 1 of 35

International Air Transport Association (IATA) 2016. Page 2 of 35

13.6 Bids declined after two rounds .......................................................................................... 12

International Air Transport Association (IATA) 2016. Page 3 of 35

2.1 Purpose and Scope of the Document

2.2 Out of Scope Items

2.3 Intended Audience

3 Business requirement background

4 Old Fuel tendering process

International Air Transport Association (IATA) 2016. Page 4 of 35

5 Why Implement the Fuel Tender XML Messages

International Air Transport Association (IATA) 2016. Page 5 of 35

6 Fuel Tender XML Messages

International Air Transport Association (IATA) 2016. Page 6 of 35

FuelTenderResponse Acceptance/rejection message response for synchronous calls

7 Messaging Bi Lateral Agreements

9.1 Nil Values in Schema

9.2 Char Encoding

9.3 Repeating Elements

10 Date and Time Reference

International Air Transport Association (IATA) 2016. Page 7 of 35

The dateTime is specified in the following form "YYYY-MM-DDThh:mm:ss" where:

YYYY indicates the year

All the messages are defined by the IATA Fuel Tender.xsd

International Air Transport Association (IATA) 2016. Page 8 of 35

12.1 Fuel Tender Invitation

12.2 Fuel Tender Bid

12.3 Fuel Tender Cancel

12.4 Fuel Tender Update

12.5 Fuel Tender Bid Decline

13.1 Successful bid with one supplier

International Air Transport Association (IATA) 2016. Page 9 of 35

13.3 Tender cancelled

International Air Transport Association (IATA) 2016. Page 10 of 35

13.4 Tender update

13.5 Award for two suppliers

International Air Transport Association (IATA) 2016. Page 11 of 35

13.6 Bids declined after two rounds

13.7 Tender cancel after one round

International Air Transport Association (IATA) 2016. Page 12 of 35

Unit Type Code LT as a refers to Litres and KG refers to Kilograms

International Air Transport Association (IATA) 2016. Page 13 of 35

15.1 Bilateral Agreements

17 Message Security Standards

International Air Transport Association (IATA) 2016. Page 14 of 35

International Air Transport Association (IATA) 2016. Page 15 of 35

Appendix A Versioning methodology

International Air Transport Association (IATA) 2016. Page 16 of 35

Appendix B Schema Changes history

0.1 Initial draft Stefan Casapu 16.10.2015

International Air Transport Association (IATA) 2016. Page 17 of 35

Fuel Tender Invitation

2 TenderIdentification Identification of the tender Y

3 TenderCode Identifying code of tender, unique in Char[20] Y

3 TenderName Name of tender Char[100] N

3 TenderHolderCode ICAO code of airline Char[5] Y

3 TenderHolderName Name of tender holder company Char[100] N

3 TenderVersion Version of the tender Number Y

2 TenderType Type of the tender(Product or Service) Char[2] Y

4 ContactPerson Name of contact person for tender Char[200] Y

4 Email E-Mail of contact person for tender Char[100] Y

4 Phone Work phone of contact person for tender Char[50] N

3 From Start of tender bidding period Date Y