COMMERCIAL DIVISION

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

“Passenger Services System For Scheduled Passenger Airlines”

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 2

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 3

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 4

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 5

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 6

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 7

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 8

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 9

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 10

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 11

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 12

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

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, 1 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 13

Required Eligibility Criteria: 4 Suppliers of PSS, providing currently their PSS to three (03) scheduled airlines at least.

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 5 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.

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. 5 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 14

Clarifications of Bids: Bidders may submit clarifications request about bidding invitation file to AIR ALGERIE by Email: [email protected] 9 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

The Submission Language is : 11 The Bid and all correspondences and documents related to the bid exchanged between the Bidder and AIR ALGERIE shall be submitted in English Language.

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 12 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

AOIR : N° 001/DC/2016 Page 15

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.

Alternate bids: 13 Alternate bids will not be considered.

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 13 . 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.

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

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

AOIR : N° 001/DC/2016 Page 16

Number of Copies : The Bid must comprise: 16 - One (01) original, - Two (02) copies (on paper print), - One (01) copy on digital format

D – BIDS SUBMISSION

Due date and time for Bids Submission: The offers submission date is limited on 11th July 2016, at 1 p.m. Bids Submission: AIR ALGERIE - Commercial Division Secretariat of Commercial Division 5th floor. 29 Bd, Zirout Youcef 16000 ALGIERS ALGERIA

18 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

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: AIR ALGERIE - Commercial Division Secretariat of Commercial Division 5th floor. 21 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 17

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.

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 27 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 18

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

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 28 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.

Competitors Protest: Any Bidder who challenges bidding results or reasons of rejection of his Bid, or who 31 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 19

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

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

Daily Flights (scheduled) 167 (Average)

32 domestic stations Destinations Served 40 international stations (Europe, Africa, China, Middle East, Canada)

2012 = 4 137 266 PB Passengers Boarded 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 20

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) Filing Fares ATPCOSATIM (national cards) 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 21

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 22

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 Standalone & 18 services Deployed at ATO /CTO Associated 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)

- OGONE : International Payments (CB, VISA, MASTERCARD) Payment - SATIM : Local payments (DZD) - Book & Hold (Collection at ATO/CTO)

AOIR : N° 001/DC/2016 Page 23

- Manage my booking (seating, meals...) Services - Online check-in

- Redemption Frequent flyer Program - 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

AIRPORT STATION DCS SUPPLIER CUTE GROUND HANDLER CODE

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 24

AIRPORT STATION DCS SUPPLIER CUTE GROUND HANDLER CODE

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

Aviapartner ( Ex Rome FCO ARCO ALITALIA SITA CUTE Flightcare)

AOIR : N° 001/DC/2016 Page 25

AIRPORT STATION DCS SUPPLIER CUTE GROUND HANDLER CODE

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)

AOIR : N° 001/DC/2016 Page 26

2. 15. DCS Equipments in Algeria

TYPE MANUFACTURER MODEL

INTERMEC PF 4i BOARDING PASS PRINTER IER IER400

GATE READER IER IER600

PASSPORT READER DESKO MPR 7200

INTERMEC PF 2i BAG TAG PRINTER IER 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 Lasers printer Ethernet 100 mbps - Processor Intel A4 Monochrome Wan 64/512kpbs - RAM:1Go min Dot Matrix printer leased line (SITA) - HDD: 300 GB min - OS : Win XP pro/ Win7 pro/ Win 8 pro 32/64 bits

Average 4 PCs per agency Average 2 printers per agency Some agencies have an ADSL connection

2. 18. AIR ALGERIE Infrastructure Network

See the following schema: AOIR : N° 001/DC/2016 Page 27

Domestic AH CTO/ATO Users with ADSL Algiers Airport Terminal 1 and 3 International AH CTO/ATO and Airports Connection and Airports

64/512 Kbps LS

Internet SITA International Network

Datacenter AH Algiers Kouba

2 x LS 1 Mbps 1 LS x 2

SITA Algiers

Datacenter MERCATOR Dubaï AIR ALGERIE Infrastructure Network

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.

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Access. Access to all systems and/or their functionalities must be controlled by session 1 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.

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

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

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

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

Access management. Ability to manage users profiles and privileges: - Creation, 6 - Amendment, - Suspension, - Cancellation.

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

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

AOIR : N° 001/DC/2016 Page 29

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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

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

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

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

Payment. Ability to accept : - International and local forms of payment (Credit/debit cards, e-wallets, 15 settlements…), - Payment on all channels (ATO/CTO, WEB, Mobile, Call Centre…).

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

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

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

Payment. Ability to support Dynamic currency 19 conversion.

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

AOIR : N° 001/DC/2016 Page 30

3. 2. Inventory

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Schedule Management

IATA standard. Incoming and outgoing IATA 1 standard schedule messages (SSIM/ ASM / SSM) must be automatically processed. Schedule. Ability to add new schedule (manually 2 and/or automatically), to change existing schedule or modify online into the inventory.

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

OAG/INNOVATA update. The supplier must 4 indicate the update frequency. Schedule. Ability to create the schedule in the inventory including (not limited to): - Flight number, - Effective and discontinue dates, 5 - Departure and arrival time, - Frequency, - Route pair, - Aircraft Type, - Terminal. Schedule Integrity. Ability to perform automated check during schedule creation/modification (e.g. 6 Arrival date is less than Departure date).

