DIVISION COMMERCIALE

Appel d’Offres International Restreint

AOIR: N° 001/DC/2016

“Système de Gestion des Passagers PSS”

pour Compagnies Aériennes Régulières

AOIR : N° 001/DC/2016 Page 1

SOMMAIRE SECTION 1: INSTRUCTIONS AUX SOUMISSONNAIRES (IS) 3

A. DISPOSITIONS GÉNÉRALES 3 1. Objet de l’Appel d’Offres 3

2. Situation actuelle 3

3. Règles d’éthique 3

4. Soumissionnaires admis à concourir 3

5. Qualification des soumissionnaires 4

6. Frais de soumission 4

7. Une offre par soumissionnaire 4

B. DOSSIER D’APPEL D’OFFRES 5 8. Contenu du dossier d’appel d’offres 5

9. Éclaircissements apportés au Dossier d’Appel d’Offres 5

10. Modification du Dossier d’Appel d’Offres 5

C. PRÉPARATION DES OFFRES 5 11. Langue de l’offre 5

12. Les Documents Constitutifs de l’offre 6

13. Montant de l’offre 6

14. Monnaie de l’offre 6

15. Validité des offres 6

16. Forme et signature de l’offre 6

D. DÉPÔT DES OFFRES 7 17. Cachetage et marquage des offres 7

18. Date et heure limite de dépôt des offres 7

19. Offres hors délai 7

20. Modification et retrait des offres 7

E. OUVERTURE DES PLIS ET ÉVALUATION DES OFFRES 8 21. Ouverture des plis par AIR ALGERIE 8

22. Confidentialité 8

23. Éclaircissements concernant les offres 8

24. Examen préliminaire et décision de conformité 9

25. Correction des erreurs 9

26. Conversion en une seule monnaie 9

27. Évaluation et comparaison des offres 9

F. ATTRIBUTION DU MARCHÉ 10 28. Critères d’attribution 10

29. Droit d’accepter ou de rejeter une ou toutes les offres 10

30. Notification de l’attribution du marché 10

31. Recours des concurrents 10

32. Absence d’obligation 11

33. Signature du contrat 11

SECTION 2: DONNÉES PARTICULIÈRES DE L’APPEL D’OFFRES (DPAO) 12

AOIR : N° 001/DC/2016 Page 2

SECTION 3 : EXIGENCES TECHNIQUES 20

1. INTRODUCTION 20

2. PRÉSENTATION D’AIR ALGERIE 20 2. 1. Informations Compagnie 20

2. 2. Faits et Chiffres 20

2. 3. Éstimation du traffic Passagers 20

2. 4. Les systèmes actuels utilisés par AIR ALGERIE 21

2. 5. Partenaires interligne actuels 21

2. 6. IET en cours 22

2. 7. Partenaires Code share 22

2. 8. Modèle Commercial 23

2. 9. Ventes indirectes via GDS pour AIR ALGERIE 23

2. 10. Émission EMD 23

2. 11. Situation actuelle de l’E-commerce 23

2. 12. DCS aux escales internationales 24

2. 13. Documents émis 26

2. 14. Compagnies assistées par AIR ALGERIE 26

2. 15. Équipements DCS en Algérie 27

2. 16. Quelques chiffres 27

2. 17. Infrastructure ATO/CTO 27

2. 18. Infrastructure réseau d’AIR ALGERIE 27

3. EXIGENCES FONCTIONNELLES 29 3. 1. Exigences générales du PSS 29

3. 2. Système d’Inventaire et Programme de vols (Inventory and Schedule) 31

3. 3. Système de Réservation (Reservation and Booking management) 35

3. 4. Système de Billeterie électronique et EMD (Ticketing and EMD) 40

3. 5. Système de Contrôle des départs (Departure Control System) 42

3. 6. Système de Tarification (Fare Quote System) 55

3. 7. Système de Gestion des recettes (Revenue Management System) 59

3. 8. Système de Fiabilisation des ventes (Revenue Integrity) 64

3. 9. E-Commerce 66

3. 10. Système de Gestion de fidélisation et expérience client (Loyalty Management System & Customer experience) 75

3. 11. Intelligence économique (Business Intelligence) 81

3. 12. Système de Gestion des irrégularités (Disruption Management System) 81

4. AUTRES EXIGENCES 83 4. 1. Plan et stratégie de Migration (Migration Plan, strategy and Risk Management) 83

4. 2. Plan d’implémentation du PSS (Implementation plan of the PSS) 83

4. 3. Tests 84

4. 4. Formation (Training) 84

4. 5. Rapports du projet (Project reports) 84

4. 6. Documentation finale (Final documentation) 84

SECTION 4: FORMULAIRES / MODÈLES DE DOCUMENTS 85

MODELE DE LETTRE DE SOUMISSION (BIDDING LETTER) 85

BORDEREAU DES PRIX 86

DÉCLARATION SUR L’HONNEUR (STATEMENT MADE ON THE HONOR) 87

LES RÈGLES D’ÉTHIQUE (ETHICS RULES) 88

GLOSSAIRE 89

AOIR : N° 001/DC/2016 Page 3

SECTION 1: INSTRUCTIONS AUX SOUMISSONNAIRES (IS)

A. DISPOSITIONS GÉNÉRALES

1. Objet de l’Appel d’Offres

“AIR ALGERIE”, lance un Appel d’Offres International Restreint destiné aux fournisseurs de Systèmes

de Gestion des Passagers ’’Passenger Service System PSS’’, hébergeant des compagnies aériennes

d’une taille similaire à celle d’AIR ALGERIE.

Les fournisseurs invités à soumissionner doivent être en mesure de fournir et de mettre en œuvre le

PSS en prenant en considération les coûts ainsi que les attentes d’AIR ALGERIE, à savoir :

- Migration vers une plateforme nouvelle génération,

- Réduction des coûts,

- Simplification des processus de gestion,

- Développement de partenariats et adhésion à une alliance,

- Offrir de nouveaux services aux clients, accroître les revenus (canaux de distribution et ventes

auxiliaires),

- Adoption d’une stratégie de centricité client,

- Avoir une meilleure visibilité pour des prises de décisions efficaces.

L’objet de cet appel d’offres est défini dans la section suivante du présent document, principalement, les

exigences fonctionnelles de la section 3 partie 3. Des fonctionnalités supplémentaires peuvent être

offertes par les répondants dans le cadre d'une offre globale. Les services et supports, le niveau de soutien

pour les processus de migration et la mise en œuvre sont des parties intégrantes de cet appel d’offre tel

que défini respectivement dans la section 3 partie 4.

2. Situation actuelle

AIR ALGERIE est le transporteur national de l'Algérie. La compagnie fournit un service de transport

passager (domestique et international) et de fret.

La situation actuelle de la compagnie est décrite dans la section 3 partie 2 de ce document.

3. Règles d’éthique

AIR ALGERIE exige des soumissionnaires à ses marchés, sous contrainte de sanctions, d’observer les

règles d’éthique professionnelle ainsi que les règles établies par le Maître de l’Ouvrage (section 4).

Ces règles font partie intégrante du Dossier d’Appel d’Offres.

4. Soumissionnaires admis à concourir

4.1 Un soumissionnaire ne doit pas :

a) faire l'objet d'une interdiction de concourir ;

b) faire l'objet d'une décision d’exclusion des Marchés d’AIR ALGERIE ;

4.2 Les soumissionnaires fourniront toutes les pièces établissant leur admissibilité à concourir que

AIR ALGERIE peut exiger.

AOIR : N° 001/DC/2016 Page 4

5. Qualification des soumissionnaires

5.1 Les Soumissionnaires fourniront, en utilisant les formulaires de la Section 4, une description préliminaire

de la méthode de travail qu’ils entendent appliquer ainsi que du calendrier de travail, y compris plans et

tableaux, le cas échéant.

Pour être admis à l’attribution du marché, les soumissionnaires devront satisfaire aux critères de

qualification minimum spécifiées dans les DPAO (section2).

5.2 Tous les soumissionnaires devront fournir et inclure dans leur offre les informations, les documents ainsi

que les formulaires figurant dans les DPAO et la Section 4.

5.3 Les soumissions présentées par un groupement de deux entreprises ou plus réunies en partenariat

seront régies par les dispositions suivantes, sauf disposition contraire spécifiée dans les DPAO :

(a) La Soumission inclura toutes les informations requises à la sous clause 5.2 ci-dessus des IS pour

chacun des partenaires (les noms complets et les adresses du siège social et des bureaux des

sociétés constituant le groupement)

(b) La Soumission sera signée de manière à engager tous les partenaires ;

(c) Tous les partenaires seront conjointement et solidairement responsables de l’exécution du contrat

conformément aux dispositions du marché ;

(d) L’un des partenaires sera désigné mandataire, et sera autorisé à recevoir les paiements et les

instructions pour et au nom de tous les partenaires du groupement d’entreprises; et

(e) L’exécution de la totalité du Marché, y compris les paiements, sera effectuée exclusivement en

relation avec le partenaire désigné en qualité de mandataire ;

(f) Une copie de l’Accord de Groupement d’entreprises conclu par les partenaires sera déposé en

même temps que la soumission; ou, une Lettre d’intention de souscrire à un accord de

Groupement d’entreprises au cas où le Marché lui était attribué sera signée par tous les

partenaires et déposée avec la soumission accompagnée d’une copie du projet d’Accord.

Les soumissionnaires ne sont pas autorisés à former un ou des groupement(s) d’entreprises ou

consortium(s) avec d’autres soumissionnaires, ni à changer de partenaire ou à modifier la structure de

groupement d’entreprises ou consortium, après la remise des offres (offre technique, ni dans l’offre

commerciale lorsque l’offre au titre de la première étape a été remise par une seule entreprise ou un

groupement d’entreprises).

6. Frais de soumission

Le Soumissionnaire supporte tous les frais liés à la préparation et à la remise de sa soumission.

AIR ALGERIE n'est en aucun cas responsable de ces frais, quel que soit le déroulement ou l'issue de la

procédure d'appel d'offres.

7. Une offre par soumissionnaire

Chaque Soumissionnaire ne présentera qu’une seule offre, soit à titre individuel, soit à titre de

partenaire d’un Groupement d’entreprises. Si un Soumissionnaire présente plus d’une offre ou participe

à plus d’une offre (sauf en qualité de sous-traitant) toutes les offres auxquelles il aura participé seront

exclues.

AOIR : N° 001/DC/2016 Page 5

B. DOSSIER D’APPEL D’OFFRES

8. Contenu du dossier d’appel d’offres

8.1 Le Dossier d'Appel d'Offres (DAO) décrit les services faisant l'objet du marché, fixe les procédures de

l'Appel d'Offres et stipule les conditions du marché. Le dossier comprend les documents énumérés ci-

après et doit être interprété, le cas échéant, avec les additifs publiés conformément à la Clause 10 (IS) :

Avis d’Appel d’Offres

Section 1 : Instructions aux Soumissionnaires (IS)

Section 2 : Données Particulières de l'Appel d'Offres (DPAO)

Section 3 : Spécifications Techniques

Section 4 : Formulaires / Modèles de documents

8.2 Les Soumissionnaires sont responsables d’examiner toutes les instructions, formulaires,

dispositions et spécifications contenues dans le dossier d’appel d’offres. Le manquement éventuel du

Soumissionnaire à fournir les informations exigées ou à soumettre une offre qui ne soit pas conforme

pour l’essentiel au dossier d’appel d’offres pourra conduire au rejet de son offre.

9. Éclaircissements apportés au Dossier d’Appel d’Offres

Un Soumissionnaire éventuel qui désire des éclaircissements sur le Dossier d’appel d’offres peut en faire

la demande par écrit à l’adresse d’AIR ALGERIE figurant dans les DPAO. AIR ALGERIE répondra par écrit à

toute demande d’éclaircissement à condition que la demande soit reçue vingt et un (21) jours avant la

date limite de dépôt des soumissions. Une copie de la réponse d’AIR ALGERIE, indiquant la question

posée mais sans en indiquer l’auteur, sera adressée à tous les acquéreurs du Dossier d’appel d’offres.

10. Modification du Dossier d’Appel d’Offres

À tout moment avant la date fixée pour le dépôt des offres, AIR ALGERIE peut modifier le Dossier

d'Appel d'offres en publiant un additif.

Tout additif ainsi publié fait partie intégrante du Dossier d'Appel d'Offres et sera communiqué par écrit à

tous les soumissionnaires qui ont retiré le Dossier d'Appel d'Offres et leur sera opposable.

Afin de donner aux soumissionnaires suffisamment de temps pour tenir compte de l'additif dans la

préparation de leurs offres, AIR ALGERIE pourra reporter, autant que nécessaire, la date limite de dépôt

des offres.

C. PRÉPARATION DES OFFRES

11. Langue de l’offre

Tous les documents relatifs à l’offre seront rédigés dans la langue spécifiée dans les DPAO (section 2).

Les documents complémentaires et les imprimés fournis par le Candidat dans le cadre de la soumission

peuvent être rédigés dans une autre langue à condition d’être accompagnés d’une traduction des

passages ad hoc dans la langue spécifiée, auquel cas, aux fins d’interprétation de l’offre, la traduction

fera foi.

AOIR : N° 001/DC/2016 Page 6

12. Les Documents Constitutifs de l’offre

La liste des documents constitufis des offres technique et commerciale est décrite dans le DPAO.

13. Montant de l’offre

13.1 Le Marché comprendra la totalité des services tels que décrits dans les Spécifications (Section 3),

présenté par le Soumissionnaire.

13.2 Le Soumissionnaire indiquera les prix de tous les éléments des services décrits dans les spécifications

et indiqués dans la Section 3. Les éléments pour lesquels aucun prix ne sera indiqué ne seront pas payés par

AIR ALGERIE lorsqu’ils seront exécutés et seront réputés avoir été inclus dans les autres prix figurant dans le

programme d’activités.

13.3 Tous les droits, taxes et autres redevances qu’il appartient au Prestataire de payer en vertu du Marché

seront inclus dans le prix total de l’offre présentée par le Soumissionnaire.

13.4 Les prix offerts par le soumissionnaire sont fermes et non révisables pendant toute la durée du marché

et ne peuvent varier en aucune manière, sauf stipulation contraire précisée dans les DPAO.

14. Monnaie de l’offre

Les prix seront libellés en dollars (USD).

15. Validité des offres

Les offres demeureront valides pour la durée indiquée aux DPAO à partir de la date d'ouverture des plis.

Dans des circonstances exceptionnelles, avant l'expiration du délai initial de validité des offres, AIR ALGERIE

peut demander aux soumissionnaires de proroger la durée de validité pour une durée additionnelle

déterminée. La demande et les réponses doivent être faites par écrit. Un Soumissionnaire peut refuser de

proroger la validité de son offre. Le Soumissionnaire qui accepte de proroger la durée de validité de son offre

ne peut modifier son offre ni ne sera autorisé à le faire.

16. Forme et signature de l’offre 16.1 Le Soumissionnaire préparera un original et le nombre de copies de l'offre indiqué aux Données particulières de l'Appel d'Offres, mentionnant clairement sur les exemplaires "ORIGINAL" et "COPIE" selon le cas. En cas de divergence entre l'original et les copies, l'original fera foi.

16.2 L'original et toutes les copies de l'offre seront tapés; ils seront signés par le Soumissionnaire ou par une

personne ou des personnes dûment autorisée(s) à engager celui-ci. Toutes les pages de l'offre, sauf les

prospectus imprimés, seront paraphées par le ou les signataires.

16.3 L'offre ne doit comporter aucune modification, suppression ni surcharge, à moins que de telles

corrections ne soient paraphées par le ou les signataires de la soumission.

AOIR : N° 001/DC/2016 Page 7

D. DÉPÔT DES OFFRES

17. Cachetage et marquage des offres

17.1 Les soumissionnaires placeront l'original et les copies de leur offre dans des enveloppes séparées et

cachetées portant la mention "ORIGINAL" et "COPIE" selon le cas. Ces enveloppes seront ensuite placées dans

une enveloppe extérieure qui devra également être cachetée.

17.2 Les enveloppes intérieure et extérieure :

a) Seront adressées à AIR ALGERIE à l'adresse indiquée aux Données particulières de l'Appel d'Offres ;

