International Limited Call for Tenders AOIR: N° 001/DC/2016

COMMERCIAL DIVISION

International Limited Call for Tenders

AOIR: N° 001/DC/2016

“Passenger Services System For Scheduled Passenger Airlines”

AOIR : N° 001/DC/2016 Page 2

TABLE OF CONTENTS

TABLE OF CONTENTS 2

SECTION 1: INSTRUCTIONS TO BIDDERS (ITB) 4

A. GENERAL PROVISIONS 4 1. Objectives and scope of this Bid 4 2. Current situation 4 3. Ethics Rules 4 4. Eligible Bidders 4 5. Qualification of the Bidder 5 6. Cost of Bidding 5 7. One Bid per Bidder 5

B. BIDDING DOCUMENTS 6 8. Content of Bidding Documents File 6 9. Clarifications of Bids 6 10. Amendment of the Bidding Invitation File 6

C. THE BIDS PREPARATION 6 11. Language of Bid 6 12. The Documents Comprising the Bid 7 13. Bid Price 7 14. Currency of Bid 7 15. Bid Validity 7 16. Format and Signing of Bid 7

D. SUBMISSION OF BIDS 8 17. Sealing and Marking of Bids 8 18. Due Date and Time for Bids Submission 8 19. Late Bids 8 20. Modification and Withdrawal of Bids 8

E. BID OPENING AND EVALUATION 9 21. Opening of Bids by AIR ALGERIE 9 22. Non-disclosure Statement 9 23. Clarification of Bids 9 24. Preliminary Examination of Bids and Determination of Responsiveness 10 25. Correction of errors 10 26. Conversion to a Single Currency 10 27. Evaluation and Bids Comparison 10

F. SUBSEQUENT VERIFICATION AND AWARD OF THE CONTRACT 11 28. Award Criteria 11 29. Right to Accept or Reject Any or All Bids 11 30. Notification of Award 11 31. Competitors Protest 11 32. Absence of Obligation 12 33. Signing the Contract Agreement 12

SECTION 2: BID DATA SHEET (BDS) 13

AOIR : N° 001/DC/2016 Page 3

SECTION 3: TECHNICAL REQUIREMENTS 20

1. INTRODUCTION 20

2. AIR ALGERIE BACKGROUND 20 2. 1. Airline Information 20 2. 2. Facts and Figures 20 2. 3. Passenger Traffic Estimation 20 2. 4. Current systems used by AIR ALGERIE 21 2. 5. Current interline e-ticket partners 21 2. 6. IET in progress 22 2. 7. Code share partners 22 2. 8. Business Model 23 2. 9. Indirect sales via GDS for AIR ALGERIE 23 2. 10. EMD Issuance 23 2. 11. E-commerce current situation summary 23 2. 12. DCS at International Stations 24 2. 13. Documents issued 26 2. 14. Airlines ground handled by AIR ALGERIE 26 2. 15. DCS Equipments in Algeria 27 2. 16. Some Figures 27 2. 17. ATO/CTO infrastructure 27 2. 18. AIR ALGERIE Infrastructure Network 27

3. FUNCTIONAL REQUIREMENTS 29 3. 1. General functional requirements of the PSS 29 3. 2. Inventory and Schedule 31 3. 3. Reservation and Booking management 35 3. 4. Ticketing and EMD 40 3. 5. Departure Control System 42 3. 6. Fare Quote System 55 3. 7. Revenue Management System 59 3. 8. Revenue Integrity 64 3. 9. E-Commerce 66 3. 10. Loyalty Management System & Customer experience 75 3. 11. Business Intelligence 82 3. 12. Disruption Management System 82

4. OTHER REQUIREMENTS 84 4. 1. Migration Plan, strategy and Risk Management 84 4. 2. Implementation plan of the PSS 84 4. 3. Tests 85 4. 4. Training 85 4. 5. Project reports 85 4. 6. Final documentation 85

SECTION 4: BIDDING FORMS / SAMPLES OF DOCUMENTS 86 SAMPLE FORMAT: BIDDING LETTER 86 PRICES LIST 87 SAMPLE OF STATEMENT MADE ON THE HONOR 88 ETHICS RULES 89

GLOSSARY 90

AOIR : N° 001/DC/2016 Page 4

SECTION 1: INSTRUCTIONS TO BIDDERS (ITB)

A. GENERAL PROVISIONS

1. Objectives and scope of this Bid

“AIR ALGERIE”, launches an International Limited Invitation addressed to Tenders who are currently

hosting airlines of a size similar to that of AIR ALGERIE, who may be able to supply and implement a

Passenger Services System on a cost effective basis and as such be recipients of this invitation to bid,

in order to fit with AIR ALGERIE’s expectations by:

- Moving to a new generation platform,

- Reducing current costs,

- Simplifying processes and workflows,

- Developing partnership relations and join an alliance,

- Offering new services to clients, to grow revenues channels and boost ancillary revenues,

- Adopting customer centricity policy,

- Having consistent visibility for better decision support.

The scope of this call is defined in subsequent section in this document, principally, the functional

requirements in section 3 part 3. Other associated functionalities may be offered by respondents as part

of an overall offering. Services and support level support for migration and implementation processes

are also within the scope of this call as defined respectively in the section 3 parts 4.

2. Current situation

AIR ALGERIE is the national flag carrier of Algeria. The company provides international passenger and

cargo services globally as well as to major domestic routes of Algeria.

The current situation of the company is described in the section 3 part 2 of this document.

3. Ethics Rules

AIR ALGERIE requires from its contracts Bidders, under constraint of penalties, to observe professional

ethics rules (specified in section 4).

These Rules are considered as part and parcel of the Bidding File.

4. Eligible Bidders

4.1 Bidders must not:

a) Be subject to competition prohibition,

b) Be subject to an AIR ALGERIE’s procurement exclusion decision.

4.2 Bidders shall provide all the necessary documents establishing their admittance to compete that

AIR ALGERIE may require.

AOIR : N° 001/DC/2016 Page 5

5. Qualification of the Bidder

5.1 Bidders shall provide, using the Bidding Forms stated in Section 4, a preliminary description of the

methodology they intend to use to perform the contract and activity schedule, including drawings

and charts, if necessary.

To qualify for the Contract awarding, Bidders shall meet the minimum qualifying criteria stated in

the BDS “Bid Data Sheet” in section 2.

5.2 All bidders shall provide and include in their offer the information, the documents and the bidding

forms as defined in the BDS and Section 4.

5.3 Bids submitted by a joint venture of two or more firms as partners shall comply with the following

requirements, unless otherwise stated in the BDS:

(a) The Bid shall include all information listed in ITB Sub – Clause 5.2 of ITB below mentioned,

for each joint venture partner (name and address of headquarters and place of business

of the companies forming the joint venture).

(b) The Bid shall be signed so as to be legally binding on all the partners.

(c) All partners shall be jointly and severally liable for the execution of the Contract in

accordance with the Contract provisions.

(d) One of the partners shall be nominated as being in charge (representative), authorized to

incur liabilities and receive payments and instructions for and on behalf of any and all

partners of the joint venture; and

(e) The performance and execution of the entire Contract, including payment, shall be done

exclusively with the partner in charge (the representative).

(f) A copy of the agreement entered into by the joint venture partners, or a Letter of Intent

to execute a joint venture agreement in the event of a successful bid, shall be signed by all

partners and submitted with the bid, together with a copy of the proposed Agreement.

Bidders are not allowed to set up one joint venture or more, or a consortium with any other Bidders, nor

to change partners or to modify the joint venture or consortium structure; after the Bid being submitted

(technical Bid, Commercial Bid once submitted by one Bidder or a joint venture).

6. Cost of Bidding

The Bidder shall bear all costs associated with the preparation and submission of his Bid, and AIR

ALGERIE will in no case be responsible or liable for those costs, whatever are the course or the outcome

of the Bidding procedure.

7. One Bid per Bidder

Each Bidder shall submit only one Bid, either individually or as a partner in a joint venture. A Bidder who

submits or participates in more than one Bid (other than as a subcontractor) will cause all the proposals

with the Bidder’s participation to be disqualified.

AOIR : N° 001/DC/2016 Page 6

B. BIDDING DOCUMENTS

8. Content of Bidding Documents File

8.1 The Bidding Document File (BDF) describes the services subject of the contract, states the Bids

procedures and Contract conditions. The file contains the documents listed herein after which

must be construed, should this happen, with the additional clauses published in accordance with

the clause 10 of the ITB:

Invitation to Bid

Section 1: Instructions to Bidders (ITB)

Section 2: Bid Data Sheet (BDS)

Section 3: Technical Specifications

Section 4: Bidding Forms/ samples of documents.

8.2 The Bidder must inspect the instructions, forms, provisions and specifications contained in the

Bidding Invitation File. Any deficiency to provide the required information, or to comply with the

Invitation to Bid File, to submit Bids, shall lead to Bids rejection.

9. Clarifications of the Bidding Invitation File

A Bidder wishing to get clarifications can submit a written request to AIR ALGERIE, to the address

indicated in the BDS. AIR ALGERIE shall reply by writing to only clarifications requests received at least

twenty-one (21) days before the Bids deposit deadline. A copy of AIR ALGERIE’s reply shall be sent to all

bidders having received the Bidding Invitation File, but without mentioning the author.

10. Amendment of the Bidding Invitation File

At any time before the Bids deposit deadline, AIR ALGERIE may modify the bidding documents by issuing

addenda.

Any addendum thus issued shall be part and parcel of the bidding documents and shall be

communicated in writing to all prospective Bidders who have retrieved the bidding invitation file.

Prospective bidders shall acknowledge receipt of each addendum to AIR ALGERIE.

To give prospective bidders reasonable time to take an addendum into account in preparing their bids,

AIR ALGERIE shall extend, as necessary, the deadline for submission of bids.

C. THE BIDS PREPARATION

11. Language of Bid

All the documents related to the submission shall be written in the language specified in the BDS

(section 2).

For bid interpretation purposes, the complementary documents and the printed forms supplied by the

Bidder can be written in another language provided, that “ad hoc paragraphs” must be accompanied by

an accurate translation in the specified language; in which case, the Translation shall prevail.

AOIR : N° 001/DC/2016 Page 7

12. The Documents Comprising the Bid

The list of documents contained in the technical and commercial offers are described in the BDS.

13. Bid Price

13.1 The Contract shall be for all Services, as described in the Specifications (Section3), and submitted by

the Bidder.

13.2 The Bidder shall fill in rates and prices for all items of the Services described in the Specifications

and listed in Section 3. Items for which no rate or price is entered by the Bidder will not be paid

for by AIR ALGERIE when executed and shall be deemed covered by the other rates and prices in

the Activity Schedule.

13.3 All duties, taxes, and other levies payable by the Service Provider under the Contract, shall be

included in the total Bid price submitted by the Bidder.

13.4 Prices quoted by the Bidder shall be firm and not adjustable during the performance of the

Contract and shall not change in no case, unless otherwise stated in the BDS.

14. Currency of Bid

The prices shall be denominated in USD.

15. Bid Validity

Bids should be valid for the period specified in the BDS from the date of Bid Opening.

In exceptional circumstances, prior to expiry of initial Bids period of validity, AIR ALGERIE may request that

the bidders extend the period of validity for a specified additional period. The request and the bidders’

responses shall be made in writing. The Bidder may refuse to extend the validity of his bid. The Bidder

agreeing to the request cannot, and is not entitled otherwise to modify the Bid.

16. Format and Signing of Bid

16.1 The Bidder shall prepare one original and a number of copies as described in the BDS, and

clearly marked as “ORIGINAL” and “COPY” as appropriate. In the event of discrepancy

between them, the original shall govern.

16.2 The original and all copies of the Bid shall be typed and shall be signed by the Bidder or a

person or persons duly authorized to sign on behalf of the Bidder. All pages of the Bid,

except printed prospectus, shall be initialed by the person or persons signing the Bid.

16.3 The Bid shall contain no alterations, cancellation or additions, except those being initialed by

the person or persons signing the Bid.

AOIR : N° 001/DC/2016 Page 8

D. SUBMISSION OF BIDS

17. Sealing and Marking of Bids

17.1 The Bidders shall seal the original and each copy of the bid in separate envelopes duly marked

“ORIGINAL BID” or “COPY” as appropriate. These envelopes shall then be sealed in an outer

envelope.

17.2 The inner and outer envelopes:

a) shall be addressed to AIR ALGERIE at the address given in the Bidding Data Sheet;

b) shall bear the project name, the title and the number of Bidding Invitation indicated in

the Bidding Data Sheet;

c) and shall bear the mention “Do Not Open Before the Date of Bids Opening”, as stated in

the Bidding Data Sheet.

17.3 Bids prepared by the Bidders must be presented in two stages, Technical Bid and Financial Bid.

In the outer envelope, the bid shall be divided in two envelopes bearing the title and the type of

each envelope; the two envelopes shall be constituted of the following:

– Technical Bid

– Commercial Bid

The inner envelopes shall indicate the name and address of the Bidder so that the bid can be

returned unopened, by AIR ALGERIE, in case it is declared “late”, according to Clause 19 of ITB.

17.4 If the outer envelope is not sealed and marked as above required, AIR ALGERIE will assume no

responsibility for the bid’s misplacement or premature opening.

18. Due Date and Time for Bids Submission

18.1 Bids must be received by AIR ALGERIE at the specified address no later than the time and date

stated in the Bidding Data Sheet.

18.2 AIR ALGERIE may, at its discretion, extend this deadline for submission of bids by amending the

bidding documents in accordance with ITB Clause 10, in which case all rights and obligations of

AIR ALGERIE and Bidders will thereafter be subject to the deadline as extended.

19. Late Bids

19.1 Any bid received by AIR ALGERIE after the bid deposit deadline prescribed by AIR ALGERIE, will be

rejected and returned unopened to the Bidder.

19.2 Bids received by AIR ALGERIE after the bid deposit deadline will bear a mention “Late Bids”. The

seal of general delivery office or the seal of AIR ALGERIE bids delivery office, as the case may be,

according to provisions in the Bidding Data Sheet, shall govern.

20. Modification and Withdrawal of Bids

20.1 The Bidder may modify or withdraw his bid after submission, provided that written notice of the

modification or withdrawal is received by AIR ALGERIE prior to Bid deposit day and time

deadline.

AOIR : N° 001/DC/2016 Page 9

20.2 The written notice of the Bidder’s modification or withdrawal shall be prepared, sealed, marked

and dispatched according to ITB Clause 17. Outer envelopes shall bear the mention

“MODIFICATION” or “WITHDRAWAL” as the case might be. The withdrawal may be made by a

written notice duly signed and received by AIR ALGERIE prior to the deadline prescribed for bid

submission.

20.3 No Bid can be modified after the deadline prescribed for bids submission.

20.4 No Bid may be withdrawn in the interval between the bids submission deadline and the expiration

of the bid validity period specified by the Bidder.

E. BID OPENING AND EVALUATION

21. Opening of Bids by AIR ALGERIE

21.1 AIR ALGERIE will open the bids, including modifications made pursuant to ITB Clause 20, choose to

attend, at the time, date, and location stipulated in the Bidding Data Sheet.

21.2 AIR ALGERIE will proceed in two (02) stages:

- The First Stage (The Technical Stage): AIR ALGERIE will proceed first and only to opening

outer envelopes which contain technical bids and any other documents other than those

related to price, AIR ALGERIE will afterward carry out a detailed analysis and evaluation of

the technical bids which contain no price indication.

- The Second Stage: (The Commercial Stage) : AIR ALGERIE will proceed afterwards to the

opening the envelopes, and to carry out the evaluation, the conformity control, the

commercial bids ranking , of the bids that meet the technical requirements at the first

stage.

22. Non-disclosure Statement

22.1 Information related to the examination, clarification, evaluation, and comparison of bids and

recommendations for the award of a contract shall not be disclosed to Bidders or any other

persons not officially concerned with such process until the award to the successful Bidder is

notified of the award according to the ITB Clause 30. Any effort by a Bidder to influence AIR

ALGERIE’s reviewing of bids or awarding decisions may result in the rejection of his Bid.

22.2 If, after notification of award, a bidder wishes to ascertain the grounds on which its bid was not

selected, it should address its request in writing to AIR ALGERIE as indicated in the Bidding Data

Sheet (item 31), who will provide prompt written explanation. Any request for explanation from

one bidder should relate only to its own bid; information about the bid of competitors will not

be addressed.

23. Clarification of Bids

In order to make easy bids examination, comparison and evaluation, AIR ALGERIE may, at its discretion,

ask the Bidder for a clarification of its bid. The request for clarification and the response shall be in