Schedule messages. Incoming schedule messages 7 that cannot be automatically processed must be manually reviewed. Schedule messages from Other Airlines (OAL), 8 Interline Partners, Codeshare Partners, Airline IT providers must be accepted. Schedule messages. Ability to send ASM/SSM 9 recap (automatically and/or manually) to other systems (OAG, INNOVATA…). Traffic Restrictions. All IATA standard traffic restrictions via SSIM/SSM/ASM to notify 10 OAL/GDS/OAG/INNOVATA are supported.

AOIR : N° 001/DC/2016 Page 31

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Short-term schedule. Ability to create extra section 11 flights and Charters flights.

Shared Schedule Database. Ability to provide a 12 single shared schedules database with DCS and reservation system. 13 MCT file from OAG or INNOVATA must be loaded. Schedule change. Ability to rebook automatically Seat Maps, Seat Assignments and Special Service 14 Requests (SSR), in case of schedule change. PNRs containing failed seats or SSRs must be queue placed.

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

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

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

Schedule Updates must be processed in real time 18 to all PSS modules. Creation flights. Automatic flight creation must be 19 at least 360 days (system period). Flight Range. 0000-9999 flight number range must 20 be supported. AVS/NAVS. Ability to control the sending and receiving of AVS/NAVS messages, based on AIR 21 ALGERIE specific rules (first closing, segment availability…). AVS agreements. Ability to display AVS 22 agreements.

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

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

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

AOIR : N° 001/DC/2016 Page 32

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional SFPD. Ability to support Secure Flight indicator 26 (SFPD) at leg level. Inventory Management

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 27 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. Ability to display a minimum of 26 classes. Normal 28 availability displays should be restricted to x classes (x being a system parameter). City pair comment. Ability to show a city pair 29 comment over and above flight details on an availability display. Flight Schedule information. Ability to retrieve 30 Flight Schedule information up to 3 days post- departure. Number of seats. Display IATA standardized 31 number of seats available in each inventory (OAL, codeshare partners …). Seat map. Ability to build or delete a seat map based on a variety of technical, business and legal requirements. 32 Must include the ability to assign specific characteristics to seats/rows and provide seat history.

Advance seat selection. Ability to manage 33 advanced seat selection and seat map retrieval. Block and restrict seat assignment. Ability to block individual seats from Advanced Seat selection or to 34 restrict the number of seats available for Advanced Seat selection by segment and/or class.

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

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

AOIR : N° 001/DC/2016 Page 33

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Nesting. Automatic and manual Inventory nesting 37 is required (hybrid, serial and parallel nesting structures). Inventory Display. Include but not limited to: - By Leg, - By segment, - Capacity and Subclass authorizations, 38 - Seats Sold, - Waitlist and Staff counts, - Overbooking %, - Availability Status, - Nesting.

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

Emergency Lock. Ability to place an emergency lock on a flight’s inventory and PNRs. Emergency 40 locked inventories and PNRs are only accessible by control agents. 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, 41 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. Waitlist. Ability to provide waitlist management process including but not limited to: - Automatic and manual creation/ clearance, 42 - Automatic prioritization processing, - Sales Restriction on the waitlist by : POS, Market, flight range, specific classes ...

IATA Codeshare. The system must support all IATA 43 Codeshare Options. Codeshare configuration and management. Ability to provide parameter driven codeshare set-up, to 44 facilitate easy addition and modification of codeshare agreements. Shared Common Inventory. Ability to share an 45 inventory with a codeshare partner(s).

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

AOIR : N° 001/DC/2016 Page 34

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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

Post Departure Processing. Post departure processing should automatically update the 50 inventory and passenger information reflecting the actual boarding statistics for a flight. Group booking. Ability to handle any changes to 51 group bookings as per AIRIMP standards. 52 POS. Point of sales management is required.

Arrival or departure day. Ability to handle flight 53 arrival or departure up to +2 or -1 days. Limitations. Ability to allow the following limitations on the flight: 54 - Number of infants according to aircraft type, - Number of WCHx, - Number of UM. Archive PNR. Ability to load historical PNR data and 55 passengers list (archive).

3. 3. Reservation and Booking management

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Reservation and Booking management IATA codes. The system must support all IATA & 1 industry codes.

Availability display. Ability to display only available 2 RBDs (inhibit closed RBD display). 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, 3 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 35

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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 4 route (connecting flights), - By departure or arrival time, - Advance and go back by number of days, - Reverse availability with change of date. Availability display. Should display a minimum of 8 flights per page. For the purposes of this requirement, connecting flights are included in the 5 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. First Availability. Ability to display first availability by 6 city pair, class, start date…

Direct Sell. Ability to sell flight direct without reference to availability display. Sell a flight by using 7 flight number, date, O&D without any reference to an availability display is required. Sell from availability. The ability to sell segments from an Availability Display by selecting the routing 8 number and class only. If the routing number includes connecting flights they will also be sold by this single sell entry (different classes). Sell Open Dated Segment. Ability to sell “open” or 9 non-booked (ARNK) segments. Booking Non-Revenue Segments. Ability to book 10 Non-Revenue segments and have the possibility to be clearly identified in PNRs. Contact Fields. Ability to : - Parameter contact field as mandatory, - Cancel or change Contact fields elements in the PNR (e.g. Business Phone, Private Phone, 11 Mobile Phone, Fax, Street Address and E-Mail address etc.), - Attribute contact fields by passenger name in the PNR. Class Upgrade/Downgrade. Ability to change the 12 RBD of a segment(s) to another RBD.

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