b) Porteront le nom du projet, le titre et le numéro de la Lettre d'Invitation ou de l’Avis d’Appel

d’Offres, tels qu'indiqués aux Données particulières de l'Appel d'Offres,

c) Porteront « la mention de ne pas ouvrir avant le jour et l'heure fixés pour l'ouverture des plis »,

comme spécifié aux DPAO.

17.3 Les offres préparées par le soumissionnaire doivent être présentées obligatoirement en deux parties

distinctes, offre technique et offre financière.

À l’intérieur de l’enveloppe extérieure, l’offre doit être divisée en deux enveloppes portant le titre ainsi que le

type d’enveloppe ; les deux enveloppes seront réparties comme suit :

– Offre Technique

– Offre Commerciale

Les enveloppes intérieures porteront chacune le nom et l'adresse du Soumissionnaire de façon à permettre à

AIR ALGERIE de renvoyer l'offre cachetée si elle a été déclarée "hors délai" conformément à la Clause 19 (IS).

17.4 Si l’enveloppe extérieure n’est pas cachetée et marquée comme stipulé ci-dessus, AIR ALGERIE ne

sera pas responsable si le dossier est égaré ou ouvert avant la date limite prévue.

18. Date et heure limite de dépôt des offres

18.1 Les offres doivent être reçues par AIR ALGERIE à l'adresse spécifiée et au plus tard à l'heure et à la date

indiquées aux Données particulières de l'Appel d'Offres.

18.2 AIR ALGERIE peut, en cas de nécessité, reporter la date limite fixée pour le dépôt des offres en

publiant un additif conformément aux dispositions de la Clause 10 des IS, auquel cas tous les droits et

obligations d’AIR ALGERIE et des soumissionnaires précédemment régis par la date limite initiale seront régis

par la nouvelle date limite.

19. Offres hors délai

19.1 Toute offre reçue par AIR ALGERIE après l'expiration du délai de dépôt des offres, fixé par AIR ALGERIE

sera écartée et renvoyée au Soumissionnaire sans avoir été ouverte.

19.2 Les offres arrivées hors délais sont réceptionnées par AIR ALGERIE avec la mention « Hors délais ». Le

cachet du bureau d’ordre général ou du bureau de réception des offres d’AIR ALGERIE, selon le cas et tel

qu’indiqué dans les DPAO, fait foi.

20. Modification et retrait des offres

20.1 Le Soumissionnaire peut modifier ou retirer son offre après l'avoir présentée, sous réserve qu’AIR

ALGERIE reçoive notification écrite de la modification ou du retrait avant les, date et heure limites de dépôt

des offres.

AOIR : N° 001/DC/2016 Page 8

20.2 La notification de modification ou de retrait de l'offre par le Soumissionnaire sera préparée, cachetée,

marquée et envoyée conformément aux dispositions de la Clause 17 des IS. Les enveloppes extérieures

porteront toutefois de plus la mention "MODIFICATION" ou "RETRAIT" selon le cas. Le retrait peut être fait par

une notification écrite dûment signée, et reçue avant la date limite fixée pour le dépôt des offres.

20.3 Aucune offre ne peut être modifiée après la date limite de dépôt des offres.

20.4 Aucune offre ne peut être retirée dans l'intervalle compris entre la date de dépôt des offres et

l'expiration de la période de validité de l'offre spécifiée par le Soumissionnaire dans sa soumission.

E. OUVERTURE DES PLIS ET ÉVALUATION DES OFFRES

21. Ouverture des plis par AIR ALGERIE

21.1 AIR ALGERIE ouvrira les plis, y compris les modifications effectuées conformément aux dispositions

de la Clause 20 des IS, à la date, à l'heure et à l'adresse précisées aux Données Particulières de l'Appel d'Offres

ou dans l’Avis d’Appel d’Offres.

21.2 AIR ALGERIE procédera en deux étapes :

– Première étape (Étape technique) : AIR ALGERIE procédera d’abord et uniquement à l’ouverture des

enveloppes extérieures, contenant les offres techniques et toutes les pièces, autres que celles ayant

trait au prix, procédera à l’analyse en détail et l’évaluation des offres techniques ne contenant

aucune indication de prix.

– Deuxième étape (Étape commerciale) : AIR ALGERIE procédera ensuite à l’ouverture des plis, à

l’évaluation, au contrôle de conformité et au classement des offres commerciales, des seuls

soumissionnaires dont les offres sont déclarées techniquement conformes à l’issue de la première

étape.

22. Confidentialité

22.1 Les renseignements relatifs à l’examen, aux éclaircissements, à l’évaluation et à la comparaison des

soumissions et aux recommandations en vue de l’attribution du marché ne seront pas divulgués aux

Soumissionnaires ni à aucune autre personne qui n’est pas officiellement concernée par ce processus avant que

la publication de l’attribution au Soumissionnaire sélectionné n’ait été annoncée conformément à la sous

clause 30 des IS. Toute tentative de la part d’un Soumissionnaire d’influencer l’examen des dossiers ou la

décision d’attribution du marché par AIR ALGERIE pourra entraîner l’exclusion de sa Soumission.

22.2 Si, après la notification de l’attribution du marché, un Soumissionnaire souhaite connaître les motifs

pour lesquels son offre n’a pas été retenue, il pourra en faire la demande par écrit à AIR ALGERIE à l’adresse

indiquée dans le DPAO (clause 31); ce dernier répondra rapidement par écrit. Seule l’offre du soumissionnaire

sera évoquée dans cette explication, à l’exclusion des offres concurrentes.

23. Éclaircissements concernant les offres

En vue de faciliter l'examen, l'évaluation et la comparaison des offres, AIR ALGERIE a toute latitude pour

demander au Soumissionnaire des éclaircissements sur son offre. La demande d'éclaircissements et la réponse

se feront par écrit, et aucun changement de prix ni aucun changement substantiel de l'offre, ne seront

demandés, offerts ou autorisés.

AOIR : N° 001/DC/2016 Page 9

24. Examen préliminaire et décision de conformité

24.1 Avant l'évaluation détaillée, AIR ALGERIE déterminera si chaque offre est conforme pour l'essentiel

aux dispositions du Dossier d'Appel d'Offres.

24.2 Une offre conforme pour l'essentiel est une offre conforme à tous les termes, conditions, et

spécifications, sans divergence ni réserve importante. Une divergence ou réserve importante est celle qui :

(i) affecte sensiblement l'étendue, la qualité ou le résultat des services ;

(ii) limite sensiblement, en contradiction avec le Dossier d'Appel d'offres, les droits d’AIR ALGERIE ou

les obligations du soumissionnaire au titre du Marché ; ou

(iii) est telle que sa rectification affecterait injustement la compétitivité des autres soumissionnaires

qui ont présenté des offres conformes pour l'essentiel au Dossier d'Appel d'Offres.

24.3 Si une soumission n'est pas conforme pour l'essentiel, elle sera rejetée par AIR ALGERIE, ne peut être

par la suite rendue conforme par la correction ou le retrait subséquent de la divergence ou réserve qui la

rendait non conforme.

25. Correction des erreurs

25.1 Les Soumissions jugées conformes pour l‘essentiel feront l’objet de vérifications par AIR ALGERIE

afin de détecter les erreurs de calcul. Les erreurs seront corrigées par AIR ALGERIE comme suit :

– lorsqu'il y a une différence entre les montants en chiffres et en lettres, le montant en lettres fera foi;

– lorsqu'il y a une incohérence entre le prix unitaire et le prix total obtenu en multipliant le prix

unitaire par la quantité, le prix unitaire cité fera foi, à moins qu’AIR ALGERIE estime qu'il s'agit d'une

erreur grossière de virgule dans le prix unitaire, auquel cas le prix total tel qu'il est présenté fera foi

et le prix unitaire sera corrigé.

25.2 Le montant figurant dans la Soumission sera corrigé par AIR ALGERIE, conformément à la procédure

susmentionnée pour la correction des erreurs et, avec l'accord du Soumissionnaire, ledit montant sera réputé

engager le Soumissionnaire. Si le Soumissionnaire n'accepte pas la correction ainsi effectuée, son offre sera

rejetée.

26. Conversion en une seule monnaie

Pour permettre l’évaluation et la comparaison des offres, AIR ALGERIE convertira les prix des offres exprimés

dans les diverses monnaies en Dinar Algérien (DZD), en utilisant le taux de change vendeur publié par la

Banque d’Algérie, le jour précédant la date d’ouverture des offres commerciales.

Les prix des offres des soumissionnaires devront correspondre à la somme de tous les montants, libellés en

diverses monnaies converties en Dinar Algérien.

27. Évaluation et comparaison des offres

27.1 Seules les Soumissions déclarées conformes pour l’essentiel seront examinées par AIR ALGERIE

conformément à la Clause 24 des IS.

27.2 Les offres reconnues conformes seront évaluées et analysées en deux phases sur la base des critères et

de leur poids respectif, et selon une méthodologie fixée dans le Dossier d’Appel d’Offres (section 2) :

AOIR : N° 001/DC/2016 Page 10

a) Première étape : Étape technique :

Les soumissionnaires dont les offres répondent aux critères de qualification et aux critères de conformité

technique contenus dans le Dossier d’Appels d’Offres, seront éligibles à l’évaluation des offres commerciales

au titre de la deuxième étape ;

Les soumissionnaires dont les offres ont été déclarées non conformes au titre de la première étape seront

informés, par écrit du rejet de leurs offres. AIR ALGERIE pourra demander au soumissionnaire dont l’offre

technique répond aux critères de qualification, des clarifications sur des aspects techniques de son offre.

b) Deuxième étape : Étape commerciale :

L’offre retenue sera l’offre la moins disante sur la base du prix seul, ou l’offre la mieux disante, tel que précisé

dans les DPAO.

La méthode appropriée pour l'évaluation est détaillée dans les Données particulières de l'Appel d'Offres et/ou

dans les Spécifications techniques.

F. ATTRIBUTION DU MARCHÉ

28. Critères d’attribution

AIR ALGERIE attribuera le Marché au Soumissionnaire ayant présenté une soumission conforme au Dossier

d’appel d’offres et évaluée l’offre la mieux disante pour AIR ALGERIE, à condition que ce soumissionnaire

remplisse les conditions de qualification pour exécuter le contrat.

29. Droit d’accepter ou de rejeter une ou toutes les offres

AIR ALGERIE se réserve le droit d'accepter ou d'écarter toute offre, et d'annuler la procédure d'Appel d'Offres

et de rejeter toutes les offres, à tout moment avant l'attribution du marché, sans, de ce fait, encourir une

responsabilité quelconque vis-à-vis du ou des soumissionnaires affectés, ni être tenu d'informer le ou les

soumissionnaires affectés des raisons de sa décision.

30. Notification de l’attribution du marché

Le Soumissionnaire dont la soumission a été acceptée sera notifié par écrit, par courrier électronique, par AIR

ALGERIE avant la date d’expiration de la validité de la soumission.

Aussi, ladite attribution provisoire doit être notifiée aux autres soumissionnaires, par courrier électronique.

31. Recours des concurrents

Tout concurrent qui conteste les résultats d’un appel d’offres, ou les motifs de l’élimination de son offre par la

commission, portés à sa connaissance par AIR ALGERIE , ou qui constate que l’une des règles de la procédure de

passation des marchés n’a pas été respectée, peut adresser une requête circonstanciée à AIR ALGERIE.

La réclamation du concurrent doit être introduite dans les dix (10) jours suivant la publication de l’avis

d’attribution provisoire du marché ou sa notification aux soumissionnaires ou la notification de l’avis de rejet

aux soumissionnaires éliminés.

AOIR : N° 001/DC/2016 Page 11

AIR ALGERIE fait connaitre au concurrent concerné la réponse réservée à sa réclamation dans un délai de vingt

et un (21) jours à compter de la date de réception de ladite réclamation.

Ne peuvent, toutefois, faire l’objet de contestation de la part des concurrents :

- le choix d’une procédure de passation de marché ou de sélection des candidats ;

- la décision d’AIR ALGERIE d’écarter la totalité des offres ou d’annuler l’appel d’offres conformément aux

dispositions de l’article 29 de l’IS.

32. Absence d’obligation

Rien dans la présente demande de proposition ne devrait être interprété comme signifiant que la compagnie

AIR ALGERIE a obligation d'acheter des fournisseurs l'un des produits ou services examinés. Toutes les

dépenses engagées par les fournisseurs liées à répondre à cet Appel d’Offre sont de la responsabilité des

fournisseurs. En acceptant d'examiner les différents fournisseurs et leurs produits, AIR ALGERIE n'a aucune

obligation de rembourser les frais supportés par le fournisseur. AIR ALGERIE se réserve le droit de rejeter toute

proposition.

33. Signature du contrat

Le contrat signé pour le vendeur doit être un mandataire social de la société ou un mandataire dûment

autorisé.

AOIR : N° 001/DC/2016 Page 12

SECTION 2: DONNÉES PARTICULIÈRES DE L’APPEL D’OFFRES (DPAO)

Les renseignements et les données qui suivent devront compléter, préciser ou modifier les clauses des

Instructions aux soumissionnaires (IS). En cas de divergence, les données particulières ci-dessous ont priorité

sur les clauses des IS.

A – DISPOSITIONS GÉNÉRALES

1

Nom et adresse d’AIR ALGERIE :

Air Algerie - Division Commerciale

29 Bd, Zirout Youcef 16000 ALGER

Email : pss.project@airalgerie.dz

Objet de l’appel d’offres :

Système de Gestion des Passagers Pour Compagnies Aériennes Régulières

Le présent appel d’offres s’adresse exclusivement aux fournisseurs ayant de

l’expérience dans la fourniture et l’implémentation de Système de Gestion des

Passagers avec des solutions annexes.

AIR ALGERIE souhaite acquérir une solution hébergée.

Les systèmes à fournir sont les suivants :

o Inventaire (Inventory),

o Réservation (Reservation and booking management)

o Billeterie électronique et EMD (Ticketing and EMD),

o Contrôle des départs (Departure control system),

o Tarification (Fare Quote),

o Gestion des recettes (Revenue Management),

o Fiabilisation des ventes (Revenue Integrity),

o E-Commerce,

o Gestion de fidélisation et expérience client (Loyalty Management et

Customer Experience),

o Intelligence économique (Business Intelligence),

o Gestion des irrégularités (Disruption Management).

Nom du projet et numéro de l’appel d’offres :

Nom : Système de Gestion des Passagers Pour Compagnies Aériennes Régulières

Numéro d’identification : “AOIR : N° 001/DC/2016”

AOIR : N° 001/DC/2016 Page 13

4

Soumissionnaires admis à concourir :

Fournisseurs de PSS, ayant déjà implémenté leurs solutions et disposant de trois (3) clients au

minimum (compagnies aériennes régulières).

5

Qualification du Soumissionnaire :

Le présent appel d’offres s’adresse aux candidats satisfaisant aux conditions suivantes :

- Le Soumissionnaire a la capacité financière et technique nécessaire pour

exécuter le marché ;

- Le Soumissionnaire doit avoir l’expérience dans la migration des systèmes PSS;

- Le soumissionnaire doit fournir, comme partie intégrante de son offre, des

documents prouvant ses qualifications à exécuter le contrat en cas

d'attribution.

Profil de l’entreprise :

Le soumissionnaire fournira les informations générales sur son entreprise indiquant sa

vision et stratégie concernant les produits et services à offrir :

- Nombre d’employés ;

- Nombre et endroits des bureaux (localisation géographique)

- Vue d’ensemble financière (doit inclure des bilans annuels et chiffres

d’affaires) ;

- Nombre de clients actuels utilisant les solutions proposées ;

- Références ;

- Investissements dans la recherche et développement.

5

Documents établissant la conformité au DAO:

Le Soumissionnaire fournira, en tant que partie intégrante de son offre, des documents

établissant que le PSS qu’il se propose de fournir et d’implémenter dans le cadre du Marché

est conforme au Dossier d’Appel d’Offres notamment dans sa Section 3.

Les documents apportant la preuve que son offre est conforme au Dossier d’Appel d’Offres

revêtiront la forme de descriptions écrites, prospectus, certificats et références de clients, y

compris :

a. L’offre technique du Soumissionnaire, c’est-à-dire une description détaillée de la solution