writing, and no change in the price or substantive change of the bid shall be sought, offered or

permitted.

AOIR : N° 001/DC/2016 Page 10

24. Preliminary Examination of Bids and Determination of Responsiveness

24.1 Prior to the detailed evaluation, AIR ALGERIE will determine if each Bid is substantially

responsive to the Bidding Invitation File.

24.2 A substantially responsive Bid is one which conforms to all terms, conditions, and specifications

of the bidding documents, without material deviation or reservation. A material deviation or

reservation is the one:

(i) Which affects in any substantial way the scope, quality, or performance of the services;

(ii) Which limits in any substantial way, which is inconsistent with the bidding Invitation File,

limits the Rights of AIR ALGERIE or the Bidder’s obligations under the Contract;

(iii) Or whose rectification would affect unfairly the competitive position of other Bidders

presenting substantially responsive bids.

24.3 If a Bid is not substantially responsive, it will be rejected by AIR ALGERIE, and may not subsequently

be made responsive by correction or withdrawal of the nonconforming deviation or reservation.

25. Correction of errors

25.1 Bids determined to be substantially responsive will be checked by AIR ALGERIE for any

arithmetic errors. Arithmetical errors will be rectified by AIR ALGERIE on the following basis:

- If there is any discrepancy between the amounts in figures and in words, the amount in words

will govern.

- If there is any discrepancy between unit rate and the line item total resulting from multiplying

the unit rate by quantity, the quoted unit rate will govern. Unless in the opinion of AIR ALGERIE

there is an obvious gross misplacement of the decimal point in the unit rate, in which case unit

rate will be corrected and the line item total as presented shall govern in accordance with this

paragraph.

25.2 The amount stated in the Bid will be adjusted by AIR ALGERIE in accordance with the above

procedure for the correction of errors and, with the concurrence of the Bidder, shall be

considered as binding upon the Bidder. If the Bidder does not accept the corrected amount, the

Bid will be rejected.

26. Conversion to a Single Currency

For evaluation and comparison purposes, AIR ALGERIE shall convert all bids prices in Algerian Dinar

(DZD) by using Algeria Rate of Exchange published by BANQUE D’ALGERIE in force the day before

commercial bids opening date.

The prices of the bids shall meet the sum of all the amounts expressed in various currencies, converted

to Algerian Dinar.

27. Evaluation and Bids Comparison

27.1 AIR ALGERIE will carry out a detailed evaluation of the bids previously determined to be

substantially responsive in order to determine whether the aspects of the bids are in accordance

with the requirements set forth in the ITB Clause 24.

27.2 Responsive bids will be evaluated and examined in two (2) stages on the basis of criteria and

their respective weights, according to the methodology set forth in the Bidding Invitation File

(section 2):

AOIR : N° 001/DC/2016 Page 11

a) The First Stage: The Technical Stage:

Bidders whose bids are responsive and meet qualification and technical criteria stated in

the Bidding Invitation File are eligible to bids commercial evaluation in a second stage;

The Bidders, whose bids are not responsive, shall be informed of the rejection of their

Bids by writing. AIR ALGERIE may ask any Bidder whose technical bid meets qualification

criteria; to give some clarifications on his bid technical aspects.

b) The Second Stage: The Commercial Stage:

The retained bid shall be the Lowest Bid on the price basis only, or on the best bid, as

stated in the Bidding Data Sheet.

The appropriated evaluation methodology is detailed in the Bid Data Sheet and / or in the

Technical Specifications Sheet.

F. SUBSEQUENT VERIFICATION AND AWARD OF THE CONTRACT

28. Award Criteria

AIR ALGERIE shall award the Contract to the Bidder having presented a Responsive Bid in conformity

with the Bidding Invitation File, and being the best bid for AIR ALGERIE, provided that the Bidder meets

the conditions of qualification to perform the contract properly.

29. Right to Accept or Reject Any or All Bids

AIR ALGERIE reserves the right to accept or reject any bid, and to cancel the bidding process and reject

all bids at any time prior to the award of contract, without thereby incurring any liability to the affected

bidder or bidders or any obligation to inform the affected Bidder or bidders about reasons of his

decision.

30. Notification of Award

AIR ALGERIE shall notify the successful Bidder about provisional acceptance of the Bid, prior to bids

validity expiration, in writing by email.

The provisional acceptance must be notified to other Bidders, in writing by email.

31. Competitors Protest

Any Bidder who challenges bidding results or reasons of rejection of his Bid, as notified by AIR ALGERIE,

or who protests any failure to comply with procurement rule, may lodge a detailed request to AIR

ALGERIE.

Competitor’s protest must be lodged within ten (10) days of the contract provisional award publication

or its notification to bidders or the notification to rejected bidders.

AIR ALGERIE shall reply to the concerned competitor’s request within twenty one (21) days of receiving

the request.

Must not be contested:

- Procurement choice or bidders selection;

- AIR ALGERIE decision to reject all the bids or cancel the bidding invitation pursuant to provisions

clause 29 of ITB.

AOIR : N° 001/DC/2016 Page 12

32. Absence of Obligation

Nothing in this Bidding invitation should be construed to mean that AIR ALGERIE has any obligation to

buy any of the supplier products or services reviewed. All bidders-incurred expenses associated with

answering this Bidding invitation are solely the responsibility of the bidder. By agreeing to review

various bidders and their products, AIR ALGERIE has no obligation to reimburse expenses incurred by

the bidder. AIR ALGERIE reserves the right to reject any and all proposals.

33. Signing the Contract Agreement

The contract signatory for the vendor shall be a corporate officer of the company or a duly authorized

agent.

AOIR : N° 001/DC/2016 Page 13

SECTION 2: BID DATA SHEET (BDS)

Following inquiries and information shall complete, define or amend Clauses of ITB. In the event of

discrepancy, below listed Bid Data Sheet shall prevail on ITB.

A – GENERAL PROVISIONS

1

Name and address of AIR ALGERIE:

AIR ALGERIE - Commercial Division

29 Bd, Zirout Youcef 16000 ALGIERS

Email: [email protected]

Scope of Bid:

Passenger Services System for Scheduled Passenger Airlines

This Bid is issued to invite reputed and experienced providers to acquire and

implement a Passenger Service System with additional solutions

AIR ALGERIE expects to acquire a hosted solution.

Services to be provided are:

o Inventory,

o Reservation and Booking management,

o Ticketing and EMD,

o Departure control system,

o Fare Quote,

o Revenue Management,

o Revenue Integrity,

o E-Commerce,

o Loyalty Management and Customer Experience,

o Business Intelligence,

o Disruption Management.

Project Name and identification number:

Name: “Passenger Services System For Scheduled Passenger Airlines”

Identification number: “AOIR: N° 001/DC/2016”

AOIR : N° 001/DC/2016 Page 14

4 Required Eligibility Criteria:

Suppliers of PSS, providing currently their PSS to three (03) scheduled airlines at least.

5

Bidder Qualification:

This invitation for Bids is open to bidders meeting below conditions:

- The bidder has the financial and technical ability to perform the contract ;

- The bidder must have experience in PSS migration for scheduled airlines ;

- The bidder shall provide, as part and parcel of its bid, documents proving

his qualifications to perform the contract if awarded.

Profile of the company:

The bidder shall provide general information about his company, showing his

vision and strategy of services to be provided:

- Number of employees ;

- Number and addresses of his offices (geographic place) ;

- A financial overview (shall contain annual balance sheets and

Revenue) ;

- Name of current clients using his solutions ;

- Professional references ;

- Investments in research and development.

5

Documents stating conformity with Bidding Document File:

The bidder shall provide, as part and parcel of his bid, documents confirming that

proposed PSS complies with the bidding invitation file including section 3.

Provided documents shall be written descriptions, prospectus, certificates and clients’

references, including to:

a. Technical bid, i.e. detailed technical description of the solution advocated by

the bidder fully compliant with technical and functional specifications.

b. Technical requirements tables duly filled as specified in section 3;

c. The preliminary project plan shall include a detailed activity schedule in

addition to human resources. It shall define bidder’s expectations from AIR

ALGERIE or any other party concerned by the implementation of the PSS,

and the coordinating methods planned to be used by the bidder with all

concerned parties.

AOIR : N° 001/DC/2016 Page 15

9

Clarifications of Bids:

Bidders may submit clarifications request about bidding invitation file to AIR ALGERIE

by Email: [email protected]

AIR ALGERIE shall reply by writing to only clarification requests received at least

twenty-one (21) days before the Bids deposit deadline.

Replies to bidders’ requests shall be sent by email to all bidders, without any disclosure

of those bidders identity.

C – PREPARATION AND BID SUBMISSION

11

The Submission Language is :

The Bid and all correspondences and documents related to the bid exchanged between

the Bidder and AIR ALGERIE shall be submitted in English Language.

12

The Bid shall contain the following documents:

Technical offer :

- This specifications book signed and each page initialed;

- Declaration on the honor duly filled and signed (section 4);

- The proxy giving the right to one or more signatories to commit the Bidder;

- A written commitment stating that at least three (03) scheduled airlines are

currently using bidder’s PSS;

- Copy of trade register and legal status of the bidder;

- Documents confirming the bidder’s qualifications;

- Qualification and experience of key management and technical staff proposed

for the contract;

- Documents related to financial standing of the bidder, including financial

statements of the last (03) three years duly certified by an auditor ;

- Documents proving that the proposed solutions complies with bidding file

specifications (digital support, prospectus summing up characteristics and

specifications of the product and services);

- Technical requirements tables duly filled as specified in section 3;

- List of all companies using PSS, demonstrating the professional references of

the bidder (specifying the solutions used);

- Table of performed or planned migration as specified in section 3 point 4

“Other requirements”;

- Three (03) PSS migrated clients’ reference letters including company

mailto:[email protected]

AOIR : N° 001/DC/2016 Page 16

Name and contact;

- List of airports served by Air Algeria and where the proposed DCS is

operated by the airlines and / or Ground Handler (to specify) (section

3/2.12);

- Planning of migration and implementation, as specified in section 3

point 4 “Other requirements”.

Commercial offer:

- Bidding letter duly filled and signed (section 4);

- Prices list filled according to bid price and signed (section 4);

- Draft of the contract Agreement in French and English;

- Draft of the Service Level Agreement.

13 Alternate bids:

Alternate bids will not be considered.

13

Bid Price:

Supplier shall precise total fees for :

- Implementation;

- Usage, support and maintenance, based on Passenger Boarded (PB) for a

minimum period of five (05) years contract, depending on annual traffic

ranges:

Less than 4 millions

Between 4 and 6 millions

Between 6 and 8 millions

More than 8 millions

All other costs must be supported by the supplier. The payment of benefits will be

made after the execution of the contract.

Duties and taxes:

Bidders shall meet their tax responsibilities and obligations in accordance with existing

regulation.

14 Currencies of Bid : Prices shall be specified in USD.

15 Bid Validity :

Bids Validity Period is one hundred eighty (180) days after Bids Submission deadline.

AOIR : N° 001/DC/2016 Page 17

16

Number of Copies :

The Bid must comprise:

- One (01) original,

- Two (02) copies (on paper print),

- One (01) copy on digital format

D – BIDS SUBMISSION

18

Due date and time for Bids Submission:

The offers submission date is limited on 11th July 2016, at 1 p.m.

Bids Submission:


Secretariat of Commercial Division 5th floor.

29 Bd, Zirout Youcef 16000 ALGIERS ALGERIA

Project Name and identification number:

Name: International Limited Call for Tenders

“Passenger Services System For Scheduled Passenger Airlines”

Identification number: “AOIR: N° 001/DC/2016”

Mention :

The envelope shall bear the mention : « DO NOT OPEN BEFORE THE DATE OF BIDS

OPENING»

E –BID OPENING AND EVALUATION

21

Day, Time and Address of bids opening:

The Bid opening session will be held on 11TH July 2016, at 02 p.m publcl Algerian Time

at the following address:


Secretariat of Commercial Division 5th floor.

29 Bd, Zirout Youcef 16000 ALGIERS ALGERIA

AIR ALGERIE shall examine the bids to determine whether they are complete and

comply with award criteria, documents are properly signed, and bids are generally in

proper order.

Prior to the detailed evaluation, AIR ALGERIE shall determine whether each bid is

AOIR : N° 001/DC/2016 Page 18

substantially of acceptable quality, complete, and meets the bidding file provisions. A

substantially responsive Bid is one which conforms to all terms, conditions,

specifications and provisions of the bidding invitation file without material deviation,

exceptions, objections, conditions or reserves.

If a bid is considered not responsive by AIR ALGERIE, it will be rejected, and may not

subsequently be made responsive by correction. AIR ALGERIE shall determine whether

a bid is responsive according to the content of bid itself.

27

Evaluation and Bids Comparison:

AIR ALGERIE shall proceed to the evaluation and comparison of bids, which have been

defined as substantially responsive to BDS.

Bids compliant with bidding invitation file shall be evaluated and analyzed by a

Committee. This evaluation will be done in two (02) stages according to the following

method:

First stage, technical evaluation: maximum 70 points.

Second stage, commercial evaluation: maximum 30 points.

First stage: technical evaluation:

Bidders whose bids meet qualification criteria (reference, ability, financial standing

etc...) and technical compliance criteria included in the bidding invitation file are eligible

to commercial bids evaluation as a second stage.

AIR ALGERIE may ask any Bidder whose technical bid meets qualification criteria; to

provide clarifications on its bid technical aspects.

Technical evaluation will be based on 04 criteria:

- References (5 points);

- Expérience in migration (10 points);

- Commonality & Integration (20 points);

- Technical Features (35 points).

Only technical bids having obtained a total of 50 points and over will be retained for the

evaluation of the corresponding commercial bids.

Bidders whose bids are qualified as non-responsive at the first technical evaluation, shall

be informed of the rejection of their Bids by writing.

Second stage: Commercial evaluation:

The evaluation of a bid by AIR ALGERIE will be based on submitted price.

The highest ranking (30 points) is given to the Lowest commercial (financial) bid.

AOIR : N° 001/DC/2016 Page 19

The ranking for other bids will be calculated as follows:

N = 30 X Mm /Mc

N = Financial rating of the bid itself

Mm = Amount of the Lowest bid

Mc = Amount of the commercial bid itself

The best bid will be the first bid in final ranking; the ranking is carried out by summing

technical and commercial (financial) points for each bidder.

In case several bids are classified at the first ranking, (same sum of points), the lowest

commercial bid will be accepted.

F – SUBSEQUENT VERIFICATION AND AWARD OF THE CONTRACT

28

Subsequent verification:

AIR ALGERIE has the right to ensure that the awarded bidder, who submitted a

responsive bid qualified as the best bid for AIR ALGERIE, has required qualifications in

accordance with bidding invitation file provisions.

In this frame, AIR ALGERIE will proceed to tests in subsequent verification, in order to

insure that the proposed solution meets performance criteria or functionalities

specified on technical specifications.

The bidder having submitted the best bid to AIR ALGERIE won’t be awarded the contract

unless the subsequent verification is positive. Otherwise, the bid shall be rejected and

AIR ALGERIE shall examine similarly the second best bid.

31

Competitors Protest:

Any Bidder who challenges bidding results or reasons of rejection of his Bid, or who

protests any failure to comply with procurement rule, may lodge a detailed request

within ten (10) days following provisional notification to :

AIR ALGERIE – COMMISSION DES MARCHES –

01 Place Maurice Audin, Algiers - Algeria.

AOIR : N° 001/DC/2016 Page 20

SECTION 3: TECHNICAL REQUIREMENTS

1. INTRODUCTION

AIR ALGERIE is the flag carrier of Algeria which provides air services (passengers and cargo) on both

national and international routes.

The current situation of AIR ALGERIE is described below.

2. AIR ALGERIE BACKGROUND

2. 1. Airline Information

Airline Name: AIR ALGERIE

IATA Airline Code: AH

IATA Accounting Code: 124

Headquarters City: ALGIERS, 01 Place Maurice Audin.

Years in operation: Since 1947

Ownership structure: ALGERIAN GOVERNMENT

2. 2. Facts and Figures

Aircraft Fleet

08/A330 03/B767 22/B737-800 (4 will be delivered in 2016) 5/B737-600 15/ ATR

Daily Flights (scheduled) 167 (Average)

Destinations Served

32 domestic stations

40 international stations (Europe, Africa, China,

Middle East, Canada)

Passengers Boarded 2012 = 4 137 266 PB 2013 = 4 547 893 PB 2014 = 5 082 508 PB

2. 3. Passenger Traffic Estimation

2015 2016 2017 2018 2019 2020 2021

5 336 633 5 603 465 5 883 638 6 177 820 6 486 711 6 811 047 7 151 599