AOIR : N° 001/DC/2016 Page 36

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Retrieve PNR by name/flight/date. Ability to retrieve PNR by passenger name, any active flight 14 segment & associated date. If the system cannot make an exact match a multi-selection list of possible passengers will be displayed.

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

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

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

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

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

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

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

Auto SSR Processing by Airport, Airline, or Others. 23 SSRs must generate messages or lists to the appropriate entity automatically. Auxiliary Service Element. Ability to support auxiliary service elements that may be requested by a 24 passenger: car rental, hotel accommodation, surface transportation and tour… 25 Name Change. Ability to change a name in a PNR.

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

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

AOIR : N° 001/DC/2016 Page 37

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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 30 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.

Display OAL availability. Ability to display OAL 31 availability.

32 OAL Booking. Ability to book OAL segments.

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

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

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

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

AOIR : N° 001/DC/2016 Page 38

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

are split. Any information specific to passenger is retained or transferred to the appropriate PNR, which contains that passenger. Queuing History of PNR. Ability to determine/view 37 which specific queues a PNR has been sent to and what action has been taken at each point.

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

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

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

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

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

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

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

Customer profile. Ability to retrieve and display 45 complete customer profile. Customer profile. Ability to Create PNR from 46 customer profile. Enroll customer. Ability to enroll customer in FFP 47 from reservation system. Miscellaneous support functions. Ability to provide: - Encode-Decode, - World city time / Airport information / Other 48 information, - Timatic, - Help, - Information Display System (IDS).

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

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

AOIR : N° 001/DC/2016 Page 39

3. 4. Ticketing and EMD

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Ticketing Management

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, 1 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.

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

3 TST. Ability to display Transitional Stored Ticket.

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

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

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

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

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

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

AOIR : N° 001/DC/2016 Page 40

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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

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

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

Printing. Ability to support the printing of coupons, receipts and itinerary/receipts. Itinerary/receipt, itinerary outputs (carrier name…) 15 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.

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

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

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

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

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

AOIR : N° 001/DC/2016 Page 41

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

EMD Management

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

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

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

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

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

3. 5. Departure Control System

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Passenger processing & Flight Control Management RES & DCS Access. Access to some reservation 1 functionalities (PNR, E-TKT, EMD, customer profile, flight program…) through DCS workstation. Integration. The RES/INV/FFP/DCS modules must be 2 fully integrated and all process must be integrated across all modules. CUTE and back office. The DCS must be certified Common User Terminal Emulation (SITA CUTE, ARINC 3 MUSE, RESA CREWS …) and can be used on back office.

DCS version for GHA. Ability to process AIR ALGERIE flights without a reduction in functionality or 4 degradation in the level of services offered when the GHA is using the same DCS solution. Interface. Ability to be interfaced with: 5 - Revenue accounting system,

AOIR : N° 001/DC/2016 Page 42

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional - 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. WorldTracer. Ability to access WorldTracer and its 6 functionalities via DCS. Additional Information for Agents. Ability to support special displays and interfaces to provide enhanced information to check-in agents : - Encode-Decode, 7 - World city time / Airport information / Other information, - Timatic, - Help. EDIFACT format. Ability to support standard EDIFACT 8 format and its variants. Capture information. Ability to capture passenger 9 information from MRZ on documents automatically upon swipe/scan. Other Devices Access. Ability to support access by structured data from intelligent devices (e.g. self- 10 service units, hand-held devices, gate readers, OCR/MSR devices …). It must support multiple devices on one workstation. Boarding Pass and Bag Tag Printers. Ability to allow a default boarding pass and Bag Tag printer for each 11 workstation whether the system is accessed via session, internet or Web. Printing. Ability to issue boarding pass and tag bag 12 according to the loaded PECTABs in the system. Print Options. Ability to support the printing in hardcopy form all types of passenger informational 13 displays either as a “screen dump” or specifically formatted for hardcopy. Printing must be to any host defined output device. PECTAB. Ability to send an AEA Parametric Data Concept message for bag tag and boarding pass to 14 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 43

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional IATA Standards. PECTAB. Ability to print Arabic characters and 15 graphical forms (logo …) in the boarding pass. PECTAB Updates. Ability to change the PECTAB 16 tables and to control/manage the changes with regard to the BP/BT documents used in each station. RFID. Ability to generate RFID tags and support all 17 related functions to RFIDs (e.g. tracking and locating etc.) Text and remarks. Ability to add free format text and 18 remarks on the boarding pass. 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 19 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. Aircraft Types-View & Copy. Ability to display all aircraft types and their configurations. It must be 20 possible to copy and then amend a type/configuration to create a new aircraft type/configuration. Aircraft Types-Create. Ability to configure each aircraft and add the configuration into the database 21 in a swift and accurate method according to the standard format. Online Aircraft Changes. Ability to cater for late equipment changes, reweighs/reconfigurations. 22 These changes must be updated in the reservation and inventory systems. Seat Characteristics. Ability to support all standard seats types’ characteristics. e.g. : window seat, aisle seat, over wing, forward, rear, restricted recline, exit 23 row, basinet row, permanently blocked seat ...Plus, seats characteristics which are user definable.

AOIR : N° 001/DC/2016 Page 44

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Seat Characteristics Amendment. Ability to amend individual or groups of seats’ characteristics for specific aircraft and/or aircraft type either 24 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. Seatmap. Ability to show all facilities in the seatmap, 25 e.g. toilet and galley. Change Seat Assignment. Ability to change seat assignment with automatic generation of new boarding pass and check-in agent warning. It must be 26 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. Inhibited Seat Assignment. Ability to inhibit seat assignments (e.g. no infants in exit rows). Wherever 27 possible this should be warned automatically by the system, with the capability to override manually. Pre-Assigned Seats. Ability to edit/release any pre- 28 assigned seats and/or protected seats both manually and based on system time parameters. Re-assign Seat. Ability to provide the functionality to 29 re-seat or offload/delete a checked-in/boarded passenger either individually or by groupings.