technique préconisée par le Soumissionnaire conforme en tous points aux spécifications

techniques et fonctionnelles ;

b. Le tableau des spécifications techniques dûment remplis tel que spécifié dans la section 3 ;

c. Un Plan de projet préliminaire devra inclure un calendrier détaillé de l’activité, ainsi que les

ressources humaines qu’il se propose d’utiliser. Il devra en outre spécifier ce que le

Soumissionnaire attend d’AIR ALGERIE et toute autre partie concernée par la mise en

œuvre de l’implémentation du PSS, et la façon dont le Soumissionnaire se propose de

coordonner l’action de toutes les parties concernées.

AOIR : N° 001/DC/2016 Page 14

9

Éclaircissements au Dossier d’Appel d’Offres :

Les soumissionnaires peuvent demander à AIR ALGERIE, par voie électronique des

éclaircissements concernant le dossier de l’Appel d’Offres à l’adresse et email ci-après :

pss.project@airalgerie.dz

AIR ALGERIE répondra par écrit à toute demande d’éclaircissement à condition que la

demande soit reçue vingt et un (21) jours avant la date limite de dépôt des offres.

Les réponses à ces demandes se feront par e-mail et seront adressées à tous les

soumissionnaires, sans que l’identité de l’auteur de la demande de clarification ne soit

mentionnée ou divulguée.

C – PRÉPARATION DES OFFRES

11

Langue de l’offre :

L'offre ainsi que toutes les correspondances et tous les documents concernant la

soumission échangée entre le Soumissionnaire et AIR ALGERIE, doivent être rédigés en

langue anglaise.

12

Documents constitutifs de l’offre :

L’offre technique :

- Le présent cahier des charges, chaque page paraphé et signée ;

- La déclaration sur l’honneur renseignée et dûment signée (Section 4);

- La délégation de pouvoirs habilitant le ou les signataire(s) de l’offre à engager le

soumissionnaire ;

- Un engagement écrit indiquant qu'au moins trois (03) compagnies aériennes

régulières utilisent actuellement le PSS du soumissionnaire ;

- Copie du registre de commerce ainsi que le statut de l’entreprise ;

- Qualifications et expérience du personnel technique et d’encadrement désigné

pour exécuter le marché ;

- Documents relatifs à la situation financière du soumissionnaire, notamment le

bilan financier des trois dernières années dûment certifiés par un commissaire

aux comptes ;

- Documents apportant la preuve que les solutions proposées sont conformes aux

spécifications (support numérique, prospectus résumant les caractéristiques des

solutions) ;

- Tableau des spécifications techniques dûment remplis tel que spécifié dans la

section 3 ;

- Liste de l'ensemble des compagnies clientes utilisatrice du PSS démontrant les

Références professionnelles du soumissionaire (en précisant les solutions

utilisées);

- Tableau des migrations réalisées ou programmées" tel que spécifié dans la

AOIR : N° 001/DC/2016 Page 15

section 3 point 4 « Autres exigences »;

- Trois (03) lettres de références de clients ayant migré vers le PSS du

soumissionnaire incluant le nom de la compagnie ainsi que le contact ;

- Liste des aéroports desservis par Air Algérie et où le DCS proposé est exploité par

des compagnies aériennes et/ou Ground Handler, à préciser.

- Le planning de migration et d’implémentation, tel que spécifié dans la section 3

Point 4 « Autres exigences ».

L’offre commerciale:

- Letter de soumission dûment renseignée et signée (section 4) ;

- Bordereau des prix signé et rempli en fonction de l’offre (section 4);

- Projet de contrat en anglais et en français ;

- Projet du Service Level Agreement (SLA).

13 Variantes:

Les variantes ne seront pas prises en considération.

13

Montant de l’offre:

Les fournisseurs sont tenus de préciser la totalité des frais :

- Implementation ;

- Usage, support et maintenance par Passager Embarqué (Passenger Boarded)

pour une période de (05) ans au minimum, selon le trafic annuel :

Moins de 4 millions

Entre 4 et 6 millions

Entre 6 and 8 millions

Plus de 8 millions

Tous les autres coûts doivent être pris en charge par le fournisseur. Le règlement des

prestations sera effectué après l’exécution du marché.

Impôts et taxes :

Le soumissionnaire retenu doit s’acquitter de toutes ses obligations fiscales selon la

réglementation en vigueur.

14 Monnaie de l’offre :

Les prix seront libellés en USD.

15 Délai de validité des offres :

La période de validité des offres est de cent quatre-vingt (180) jours, après la date limite de

dépôt des offres.

AOIR : N° 001/DC/2016 Page 16

16

Nombre de copies :

L'offre du soumissionnaire doit comprendre :

- Une (01) originale

- Deux (02) copies (support papier)

- Une (01) copie format numérique.

D – REMISE DES OFFRES

18

Date et heure limite pour le dépôt des offres :

Les Soumissionnaires sont invités à déposer leurs Offres le 11 Juillet 2016 avant 13 heures,

heure locale.

Dépôt des offres :

AIR ALGERIE – Division Commerciale

Secritariat Division Commerciale Etage : 5

29 Bd, Zirout Youcef 16000 ALGER, Algérie

Nom et numéro de l’appel d’offres:

Nom : Appel d’Offres International Restreint

« Système de Gestion des Passagers Pour Compagnies Aériennes Régulières »

Numéro d’identification : « AOIR : N° 001/DC/2016 »

Mention :

L’avertissement suivant doit figurer sur l’enveloppe : « NE PAS OUVRIR AVANT LA DATE

D’OUVERTURE DES PLIS »

E –OUVERTURE DES PLIS ET EVALUATION DES OFFRES

21

Date, heure et adresse pour l'ouverture des plis :

La séance d’ouverture des plis aura lieu le 11 Juillet 2016, à 14H00 à l’adresse suivante :

AIR ALGERIE

Division Commerciale,

Secritariat Division Commerciale

29 BD, Zighout Youcef 16000 ALGER

AIR ALGERIE examinera les offres pour déterminer si elles sont complètes, si le

soumissionnaire répond aux conditions d'éligibilité, si les documents ont été correctement

signés, et si les offres sont d'une façon générale en bon ordre.

Avant l’évaluation détaillée, AIR ALGERIE déterminera si chaque offre est de qualité

acceptable, complète, et conforme pour l’essentiel aux dispositions du Dossier d’Appel

d’Offres. Aux fins de cette détermination, une offre conforme pour l’essentiel est une offre

AOIR : N° 001/DC/2016 Page 17

conforme à toutes les stipulations, spécifications et conditions du Dossier d’Appel d’offres,

sans divergences, exceptions, objections, conditions ou réserves notables.

Les offres non conformes seront rejetées par AIR ALGERIE et ne pourront faire ultérieurement

l’objet de modifications visant à en rectifier la non-conformité. AIR ALGERIE déterminera si une

offre est conforme en se fondant sur le contenu de l’offre proprement dite.

27

Évaluation et comparaison des offres :

AIR ALGERIE procédera à l'évaluation et à la comparaison des offres dont elle aura

déterminé au préalable qu'elles répondent pour l'essentiel aux dispositions du Dossier

d’Appel d’Offres.

Les offres reconnues conformes au DAO, seront évaluées et analysées par la commission

d’évaluation. Cette évaluation se fera en deux (02) phases selon la méthodologie suivante :

- Première phase, Évaluation de l’offre technique : 70 points maximum

- Deuxième phase, Évaluation de l’offre commerciale : 30 points maximum

- Première phase : Évaluation de l’offre technique

Les soumissionnaires dont les offres répondent aux critères de qualification (références,

capacité, situation financière, etc.) et aux critères de conformité technique contenus dans le

Dossier d’Appel d’Offre, seront éligibles à l’évaluation des offres commerciales au titre de la

deuxième étape.

AIR ALGERIE pourra demander au soumissionnaire dont l’offre technique répond aux

critères de qualification, des clarifications sur des aspects techniques de son offre.

L’évaluation technique sera basée sur quatre critères à savoir :

- Les Références professionnelles (05 points) ;

- L’expérience dans la Migration (10 points) ;

- La Communalité & l’Intégration (20 points) ;

- Les Fonctionnalités techniques (35 points).

Seules les offres techniques ayant obtenu un total de 50 points et plus seront retenues

pour l’évaluation des offres commerciales correspondantes.

Les soumissionnaires dont les offres ont été déclarées non conformes au titre de la

première étape seront informés, par écrit du rejet de leurs offres.

-Deuxième phase : Évaluation de l’offre commerciale

L'évaluation d'une offre par AIR ALGERIE se fera sur la base du prix de l'offre.

La note maximale (30 points) est attribuée à l’offre Commerciale (financière) la moins

disante.

AOIR : N° 001/DC/2016 Page 18

Les points attribués pour les autres offres seront calculés comme suit :

N = 30 X Mm / Mc

N = Note financière de l’offre considérée

Mm = Montant de l’offre la moins disante.

Mc = Montant de l’offre commerciale considérée.

L’offre la mieux disante sera celle qui occupera le 1er rang au classement final, classement

opéré sur la somme des notes techniques et commerciales (financières) obtenues par

chaque soumissionnaire.

Dans le cas ou plusieurs offres seraient classées au premier rang (même nombre de points

obtenus), le choix portera sur l’offre Commerciale la moins disante.

F – VÉRIFICATION A POSTERIORI ET ATTRIBUTION DU MARCHE

28

Vérification à posteriori

AIR ALGERIE se réserve le droit de s’assurer que le Soumissionnaire, ayant remis l’offre

conforme évaluée la mieux disante pour AIR ALGERIE, a les qualifications voulues pour

exécuter le Marché de façon satisfaisante, conformément aux dispositions du Dossier

d’Appel d’Offres.

Dans ce cadre, AIR ALGERIE procèdera, lors de la vérification à posteriori, à des tests pour

s’assurer que les Systèmes proposés répondent aux critères de performance ou de

fonctionnalités définis dans les Spécifications techniques.

Le Soumissionnaire ayant remis l’offre conforme évaluée la mieux disante pour AIR ALGERIE

ne se verra attribuer le Marché que si la vérification à posteriori se conclut de manière

positive. Dans la négative, son offre sera rejetée et AIR ALGERIE examinera la deuxième offre

évaluée la mieux disante, pour s’assurer de la même façon de la capacité du Soumissionnaire

à exécuter le marché de manière satisfaisante.

31

Recours des concurrents :

Tout concurrent qui conteste les résultats d’un appel d’offres, ou les motifs de l’élimination

de son offre par la commission, ou qui constate que l’une des règles de la procédure de

passation des marchés n’a pas été respectée, peut adresser une requête circonstanciée,

dans les dix (10) jours suivant la notification provisoire, à l’adresse :

AIR ALGERIE – COMMISSION DES MARCHÉS –

01 Place Maurice Audin, Alger- Algérie.

AOIR : N° 001/DC/2016 Page 19

AOIR : N° 001/DC/2016 Page 20

SECTION 3 : EXIGENCES TECHNIQUES

1. INTRODUCTION

AIR ALGERIE est le transporteur national de l'Algérie qui fournit un service de transport aérien

(passengers et fret) sur le réseau international et domestique.

La situation actuelle de la compagnie est décrite ci-dessous.

2. PRÉSENTATION D’AIR ALGERIE

2. 1. Informations Compagnie

Airline Name: AIR ALGERIE

IATA Airline Code: AH

IATA Accounting Code: 124

Headquarters City: ALGIERS, 01 Place Maurice Audin.

Years in operation: Depuis 1947

Ownership structure: ALGERIAN GOVERNMENT

2. 2. Faits et Chiffres

Aircraft Fleet

08/A330

03/B767

22/B737-800 (4 will be delivered in 2016)

5/B737-600

15/ ATR

Daily Flights (scheduled) 167 (Average)

Destinations Served

32 domestic stations

40 international stations (Europe, Africa, China,

Middle East, Canada)

Passengers Boarded

2012 = 4 137 266 PB

2013 = 4 547 893 PB

2014 = 5 082 508 PB

2. 3. Éstimation du traffic Passagers

2015 2016 2017 2018 2019 2020 2021

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

AOIR : N° 001/DC/2016 Page 21

2. 4. Les systèmes actuels utilisés par AIR ALGERIE

System Product Name / Vendor

Reservations/ Inventory/ Ticketing MARS / MERCATOR

Distribution Program OAG - INNOVATA (manually not SSIM)

Revenue Management System NOT AVAILABLE

Revenue Accounting System RAPID / MERCATOR

CRM/Loyalty system CRIS / MERCATOR

Schedule Management System AIMS

Flight Operations System AIMS

Internet Booking Engine IBE/MERCATOR

Revenue Integrity / Flight Firming CALIDRIS / MERCATOR

Data Warehouse In-house

Payment Service Provider(s) OGONE (international cards)

SATIM (national cards) Filing Fares ATPCO

Fares Quote WORLDSPAN

Electronic Ticket Server ETS / MERCATOR

Departure Control System MACS /MERCATOR

Call Centre System/CRM Hermes NET/VOCALCOM

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

2. 5. Partenaires interligne actuels

Airlines Airlines Code

AIR BURKINA 2J

AFRIQYAH 8U

AIR France AF

ROYAL AIR MAROC AT

ALITALIA AZ

BRITISH AIRWAYS BA

CATHAY PACIFIC CX

DEUTSH BAHN DB

DELTA AIRLINES DL

EMIRATES EK

ETHIOPIAN AIRLINES ET

ETIHAD AIRWAYS EY

GARUDA INDONESIA GA

GULF AIR GF

HAHN AIR HR

HAINAN AIR HU

IBERIA IB

YEMENIA AIRWAYS IY

JAPAN AIRLINES JL

KOREAN AIRLINES KE

AOIR : N° 001/DC/2016 Page 22

Airlines Airlines Code

AIR MALTA KM

KENYA AIWAYS KQ

KUWAIT AIRWAYS KU

MAURITANIA AIRLINES L6

EQUATORIAL CONGO AIRLINES - ECAIR LC

LUXAIR LG

LUFTHANSA LH

AIR LIBAN ME

MALYSIA AIRLINES MH

EGYPT AIR MS

ALL NIPPON NH

ASIANA AIRLINES OZ

QATAR AIRWAYS QR

SYRIAN ARAB AIRLINES RB

ROYAL JORDANIAN RJ

BRUSSELS AIRLINES SN

SINGAPORE AIRLINES SQ

AEROFLOT SU

SAUDIA AIRLINES SV

TURKISH AIRLINES TK

TAP Portugal TP

TUNISAIR TU

UNITED AIRLINES UA

VIETNAM AIRLINES VN

2. 6. IET en cours

AIR CANADA AC

TASSILI AIRLINES SF

RWANDAIR WB

2. 7. Partenaires Code share

Airline Agreement type (Block Space / Free-flow)

TURKISH AIRLINES -TK - Free-Flow

AOIR : N° 001/DC/2016 Page 23

2. 8. Modèle Commercial

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. Ventes indirectes via GDS pour AIR ALGERIE

Name

1 Abacus

2 Amadeus

3 Axess

4 Sabre

5 Travelport (Galileo/Apollo)

6 Travelsky

2. 10. Émission EMD

Services Category Status

18 services Standalone & Associated Deployed at ATO /CTO

04 services Standalone Deployed at Amadeus Travel Agencies in 25 BSP

05 services Standalone Deployed at Amadeus Travel Agencies in Algeria Market

04 services Standalone Implementing at Travelport

04 services Standalone To be implemented at Sabre

2. 11. Situation actuelle de l’E-commerce

IBE Features Description

IBE Languages FR/EN

Search Schedule/Price/Flexible search (calendar fares)

Payment

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

- SATIM : Local payments (DZD)

- Book & Hold (Collection at ATO/CTO)

AOIR : N° 001/DC/2016 Page 24

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

- Online check-in

Frequent flyer Program - Redemption

- Upgrade

Promotional offers Discount codes

IBE Numbers (2015) Estimation

Sessions/month 620 000

Single Visits/month 316 000

Daily sessions/hour 1 700

Annual growth (single visits) 20%

Historical Peak (2014)

Single visits/hour 8 000

Single visits/day 54 000

2. 12. DCS aux escales internationales

STATION AIRPORT

CODE

DCS SUPPLIER CUTE GROUND HANDLER