AOIR : N° 001/DC/2016 Page 21

2. 4. Current systems used by AIR ALGERIE

System Product Name / Vendor

Reservations/ Inventory/ Ticketing MARS / MERCATOR

Distribution Program OAG - INNOVATA (manually not SSIM)

Revenue Management System NOT AVAILABLE

Revenue Accounting System RAPID / MERCATOR

CRM/Loyalty system CRIS / MERCATOR

Schedule Management System AIMS

Flight Operations System AIMS

Internet Booking Engine IBE/MERCATOR

Revenue Integrity / Flight Firming CALIDRIS / MERCATOR

Data Warehouse In-house

Payment Service Provider(s) OGONE (international cards)

SATIM (national cards) Filing Fares ATPCO

Fares Quote WORLDSPAN

Electronic Ticket Server ETS / MERCATOR

Departure Control System MACS /MERCATOR

Call Centre System/CRM Hermes NET/VOCALCOM

Back-office ATO/CTO SYGA / (In-house)

2. 5. Current interline e-ticket partners

Airlines Airlines Code

AIR BURKINA 2J

AFRIQYAH 8U

AIR France AF

ROYAL AIR MAROC AT

ALITALIA AZ

BRITISH AIRWAYS BA

CATHAY PACIFIC CX

DEUTSH BAHN DB

DELTA AIRLINES DL

EMIRATES EK

ETHIOPIAN AIRLINES ET

ETIHAD AIRWAYS EY

GARUDA INDONESIA GA

GULF AIR GF

HAHN AIR HR

HAINAN AIR HU

IBERIA IB

YEMENIA AIRWAYS IY

JAPAN AIRLINES JL

KOREAN AIRLINES KE

AOIR : N° 001/DC/2016 Page 22

Airlines Airlines Code

AIR MALTA KM

KENYA AIWAYS KQ

KUWAIT AIRWAYS KU

MAURITANIA AIRLINES L6

EQUATORIAL CONGO AIRLINES - ECAIR LC

LUXAIR LG

LUFTHANSA LH

AIR LIBAN ME

MALYSIA AIRLINES MH

EGYPT AIR MS

ALL NIPPON NH

ASIANA AIRLINES OZ

QATAR AIRWAYS QR

SYRIAN ARAB AIRLINES RB

ROYAL JORDANIAN RJ

BRUSSELS AIRLINES SN

SINGAPORE AIRLINES SQ

AEROFLOT SU

SAUDIA AIRLINES SV

TURKISH AIRLINES TK

TAP Portugal TP

TUNISAIR TU

UNITED AIRLINES UA

VIETNAM AIRLINES VN

2. 6. IET in progress

AIR CANADA AC

TASSILI AIRLINES SF

RWANDAIR WB

2. 7. Code share partners

Airline Agreement type (Block Space / Free-flow)

TURKISH AIRLINES -TK - Free-Flow

AOIR : N° 001/DC/2016 Page 23

2. 8. Business Model

Model Number

Direct Call Center 1

CTO/ATO 151 (107 in Algeria, 44 international)

Direct IBE 1

Direct General Sales Agents 7

Indirect GDS 6

2. 9. Indirect sales via GDS for AIR ALGERIE

Name

1 Abacus

2 Amadeus

3 Axess

4 Sabre

5 Travelport (Galileo/Apollo)

6 Travelsky

2. 10. EMD Issuance

Services Category Status

18 services Standalone &

Associated Deployed at ATO /CTO

04 services Standalone Deployed at Amadeus Travel Agencies in 25 BSP

05 services Standalone Deployed at Amadeus Travel Agencies in Algeria Market

04 services Standalone Implementing at Travelport

04 services Standalone To be implemented at Sabre

2. 11. E-commerce current situation summary

IBE Features Description

IBE Languages FR/EN

Search Schedule/Price/Flexible search (calendar fares)

Payment

- OGONE : International Payments (CB, VISA, MASTERCARD)

- SATIM : Local payments (DZD)

- Book & Hold (Collection at ATO/CTO)

AOIR : N° 001/DC/2016 Page 24

Services - Manage my booking (seating, meals...)

- Online check-in

Frequent flyer Program - Redemption - Upgrade

Promotional offers Discount codes

IBE Numbers (2015) Estimation

Sessions/month 620 000

Single Visits/month 316 000

Daily sessions/hour 1 700

Annual growth (single visits) 20%

Historical Peak (2014)

Single visits/hour 8 000

Single visits/day 54 000

2. 12. DCS at International Stations

STATION AIRPORT

CODE DCS SUPPLIER CUTE GROUND HANDLER

Abidjan ABJ DC ALTEA AMADEUS SITA CUTE NAS

Alicante ALC RESIBER IBERIA SITA CUTE IBERIA

Amman AMM MACS MERCATOR SITA CUTE ROYAL JORDANIAN

Bamako BKO DC ALTEA AMADEUS RESA CREWS ASAM S.A

Barcelona BCN RESIBER IBERIA SITA CUTE IBERIA

Berlin SXF EDS EDS SITA CUTE ACCIONA

Beirut BEY DCS SITA SITA SITA CUTE LAT

Bordeaux BOD MACS MERCATOR RESA CREWS Aviapartner

Brussels BRU EDS EDS ARINC MUSE Swissport

Cairo CAI DC ALTEA AMADEUS SITA CUTE Egypt Air

Casablanca CMN MACS MERCATOR SITA CUTE Royal Air Maroc

Charles De Gaulle CDG MACS MERCATOR RESA CREWS Alyzia

AOIR : N° 001/DC/2016 Page 25

STATION AIRPORT


Dakar DKR DC ALTEA AMADEUS RESA CREWS SHS

Damascus DAM SITA DCS SITA SITA CUTE Syrian Air

Dubai DXB MACS MERCATOR SITA CUTE Dnata

Frankfurt FRA MACS MERCATOR SITA CUTE ACCIONA

Geneva GVA EDS EDS SITA CUTE Swissport

Istanbul IST EDS EDS SITA CUTE HAVAS

Jeddah JED MACS MERCATOR SITA CUTE S G S

Lille LIL MACS MERCATOR RESA CREWS Aviapartner

London LHR MACS MERCATOR ARINC MUSE Swissport (Ex Servisair)

Lyon LYS MACS MERCATOR RESA CREWS Aviapartner

Lisbon LIS DC ALTEA AMADEUS SITA CUTE Groundforce

Medina MED MACS MERCATOR SITA CUTE S G S

Madrid MAD RESIBER IBERIA SITA CUTE IBERIA

Marseille MRS MACS MERCATOR RESA CREWS Aviapartner

Metz ETZ DC ALTEA AMADEUS RESA CREWS EMNPL

Milan MXP DC ALTEA AMADEUS ARINC MUSE WFS (Ex Ata Italia)

Montreal YUL MACS MERCATOR ARINC MUSE Swissport (Ex Servisair)

Moscow SVO SABRE DCS SABRE SITA CUTE Shremetyevo Airport

Mulhouse MLH SITA DCS SITA RESA CREWS Swissport

Nantes NTE LCA UNISYS RESA CREWS Aviapartner

Niamey NIM DC ALTEA AMADEUS RESA CREWS Regie Assistance

Nice NCE MACS MERCATOR RESA CREWS Aviapartner

Nouakchott NKC DC ALTEA AMADEUS RESA CREWS Mauritania Airlines

Orly ORY MACS MERCATOR RESA CREWS Alyzia

Ouagadougou OUA DC ALTEA AMADEUS RESA CREWS RACGAE

Beijing PEK MACS MERCATOR SITA CUTE B. G. S

Rome FCO ARCO ALITALIA SITA CUTE Aviapartner ( Ex Flightcare)

AOIR : N° 001/DC/2016 Page 26

STATION AIRPORT


Sabiha SAW SITA DCS SITA SITA CUTE TGS

Toulouse TLS MACS MERCATOR RESA CREWS Aviapartner

Tunis TUN MACS MERCATOR RESA CREWS Tunis Air

Vienna VIE DC ALTEA AMADEUS SITA CUTE CELEBI

Montpellier MPL LCA UNISYS RESA CREWS Aviapartner

Palma De Mallorca PMI RESIBER IBERIA SITA CUTE IBERIA

Strasbourg SXB LCA UNISYS RESA CREWS Aviapartner

2. 13. Documents issued

The boarding pass and bag tag PECTABs used are different from station to another. In some stations, the

Ground handler uses its own documents to issue boarding pass and bag tag for AIR ALGERIE, therefore

the PECTAB is different and is configured in the system accordingly.

2. 14. Airlines ground handled by AIR ALGERIE

AIRLINE CODE DCS SUPPLIER

EGYPT AIR MS AMADEUS (ALTEA DC)

TUNIS AIR TU AMADEUS (ALTEA DC)

SAUDI AIRLINES SV AMADEUS (ALTEA DC)

ROYAL AIR MAROC AT AMADEUS (ALTEA DC)

ROYAL JORDANIAN RJ AMADEUS (ALTEA DC)

SYRIAN ARAB AIRLINES RB SITA

LYBIAN LN MERCATOR (MACS)

AIR MÉDITERRANÉE ML MERCATOR (MACS)

JetairFly TB MERCATOR (MACS)

AIR MALTA KM MERCATOR (MACS)

IBERIA IB IBERIA (RESIBER)

https://fr.wikipedia.org/wiki/JetairFly

AOIR : N° 001/DC/2016 Page 27

2. 15. DCS Equipments in Algeria

TYPE MANUFACTURER MODEL

BOARDING PASS PRINTER INTERMEC IER

PF 4i IER400

GATE READER IER IER600

PASSPORT READER DESKO MPR 7200

BAG TAG PRINTER INTERMEC IER

PF 2i IER400/IER506

SCANNERS INTERMEC SR30

PCS HEWLETT-PACKARD HP Pro 3330 mt / HP dx2400 mt

OS MICROSOFT WINDOWS 7

2. 16. Some Figures

NUMBER OF MACS SESSIONS (Algeria) 285

NUMBER OF USERS 2550

NUMBER OF PRINTERS BPP and BTP (Algeria) 290

NUMBER OF SCANNERS (Algeria) 100

GATE READERs (Algeria) 10

2. 17. ATO/CTO infrastructure

PC Printer Network

- HP/Acer/Others - Processor Intel - RAM:1Go min - HDD: 300 GB min - OS : Win XP pro/

Win7 pro/ Win 8 pro 32/64 bits

Average 4 PCs per agency

Lasers printer A4 Monochrome Dot Matrix printer Average 2 printers per agency

Ethernet 100 mbps Wan 64/512kpbs leased line (SITA) Some agencies have an ADSL connection

2. 18. AIR ALGERIE Infrastructure Network

See the following schema:

Internet

Users with ADSL Connection

SITA International

Network

Datacenter AH Algiers Kouba

LS 6

4/5

12 K

bps

Domestic AH CTO/ATO and Airports

International AH CTO/ATO and Airports

Algiers Airport Terminal 1 and 3

Datacenter MERCATOR Dubaï

2 x

LS 1

Mbps

SITA Algiers

AIR ALGERIE Infrastructure Network

AOIR : N° 001/DC/2016 Page 29

3. FUNCTIONAL REQUIREMENTS

This Bid is issued to invite reputed and experienced suppliers to provide a hosted Passenger Service

System.

This section lists AIR ALGERIE’s current and future functional requirements. The system must be able to

deliver these functional requirements either currently or prior to an agreed upon future date. Please

indicate which of the functions below are currently supported and which will be supported in the future

and by what date.

Legend: Y=Yes, N=No, P=Partial, F=Future (Indicate timelines)

3. 1. General functional requirements of the PSS

All PSS modules listed below must support all IATA standards and recommended practices.

Item Functional Requirement Compliance

Y/N/P/F Core or

Optional Observation

1

Access. Access to all systems and/or their functionalities must be controlled by session characteristics and by agent authorization. It shall be possible to define a group of users with limited set of functions to be defined by AIR ALGERIE.

2 Access. Ability to access system via internet/Web (secure access) and leased lines.

3 GUI. Graphical User Interface must be available for direct user entries for all modules. Native mode is required.

4 GUI. All native entries must be supported on the GUI.

5 Modes. Training, Test/acceptance and production modes are required.

6

Access management. Ability to manage users

profiles and privileges:

- Creation,

- Amendment,

- Suspension,

- Cancellation.

7 Online Help. Ability to provide help information and user guides.

8 Session. Ability to auto sign-out after a defined period of inactivity (to be specified).

AOIR : N° 001/DC/2016 Page 30


Y/N/P/F Core or


9 Log. History logging for all modules must be available (who, when and what change were made).

10

Security. The provider must guarantee : - Security, confidentiality and integrity of data, - High Availability, - Disaster Recovery.

11 Integration. All PSS modules must be fully integrated (reservation/ticketing, inventory, DCS, IBE, RI…)

12 Integration. Ability to provide integration capabilities (APIs, Web Services, Middleware, etc.) to facilitate integration with third party systems.

13 Connectivity. Ability to support connectivity with all GDS, Interline and Codeshare partners.

14 Payment. Payment solution must be PCI-DSS compliant.

15

Payment. Ability to accept : - International and local forms of payment

(Credit/debit cards, e-wallets, settlements…),

- Payment on all channels (ATO/CTO, WEB, Mobile, Call Centre…).

16 Payment. Ability to provide PSP integration (WorldPay, wirecard…).

17 Payment. Ability to support Fraud prevention and chargeback controls.

18 Payment. Ability to provide Security checks (CVV, 3D Secure…).

19 Payment. Ability to support Dynamic currency conversion.

20 Data warehouse. Ability to extract automatically and manually all data (E.g. PNR data, Schedules data, Inventory data, DCS data…).

AOIR : N° 001/DC/2016 Page 31

3. 2. Inventory


Y/N/P/F Core or


Schedule Management

1 IATA standard. Incoming and outgoing IATA standard schedule messages (SSIM/ ASM / SSM) must be automatically processed.

2

Schedule. Ability to add new schedule (manually and/or automatically), to change existing schedule or modify online into the inventory.

3

Schedule. Creation, modification activities must be restricted only to specific agents based on AIR ALGERIE business rules requirement.

4 OAG/INNOVATA update. The supplier must indicate the update frequency.

5

Schedule. Ability to create the schedule in the inventory including (not limited to):

- Flight number, - Effective and discontinue dates, - Departure and arrival time, - Frequency, - Route pair, - Aircraft Type, - Terminal.

6

Schedule Integrity. Ability to perform automated check during schedule creation/modification (e.g. Arrival date is less than Departure date).

7 Schedule messages. Incoming schedule messages that cannot be automatically processed must be manually reviewed.

8 Schedule messages from Other Airlines (OAL), Interline Partners, Codeshare Partners, Airline IT providers must be accepted.

9 Schedule messages. Ability to send ASM/SSM recap (automatically and/or manually) to other systems (OAG, INNOVATA…).

10

Traffic Restrictions. All IATA standard traffic restrictions via SSIM/SSM/ASM to notify OAL/GDS/OAG/INNOVATA are supported.

AOIR : N° 001/DC/2016 Page 32


Y/N/P/F Core or


11 Short-term schedule. Ability to create extra section flights and Charters flights.

12 Shared Schedule Database. Ability to provide a single shared schedules database with DCS and reservation system.

13 MCT file from OAG or INNOVATA must be loaded.

14

Schedule change. Ability to rebook automatically Seat Maps, Seat Assignments and Special Service Requests (SSR), in case of schedule change. PNRs containing failed seats or SSRs must be queue placed.

15 Schedule change. Automatic/manual passenger re-accommodation is required in case of schedule change.

16 Codeshare schedule change. Ability to re-accommodate automatically the passengers in case of codeshare schedule change.

17 Restriction codes. Ability to display restricted segments in passenger application according to the SSIM manual (e.g. APPENDIX G).

18 Schedule Updates must be processed in real time to all PSS modules.

19 Creation flights. Automatic flight creation must be at least 360 days (system period).

20 Flight Range. 0000-9999 flight number range must be supported.

21

AVS/NAVS. Ability to control the sending and receiving of AVS/NAVS messages, based on AIR ALGERIE specific rules (first closing, segment availability…).

22 AVS agreements. Ability to display AVS agreements.

23 Seat configuration. Ability to proceed to an automatic configuration of the seat map on the DCS after schedule amendment in the inventory.

24 Leg/Circular flights. Multi-leg/Circular flights must be supported.

25 Meal. Ability to support all IATA meal service codes and Inflight Service (IFS) codes in SSIM/SSM/ASM.

AOIR : N° 001/DC/2016 Page 33


Y/N/P/F Core or