Non-reservations Flight Creation. Ability to create 30 revenue flights, charter flights, cargo flights, Ground Handling flights, test flights, pseudo flights… Flight status. Ability to support the following flight status: - Flight editing, - Check-in Suspended, - Flight Open for check-in from all channels, 31 - Flight Held, - Flight updated, - Flight closed for check-in, - Flight gated, - Flight finalized, - Post Departure. Flight Amendment. Ability to add a leg to an open 32 flight without any disruption for the check-in process. Re-open Flight. Ability to re-open a post departed 33 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 45

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Online Flight Changes. Ability to accept late flight 35 changes, and must be updated in the inventory system. PNL/ADL. Ability to support PNL/ADL processing 36 (codeshare flights, third party…). Flight open. Ability to open Flight for specific check- in channels based on configurable parameters: 37 Airport check-in, Inbound Through Check-in, Web check-in.

Online/Offline. Ability to set and manage a station as 38 online or offline (station handled in a different DCS). Stations. Ability to identify the stations for which General Declaration (GD) is required, and maintain 39 this list of stations. The GD must be sent automatically. Government order. Ability to set a flight as eligible for API/APP/AQQ/PNRGOV/iAPI printing of the 40 boarding pass is inhibited until the complete API data are submitted.

New Regulations security/immigration processing to support control authorities. Ability to comply with 41 any future Government initiatives before the compliance date set by the Government. US DOT. The DCS must be certified to work with the 42 USDOT/TSA and support existing regulations. 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 43 of the boarding pass must be inhibited in case of mismatch and the check-in agents prompted. The database must be regularly updated. Limitations on the flight. Ability to allow the following limitations on the flight : - Number of infants according to aircraft 44 type, - Number of WCHx, - Jump seats, - Number of passengers in the waitlist... ETKT/PNR access. Ability to retrieve and display the passenger’s PNR and ETKT from DCS, via a line 45 number reference, or seat number reference, boarding number, a bag tag number or PNR code.

AOIR : N° 001/DC/2016 Page 46

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional 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 46 more passengers). This functionality should allow one or more remarks to be entered into all PNRs selected. SSR/OSI Codes. The application must process SSR/OSI elements at check-in and provide the check- 47 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. Frequent flyer number. Ability to check and validate 48 the frequent flyer number with regard to the customer profile. FQTV Validation. Ability to validate FQTV in DCS for 49 other airlines program according to the bilateral agreement. 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, ...); 50 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. Arrival/departure flights. Ability to display arrival/departure flights list by date : - Flight number - Destination - STD/STA - ETD/ATD 51 - ETA/ATA - Aircraft registration - Number of passengers booked - Flight status - Terminal - Gate number.

AOIR : N° 001/DC/2016 Page 47

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional 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 52 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. Passenger Lists. Ability to display passenger and standby lists including “logical opposite” options 53 such as “Non-Checked in”, All lists as defined in Reservations e.g.: list by class, by SSRs, … Passenger Check-in list Display is required : - Flight number - Full name - Gender - Seat number 54 - Baggage Piece/Weight - Class - Segment - Checked-in by - SSR and comments - Check-in status Passenger Display Check-in. Ability to support passenger check-in from a passenger list or full 55 passenger display (i.e. supplying the line number for a single party or multiple numbers/range of numbers for multiple party check-in). Passenger Name Check-in. Ability to support passenger check-in by a portion of passenger name, including providing a Similar Names List from which 56 to select, if similar names exist. Example, require agent to enter only first two characters of passenger name, followed by number in party. 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 57 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. Partial PNR acceptance. Ability to support Partial PNR processes, e.g. only one passenger from a PNR 58 checking-in with others either checking in at a subsequent time or being treated as no-shows. The

AOIR : N° 001/DC/2016 Page 48

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional application should automatically attempt to reserve suitable seats for other passengers in the PNR so that they will be seated together if possible. Cancel Check-in Transaction. Ability to cancel all 59 incomplete (pending) check-in requests.