Abidjan ABJ DC ALTEA AMADEUS SITA CUTE NAS

Alicante ALC RESIBER IBERIA SITA CUTE IBERIA

Amman AMM MACS MERCATOR SITA CUTE ROYAL JORDANIAN

Bamako BKO DC ALTEA AMADEUS RESA CREWS ASAM S.A

Barcelona BCN RESIBER IBERIA SITA CUTE IBERIA

Berlin SXF EDS EDS SITA CUTE ACCIONA

Beirut BEY DCS SITA SITA SITA CUTE LAT

Bordeaux BOD MACS MERCATOR RESA CREWS Aviapartner

Brussels BRU EDS EDS ARINC MUSE Swissport

Cairo CAI DC ALTEA AMADEUS SITA CUTE Egypt Air

Casablanca CMN MACS MERCATOR SITA CUTE Royal Air Maroc

Charles De Gaulle CDG MACS MERCATOR RESA CREWS Alyzia

AOIR : N° 001/DC/2016 Page 25

STATION AIRPORT

CODE

DCS SUPPLIER CUTE GROUND HANDLER

Dakar DKR DC ALTEA AMADEUS RESA CREWS SHS

Damascus DAM SITA DCS SITA SITA CUTE Syrian Air

Dubai DXB MACS MERCATOR SITA CUTE Dnata

Frankfurt FRA MACS MERCATOR SITA CUTE ACCIONA

Geneva GVA EDS EDS SITA CUTE Swissport

Istanbul IST EDS EDS SITA CUTE HAVAS

Jeddah JED MACS MERCATOR SITA CUTE S G S

Lille LIL MACS MERCATOR RESA CREWS Aviapartner

London LHR MACS MERCATOR ARINC MUSE Swissport (Ex Servisair)

Lyon LYS MACS MERCATOR RESA CREWS Aviapartner

Lisbon LIS DC ALTEA AMADEUS SITA CUTE Groundforce

Medina MED MACS MERCATOR SITA CUTE S G S

Madrid MAD RESIBER IBERIA SITA CUTE IBERIA

Marseille MRS MACS MERCATOR RESA CREWS Aviapartner

Metz ETZ DC ALTEA AMADEUS RESA CREWS EMNPL

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

Montreal YUL MACS MERCATOR ARINC MUSE Swissport (Ex Servisair)

Moscow SVO SABRE DCS SABRE SITA CUTE Shremetyevo Airport

Mulhouse MLH SITA DCS SITA RESA CREWS Swissport

Nantes NTE LCA UNISYS RESA CREWS Aviapartner

Niamey NIM DC ALTEA AMADEUS RESA CREWS Regie Assistance

Nice NCE MACS MERCATOR RESA CREWS Aviapartner

Nouakchott NKC DC ALTEA AMADEUS RESA CREWS Mauritania Airlines

Orly ORY MACS MERCATOR RESA CREWS Alyzia

Ouagadougou OUA DC ALTEA AMADEUS RESA CREWS RACGAE

Beijing PEK MACS MERCATOR SITA CUTE B. G. S

Rome FCO ARCO ALITALIA SITA CUTE Aviapartner ( Ex

Flightcare)

AOIR : N° 001/DC/2016 Page 26

STATION AIRPORT

CODE

DCS SUPPLIER CUTE GROUND HANDLER

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 émis

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. Compagnies assistées par 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 27

2. 15. Équipements DCS en Algérie

TYPE MANUFACTURER MODEL

BOARDING PASS PRINTER INTERMEC

IER

PF 4i

IER400

GATE READER IER IER600

PASSPORT READER DESKO MPR 7200

BAG TAG PRINTER INTERMEC

IER

PF 2i

IER400/IER506

SCANNERS INTERMEC SR30

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

OS MICROSOFT WINDOWS 7

2. 16. Quelques chiffres

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. Infrastructure ATO/CTO

PC Printer Network

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

Win7 pro/ Win 8 pro 32/64 bits

Average 4 PCs per agency

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

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

2. 18. Infrastructure réseau d’AIR ALGERIE

Voir schéma ci-après :

Internet

Users with ADSL Connection

SITA

International Network

Datacenter AH Algiers Kouba

LS

64/512

Kbps LS 64/512 Kbps

Domestic AH CTO/ATO and Airports

International AH CTO/ATO and Airports

Algiers Airport Terminal 1 and 3

LS

256 Kbps

Datacenter MERCATOR Dubaï

2 x LS 1

Mbps

SITA Algiers

AIR ALGERIE Infrastructure Network

AOIR : N° 001/DC/2016 Page 29

3. EXIGENCES FONCTIONNELLES

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. Exigences générales du PSS

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

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

1

Access. Access to all systems and/or their

functionalities must be controlled by session

characteristics and by agent authorization. It shall

be possible to define a group of users with limited

set of functions to be defined by AIR ALGERIE.

2 Access. Ability to access system via internet/Web

(secure access) and leased lines.

3

GUI. Graphical User Interface must be available

for direct user entries for all modules. Native

mode is required.

4 GUI. All native entries must be supported on the

GUI.

5 Modes. Training, Test/acceptance and production

modes are required.

6

Access management. Ability to manage users

profiles and privileges:

- Creation,

- Amendment,

- Suspension,

- Cancellation.

7 Online Help. Ability to provide help information

and user guides.

8 Session. Ability to auto sign-out after a defined

period of inactivity (to be specified).

AOIR : N° 001/DC/2016 Page 30

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

9

Log. History logging for all modules must be

available (who, when and what change were

made).

10

Security. The provider must guarantee :

- Security, confidentiality and integrity of data,

- High Availability,

- Disaster Recovery.

11

Integration. All PSS modules must be fully

integrated (reservation/ticketing, inventory, DCS,

IBE, RI…)

12

Integration. Ability to provide integration

capabilities (APIs, Web Services, Middleware, etc.)

to facilitate integration with third party systems.

13 Connectivity. Ability to support connectivity with

all GDS, Interline and Codeshare partners.

14 Payment. Payment solution must be PCI-DSS

compliant.

15

Payment. Ability to accept :

- International and local forms of payment

(Credit/debit cards, e-wallets,

settlements…),

- Payment on all channels (ATO/CTO, WEB,

Mobile, Call Centre…).

16 Payment. Ability to provide PSP integration

(WorldPay, wirecard…).

17 Payment. Ability to support Fraud prevention and

chargeback controls.

18 Payment. Ability to provide Security checks (CVV,

3D Secure…).

19 Payment. Ability to support Dynamic currency

conversion.

20

Data warehouse. Ability to extract automatically

and manually all data (E.g. PNR data, Schedules

data, Inventory data, DCS data…).

AOIR : N° 001/DC/2016 Page 31

3. 2. Système d’Inventaire (Inventory)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

Schedule Management

1

IATA standard. Incoming and outgoing IATA standard

schedule messages (SSIM/ ASM / SSM) must be automatically

processed.

2

Schedule. Ability to add new schedule (manually and/or

automatically), to change existing schedule or modify online

into the inventory.

3

Schedule. Creation, modification activities must be restricted

only to specific agents based on AIR ALGERIE business rules

requirement.

4 OAG/INNOVATA update. The supplier must indicate the

update frequency.

5

Schedule. Ability to create the schedule in the inventory

including (not limited to):

- Flight number,

- Effective and discontinue dates,

- Departure and arrival time,

- Frequency,

- Route pair,

- Aircraft Type,

- Terminal.

6

Schedule Integrity. Ability to perform automated check during

schedule creation/modification (e.g. Arrival date is less than

Departure date).

7 Schedule messages. Incoming schedule messages that cannot

be automatically processed must be manually reviewed.

8

Schedule messages from Other Airlines (OAL), Interline

Partners, Codeshare Partners, Airline IT providers must be

accepted.

9

Schedule messages. Ability to send ASM/SSM recap

(automatically and/or manually) to other systems (OAG,

INNOVATA…).

10

Traffic Restrictions. All IATA standard traffic restrictions via

SSIM/SSM/ASM to notify OAL/GDS/OAG/INNOVATA are

supported.

AOIR : N° 001/DC/2016 Page 32

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

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

Charters flights.

12 Shared Schedule Database. Ability to provide a single shared

schedules database with DCS and reservation system.

13 MCT file from OAG or INNOVATA must be loaded.

14

Schedule change. Ability to rebook automatically Seat Maps,

Seat Assignments and Special Service Requests (SSR), in case

of schedule change.

PNRs containing failed seats or SSRs must be queue placed.

15 Schedule change. Automatic/manual passenger re-

accommodation is required in case of schedule change.

16

Codeshare schedule change. Ability to re-accommodate

automatically the passengers in case of codeshare schedule

change.

17

Restriction codes. Ability to display restricted segments in

passenger application according to the SSIM manual (e.g.

APPENDIX G).

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

modules.

19 Creation flights. Automatic flight creation must be at least 360

days (system period).

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

supported.

21

AVS/NAVS. Ability to control the sending and receiving of

AVS/NAVS messages, based on AIR ALGERIE specific rules (first

closing, segment availability…).

22 AVS agreements. Ability to display AVS agreements.

23

Seat configuration. Ability to proceed to an automatic

configuration of the seat map on the DCS after schedule

amendment in the inventory.

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

supported.

25 Meal. Ability to support all IATA meal service codes and

Inflight Service (IFS) codes in SSIM/SSM/ASM.

AOIR : N° 001/DC/2016 Page 33

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

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

level.

Inventory Management

27

Minimum Connection Time Table. City pairs must have a user

updateable table, which establishes the minimum/maximum

connection times between flights. Connections must be

configurable by carrier code, flight number and class with the

ability to give preference to Codeshare partners. The

minimum connection table should also be able to cater for

multiple airports within a city code.

28

Ability to display a minimum of 26 classes. Normal availability

displays should be restricted to x classes (x being a system

parameter).

29 City pair comment. Ability to show a city pair comment over

and above flight details on an availability display.

30 Flight Schedule information. Ability to retrieve Flight Schedule

information up to 3 days post-departure.

31 Number of seats. Display IATA standardized number of seats

available in each inventory (OAL, codeshare partners …).

32

Seat map. Ability to build or delete a seat map based on a

variety of technical, business and legal requirements.

Must include the ability to assign specific characteristics to

seats/rows and provide seat history.

33 Advance seat selection. Ability to manage advanced seat

selection and seat map retrieval.

34

Block and restrict seat assignment. Ability to block individual

seats from Advanced Seat selection or to restrict the number

of seats available for Advanced Seat selection by segment

and/or class.

35

Group Seating. Ability to assign group seat block, to display

group seat map and to allocate seats to individual names from

the group block.

36

Cancel Unassigned Seats. Ability to cancel unassigned seats

reserved in a group PNR transaction, to remove seats initially

reserved for a group.

37 Nesting. Automatic and manual Inventory nesting is required

(hybrid, serial and parallel nesting structures).

AOIR : N° 001/DC/2016 Page 34

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

38

Inventory Display. Include but not limited to:

- By Leg,

- By segment,

- Capacity and Subclass authorizations,

- Seats Sold,

- Waitlist and Staff counts,

- Overbooking %,

- Availability Status,

- Nesting.

39 Inventory History. Ability to display real-time history of all

changes within inventory by user, city, time, date …

40

Emergency Lock. Ability to place an emergency lock on a

flight’s inventory and PNRs. Emergency locked inventories and

PNRs are only accessible by control agents.

41

Flight Readouts. Ability to show out leg information for a

flight by compartment which should contain the departure

airport code, availability status, seats available or overbooked,

and aircraft capacity, plus various indicator such as capacity,

Block by class, capacity booked and forecasted by class,

Available loads by class, Waiting list, Group, request, Single

Date, Date range.

42

Waitlist. Ability to provide waitlist management process

including but not limited to:

- Automatic and manual creation/ clearance,

- Automatic prioritization processing,

- Sales Restriction on the waitlist by : POS, Market, flight

range, specific classes ...

43 IATA Codeshare. The system must support all IATA Codeshare

Options.

44

Codeshare configuration and management. Ability to provide

parameter driven codeshare set-up, to facilitate easy addition

and modification of codeshare agreements.

45 Shared Common Inventory. Ability to share an inventory with

a codeshare partner(s).

46 Codeshare Flight number Allocation. System must provide for

codeshare flight number allocation.

47 Passenger servicing by operating codeshare partner via the

codeshare PNR.

AOIR : N° 001/DC/2016 Page 35

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

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

49 PFS. Ability to process PFS messages by both compartment

and RBD.

50

Post Departure Processing. Post departure processing should

automatically update the inventory and passenger

information reflecting the actual boarding statistics for a

flight.

51 Group booking. Ability to handle any changes to group

bookings as per AIRIMP standards.

52 POS. Point of sales management is required.

53 Arrival or departure day. Ability to handle flight arrival or

departure up to +2 or -1 days.

54

Limitations. Ability to allow the following limitations on the

flight:

- Number of infants according to aircraft type,

- Number of WCHx, Number of UM.

55 Archive PNR. Ability to load historical PNR data and

passengers list (archive).

3. 3. Système de Réservation (Reservation and Booking management)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

Reservation and Booking management

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

codes.

2 Availability display. Ability to display only available RBDs

(inhibit closed RBD display).

3

Availability display. For each flight, the display must include:

airline code and flight number, departure date, segment

board/off cities, departure and arrival times (including next

day arrival indicator), day of week, seats available by class of

service, equipment, meal service, number of stops, elapsed

time, mileage and e-ticket eligibility.

Codeshare and alliance partners should be clearly indicated

and in the case of codeshare, the operating/marketing carrier

must be clearly shown.

AOIR : N° 001/DC/2016 Page 36

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

4

Availability display. Availability capability must include, but

not limited to the following:

- By specific carrier(s), by Class, by Best price,

- by direct and single stop flights, via specific route

(connecting flights),

- By departure or arrival time,

- Advance and go back by number of days,

- Reverse availability with change of date.

5

Availability display. Should display a minimum of 8 flights per

page. For the purposes of this requirement, connecting flights

are included in the requirement. Therefore, a flight from A to

B, connecting with a flight from B to C, would be counted as

two flights. Availability displays must be page-able both

forwards and backwards.

6 First Availability. Ability to display first availability by city pair,

class, start date…

7

Direct Sell. Ability to sell flight direct without reference to

availability display. Sell a flight by using flight number, date,

O&D without any reference to an availability display is

required.

8

Sell from availability. The ability to sell segments from an

Availability Display by selecting the routing number and class

only. If the routing number includes connecting flights they

will also be sold by this single sell entry (different classes).

9 Sell Open Dated Segment. Ability to sell “open” or non-

booked (ARNK) segments.

10

Booking Non-revenue Segments. Ability to book Non-Revenue

segments and have the possibility to be clearly identified in

PNRs.

11

Contact Fields. Ability to :

- Parameter contact field as mandatory,

- Cancel or change Contact fields elements in the PNR

(e.g. Business Phone, Private Phone, Mobile Phone, Fax,

Street Address and E-Mail address etc.),

- Attribute contact fields by passenger name in the PNR.

12 Class Upgrade/Downgrade. Ability to change the RBD of a

segment(s) to another RBD.

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

AOIR : N° 001/DC/2016 Page 37

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

segments order in PNR.

14

Retrieve PNR by name/flight/date. Ability to retrieve PNR by

passenger name, any active flight segment & associated date.

If the system cannot make an exact match a multi-selection list

of possible passengers will be displayed.

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

unique Host Record Locator.

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

Record locator.

17 Retrieve PNR from name list. Ability to display a list of

passengers, then select and display a PNR.

18

PNR validation closure. Ability to check/alert for:

- Duplicate segment,

- Minimum connecting time,

- Geographic and temporal continuity Itinerary.

19 PNR Closure. Ability to inhibit PNR closure if mandatory fields

are not completed.

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

21

SSR/OSI element. Ability to input an SSR/OSI element into the

PNR as per IATA standards, (SSR FOID for E-Ticketing, APIS,

special meals...).

22

SSR/OSI Queuing. Ability to queue SSR/OSI elements

(immediately or deferred, depending on the departure date)

to appropriate locations.

23

Auto SSR Processing by Airport, Airline, or Others. SSRs must

generate messages or lists to the appropriate entity

automatically.

24

Auxiliary Service Element. Ability to support auxiliary service

elements that may be requested by a passenger: car rental,