26 SFPD. Ability to support Secure Flight indicator (SFPD) at leg level.

Inventory Management

27

Minimum Connection Time Table. City pairs must have a user updateable table, which establishes the minimum/maximum connection times between flights. Connections must be configurable by carrier code, flight number and class with the ability to give preference to Codeshare partners. The minimum connection table should also be able to cater for multiple airports within a city code.

28 Ability to display a minimum of 26 classes. Normal availability displays should be restricted to x classes (x being a system parameter).

29 City pair comment. Ability to show a city pair comment over and above flight details on an availability display.

30 Flight Schedule information. Ability to retrieve Flight Schedule information up to 3 days post-departure.

31 Number of seats. Display IATA standardized number of seats available in each inventory (OAL, codeshare partners …).

32

Seat map. Ability to build or delete a seat map based on a variety of technical, business and legal requirements. Must include the ability to assign specific characteristics to seats/rows and provide seat history.

33 Advance seat selection. Ability to manage advanced seat selection and seat map retrieval.

34

Block and restrict seat assignment. Ability to block individual seats from Advanced Seat selection or to restrict the number of seats available for Advanced Seat selection by segment and/or class.

35 Group Seating. Ability to assign group seat block, to display group seat map and to allocate seats to individual names from the group block.

36

Cancel Unassigned Seats. Ability to cancel unassigned seats reserved in a group PNR transaction, to remove seats initially reserved for a group.

AOIR : N° 001/DC/2016 Page 34


Y/N/P/F Core or


37 Nesting. Automatic and manual Inventory nesting is required (hybrid, serial and parallel nesting structures).

38

Inventory Display. Include but not limited to: - By Leg, - By segment, - Capacity and Subclass authorizations, - Seats Sold, - Waitlist and Staff counts, - Overbooking %, - Availability Status, - Nesting.

39 Inventory History. Ability to display real-time history of all changes within inventory by user, city, time, date …

40

Emergency Lock. Ability to place an emergency lock on a flight’s inventory and PNRs. Emergency locked inventories and PNRs are only accessible by control agents.

41

Flight Readouts. Ability to show out leg information for a flight by compartment which should contain the departure airport code, availability status, seats available or overbooked, and aircraft capacity, plus various indicator such as capacity, Block by class, capacity booked and forecasted by class, Available loads by class, Waiting list, Group, request, Single Date, Date range.

42

Waitlist. Ability to provide waitlist management process including but not limited to:

- Automatic and manual creation/ clearance, - Automatic prioritization processing, - Sales Restriction on the waitlist by : POS,

Market, flight range, specific classes ...

43 IATA Codeshare. The system must support all IATA Codeshare Options.

44

Codeshare configuration and management. Ability to provide parameter driven codeshare set-up, to facilitate easy addition and modification of codeshare agreements.

45 Shared Common Inventory. Ability to share an inventory with a codeshare partner(s).

46 Codeshare Flight number Allocation. The system must provide codeshare flight number allocation.

AOIR : N° 001/DC/2016 Page 35


Y/N/P/F Core or


47 Passenger servicing by operating codeshare partner via the codeshare PNR.

48 PNL/ADL. Ability to generate PNL/ADL for third party DCS.

49 PFS. Ability to process PFS messages by both compartment and RBD.

50

Post Departure Processing. Post departure processing should automatically update the inventory and passenger information reflecting the actual boarding statistics for a flight.

51 Group booking. Ability to handle any changes to group bookings as per AIRIMP standards.

52 POS. Point of sales management is required.

53 Arrival or departure day. Ability to handle flight arrival or departure up to +2 or -1 days.

54

Limitations. Ability to allow the following limitations on the flight:

- Number of infants according to aircraft type, - Number of WCHx, - Number of UM.

55 Archive PNR. Ability to load historical PNR data and passengers list (archive).

3. 3. Reservation and Booking management


Y/N/P/F Core or


Reservation and Booking management

1 IATA codes. The system must support all IATA & industry codes.

2 Availability display. Ability to display only available RBDs (inhibit closed RBD display).

3

Availability display. For each flight, the display must include: airline code and flight number, departure date, segment board/off cities, departure and arrival times (including next day arrival indicator), day of week, seats available by class of service, equipment, meal service, number of stops, elapsed time, mileage and e-ticket eligibility. Codeshare and alliance partners should be clearly indicated and in the case of codeshare, the operating/marketing carrier must be clearly shown.

AOIR : N° 001/DC/2016 Page 36


Y/N/P/F Core or


4

Availability display. Availability capability must include, but not limited to the following:

- By specific carrier(s), by Class, by Best price, - by direct and single stop flights, via specific

route (connecting flights), - By departure or arrival time, - Advance and go back by number of days, - Reverse availability with change of date.

5

Availability display. Should display a minimum of 8 flights per page. For the purposes of this requirement, connecting flights are included in the requirement. Therefore, a flight from A to B, connecting with a flight from B to C, would be counted as two flights. Availability displays must be page-able both forwards and backwards.

6 First Availability. Ability to display first availability by city pair, class, start date…

7

Direct Sell. Ability to sell flight direct without reference to availability display. Sell a flight by using flight number, date, O&D without any reference to an availability display is required.

8

Sell from availability. The ability to sell segments from an Availability Display by selecting the routing number and class only. If the routing number includes connecting flights they will also be sold by this single sell entry (different classes).

9 Sell Open Dated Segment. Ability to sell “open” or non-booked (ARNK) segments.

10 Booking Non-Revenue Segments. Ability to book Non-Revenue segments and have the possibility to be clearly identified in PNRs.

11

Contact Fields. Ability to : - Parameter contact field as mandatory, - Cancel or change Contact fields elements in the

PNR (e.g. Business Phone, Private Phone, Mobile Phone, Fax, Street Address and E-Mail address etc.),

- Attribute contact fields by passenger name in the PNR.

12 Class Upgrade/Downgrade. Ability to change the RBD of a segment(s) to another RBD.

13 Insert/Move/Re-arrange PNR segments. Ability to rearrange segments order in PNR.

AOIR : N° 001/DC/2016 Page 37


Y/N/P/F Core or


14

Retrieve PNR by name/flight/date. Ability to retrieve PNR by passenger name, any active flight segment & associated date. If the system cannot make an exact match a multi-selection list of possible passengers will be displayed.

15 Retrieve PNR by Host RLOC. Ability to retrieve a PNR by its unique Host Record Locator.

16 Retrieve PNR by GDS RLOC. Ability to retrieve a PNR by GDS Record locator.

17 Retrieve PNR from name list. Ability to display a list of passengers, then select and display a PNR.

18

PNR validation closure. Ability to check/alert for: - Duplicate segment, - Minimum connecting time, - Geographic and temporal continuity in the

Itinerary.

19 PNR Closure. Ability to inhibit PNR closure if mandatory fields are not completed.

20 Seatmap. Ability to display the seatmap and assign a seat.

21 SSR/OSI element. Ability to input an SSR/OSI element into the PNR as per IATA standards, (SSR FOID for E-Ticketing, APIS, special meals...).

22 SSR/OSI Queuing. Ability to queue SSR/OSI elements (immediately or deferred, depending on the departure date) to appropriate locations.

23 Auto SSR Processing by Airport, Airline, or Others. SSRs must generate messages or lists to the appropriate entity automatically.

24

Auxiliary Service Element. Ability to support auxiliary service elements that may be requested by a passenger: car rental, hotel accommodation, surface transportation and tour…

25 Name Change. Ability to change a name in a PNR.

26 Inhibit Name Change. The System must inhibit modifications to name changes, based on specific rules.

27 Cancel/Re-book. Ability to cancel some or all segments in a PNR element and re-book them for an alternative date.

AOIR : N° 001/DC/2016 Page 38


Y/N/P/F Core or


28 Display PNR data. Ability to display Normal, Complete & Historical PNRs and PNRs non-active.

29 PNR display. Ability to display the same PNR on all GDS as displayed on AIR ALGERIE’s system in term of creation, change and cancellation, and Vice Versa.

30

Display passengers. Ability to Display passengers with (not limited to):

- Holding inbound connections to the flight, - Seats selection, - Special meals, - Last booked passengers based on order, - Any AUX, SSR, or OSI element, - Holding outbound connections from this flight, - No-show and go-shows lists, - Ticketed passengers. Only entirely ticketed

passengers are selected, - Electronic tickets or are marked to have electronic

tickets flown, open, void, suspended, exchanged, refunded...,

- Unconfirmed passengers (HL, US, UU, HN), - A cancelled status on the requested segment (HX,

UC, UN, NO, XX, XL), - Display Space-available passengers (NR), - Only codeshare passengers regardless of their

status, - Passport Information, - Unaccompanied Minors (UM), - Infants and children (INF and CHD). - Gender.

31

Display OAL availability. Ability to display OAL availability.

32 OAL Booking. Ability to book OAL segments.

33 Status confirmed PNR. Booked passengers with confirmed reservations must have the following status HK, KK, and KL.

34

PNR Updates. Ability to update PNRs after flight finalization (via direct PNR updates or automated PFS message processing), e.g. identification of no-shows, modification of goshows and subsequent action to those PNRs.

35 Divide or split a PNR. Ability to separate passengers from a PNR, the original and new PNRs must be cross-referenced.

36 Retain SSRs for divided PNRs. Ability to retain any common information SSRs, contacts etc. when PNRs

AOIR : N° 001/DC/2016 Page 39


Y/N/P/F Core or


are split. Any information specific to passenger is retained or transferred to the appropriate PNR, which contains that passenger.

37 Queuing History of PNR. Ability to determine/view which specific queues a PNR has been sent to and what action has been taken at each point.

38 Active PNR. PNRs should be active in the system no less than two days after the departure date of the last segment.

39 PNR archive. PNR archiving and options for the retrieval of archived PNR for up to 10 years.

40 Public/Private Remark. Ability to introduce a public/Private remark element (free format element).

41 Group PNR. Ability to create and display group PNRs.

42 GDS Group PNR. Ability to manage group PNRs created by the travel agencies through GDS.

43 Divide PNR group. Ability to split and reduce the number of passengers in a group PNR.

44 Frequent flyer number. Ability to introduce frequent flyer details in the PNR. It should be possible to cancel or change these details.

45

Customer profile. Ability to retrieve and display complete customer profile.

46 Customer profile. Ability to Create PNR from customer profile.

47 Enroll customer. Ability to enroll customer in FFP from reservation system.

48

Miscellaneous support functions. Ability to provide: - Encode-Decode, - World city time / Airport information / Other

information, - Timatic, - Help, - Information Display System (IDS).

49 Codeshare PNR. Ability to create, display and manage seamless codeshare PNRs.

50 E-Ticket Segments. All sold segments must clearly indicate eligibility for E-Ticketing.

AOIR : N° 001/DC/2016 Page 40

3. 4. Ticketing and EMD


Y/N/P/F Core or


Ticketing Management

1

Compliance with Industry Standards. Compliance with all Industry standards is required including but not limited to:

1) Request/push control of ETR coupons between IET carriers.

2) Current IATA EDIFACT/PADIS messaging standard in order to exchange e-Ticketing data between airline carriers,

3) E-Ticket processing at stations with third party ground handling,

4) Support for conjunctive e-Tickets with the industry standard of sixteen coupons,

5) Support of the most recent CRS/GDS/EDIFACT version for the exchange of ticket data from the GDS to the validating carrier for both e-Tickets.

2 System Controls. Parameters are required to enable controls in regards to partners and GDSs, e.g. Carrier eligibility table.

3 TST. Ability to display Transitional Stored Ticket.

4 Ticketing Functionalities. Ability to allow E-Ticket exchanges, add, collects, re-price and re-issue, refunds, voids, suspend and revalidate.

5

Link Records. Functionality is required to link E-Ticketing records to one or more segments in multiple PNRs and/or to name, coupon, and segment automatically.

6 Auto price all PNRs. Ability to price automatically PNRs by the system.

7 Automatic refund and exchange. Ability to exchange and refund E-tickets automatically.

8 Coupon status. Ability to support manual change Coupon status by duty code.

9

ETKT display. Ability to display the same ETKT elements on all GDS and IET carriers as displayed on AIR ALGERIE system regarding creation, change and cancellation.

AOIR : N° 001/DC/2016 Page 41


Y/N/P/F Core or


10 Display Single Electronic Ticket Record (ETR). Ability to display ETR by ticket number, record locator, FOID or name/flight/date/Segment.

11

Display Multiple Electronic Ticket Records (ETR). Ability to display all ETRs by board point city, carrier/flight number or by frequent flyer number…

12

E-Ticket History Display. Ability to: - Display used E-ticket online 60 days at least; - Retrieve E-ticket/TST/TSM purged files

(Archives).

13 E-Ticket customization. Ability to customize E-Ticket receipt.

14 E-ticket issuance. Ability to issue E-tickets through all distribution channels.

15

Printing. Ability to support the printing of coupons, receipts and itinerary/receipts. Itinerary/receipt, itinerary outputs (carrier name…) must be converted from the ticket into a plain language itinerary. It must be possible to send ticket receipts by email.

16 E-TKT/DCS. Ability to handle E-TKT with other DCS.

17 Fares Interface. Ability to interface E-Ticketing with Fares system.

18 Interline Partners & Codeshare. Ability to support IET standards and codeshare options.

19 FOP. Ability to support multiple forms of payment (CC, Invoice, Miles, check, cash…)

20

Sales Reporting. Ability to provide Sales reporting by office, by agent with all transaction details for: - E-ticket sales, service fees and EMD, - Reissues, void and refunds of E-tickets

21

Daily Sales Reporting. Ability to manage finalization sales report manually or automatically for each ATO/CTO every day based on local time.

AOIR : N° 001/DC/2016 Page 42


Y/N/P/F Core or


EMD Management

22 EMD Type. Must support both EMD types associated and standalone.

23 EMD issuance, change, cancellation and management must be compliant with Industry Standards.

24

Auxiliary Services. Ability to issue EMD for auxiliary services that may be requested by a passenger: car rental, hotel accommodation, surface transportation and tour…

25 Retrieve EMD. Ability to retrieve EMD by Name/City pair/Flight number/Date/EMD record.

26

The system must allow: - EMD archiving, - Interline EMD management, - EMD reporting, - EMD issuance by external systems (GDS), - Ground Handling EMD (external DCS).

3. 5. Departure Control System


Y/N/P/F Core or


Passenger processing & Flight Control Management

1 RES & DCS Access. Access to some reservation functionalities (PNR, E-TKT, EMD, customer profile, flight program…) through DCS workstation.

2 Integration. The RES/INV/FFP/DCS modules must be fully integrated and all process must be integrated across all modules.

3

CUTE and back office. The DCS must be certified Common User Terminal Emulation (SITA CUTE, ARINC MUSE, RESA CREWS …) and can be used on back office.

4

DCS version for GHA. Ability to process AIR ALGERIE flights without a reduction in functionality or degradation in the level of services offered when the GHA is using the same DCS solution.

5 Interface. Ability to be interfaced with:

- Revenue accounting system,

AOIR : N° 001/DC/2016 Page 43


Y/N/P/F Core or


- Catering system, - Cargo system, - Baggage reconciliation system (BRS), - Schedule system (Flight and crew), - Flight planning system, - ACARS, - Central Flow Management Unit (Eurocontrol), - Aircraft data links system.

The supplier must provide a list of the available interfaces for the systems above.

6 WorldTracer. Ability to access WorldTracer and its functionalities via DCS.

7

Additional Information for Agents. Ability to support special displays and interfaces to provide enhanced information to check-in agents :

- Encode-Decode, - World city time / Airport information / Other

information, - Timatic, - Help.

8 EDIFACT format. Ability to support standard EDIFACT format and its variants.

9 Capture information. Ability to capture passenger information from MRZ on documents automatically upon swipe/scan.

10

Other Devices Access. Ability to support access by structured data from intelligent devices (e.g. self-service units, hand-held devices, gate readers, OCR/MSR devices …). It must support multiple devices on one workstation.

11

Boarding Pass and Bag Tag Printers. Ability to allow a default boarding pass and Bag Tag printer for each workstation whether the system is accessed via session, internet or Web.

12 Printing. Ability to issue boarding pass and tag bag according to the loaded PECTABs in the system.

13

Print Options. Ability to support the printing in hardcopy form all types of passenger informational displays either as a “screen dump” or specifically formatted for hardcopy. Printing must be to any host defined output device.

14

PECTAB. Ability to send an AEA Parametric Data Concept message for bag tag and boarding pass to host or cute devices. Layout/format, bar codes, human readable letters/numbers in the PECTABs are defined by AIR ALGERIE and must comply with all