Pseudo Groups/Parties. Ability to identify passengers who have been checked-in together even 60 though they are traveling on different PNRs (i.e. pooling). Upgrade/Downgrade. Ability to manually upgrade or 61 downgrade a passenger into a different cabin and or class. Upgrade/Downgrade. Ability to provide a mechanism to manage Upgrade/Downgrade lists. This includes passengers being automatically or 62 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. Check-in inhibition. Ability to inhibit check-in 63 without an E-ticket number. Accumulate weight. Ability to accumulate the total weight of all checked-in bags, with possibility to print 64 each piece weight on the tag bag in addition to the total weight of all bags. Bag Tag from Passenger Display. Ability to support issuing bag tags from a passenger list or full 65 passenger display (i.e. supplying the line number for a single party or multiple numbers / range of numbers for multiple bag tag issue). Replacement Bag Tags. Ability to replace previously issued tags. The original bag tags would be 66 deleted/cancelled and the new ones would reflect the checked baggage. A record of old/deleted bag tag numbers would retain. 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 67 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 49

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional * Frequent flyer entitlement, * Agent discretionary waivers * Prepaid bags - Restrict the boarding pass print. This setting shall be configurable. Excess Baggage Coupon. Ability to print excess baggage coupon by weight and piece. The coupon must include: - Flight number, 68 - Routing, - Passenger name, - Sequence number, - Excess baggage weight, - Number of extra pieces. Re-issue Boarding Pass. Ability to reissue a previously issued boarding pass. The check-in agent 69 should be prompted to retrieve the original boarding pass from the passenger. Payment Collection. Ability to collect ancillary 70 services fees and issue EMDs. Bulk Transfer. Ability to bulk transfer passengers (whether checked-in or not, standby...), with all their 71 relevant information, from one flight to another and from one airport to another. Disruptions managements & Automatic Seat Re- 72 accommodation in case of flight equipment change. Flight Interruption Manifest. Ability to support FIMs 73 according to IATA recommendations. Codeshare flight. Support operating carrier and 74 marketing carrier flight numbers and carrier codes for IATCI down-line connections. Codeshare Tags. Ability to print the true operating 75 carrier flight number on the bag tag as required. IATCI. Ability to support all IATCI standards and recommended practices including Interline Fall Back 76 (IFM) messages and bi-directional messages for Through Check-in. Connection Flight Data. Ability to add manually 77 connection flight data to a passenger’s DCS records and automatically perform through check-in. Through/Transit Passengers. Ability to manage 78 Through/Transit passengers in the same manner as originating passengers are handled.

AOIR : N° 001/DC/2016 Page 50

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Non-Revenue Passengers. Ability to provide a mechanism to manage Non- Revenue passengers and 79 identify Non-Revenue passengers based on UL rules at all stages of the check-in process. Auto Seat or Standby. Ability to auto-examine the availability of seat upon check-in and either assign a 80 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. Standby Handling. Ability to provide a manual and 81 automated management of standby passengers revenue/nonrevenue, based on business rules. Cockpit Access. Ability to support the assignment of 82 Jump Seats and cockpit seats for qualified personnel. Jump seat. Ability to show Jump seat passenger figures in : - Passenger manifest 83 - Total checked-in figures - Relevant post departure messages - BSM for the baggage accepted Passenger Boarding/De-boarding. Ability to mass 84 board/de-board the aircraft (Automatically or manually). Gate Assignment. Ability to assign flights to a gate 85 and change the gate assignment as required. Boarding documents. Ability to generate boarding 86 documents for control e.g.: PIL, passengers’ counts, missing passengers report… Meal calculations. Ability to calculate the expected 87 number of meals in each cabin. Messages Addresses Ability to support an unlimited 88 number of addresses to receive check-in and loading messages as the flight is closed out. Post-Departure Messages. Ability to generate all lists and send (automatically or manually) all IATA 89 standard messages at flight departure such as FTL, PSM, PTM, SOM, TPM, and IDM... Inhibit messages generation. Ability to inhibit 90 messages generation for Training flights, Test flights … PFS Codeshare. Ability to support a split PFS 91 messages for codeshare flights.

AOIR : N° 001/DC/2016 Page 51

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Flights processing. Ability to default any session to any flight (one or multiple flights). This enables the 92 check-in agent to input transactions without the need to repeat the flight number and date in the input. Flights processing. Ability to process multiple flights 93 on the same screen. Ramp management tools. Ability to 94 manage/coordinate Ramp tasks. History transactions. Ability to capture all flight transactions for any level and retrieve the report 95 online (the supplier must specify the number of days that history is Available in the system). Reports. Ability to provide different reports by agent 96 code e.g. Number of PAX checked-in … Load Control Centralized Load Control. Ability to support 97 Centralized Load Control including multi flight handling. Integration. Weight & Balance and check-in 98 functionalities must be fully integrated within DCS. User profiles. Ability to allow the creation and differentiation of user profiles e.g. load control 99 Supervisor / Agents etc. and provide secure single login feature. 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, 100 - 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.

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

AOIR : N° 001/DC/2016 Page 52

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional and other load-planning related messages. IATA messages. Ability to process incoming LDM, 102 LPM, and CPM messages from an up-line station with third party mechanism. Supplementary information. Ability to display and 103 update supplementary information that may be associated with all types of messages. Capturing of changes. Ability to capture the changes of cargo/mail/baggage/COMAIL made by local airline 104 personnel at stations as defined by the business rules. Aircraft Types. Ability to support these aircraft types : 105 - narrow / wide bodied, - Multi deck, Combis and freighters. - Multi sector / charter / ad hoc. Ability to support 106 transfer / multi sector / charter / ad hoc flights. Aircraft changes. Ability to support aircraft changes 107 automatically or manually actioned by load control. Lock/unlock. Ability to provide the facility to lock, 108 unlock a flight and cancel a flight from the System. Estimated zero fuel weight. Ability to provide 109 Estimated zero fuel weight information and fuel data to/from Flight Planning System. Standard IATA UWS. Ability to receive standard IATA 110 UWS cargo messaging for load planning and finalization. Graphical aircraft loading. Ability to support 111 graphical aircraft loading capabilities (move/swap/drag/drop load items). Hosting OAL. Ability to host other airlines for load 112 control. Creation of flights. Ability to support creation of 113 flights at departure, en-route and diversion stations including offline stations. IATA load control documents. Ability to provide generation and printing of IATA load control documents including graphical for (but not limited to): 114 - Load Instruction Report, - Provisional / Final / ACARS Load Sheet, - ZFW Messages, - Fuel Loading Instruction, - NOTOC documents.