hotel accommodation, surface transportation and tour…

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

26 Inhibit Name Change. The System must inhibit modifications

to name changes, based on specific rules.

AOIR : N° 001/DC/2016 Page 38

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

27 Cancel/Re-book. Ability to cancel some or all segments in a

PNR element and re-book them for an alternative date.

28 Display PNR data. Ability to display Normal, Complete &

Historical PNRs and PNRs non-active.

29

PNR display. Ability to display the same PNR on all GDS as

displayed on AIR ALGERIE’s system in term of creation, change

and cancellation, and Vvs.

30

Display passengers. Ability to Display passengers with (not

limited to):

- Holding inbound connections to the flight,

- Seats selection,

- Special meals,

- Last booked passengers based on order,

- Any AUX, SSR, or OSI element,

- Holding outbound connections from this flight,

- No-show and go-shows lists,

- Ticketed passengers. Only entirely ticketed passengers are

selected,

- Electronic tickets or are marked to have electronic tickets

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

- Unconfirmed passengers (HL, US, UU, HN),

- A cancelled status on the requested segment (HX, UC, UN,

NO, XX, XL),

- Display Space-available passengers (NR),

- Only codeshare passengers regardless of their status,

- Passport Information,

- Unaccompanied Minors (UM),

- Infants and children (INF and CHD).

- Gender.

31 Display OAL availability. Ability to display OAL availability.

32 OAL Booking. Ability to book OAL segments.

33 Status confirmed PNR. Booked passengers with confirmed

reservations must have the following status HK, KK, and KL.

34

PNR Updates. Ability to update PNRs after flight finalization

(via direct PNR updates or automated PFS message

processing), e.g. identification of no-shows, modification of

goshows and subsequent action to those PNRs.

35 Divide or split a PNR. Ability to separate passengers from a

PNR, the original and new PNRs must be cross-referenced.

AOIR : N° 001/DC/2016 Page 39

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

36

Retain SSRs for divided PNRs. Ability to retain any common

information SSRs, contacts etc. when PNRs are split. Any

information specific to passenger is retained or transferred to

the appropriate PNR, which contains that passenger.

37

Queuing History of PNR. Ability to determine/view which

specific queues a PNR has been sent to and what action has

been taken at each point.

38 Active PNR. PNRs should be active in the system no less than

two days after the departure date of the last segment.

39 PNR archive. PNR archiving and options for the retrieval of

archived PNR for up to 10 years.

40 Public/Private Remark. Ability to introduce a public/Private

remark element (free format element).

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

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

travel agencies through GDS.

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

passengers in a group PNR.

44

Frequent flyer number. Ability to introduce frequent flyer

details in the PNR. It should be possible to cancel or change

these details.

45 Customer profile. Ability to retrieve and display complete

customer profile.

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

47 Enroll customer. Ability to enroll customer in FFP from

reservation system.

48

Miscellaneous support functions. Ability to provide:

- Encode-Decode,

- World city time / Airport information / Other information,

- Timatic, - Help,

- Information Display System (IDS).

49 Codeshare PNR. Ability to create, display and manage

seamless codeshare PNRs.

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

eligibility for E-Ticketing.

AOIR : N° 001/DC/2016 Page 40

3. 4. Système de Billeterie électronique et EMD (Ticketing and EMD)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

Ticketing Management

1

Compliance with Industry Standards.

Compliance with all Industry standards is required including

but not limited to:

1) Request/push control of ETR coupons between IET

carriers.

2) Current IATA EDIFACT/PADIS messaging standard in

order to exchange e-Ticketing data between airline

carriers,

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

handling,

4) Support for conjunctive e-Tickets with the industry

standard of sixteen coupons,

5) Support of the most recent CRS/GDS/EDIFACT version

for the exchange of ticket data from the GDS to the

validating carrier for both e-Tickets.

2 System Controls. Parameters are required to enable controls

in regards to partners and GDSs, e.g. Carrier eligibility table.

3 TST. Ability to display Transitional Stored Ticket.

4

Ticketing Functionalities. Ability to allow E-Ticket exchanges,

add, collects, re-price and re-issue, refunds, voids, suspend

and revalidate.

5

Link Records. Functionality is required to link E-Ticketing

records to one or more segments in multiple PNRs and/or to

name, coupon, and segment automatically.

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

system.

7 Automatic refund and exchange. Ability to exchange and

refund E-tickets automatically.

8 Coupon status. Ability to support manual change Coupon

status by duty code.

9

ETKT display. Ability to display the same ETKT elements on all

GDS and IET carriers as displayed on AIR ALGERIE system

regarding creation, change and cancellation.

AOIR : N° 001/DC/2016 Page 41

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

10

Display Single Electronic Ticket Record (ETR). Ability to display

ETR by ticket number, record locator, FOID or

name/flight/date/Segment.

11

Display Multiple Electronic Ticket Records (ETR). Ability to

display all ETRs by board point city, carrier/flight number or by

frequent flyer number…

12

E-Ticket History Display. Ability to:

- Display used E-ticket online 60 days at least;

- Retrieve E-ticket/TST/TSM purged files (Archives).

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

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

distribution channels.

15

Printing. Ability to support the printing of coupons, receipts

and itinerary/receipts.

Itinerary/receipt, itinerary outputs (carrier name…) must be

converted from the ticket into a plain language itinerary.

It must be possible to send ticket receipts by email.

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

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

system.

18 Interline Partners & Codeshare. Ability to support IET

standards and codeshare options.

19 FOP. Ability to support multiple forms of payment (CC, Invoice,

Miles, check, cash…)

20

Sales Reporting. Ability to provide Sales reporting by office, by

agent with all transaction details for:

- E-ticket sales, service fees and EMD,

- Reissues, void and refunds of E-tickets

21

Daily Sales Reporting. Ability to manage finalization sales

report manually or automatically for each ATO/CTO every day

based on local time.

AOIR : N° 001/DC/2016 Page 42

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

EMD Management

22 EMD Type. Must support both EMD types associated and

standalone.

23 EMD issuance, change, cancellation and management must

be compliant with Industry Standards.

24

Auxiliary Services. Ability to issue EMD for auxiliary services

that may be requested by a passenger: car rental, hotel

accommodation, surface transportation and tour…

25 Retrieve EMD. Ability to retrieve EMD by Name/City

pair/Flight number/Date/EMD record.

26

The system must allow:

- EMD archiving,

- Interline EMD management,

- EMD reporting,

- EMD issuance by external systems (GDS),

- Ground Handling EMD (external DCS).

3. 5. Système de Contrôle des départs (Departure Control System)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

Passenger processing & Flight Control Management

1

RES & DCS Access. Access to some reservation functionalities

(PNR, E-TKT, EMD, customer profile, flight program…) through

DCS workstation.

2

Integration. The RES/INV/FFP/DCS modules must be fully

integrated and all process must be integrated across all

modules.

3

CUTE and back office. The DCS must be certified Common

User Terminal Emulation (SITA CUTE, ARINC MUSE, RESA

CREWS …) and can be used on back office.

4

DCS version for GHA. Ability to process AIR ALGERIE flights

without a reduction in functionality or degradation in the level

of services offered when the GHA is using the same DCS

solution.

5 Interface. Ability to be interfaced with:

- Revenue accounting system,

AOIR : N° 001/DC/2016 Page 43

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

- Catering system,

- Cargo system,

- Baggage reconciliation system (BRS),

- Schedule system (Flight and crew),

- Flight planning system,

- ACARS,

- Central Flow Management Unit (Eurocontrol),

- Aircraft data links system.

The supplier must provide a list of the available interfaces for

the systems above.

6 WorldTracer. Ability to access WorldTracer and its

functionalities via DCS.

7

Additional Information for Agents. Ability to support special

displays and interfaces to provide enhanced information to

check-in agents :

- Encode-Decode,

- World city time / Airport information / Other information,

- Timatic,

- Help.

8 EDIFACT format. Ability to support standard EDIFACT format

and its variants.

9 Capture information. Ability to capture passenger information

from MRZ on documents automatically upon swipe/scan.

10

Other Devices Access. Ability to support access by structured

data from intelligent devices (e.g. self-service units, hand-held

devices, gate readers, OCR/MSR devices …). It must support

multiple devices on one workstation.

11

Boarding Pass and Bag Tag Printers. Ability to allow a default

boarding pass and Bag Tag printer for each workstation

whether the system is accessed via session, internet or Web.

12 Printing. Ability to issue boarding pass and tag bag according

to the loaded PECTABs in the system.

13

Print Options. Ability to support the printing in hardcopy form

all types of passenger informational displays either as a

“screen dump” or specifically formatted for hardcopy. Printing

must be to any host defined output device.

14

PECTAB. Ability to send an AEA Parametric Data Concept

message for bag tag and boarding pass to host or cute devices.

Layout/format, bar codes, human readable letters/numbers in

AOIR : N° 001/DC/2016 Page 44

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

the PECTABs are defined by AIR ALGERIE and must comply

with all IATA Standards.

15 PECTAB. Ability to print Arabic characters and graphical forms

(logo …) in the boarding pass.

16

PECTAB Updates. Ability to change the PECTAB tables and to

control/manage the changes with regard to the BP/BT

documents used in each station.

17 RFID. Ability to generate RFID tags and support all related

functions to RFIDs (e.g. tracking and locating etc.)

18 Text and remarks. Ability to add free format text and remarks

on the boarding pass.

19

Aircraft Configurations. Ability to cater for all aircraft types

which are utilized through the RES application but also to cater

for different seat configurations for all of these aircraft (many

to one correlation).

Ability to cater for aircraft types and seat configurations which

will be input manually and not come from the RES system.

There should be no restrictions on the number of aircraft types

or the number of configurations per aircraft type for the DCS

application.

20

Aircraft Types-View & Copy. Ability to display all aircraft types

and their configurations. It must be possible to copy and then

amend a type/configuration to create a new aircraft

type/configuration.

21

Aircraft Types-Create. Ability to configure each aircraft and

add the configuration into the database in a swift and accurate

method according to the standard format.

22

Online Aircraft Changes. Ability to cater for late equipment

changes, reweighs/reconfigurations. These changes must be

updated in the reservation and inventory systems.

23

Seat Characteristics. Ability to support all standard seats

types’ characteristics. e.g. : window seat, aisle seat, over wing,

forward, rear, restricted recline, exit row, basinet row,

permanently blocked seat ...Plus, seats characteristics which

are user definable.

AOIR : N° 001/DC/2016 Page 45

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

24

Seat Characteristics Amendment. Ability to amend individual

or groups of seats’ characteristics for specific aircraft and/or

aircraft type either immediately or from/to a specific date. An

ad-hoc provision to change a seat or group of seats for a flight

segment is also required.

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

and galley.

26

Change Seat Assignment. Ability to change seat assignment

with automatic generation of new boarding pass and check-in

agent warning. It must be possible to override the system and

assign seats that would not normally be applicable to the

passenger or to upgrade/downgrade them into another cabin.

27

Inhibited Seat Assignment. Ability to inhibit seat assignments

(e.g. no infants in exit rows). Wherever possible this should be

warned automatically by the system, with the capability to

override manually.

28

Pre-Assigned Seats. Ability to edit/release any pre-assigned

seats and/or protected seats both manually and based on

system time parameters.

29

Re-assign Seat. Ability to provide the functionality to re-seat

or offload/delete a checked-in/boarded passenger either

individually or by groupings.

30

Non-reservations Flight Creation. Ability to create revenue

flights, charter flights, cargo flights, Ground Handling flights,

test flights, pseudo flights…

31

Flight status. Ability to support the following flight status:

- Flight editing,

- Check-in Suspended,

- Flight Open for check-in from all channels,

- Flight Held,

- Flight updated,

- Flight closed for check-in,

- Flight gated,

- Flight finalized,

- Post Departure.

32 Flight Amendment. Ability to add a leg to an open flight

without any disruption for the check-in process.

33 Re-open Flight. Ability to re-open a post departed flight with

single or multiple legs (the ability to open any leg).

AOIR : N° 001/DC/2016 Page 46

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

34 Ability to manage a flight from the diverted station.

35 Online Flight Changes. Ability to accept late flight changes,

and must be updated in the inventory system.

36 PNL/ADL. Ability to support PNL/ADL processing (codeshare

flights, third party…).

37

Flight open. Ability to open Flight for specific check-in

channels based on configurable parameters: Airport check-in,

Inbound Through Check-in, Web check-in.

38 Online/Offline. Ability to set and manage a station as online or

offline (station handled in a different DCS).

39

Stations. Ability to identify the stations for which General

Declaration (GD) is required, and maintain this list of stations.

The GD must be sent automatically.

40

Government order. Ability to set a flight as eligible for

API/APP/AQQ/PNRGOV/iAPI printing of the boarding pass is

inhibited until the complete API data are submitted.

41

New Regulations security/immigration processing to support

control authorities. Ability to comply with any future

Government initiatives before the compliance date set by the

Government.

42 US DOT. The DCS must be certified to work with the

USDOT/TSA and support existing regulations.

43

Watch lists. Ability to check passengers API based on the

match of SPL (Specified Persons List) and the Black list for

flights to Canada and USA. The printing of the boarding pass

must be inhibited in case of mismatch and the check-in agents

prompted. The database must be regularly updated.

44

Limitations on the flight. Ability to allow the following

limitations on the flight :

- Number of infants according to aircraft

type,

- Number of WCHx,

- Jump seats,

- Number of passengers in the waitlist...

45

ETKT/PNR access. Ability to retrieve and display the

passenger’s PNR and ETKT from DCS, via a line number

reference, or seat number reference, boarding number, a bag

tag number or PNR code.

AOIR : N° 001/DC/2016 Page 47

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

46

Single/Multiple Remarks. Ability to enter public and/or

private remarks (refer to RES requirements) for passengers

selected from a display (i.e. one or more passengers). This

functionality should allow one or more remarks to be entered

into all PNRs selected.

47

SSR/OSI Codes. The application must process SSR/OSI

elements at check-in and provide the check-in agent with

adequate information to pass onto the customer, e.g. advice

to the passenger on whether or not a request has been or can

be fulfilled.

48 Frequent flyer number. Ability to check and validate the

frequent flyer number with regard to the customer profile.

49 FQTV Validation. Ability to validate FQTV in DCS for other

airlines program according to the bilateral agreement.

50

Flight displays. Ability to display :

1) General flight information (flight number, routing, time,

registration, configuration, ...);

2) Commercial flight information (flight number, figures of

passengers booked, checked-in, waitlisted, infants and

Childs, codeshare information, meals, ...);

3) Operations flight information (Dry operating weight/index,

pantry and hold versions ...);

4) Baggage information (bag count, weight summary,

different lists of all bags assigned to a flight, whether

associated to a passenger or not …).

5) Boarding information.

51

Arrival/departure flights. Ability to display arrival/departure

flights list by date :

- Flight number

- Destination

- STD/STA

- ETD/ATD

- ETA/ATA

- Aircraft registration

- Number of passengers booked

- Flight status

- Terminal

- Gate number.

AOIR : N° 001/DC/2016 Page 48

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

52

Check-in Displays. Ability to provide various displays of

inventory levels by cabin, which include seating capacity, seats

booked (from inventory), available seats, seating limits,

checked-in and accepted passengers, protected seats, number

of passengers on standby, desiring through passengers and the

remaining number of passengers to check-in, goshow, ID,

special ID etc. Provide flight counts throughout check-in

process and reconciliation information at flight close-out.

53

Passenger Lists. Ability to display passenger and standby lists

including “logical opposite” options such as “Non-Checked in”,

All lists as defined in Reservations e.g.: list by class, by SSRs, …

54

Passenger Check-in list Display is required :

- Flight number

- Full name

- Gender

- Seat number

- Baggage Piece/Weight

- Class

- Segment

- Checked-in by

- SSR and comments

- Check-in status

55

Passenger Display Check-in. Ability to support passenger

check-in from a passenger list or full passenger display (i.e.

supplying the line number for a single party or multiple

numbers/range of numbers for multiple party check-in).

56

Passenger Name Check-in. Ability to support passenger check-

in by a portion of passenger name, including providing a

Similar Names List from which to select, if similar names exist.

Example, require agent to enter only first two characters of

passenger name, followed by number in party.

57