AOIR : N° 001/DC/2016 Page 44


Y/N/P/F Core or


IATA Standards.

15 PECTAB. Ability to print Arabic characters and graphical forms (logo …) in the boarding pass.

16 PECTAB Updates. Ability to change the PECTAB tables and to control/manage the changes with regard to the BP/BT documents used in each station.

17 RFID. Ability to generate RFID tags and support all related functions to RFIDs (e.g. tracking and locating etc.)

18 Text and remarks. Ability to add free format text and remarks on the boarding pass.

19

Aircraft Configurations. Ability to cater for all aircraft types which are utilized through the RES application but also to cater for different seat configurations for all of these aircraft (many to one correlation).

Ability to cater for aircraft types and seat configurations which will be input manually and not come from the RES system.

There should be no restrictions on the number of aircraft types or the number of configurations per aircraft type for the DCS application.

20

Aircraft Types-View & Copy. Ability to display all aircraft types and their configurations. It must be possible to copy and then amend a type/configuration to create a new aircraft type/configuration.

21

Aircraft Types-Create. Ability to configure each aircraft and add the configuration into the database in a swift and accurate method according to the standard format.

22

Online Aircraft Changes. Ability to cater for late equipment changes, reweighs/reconfigurations. These changes must be updated in the reservation and inventory systems.

23

Seat Characteristics. Ability to support all standard seats types’ characteristics. e.g. : window seat, aisle seat, over wing, forward, rear, restricted recline, exit row, basinet row, permanently blocked seat ...Plus, seats characteristics which are user definable.

AOIR : N° 001/DC/2016 Page 45


Y/N/P/F Core or


24

Seat Characteristics Amendment. Ability to amend individual or groups of seats’ characteristics for specific aircraft and/or aircraft type either immediately or from/to a specific date. An ad-hoc provision to change a seat or group of seats for a flight segment is also required.

25 Seatmap. Ability to show all facilities in the seatmap, e.g. toilet and galley.

26

Change Seat Assignment. Ability to change seat assignment with automatic generation of new boarding pass and check-in agent warning. It must be possible to override the system and assign seats that would not normally be applicable to the passenger or to upgrade/downgrade them into another cabin.

27

Inhibited Seat Assignment. Ability to inhibit seat assignments (e.g. no infants in exit rows). Wherever possible this should be warned automatically by the system, with the capability to override manually.

28 Pre-Assigned Seats. Ability to edit/release any pre-assigned seats and/or protected seats both manually and based on system time parameters.

29 Re-assign Seat. Ability to provide the functionality to re-seat or offload/delete a checked-in/boarded passenger either individually or by groupings.

30 Non-reservations Flight Creation. Ability to create revenue flights, charter flights, cargo flights, Ground Handling flights, test flights, pseudo flights…

31

Flight status. Ability to support the following flight status:

- Flight editing, - Check-in Suspended, - Flight Open for check-in from all channels, - Flight Held, - Flight updated, - Flight closed for check-in, - Flight gated, - Flight finalized, - Post Departure.

32 Flight Amendment. Ability to add a leg to an open flight without any disruption for the check-in process.

33 Re-open Flight. Ability to re-open a post departed flight with single or multiple legs (the ability to open any leg).

34 Ability to manage a flight from the diverted station.

AOIR : N° 001/DC/2016 Page 46


Y/N/P/F Core or


35 Online Flight Changes. Ability to accept late flight changes, and must be updated in the inventory system.

36 PNL/ADL. Ability to support PNL/ADL processing (codeshare flights, third party…).

37

Flight open. Ability to open Flight for specific check-in channels based on configurable parameters: Airport check-in, Inbound Through Check-in, Web check-in.

38 Online/Offline. Ability to set and manage a station as online or offline (station handled in a different DCS).

39

Stations. Ability to identify the stations for which General Declaration (GD) is required, and maintain this list of stations. The GD must be sent automatically.

40

Government order. Ability to set a flight as eligible for API/APP/AQQ/PNRGOV/iAPI printing of the boarding pass is inhibited until the complete API data are submitted.

41

New Regulations security/immigration processing to support control authorities. Ability to comply with any future Government initiatives before the compliance date set by the Government.

42 US DOT. The DCS must be certified to work with the USDOT/TSA and support existing regulations.

43

Watch lists. Ability to check passengers API based on the match of SPL (Specified Persons List) and the Black list for flights to Canada and USA. The printing of the boarding pass must be inhibited in case of mismatch and the check-in agents prompted. The database must be regularly updated.

44

Limitations on the flight. Ability to allow the following limitations on the flight :

- Number of infants according to aircraft type, - Number of WCHx, - Jump seats, - Number of passengers in the waitlist...

45

ETKT/PNR access. Ability to retrieve and display the passenger’s PNR and ETKT from DCS, via a line number reference, or seat number reference, boarding number, a bag tag number or PNR code.

AOIR : N° 001/DC/2016 Page 47


Y/N/P/F Core or


46

Single/Multiple Remarks. Ability to enter public and/or private remarks (refer to RES requirements) for passengers selected from a display (i.e. one or more passengers). This functionality should allow one or more remarks to be entered into all PNRs selected.

47

SSR/OSI Codes. The application must process SSR/OSI elements at check-in and provide the check-in agent with adequate information to pass onto the customer, e.g. advice to the passenger on whether or not a request has been or can be fulfilled.

48 Frequent flyer number. Ability to check and validate the frequent flyer number with regard to the customer profile.

49 FQTV Validation. Ability to validate FQTV in DCS for other airlines program according to the bilateral agreement.

50

Flight displays. Ability to display : 1) General flight information (flight number,

routing, time, registration, configuration, ...); 2) Commercial flight information (flight number,

figures of passengers booked, checked-in, waitlisted, infants and Childs, codeshare information, meals, ...);

3) Operations flight information (Dry operating weight/index, pantry and hold versions ...);

4) Baggage information (bag count, weight summary, different lists of all bags assigned to a flight, whether associated to a passenger or not …).

5) Boarding information.

51

Arrival/departure flights. Ability to display arrival/departure flights list by date :

- Flight number - Destination - STD/STA - ETD/ATD - ETA/ATA - Aircraft registration - Number of passengers booked - Flight status - Terminal - Gate number.

AOIR : N° 001/DC/2016 Page 48


Y/N/P/F Core or


52

Check-in Displays. Ability to provide various displays of inventory levels by cabin, which include seating capacity, seats booked (from inventory), available seats, seating limits, checked-in and accepted passengers, protected seats, number of passengers on standby, desiring through passengers and the remaining number of passengers to check-in, goshow, ID, special ID etc. Provide flight counts throughout check-in process and reconciliation information at flight close-out.

53

Passenger Lists. Ability to display passenger and standby lists including “logical opposite” options such as “Non-Checked in”, All lists as defined in Reservations e.g.: list by class, by SSRs, …

54

Passenger Check-in list Display is required : - Flight number - Full name - Gender - Seat number - Baggage Piece/Weight - Class - Segment - Checked-in by - SSR and comments - Check-in status

55

Passenger Display Check-in. Ability to support passenger check-in from a passenger list or full passenger display (i.e. supplying the line number for a single party or multiple numbers/range of numbers for multiple party check-in).

56

Passenger Name Check-in. Ability to support passenger check-in by a portion of passenger name, including providing a Similar Names List from which to select, if similar names exist. Example, require agent to enter only first two characters of passenger name, followed by number in party.

57

Multiple Passenger Name Check-in. Ability to support multiple passenger check-in by a portion of more than one passenger name, including providing a Similar Names List for both passengers from which to select, if similar names exist. Example, require agent to enter only first two characters of each passenger’s name, followed by number in party.

58

Partial PNR acceptance. Ability to support Partial PNR processes, e.g. only one passenger from a PNR checking-in with others either checking in at a subsequent time or being treated as no-shows. The

AOIR : N° 001/DC/2016 Page 49


Y/N/P/F Core or


application should automatically attempt to reserve suitable seats for other passengers in the PNR so that they will be seated together if possible.

59 Cancel Check-in Transaction. Ability to cancel all incomplete (pending) check-in requests.

60

Pseudo Groups/Parties. Ability to identify passengers who have been checked-in together even though they are traveling on different PNRs (i.e. pooling).

61 Upgrade/Downgrade. Ability to manually upgrade or downgrade a passenger into a different cabin and or class.

62

Upgrade/Downgrade. Ability to provide a mechanism to manage Upgrade/Downgrade lists. This includes passengers being automatically or manually placed on such lists at the time of check-in or subsequent to check-in based upon system parameters. The ability to identify upgraded/ downgraded passengers as voluntary or involuntary.

63 Check-in inhibition. Ability to inhibit check-in without an E-ticket number.

64

Accumulate weight. Ability to accumulate the total weight of all checked-in bags, with possibility to print each piece weight on the tag bag in addition to the total weight of all bags.

65

Bag Tag from Passenger Display. Ability to support issuing bag tags from a passenger list or full passenger display (i.e. supplying the line number for a single party or multiple numbers / range of numbers for multiple bag tag issue).

66

Replacement Bag Tags. Ability to replace previously issued tags. The original bag tags would be deleted/cancelled and the new ones would reflect the checked baggage. A record of old/deleted bag tag numbers would retain.

67

Excess baggage : - Apply IATA Resolution 302 ABR bag rules and

rates to calculate excess baggage fees. - Ability to prompt total excess baggage amount,

calculated based on the total excess weight and the baggage rate for the destination

- Must be detected based on ticket allowance and other allowances and waivers, as defined in the system. The waivers and allowances include but will not be limited to:

AOIR : N° 001/DC/2016 Page 50


Y/N/P/F Core or


* Frequent flyer entitlement, * Agent discretionary waivers * Prepaid bags

- Restrict the boarding pass print. This setting shall be configurable.

68

Excess Baggage Coupon. Ability to print excess baggage coupon by weight and piece. The coupon must include:

- Flight number, - Routing, - Passenger name, - Sequence number, - Excess baggage weight, - Number of extra pieces.

69

Re-issue Boarding Pass. Ability to reissue a previously issued boarding pass. The check-in agent should be prompted to retrieve the original boarding pass from the passenger.

70 Payment Collection. Ability to collect ancillary services fees and issue EMDs.

71

Bulk Transfer. Ability to bulk transfer passengers (whether checked-in or not, standby...), with all their relevant information, from one flight to another and from one airport to another.

72 Disruptions managements & Automatic Seat Re-accommodation in case of flight equipment change.

73 Flight Interruption Manifest. Ability to support FIMs according to IATA recommendations.

74 Codeshare flight. Support operating carrier and marketing carrier flight numbers and carrier codes for IATCI down-line connections.

75 Codeshare Tags. Ability to print the true operating carrier flight number on the bag tag as required.

76

IATCI. Ability to support all IATCI standards and recommended practices including Interline Fall Back (IFM) messages and bi-directional messages for Through Check-in.

77 Connection Flight Data. Ability to add manually connection flight data to a passenger’s DCS records and automatically perform through check-in.

78 Through/Transit Passengers. Ability to manage Through/Transit passengers in the same manner as originating passengers are handled.

AOIR : N° 001/DC/2016 Page 51


Y/N/P/F Core or


79

Non-Revenue Passengers. Ability to provide a mechanism to manage Non- Revenue passengers and identify Non-Revenue passengers based on UL rules at all stages of the check-in process.

80

Auto Seat or Standby. Ability to auto-examine the availability of seat upon check-in and either assign a seat or a standby priority. The check-in agent must be prompted when a passenger goes on standby and the printing of boarding pass is inhibited.

81

Standby Handling. Ability to provide a manual and automated management of standby passengers revenue/nonrevenue, based on business rules.

82 Cockpit Access. Ability to support the assignment of Jump Seats and cockpit seats for qualified personnel.

83

Jump seat. Ability to show Jump seat passenger figures in : - Passenger manifest - Total checked-in figures - Relevant post departure messages - BSM for the baggage accepted

84 Passenger Boarding/De-boarding. Ability to mass board/de-board the aircraft (Automatically or manually).

85 Gate Assignment. Ability to assign flights to a gate and change the gate assignment as required.

86 Boarding documents. Ability to generate boarding documents for control e.g.: PIL, passengers’ counts, missing passengers report…

87 Meal calculations. Ability to calculate the expected number of meals in each cabin.

88 Messages Addresses Ability to support an unlimited number of addresses to receive check-in and loading messages as the flight is closed out.

89

Post-Departure Messages. Ability to generate all lists and send (automatically or manually) all IATA standard messages at flight departure such as FTL, PSM, PTM, SOM, TPM, and IDM...

90 Inhibit messages generation. Ability to inhibit messages generation for Training flights, Test flights …

91 PFS Codeshare. Ability to support a split PFS messages for codeshare flights.

AOIR : N° 001/DC/2016 Page 52


Y/N/P/F Core or


92

Flights processing. Ability to default any session to any flight (one or multiple flights). This enables the check-in agent to input transactions without the need to repeat the flight number and date in the input.

93 Flights processing. Ability to process multiple flights on the same screen.

94 Ramp management tools. Ability to manage/coordinate Ramp tasks.

95

History transactions. Ability to capture all flight transactions for any level and retrieve the report online (the supplier must specify the number of days that history is Available in the system).

96 Reports. Ability to provide different reports by agent code e.g. Number of PAX checked-in …

Load Control

97 Centralized Load Control. Ability to support Centralized Load Control including multi flight handling.

98 Integration. Weight & Balance and check-in functionalities must be fully integrated within DCS.

99

User profiles. Ability to allow the creation and differentiation of user profiles e.g. load control Supervisor / Agents etc. and provide secure single login feature.

100

Display of flight progression. Ability to provide a display of flight progression including (but not limited to):

- Up line release, - Aircraft registration, - Transit passenger / baggage details, - LDM/CPM from non-mechanized, - Load Instruction generated, - Fuel Sheet / ZFW message generated, - Check-in linked, - Passenger seating completed, - Flight Status (Open, Closed, Suspended, Hold, Released), - Check-in / boarding Status (Open, Closed, Released, Unavailable), - Load Sheet generated, - Close out messages sent.

101 IATA standard formats. Ability to support IATA standard formats for load sheet/load plan/NOTOC

AOIR : N° 001/DC/2016 Page 53


Y/N/P/F Core or


and other load-planning related messages.

102 IATA messages. Ability to process incoming LDM, LPM, and CPM messages from an up-line station with third party mechanism.

103 Supplementary information. Ability to display and update supplementary information that may be associated with all types of messages.

104

Capturing of changes. Ability to capture the changes of cargo/mail/baggage/COMAIL made by local airline personnel at stations as defined by the business rules.

105

Aircraft Types. Ability to support these aircraft types :

- narrow / wide bodied, - Multi deck, Combis and freighters. -

106 Multi sector / charter / ad hoc. Ability to support transfer / multi sector / charter / ad hoc flights.

107 Aircraft changes. Ability to support aircraft changes automatically or manually actioned by load control.

108 Lock/unlock. Ability to provide the facility to lock, unlock a flight and cancel a flight from the System.

109 Estimated zero fuel weight. Ability to provide Estimated zero fuel weight information and fuel data to/from Flight Planning System.

110 Standard IATA UWS. Ability to receive standard IATA UWS cargo messaging for load planning and finalization.

111 Graphical aircraft loading. Ability to support graphical aircraft loading capabilities (move/swap/drag/drop load items).

112 Hosting OAL. Ability to host other airlines for load control.

113 Creation of flights. Ability to support creation of flights at departure, en-route and diversion stations including offline stations.

114

IATA load control documents. Ability to provide generation and printing of IATA load control documents including graphical for (but not limited to):

- Load Instruction Report, - Provisional / Final / ACARS Load Sheet, - ZFW Messages, - Fuel Loading Instruction, - NOTOC documents.

AOIR : N° 001/DC/2016 Page 54


Y/N/P/F Core or


115 Load planning. Ability to provide a customer-configurable table of passenger and baggage weights to be used for load planning purposes.

116 Weight table. Ability to change passenger/baggage weight table (load planning or check-in) for a flight.

117 Load sheets via ACARS. Ability to provide the facility of sending load sheets via ACARS.

118 ACARS messaging. Ability to provide free format ACARS messaging with option to inhibit by location, sign-in level, etc.

119 Preplanning purposes. Ability to store historical data in the system for preplanning purposes.

120 Trimming. Ability to support trimming by:

- class/cabin & seat row, - compartment/bay.

121 Adjustable and restricted weight. Ability to support maximum, adjustable and restricted weight and trim limitations for ZFW, TOW, LDW, RTOW, TW.

122