AOIR : N° 001/DC/2016 Page 53

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Load planning. Ability to provide a customer- 115 configurable table of passenger and baggage weights to be used for load planning purposes. Weight table. Ability to change passenger/baggage 116 weight table (load planning or check-in) for a flight. Load sheets via ACARS. Ability to provide the facility 117 of sending load sheets via ACARS. ACARS messaging. Ability to provide free format 118 ACARS messaging with option to inhibit by location, sign-in level, etc. Preplanning purposes. Ability to store historical data 119 in the system for preplanning purposes. Trimming. Ability to support trimming by: 120 - class/cabin & seat row, - compartment/bay. Adjustable and restricted weight. Ability to support 121 maximum, adjustable and restricted weight and trim limitations for ZFW, TOW, LDW, RTOW, TW. Control parameter. Ability to automatically calculate, recalculate and validate the control parameter as and when any cargo, mail, baggage weight / 122 passenger weight / crew / catering or placement data is added, modified, or deleted from external system or DCS. Graphical presentation of balance conditions. Ability to provide a graphical presentation of balance 123 conditions, including Ideal Trim Range / C of G for ZFW, TOW, LDW and MAC. Different colors are used to depict different limits. Baggage classification. Ability to support all types of 124 baggage classification. E.g.: BF, BC, BY, BT, BR … Local / transfer dead-load. Ability to provide a 125 display of all local / transfer dead-load. Auto-load distribution. Ability to support auto-load 126 distribution with optimal balance. Dangerous Goods conditions. Ability to incorporate 127 Dangerous Goods conditions. 128 Loads transfer. Ability to support all loads transfer. Jump seats. Ability to display jump seats on the load- 129 sheet. LDP documents. Ability to store/retrieve/reprint all 130 LDP documents (load-sheet, load-plan …).

AOIR : N° 001/DC/2016 Page 54

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional Out of balance limitations. Ability to alert for any 131 out of balance limitations. Balance condition. Ability to adjust balance 132 condition by offloading manually an overloaded aircraft. Final weights. Ability to use only final weights after 133 flight closure. Validate flight closure. Ability to validate flight 134 closure and load sheet issuance according to capacity limitations. 135 AHM 560 & 565. Ability to support AHM 560 & 565. IATA 560 & 565 format. Ability to print database in 136 standard IATA 560 & 565 format. Static database. Ability to manage static database 137 (display, add, update, delete …) according to user authority. ULD database. Ability to provide ULD database, to 138 include individual / ULD type tare weights and ULD numbers according to business rules. Display/re-print. Ability to display/re-print load- 139 sheet, load plan and NOTOC after departure. Real time history. Ability to display all users’ 140 transactions.

3. 6. Fare Quote System

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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

AOIR : N° 001/DC/2016 Page 55

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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

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

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

Best Buy pricing from fares. Ability to display the “lowest fare” by sorting fares over through fares in order, from low to high. 9 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.

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

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

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

Additional information. Ability to retrieve additional information based on : - RBD by carrier, 13 - Routing, - specific rule category, - Taxes/fees (ATPCO service fees)/other charges.

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

AOIR : N° 001/DC/2016 Page 56

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

Pricing currency. Ability to price: - Itinerary using specific currency, 17 - In currency of choice unless inhibited by AH specific rules or government regulation.

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

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

Price itinerary. Ability to price with specific segment, multiple segments, combined with any one or combination of : 20 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…

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

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

Pricing. Ability to manage different IATA pricing 23 controls.

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

Reason for failure. Ability to provide the reason for failure when the itinerary does not price as 25 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 57

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

provide normal fare of the relevant cabin otherwise IATA fares.

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

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

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

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

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

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

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

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

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

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

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

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

AOIR : N° 001/DC/2016 Page 58

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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

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

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

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

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

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

3. 7. Revenue Management System

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Revenue Management System

General :

1 Integration. Must be Integrated with Inventory.

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

AOIR : N° 001/DC/2016 Page 59

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

3 Ability to provide a leg based system.

4 Ability to be upgradeable to O&D system.

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

Ability to control economic, business and first 6 cabin.

7 Ability to control code share flights.

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

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

10 Ability to ensure a competitive intelligence.

11 Ability to handle more than 26 classes.

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

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

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

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

Ability to manage and influence forecasting and 16 optimization process.

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

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

Forecasting

19 Ability to provide different forecasting models.

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

AOIR : N° 001/DC/2016 Page 60

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

Ability to take in consideration Pricing elasticity 23 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.

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

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

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

Optimization

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

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

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

Ability to fill and extract data automatically and 33 frequently.

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

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

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

AOIR : N° 001/DC/2016 Page 61

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Overbooking

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

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

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

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

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

Reporting

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

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

The system must be able to : - Select a variety of fields according to user 44 criteria, - Provide report about all user's actions.

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

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

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

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

AOIR : N° 001/DC/2016 Page 62

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

50 Ability to provide categorization tables.

Ability to provide reports about availability by 51 class.

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

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

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

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

Group Management

The RMS must include a Group management 56 module.

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

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

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

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

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

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

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

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

AOIR : N° 001/DC/2016 Page 63

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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

68 Must provide an evaluation rate of the flight.

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

70 Must provide evaluation report.

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

Ability to manage Groups requests collected from 72 travel agencies.

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

3. 8. Revenue Integrity

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Revenue Integrity Management

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

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

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

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

AOIR : N° 001/DC/2016 Page 64

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Ability to detect : - MCT violation; - Impossible journeys according to business 5 rules; - Redundant segments; - Churning PNRs.