Multiple Passenger Name Check-in. Ability to support multiple

passenger check-in by a portion of more than one passenger

name, including providing a Similar Names List for both

passengers from which to select, if similar names exist.

Example, require agent to enter only first two characters of

each passenger’s name, followed by number in party.

58

Partial PNR acceptance. Ability to support Partial PNR

processes, e.g. only one passenger from a PNR checking-in

with others either checking in at a subsequent time or being

treated as no-shows. The application should automatically

AOIR : N° 001/DC/2016 Page 49

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

attempt to reserve suitable seats for other passengers in the

PNR so that they will be seated together if possible.

59 Cancel Check-in Transaction. Ability to cancel all incomplete

(pending) check-in requests.

60

Pseudo Groups/Parties. Ability to identify passengers who

have been checked-in together even though they are traveling

on different PNRs (i.e. pooling).

61 Upgrade/Downgrade. Ability to manually upgrade or

downgrade a passenger into a different cabin and or class.

62

Upgrade/Downgrade. Ability to provide a mechanism to

manage Upgrade/Downgrade lists. This includes passengers

being automatically or manually placed on such lists at the

time of check-in or subsequent to check-in based upon system

parameters. The ability to identify upgraded/ downgraded

passengers as voluntary or involuntary.

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

ticket number.

64

Accumulate weight. Ability to accumulate the total weight of

all checked-in bags, with possibility to print each piece weight

on the tag bag in addition to the total weight of all bags.

65

Bag Tag from Passenger Display. Ability to support issuing bag

tags from a passenger list or full passenger display (i.e.

supplying the line number for a single party or multiple

numbers / range of numbers for multiple bag tag issue).

66

Replacement Bag Tags. Ability to replace previously issued

tags. The original bag tags would be deleted/cancelled and the

new ones would reflect the checked baggage. A record of

old/deleted bag tag numbers would retain.

67

Excess baggage :

- Apply IATA Resolution 302 ABR bag rules and rates to

calculate excess baggage fees.

- Ability to prompt total excess baggage amount, calculated

based on the total excess weight and the baggage rate for

the destination

- Must be detected based on ticket allowance and other

allowances and waivers, as defined in the system. The

waivers and allowances include but will not be limited to:

* Frequent flyer entitlement,

* Agent discretionary waivers

* Prepaid bags

AOIR : N° 001/DC/2016 Page 50

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

- Restrict the boarding pass print. This setting shall be

configurable.

68

Excess Baggage Coupon. Ability to print excess baggage

coupon by weight and piece.

The coupon must include:

- Flight number,

- Routing,

- Passenger name,

- Sequence number,

- Excess baggage weight,

- Number of extra pieces.

69

Re-issue Boarding Pass. Ability to reissue a previously issued

boarding pass. The check-in agent should be prompted to

retrieve the original boarding pass from the passenger.

70 Payment Collection. Ability to collect ancillary services fees

and issue EMDs.

71

Bulk Transfer. Ability to bulk transfer passengers (whether

checked-in or not, standby...), with all their relevant

information, from one flight to another and from one airport

to another.

72 Disruptions managements & Automatic Seat Re-

accommodation in case of flight equipment change.

73 Flight Interruption Manifest. Ability to support FIMs according

to IATA recommendations.

74 Codeshare flight. Support operating and marketing carrier

flight numbers and codes for IATCI down-line connections.

75 Codeshare Tags. Ability to print the true operating carrier

flight number on the bag tag as required.

76

IATCI. Ability to support all IATCI standards and recommended

practices including Interline Fall Back (IFM) messages and bi-

directional messages for Through Check-in.

77

Connection Flight Data. Ability to add manually connection

flight data to a passenger’s DCS records and automatically

perform through check-in.

78

Through/Transit Passengers. Ability to manage

Through/Transit passengers in the same manner as originating

passengers are handled.

AOIR : N° 001/DC/2016 Page 51

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

79

Non-Revenue Passengers. Ability to provide a mechanism to

manage Non- Revenue passengers and identify Non-Revenue

passengers based on UL rules at all stages of the check-in

process.

80

Auto Seat or Standby. Ability to auto-examine the availability

of seat upon check-in and either assign a seat or a standby

priority. The check-in agent must be prompted when a

passenger goes on standby and the printing of boarding pass is

inhibited.

81

Standby Handling. Ability to provide a manual and automated

management of standby passengers revenue/nonrevenue,

based on business rules.

82 Cockpit Access. Ability to support the assignment of Jump

Seats and cockpit seats for qualified personnel.

83

Jump seat. Ability to show Jump seat passenger figures in :

- Passenger manifest

- Total checked-in figures

- Relevant post departure messages

- BSM for the baggage accepted

84 Passenger Boarding/De-boarding. Ability to mass board/de-

board the aircraft (Automatically or manually).

85 Gate Assignment. Ability to assign flights to a gate and change

the gate assignment as required.

86

Boarding documents. Ability to generate boarding documents

for control e.g.: PIL, passengers’ counts, missing passengers

report…

87 Meal calculations. Ability to calculate the expected number of

meals in each cabin.

88

Messages Addresses Ability to support an unlimited number

of addresses to receive check-in and loading messages as the

flight is closed out.

89

Post-Departure Messages. Ability to generate all lists and send

(automatically or manually) all IATA standard messages at

flight departure such as FTL, PSM, PTM, SOM, TPM, and IDM...

90 Inhibit messages generation. Ability to inhibit messages

generation for Training flights, Test flights …

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

codeshare flights.

AOIR : N° 001/DC/2016 Page 52

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

92

Flights processing. Ability to default any session to any flight

(one or multiple flights). This enables the check-in agent to

input transactions without the need to repeat the flight

number and date in the input.

93 Flights processing. Ability to process multiple flights on the

same screen.

94 Ramp management tools. Ability to manage/coordinate Ramp

tasks.

95

History transactions. Ability to capture all flight transactions

for any level and retrieve the report online (the supplier must

specify the number of days that history is Available in the

system).

96 Reports. Ability to provide different reports by agent code e.g.

Number of PAX checked-in …

Load Control

97 Centralized Load Control. Ability to support Centralized Load

Control including multi flight handling.

98 Integration. Weight & Balance and check-in functionalities

must be fully integrated within DCS.

99

User profiles. Ability to allow the creation and differentiation

of user profiles e.g. load control Supervisor / Agents etc. and

provide secure single login feature.

100

Display of flight progression. Ability to provide a display of

flight progression including (but not limited to):

- Up line release,

- Aircraft registration,

- Transit passenger / baggage details,

- LDM/CPM from non-mechanized,

- Load Instruction generated,

- Fuel Sheet / ZFW message generated,

- Check-in linked,

- Passenger seating completed,

- Flight Status (Open, Closed, Suspended,

Hold, Released),

- Check-in / boarding Status (Open, Closed,

Released, Unavailable),

- Load Sheet generated,

- Close out messages sent.

101 IATA standard formats. Ability to support IATA standard

AOIR : N° 001/DC/2016 Page 53

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

formats for load sheet/load plan/NOTOC and other load-

planning related messages.

102

IATA messages. Ability to process incoming LDM, LPM, and

CPM messages from an up-line station with third party

mechanism.

103

Supplementary information. Ability to display and update

supplementary information that may be associated with all

types of messages.

104

Capturing of changes. Ability to capture the changes of

cargo/mail/baggage/COMAIL made by local airline personnel

at stations as defined by the business rules.

105

Aircraft Types. Ability to support these aircraft types :

- narrow / wide bodied,

- Multi deck, Combis and freighters.

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

multi sector / charter / ad hoc flights.

107 Aircraft changes. Ability to support aircraft changes

automatically or manually actioned by load control.

108 Lock/unlock. Ability to provide the facility to lock, unlock a

flight and cancel a flight from the System.

109

Estimated zero fuel weight. Ability to provide Estimated zero

fuel weight information and fuel data to/from Flight Planning

System.

110 Standard IATA UWS. Ability to receive standard IATA UWS

cargo messaging for load planning and finalization.

111 Graphical aircraft loading. Ability to support graphical aircraft

loading capabilities (move/swap/drag/drop load items).

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

113

Creation of flights. Ability to support creation of flights at

departure, en-route and diversion stations including offline

stations.

114

IATA load control documents. Ability to provide generation

and printing of IATA load control documents including

graphical for (but not limited to):

- Load Instruction Report,

- Provisional / Final / ACARS Load Sheet,

- ZFW Messages,

- Fuel Loading Instruction,

AOIR : N° 001/DC/2016 Page 54

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

- NOTOC documents.

115

Load planning. Ability to provide a customer-configurable

table of passenger and baggage weights to be used for load

planning purposes.

116 Weight table. Ability to change passenger/baggage weight

table (load planning or check-in) for a flight.

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

sending load sheets via ACARS.

118 ACARS messaging. Ability to provide free format ACARS

messaging with option to inhibit by location, sign-in level, etc.

119 Preplanning purposes. Ability to store historical data in the

system for preplanning purposes.

120

Trimming. Ability to support trimming by:

- class/cabin & seat row,

- compartment/bay.

121

Adjustable and restricted weight. Ability to support

maximum, adjustable and restricted weight and trim

limitations for ZFW, TOW, LDW, RTOW, TW.

122

Control parameter. Ability to automatically calculate,

recalculate and validate the control parameter as and when

any cargo, mail, baggage weight / passenger weight / crew /

catering or placement data is added, modified, or deleted

from external system or DCS.

123

Graphical presentation of balance conditions. Ability to

provide a graphical presentation of balance conditions,

including Ideal Trim Range / C of G for ZFW, TOW, LDW and

MAC. Different colors are used to depict different limits.

124 Baggage classification. Ability to support all types of baggage

classification. E.g.: BF, BC, BY, BT, BR …

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

local / transfer dead-load.

126 Auto-load distribution. Ability to support auto-load

distribution with optimal balance.

127 Dangerous Goods conditions. Ability to incorporate

Dangerous Goods conditions.

128 Loads transfer. Ability to support all loads transfer.

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

AOIR : N° 001/DC/2016 Page 55

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

130 LDP documents. Ability to store/retrieve/reprint all LDP

documents (load-sheet, load-plan …).

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

balance limitations.

132 Balance condition. Ability to adjust balance condition by

offloading manually an overloaded aircraft.

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

closure.

134 Validate flight closure. Ability to validate flight closure and

load sheet issuance according to capacity limitations.

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

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

IATA 560 & 565 format.

137 Static database. Ability to manage static database (display,

add, update, delete …) according to user authority.

138

ULD database. Ability to provide ULD database, to include

individual / ULD type tare weights and ULD numbers according

to business rules.

139 Display/re-print. Ability to display/re-print load-sheet, load

plan and NOTOC after departure.

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

3. 6. Système de Tarification (Fare Quote System)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

1

ATPCO and SITA database. Ability to collect from both ATPCO

and SITA all fares and rules. The supplier should indicate the

update frequency.

2

ATPCO categories. Ability to support all ATPCO categories

from 00 to 50, YR/YQ/ optional services/ routing/ footnote/

taxes.

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

high.

AOIR : N° 001/DC/2016 Page 56

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

4

Multiple options. Provide the ability to retrieve fares with

multiple options, e.g. Private fares, Passenger type and Fare

type.

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

before creating PNR.

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

OAL general rules.

7 Rule content default. The System must ensure that rule

content default is ATPCO.

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

9

Best Buy pricing from fares. Ability to display the “lowest

fare” by sorting fares over through fares in order, from low to

high.

If a date is included in the input, only those fares valid for that

date are considered. Ability to automatically create an

itinerary for the chosen option without manually booking

flights.

10 Best Buy pricing from availability. Ability to easily select the

cheapest available flight segment from an availability display.

11

Best Buy pricing from Itinerary. Ability to easily select the

cheapest available class from an existing itinerary and to re-

book the relevant segments with the cheaper class in a single

transaction.

12

Basic fare information. Ability to provide the minimum

requirements for basic fare information as per industry

standard such as fare basic code, booking class, carrier, etc.

13

Additional information. Ability to retrieve additional

information based on :

- RBD by carrier,

- Routing,

- specific rule category,

- Taxes/fees (ATPCO service fees)/other charges.

14 Additional information. Ability to retrieve distance between

cities/airports (kilometer, miles).

AOIR : N° 001/DC/2016 Page 57

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

15

Currency. Ability to retrieve fares in more than one currency

at one time sorted by currency. Convert to any currency

regardless of currency field.

16

Specific Exchange Rate. Ability to provide user option input to

select specific exchange rate or multiple exchange rates for

currency conversions.

17

Pricing currency. Ability to price:

- Itinerary using specific currency,

- In currency of choice unless inhibited by AH specific rules

or government regulation.

18 Specific rule entries. Ability to provide specific rule entries by

carrier/IATA fares, city pair, fare-basis code, rule number.

19

Fare calculation element. Price itinerary with details of each

fare calculation element ( but not limited to fare basis )

including taxes and tax type, passenger facility charges (PFCs),

Global Indicator, currency, fare including base, tax, total,

surcharges, ROE.

20

Price itinerary. Ability to price with specific segment, multiple

segments, combined with any one or combination of :

Specified fare basis, discount amount/percentage, passenger

type(s), override connection/stopover, point of ticketing, side

trip, tax exempt, tax (es), validity dates, restricted fares…

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

22 Segments out of sequence. The System must inhibit auto-

pricing of segments out of sequence in a single PNR.

23 Pricing. Ability to manage different IATA pricing controls.

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

25

Reason for failure. Ability to provide the reason for failure

when the itinerary does not price as booked, the system must

provide options for the itinerary (e.g. minimum stay not met,

fare combinability …). If necessary the system must provide

normal fare of the relevant cabin otherwise IATA fares.

AOIR : N° 001/DC/2016 Page 58

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

26 Zone Employee Discount (ZED) fares. Ability to price ZED fares

and calculate the taxable amount for specific countries.

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

from unrestricted fare.

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

the PNR.

29

Fare Calculation Mode Indicator. The system must have the

facility to apply Fare Calculation Mode Indicator (FCMI) to all

types of tickets (E-ticket, EMD).

30 Manual fare calculation. Ability to build a manual fare

calculation to drive a ticket applying industry standard format.

31 History. Ability to provide history for all fare and rule

transmissions at minimum 12 months.

32 Exchange Rate. Ability to provide history of all exchanges

rates within system window at minimum 12 months.

33 Online Query. Ability to provide online query to access all

historical fare and rule data.

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

sort order.

35

BSR/BBR. Ability to Update/process BSR/BBR/IROE according

to industry standards (IATA resolution 024 series). Use ICH 5

day rate when standard industry source are not found in the

IATA resolution 024e series.

36 ICH/BSR/BBR/IROE. Ability to retrieve all or specific current

exchange rates for: ICH/BSR/BBR/IROE.

37

Rounding Principles. Process the rounding principles

according to IATA resolution 024d for fares and other charges

and amounts truncated for currency conversions.

38

Fare Construction Principles. Ability to enforce all fare

construction principles according to the IATA resolution

manual for composite.

39 Free Baggage Allowance. Ability to retrieve all carriers free

baggage allowance per carrier including dimensions for all

AOIR : N° 001/DC/2016 Page 59

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

points or by city pair or origin/destination countries filed in

ATPCO.

40

Excess Baggage Charges. Ability to retrieve all carriers’ excess

baggage charges per carrier including dimensions for all

points, by city pair or by origin/destination countries.

41 Taxes/Fees/Surcharges. Ability to retrieve all applicable

taxes/ fees/ surcharges by country or by city pair.

42 Calculation Mileage. Ability to support TPM and MPM

calculation Mileage.

43

Mileage. Ability to calculate mileage for a string of cities w/o

PNR (including carrier, surface sectors, global indicators, fare

amount).

44

Corresponding fare. Ability to return fare corresponding to

the available inventory (availability of seats in the flight in the

particular RBD). The system should price the lowest fare

according to the RBD available.

45

Remark. Ability to generate automatically a remark for

specific fares according to passenger typology (e.g.: generate

remark for special discount for infant to provide document

proof).

3. 7. Système de Gestion des recettes (Revenue Management System)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

Revenue Management System

General :

1 Integration. Must be Integrated with Inventory.

2 Revenue Accounting Data. Ability to process Revenue

Accounting data.

3 Ability to provide a leg based system.