Control parameter. Ability to automatically calculate, recalculate and validate the control parameter as and when any cargo, mail, baggage weight / passenger weight / crew / catering or placement data is added, modified, or deleted from external system or DCS.

123

Graphical presentation of balance conditions. Ability to provide a graphical presentation of balance conditions, including Ideal Trim Range / C of G for ZFW, TOW, LDW and MAC. Different colors are used to depict different limits.

124 Baggage classification. Ability to support all types of baggage classification. E.g.: BF, BC, BY, BT, BR …

125 Local / transfer dead-load. Ability to provide a display of all local / transfer dead-load.

126 Auto-load distribution. Ability to support auto-load distribution with optimal balance.

127 Dangerous Goods conditions. Ability to incorporate Dangerous Goods conditions.

128 Loads transfer. Ability to support all loads transfer.

129 Jump seats. Ability to display jump seats on the load-sheet.

130 LDP documents. Ability to store/retrieve/reprint all LDP documents (load-sheet, load-plan …).

AOIR : N° 001/DC/2016 Page 55


Y/N/P/F Core or


131 Out of balance limitations. Ability to alert for any out of balance limitations.

132 Balance condition. Ability to adjust balance condition by offloading manually an overloaded aircraft.

133 Final weights. Ability to use only final weights after flight closure.

134 Validate flight closure. Ability to validate flight closure and load sheet issuance according to capacity limitations.

135 AHM 560 & 565. Ability to support AHM 560 & 565.

136 IATA 560 & 565 format. Ability to print database in standard IATA 560 & 565 format.

137 Static database. Ability to manage static database (display, add, update, delete …) according to user authority.

138 ULD database. Ability to provide ULD database, to include individual / ULD type tare weights and ULD numbers according to business rules.

139 Display/re-print. Ability to display/re-print load-sheet, load plan and NOTOC after departure.

140 Real time history. Ability to display all users’ transactions.

3. 6. Fare Quote System


Y/N/P/F Core or


1 ATPCO and SITA database. Ability to collect from both ATPCO and SITA all fares and rules. The supplier should indicate the update frequency.

2 ATPCO categories. Ability to support all ATPCO categories from 00 to 50, YR/YQ/ optional services/ routing/ footnote/ taxes.

3 Display Fares. Ability to display all fares by O&D from low to high.

AOIR : N° 001/DC/2016 Page 56


Y/N/P/F Core or


4 Multiple options. Provide the ability to retrieve fares with multiple options, e.g. Private fares, Passenger type and Fare type.

5 Display Fares. Ability to display fares with or without taxes before creating PNR.

6 Carrier general rules. Provide the ability to retrieve AH and OAL general rules.

7 Rule content default. The System must ensure that rule content default is ATPCO.

8 Rule content. Ability to display a summary of any rule.

9

Best Buy pricing from fares. Ability to display the “lowest fare” by sorting fares over through fares in order, from low to high. If a date is included in the input, only those fares valid for that date are considered. Ability to automatically create an itinerary for the chosen option without manually booking flights.

10 Best Buy pricing from availability. Ability to easily select the cheapest available flight segment from an availability display.

11

Best Buy pricing from Itinerary. Ability to easily select the cheapest available class from an existing itinerary and to re-book the relevant segments with the cheaper class in a single transaction.

12

Basic fare information. Ability to provide the minimum requirements for basic fare information as per industry standard such as fare basic code, booking class, carrier, etc.

13

Additional information. Ability to retrieve additional information based on :

- RBD by carrier, - Routing, - specific rule category, - Taxes/fees (ATPCO service fees)/other

charges.

14 Additional information. Ability to retrieve distance between cities/airports (kilometer, miles).

AOIR : N° 001/DC/2016 Page 57


Y/N/P/F Core or


15

Currency. Ability to retrieve fares in more than one currency at one time sorted by currency. Convert to any currency regardless of currency field.

16 Specific Exchange Rate. Ability to provide user option input to select specific exchange rate or multiple exchange rates for currency conversions.

17

Pricing currency. Ability to price: - Itinerary using specific currency, - In currency of choice unless inhibited by AH

specific rules or government regulation.

18 Specific rule entries. Ability to provide specific rule entries by carrier/IATA fares, city pair, fare-basis code, rule number.

19

Fare calculation element. Price itinerary with details of each fare calculation element ( but not limited to fare basis ) including taxes and tax type, passenger facility charges (PFCs), Global Indicator, currency, fare including base, tax, total, surcharges, ROE.

20

Price itinerary. Ability to price with specific segment, multiple segments, combined with any one or combination of : Specified fare basis, discount amount/percentage, passenger type(s), override connection/stopover, point of ticketing, side trip, tax exempt, tax (es), validity dates, restricted fares…

21 Open segments. Provide the ability to price open segments.

22 Segments out of sequence. The System must inhibit auto-pricing of segments out of sequence in a single PNR.

23 Pricing. Ability to manage different IATA pricing controls.

24 Price. Ability to price automatically all trip types (OW/RT/OJ…).

25

Reason for failure. Ability to provide the reason for failure when the itinerary does not price as booked, the system must provide options for the itinerary (e.g. minimum stay not met, fare combinability …). If necessary the system must

AOIR : N° 001/DC/2016 Page 58


Y/N/P/F Core or


provide normal fare of the relevant cabin otherwise IATA fares.

26 Zone Employee Discount (ZED) fares. Ability to price ZED fares and calculate the taxable amount for specific countries.

27 Discount. Ability to price a fare where a discount is applicable from unrestricted fare.

28 Re-price/Refund. Ability to auto re-price/refund itinerary in the PNR.

29

Fare Calculation Mode Indicator. The system must have the facility to apply Fare Calculation Mode Indicator (FCMI) to all types of tickets (E-ticket, EMD).

30 Manual fare calculation. Ability to build a manual fare calculation to drive a ticket applying industry standard formats.

31 History. Ability to provide history for all fare and rule transmissions at minimum 12 months.

32 Exchange Rate. Ability to provide history of all exchanges rates within system window at minimum 12 months.

33 Online Query. Ability to provide online query to access all historical fare and rule data.

34 Flexible sort order. Ability to process according to a flexible sort order.

35

BSR/BBR. Ability to Update/process BSR/BBR/IROE according to industry standards (IATA resolution 024 series). Use ICH 5 day rate when standard industry source are not found in the IATA resolution 024e series.

36 ICH/BSR/BBR/IROE. Ability to retrieve all or specific current exchange rates for: ICH/BSR/BBR/IROE.

37

Rounding Principles. Process the rounding principles according to IATA resolution 024d for fares and other charges and amounts truncated for currency conversions.

AOIR : N° 001/DC/2016 Page 59


Y/N/P/F Core or


38 Fare Construction Principles. Ability to enforce all fare construction principles according to the IATA resolution manual for composite.

39

Free Baggage Allowance. Ability to retrieve all carriers free baggage allowance per carrier including dimensions for all points or by city pair or origin/destination countries filed in ATPCO.

40

Excess Baggage Charges. Ability to retrieve all carriers’ excess baggage charges per carrier including dimensions for all points, by city pair or by origin/destination countries.

41 Taxes/Fees/Surcharges. Ability to retrieve all applicable taxes/ fees/ surcharges by country or by city pair.

42 Calculation Mileage. Ability to support TPM and MPM calculation Mileage.

43 Mileage. Ability to calculate mileage for a string of cities w/o PNR (including carrier, surface sectors, global indicators, fare amount).

44

Corresponding fare. Ability to return fare corresponding to the available inventory (availability of seats in the flight in the particular RBD). The system should price the lowest fare according to the RBD available.

45

Remark. Ability to generate automatically a remark for specific fares according to passenger typology (e.g.: generate remark for special discount for infant to provide document proof).

3. 7. Revenue Management System


Y/N/P/F Core or


Revenue Management System

General :

1 Integration. Must be Integrated with Inventory.

2 Revenue Accounting Data. Ability to process Revenue Accounting data.

AOIR : N° 001/DC/2016 Page 60


Y/N/P/F Core or


3 Ability to provide a leg based system.

4 Ability to be upgradeable to O&D system.

5 Ability to support connecting and multi-leg/Circular flights.

6 Ability to control economic, business and first cabin.

7 Ability to control code share flights.

8 Ability to consider program irregularities and update automatically data after every change made to flights in the inventory.

9 Ability to update automatically the set of historical flight every night with the departed flights.

10 Ability to ensure a competitive intelligence.

11 Ability to handle more than 26 classes.

12 Ability to take into account the waitlist in the flights.

13 Ability to store data minimum 10 years for forecasting and reports.

14 Web data provider integration is required (QL2, INFARE or any other solution).

15 Ability to control by Point of sell, GDS and CRS.

16 Ability to manage and influence forecasting and optimization process.

17 Ability to detect and alert when flight data failed to be received or to be transmitted.

18 Ability to provide a guidebook related to the Revenue Management System.

Forecasting

19 Ability to provide different forecasting models.

20

Ability to provide forecasting according to historical data per: - flight/segment/leg/market/network, - Date/Range date, - Class/Cabin.

AOIR : N° 001/DC/2016 Page 61


Y/N/P/F Core or


21

Ability to forecast by taking into account: demand, load factor, No-Shows, cancellations, upgrading, spoilages and expected to-board passengers at booking class level…

22 Ability to take into consideration market growth/decline and sudden change in market.

23 Ability to take in consideration Pricing elasticity and business rules.

24 Ability to handle events calendar.

25 Ability to take into account competitors practice.

26 Ability to detect and alert abnormal flights.

27 Ability to manage manually and/or automatically forecasting of flights (e.g.: date level, include or exclude given flight in historical data…).

28 Ability to display the history for all manual or automatic actions taken during the flight's life cycle (changes in controls and forecasts…).

29 Ability to store all the actions performed by the user and the forecasting provided by the system.

Optimization

30 Ability to provide several statistical model of optimization (EMSR, EMSR b…).

31 Ability to take into consideration competitors based on departure time, arrival time and route…

32 Ability to take into account the competitor's fares to re-optimize on real time with user validation.

33 Ability to fill and extract data automatically and frequently.

34 Ability to provide analysts flight re-optimization according to predefined parameters.

35 Ability to provide different nesting (serial, hybrid, mix...).

36

Ability to alert analyst for flights presenting risk of spoilage (low booking classes closed too early or low booking classes still available despite valuable demand).

AOIR : N° 001/DC/2016 Page 62


Y/N/P/F Core or


Overbooking

37 Ability to apply overbooking per flight, cabin, class, date…

38 Ability to take into account cost of cancellations and no-shows.

39 Ability to include or exclude reservation classes defined by the user

40 Ability to alert analysts for flights presenting risk of denied boarding.

41

Ability to compute and display departure day indicators including, but not limited to indicators such as Expected Revenue, Expected Load Factor, Passenger Expected Load Factor,...

Reporting

42 The system must generate reporting with different format (text, excel, word document, PDF…).

43

The reports must include, but are not limited to the following information: Reservation, Inventory Departure Control, Forecast, Optimization, Fare data…

44

The system must be able to : - Select a variety of fields according to user

criteria, - Provide report about all user's actions.

45

Ability to provide reports per log date for specified periods (year, month, dates) according to a market, network, routes, flight number, cabin compartment,….

46 Ability to provide reports per (including but not limited to) O&D, POS, flight number…

47

Ability to provide reports including but not limited to load factor, booking by class/cabin, estimated revenue, risks management, overbooking, no show, waitlist,...

48 Ability to provide reports including traffic distribution by segment/leg for multi leg/circular flights.

AOIR : N° 001/DC/2016 Page 63


Y/N/P/F Core or


49 Ability to establish comparison based on periods having all classes, schedule, booking rates...

50 Ability to provide categorization tables.

51 Ability to provide reports about availability by class.

52 Ability to provide reports about competitor's fare availability.

53 Ability to provide reports about performance ratios by flight analyst.

54 The system must provide reports about abnormal flights presenting false or missing data.

55 The system must provide reports about pertinence of forecasting and optimization

Group Management

56 The RMS must include a Group management module.

57 The Group module must be integrated with the inventory system.

58 Revenue Accounting Data. Ability to process Revenue Accounting data.

59 This module must Manage PNR Group creation, cancellations, amendments, payments and historical Groups.

60 Must provide the ability to adjust manually G class parameter.

61 The system must provide Group quotation methods (individual movement and others)

62 The system must be able to automatically generate groups fare quote.

63 The system must provide an evaluation of the expected recipe (positive/negative) once the Group is accepted.

64 In case of a negative recipe, the system must provide alternatives (offer a rerouting, flight change…).

AOIR : N° 001/DC/2016 Page 64


Y/N/P/F Core or


65 The system must be able to store Group's characteristics (size, dates, and destinations).

66 The system must be able to forecast about the realization rate of the group.

67 Ability to generate the re-optimization of the flights in case of group cancellation.

68 Must provide an evaluation rate of the flight.

69 Ability to manage Groups requests in one way and round trip.

70 Must provide evaluation report.

71 Must provide reports about No Show, payment and sites creators of Groups.

72 Ability to manage Groups requests collected from travel agencies.

73 Ability to set and enforce checks for Groups (deposit time limit, ticketing time limit…).

3. 8. Revenue Integrity


Y/N/P/F Core or


Revenue Integrity Management

1 Integration. The system must be integrated with all PSS modules (reservation/ticketing, inventory, DCS…).

2 Time Limit Management. Ability to manage Time limit controller.

3

Time Limit Controller. Ability to provide a Time Limit Controller for: - Un-ticketed individual PNRs segments; - Un-issued EMDs for chargeable services.

4

Time Limit Controller. Ability to provide a Time Limit controller for PNRs group to enforce compliance with Group Deposit, Names, and Ticketing requirements.

AOIR : N° 001/DC/2016 Page 65


Y/N/P/F Core or


5

Ability to detect : - MCT violation; - Impossible journeys according to business

rules; - Redundant segments; - Churning PNRs.

6

Duplicate PNRS. Ability to detect duplicate PNRS for Overlapping flight times and Incoherent or duplicated segments / O&D itineraries according to defined rules such as :

- Name Comparison - Information from the PNR (passenger contact,

FFP number, Gender, APIS, Date of birth).

7 Fictitious and Suspicious Names. Ability to detect Fictitious and Suspicious Names and control name changes according to defined rules.

8

Hidden Groups. Ability to detect hidden Groups according to defined rules such as :

- Same market/flight and travel date; - Departure time within defined criteria; - Booked or last changed on the same calendar

day; - Same Class(es); - Booked by same booking office (IATA/Pseudo

City Code or Booking Office ID) - Total passengers in combined PNRs.

9 Waitlist clearer. Ability to Remove waitlisted segments present in PNRs (waitlist clearer).

10

Synchronize E-Ticket. Ability to Synchronize E-Ticket to reservation and control all reservation changes (e-ticket mismatches, manual associated e-tickets …).

11 E-Ticket Control. Ability to detect and cancel PNRs with voided and refunded E-Tickets according to business rules.

12 EMD de-synchronizations. Ability to detect EMD de-synchronizations.

13 Control and audit. Ability to control and audit in real-time all unusual sales for agencies.

14 Passive booking. Ability to detect Passive booking (Passive requests not matching any active booking).

AOIR : N° 001/DC/2016 Page 66


Y/N/P/F Core or


15 Control E-ticket. Ability to control E-ticket match to the flight (passenger name, class, route, carrier, flight number, date, infant indicator …) at check-in.

16 Coupons order. Ability to control the use of coupons in the correct order at check-in.

17 Typological Fares. Ability to control validity of Typological Fares at check-in.

18

Go-show Handler. Ability to check if passenger RBD of fare is valid for go-show when checked-in and update the PNR according to business rules.

19 No-show Handler. Ability to detect any booking with a no-show passenger as defined and update the PNR according to business rules.

3. 9. E-Commerce


Y/N/P/F Core or


IBE management

1 Integration. Ability to interface with PSS components, loyalty system, and AH corporate web site.

2

Integration with AH web site. Ability to provide all required tools/widgets/web services detailed documentation to interface AH web site with the provider's IBE and all related services, The provider must guarantee all the support/assistance required.

3

Administration Tools. Ability to: - Customize the IBE with the look and feel of

AIR ALGERIE’s brand, - Configure page layouts, - Modify and optimize booking flows (E.g.

change/ reduce booking steps).

4

Administration Tools. Ability to : - Customize and categorize ancillary services

and cross-sells, - Configure promotional web offers/corporate

offers, - Enable and disable features, preview changes,

AOIR : N° 001/DC/2016 Page 67


Y/N/P/F Core or


track changes and roll back changes.

5

Administration Tools Management. The administration and the configuration must be done autonomously according to configurable rules.

6