Duplicate PNRS. Ability to detect duplicate PNRS for Overlapping flight times and Incoherent or duplicated segments / O&D itineraries according 6 to defined rules such as : - Name Comparison - Information from the PNR (passenger contact, FFP number, Gender, APIS, Date of birth).

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

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 8 day; - Same Class(es); - Booked by same booking office (IATA/Pseudo City Code or Booking Office ID) - Total passengers in combined PNRs.

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

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

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

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

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

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

AOIR : N° 001/DC/2016 Page 65

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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

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

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

3. 9. E-Commerce

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

IBE management

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

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

Administration Tools. Ability to: - Customize the IBE with the look and feel of AIR ALGERIE’s brand, 3 - Configure page layouts, - Modify and optimize booking flows (E.g. change/ reduce booking steps).

Administration Tools. Ability to : - Customize and categorize ancillary services and cross-sells, 4 - Configure promotional web offers/corporate offers, - Enable and disable features, preview changes,

AOIR : N° 001/DC/2016 Page 66

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

track changes and roll back changes.

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

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 6 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.

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

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 8 search, week-end search, budget driven, period of stay...). Result travel recommendations should be displayed in easy manner for a quick comparison and upsell.

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

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

Hosting. The solution must support : - Availability and Risk management - High availability (99.9 uptime is the minimum 11 required) - Online traffic including temporary peaks/overloads. - Traffic evolution, smooth and fast navigation.

AOIR : N° 001/DC/2016 Page 67

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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) 13 - 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.

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

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

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

Availability Search. Ability to support combined criteria for availability search including : - Trip type (OW, RT, itineraries with multiple stopovers, open jaws,), - Reservation class, 17 - 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.

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

AOIR : N° 001/DC/2016 Page 68

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

19 Group Booking. Ability to handle group booking.

Calendar Display. Ability to support Calendar fares 20 display.

Fares. Ability to support: - Fare families/branded fares, - Online/web oriented fares, - Typological fares according to selected PTC 21 (adult, infant, child, student, senior, youth, UM…), - Behavioral fares (family plan, couple plan…), - Web discount code capabilities.

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

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

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

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

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

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

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

29 Currencies. Ability to price in multiple currencies.

AOIR : N° 001/DC/2016 Page 69

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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, 32 - 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.

Passenger Information. Ability to : - Manage/configure travel requirements information (e.g. APIS based on 33 departure/destination), - Support specific PTC information (e.g. Extra contact Info for UM).

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

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

Ancillary services. Ability to : - Offer air and non-air (standalone) services - Offer chargeable and non-chargeable ancillaries and issue EMD. 36 - 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

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

AOIR : N° 001/DC/2016 Page 70

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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

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

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

Payment Gateway Interface. Should integrate all payments methods currently used : 41 - Visa, MasterCard (OGONE Payment Gateway ), - CIB card (local payment method with SATIM payment gateway).

Payment. Ability to integrate all major payments methods widely used : 42 - Credit Card : Amex, DinersClub …, - E-banking: Sofort , Giropay…, - E-wallet : PayPal …

43 FOP. Ability to support multiple FOP.

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

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 45 languages support…), - Process payment transactions, - Send customizable email confirmations, - Deliver a full visibility of transactions and comprehensive reporting/ Fraud analytics reports.

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

AOIR : N° 001/DC/2016 Page 71

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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. 47 - 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.

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), 49 - 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).

Manage my booking. Ability for the customer to change their booking. This includes, adding segments, managing passenger details such as 50 special service requests, adding passport information, frequent traveler data, and exchanges.

Manage my booking. Ability to retrieve Booking using: 51 - Name / Booking Reference, - Name / ETKT.

Online changes. Ability to support: - Re-pricing &Reissue or refund, 52 - Compute upgrade fees with payment collection, - Advanced shopping display.

AOIR : N° 001/DC/2016 Page 72

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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 53 content will be defined, - Support additional information, - Attach documents in emails (e.g. fare conditions, ETKTs...), - Support multiple languages, at least FR, EN, AR.

IBE generated documents (e.g. ETKTs, e-boarding pass, EMD…). Ability to: 54 - Customize documents content, - Support standard format (e.g. PDF) - Support multiple languages

Multiple languages. Ability to support multiple 55 languages in all IBE interfaces (French, English and Arabic….).

Flight Status. Ability to provide flight status 56 through IBE /Mobile web /Mobile application.

Mobile WEB/APP. Ability to provide an 57 optimized/customizable user interface.

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, 58 - 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 73

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Mobile App. Ability to provide an IOS and Android Application with similar services as the mobile/desktop version : - Update , maintenance and management is 59 provider responsibility, - Ability to provide hosting on Google Play and AppStore on behalf of AIR ALGERIE, - Ensure maintenance and upgrades according to technology evolution.

Award Shopping. Ability to provide Award shopping and redemption facilities. 60 Ability to combine multiple FOP (e.g. combination of miles and cash for award tickets).

Upgrade Award. Ability to provide automatic 61 upgrade award.

Reporting. Ability to provide reporting for: 62 - Usage of promotional/corporate code, - Cross-sells and ancillary services.

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 63 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…).

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- 64 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 74

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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, 65 - 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.

B2B. Ability to manage corporate customers across : - Online booking, - Corporate fares application, 66 - Corporate loyalty program, reward benefit, - Promotional offers, - Notifications for special offers, - Reporting features.

Irregularity Management. Ability to enable online reissue/ free re-accommodations / chargeable 67 upsells based on Involuntary rules. Ability to provide notifications.

3. 10. Loyalty Management System & Customer experience

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Loyalty Management