4 Ability to be upgradeable to O&D system.

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

AOIR : N° 001/DC/2016 Page 60

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

6 Ability to control economic, business and first cabin.

7 Ability to control code share flights.

8

Ability to consider program irregularities and update

automatically data after every change made to flights in the

inventory.

9 Ability to update automatically the set of historical flight every

night with the departed flights.

10 Ability to ensure a competitive intelligence.

11 Ability to handle more than 26 classes.

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

13 Ability to store data minimum 10 years for forecasting and

reports.

14 Web data provider integration is required (QL2, INFARE or any

other solution).

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

16 Ability to manage and influence forecasting and optimization

process.

17 Ability to detect and alert when flight data failed to be

received or to be transmitted.

18 Ability to provide a guidebook related to the Revenue

Management System.

Forecasting

19 Ability to provide different forecasting models.

20

Ability to provide forecasting according to historical data per:

- flight/segment/leg/market/network,

- Date/Range date,

- Class/Cabin.

21

Ability to forecast by taking into account: demand, load factor,

No-Shows, cancellations, upgrading, spoilages and expected

to-board passengers at booking class level…

AOIR : N° 001/DC/2016 Page 61

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

22 Ability to take into consideration market growth/decline and

sudden change in market.

23 Ability to take in consideration Pricing elasticity and business

rules.

24 Ability to handle events calendar.

25 Ability to take into account competitors practice.

26 Ability to detect and alert abnormal flights.

27

Ability to manage manually and/or automatically forecasting

of flights (e.g.: date level, include or exclude given flight in

historical data…).

28

Ability to display the history for all manual or automatic

actions taken during the flight's life cycle (changes in controls

and forecasts…).

29 Ability to store all the actions performed by the user and the

forecasting provided by the system.

Optimization

30 Ability to provide several statistical model of optimization

(EMSR, EMSR b…).

31 Ability to take into consideration competitors based on

departure time, arrival time and route…

32 Ability to take into account the competitor's fares to re-

optimize on real time with user validation.

33 Ability to fill and extract data automatically and frequently.

34 Ability to provide analysts flight re-optimization according to

predefined parameters.

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

36

Ability to alert analyst for flights presenting risk of spoilage

(low booking classes closed too early or low booking classes

still available despite valuable demand).

Overbooking

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

AOIR : N° 001/DC/2016 Page 62

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

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

shows.

39 Ability to include or exclude reservation classes defined by the

user

40 Ability to alert analysts for flights presenting risk of denied

boarding.

41

Ability to compute and display departure day indicators

including, but not limited to indicators such as Expected

Revenue, Expected Load Factor, Passenger Expected Load

Factor,...

Reporting

42 The system must generate reporting with different format

(text, excel, word document, PDF…).

43

The reports must include, but are not limited to the following

information: Reservation, Inventory Departure Control,

Forecast, Optimization, Fare data…

44

The system must be able to :

- Select a variety of fields according to user criteria,

- Provide report about all user's actions.

45

Ability to provide reports per log date for specified periods

(year, month, dates) according to a market, network, routes,

flight number, cabin compartment,….

46 Ability to provide reports per (including but not limited to)

O&D, POS, flight number…

47

Ability to provide reports including but not limited to load

factor, booking by class/cabin, estimated revenue, risks

management, overbooking, no show, waitlist,...

48 Ability to provide reports including traffic distribution by

segment/leg for multi leg/circular flights.

49 Ability to establish comparison based on periods having all

classes, schedule, booking rates...

50 Ability to provide categorization tables.

AOIR : N° 001/DC/2016 Page 63

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

51 Ability to provide reports about availability by class.

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

53 Ability to provide reports about performance ratios by flight

analyst.

54 The system must provide reports about abnormal flights

presenting false or missing data.

55

The system must provide reports about pertinence of

forecasting and optimization

Group Management

56 The RMS must include a Group management module.

57 The Group module must be integrated with the inventory.

58 Ability to process Revenue Accounting data.

59 This module must Manage PNR Group creation, cancellations,

amendments, payments and historical Groups.

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

61 The system must provide Group quotation methods

(individual movement and others)

62 The system must be able to automatically generate groups

fare quote.

63 The system must provide an evaluation of the expected recipe

(positive/negative) once the Group is accepted.

64 In case of a negative recipe, the system must provide

alternatives (offer a rerouting, flight change…).

65 The system must be able to store Group's characteristics (size,

dates, and destinations).

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

of the group.

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

group cancellation.

AOIR : N° 001/DC/2016 Page 64

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

68 Must provide an evaluation rate of the flight.

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

70 Must provide evaluation report.

71 Must provide reports about No Show, payment and sites

creators of Groups.

72 Ability to manage Groups requests collected from travel

agencies.

73 Ability to set and enforce checks for Groups (deposit, ticketing

time limit…).

3. 8. Système de Fiabilisation des ventes (Revenue Integrity)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

Revenue Integrity Management

1 Integration. The system must be integrated with all PSS

modules (reservation/ticketing, inventory, DCS…).

2 Time Limit Management. Ability to manage Time limit

controller.

3

Time Limit Controller. Ability to provide a Time Limit

Controller for:

- Un-ticketed individual PNRs segments;

- Un-issued EMDs for chargeable services.

4

Time Limit Controller. Ability to provide a Time Limit

controller for PNRs group to enforce compliance with Group

Deposit, Names, and Ticketing requirements.

5

Ability to detect :

- MCT violation;

- Impossible journeys according to business rules;

- Redundant segments;

- Churning PNRs.

AOIR : N° 001/DC/2016 Page 65

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

6

Duplicate PNRS. Ability to detect duplicate PNRS for

Overlapping flight times and Incoherent or duplicated

segments / O&D itineraries according to defined rules such as :

- Name Comparison

- Information from the PNR (passenger contact, FFP number,

Gender, APIS, Date of birth).

7

Fictitious and Suspicious Names. Ability to detect Fictitious

and Suspicious Names and control name changes according to

defined rules.

8

Hidden Groups. Ability to detect hidden Groups according to

defined rules such as :

- Same market/flight and travel date;

- Departure time within defined criteria;

- Booked or last changed on the same calendar day;

- Same Class(es);

- Booked by same booking office (IATA/Pseudo City Code or

Booking Office ID)

- Total passengers in combined PNRs.

9 Waitlist clearer. Ability to Remove waitlisted segments

present in PNRs (waitlist clearer).

10

Synchronize E-Ticket. Ability to Synchronize E-Ticket to

reservation and control all reservation changes (e-ticket

mismatches, manual associated e-tickets …).

11 E-Ticket Control. Ability to detect and cancel PNRs with voided

and refunded E-Tickets according to business rules.

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

synchronizations.

13 Control and audit. Ability to control and audit in real-time all

unusual sales for agencies.

14 Passive booking. Ability to detect Passive booking (Passive

requests not matching any active booking).

15

Control E-ticket. Ability to control E-ticket match to the flight

(passenger name, class, route, carrier, flight number, date,

infant indicator …) at check-in.

16 Coupons order. Ability to control the use of coupons in the

AOIR : N° 001/DC/2016 Page 66

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

correct order at check-in.

17 Typological Fares. Ability to control validity of Typological

Fares at check-in.

18

Go-show Handler. Ability to check if passenger RBD of fare is

valid for go-show when checked-in and update the PNR

according to business rules.

19

No-show Handler. Ability to detect any booking with a no-

show passenger as defined and update the PNR according to

business rules.

3. 9. E-Commerce

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

IBE management

1 Integration. Ability to interface with PSS components, loyalty

system, and AH corporate web site.

2

Integration with AH web site. Ability to provide all required

tools/widgets/web services detailed documentation to

interface AH web site with the provider's IBE and all related

services, The provider must guarantee all the

support/assistance required.

3

Administration Tools. Ability to:

- Customize the IBE with the look and feel of AIR ALGERIE’s

brand,

- Configure page layouts,

- Modify and optimize booking flows (E.g. change/ reduce

booking steps).

4

Administration Tools. Ability to :

- Customize and categorize ancillary services and cross-

sells,

- Configure promotional web offers/corporate offers,

AOIR : N° 001/DC/2016 Page 67

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

- Enable and disable features, preview changes, track

changes and roll back changes.

5

Administration Tools Management. The administration and

the configuration must be done autonomously according to

configurable rules.

6

Graphic charter and content edition.

IBE should be adapted to respect AIR ALGERIE graphic charter

to guaranty a consistent visual identity; graphic, iconographic,

typographic and ergonomic guidelines should be integrated.

Ability to modify texts, tooltips, re-directional links, popup and

notification messages, error and information messages, field

indications and acceptance checkboxes.

7

Fare Family management. Ability to provide a full Fare Family

management tool: real time creation, maintenance and

update of fare families….

8

Advanced/Inspirational Search Tool. Ability to offer an

advanced tool to provide for web site visitors an attractive

experience using flexible search (flexible date range/flexible

destinations) and combined search criteria

(activity/destination search, week-end search, budget driven,

period of stay...).

Result travel recommendations should be displayed in easy

manner for a quick comparison and upsell.

9

Secure environment. A robust SSL certificate must be

provided, its renewal and maintenance will be included in the

support contract.

Data transmission, storage and use must be done in

accordance with all security processes/ protocols and

applicable laws.

10

Browser Compatibility: IBE should be compliant with major

and widely used browsers, IBE should also be maintained to

meet technology development and new versions release.

11

Hosting. The solution must support :

- Availability and Risk management

- High availability (99.9 uptime is the minimum required)

- Online traffic including temporary peaks/overloads.

- Traffic evolution, smooth and fast navigation.

AOIR : N° 001/DC/2016 Page 68

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

12 Hosting. Hosting management including security, monitoring,

enhancements and maintenance are provider responsibility.

13

Cost/Performance control.

- Ability to provide all mechanisms to keep a cost effective

solution and protect AIR ALGERIE revenue from bad and

abusive practices (protection from scripts and bots,

illegitimate HTTP post/get, crawling)

- Ability to keep tracking/logs of activities including

Metasearch engine controls, pricing transactions

optimization.

- Ability to employ IP throttling and blocking to restrict the

number of hits to the host system and reduce site

performances.

14

Monitoring & updates: Ability to maintain an up to date

solution with all corrective patches, updates and

enhancements according to latest technologies and standards

(e.g.: Security recommendations, Industry norm and

standards…).

15

Test environments. Ability to provide testing environments

(e.g. workflow, design, layout changes, adding functionality,

enabling and disabling features, developments…).

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

for multiple destinations.

17

Availability Search. Ability to support combined criteria for

availability search including :

- Trip type (OW, RT, itineraries with multiple stopovers,

open jaws,,),

- Reservation class,

- Schedule search : should display existing flights per travel

dates, over a configurable range,

- Flexible search : calendar/matrix display per travel dates,

over a configurable range,

- Direct flight only filter/ Origin-destination.

18

PTC. Ability to support multiple PTC in query/ list all supported

PTC.

Ability to apply specificities/checks/restrictions according to

selected PTC (applicable fares, additional information on PAX

details, specific SSRs…).

AOIR : N° 001/DC/2016 Page 69

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

19 Group Booking. Ability to handle group booking.

20 Calendar Display. Ability to support Calendar fares display.

21

Fares. Ability to support:

- Fare families/branded fares,

- Online/web oriented fares,

- Typological fares according to selected PTC (adult, infant,

child, student, senior, youth, UM…),

- Behavioral fares (family plan, couple plan…),

- Web discount code capabilities.

22 Display remaining seats. Ability to display remaining seats,

configurable (if lower than a pre-defined threshold).

23

Cabin/class Selection. Ability to Support selection of different

cabin classes on individual segments and different brands on

the outbound and return leg.

24 Partners/codeshare flights. Ability to offer

partners/codeshare flights.

25

Fare conditions detailed Display. Ability to display fare

conditions details /fare families attributes.

In case of fare combination, only the most restrictive

condition should be displayed.

26

Fare Conditions Summary display. Ability to display in

multiple languages (FR/EN/AR are minimum requirements):

- A user-friendly summary of fare families and fare

conditions,

- A user-friendly summary of fare families’ comparison.

27

Fees. Ability to configure booking fees, payment fees, services

fees based on business rules (e.g. POS, per PNR, per itinerary,

FOP...).

28 Taxes Breakdown. Ability to configure and display full

taxes/charges/fees breakdown (e.g. depending on POC).

29 Currencies. Ability to price in multiple currencies.

30

Dynamic conversion display. Automatic notification for

converted Fares before payment (when the displayed fare

currency and payment currency are different).

AOIR : N° 001/DC/2016 Page 70

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

31 Ancillary services. Ability to support both cross-channels and

ecommerce specific ancillaries’ services.

32

Flight Summary. Should be displayed during all booking steps,

it should be possible from any booking steps to modify

selected entries. Flight summary include (Partial list):

- Travelers details,

- Itinerary summary,

- Baggage allowance,

- Price summary including all paid services details (Tickets,

chargeable services, ancillaries and cross-sells), all taxes,

charges and applicable fees,

- Fare conditions link.

33

Passenger Information. Ability to :

- Manage/configure travel requirements information (e.g.

APIS based on departure/destination),

- Support specific PTC information (eg. Extra contact Info for

UM).

34 Seat Selection. Ability to select seat using seatmap (including

a legend) from booking/booking management.

35 Seatmap Restriction. Ability to restrict high value seats display

to specific customers based on business rules.

36

Ancillary services. Ability to :

- Offer air and non-air (standalone) services

- Offer chargeable and non-chargeable ancillaries and issue

EMD.

- Support multiple touch points (configurable e.g.

Standalone, booking, online check-in ...).

- Provide a shopping cart with all associated taxes and fees

shown

- Include/exclude products

37

Cross-sell. Ability to offer seamless points of integration

(homepage, on booking flow, manage my booking) for

example Hotel, car rental and insurance services.

38 Services time limit control. Ability to manage time limit to

access/order services (e.g. Meals 24H before departure).

AOIR : N° 001/DC/2016 Page 71

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

39

Profile. Ability for the passenger to create and have secure

access to their profile.

Profile should include, but not limited to their name, frequent

flyer information, contact, address, special service

information, current reservations, passport or other

identification.

40

Frequent Flyer Login. Ability to log with FF number. The

profile should be automatically loaded and used for booking

or next transactions.

41

Payment Gateway Interface. Should integrate all payments

methods currently used :

- Visa, MasterCard (OGONE Payment Gateway ),

- CIB card (local payment method with SATIM payment

gateway).

42

Payment. Ability to integrate all major payments methods

widely used :

- Credit Card : Amex, DinersClub …,

- E-banking: Sofort , Giropay…,

- E-wallet : PayPal …

43 FOP. Ability to support multiple FOP.

44 Omni channel Payment Solution. Should integrate all

payments methods for web, mobile web version App.

45

Payment. Ability to :

- Provide a fully integrated payment solution to the

booking flow and to all paid services,

- Configure payment according to business rules (e.g.

Payment page/messages customization, POS/POC

configuration, multi languages support…),

- Process payment transactions,

- Send customizable email confirmations,

- Deliver a full visibility of transactions and comprehensive

reporting/ Fraud analytics reports.

46

Ticketing issuance failure when successful payment. Ability to

manage Ticketing issuance failure when successful payment,

by server (IBE) to server (payment gateway) solution.

AOIR : N° 001/DC/2016 Page 72

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

47

Book and hold option. Ability to support book and hold

option: it must be possible for users to book their trip online,

comeback later to pay and continue the process Online, on

mobile and/or ATO/CTO.

- Fares control for delayed payments should be done

according to airline rules (fare expiry controls).

- Ability to configure cancellation rules (E.g. Hold duration

TTL, reminder e-mails...).

48 Online invoices. Ability to issue online invoices.

49

Promotional/corporate Codes/offers.

Ability to create and manage promotional offers based on

business rules including but not limited to :

- Application rules (Net fare, PTC, sales dates/time,

passenger number, cabins),

- Sales country, password use,

- Fixed amount/rate,

- Itinerary option restrictions (OW/RT/stopover/Multi

destinations),

- Travel dates/flights/days,

- Payment modes restriction (e.g. discount for the uses of a

specific payment mode).

50

Manage my booking. Ability for the customer to change their

booking. This includes, adding segments, managing passenger

details such as special service requests, adding passport