Graphic charter and content edition. IBE should be adapted to respect AIR ALGERIE graphic charter to guaranty a consistent visual identity; graphic, iconographic, typographic and ergonomic guidelines should be integrated. Ability to modify texts, tooltips, re-directional links, popup and notification messages, error and information messages, field indications and acceptance checkboxes.

7 Fare Family management. Ability to provide a full Fare Family management tool: real time creation, maintenance and update of fare families….

8

Advanced/Inspirational Search Tool. Ability to offer an advanced tool to provide for web site visitors an attractive experience using flexible search (flexible date range/flexible destinations) and combined search criteria (activity/destination search, week-end search, budget driven, period of stay...). Result travel recommendations should be displayed in easy manner for a quick comparison and upsell.

9

Secure environment. A robust SSL certificate must be provided, its renewal and maintenance will be included in the support contract. Data transmission, storage and use must be done in accordance with all security processes/ protocols and applicable laws.

10

Browser Compatibility: IBE should be compliant with major and widely used browsers, IBE should also be maintained to meet technology development and new versions release.

11

Hosting. The solution must support : - Availability and Risk management - High availability (99.9 uptime is the minimum

required) - Online traffic including temporary

peaks/overloads. - Traffic evolution, smooth and fast navigation.

AOIR : N° 001/DC/2016 Page 68


Y/N/P/F Core or


12 Hosting. Hosting management including security, monitoring, enhancements and maintenance are provider responsibility.

13

Cost/Performance control. - Ability to provide all mechanisms to keep a

cost effective solution and protect AIR ALGERIE revenue from bad and abusive practices (protection from scripts and bots, illegitimate HTTP post/get, crawling)

- Ability to keep tracking/logs of activities including Metasearch engine controls, pricing transactions optimization.

- Ability to employ IP throttling and blocking to restrict the number of hits to the host system and reduce site performances.

14

Monitoring & updates: Ability to maintain an up to date solution with all corrective patches, updates and enhancements according to latest technologies and standards (e.g.: Security recommendations, Industry norm and standards…).

15

Test environments. Ability to provide testing environments (e.g. workflow, design, layout changes, adding functionality, enabling and disabling features, developments…).

16 Multi-destinations. Ability to book up to 6 segments (at least) for multiple destinations.

17

Availability Search. Ability to support combined criteria for availability search including :

- Trip type (OW, RT, itineraries with multiple stopovers, open jaws,),

- Reservation class, - Schedule search : should display existing

flights per travel dates, over a configurable range,

- Flexible search : calendar/matrix display per travel dates, over a configurable range,

- Direct flight only filter/ Origin-destination.

18

PTC. Ability to support multiple PTC in query/ list all supported PTC. Ability to apply specificities/checks/restrictions according to selected PTC (applicable fares, additional information on PAX details, specific SSRs…).

AOIR : N° 001/DC/2016 Page 69


Y/N/P/F Core or


19 Group Booking. Ability to handle group booking.

20 Calendar Display. Ability to support Calendar fares display.

21

Fares. Ability to support: - Fare families/branded fares, - Online/web oriented fares, - Typological fares according to selected PTC

(adult, infant, child, student, senior, youth, UM…),

- Behavioral fares (family plan, couple plan…), - Web discount code capabilities.

22 Display remaining seats. Ability to display remaining seats, configurable (if lower than a pre-defined threshold).

23

Cabin/class Selection. Ability to Support selection of different cabin classes on individual segments and different brands on the outbound and return leg.

24 Partners/codeshare flights. Ability to offer partners/codeshare flights.

25

Fare conditions detailed Display. Ability to display fare conditions details /fare families attributes. In case of fare combination, only the most restrictive condition should be displayed.

26

Fare Conditions Summary display. Ability to display in multiple languages (FR/EN/AR are minimum requirements): - A user-friendly summary of fare families and

fare conditions, - A user-friendly summary of fare families’

comparison.

27 Fees. Ability to configure booking fees, payment fees, services fees based on business rules (e.g. POS, per PNR, per itinerary, FOP...).

28 Taxes Breakdown. Ability to configure and display full taxes/charges/fees breakdown (e.g. depending on POC).

29 Currencies. Ability to price in multiple currencies.

AOIR : N° 001/DC/2016 Page 70


Y/N/P/F Core or


30

Dynamic conversion display. Automatic notification for converted Fares before payment (when the displayed fare currency and payment currency are different).

31 Ancillary services. Ability to support both cross-channels and ecommerce specific ancillaries’ services.

32

Flight Summary. Should be displayed during all booking steps, it should be possible from any booking steps to modify selected entries. Flight summary include (Partial list):

- Travelers details, - Itinerary summary, - Baggage allowance, - Price summary including all paid services

details (Tickets, chargeable services, ancillaries and cross-sells), all taxes, charges and applicable fees,

- Fare conditions link.

33

Passenger Information. Ability to : - Manage/configure travel requirements

information (e.g. APIS based on departure/destination),

- Support specific PTC information (e.g. Extra contact Info for UM).

34 Seat Selection. Ability to select seat using seatmap (including a legend) from booking/booking management.

35 Seatmap Restriction. Ability to restrict high value seats display to specific customers based on business rules.

36

Ancillary services. Ability to : - Offer air and non-air (standalone) services - Offer chargeable and non-chargeable

ancillaries and issue EMD. - Support multiple touch points (configurable

e.g. Standalone, booking, online check-in ...). - Provide a shopping cart with all associated

taxes and fees shown - Include/exclude products

37

Cross-sell. Ability to offer seamless points of integration (homepage, on booking flow, manage my booking) for example Hotel, car rental and insurance services.

AOIR : N° 001/DC/2016 Page 71


Y/N/P/F Core or


38 Services time limit control. Ability to manage time limit to access/order services (e.g. Meals 24H before departure).

39

Profile. Ability for the passenger to create and have secure access to their profile. Profile should include, but not limited to their name, frequent flyer information, contact, address, special service information, current reservations, passport or other identification.

40 Frequent Flyer Login. Ability to log with FF number. The profile should be automatically loaded and used for booking or next transactions.

41

Payment Gateway Interface. Should integrate all payments methods currently used :

- Visa, MasterCard (OGONE Payment Gateway ), - CIB card (local payment method with SATIM

payment gateway).

42

Payment. Ability to integrate all major payments methods widely used :

- Credit Card : Amex, DinersClub …, - E-banking: Sofort , Giropay…, - E-wallet : PayPal …

43 FOP. Ability to support multiple FOP.

44 Omni channel Payment Solution. Should integrate all payments methods for web, mobile web version and mobile App.

45

Payment. Ability to : - Provide a fully integrated payment solution to

the booking flow and to all paid services, - Configure payment according to business

rules (e.g. Payment page/messages customization, POS/POC configuration, multi languages support…),

- Process payment transactions, - Send customizable email confirmations, - Deliver a full visibility of transactions and

comprehensive reporting/ Fraud analytics reports.

46

Ticketing issuance failure when successful payment. Ability to manage Ticketing issuance failure when successful payment, by server (IBE) to server (payment gateway) solution.

AOIR : N° 001/DC/2016 Page 72


Y/N/P/F Core or


47

Book and hold option. Ability to support book and hold option: it must be possible for users to book their trip online, comeback later to pay and continue the process Online, on mobile and/or ATO/CTO. - Fares control for delayed payments should be

done according to airline rules (fare expiry controls).

- Ability to configure cancellation rules (E.g. Hold duration TTL, reminder e-mails...).

48 Online invoices. Ability to issue online invoices.

49

Promotional/corporate Codes/offers. Ability to create and manage promotional offers based on business rules including but not limited to : - Application rules (Net fare, PTC, sales

dates/time, passenger number, cabins), - Sales country, password use, - Fixed amount/rate, - Itinerary option restrictions

(OW/RT/stopover/Multi destinations), - Travel dates/flights/days, - Payment modes restriction (e.g. discount for

the uses of a specific payment mode).

50

Manage my booking. Ability for the customer to change their booking. This includes, adding segments, managing passenger details such as special service requests, adding passport information, frequent traveler data, and exchanges.

51

Manage my booking. Ability to retrieve Booking using: - Name / Booking Reference, - Name / ETKT.

52

Online changes. Ability to support: - Re-pricing &Reissue or refund, - Compute upgrade fees with payment

collection, - Advanced shopping display.

AOIR : N° 001/DC/2016 Page 73


Y/N/P/F Core or


53

Emails. Ability to: - Support Reminder emails, confirmation

emails…, - Send/schedule emails, action, time and event

triggers must be considered, - Customize emails using pics/logos/ links. The

content will be defined, - Support additional information, - Attach documents in emails (e.g. fare

conditions, ETKTs...), - Support multiple languages, at least FR, EN,

AR.

54

IBE generated documents (e.g. ETKTs, e-boarding pass, EMD…). Ability to:

- Customize documents content, - Support standard format (e.g. PDF) - Support multiple languages

55 Multiple languages. Ability to support multiple languages in all IBE interfaces (French, English and Arabic….).

56 Flight Status. Ability to provide flight status through IBE /Mobile web /Mobile application.

57 Mobile WEB/APP. Ability to provide an optimized/customizable user interface.

58

Mobile WEB/APP. Ability to provide (including but not limited): - Optimized search including calendar view, - Upsells facilities with fare families support, - Booking management Interface, - Special services request, - Book and purchase air and non-air ancillaries/

3rd parties cross sell, - Check-in/ e-boarding facilities, - Frequent Flyer Program integration, - Payment platform compliance, - Timetable, route map and flights status

facilities, - Voluntary changes (automatic

exchange/Refund), - Send confirmation including booking

confirmation, Etkt receipt/Mobile E-boarding pass…,

- Provide a mobile boarding pass, to be displayed on a mobile phone/device,

- Support multiple languages, - Irregularity schedule notifications.

AOIR : N° 001/DC/2016 Page 74


Y/N/P/F Core or


59

Mobile App. Ability to provide an IOS and Android Application with similar services as the mobile/desktop version : - Update , maintenance and management is

provider responsibility, - Ability to provide hosting on Google Play and

AppStore on behalf of AIR ALGERIE, - Ensure maintenance and upgrades according to

technology evolution.

60

Award Shopping. Ability to provide Award shopping and redemption facilities. Ability to combine multiple FOP (e.g. combination of miles and cash for award tickets).

61 Upgrade Award. Ability to provide automatic upgrade award.

62 Reporting. Ability to provide reporting for: - Usage of promotional/corporate code, - Cross-sells and ancillary services.

63

Statistics tool. Ability to provide an advanced Statistics tool related to IBE traffic (e.g.: booking stats, revenue stats, refund and exchange stats, OLCI, Number of page views...), exceptions and error logs are also required. - Deliver a comprehensive reporting for all

channels (WEB/Mobile) - Export Data facilities to common/ standard

formats are required (e.g.: xlsx, CSV…).

64

Web Analytics Tools: Ability to provide fully integrated and advanced analytic tools to track and report users behavior, online campaigns, conversions, goals and all related traffic, E-commerce module, sales activity and transactions tracking is also required, a flexible, configurable interface must be provided to view/export/edit personalized reports/ statistics.

AOIR : N° 001/DC/2016 Page 75


Y/N/P/F Core or


65

Online check-in. Ability to provide (including but not limited to) : - Seat selection, - Send check-in confirmation, - Enable/disable e-boarding pass

issuance/delivery. Configuration must be done autonomously using admin interface,

- Online Check-in/boarding Controls according to configurable parameters (e.g. PTC, Fare, APIS collection...),

- Configurable Check-in open/close time (e.g. for international/domestic flights),

- Through check-in, - Online check-in / Through check-in for

codeshare flights.

66

B2B. Ability to manage corporate customers across :

- Online booking, - Corporate fares application, - Corporate loyalty program, reward benefit, - Promotional offers, - Notifications for special offers, - Reporting features.

67

Irregularity Management. Ability to enable online reissue/ free re-accommodations / chargeable upsells based on Involuntary rules. Ability to provide notifications.

3. 10. Loyalty Management System & Customer experience


Y/N/P/F Core or


Loyalty Management

1 Integration. Must be Integrated with the PSS core.

2 Revenue Accounting Data. Ability to process revenue accounting data.

3

Membership card number. Ability to : - Contain at least 11 digits with a check digit, - Define number range for each enrolment

channel, by city codes, territory etc…

AOIR : N° 001/DC/2016 Page 76


Y/N/P/F Core or


4

Access Administration and user profile. Ability to define user profiles according to their roles and attribute permissions to access accordingly. Ability to provide restricted access for each profile.

5 Enrolment. Ability to Enroll through multiple channels: Internet (web, mobile), Reservation system, DCS, upload batch, online system.

6

Profile management. Ability to: - Synchronize member profiles with the PSS

(Reservation, DCS and IBE), - Update Personal Information through different

channels, - Store multiple addresses (Home, work), e-mails

and phone numbers for each member, and highlight the member's preferred contact information,

- Add Passport details, - Link between Family members, add family

details, - Select Preferences (meals, seating,

demographics, hobbies, lifestyle etc.), - Detect possible duplicate accounts based on

name check, date of birth, Email address etc…, - Merge/demerge accounts, - Support the definition and transition

(automated & manual) of member status codes in accordance with defined transition rules (e.g. ‘Active’, ‘Inactive’, ’Merged’, etc.).

AOIR : N° 001/DC/2016 Page 77


Y/N/P/F Core or


7

Membership management. Ability to : - Provide a complete view of member

information, contacts, last transactions, tier miles/segments summary,

- Support multiple tier/sub-tiers levels, - Print Membership card with encoding according

to defined template, - Restrict the number of free card printing, from

x number the card should be printed against fee payment,

- Provide Membership cards history, - Manage mileage expiry, - Manage the Parent-Guardian and Minor details, - Manage the Family Members, - Allow Transfer of miles, - Setup, generate and deliver E-Statement via

email automatically or manually. The statement delivery can be configured according to defined frequency, tier level, member status.

8

Sub Programs. Ability to support the creation and management of multiple frequent flyer sub-programs on the same customer base (e.g. Family Programs, VIP Programs, and Guest Programs).

9

Tier management. Ability to: - Manage automatically tier change according to

defined rules based on both tier miles and segments,

- Set up a specific rules to define tier and segment miles,

- Change tier using Manual Override, - Upgrade based on calendar year and rolling tier

rule, - Support both tier miles and tier segments, - Retain/downgrade tiers manually, - Provide second chance (grace period) for retain

tiers.

10 Fulfillment. Ability to provide data to fulfillment house and reverse feedback from fulfillment house for returned and undelivered mails.

AOIR : N° 001/DC/2016 Page 78


Y/N/P/F Core or


11

Redemption. Ability to: - Validate account balances for redemption and

perform the redeeming miles from the member's account,

- Support multiple type of rewards: air (Tickets, Upgrades and excess Luggage etc.) and non-air (Hotel, car rent etc.),

- Support both automatic and manual Redemptions,

- Support Vouchers, gifts, Partners redemption, - Process in real-time through the reservations

system, - Define reward pricing in both miles and cash

options, - Allow online redemption via web and mobile, - Setup Redemption discount depending on

sectors/flight number range, - Restrict member redemptions to a defined list

of beneficiaries (defined by the member), - Redeem miles from a defined corporate account

for corporate employees registered in the FFP or restricted list of defined corporate beneficiaries,

- Define reward cancellations fees (fixed fee or percentage of the total reward amount).

12

Communication. Ability to : - Deliver notifications through multiple channels

(e-mail, Web, SMS), - Set up notifications for the members based on

tier change, enrolment, accrual activity, redemption activity,

- Allow delivery channel selection by the member,

- Provide a complete communication history, - Support multiple languages (FR, EN, AR etc.) - Customize templates communication with

different format (Html, Txt),

13

Partnership management. Ability to: - Support Airline and Non-Air partnerships, - Maintains partner contracts and

mileage/currency exchange rates, - Provide User friendly interface to define rules

for partner accruals and redemptions, - Generate vouchers for partner redemptions, - Support automated data exchange with

partners, - Provide Flexible user defined formats for data

exchange (Excel, Txt etc.), - Ensure Fraud prevention,

AOIR : N° 001/DC/2016 Page 79


Y/N/P/F Core or


- Provide automated billing, - Support specific codeshare rules for partner

accrual (i.e. operating vs. marketed carrier),

14

Campaigns. Ability to : - Setup, configure and manage promotions

through campaign management engine, - Support accrual and redemption promotional

campaigns, - Allow both targeted and generic campaigns

using any parameter in customer profile, - Use multiple interfaces to register for

campaigns, - Provide campaign performance monitoring.

15

Accrual processing. Ability to - Process accrual based on Batch or Airline PSS