1 Integration. Must be Integrated with the PSS core.

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

Membership card number. Ability to : - Contain at least 11 digits with a check digit, 3 - Define number range for each enrolment channel, by city codes, territory etc…

AOIR : N° 001/DC/2016 Page 75

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Access Administration and user profile. Ability to define user profiles according to their roles and 4 attribute permissions to access accordingly. Ability to provide restricted access for each profile.

Enrolment. Ability to Enroll through multiple 5 channels: Internet (web, mobile), Reservation system, DCS, upload batch, online system.

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 6 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 76

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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, 7 - 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.

Sub Programs. Ability to support the creation and management of multiple frequent flyer sub- 8 programs on the same customer base (e.g. Family Programs, VIP Programs, and Guest Programs).

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, 9 - 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.

Fulfillment. Ability to provide data to fulfillment 10 house and reverse feedback from fulfillment house for returned and undelivered mails.

AOIR : N° 001/DC/2016 Page 77

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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, 11 - 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).

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, 12 - 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),

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, 13 - 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 78

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

- Provide automated billing, - Support specific codeshare rules for partner accrual (i.e. operating vs. marketed carrier),

Campaigns. Ability to : - Setup, configure and manage promotions through campaign management engine, - Support accrual and redemption promotional campaigns, 14 - Allow both targeted and generic campaigns using any parameter in customer profile, - Use multiple interfaces to register for campaigns, - Provide campaign performance monitoring.

Accrual processing. Ability to - Process accrual based on Batch or Airline PSS data on real time, 15 - Accrue miles according to: booking class, flown class, segment, O&D, flight number, revenue/non-revenue segment etc…

PNR data. Ability to: - Store and view booked and flown data, 16 - Provide Reservation and Check-in Information, - Submit for Retro accrual.

AOIR : N° 001/DC/2016 Page 79

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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 17 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.

Reports. Ability to provide: - Pre-defined reports, - Customized reports, - Dashboards, 18 - Exportation to standard formats (HTML, EXCEL, PDF…) - Error reports, - Fraud management reports.

AOIR : N° 001/DC/2016 Page 80

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

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, 19 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.

Alliance operations. Ability to support Alliance 21 operations.

22 Lounge access. Ability to Include lounge module.

Calculate value. Ability to calculate the member 23 value (Revenue, Importance, High Tier etc.) and provide ranking according to revenue generated.

AOIR : N° 001/DC/2016 Page 81

3. 11. Business Intelligence

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Business Intelligence

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, 1 dashboards and statistics, - Create reports with user’s defined parameters, - Export Data, reports with different format (text, Excel, word document, PDF, ZIP…).

Business Intelligence. Ability to provide Dashboards executives for an overview of : - Commercial performances (by web sells and by point of sale) data comparisons, 2 - Competitors capacity, frequency and fares market share, Opportunities (Codeshare, interlining, alliances, new routes…).

3. 12. Disruption Management System

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

Disruption Management System

Integration. Ability to interface with the whole 1 PSS components.

Flights disruption. Ability to handle in real time all 2 irregular flights operations.

Passengers Re-book. Ability to re-book automatically (ETKT, EMD, SSRs, ancillaries) 3 passengers according to the available travel alternatives.

Passengers Re-book. Ability to re-book 4 automatically passengers on connecting flights.

Re-issue and Refund. Ability to re-issue and 5 refund E-tickets automatically.

AOIR : N° 001/DC/2016 Page 82

Compliance Core or Item Functional Requirement Observation Y/N/P/F Optional

E-TKT Status. Ability to handle manually ETKT 6 coupon status.

Passenger re-accommodation. Ability to re- 7 accommodate automatically passengers from Inventory and DCS.

Baggage handling. Ability to handle passengers’ 8 baggage (re-tag, messages regeneration).

Customer Prioritization. Ability to handle priority 9 customer based on value (FFP, fares paid, class of travel...).

Disruption costs. Ability to provide cost effective 10 solution to reduce disruption costs.

Passengers Compensation. Ability to calculate 11 compensations.

Queue PNRs. Ability to queue PNRs on defined 12 queues

Notification. Ability to notify by APPS, e-mail and 13 SMS passengers affected by the disruption.

14 Reporting. Ability to provide detailed reports

AOIR : N° 001/DC/2016 Page 83

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 84

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 85

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 86

PRICES LIST

Unit Price Duty Item Description Quantity Price Free/USD One fee Migration & implementation 01 Less than 4 Million PB ……………….. Per PB

Monthly Usage, Support & Between 4 and 6 Million PB ……………….. Per PB fees Maintenance Between 6 and 8 Million PB ……………….. Per PB More than 8 Million ……………….. Per PB Price Duty Annual Evaluation Estimated number of passengers Free Total duty free on 12 Month - Year 2017 5 883 638 Borded Passengers Total duty free on 12 Month - Year 2018 6 177 820 Borded Passengers Total duty free on 12 Month - Year 2019 6 486 711 Borded Passengers Total duty free on 12 Month - Year 2020 6 811 047 Borded Passengers Total duty free on 12 Month - Year 2021 7 151 599 Borded Passengers Total price (Total Taxes Included) (USD)

All other costs must be supported by the supplier

AOIR : N° 001/DC/2016 Page 87

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 88

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 89

GLOSSARY

AOIR : N° 001/DC/2016 Page 90

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 91

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 Provider of competitive fare pricing information, seat availability and promotional data from INFARE / QL2 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 92

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

AOIR : N° 001/DC/2016 Page 93