information, frequent traveler data, and exchanges.

51

Manage my booking. Ability to retrieve Booking using:

- Name / Booking Reference,

- Name / ETKT.

52

Online changes. Ability to support:

- Re-pricing &Reissue or refund,

- Compute upgrade fees with payment collection,

- Advanced shopping display.

AOIR : N° 001/DC/2016 Page 73

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

53

Emails. Ability to:

- Support Reminder emails, confirmation emails…,

- Send/schedule emails, action, time and event triggers

must be considered,

- Customize emails using pics/logos/ links. The content will

be defined,

- Support additional information,

- Attach documents in emails (e.g. fare conditions, ETKTs...),

- Support multiple languages, at least FR, EN, AR.

54

IBE generated documents (e.g. ETKTs, e-boarding pass,

EMD…). Ability to:

- Customize documents content,

- Support standard format (e.g. PDF)

- Support multiple languages

55 Multiple languages. Ability to support multiple languages in

all IBE interfaces (French, English and Arabic….).

56 Flight Status. Ability to provide flight status through IBE

/Mobile web /Mobile application.

57 Mobile WEB/APP. Ability to provide an

optimized/customizable user interface.

58

Mobile WEB/APP. Ability to provide (including but not

limited):

- Optimized search including calendar view,

- Upsells facilities with fare families support,

- Booking management Interface,

- Special services request,

- Book and purchase air and non-air ancillaries/ 3rd parties

cross sell,

- Check-in/ e-boarding facilities,

- Frequent Flyer Program integration,

- Payment platform compliance,

- Timetable, route map and flights status facilities,

- Voluntary changes (automatic exchange/Refund),

- Send confirmation including booking confirmation, Etkt

receipt/Mobile E-boarding pass…,

- Provide a mobile boarding pass, to be displayed on a

mobile phone/device,

- Support multiple languages,

- Irregularity schedule notifications.

AOIR : N° 001/DC/2016 Page 74

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

59

Mobile App. Ability to provide an IOS and Android Application

with similar services as the mobile/desktop version :

- Update , maintenance and management is provider

responsibility,

- Ability to provide hosting on Google Play and AppStore on

behalf of AIR ALGERIE,

- Ensure maintenance and upgrades according to technology

evolution.

60

Award Shopping. Ability to provide Award shopping and

redemption facilities.

Ability to combine multiple FOP (e.g. combination of miles and

cash for award tickets).

61 Upgrade Award. Ability to provide automatic upgrade award.

62

Reporting. Ability to provide reporting for:

- Usage of promotional/corporate code,

- Cross-sells and ancillary services.

63

Statistics tool. Ability to provide an advanced Statistics tool

related to IBE traffic (e.g.: booking stats, revenue stats, refund

and exchange stats, OLCI, Number of page views...),

exceptions and error logs are also required.

- Deliver a comprehensive reporting for all channels

(WEB/Mobile)

- Export Data facilities to common/ standard formats are

required (e.g.: xlsx, CSV…).

64

Web Analytics Tools: Ability to provide fully integrated and

advanced analytic tools to track and report users behavior,

online campaigns, conversions, goals and all related traffic, E-

commerce module, sales activity and transactions tracking is

also required, a flexible, configurable interface must be

provided to view/export/edit personalized reports/ statistics.

AOIR : N° 001/DC/2016 Page 75

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

65

Online check-in. Ability to provide (including but not limited

to) :

- Seat selection,

- Send check-in confirmation,

- Enable/disable e-boarding pass issuance/delivery.

Configuration must be done autonomously using admin

interface,

- Online Check-in/boarding Controls according to

configurable parameters (e.g. PTC, Fare, APIS collection...),

- Configurable Check-in open/close time (e.g. for

international/domestic flights),

- Through check-in,

- Online check-in / Through check-in for codeshare flights.

66

B2B. Ability to manage corporate customers across :

- Online booking,

- Corporate fares application,

- Corporate loyalty program, reward benefit,

- Promotional offers,

- Notifications for special offers,

- Reporting features.

67

Irregularity Management. Ability to enable online reissue/

free re-accommodations / chargeable upsells based on

Involuntary rules.

Ability to provide notifications.

3. 10. Système de Gestion de fidélisation et expérience client (Loyalty Management System &

Customer experience)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

Loyalty Management

1 Integration. Must be Integrated with the PSS core.

2 Revenue Accounting Data. Ability to process revenue

accounting data.

3

Membership card number. Ability to :

- Contain at least 11 digits with a check digit,

- Define number range for each enrolment channel, by city

codes, territory etc…

AOIR : N° 001/DC/2016 Page 76

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

4

Access Administration and user profile. Ability to define user

profiles according to their roles and attribute permissions to

access accordingly.

Ability to provide restricted access for each profile.

5

Enrolment. Ability to Enroll through multiple channels:

Internet (web, mobile), Reservation system, DCS, upload

batch, online system.

6

Profile management. Ability to:

- Synchronize member profiles with the PSS (Reservation,

DCS and IBE),

- Update Personal Information through different channels,

- Store multiple addresses (Home, work), e-mails and phone

numbers for each member, and highlight the member's

preferred contact information,

- Add Passport details,

- Link between Family members, add family details,

- Select Preferences (meals, seating, demographics, hobbies,

lifestyle etc.),

- Detect possible duplicate accounts based on name check,

date of birth, Email address etc…,

- Merge/demerge accounts,

- Support the definition and transition (automated &

manual) of member status codes in accordance with

defined transition rules (e.g. Active, Inactive, Merged, etc.).

7

Membership management. Ability to :

- Provide a complete view of member information, contacts,

last transactions, tier miles/segments summary,

- Support multiple tier/sub-tiers levels,

- Print Membership card with encoding according to defined

template,

- Restrict the number of free card printing, from x number

the card should be printed against fee payment,

- Provide Membership cards history,

- Manage mileage expiry,

- Manage the Parent-Guardian and Minor details,

- Manage the Family Members,

- Allow Transfer of miles,

- Setup, generate and deliver E-Statement via email

automatically or manually. The statement delivery can be

configured according to defined frequency, tier level,

member status.

AOIR : N° 001/DC/2016 Page 77

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

8

Sub Programs. Ability to support the creation and

management of multiple frequent flyer sub-programs on the

same customer base (e.g. Family Programs, VIP Programs, and

Guest Programs).

9

Tier management. Ability to:

- Manage automatically tier change according to defined

rules based on both tier miles and segments,

- Set up a specific rules to define tier and segment miles,

- Change tier using Manual Override,

- Upgrade based on calendar year and rolling tier rule,

- Support both tier miles and tier segments,

- Retain/downgrade tiers manually,

- Provide second chance (grace period) for retain tiers.

10

Fulfillment. Ability to provide data to fulfillment house and

reverse feedback from fulfillment house for returned and

undelivered mails.

11

Redemption. Ability to:

- Validate account balances for redemption and perform the

redeeming miles from the member's account,

- Support multiple type of rewards: air (Tickets, Upgrades and

excess Luggage etc.) and non-air (Hotel, car rent etc.),

- Support both automatic and manual Redemptions,

- Support Vouchers, gifts, Partners redemption,

- Process in real-time through the reservations system,

- Define reward pricing in both miles and cash options,

- Allow online redemption via web and mobile,

- Setup Redemption discount depending on sectors/flight

number range,

- Restrict member redemptions to a defined list of

beneficiaries (defined by the member),

- Redeem miles from a defined corporate account for

corporate employees registered in the FFP or restricted list

of defined corporate beneficiaries,

- Define reward cancellations fees (fixed fee or percentage of

the total reward amount).

AOIR : N° 001/DC/2016 Page 78

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

12

Communication. Ability to :

- Deliver notifications through multiple channels (e-mail,

Web, SMS),

- Set up notifications for the members based on tier change,

enrolment, accrual activity, redemption activity,

- Allow delivery channel selection by the member,

- Provide a complete communication history,

- Support multiple languages (FR, EN, AR etc.)

- Customize templates communication with different format

(Html, Txt),

13

Partnership management. Ability to:

- Support Airline and Non-Air partnerships,

- Maintains partner contracts and mileage/currency exchange

rates,

- Provide User friendly interface to define rules for partner

accruals and redemptions,

- Generate vouchers for partner redemptions,

- Support automated data exchange with partners,

- Provide Flexible user defined formats for data exchange

(Excel, Txt etc.),

- Ensure Fraud prevention,

- Provide automated billing,

- Support specific codeshare rules for partner accrual (i.e.

operating vs. marketed carrier),

14

Campaigns. Ability to :

- Setup, configure and manage promotions through campaign

management engine,

- Support accrual and redemption promotional campaigns,

- Allow both targeted and generic campaigns using any

parameter in customer profile,

- Use multiple interfaces to register for campaigns,

- Provide campaign performance monitoring.

15

Accrual processing. Ability to

- Process accrual based on Batch or Airline PSS data on real

time,

- Accrue miles according to: booking class, flown class,

segment, O&D, flight number, revenue/non-revenue

segment etc…

AOIR : N° 001/DC/2016 Page 79

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

16

PNR data. Ability to:

- Store and view booked and flown data,

- Provide Reservation and Check-in Information,

- Submit for Retro accrual.

17

Customer Care. Ability to :

- Support complete log of customer contacts,

- Provide multiple detailed levels classification of each

contact,

- Capture other involved parties,

- Support third parties,

- Support document imaging, individual and batch upload,

- Special handle of baggage loss,

- Facilitate detail investigation of each complaint using PNR

and Check-In repositories,

- Support simple workflow to assign tasks to different teams

or individuals,

- Record level security to prevent unauthorized data access

and update,

- Seamlessly link to Member profiles,

- Maintain complete compensation profile (payment, cost

center authorization, form of payment, different currencies

etc.),

- Allow Miles credit or enrolment in Loyalty program as

compensation,

- Provide standard action list for similar cases based on

category,

- Enable proactive actions in case of flight disruption.

18

Reports. Ability to provide:

- Pre-defined reports,

- Customized reports,

- Dashboards,

- Exportation to standard formats (HTML, EXCEL, PDF…)

- Error reports,

- Fraud management reports.

AOIR : N° 001/DC/2016 Page 80

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

19

Loyalty Website. Ability to:

- Provide a dedicated Loyalty member website with the

possibility to browse transactions and profile information,

- Allowing members to enroll, view and update profiles, see

past activities, submit retro claims, register to campaigns

etc. through loyalty website,

- Check for valid email Address at the enrolment. Enrolment

cannot be completed before Email address Validation,

- Allow members to login with their loyalty credentials (i.e.

alias, frequent flyer number, email, pin number),

- Reset or retrieve password in a secure manner,

- Set up a maximum number of incorrect login attempts a

user can make before being locked out of the system,

- View the membership card and request its printing,

- View and print the account statements,

- Allow members to submit a contact form (i.e. query,

complaint, request),

- Integrate with any 3rd party Mobile App,

- Allow members to view future transactions and future miles

earned according to booking.

20 Corporate. Ability to Include Corporate Module.

21 Alliance operations. Ability to support Alliance operations.

22 Lounge access. Ability to Include lounge module.

23

Calculate value. Ability to calculate the member value

(Revenue, Importance, High Tier etc.) and provide ranking

according to revenue generated.

AOIR : N° 001/DC/2016 Page 81

3. 11. Intelligence économique (Business Intelligence)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

Business Intelligence

1

Ability to provide (including but not limited) :

- Intuitive analytics and visually appealing,

- Web-based system management tools,

- Daily, weekly, monthly and yearly reports, dashboards and

statistics,

- Create reports with user’s defined parameters,

- Export Data, reports with different format (text, Excel, word

document, PDF, ZIP…).

2

Ability to provide Dashboards executives for an overview of :

- Commercial performances (by web sells and by point of

sale) data comparisons,

- Competitors’ capacity, frequency and fares market share,

Opportunities (Codeshare, interlining, alliances, new

routes…).

3. 12. Système de Gestion des irrégularités (Disruption Management System)

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

Disruption Management System

1 Integration. Ability to interface with the whole PSS

components.

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

flights operations.

3

Passengers Re-book. Ability to re-book automatically (ETKT,

EMD, SSRs, ancillaries) passengers according to the available

travel alternatives.

4 Passengers Re-book. Ability to re-book automatically

passengers on connecting flights.

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

automatically.

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

AOIR : N° 001/DC/2016 Page 82

Item Functional Requirement Compliance

Y/N/P/F

Core or

Optional Observation

7 Passenger re-accommodation. Ability to re-accommodate

automatically passengers from Inventory and DCS.

8 Baggage handling. Ability to handle passengers’ baggage (re-

tag, messages regeneration).

9 Customer Prioritization. Ability to handle priority customer

based on value (FFP, fares paid, class of travel...).

10 Disruption costs. Ability to provide cost effective solution to

reduce disruption costs.

11 Passengers Compensation. Ability to calculate compensations.

12 Queue PNRs. Ability to queue PNRs on defined queues

13 Notification. Ability to notify by APPS, e-mail and SMS

passengers affected by the disruption.

14 Reporting. Ability to provide detailed reports

AOIR : N° 001/DC/2016 Page 83

4. AUTRES EXIGENCES

4. 1. Plan et stratégie de Migration (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. Plan d’implémentation du PSS (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. Formation (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. Rapports du projet (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. Documentation finale (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: FORMULAIRES / MODÈLES DE DOCUMENTS

MODELE DE LETTRE DE SOUMISSION (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 US Dollars currency in words] [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

BORDEREAU DES PRIX

Item Descrition Quantité Prix

unitaire

Prix

HT/USD

One fee Migration &

implémentation 01

Monthly fees Usage, Support

& Maintenance

Less than 4 Million PB ………………. Per PB

Between 4 and 6 Million PB ………………. Per PB

Between 6 and 8 Million PB ………………. Per PB

More than 8 Million ………………. Per PB

Evaluation Annuelle Nombe de Passgers Estimé Prix HT

Total HT sur 12 Mois - Année

2017

5 883 638 Borded Passengers

Total HT sur 12 Mois - Année

2018

6 177 820 Borded Passengers

Total HT sur 12 Mois - Année

2019

6 486 711 Borded Passengers

Total HT sur 12 Mois - Année

2020

6 811 047 Borded Passengers

Total HT sur 12 Mois - Année

2021

7 151 599 Borded Passengers

Total TTC (USD)

Tous les autres coûts doivent être pris en charge par le fournisseur.

AOIR : N° 001/DC/2016 Page 87

DÉCLARATION SUR L’HONNEUR (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

LES RÈGLES D’ÉTHIQUE (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

GLOSSAIRE

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

AOIR : N° 001/DC/2016 Page 91

Terms Description

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

IBE Internet Booking Engine

ICH IATA Clearing House

IDM Industry Discount Message

IDS Information Display System

IET Interline Electronic Ticket

IFM Interline Fall-back Message

IFS In Flight Service

INF INFant

INFARE / QL2 Provider of competitive fare pricing information, seat availability and promotional data from

companies.

INNOVATA Source of Airline Schedule Data (Schedule publisher)

ITB Instructions to Bidders

LDM LoaD Message

LDP LoaD Planning

LDW Landing Weight

LPM Load Planning Message

MAC Mean Aerodynamic Chord

MACS Mercator Airport Control System

MARS Mercator Airlines Reservation System

MCT Minimum Connecting Time

MERCATOR Airlines systems providers

MPM Maximum Permitted Mileage

MRZ Machine Readable Zone

MSR Magnetic Stripe Reader

NAVS Numeric Availability sent Messages

NOTOC Special Load NOtification TO Captain

NUC Neutral Unit Calculation

O&D Origin & Destination

OAG Official Airlines Guide (Schedule publisher)

OAL Other Air Lines

OCR Optical Character Recognition

OGONE Payment Gateway provider

OJ Open Jaw

OLCI On Line Check-In

OSI Other Services Information

OW One Way

PADIS Passenger and Airport Data Interchange

PAX Passengers

PB Passenger Boarded

PCI-DSS Payment Card Industry - Data Security Standard

PECTAB Parametric Table

PFC Passenger Facility Charges

PFS Passenger Final Sales

PIL Passenger Information List

PNL Passenger Name List

PNR Passenger Name Record

POC Point Of Commencement

POS Point Of Sales

AOIR : N° 001/DC/2016 Page 92

Terms Description

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

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