data on real time, - Accrue miles according to: booking class, flown

class, segment, O&D, flight number, revenue/non-revenue segment etc…

16

PNR data. Ability to: - Store and view booked and flown data, - Provide Reservation and Check-in Information, - Submit for Retro accrual.

AOIR : N° 001/DC/2016 Page 80


Y/N/P/F Core or


17

Customer Care. Ability to : - Support complete log of customer contacts, - Provide multiple detailed levels classification of

each contact, - Capture other involved parties, - Support third parties, - Support document imaging, individual and

batch upload, - Special handle of baggage loss, - Facilitate detail investigation of each complaint

using PNR and Check-In repositories, - Support simple workflow to assign tasks to

different teams or individuals, - Record level security to prevent unauthorized

data access and update, - Seamlessly link to Member profiles, - Maintain complete compensation profile

(payment, cost center authorization, form of payment, different currencies etc.),

- Allow Miles credit or enrolment in Loyalty program as compensation,

- Provide standard action list for similar cases based on category,

- Enable proactive actions in case of flight disruption.

18

Reports. Ability to provide: - Pre-defined reports, - Customized reports, - Dashboards, - Exportation to standard formats (HTML, EXCEL,

PDF…) - Error reports, - Fraud management reports.

AOIR : N° 001/DC/2016 Page 81


Y/N/P/F Core or


19

Loyalty Website. Ability to: - Provide a dedicated Loyalty member website

with the possibility to browse transactions and profile information,

- Allowing members to enroll, view and update profiles, see past activities, submit retro claims, register to campaigns etc. through loyalty website,

- Check for valid email Address at the enrolment. Enrolment cannot be completed before Email address Validation,

- Allow members to login with their loyalty credentials (i.e. alias, frequent flyer number, email, pin number),

- Reset or retrieve password in a secure manner, - Set up a maximum number of incorrect login

attempts a user can make before being locked out of the system,

- View the membership card and request its printing,

- View and print the account statements, - Allow members to submit a contact form (i.e.

query, complaint, request), - Integrate with any 3rd party Mobile App, - Allow members to view future transactions and

future miles earned according to booking.

20 Corporate. Ability to Include Corporate Module.

21 Alliance operations. Ability to support Alliance operations.

22 Lounge access. Ability to Include lounge module.

23 Calculate value. Ability to calculate the member value (Revenue, Importance, High Tier etc.) and provide ranking according to revenue generated.

AOIR : N° 001/DC/2016 Page 82

3. 11. Business Intelligence


Y/N/P/F Core or


Business Intelligence

1

Business Intelligence. Ability to provide (including but not limited) :

- Intuitive analytics and visually appealing, - Web-based system management tools, - Daily, weekly, monthly and yearly reports,

dashboards and statistics, - Create reports with user’s defined

parameters, - Export Data, reports with different format

(text, Excel, word document, PDF, ZIP…).

2

Business Intelligence. Ability to provide Dashboards executives for an overview of :

- Commercial performances (by web sells and by point of sale) data comparisons,

- Competitors capacity, frequency and fares market share, Opportunities (Codeshare, interlining, alliances, new routes…).

3. 12. Disruption Management System


Y/N/P/F Core or


Disruption Management System

1 Integration. Ability to interface with the whole PSS components.

2 Flights disruption. Ability to handle in real time all irregular flights operations.

3

Passengers Re-book. Ability to re-book automatically (ETKT, EMD, SSRs, ancillaries) passengers according to the available travel alternatives.

4 Passengers Re-book. Ability to re-book automatically passengers on connecting flights.

5 Re-issue and Refund. Ability to re-issue and refund E-tickets automatically.

AOIR : N° 001/DC/2016 Page 83


Y/N/P/F Core or


6 E-TKT Status. Ability to handle manually ETKT coupon status.

7 Passenger re-accommodation. Ability to re-accommodate automatically passengers from Inventory and DCS.

8 Baggage handling. Ability to handle passengers’ baggage (re-tag, messages regeneration).

9 Customer Prioritization. Ability to handle priority customer based on value (FFP, fares paid, class of travel...).

10 Disruption costs. Ability to provide cost effective solution to reduce disruption costs.

11 Passengers Compensation. Ability to calculate compensations.

12 Queue PNRs. Ability to queue PNRs on defined queues

13 Notification. Ability to notify by APPS, e-mail and SMS passengers affected by the disruption.

14 Reporting. Ability to provide detailed reports

AOIR : N° 001/DC/2016 Page 84

4. OTHER REQUIREMENTS

4. 1. Migration Plan, strategy and Risk Management

4.1.1. The provider shall list the scheduled Airlines for which a migration was performed with stating the

previous systems (or PSS modules) and their suppliers (according to below table).

Airline Provider System / Module

4.1.2. The provider shall also present the plan and the approach for migration of all AIR ALGERIE’s data

(Schedule, PNRs, ETKTs/EMDs, FFP…), including the integration process of the partners (IET, IATCI…) and

third parties (GHA DCS…).

The provider must indicate time and human resources to be dedicated to the migration:

Number of persons required (full or partial time),

Number of working days,

Responsibility of each stakeholder,

Detailed plan with milestones including tests and rehearsals.

4.1.3. The supplier must indicate for each module the estimated rejection/risk rate, the rejection cases

and difficulties that could be faced during the migration and how the supplier will resolve/correct them.

4. 2. Implementation plan of the PSS

4.2.1. The provider must list, for each module, hardware, software and network detailed

recommendations to ensure optimal performances taking into consideration AIR ALGERIE’s existing

infrastructure.

4.2.2. The bidder must provide technical support fitted to expected services, containing:

Contacts (phone numbers, email addresses…) for technical support and incidents

management,

Onsite/remote interventions when needed,

24/7 availability

Multilingual support (French and English)

4.2.3. The bidder must inform AIR ALGERIE about any update, enhancement or innovation.

4.2.4. The provider must ensure post implementation support during a minimum six (6) months after

each cutover.

AOIR : N° 001/DC/2016 Page 85

4. 3. Tests

The provider shall perform all operational tests of the PSS implementation. Testing should particularly

focus on the following aspects (not limited to):

The full functioning of the systems,

The integration of the solution to the existing network,

A test set on the migration of existing data,

AIR ALGERIE must perform validation testing (UAT User Acceptance Test).

4. 4. Training

The provider will ensure the necessary training to AIR ALGERIE for implementation, administration,

configuration, operations and technologies used in the context of the proposed solution.

The bidder must detail in its offer the training programs, the durations and the certification of the

trainers.

Training must be done in the form of practical workshops and include simulations based on real case

studies and covering all aspects of the program.

4. 5. Project reports

The bidder must submit reports at each step of the project describing the following points:

The intervening plan of both parties, AIR ALGERIE and Bidder, specifying profiles, roles and

tasks involved in this mission,

The requirements in terms of resources and information that will set up AIR ALGERIE to the

project’s success.

4. 6. Final documentation

The Bidder shall provide full documentation specific to the whole PSS solution. The formats of these

deliverables paper and "soft copy" (standard formats) will be the exclusive property of AIR ALGERIE.

AOIR : N° 001/DC/2016 Page 86

SECTION 4: BIDDING FORMS / SAMPLES OF DOCUMENTS

SAMPLE FORMAT: BIDDING LETTER

(Bidder’s Letterhead)

Type of consultation AOIR: N°:_______of_______ [The Services Contract] To: [Name and address] Dear Sirs, Having examined the bidding documents, and as a reply to your letter of invitation for Bid according

to the invitation for Bid [n° ] of [ ] we, the undersigned (name of the Bidder), offer to perform

the Services of the above mentioned contract in full conformity with the bidding documents for the

sum of [amount in local currency in words] [amount in figures], and [amount of foreign currency in

words, if any] [amount in figures].

The above mentioned amounts; fixed on the basis of technical bid, are consistent with breakdowns of

joint prices and forms a part of our bid of __________ submitted under the invitation for bid

n°[_________] of [_________].

We are committed by this Price Bid , from the bids opening date indicated in your invitation letter of

(_____) until the expiry of the bid validity period extended by supplementary 30 days according to

the invitation for bid i.e. the [_________] in accordance with our bid letter of [_______] still effective

according to the invitation for bid n°[______] of [________].

Made on______________________________ _____________________________________ [Signature] Acting as: [Title] Duly authorized to sign this bid for and on behalf of: *Bidder’s name+.

AOIR : N° 001/DC/2016 Page 87

PRICES LIST

Item Description Quantity Unit

Price

Price Duty

Free/USD

One fee Migration & implementation 01

Monthly

fees

Usage, Support &

Maintenance

Less than 4 Million PB ……………….. Per PB

Between 4 and 6 Million PB ……………….. Per PB

Between 6 and 8 Million PB ……………….. Per PB

More than 8 Million ……………….. Per PB

Annual Evaluation Estimated number of passengers Price Duty

Free

Total duty free on 12 Month - Year 2017 5 883 638 Borded Passengers





Total price (Total Taxes Included) (USD)

All other costs must be supported by the supplier

AOIR : N° 001/DC/2016 Page 88

SAMPLE OF STATEMENT MADE ON THE HONOR

(On the Bidder Letter heading)

Consultation type AOIR: N° …………………dated as of…………..

To: (Name and address) Dear Sirs, I the undersigned (the Tenderer’s name) certify that I have been informed about the ethics rules

stated by AIR ALGERIE.

I agree to observe at the time of entering a bargain, concluding or executing the Contract, the

strictest professional ethics rules.

I forbid myself, under the sanctions provided by the laws and regulations in force:

- To recourse to any interference, practice, swindling or any fraudulent or collusive practice, in

order to obtain the Contract.

- To promise to offer or to give an advantage of any nature either in order to influence the AIR

ALGERIE agent action during the Contract awarding or the Contract execution.

Algiers on: Name and Surname: Signature: Title:

AOIR : N° 001/DC/2016 Page 89

ETHICS RULES

AIR ALGERIE has as a principle to ask to the Tenderers, underwriters and suppliers to comply, at the

conclusion and the execution of its Contracts, the strictest professional ethics rules. In pursuance of

this principle, AIR ALGERIE:

a. Defines, in order to apply this provision , the following expressions:

Is guilty of “corruption” anyone offering, giving, applying or accepting any advantage in order

to influence an AIR ALGERIE Agent during a Contract granting or execution, and

Anyone practicing “swindling” or fraudulent practice, deforming or distorting facts in order to

influence the practice granting or execution in a manner causing prejudice to AIR ALGERIE. “

The swindling” also combines any agreement or collusive act of the Tenderers ( before or

after the Tenderer handing over) aiming to maintain artificially the Offers price to levels non

corresponding to those resulting from a free end opened competition, and thus depriving AIR

ALGERIE from the advantages of this later.

b. Shall reject the Contract granting proposal in case it establishes that the Tenderer to which it is

recommended to grant the Contract, is guilty of corruption or has practiced swindling in order to

get the said Contract.

c. Shall exclude indefinitely a firm or for a determined period from any granting, if AIR ALGERIE

established at any moment that this Firm has practiced corruption, swindling in view of getting

the Contract.

The intervening parties in the Contract drawing up proceedings must show independence towards the competitors and shall not accept from them no advantage represented in gratification and must not have relations with them that would compromise their objectivity and impartiality.

AOIR : N° 001/DC/2016 Page 90

GLOSSARY

AOIR : N° 001/DC/2016 Page 91

Terms Description

ABR Automated Baggage Rules

ACARS Aircraft Communication Addressing and Reporting System

ADL Additions and Deletions List

AEA Association of European Airlines

AHM Airport Handling Manuel

AIMS Airplane Information Management System

AIRIMP Reservation Interline Message Procedures

AOIR Appel d'offres International Restreint

API Advanced Passenger Information

APIS Advanced Passenger Information System

APP Advanced Passenger Processing

AQQ APIS Quick Query

ASM Ad hoc Schedule Message

ATO Airport Ticketing Office

ATPCO Airlines Tariff Publishing Company

AUX Auxiliaries

AVS Availability sent Messages

BBR Bank Buying Rate

BDF Bid Document File

BDS Bid Data Sheet

BPP Boarding Pass Printer

BRS Baggage Reconciliation System

BSM Baggage Source Message

BSP Billing and Settlement Plan

BSR Bank Selling Rate

BTP Bag Tag Printer

CHD Child

CIB Carte Inter Bancaire

COMAIL Company Mail

CPM Container/Pallet Distribution Message

CRIS Customer Relationship Information System

CRM Customer Relationship Management

CRS Computer Reservation System

CSR Counter Sales Reporting

CTO City Ticketing Office

CVV Card Verification Value

DCS Departure Control System

EDIFACT Electronic Data Interchange For Administration, Commerce and Transport

EMD Electronic Miscellaneous Documents

EMSR Expected Marginal Seat Revenue

ETA Estimation Time Arrival

ETD Estimation Time Departure

ETKT Electronic Ticket

ETR Electronic Ticket Record

ETS Electronic Ticket Server

EURO CONTROL Organisation Européenne pour la Sécurité de la Navigation Aérienne

FCMI Fare Calculation Mode Indicator

FFP Frequent Flyer Record

FOID Form Of IDentification

FOP Form Of Payment

FQTV FreQuent TraVeler

FTL Frequent Traveler List

GD General Declaration

GDS Global Distribution System

GHA Ground Handling Assistant

GI Global Indicator

GUI Graphic User Interface

IAPI Interactive Advanced Passenger Information

IATCI Inter Airline Through Check-In

AOIR : N° 001/DC/2016 Page 92

Terms Description

IBE Internet Booking Engine

ICH IATA Clearing House

IDM Industry Discount Message

IDS Information Display System

IET Interline Electronic Ticket

IFM Interline Fall-back Message

IFS In Flight Service

INF INFant

INFARE / QL2 Provider of competitive fare pricing information, seat availability and promotional data from companies.

INNOVATA Source of Airline Schedule Data (Schedule publisher)

ITB Instructions to Bidders

LDM LoaD Message

LDP LoaD Planning

LDW Landing Weight

LPM Load Planning Message

MAC Mean Aerodynamic Chord

MACS Mercator Airport Control System

MARS Mercator Airlines Reservation System

MCT Minimum Connecting Time

MERCATOR Airlines systems providers

MPM Maximum Permitted Mileage

MRZ Machine Readable Zone

MSR Magnetic Stripe Reader

NAVS Numeric Availability sent Messages

NOTOC Special Load NOtification TO Captain

NUC Neutral Unit Calculation

O&D Origin & Destination

OAG Official Airlines Guide (Schedule publisher)

OAL Other Air Lines

OCR Optical Character Recognition

OGONE Payment Gateway provider

OJ Open Jaw

OLCI On Line Check-In

OSI Other Services Information

OW One Way

PADIS Passenger and Airport Data Interchange

PAX Passengers

PB Passenger Boarded

PCI-DSS Payment Card Industry - Data Security Standard

PECTAB Parametric Table

PFC Passenger Facility Charges

PFS Passenger Final Sales

PIL Passenger Information List

PNL Passenger Name List

PNR Passenger Name Record

POC Point Of Commencement

POS Point Of Sales

PSM Passenger Service Message

PSP Payment Service Provider

PSS Passenger Services Systems

PTC Passenger Type Code

PTM Passenger Transfer Message

RAPID Revenue Accounting Prorate Interline Decision

RBD Reservation Booking Designator

RFID Radio Frequency Identification

RI Revenue Integrity

RLOC Record Locator

RMS Revenue Management System

ROE Rate Of Exchange

RT Round Trip

AOIR : N° 001/DC/2016 Page 93

Terms Description

RTOW Regulated Take Of Weight

RW Round World

SATIM Société d'Automatisation des Transactions Interbancaires et Monétiques

SFPD Secure Flight Passenger Data

SOM Seat Occupied Message

SPL Specified Persons List

SSIM Standard Schedule Information Manuel

SSL Secure Sockets Layer

SSM Standard Schedule Message

SSR Special Service Request

STA Scheduled Time Arrival

STD Scheduled Time Departure

SYGA SYstème de Gestion Agences

TIMATIC Travel Information Manual Automatic

TOW Table Of Weight

TPM Teletype Passenger Manifest

TPM Ticketed Point Mileage

TSA Transportation Security Administration

TSM Transitional Stored Miscellaneous

TST Transitional Stored Ticket

TTL Ticketing Time Limit

TW Taxi Weight

UAT User Acceptance Tests

ULD Unit Load Device

UM Unaccompanied Minor

US DOT United State Department Of Transportation

WCH Wheel chair

WORLDSPAN provider of travel technology

ZED Zone Employee Discount

ZFM Zero Fuel Weight

https://en.wikipedia.org/wiki/Technology