Embed Size (px)
Citation preview
Ref:GM(ICM)/CAC/CONT/GDS/20
INVITION TO BID
Global Distribution Systems (GDS) Partnership
Pakistan International Airlines, the National Flag Carrier, invites Bids, on Single Stage Two envelopes basis from national and international companies to form industry alliances and partnerships with PIA's
loyalty program for Global Distribution Systems (GDS) Partnership. Prospective firms/companies are required to submit Tender Fee of Rs. 3000 (non-refundable) in shape of a Pay Order (in the name of PIACL) along with the Proposal. (For Local Bidders Only). The Bids, prepared in accordance with the instructions in the RFP documents, must reach at General Manager Inventory & Contract Management, Supply Chain Management, PIA Head Office, Karachi latest by 02-09-2020 till 1030Hrs (PST). The Bids will be opened the same day at 11:00 Hrs (PST).
Muhammad Asim khan
General Manager Inventory & Contract Management Supply Chain Management PIA Head Office, Karachi.
Ph: 021 9904 3081, 9904 4216 Email: [email protected]
1
Invitation to
Bid
( ITB )
Global Distribution Systems
(GDS) Partnership
Pakistan International Airlines Corporation
Limited PIACL)
2
ITB for Selection Global Distribution System Partner
Introduction ....................................................................................................................................................... 3
Airline Primary Information ........................................................................................................................... 3
Facts and Figures ........................................................................................................................................... 3
Business Model .............................................................................................................................................. 5
E-commerce current situation ....................................................................................................................... 5
Code Share Partners .......................................................................................................................................... 5
Objectives .......................................................................................................................................................... 6
Scope of Work ................................................................................................................................................... 7
Feature Requirements Matrix ....................................................................................................................... 7
Integration of Systems already available with PIACL .................................................................................... 7
Training .......................................................................................................................................................... 8
Responding to this ITB ....................................................................................................................................... 8
Service PROVIDER ’s responsibility ................................................................................................................ 8
PIACL’s obligations to the Bidders ................................................................................................................. 8
Elements of Bidders Response ...................................................................................................................... 9
Bidder Company background .................................................................................................................... 9
Platform Overview ..................................................................................................................................... 9
Functionality .............................................................................................................................................. 9
Time-line .................................................................................................................................................... 9
Staffing Needs ............................................................................................................................................ 9
Additional hardware, solution, software .................................................................................................... 9
Training & Documentation ........................................................................................................................ 9
Initial system loading ............................................................................................................................... 10
Testing Plan .............................................................................................................................................. 10
Implementation ....................................................................................................................................... 10
Reports ..................................................................................................................................................... 10
Hardware, software and network connectivity requirements ................................................................ 11
System integration ................................................................................................................................... 11
Business Continuity and Disaster Recovery ............................................................................................. 11
Pricing Proposal ..................................................................................................................................... 112
Schedule of Events ........................................................................................................................................... 13
Selection Criteria ............................................................................................................................................. 14
Mandatory Requirements ........................................................................................................................... 14
Evaluation of Bid Selection Criteria ............................................................................................................. 15
3
Technical Proposal’s Evaluation .................................................................................................................. 14
Financial Proposal’s Evaluation ................................................................................................................... 15
Format for Technical Bid .............................................................................................................................. 16
Technical Bid Format ............................................................................................................................... 17
Financial Bid Format .................................................................................................................................... 19
Pricing for proposed GDS Platform – Usage Fees ...................................................................................... 19
INTEGRITY PACT ............................................................................................................................................... 21
4
PIACL Profile
Introduction Pakistan International Airlines Company Limited (PIACL) is the flag carrier of Pakistan and is in
the business of air transportation of passengers and cargo and related activities. PIACL's primary
focus is to serve the Pakistani community at large and travelers across the globe in general. The
airline has its offices and stations located across the world.
PIACL has recently migrated to new Passenger Service System (PSS) from HITIT Computer
Services, and as part of strategizing its position in the global markets, and to opt for the latest
technological platforms, PIACL is now looking to further enhance its reach through participation
in the major Global Distribution Systems (GDS)in addition to its existing GDS partners. The
objectives are to acquire managed services with high capabilities of multi-channel dynamic sales
and distributions for increase in selling base and enhancement of revenues. Interested parties
should be established Global Distribution System having large presence around the globe and be
able to integrate with our PSS for timetable (schedule, Capacity, Inventory, availability & Price
and has the ability to build network auxiliaries including Hotel, Visa, Car Rental, and Insurance
etc.
Airline Primary Information Airline Name: Pakistan International Airlines
Corporation Limited
IATA Airline Code: PK
IATA Accounting Code: 0000000044
Headquarters City: Karachi, Pakistan
Years in operation: Since 1956
Ownership structure:
Majority owned by the Government of
Pakistan (91.7 %), while public/other
shares 4.4 % and PIACL Employees
Empower Trust shares 3.9 %.
Website address: www.piac.com.pk
Facts and Figures Aircraft Fleet 4 / ATR 42-500
5 / ATR 72-500
11 /Airbus A320-200
5
6 / Boeing 777-200ER
2 / Boeing 777-200LR
4 / Boeing 777-300ER
Daily Flights
(scheduled)
117 (Average)
Destinations
Served
16 Online Domestic Stations – Bahawalpur, Chitral, Faisalabad,
Gilgit, Gwadar, , Islamabad, Karachi, Lahore, Multan, Peshawar,
Quetta, Rahim Yar Khan, Sialkot, Skardu, Sukkur, and Turbat.
24 Online International Stations - Beijing, Kabul, Kuala
Lumpur, Tokyo, Birmingham, Copenhagen, London, Manchester,
Milan, Oslo, Paris, Abu Dhabi, Al Ain, Dammam, Doha, Dubai,
Jeddah, Kuwait, Madinah, Muscat, Riyadh, Sharjah, Barcelona,
and Toronto.
PK Markets Pakistan, Regional, Saudia Arabia, Gulf, UK & Europe, and US &
Canada.
Actual Passengers
Boarded
Segments (PBS)
2019 5.290 Million
2018
2017
5.202 Million
5.341 Million
2016 5.781 Million
2015 5.638 Million
2014 4.202 Million
2013 4.449 Million
2012 5.236 Million
2011 5.953 Million
2010 5.538 Million
Projected
Passengers
Boarded
Segments (PBS)
2020 6.72 Millions
2021 7.84 Millions
2022 8.67 Millions
2023
9.37 Millions
6
Business Model Model Number
Direct Call Center 1
Direct Website 1
CTO/ATO (Active only) 67
Global Distribution Systems (GDS) 7
Direct Internet Booking Engine (IBE) 1
Direct General Sales Agents (GSA) including Cargo 15
E-commerce current situation IBE Features Description
IBE Languages EN
Search Schedule/Price/Flexible search (calendar fares)
Payment International Payments (VISA / MasterCard), WorldPay
Merchant Services
Services Seat / Meals Selection, Auto Exchange and Refund, Multicity
Selection, Interline Selling, online Check-In
Frequent flyer Program Registration, Flight History, Miles Balance, Status
Promotional offers Discounts
Code Share Partners
Airline
Etihad Airways - EY
China Southern Airline- CN
Turkish Airline- TK
7
Global Distribution System Partnership
Objectives PIACL aims to modernize and enhance its sales and distribution through partnership of multiple
Global Distribution System (GDS)platforms with enhanced, modern and agile functionalities.
The selected GDS platforms must provide competitive advantage to PIACL, not only in the
short-term by rapidly delivering cost savings and revenue gains, but also in the long-term by
improving our market agility, reach and adapting quickly to our business model. Moreover, it
allows Travel agencies to compare information on timetable (schedule, capacity, Inventory,
Availability, price, and book tickets on a large a varied no of travel service providers worldwide.
PIACL‟s objectives for the new GDS platform and Provider‟s capabilities are:
• To opt for a next-generation global sales and distribution platforms built on the latest
Services Oriented Architecture (SOA) and agile technologies, aligned with the needs of
the modern era of smart devices.
• Selecting GDS partners that has the capacity and is capable to provide managed services
for Global Distribution System (GDS) platform.
• Selecting partners, highly conversant with IATA, ICAO, A4A, ISO, EDIFACT, AIRIMP,
SSIM and other Airline related standards.
• Align PIACL‟s sales & distribution to the industry‟s latest standards and IATA initiatives
like New Distribution Capability (NDC), One Order, One Identity & Fast Travel etc.
• Capable of delivering the next generation of IT distribution solutions and aligned with
latest trends in the airline industry including Ticketing and Electronic Miscellaneous
Documents (EMD) (both standalone and associated).
• Should allow airline to be more creative, and precise, in creating personalized packages,
target segmentations and deliver offers and services through multiple channels.
• Should allow to package/ bundle and ancillary services like Extra Baggage, Leg space,
selected seats, etc. and auxiliary services like car rentals, hotel booking, insurances, Visa
services etc. in addition to airline tickets.
• Support a variety of forms of payment or modes and protect customers‟ privacy concerns
and increase revenue from new/ repeat customers.
• Deep customer intimacy and social network integration
• Integrated near real-time business intelligence and the potential for „Big Data‟ integration
and exploitation, Operational Data Store, Analytics and Insights and Predictive Analytics.
• APIs (web-services) to support in-house developments, integration and/or third party
solutions such as metasearch or direct agency connections, tour operator or corporate
distribution or partnership.
8
Scope of Work PIACL is seeking multiple GDS Platforms as a Service model, where the PROVIDER takes on
responsibility for developing, maintaining and delivering the services as defined in this document to
inside and outside users for the PIACL organization. PIACL users include, but are not limited to
passengers booking agents, reservations, travel agents (accredited and non-accredited), General
Sales Agents (GSAs), Virtual Sales Agents and Pakistan Sales Agents (PSAs), tour operators and
corporate customers, contractors, code shares, interlines, and airline partners etc.
However, PIACL reserve the right to revisit the scope following analysis of the responses to the
ITB and include or exclude components.
Feature Requirements Matrix This Bid is issued to invite reputed and experienced suppliers to provide Global Distribution
System (GDS). The system must be able to deliver these Feature Requirements either currently or
prior to an agreed upon future date, as detailed in the Feature Requirements Matrix at the
appendix to this ITB. A soft copy of Technical Bid along with functional requirement matrix is also
needed to be submitted in CD format with Proposal.
Integration of Systems already available with PIACL The providers will have to integrate with the PIACL‟s Passenger Services System, via industry
standard messages such as EDIFACT or APIs, etc. Revenue Accounting Systems and others as
implemented/ acquired by PIACL including the current and to also any future additional related
system.
In addition to the above coverage of the scope of this document, PIACL values reliability and
availability and also the timing of migration and implementation. PIACL wishes to deploy the
system to the best of its abilities and to this end is looking for a Bidder that can both demonstrate
and deploy best practice use of their system to PIACL‟s benefit.
PROVIDERS will be expected to present best practice use of their system/ Services and to deploy
these with PIACL. The focus must be to get the best from the PROVIDER system and to limit
customization and development work outside the necessary interfaces with other systems
necessary for migration.
PIACL wish to deploy the PROVIDER services with a minimum, or no customization and
adaption. The final implementation plan will be mutually agreed between the selected Bidder and
PIACL.
This document and the PROVIDER response to this ITB will form an integral part of the contract
between PIACL and the selected PROVIDERS.
9
Training The PROVIDERS will ensure the necessary training to PAKISTAN INTERNATIONAL
AIRLINES for implementation, administration, configuration, operations and technologies used in
the context of the proposed solution.
The PROVIDERS must detail in its offer the training programs, contents, the durations and the
certification of the trainers.
Responding to this ITB The tendering process that PIACL will follow is described in this section. The selection of a
Bidder will be determined based on the information provided in response to the requirements set
forth in this document. The proposal should also include a functional description of the
proposed GDS components which clearly matches with the functionality and technical
requirements you find in this ITB.
Criteria will be weighted and consideration made on the Total Cost of Ownership (TCO)
including the system functionality, other fee (as specified in the fee structure), technical service,
resources of each Bidder and cost. The selected vendor‟s ability to provide a product and level
of service that will help PIACL with a successful implementation is also part of the selection
process.
PIACL has developed a method to select the appropriate PROVIDERS through tendering process as
regulated by the Public Procurement Regulatory Authority (PPRA) of Govt. of Pakistan.
For the avoidance of doubt all costs associated with the development of the response,
demonstrations and presentations are at the PROVIDERS‟s expense alone. PIACL will bear all of
its own costs associated with this process.
Service PROVIDERS responsibility
All information provided pursuant to this ITB shall be treated in strictest confidence by the bidder.
The submission of a proposal represents that the Bidder has read and understood the tender
documents.
The Bidder shall undertake the preparation of their tender submission at their own expense
including travel to PIA‟s defined location during the tender process if needed.
Upon receiving responses to this ITB, PIACL may ask vendors to perform in-person
demonstrations. The Bidder will be expected to demonstrate that the main elements of the proposed
GDS adequately meet the functional and technical requirements outlined in the ITB.
PIACL’s obligations to the Bidders
PIACL will assist the bidders whenever and wherever possible in determining local conditions and
clarification of the tender documents. Any clarification questions and answers will be circulated
to all vendors.
PIACL reserves the right to accept or reject any proposal either in part or whole without incurring
any liability or inferring any obligation to the Bidder concerned.
10
Elements of Bidders Response Bidder Company background
The following Bidder information is to be provided:
• Name of company
• Head office address
• Primary contact details
• Corporate Profile - include information about your overall business and GDS
products.
• Existing agent network, OTA Meta, and market share details
• Related Past Experience
• Company Financials - evidence of financial stability for the last 3+ years
• At least one (1) customer references indicating the services provided as related to
the services requested in this ITB
• Involvement of third parties - any sub-contractors or assigned vendor(s) shall be
named within the proposal.
Platform Overview
Provide a high-level description of all components of systems and for each and/or any
other system you wish to include in your proposal. Attach additional documentation
as Appendices if needed.
Functionality
Please provide responses to each of the items laid out in Feature Requirements
Matrix using the Excel spreadsheet format provided with the ITB(the Feature
Requirements Matrix).
Vendors shall indicate whether their proposed solution complies or does not comply
with the requirements and submit relevant information in sufficient detail to enable a
good assessment of the product and services offered.
Time-line
The proposal should include a time line and high level milestones for the
implementation, using the date of 10th
September 2020as the starting point.
Staffing Needs
The proposal should specify the PROVIDER‟s team including the required
competencies and knowledge and the capacity for managing project and should also
be capable to provide additional Technical or Functional skilled resources as per
agreed man day rates during the contract period.
Additional hardware, solution, software
The proposal should be able to cater to additional hardware, solution, software
requirements form the PROVIDERS or a third party as and when needed during the
contract period. The terms and condition will be mutually agreed upon at execution.
Training & Documentation
The proposal should describe the time needed for training and the type of training
(e.g. classroom training, on-line training, hands-on training or "train the trainer"
11
approach). The proposal should also contain a recommended practice for training of
new staff and refresher training after cutover.
Describe what documentation is provided before and after the training.
Initial system loading
The proposal should outline the steps for preparing and loading the database: schedules,
inventory, fares, etc. The PROVIDERS must list, for each module, hardware, software
and network detailed recommendations to ensure optimal performances.
The bidder must provide technical support for expected services, containing:
• Contacts (phone numbers, email addresses…) for technical support and incidents
management,
• Onsite/remote interventions when needed,
• 24/7 availability
• English Language
Testing Plan
The PROVIDERS shall perform all operational tests of the GDS implementation. Testing
should particularly focus on the following aspects (not limited to):
• The full functioning of the systems, as per Feature Requirement Matrix.
• The integration of the solution to the existing network,
• Security of the overall system, connectivity and data.
• PIACL and the PROVIDERS will jointly perform validation testing/ UAT (User
Acceptance Test).
Implementation
Information required in this section includes a description of your proposed
implementation milestones and timelines, activities, Bidder and PIACL people
involved in the project, etc., as well as an outline of the training courses provided.
A train-the-trainer approach is preferred.
Reports
The bidder must submit reports at each step of the project describing the following points:
• The intervening plan of both parties, PAKISTAN INTERNATIONAL AIRLINES
and Bidder, specifying profiles, roles and tasks involved in this mission,
• The requirements in terms of resources and information that will set up
PAKISTAN INTERNATIONAL AIRLINES to the project‟s success.
12
Hardware, software and network connectivity requirements
For each system, list hardware, software and network connectivity that PIACL will
need to install for implementation of your proposed GDS Platform. Specify required
software on either servers or workstations.
System integration
Please describe the type of interface / link that Bidder will provide in order for
PIACL‟s systems to interact with your proposed GDS Platform and specify if these
are included as standard or an additional cost item.
Business Continuity and Disaster Recovery
Briefly describe your Business Continuity and Disaster Recovery program and
specify if these measures are included as standard or an additional cost item.
Provide a technical overview of the hardware and software implemented at the main
data center and back-up data center and where the modules proposed to PIACL will
be hosted.
Pricing Proposal
Provide responses in the financial bid format.
The proposal should take into account all the costs for the system, i.e. specify initial
set-up fees, covering costs up to cutover as well as recurring charges covering
operating costs after cutover for a three (3) year contract term. A clear distinction
should be made between fixed pricing and pricing related to passenger booking/
segments volumes to be mentioned in the Financial Bid.
Prices must be quoted in US Dollars (USD).
13
Schedule of Events
Event Date/
Duration
Details
Sign and submit Non-
Disclosure Agreement
At the time of
provision of ITB.
PROVIDERS to submit signed NDA physically or email the scanned image.
GM Inventory & Contracts Management
Address:
Supply chain management
Department, PIACL Head Office, Karachi.
Ph: 021 9904 4216, 99044101,
99043081
Email: [email protected],
PROVIDERS to nominate
representative(s) for attending
the Pre-Bid Meetings and
further Communication.
At least a day
before Pre-Bid
Meeting.
PROVIDERS to email its designated
representatives‟ contact information to:
Pre-Bid Meetings
PIACL may, at its sole
discretion wish to rely on the
PROVIDERS S responses to
ITB.
17-18 August
2020
Submission and Opening of
ITB Response
2nd September 2020 Hard Copy and CD / USB
Evaluation of the Technical
Bids
9th September 2020
Opening of Financial Bid 16th September 2020
Issuance of LOI/ Contract
Award/ Signing of Contract
Uploaded on the PIACL/ PPRA
Website.
14
Selection Criteria Mandatory Requirements
Sr.
No
Criteria Eligibility
(YES/ NO)
Evidence Reference
1 Firm must be an established international GDS network with at
least last 5 years in service and operations.
2 Compliance to all mandatory requirements as mentioned in the
annexed Functional Requirement Matrix.
3 Firm must have IATA New Distribution Capability (NDC)
Certification.
4 Firm must have advanced technology solution to enable online
bookings via Provider‟s powered OTAs and METAs.
5 Firm must have "Electronic Ticketing System PROVIDERS
Agreement" (IATA Resolution No. 854) for all PK Markets.
6 Firm must support of PNR Synchronization from PK Host to
GDS and GDS to PK Host
7
Firm must have safe and secure infrastructure and have trusted
and established security policies in place to assure against data
loss and theft, and strategies in place to deal with business
continuity and data recovery.
8 Firm must have at least one office location in Pakistan.
9 Firm must have sturdy technical infrastructure and has a defined
approach for continuous periodic upgrades.
10 Firm must be Payment Card Industry (PCI)/ DSSand EU‟s GDPR
compliant
11 Firm must have comprehensive interlining capabilities with other
airlines.
12
Goods and Services can only be supplied / sources / routed from
origin” in “eligible” in member countries.
“Eligible” is defined as any country or region that is
allowed to do business in Pakistan by the law of
Government of Pakistan.
Centre “Origin” shall be considered to be the place where
the services are provided.
• Verifiable proof for all the above shall be mandatory. Non-submission may cause disqualification of the bidder
for any further process. All bidders must fill the checklist format compliance of the eligibility criteria above.
• PIACL reserves the right to review, modify or adapt these criteria at its sole discretion.
15
Evaluation of Bid Selection Criteria Total Marks are 200 (Final Total Marks = Technical + Financial). Selection will be made on
the combine weightage of Technical and Financial Proposals. Weightage factor is as under:
Technical Proposal: 60% (Acquired Marks * 0.60)
Financial Proposal: 40% (Acquired Marks * 0.40)
Technical Proposal’s Evaluation Technical Evaluation will be based on Mandatory Requirements and Technical Requirements.
Bidder must comply with all of the Mandatory Requirement. Failure to comply with any of
the Mandatory Requirements item in the Functional Requirement Matrix will automatically
disqualify the bid.
Technical Requirements are based on scoring system and has total marks are 100. Bidder must
acquire 70% of the total marks of the Technical Proposal to qualify for the opening of
Financial Proposal. Less than 70% of the score will result in bid’s disqualification.
Financial Proposal’s Evaluation Financial Proposal‟s marks are 100, and the Financial Proposal should give all relevant price
information and should not contradict the Technical proposal in any manner. All prices should be
quoted in USD only. Prices should be valid for 180 days from the date of submission. All
increases in price will be to vendor‟s account.
Audited reports of last three years will be submitted with Technical Proposal, however, their
marks will be counted during Financial Evaluation of the bids.
16
S. No. Criteria Marks
1 Bidder will require to submit last three years audited reports
(Yes = 10, No = 0)
(Duly verified financial statements or Audited accounts required)
10
2 Financial Strength (Last three (3) year’s Average Gross Revenue)
If equal or greater than USD 500 Million then 20 marks,
if equal or greater than USD 300 but below USD 500 million then 15 marks,
if equal or greater than USD 100 but below USD 300 million then 10 marks,
if less than USD 100.00 million then 0 marks
Note: Revenue of a subsidiary or parent company engaged in same line of
business also qualify.
20
3 Lowest Bid (for each Market – Home/ Rest of the World)
(1st Lowest =70, 2nd Lowest = 40, 3rd Lowest= 20, Rest of Bids = 0.)
70
Total Marks 100
Format for Technical Bid The technical bid is to be submitted as per the Functional Requirement matrix as per provided
appendixes, and a certificate is to be submitted confirming the willingness to integrate all the
existing relevant applications at PIACL.
All claims made by the Tenderer regarding the below mentioned Evaluation criteria must be
backed by verifiable proof of evidence. Tenderers may fill out the following form for self-
evaluation. The Authority competent to evaluate is the purchaser – PIACL.
That the shortlisted bidder shall deposit with PIACL after issuance of LOI before the signing of
the contract an amount 0f 10% of the total contract value as performance guarantee as interest
free security deposit which shall continue to be held by PIACL until three months after expiry of
the contract period and/or termination whichever is earlier. This amount will be refunded after
settlement of all outstanding dues.
17
Technical Bid Format
Requirements with description Max.
Marks
1 Company Age
5 marks for equal or greater than 10 years,
3 marks for equal or greater than 5 years but less than 10 years,
0 marks for less than 5 years
(Certificate of Incorporation or Registration by concerned authorities)
5
2 IATA New Distribution Capability (NDC) Certification
Level 3 or Above Certified = 5 marks
Level 2 Certified = 3 marks
Level 1 Certified = 0 marks
(Provide Copy of the IATA NDC Certificate, If not provided, Not Eligible )
5
3 Market Share in Percentage as per IATA Direct Data Solution (DDS-Year 2018)
Countries Market Share %
Marks
PAKISTAN 5
Asia Pacific (Excl. Pakistan) 5
Kingdom of Saudi Arabia (KSA)
5
EMEA (Excl. KSA, Pakistan, UK & EUROPE)
5
UK&EUROPE 5
US & CANADA 5
Highest Market Share among participants in each of above market= 5 Marks
2nd Highest Market Share among participants in each of above market= 3 Marks
3rd Highest & others among participants in each of above market= 0 Marks
(Attach copy of comparative state of all GDSs as per GDS MIDT)
30
4 No of Airlines available on the GDS Network – potential for Interlines
1stHighest no of Airline participants in the network = 10 Marks
2nd Highest no of Airline participants in the network = 5 Marks
3rd Highest no of Airline participants in the network = 0 Marks
10
18
(Provide the list of Airlines participants in the network)
5 Number of Active Travel Agents on the Bidders Network Globally
Equal or greater than 100,000 = 10 marks
Equal or greater than 50,000 but less than 100,000 Agents= 5 marks
Less than 50,000 Agents = 0 marks
(Provide affidavit of the number of active Agents)
10
6 Number of Active Travel Agents on the Bidders Network in Pakistan
Equal or greater than 1,000 Agents = 10 marks
Equal or greater than 500 but less than 1,000 = 5 marks
Less than 500 Agents = 0 marks
(Provide affidavit of the number of active Agents)
10
7 Number of affiliated OTAs or META Search Engines
Equal or Above 20 Agents = 10 marks
Equal or greater than 10 but less than 20 = 5 marks
Less than 10 Agents = 0 marks
(Provide the list of affiliated active OTAs & META Search Engines)
10
8 Presence of Local Representative/ office in Pakistan
(Copy of Tenancy documents/ agreement to be provided), if distributor appointed, then
company can mention on their behalf.
5
9 Bidder to give Presentations and Platform Demonstrations based on the Feature
Requirement Matrix, PIACL team may also visit to the Bidders offices, its client’s offices.
Marks will be given at the sole discretion of PIACL’s evaluation team.
15
TOTAL Marks 100
19
Financial Bid Format To assist PIACL‟s evaluation, vendors are requested to include their complete pricing in the
table format below. If additional space is needed, please either add rows or include explanatory
notes at the foot of each table. (Prices must be quoted in US Dollars - USD).
In addition, please clarify prices of all systems, implementation and integration services if
required. The pricing model must include the below mentioned activities, such as:
• Implementation, project management and cutover support
• Hosting, storage and Disaster Recovery
• Training, documentation and manuals
• Help desk ad Ongoing support
• Service Level Agreements (SLA)
Pricing for proposed GDS Platform – Usage Fees
Pricing Component / Activity Price in USD Remarks
Net Booking Fee per Segment (USD)
Booking Volume Threshold Per
Contract Year Home Market Remarks
0 to 0.55 Million
Net Booking fee includes Active,
Passive or Group Booking, etc.
No Other Charges including
cancellations & ticketing will be
applicable.
0.55 to 1.1 Million
1.1 Million
Booking Volume Threshold Per
Contract Year Rest of the World Markets
0 to 0.25 Million
0.25 to 0.5 Million
0.5 to 0.75 Million
0.75 to 1.1 Million
1.1 Million
EMD
Any other Service Optional - to be defined in
Schedule 5
Important Note:#
a. Home Markets are defined as Domestic to Domestic & Domestic to International
b. Rest of the World Segments are defined as International to Domestic & International to
International
20
c. For the purpose of financial evaluations only, and to calculate the Total Cost of Ownership,
upper limits for all thresholds will multiplied with the home and rest of markets rates,
however for last threshold 2 Million will be considered (where Greater than 1.1 is
mentioned).
d. PIACL reserves the right to select multiple GDS services providers, without any exclusivity.
e. Preferences will be given to the bidder providing Volume Credit on the any other Service
thresholds.
f. However, the Customer may opt additional optional services on agreed rates.
g. PIACL will not be responsible for any charges payable to any travel services providers like
OTAs, Search Engines or travel service partners etc. directly.
h. Bidders must explicitly mention all possible charges in the financial proposal and no
payments will be made on charges other than mentioned in the bid and agreed by PIACL
during the entire contract period.
i. It is explicitly explained that Bidder will not charge for the upgrades, version change, or even
feature or product change during the contract period.
21
INTEGRITY PACT
(To be submitted on Company’s Letterhead)
Declaration of Fees, Commissions and Brokerage Etc. Payable by the Suppliers, Vendors, Distributors,
Manufacturers, Contractor & Service PROVIDERS of Goods, Services &
Works___________________________________________ the Seller / Supplier / Contractor hereby
declares its intention not to obtain the procurement of any Contract, right, interest, privilege or other
obligation or benefit from Government of Pakistan or any administrative sub-division or agency thereof
or any other entity owned or controlled by it (GOP) through any corrupt business practice.
Without limiting the generality of the forgoing the Seller / Supplier / Contractor represents and warrants
that it has fully declared the brokerage, commission, fees etc., paid or payable to anyone and not given
or agreed to give and shall not give or agree to give to anyone within or outside Pakistan either directly
or indirectly through any natural or juridical person, including its affiliate, agent, associate, broker,
consultant, director, promoter, shareholder sponsor or subsidiary, any commission, gratification, bribe,
finder’s fee or kickback whether described as consultation fee or otherwise, with the object of obtaining
or including the procurement of a contract, right, interest, privilege or other obligation or benefit in
whatsoever form from Government of Pakistan, except that which has been expressly declared pursuant
hereto.
The Seller / Supplier / Contractor certifies that it has made and will make full disclosure of all
agreements and arrangements with all persons in respect of or related to the transaction with
Government of Pakistan and has not taken any action or will not take any action to circumvent the
above declaration, representation or warranty.
The Seller / Supplier / Contractor accepts full responsibility and strict liability for making any false
declaration, not making full disclosure, misrepresenting facts or taking any action likely to defeat the
purpose of this declaration, representation and warranty. It agrees that any contract, right, interest,
privilege or other obligation or benefit obtained or procured as aforesaid shall without prejudice to any
other right and remedies available to Government of Pakistan under any law, contract or other
instrument, be void-able at the option of Government of Pakistan.
Notwithstanding any rights and remedies exercised by Government of Pakistan in this regard, the Seller
/ Supplier / Contractor agrees to indemnify Government of Pakistan for any loss or damage incurred by
it on account of its corrupt business practices and further pay compensation to Government of Pakistan
in any amount equivalent to ten time the sum of any commission, gratification, brief, finder’s fee or
kickback given by the Seller / Supplier / Contractor as aforesaid for the purpose of obtaining or inducing
the procurement of any contract, right, interest, privilege or other obligation or benefit in whatsoever
from Government of Pakistan.
22
(To be submitted on Stamp Paper)
GM Inventory & Contracts Management
Supply Chain Management Department
Pakistan International Airlines, Karachi.
Subject: Undertaking to Execute the Contract
Dear Sir,
1. We/I, the undersigned bidder do hereby confirm, agree and undertake to do following in
the event our / my tender for supply/Services of
________________________________________________________________________
toPIACL is approved and accepted:
2. That we / I will into and execute the formal contract, a copy of which has been supplied
to us / me, receipt whereof is hereby acknowledge and which has been studied and
understood by me / us without any change, amendment, revision or addition thereto,
within a period of seven days when required by PIACL to do so.
3. That all expense in connection with the preparation and execution of the contract
including stamp duty will be borne by us / me.
4. That we / I shall deposit with PIACL before the signing of the contract an amount 0f 10%
of the total contract value as performance guarantee as interest free security deposit which
shall continue to be held by PIACL until three months after expiry of the contract period
and/or termination whichever is earlier. This amount will be refunded after settlement of
all outstanding dues.
5. That in event of our / my failure to execute the formal contract within the period ofseven
days specified by PIACL the Earnest money held by PIACL, shall be fortified and we / I
shall not question the same.
Bidder‟s Signature_________________________
Name in full _______________________________
Designation ________________________________
Address ________________________________
________________________________
Phone / Fax # _______________________________
CNIC _______________________________
Seal _______________________________
Date _______________________________
23
Draft Agreement
GLOBAL DISTRIBUTION SYSTEM PARTICIPATION
between
[SELECTED BIDDER]
and
PAKISTAN INTERNATIONAL AIRLINES
24
CONTENTS
PARTIES
(1)
This agreement is made on this _____________day of _________between Pakistan International Airlines Corporation Limited (PIACL), a public limited company incorporated and governed by and under the Laws of Pakistan having its Head Office at Jinnah International Airport, Karachi, (hereinafter referred to as Customer which expression shall where the context so admits include its successors and assigns ) of the one part
(2) and
(3) [name and registered address of service provider][Registration details] _______________________________________________(hereinafter called referred to as Service Provider which expression shall where the context so admits include its successors and assigns) of the
other part.
The Customer and the Service Provider may individually be referred to as a “Party” and collectively be referred to, as “Parties”, respectively, as the context of this Agreement requires.
BACKGROUND
(A) Service PROVIDER has developed and provides managed services consisting of end-to-end software application platform and a network of agents for Global Distribution System (GDS) at its remote location for the purpose of processing all aspects of sales of reservation of airline inventory, auxiliaries and ancillaries.
(B) The Customer wishes to use Service PROVIDER’s Global Distribution System (GDS) and its network services in its business operations.
(C) The Customer has desired to have systems as defined in the following section, and in addition integration with the already installed systems in PIA will also be required.
(D) Integrations with already installed systems including Reservations Engine, Interline & Code Share Integration, Pricing & Fare Management, Exchange & Refund, E-Ticketing & EMD (Electronic Miscellaneous Documents), Communication Manager and Frequent Flyer etc.
(E) Detailed requirements mentioned in but not limited to the Feature Requirements Matrix is appendix to and is part of this agreement.
(F) Service PROVIDER has agreed to provide and the Customer has agreed to take and pay for Service PROVIDER’s Global Distribution System (GDS) services subject to the terms and conditions of this Agreement.
AGREED TERMS
1. Interpretation
1.1 The definitions and rules of interpretation in this clause shall apply in this Agreement.
Active Booking: Means any Booking other than a Passive Booking or a Group Booking. Affiliate: Means, with respect to any Person, any other Person directly or indirectly controlling or controlled by, or under common control with, such Person. For purposes of this definition, “control”,
25
including “controlled by” and “under common control with”, means the power, directly or indirectly, to direct the management and policies of a Person, whether through ownership of voting interests, by contract or otherwise. Agencies: All agencies, their employees, agents, sub-agents or partners, corporates.
Authorised Users: All agencies (it’s those employees and sub agents), partners, corporates and independent contractors of Customer who are authorized by Service provider to use the SP System.
Booking Volume Credits: Total booking volume credit is calculated by multiplying the applicable credit rate with difference of the yearly volume in each point of sale on completion for each contract year. The volume credit rates are defined in the Schedule 1.
Business Day:means with respect to obligations to be performed by Service PROVIDER, any day,
other than a Saturday, Sunday, statutory or civic federal holiday in Pakistan. Code sharing: Means the industry practice whereby one carrier operates services using the airline designator code of another carrier. Code sharing Flights: Means flights marketed by Customer using its airline designator code but operated by another carrier.
Confidential Information: information that is proprietary or confidential and is either clearly labelled as such or identified as Confidential Information in clause 9.
Contract Year: the period of twelve (12) months from and including the Go-Live Date and each period of twelve (12) months thereafter;
Customer Account Team: the individuals appointed by the Customer from time to time who shall serve as Service PROVIDER’s primary contacts for Service PROVIDER’s activities under this Agreement.
Customer Data: the data input into the information fields of the Software by the Customer, by Authorised Users, or by Service PROVIDER on the Customer's behalf.
Customer's Project Manager: the member of the Customer Account Team appointed in accordance with clause 6(c).
Dollar or $ or USD: the lawful currency of the United States of America;
Effective Date: the date of signature of this Agreement.
Fees: The fees payable to Service PROVIDER as described in Schedule 1. Fee is applicable on the net segments booked and any other applicable fee per the Schedule 1.
Full Content: means all Fares (and associated inventory and rules), products, services and Functionality made available by the Customer, or via, any Distribution Channel (except Private Fare which are expressly excluded from this definition), and all other promotional fares (and associated inventory), all other promotions, incentives, commissions or other substantially similar program for flights distributed by the Customer through any Distribution Channel.
GDPR Regulation: The General Data Protection Regulation (Regulation (EU) 2016/679) as amended.
GDS: means a global distribution system (sometimes referred to as a computerized reservation system). A GDS collects, processes and distributes (via computers, websites, application programming interfaces or other devices or solutions) information concerning air transportation, and may also offer ground transportation, lodging or other travel related products or services offered by travel suppliers.
Go-Live Date: the date that the Customer is fully implemented on the Service Provider System and
made available to Customer for productive use commences live usage of Service Provider System.
Group Booking: Means a Booking created by or secured to an Service Provider Subscriber using group functionality provided by Service PROVIDER through the Service Provider System.
Implementation Services: the implementation and related work referred to in clause 2, to be performed by Service PROVIDER to configure the Software so that the Software conforms to the Product Specification.
26
Maintenance and Support: any Fault corrections, updates and upgrades that Service PROVIDER may provide or perform with respect to the Software and Platform Services, as well as any other support or training services provided to the Customer under this Agreement.
Managed Services: The Service PROVIDER will be responsible for including but not limited to developing, providing the software platform services, new agent activation, training, monitoring agents, hosting, maintenance, completing integrations with the third parties, ensuring uptime, smooth operations, help desk and also the service level agreements SLAs.
New Distribution Capability (NDC): NDC is a travel industry-supported program launched by IATA for the development and market adoption of a new, XML-based data transmission standard. NDC is about giving travel agents the same capability as airline websites.
Net Booking Fee per Net Segment: Net Booking fee includes charges for Active, Passive or Group
Booking and Does Not include any other charges like but not limited to cancellations & ticketing.
Net Booking Segment: means a Passenger Segment booked for one airport to the next airport. E.g.
Karachi to Lahore is one segment, Karachi to Lahore to Islamabad is two segments.
Normal Business Hours:means Service PROVIDER[local] office working hours from Monday to Friday9:00 am to 5:00 pm PST time, or as prescribed by the Government and notified by Customer except gazette holidays in Pakistan.
Travel Agency: Subsidiary of Service PROVIDER that holds the necessary tour operator and travel agency licenses to act as the Merchant of Record (MoR) and provide the necessary travel and fulfilment services for auxiliaries (non-flight travel products such as hotel, car rental, transfer, tours, travel insurance and flight hotel bundles).
Opaque Fare: Means a Fare sold under conditions where the purchaser is unable to identify, prior to purchase of the Fare, the specific airline offering the Fare and either the time of departure or time of arrival of the applicable flight. Optional Services: Means those optional services offered from time to time by Service PROVIDER, in its discretion, in which Customer has elected to participate by executing and delivering to Service PROVIDER the applicable Optional Services Addendum. Optional Services Addendum: Means an addendum executed by Customer and Service PROVIDER that covers one or more Optional Services. Passive Booking: means any Booking created by or secured to a SP Subscriber using action codes or status codes BK, BL, DS, GK, GL, PL or YK or their successor or replacement codes, or any similar Booking designated by Service PROVIDER. Person: Means any individual, firm, corporation, partnership, association, Limited Liability Company, joint-stock company, trust, unincorporated organization or other entity.
Platform: Travel booking management system and all its sub-components, modules and its integrations etc. that provides users with a platform for planning, booking, reservation and managing travel plans and related services. Customers, its employees, agencies, corporates and partners will use this platform with features as defined in the Feature Requirement Matrix.
PNR: Means a passenger name record created in the SP System.
Project Plan: the plan to be developed in the planning stage of the Implementation Services as per Schedule 2.
Private Fares: means fare filed in, or provided to a private area of, any Distribution Channel where access to, and the sale of, such fare is limited by the Customer to a select group of individuals or corporate travelers and there is a good faith effort by the Customer (or a person acting on behalf of the Customer) to limit the sales of such fares to the select group of individuals or corporate travelers. Private Fares do not include fares accessible by all, or substantially all, of the members/users of any Customer reservations channels;
27
Published Fares: Means Fares made generally available to the public through any Reservations Outlet but excluding Unpublished Fares.
Reservations Outlet: means any source from which some or all of the products and services of Customer can be reserved or purchased by any Person, including any GDS, Customer’s reservations system or its reservation or sales personnel or agents, or any internet site or direct connection, whether operated or marketed by Customer or any third party.
Service Level Arrangements: the service level arrangements set out in Schedule 4.
Services: Tour Operator & Travel Agency Licenses (MoR), Agent Selection & Management, Content Management, Campaign Management, Competition Management, Agency Network Management, Analytics & Customer Behaviour Management, Quality Control Management, Multi-Lingual Contact Centre, Fulfilment Services (Cancel, Reissue, etc.), Reporting (Airline, Suppliers), Invoicing, Collection, Payment and Taxation services necessary to sell, manage and operate auxiliaries (non-flight travel products such as hotel, car rental, transfer, tours, travel insurance and flight, hotel bundles).
Software: Service PROVIDER ’s Sales and Distribution System known as [Service PROVIDER ’s Product Suit Name] Global Distribution System (GDS), including any error corrections, updates, upgrades, modifications and enhancements to it provided to the Customer under this Agreement.
Selected Participation Option: Means the participation option designated as the Selected Participation Options. Service Provider (SP) Licensee: Means a Person licensed to market or distribute any version of the SP System in any area of the world, including any Affiliate of Service PROVIDER or any third party that is licensed to do so. Service Provider (SP) Subscriber: Means a Person that utilizes any version of the SP System. Service Provider (SP) System: Means Service PROVIDER’s GDS, including all versions thereof made available by Service PROVIDER from time to time, including any version offered through a SP Licensee.
Term: means the Initial Term as may be varied by (a) any extensions to this Agreement which are agreed pursuant to clause 12; or (b) the earlier termination of this Agreement in accordance with clause 12.
Third Party or Parties: any business, firm or company that is partnered with either the Customer or the Services PROVIDER and has the product or service including but not limited to ancillary services to be offered through the SP System.
Unpublished Fares: Means net Fares, bulk Fares, and Fares not generally available for purchase by the public, including corporate discounted Fares, tour operator Fares, consolidator Fares, wholesaler Fares, off-tariff Fares, group Fares, and meeting and incentive Fares.
Virus: anything or device (including any software, code, file or programme) which may: prevent, impair or otherwise adversely affect the operation of any computer software, hardware or network, any telecommunications service, equipment or network or any other service or device; prevent, impair or otherwise adversely affect access to or the operation of any programme or data, including the reliability of any programme or data (whether by re-arranging, altering or erasing the programme or data in whole or part or otherwise); or adversely affect the user experience, including worms, Trojan horses, viruses and other similar things or devices.
1.2 Clause, Schedule and paragraph headings shall not affect the interpretation of this Agreement.
1.3 A person means an individual, business concern, corporation, company, cooperative, partnership, trust, unincorporated association, entity with juridical personality or governmental authority, and pronouns which refer to a person shall have a similarly extended meaning.
1.4 A reference to a company shall include any company, corporation, holding, subsidiary, associated company or other body corporate, wherever and however incorporated or established.
28
1.5 Unless the context otherwise requires, words in the singular shall include the plural and in the plural include the singular.
1.6 Unless the context otherwise requires, a reference to one gender shall include a reference to the other genders.
1.7 A reference to writing or written includes letters, faxes and e-mail.
1.8 References to clauses and Schedules are to the clauses and Schedules of this Agreement and references to paragraphs are to paragraphs of the relevant Schedule.
1.9 A reference to a statute or statutory provision is a reference to it as it is in force as at the date of this Agreement.
1.10 If there is an inconsistency between any of the provisions in the main body of this Agreement and the Schedules, the provisions in the main body of this Agreement shall prevail.
2. Implementation Services
2.1 Service PROVIDER shall perform the Implementation Services in accordance with the timetable set out in Schedule 2. Service PROVIDER shall meet the performance dates set out in Schedule 2, any such dates shall be firm and final unless otherwise agreed between the 2 parties in writing. Time shall be the essence in this Agreement.
3. Hosting, Maintenance and Support
3.1 Service PROVIDER shall be responsible for Hosting, Maintenance and Support services related to the Service Provider System.
4. Customer INPUT Data
4.1 The Customer shall own all rights, title and interest in and to all of the Customer Input Data including but not limited to flight schedules, fares, interline agreements, capacity, inventory etc.
4.2 In the event of any loss or damage to Customer Data, Service PROVIDER will restore the lost or damaged Customer Data from the latest backup of such Customer Data maintained by Service PROVIDER in accordance with the Back-up and Recovery procedures.
4.3 If Service PROVIDER processes any personal data on the Customer’s behalf when performing its obligations under this Agreement, the parties record their intention that the Customer shall be the data controller and Service PROVIDER shall be a data processor and will ensure confidentiality of the customer’s data as per applicable laws:
5. Service PROVIDER’s obligations
5.1 Service PROVIDER undertakes that all the services will be performed substantially in accordance with this Agreement, the Product Platform and with industry standards and quality.
5.2 This Agreement shall not prevent Service PROVIDER and the Customer from entering into similar Agreements with third parties, or from independently developing, using, selling or licensing materials, products or services which are similar/ complementary / supplementary to those provided under this Agreement.
5.3 Service Provider shall:
(a) Maintain and operate the SP System;
(b) Provide the services described in the Selected Participation Option and any Optional Services;
29
(c) Construct and display Full Content in the SP System in accordance with the Selected Participation Options;
5.4 In the event of any any loss to customer attributable to non-conformance to this agreement by service Provider and/or, poor under and non-performance of Service Provider, Service PROVIDER shall be liable to provide remedies for damages through its own resources within timelines. However, the Customer shall be entitled to claim and deduct the amount of loss/damages from the security deposit as agreed between the customer and the Service Provider at Schedule 4. The Service Provider shall have no claim in this behalf.
6. Customer's obligations
The Customer shall:
(a) provide Service Provider and its subsidiary travel agencies with:
(i) all necessary co-operation in relation to this Agreement; and
(ii) all necessary access co-operation for integration and negotiations with the third
parties for adding auxiliary services to the platform.
(iii) all necessary access to such information as may be required by Service PROVIDER and its subsidiary travel agencies;
in order to comply with its obligations pursuant to clause 5
(b) provide such personnel assistance, including the Customer Account Team and other Customer personnel, as may be reasonably requested by Service PROVIDER from time to time.
(c) Nominate/designate the Customer's Project Manager, who shall have the authority to contractually bind the Customer on all matters relating to this Agreement. The Customer shall use reasonable endeavours to ensure continuity of the Customer's Project Manager during the term of this agreement;
(d) comply with all applicable laws and regulations with respect to its activities under this Agreement; and
(e) carry out all other Customer responsibilities set out in this Agreement or in any of the Schedules in a timely and efficient manner. In the event of any delays in the Customer's provision of such assistance as agreed by the parties, Service PROVIDER may adjust any timetable or delivery Schedule set out in this Agreement as reasonably necessary.
6.2 Customer shall facilitate and coordinate for integration of its reservations system and services with Service PROVIDER to provide, through the SP System, as advantageous and uniform reservations system and services to all SP Subscribers as Customer provides through any GDS. All improvements, enhancements, and additional functions to Customer’s reservations system or services offered to users of any GDS shall be offered through the SP System by Customer to all SP Subscribers. Customer’s reservations system and services include requesting air segment availability, air segment selling, PNR servicing capability, ticketing capability, passenger information, interim schedule change data, fare data, seat inventory, fare quotations, and procedural information.
6.3 Customer shall:
30
(a) Provide through the SP System to all SP Subscribers access to Full Content, including the
ability to view, book, ticket, document and fulfill Full Content;
(b) Not withhold from SP Subscribers, who access the SP System from any country, Fares
included within Full Content that Customer makes available to users of any GDS in that
country;
(c) Provide to SP Subscribers, who access the SP System from any country, no less favorable seat
inventory for Fares included within Full Content than Customer makes available to users of any
GDS in that country;
(d) Not close Customer’s flights to SP Subscribers, who access the SP System from any country,
on a less favorable basis than Customer uses to close its flights to users of any GDS in that
country; and
(e) Provide Service PROVIDER with all information and revisions to information concerning its air
travel services provided to passengers or prospective passengers, including interim schedule
change data, fare data and seat inventory, fare quotations, and such other material that may
be included in the SP System, as rapidly as possible and on at least as timely, regular,
accurate and complete basis as such information is provided to any GDS.
6.4 Customer shall not charge any SP Subscriber or any of its customers any service fee, surcharge or similar charge (“Subscriber Surcharge”) on account of that SP Subscriber’s selection, possession or use of the SP System, including in connection with Bookings made or tickets issued, except Customer may:
(a) Charge SP Subscribers a Subscriber Surcharge if Customer charges the users of all GDSs
that Subscriber Surcharge in the same amount and subject to the same terms and conditions;
and
(b) Enter into an agreement with an individual user of a GDS that provides for an amount of or
terms and conditions for a Subscriber Surcharge that differ from what is allowed under Clause
6.4(a) if Customer charges that user that Subscriber Surcharge in the same amount and
subject to the same terms and conditions for all GDSs selected, possessed or used by that
user.
6.5 Customer grants ticketing authority and credit card and payment authorization authority through the SP
System for its transportation and related services to Service PROVIDER and its Affiliates, acting as a representative of Customer, and all SP Subscribers worldwide to issue transportation documents, whether automatically, or electronically, and obtain credit card or other payment authorizations on Customer’s behalf.
6.6 All ticketing activities in any territory where there exists any settlement plan or ticketing scheme or vehicle shall be settled through the applicable settlement plan or ticketing scheme or vehicle, including the Airlines Reporting Corporation (ARC) for the United States, Puerto Rico, US Virgin Islands and American Samoa Points of Sale, the IATA Billing and Settlement Plan (BSP) for reporting and remitting procedures of IATA accredited SP Subscribers, the Transport Clearing House (TCH) of the Air Transport Settlement System (ATSS) for Russia and other applicable Points of Sale and direct ticketing with Customer. Customer shall promptly execute and deliver to Service PROVIDER all agreements or other authorizations, and provide Service PROVIDER with all data necessary for the activities authorized under this Clause 6.6.
31
6.7 Customer shall not terminate the ARC or IATA/BSP agency appointment agreement or any similar
agency authorization or appointment of any SP Subscriber, or take any other action to revoke or limit a
SP Subscriber’s authority or ability to issue tickets, unless that SP Subscriber: (a) has materially
breached an agreement with Customer and has failed to cure such breach within the cure period after
receipt of written notice of such breach; or (b) is engaged or is reasonably suspected by Customer to be
engaged in fraudulent activities. If Customer takes an action covered by this clause against a SP
Subscriber that is reasonably suspected to be engaged in fraudulent activities, Customer shall promptly
investigate such matter in a commercially reasonable manner. If such investigation reveals that the SP
Subscriber did not actually engage in fraudulent activities, Customer shall promptly rescind the action
taken against, and reinstate the SP Subscriber.
7. Charges and Payments
7.1 The Customer shall pay the amounts set out in 0 (Zero) for one time implementation Services. Net Booking Fee per Net Segment and Optional Services Fees as agreed between the parties.
7.2 Service PROVIDER shall invoice the Customer monthly [as of the last day of each month] for the all the fees defined in clause 7.1 via the IATA Clearing House under its normal procedures.
8. Proprietary rights
8.1 The parties acknowledge and agree that Customer and Service PROVIDER and its subsidiary travel agencies and/or its licensors own all intellectual property rights in the Software and the Services. Except as expressly stated in this Agreement, this Agreement does not grant the parties any rights to, or in, patents, copyrights, database rights, trade secrets, trade names, trademarks (whether registered or unregistered), or any other rights or licences in respect of the Software, Services or any related documentation.
8.2 Service PROVIDER confirms that it has all the rights in relation to the Platform that are necessary to grant all the rights it purports to grant under, and in accordance with, the terms of this Agreement.
9. Confidentiality
9.1 Each party may be given access to Confidential Information from the other party in order to perform its obligations under this Agreement. A party's Confidential Information shall not include information that:
(a) is or becomes publicly known other than through any act or omission of the receiving party; or
(b) was in the other party's lawful possession before the disclosure; or
(c) is lawfully disclosed to the receiving party by a third party without restriction on disclosure; or
(d) is independently developed by the receiving party, which independent development can be shown by written evidence; or
(e) is required to be disclosed by law, by any court of competent jurisdiction or by any regulatory or administrative body.
9.2 Each party shall hold the other's Confidential Information in confidence and, unless required by law, not make the other's Confidential Information available to any third party or use the other's Confidential Information for any purpose other than the implementation of this Agreement.
9.3 Each party shall take all reasonable steps to ensure that the other's Confidential Information to which it has access is not disclosed or distributed by its employees or agents in violation of the terms of this Agreement.
9.4 Service PROVIDER and its subsidiary travel agencies acknowledge that the Customer Data is the Confidential Information of the Customer.
32
9.5 No party shall make, or permit any person to make, any public announcement concerning this Agreement without the prior written consent of the other parties (such consent not to be unreasonablywithheldor delayed), except as required by law, any governmental or regulatory authority (including, without limitation, any relevant securities exchange), any court or other authority of competent jurisdiction.
9.6 This clause 9 shall survive termination of this Agreement, however arising.
10. Indemnity
10.1 The parties shall defend, indemnify and hold harmless each other against claims, actions, proceedings, losses, damages, expenses and costs (including without limitation court costs and reasonable legal fees) arising out of or in connection with the parties negligence solely attributable to the defaulting party in using the Platform or Software or Services, provided that:
(a) theparties given prompt notice of any such claim;
(b) the parties provides reasonable co-operation to the other party in the defence and settlement of such claim, at their own expense; and
(c) each party is given sole authority to defend or settle the claim.
10.2 Each party shall defend each other against any claim that the Software infringes any patent effective as of the Effective Date, copyright, database right or right of confidentiality, and shall indemnify the other party for any amounts awarded against the party in judgment or settlement of such claims, provided that:
(a) each party is given prompt notice of any such claim;
(b) the parties provides reasonable co-operation to the other party in the defence and settlement of such claim, at their own expense; and
(c) each party is given sole authority to defend or settle the claim.
11. Limitation of liability
11.1 This clause 11 sets out the entire financial liability of Service PROVIDER and its subsidiary travel agencies and its partners (including any liability for the acts or omissions of its employees, agents and
sub-contractors) to the Customer:
11.2 arising under or in connection with this Agreement;
11.3 in respect of any use made by the Customer of the Services, the GDS Platform or any part of them; and
11.4 in respect of any representation, misrepresentation (whether innocent or negligent), statement or tortious act or omission (including negligence) arising under or in connection with this Agreement.
11.5 Except as expressly and specifically provided in this Agreement:
11.6 Nothing in this Agreement excludes the liability of Service PROVIDER and its subsidiary travel agencies:
(a) for death or personal injury caused by Service PROVIDER ’s negligence; or
(b) for fraud or fraudulent misrepresentation of Service PROVIDER
11.7 The Service Level Arrangements state the Customer's full and exclusive right and remedy, and Service PROVIDER ’sand its subsidiary travel agencies only obligation and liability in respect of, the performance and/or availability of the Hosted Service, or their non-performance and non-availability.
11.8 The total aggregate liability of the Service Provider and its affiliate, in contract (including in respect of the indemnity), tort (including without limitation negligence or breach of statutory duty),
33
misrepresentation (whether innocent or negligent), restitution or otherwise, arising in connection with the performance or contemplated performance of this Agreement shall not be limited to the total contract price and shall be on the basis of actual loss and damage caused to the Carrier
11.9 The Penalties are defined in the Service Level Agreements Schedule 4.
12. Term and Termination
12.1 This Agreement shall commence on the Effective Date and shall continue for the period of three (3) years following the Go-Live Date (“Initial Term”), unless otherwise terminated as provided in this clause 12. After a full three (3) years, this Agreement may be renewed on mutually agreed terms to be finalized by the parties six (6) months before the end of the Initial Term in line with the Public Procurement Regulatory Authority (PPRA) Rule of Government of Pakistan
12.2 Either Party may terminate this agreement with a 6 months’ notice prior to termination without providing any reason.
12.3 Without affecting any other right or remedy available to it, either party may terminate this Agreement with immediate effect by giving written notice to the other party if:
(a) the other party commits a material breach of any other term of this Agreement which breach is irremediable or (if such breach is remediable) fails to remedy that breach within a period of 30 days after being notified in writing to do so;
(b) a petition is filed, a notice is given, a resolution is passed, or an order is made, for or in connection with the winding up of that other party (being a company) other than for the sole purpose of a scheme for a solvent amalgamation of that other party with one or more other companies or the solvent reconstruction of that other party;
(c) an application is made to court, or an order is made, for the appointment of an administrator, or if a notice of intention to appoint an administrator is given or if an administrator is appointed, over the other party (being a company);
(d) the holder of a qualifying floating charge over the assets of that other party (being a company) has become entitled to appoint or has appointed an administrative receiver;
(e) a person becomes entitled to appoint a receiver over the assets of the other party or a receiver is appointed over the assets of the other party;
(f) a creditor or encumbrance of the other party attaches or takes possession of, or a distress, execution, sequestration or other such process is levied or enforced on or sued against, the whole or any part of the other party's assets and such attachment or process is not discharged within [14] days;
(g) any event occurs, or proceeding is taken, with respect to the other party in any jurisdiction to which it is subject that has an effect equivalent or similar to any of the events mentioned in clause to clause 12.3(f) (inclusive); or
(h) the other party suspends or ceases, or threatens to suspend or cease, carrying on all or a substantial part of its business.
12.4 On termination of this Agreement for any reason:
(a) all licences granted under this Agreement shall immediately terminate;
(b) each party shall return and make no further use of any platform, property, materials and other items (and all copies of them) belonging to the other party;
(c) Service PROVIDER and its subsidiary travel agencies may destroy or otherwise dispose of any of the Customer Data in its possession unless Service PROVIDER receives, no later than ten days after the effective date of the termination of this Agreement, a written request for the delivery to the Customer point and time of termination Data back-up. Service PROVIDER and
34
its subsidiary travel agencies shall deliver the back-up to the Customer within 30 days of its receipt of such a written request.
(d) any rights, remedies, obligations or liabilities of the parties that have accrued up to the date of termination, including the right to claim damages in respect of any breach of the Agreement which existed at or before the date of termination shall not be affected or prejudiced.
(e) Both Parties will have the right to audit and confirm that the obligations of both Parties under this clause 11.3 have been completed.
13. Force majeure
Neither party shall be in breach of this Agreement nor liable for delay in performing, or failure to perform, any of its obligations under this Agreement if such delay or failure results from events, circumstances or causes beyond its reasonable control, including, strikes, lock-outs or other industrial disputes (whether involving the workforce of Service PROVIDER or any other party), failure of a utility service or transport or telecommunications network, act of God, war, riot, civil commotion, malicious damage, compliance with any law or governmental order, rule, regulation or direction, accident, breakdown of plant or machinery, fire, flood, storm or default of suppliers or sub-contractors. In such circumstances the affected party shall be entitled to a reasonable extension of the time for performing such obligations, provided that if the period of delay or non-performance continues for 3 months, the party not affected may terminate this Agreement by giving 30 days' written notice to the other party.
14. Waiver
14.1 A waiver of any right under this Agreement is only effective if it is in writing and it applies only to the party to whom the waiver is addressed and to the circumstances for which it is given.
14.2 Unless specifically provided otherwise, rights arising under this Agreement are cumulative and do not exclude rights provided by law.
15. Rights and remedies
Except as expressly provided in this Agreement, the rights and remedies provided under this Agreement are in addition to, and not exclusive of, any rights or remedies provided by law.
16. Severance
16.1 If any provision (or part of a provision) of this Agreement is found by any court or administrative body of competent jurisdiction to be invalid, unenforceable or illegal, the other provisions shall remain in force.
16.2 If any invalid, unenforceable or illegal provision would be valid, enforceable or legal if some part of it were deleted, the provision shall apply with whatever modification is necessary to give effect to the commercial intention of the parties.
17. Entire Agreement
17.1 Each party acknowledges that in entering into this Agreement it does not rely on, and shall have no remedies in respect of, any statement, representation, assurance or warranty (whether made innocently or negligently) that is not set out in this Agreement.
17.2 Each party agrees that it shall have no claim for innocent or negligent misrepresentation [or negligent misstatement based on any statement in this Agreement.
17.3 Nothing in this clause shall limit or exclude any liability for fraud.
18. Assignment
18.1 The Customer, without the prior written consent of Service PROVIDER, may subscribe or enter agreement or relation for GDS or services as defined in this Agreement with third party or parties for any market in any other manner.
35
18.2 Either may not at any time assign, transfer, charge, sub-contract or deal in any other manner with all or any of its rights or obligations under this agreement without Service Provider’s consent.
19. No partnership or agency
Nothing in this agreement is intended to, or shall be deemed to, establish any partnership or joint venture between any of the parties, constitute any party the agent of another party, nor authorise any party to make or enter into any commitments for or on behalf of any other party.
20. Variation
No variation of this agreement shall be effective unless it is in writing and signed by the parties (or their authorised representatives).
21. Third party rights
This agreement does not confer any rights on any person or party (other than the parties to this agreement and (where applicable) their successors and permitted assigns) pursuant to the Contracts (Rights of Third Parties) Act 1999.
22. Notices
22.1 Any notice required to be given under this agreement shall be in writing and shall be delivered by hand or sent by pre-paid first-class post or recorded delivery post to the other party at its address set out in this agreement, or such other address as may have been notified by that party for such purposes, or sent by fax to the other party's fax number as set out in this agreement.
22.2 A notice delivered by hand shall be deemed to have been received when delivered (or if delivery is not in business hours, at 9 am on the first business day following delivery). A correctly addressed notice sent by pre-paid first-class post or recorded delivery post shall be deemed to have been received at the time at which it would have been delivered in the normal course of post. A notice sent by fax shall be deemed to have been received at the time of transmission (as shown by the timed printout obtained by the sender).
23. Dispute Resolution
Any dispute, claim or controversy arising under this agreement, shall be referred to the Mediation Rules (the “Rules”) of the International Chamber of Commerce (the “ICC”) administered by the ICC International Centre for ADR (the “Centre”), which is a separate administrative body within the ICC.
24. Governing law
This agreement and any disputes or claims arising out of or in connection with it or its subject matter or formation (including non-contractual disputes or claims) are governed by, and construed in accordance with, the law of mutually agreed neutral venue.
25. Jurisdiction
The parties irrevocably agree that the courts of neutral and mutually agreed place have non-exclusive jurisdiction to settle any dispute or claim that arises out of or in connection with this agreement or its subject matter or formation (including non-contractual disputes or claims).
36
Signed by [NAME] for and on behalf of [SELECTED Bidder]
....................................... Title:
Signed by [NAME] for and on behalf of Pakistan International Airlines
....................................... Title:
37
Schedule 1 – Fees
1. NO IMPLEMENTATION CHARGES
2. TRANSACTION CHARGES
Pricing Component / Activity Price in USD Remarks
Net Booking Fee per Segment (USD)
Booking Volume Threshold Per
Contract Year Home Market Remarks
0 to 0.55 Million
Net Booking fee includes Active,
Passive or Group Booking, etc.
No Other Charges including
cancellations & ticketing will be
applicable.
0.55 to 1.1 Million
1.1 Million
Booking Volume Threshold Per
Contract Year Rest of the World Markets
0 to 0.25 Million
0.25 to 0.5 Million
0.5 to 0.75 Million
0.75 to 1.1 Million
1.1 Million
EMD
Any other Service Optional
3. PAYMENT SCHEDULE
[The customer and the Service PROVIDER will agree on the payment schedule and method for the payments after the completion of the bidding process.]
38
Schedule 2 - Implementation Services
1. TIMETABLE
As agreed in this contract.
2. PLANNING
Service PROVIDER shall prepare the Project Plan in co-operation with the Customer during this stage of the Implementation Services.
3. DESIGN
Service PROVIDER shall develop a configuration of hosting servers designed to provide access to the Software. The design shall include redundancy across application servers, database servers, and switches in order to allow for continued service in the event of certain component malfunctions.
4. IMPLEMENTATION
Service PROVIDER and the Customer shall co-operate in implementing the Services in accordance with the implementation provisions of the Project Plan.
5. TRAINING
Service PROVIDER and its subsidiary travel agencies shall provide training to such number of the Authorised Users as are specified in, and are otherwise in accordance with, the Project Plan at the cost of Service Provider including boarding lodging.
6. ROLLOUT
Service PROVIDER and its subsidiary travel agencies and the Customer shall co-operate in rolling out the Services to the Customer's Authorised Users in accordance with the roll-out provisions of the Project Plan.
7. IMPLEMENTATION TESTS
Both parties will prepare the details of their intended criteria for testing that the Implementation Services have been performed in such a manner that the integrations between the SP System and Customer’s existing systems can be completed on or before the applicable date set out in the Project Plan, such criteria the "Implementation Criteria”. Service PROVIDER shall, within the time period provided in the Project Plan, either approve or reject the applicable Implementation Criteria by giving written notice to the Customer. Service PROVIDER shall only be entitled to reject any of the Implementation Criteria on the basis that, and by detailing the manner in which, the specific Implementation Criteria require the SP System to function and perform in a manner which is outside the SP System’s technical capabilities at the time of the Implementation Tests. If Service PROVIDER rejects any of the Implementation Criteria above, the Customer may submit a revised version of the applicable Implementation Criteria to Service PROVIDER. Once Service PROVIDER has satisfied itself that it has completed the Implementation Services, it shall allow the Customer to conduct the tests in accordance with the Implementation Criteria (“Implementation Tests”). Service PROVIDER shall ensure that the SP System is ready for the commencement of the Implementation Tests by the applicable date set out in the Project Plan. The Customer shall complete the Implementation Tests within the period set out in the Project Plan for the conduct of the Implementation Tests. Service PROVIDER shall provide all such assistance as may be required by the Customer in the conduct of such Implementation Testing and Service PROVIDER may be present at such Implementation Tests.
39
Schedule 3 - Platform or Network Specification
8. GLOBAL DISTRIBUTION SYSTEM – NETWORK SPECIFICATIONS
The Service Provider will be responsible to provide hosting, maintenance of the platform at its own expense and will ensure 99.95% uptime in order to ensure maximum coverage and selling base for the Customer.
40
Schedule 4 - Service Level Arrangements
9. SERVICE AVAILABILITY
Service PROVIDER shall provide at least a 99.8% uptime service availability level (Uptime Service Level) and in case of below the target uptime level of 99.8%, penalties will be applied with exception of (planned interruptions, Denial of Services Attacks (DoS) and reasons outside the control of Service PROVIDER ), as the Customer is responsible for its own internet access. Availability does not include Maintenance Events, Customer-caused or third party-caused outages or disruptions (except to the extent that such outages or disruptions are caused by those duly authorised third parties sub-contracted by Service PROVIDER to perform the Services), or outages or disruptions attributable in whole or in part to force majeure events within the meaning of clause 13.
10. AVAILABILITY MEASUREMENT The proportion of time that the service was actually available for use by the Customer expressed as a
percentage. The monthly Service Availability is calculated as follows:
Availability % = [(Max Service Time – Unplanned Downtime) / Max Service Time] * 100
Where:
Max Service Time means the aggregate number of hours in any month during which that
application is actually available for
Unplanned Downtime shall mean the aggregate number of hours in any month during which
that application is unavailable, excluding any planned or scheduled downtime
The Service up time and downtime are based on the calendar month and agreed availability for the
application (including hours supported). The “Unplanned Downtime” is calculated based on Top
(Critical) incidents logged by the Customer during the month within the agreed Service Hours for that
Application. Similarly, agreed Service Time will vary for each calendar month based on days and
Application service terms. The availability commitment excludes outages taken for scheduled
maintenance.
11. PENALTIES
12. In the event that a Severity 1 Problems are not resolved in excess of their respective Service Level Work Around Solution times– 2.5percent (2.5%) of the following month’s Application Service Fees calculated as per the Schedule 1;
13. In the event that a Severity 2 Problems are not resolved in excess of their respective Service Level Work Around Solution times – 5 percent (5%) of the following month’s Application Service Fees calculated as per the Schedule 1;
14. In the event that a Severity 3 Problems are not resolved in excess of their respective Service Level Work Around Solution times – 7.5 percent (7.5%) of the following month’s Application Service Fees calculated as per as per the Schedule 1.
If Service PROVIDER fails for three (3) consecutive months or five (5) months in any consecutive
twelve-month period to meet the Severity 1 and Severity 2 Service Levels, or in the event that there are
three (3) separate Severity 1 Problems of continuous duration that are each in excess of twelve (12)
hours in any one year period, within thirty (30) days of such an event the Customer may either: (a)
reduce payment of the Application Service Fees in an amount of ten percent (10%) of total monthly
Application Service Fees calculated as per the Schedule 1 of this Agreement.
Penalties will be defined mutually by the Customer and the Service Provider for the misuse or
misconduct by the Travel Agents or Subsidiaries of the Service Provider.
41
Schedule 5 - Feature Requirements Matrix
Attached Excel sheet.
Item#
Functional Requirements Criteria
Availability Display in GDS
Display. For each flight in an availability display, 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 carrier must be shown.
Mandatory
Availability capability for the following: Mandatory
by specific carrier(s)- up to 3 Mandatory
by specific class Mandatory
by direct and single stop flights only Mandatory
via specific route Mandatory
Advance and go back by number of days. The ability to change the date of the current Availability Display by simply inputting +/- x days or by selecting date tabs
Mandatory
Reverse availability with change of date. Once an availability display has been input, an abbreviated input for another availability in the reverse order is required
Mandatory
Ability to display a minimum of 26 booking classes Desired
Ability to Handle OAG/Innovata : Selected GDS must be able to handle these 2 core & all other Industry level IATA scheduling data standards with ease.
Mandatory
First Available. The ability to select a city pair and class plus a start date is required. The system should then check availability from this date forward and return the first date when the selected class is available for sale.
Mandatory
Ability to manually update OAL flight status (AVS). When the status changes on a cont rolled flight, the option of sending availability status messages (automatically or manually) is required.
Desired
9 Flights per Availability. Availability Displays should display a minimum of 9 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.
Mandatory
Ability to show a city pair comment. There is a requirement to show optional information over and above the normal flight details on an availability display. e.g. CMBSIN-comment: “Kingston is experiencing a drought. Passengers are advised to take their own water.”
Desired
Ability to display out and back availability in a single screen/display. Mandatory
Ability to retrieve Flight Schedule information up to 3 days post-departure at a minimum. Mandatory
42
Number of seats. Display IATA-standardized number of seats available in each inventory. Mandatory
Re-accommodation as a result of schedule change. Automated passenger re-accommodation as the result of a schedule change. Options to manually vet and change the system allocated flights are also required.
Mandatory
ASR retained. All passenger re-book/re-accommodation transactions (including schedule change), will attempt to retain Advance Seat Reservations.
Mandatory
Passenger Notification Options. The following notification options are required: “Yes, send notification”
Desired
“No, do not send notification”
“Deferred delivery of notification”
“Specified City where automatic notifications are possible”.
Misconnect Passengers. Misconnect PNRs caused by schedule change or by re-book transactions must be queued internally for follow up amendment. (The ability to have the system send to an Internal email instead of placing on a queue is also favorable)
Mandatory
Block and restrict seat assignment. The 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.
Mandatory
PFS. The ability to process PFS messages by both compartment and RBD is required. Desired
Post Departure Processing. Post departure processing should automatically update the inventory and passenger information reflecting the actual boarding statistics for a flight.
Desired
Enter/Change/Delete ticketing time limit. Mandatory
Cancel Unassigned Seats. The cancel unassigned seats in a group PNR transaction is used to remove seats initially reserved for a group. As the departure time approaches the user may wish to review the number of unassigned names and make adjustments as necessary.
Mandatory
AIRIMP. The ability to handle any changes to group bookings as per AIRIMP standards. Mandatory
AVS. The System must provide the ability to control the sending and receiving of AVS messages, based carrier specific rules (e.g. first closing, segment availability, message batching)
Mandatory
City Pair Availability Host carrier must be able to suppress/preference carriers in City Pair Availability
Mandatory
Revenue Management System Ability to support PIA CURRENT RM system; provide files on daily basis containing advanced bookings and Post Departure records.
Desired
Inhibit advance seat selection. The System must provide the ability to inhibit advance seat selection and seat map retrieval based on carrier specific rules.
Mandatory
Group Seating including group seat block assignment, group seat map display and seat allocation to individual names from the group block.
Mandatory
GUI Front End. All inventory displays and updates can be actioned via a user-friendly front end (GUI).
Desired
Flight number capacity. There must be no upper limit to the number of flights which can be put into the system. It is recognized that flight numbers do not currently exceed four digits, i.e. 9999.
Mandatory
Emergency Lock. It should be possible to place an emergency lock on a flight’s inventory and PNRs. Emergency locked inventories and PNRs are only accessible by control agents.
Desired
Flight Readouts. Readouts should show leg information for a flight by compartment and contain the departure airport code, availability status, seats open or overbooked, and aircraft capacity, plus various indicator such as Max, CAP, booked, Waiting list, Group,
Desired
43
request, Block by class
CODE SHARES IATA. The system must support all IATA Options for Codeshare. Mandatory
IATA Message formats. Standard IATA AVS/NAVS RAS message generation must be supported.
Mandatory
Codeshare flight. Support operating carrier and marketing carrier flight numbers and carrier codes for IATCI down-line connections.
Mandatory
PNR HANDLING FUNCTIONALITY The system must support all IATA & industry accepted codes. Mandatory
Sales. All sales functionality should apply to both host and OAL flights. Sell functionality must be able to handle infants regardless of whether they occupy a seat or pay a fare. System wide parameters should determine if an infant name and age are required.
Mandatory
Sell flight direct without reference to availability display. The ability to sell a flight by using flight number, date, O&D without any reference to an availability display is required.
Mandatory
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.
Mandatory
Mix of sell and waitlist segments allowed. PNRs may contain an unrestricted mixture of segments and status codes. A warning advising duplicate segments (confirmed only) should be given at End of Transaction.
Mandatory
Ability to book Non Rev/Rev Space-available segments. The ability to book Non-Revenue and or Revenue segments as “space available” and have such segments clearly identified in PNRs.
Desired
Ability to Upgrade/Downgrade. The ability to change the class (up or down) of a segment or segments to another class when a PNR is displayed if that class is available. e.g. GCMMIA Y class and MIAGCM Y class segments are in PNR. A simple entry should be available to change Y class to J class on one or both flights.
Mandatory
Ability to sell different classes in one entry for connecting flights. Agents need the ability to sell different classes on connecting flights from an Availability Display. e.g. Availability from KIN to HAV via GCM. With one input an agent should be able to sell KINGCM as economy and GCMHAV as business class.
Mandatory
Sell Open Dated Segment. Agents require the ability to sell “open” or non booked (ARNK) segments. Agents must also be able to input a date in any “open” segment.
Desired
Info tag on information only segments. The ability to input “information segments”, e.g. Arrival Segments and ARNK segments, is required. Information only segments in PNRs need to be clearly labeled as information only.
Mandatory
Auxiliary Service Element. The system must support auxiliary service elements that may be requested by a passenger: air taxi, car rental, car rental operator, hotel accommodation, hotel accommodation operator, surface transportation, tour and tour operator (ATX, CAR, CCR, HTL, HHL, SUR, TUR, and TTO).
Desired
Ability to rearrange segment order in PNR. The agent should have the ability to rearrange the segment order as desired within a PNR.
Mandatory
Non-group PNR maximum names. Mandatory
Non-group PNRs should support at least nine names plus infants (System wide parameters should determine if an infant name and age are required). All names can
44
either be input in a single transaction or as multiple transactions.
Inhibit Name Change. The System must inhibit modifications to name changes, based on carrier specific rules. List rules available in the system.
Mandatory
Multiple PNR display modes: Normal, Complete & Historical PNRs. In addition to normal PNR display, alternative modes are required to assist in passenger handling, e.g. “Complete PNR” showing all elements including non-active elements and “Historical PNR” for displaying PNRs which are no longer active.
Desired
Ability to view only specified PNR data. e.g. only display segments, contact details, SSR, or OSI. Also the ability to view cancelled elements, e.g. cancelled flights, cancelled SSRs, etc.
Desired
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.
Desired
Retrieve PNR by Host Record Locator. Ability to retrieve a PNR by its unique Host Record Locator.
Desired
Retrieve PNR from name list. The ability to display a list of passengers and then select and display a PNR by selecting a passenger from the list by number.
Desired
Retrieve PNR from availability e.g. Availability displayed, Pax advises he is booked on flight. Retrieve PNR by name & displayed segment number.
Desired
Enter sold segment into existing PNR. e.g. sell segment, retrieve PNR, enter segment. Desired
Ability to divide or split a PNR. The ability to separate passengers from a PNR, file the original PNR (minus the split passengers) and then modify and file a new PNR for the split passengers. Once filed the original and new PNRs must be cross referenced.
Mandatory
Ability to divide PNR and retain related SSRs. Refer above. When PNRs are split any common information SSRs, contacts etc. are retained in both PNRs. Any information that is passenger specific is retained or transferred to the appropriate PNR which contains that passenger.
Mandatory
Ability to concatenate entries to build a PNR. Agents should be able to input multiple PNR elements via a single entry e.g. name, contacts, flight segments.
Mandatory
Reduce number in party. The ability to reduce the number of passengers in a group PNR even when names have not been advised, e.g. reduce group PNR seats from 50 to 40.
Mandatory
Insert/Move/Re-arrange PNR fields. Ability to rearrange element order in PNR. The agent should can re-arrange the element order as desired within a PNR.
Mandatory
Ticketing/E-TKT within RES PNR. The ability to issue an e-Ticket from the reservations system via a simple entry while displaying a PNR without the need to sign-in to the ticketing system. An SSR FOID will be an optional for this transaction. This ability may be restricted to certain user groups. It must also be possible to combine paper and electronic tickets within a single PNR if all carriers’ segments are not eligible for e-ticketing
Mandatory
Auto SSR processing by airport, airline, or others. SSRs must generate messages or lists to the appropriate entity, usually an airport, which can meet the requirements of the special service request. This should occur automatically.
Desired
Cancellation of information segments does not generate a message to carrier. If an information segment is cancelled no messages should be sent to the specified carrier nor to any other carrier.
Desired
Contact Fields. Contact fields are to contain different field types, including: Agent, Business Phone, Private Phone, Mobile Phone, Fax, Street Address. E-Mail address etc. It should be possible to cancel or change this PNR element.
Mandatory
Ability to view queuing history of PNR. The ability to determine which specific queues a PNR has been sent to and what action has been taken at each point.
Mandatory
45
Plain language itinerary print out. The ability to convert a PNR into a plain language itinerary.
Mandatory
Active PNR. All future PNRs should be active in the system. PNRs should only be archived no less than two days after the departure date of the last segment.- Please state maximum time allowed or if system does not archive and pnr’s are always accessible.
Mandatory
Public Remark. A public remark element is required. This is a free format element which enables the agent to provide information not applicable to other elements, e.g. “Passenger is afraid of flying”. This remark will be printed on PNR print-outs and itineraries. It should be possible to cancel or change this PNR element.
Mandatory
Private Remark. A private remark element is required. This is a free format element which enables the agent to provide information not applicable to other elements e.g. “Passenger is psychotic”. This remark will never appear on itineraries. The remark will only be printed on PNR print-out when specifically requested via a special print option. It should be possible to cancel or change this PNR element.
Mandatory
SSR element. The ability to input an SSR element into the PNR as per IATA standards, including SSR FOID for e-Ticketing. SSR elements are queued (immediately or deferred, depending on the departure date) to appropriate locations. It should be possible to cancel or change this PNR element.
Mandatory
OSI Element. The ability to put an Other Service Information (OSI) element in the PNR. OSI elements are queued (immediately or deferred, depending on the departure date) to appropriate locations. It should be possible to cancel or change this PNR element.
Mandatory
Tkt Element. The ability to input a manual ticket element or in the case of automated ticketing (E-Ticket, ATB etc) a ticket element is input by the system. It should be possible to cancel or change this PNR element.
Mandatory
FF number. A PNR element is required for frequent flyer details. It should be possible to cancel or change this PNR element.
Mandatory
Passport/Visa Element. A PNR element is required for passport/visa information. It should be possible to cancel or change this PNR element.
Mandatory
Ignore PNR. The ability to ignore any activity undertaken by the agent on a PNR prior to “EOT” is required.
Mandatory
Cancel Passenger. The ability to cancel a specific passenger(s) within a PNR is required. Non-specified passengers are not affected.
Mandatory
Cancel PNR. The ability to cancel a complete PNR is required. Mandatory
Cancel PNR Elements. The ability to cancel/change specific PNR elements is required. Mandatory
Cancel Segments. The ability to cancel some or all segments in a PNR element is required. Mandatory
Cancel/Rebook. The ability to cancel some or all segments in a PNR element and re-book them for an alternative date via a single input which specifies that date(s) is required. The same functionality is required by class i.e. change all classes for the booking from class A to class B with a single input specifying that class.
Mandatory
Print PNR. The ability to print the PNR to an associated printer. Print options must include: print entire PNR, print active PNR, print only name & segments, print only specific PNR elements (e.g., OSI, SSR), print PNR with private remarks. ( also option to Email PNR)
Mandatory
Place PNRs listed on a nominated queue. Any listing option displayed on screen, e.g. un-ticketed PNRs, should be able to be sent to any queue for processing with a single transaction so that all PNRs appearing on the list are queued to the selected queue.
Mandatory
Re-display multi-selection list. The latest multi-selection list display should be kept so that at any time a simple transaction can re-display the list.
Mandatory
Booked passengers with confirmed reservations (HK, KK, KL, RR). Mandatory
46
Display Groups for which all names have been advised. Mandatory
Include block seat. Desired
Display Groups (group and passenger name). Mandatory
Display passengers holding inbound connections to the flight. Mandatory
Display passengers with ASR elements. Mandatory
Display last booked passengers based on order. Desired
Display Passengers with special meals. Mandatory
Display Passengers with active OSI elements. Mandatory
Display any AUX, SSR, or OSI element of selected passengers in the list. Mandatory
Display Passengers holding outbound connections from this flight. Mandatory
Display Reconfirmed passengers. Mandatory
Display Passengers with active SSR elements. Mandatory
Display Ticketed passengers. Only entirely ticketed passengers are selected. Mandatory
Display Passengers who have electronic tickets or are marked to have electronic tickets issued.
Mandatory
Display Unconfirmed passengers (HL, US, UU, HN). Mandatory
Display Passengers with a cancelled status on the requested segment (HX, UC, UN, NO, XX, XL).
Mandatory
Display Space-available passengers (SA, ID, NR). Desired
Display by Individual Status Code Lists. Passengers are displayed based on the status code entered, e.g. KK, XX, HL, SA.
Mandatory
Display Unaccompanied Minors. Mandatory
Display PNRs with infants. Mandatory
Display PNRs with children. Mandatory
Display Only codeshare passengers regardless of their status. Mandatory
Passport Information. This transaction should list passenger names and passport numbers only. If viewed on screen it should be possible to select the PNR from a number on the list.
Desired
Itinerary Pricing
Basic fare information. The System must provide the minimum requirements for basic fare information as per industry standard such as fare basic code, booking class, carrier, etc. List information available in your system.
Mandatory
Link to external fares/fare quote database. Links to fare database providers such as SITA and ATPCo, with automatic processing of fare rule data and acceptance of ALL available daily transmissions from these fares provider.
Mandatory
Best Buy pricing from fares. The ability to display the “lowest fare” by either specifying the fare or by sorting fares over an O&D 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.
Mandatory
Best Buy pricing from availability. The ability to easily select the cheapest available flight segment from an availability display. All flights operating over the O&D for the specified day are checked.
Mandatory
Best Buy pricing from Itinerary. The 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.
Mandatory
LAF-Lowest Available Fares. The ability to easily select the cheapest available flight segment from an O&D over a date range input by the agent.
Mandatory
47
User friendly access. The System must provide user friendly access to fares and rules for self-service/internet users.
Desired
User defined filter. Provide user defined filter functionality on display of fares and rules information.
Mandatory
Non-public (private) and public-fares. Provide automated integrated access to both applicable published fares and customer specific un-published fares.
Mandatory
Provide the ability to retrieve fares with multiple options, e.g. Desired
Private fares
Passenger type
Fare type
List your system options.
Fares with special provisions. Provide the ability to retrieve and identify fares with special provisions, e.g. non-priceable fares, non-saleable fares, upgradeable fares.
Desired
Additional information. Provide the ability to retrieve additional information based on original entry e.g.
Mandatory
+ RBD by carrier Mandatory
+ Routing Mandatory
+ Footnotes Mandatory
+ Taxes/fees (ATPCo service fees)/other charges. Mandatory
Handle Single & Multiple Electronic Ticket Records (ETRs( Mandatory
Special off-tariff group and meeting fares. Automatically upload and implement special off-tariff group and meeting fares to a contract fares database.
Mandatory
Currency. Provide ability to retrieve fares in more than one currency at one time sorted by currency. Convert to any currency regardless of currency field.
Mandatory
Currency. Price itinerary using specific currency. Mandatory
Carrier general rules. Provide the ability to retrieve carrier general rules. Mandatory
Rule content default. The System must ensure that rule content default is ATPCo or SITA. Mandatory
Multilateral/bilateral fare. Provide the ability to process ATPCo/SITA multilateral/ Mandatory
bilateral fare product and any new applications which are introduced from time to time. Desired
Specific rule entries. The System must provide stand alone specific rule entries by e.g. fare-basis code, rule number, city pair.
Mandatory
Fare calculation element. Price itinerary with details of each fare calculation element, including, but not limited to fare basis, taxes and tax type, PFCs, Global Indicator, currency, fare including base, tax, total, surcharges, ROE.
Mandatory
Validation. Provide the ability to validate relevant ATPCo/SITA data (e.g. footnotes/routings).
Mandatory
Price itinerary with specific segment, multiple segments, range of segments combined with any one or combination of: specified fare basis, ticket designator, discount amount/percentage, passenger type(s), override connection/stopover, point of sale, point of ticketing, side trip, tax exempt, tax(es), validity dates, restricted fares excluded.
Mandatory
Low fare finder. Price itinerary with low fare finder plus offer options of alternate itineraries with low fares for travel on UL and OAL.
Mandatory
Open segments. Provide the ability to price open segments. Desired
Segments out of sequence. The System must inhibit auto-pricing of segments out of sequence in a single PNR.
Mandatory
Auto-price one ways as separate itineraries when specific carrier’s product requires it. Mandatory
48
Reason for failure. Provide the reason for failure when the itinerary does not price as booked and provide options for the itinerary (e.g. minimum stay not met, to qualify for the fare, minimum stay of first Sunday is required).
Mandatory
ZED fares. Provide the ability to price ZED fares and calculate the taxable amount for specific countries. Must be fully compliant with Cat 25.
Desired
Discount. Provide the ability to price a fare where a discount is applicable and is booked in a different booking class than the base fare.
Mandatory
Corporate Record. Utilize information contained in Corporate Record (e.g. account code) when pricing PNRs.
Desired
Re-price. Provide the ability to re-price itinerary including fees without making the change in the PNR.
Mandatory
Currency. Provide the ability to price in currency of choice unless inhibited by the carrier specific rules or government regulation.
Mandatory
The System must have the facility to apply Fare Calculation Mode Indicator (FCMI) to all type of tickets.
Mandatory
Manual fare calculation. Provide the ability to build a manual fare calculation to drive a ticket applying industry standard formats.
Mandatory
History. Provide history for all fare and rule transmissions (e.g. ATPCo). Mandatory
Exchange Rate. Provide history of all exchanges rates e.g. ICH/BSR/BBR/IROE within system window of preferable 24 months.
Mandatory
Online query. The System must provide online query to access all historical fare and rule data.
Desired
Fare data and rules. Provide the ability to file and receive fare data and rules through ATPCo/SITA, through other intermediary sources or directly to/from the carrier.
Mandatory
Flexible sort order. Provide the ability to process according to a flexible sort order. Mandatory
BSR/BBR. 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.
Desired
ICH/BSR/BBR/IROE. Provide the ability to retrieve all or specific current exchange rates for: ICH/BSR/BBR/IROE.
Mandatory
Rounding principles. Process the rounding principles according to IATA resolution 024d for fares and other charges and amounts truncated for currency conversions.
Mandatory
Specific exchange rate. Provide user option input to select specific exchange rate or multiple exchange rates for currency conversions.
Mandatory
Lowest applicable fare. Provide the ability to search and price the lowest applicable fare validating all rules.
Mandatory
Fare construction principles. Enforce all fare construction principles according to the IATA resolution manual for composite.
Mandatory
Free baggage allowance. Provide the ability to retrieve all carriers free baggage allowance per carrier including dimensions for all points or by city pair or origin/destination countries.
Mandatory
Excess baggage charges. Provide the ability to retrieve all carriers’ excess baggage charges per carrier including dimensions for all points or by city pair or by origin/destination countries.
Mandatory
Taxes/fee/surcharges. Provide the ability to retrieve all applicable taxes/fees/surcharges by country or by city pair. Should also show SEASONAL surcharges, if applied by PIA during certain travel dates.
Mandatory
Mileage. Provide the facility to calculate mileage for a string of cities w/o PNR (including carrier, surface sectors, global indicators, fare amount).
Mandatory
49
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.
Mandatory
Voluntary itinerary change or refund. The System in addition to automated reissue and refund processing it should also process any set of voluntary itinerary change or refund rules. Handle public and private fares, multi-carrier itineraries, and waiver scenarios. Accommodate e-tickets, paper tickets, manually-priced tickets and previously reissued tickets. Allow for agent-less itinerary change and refund transactions (e.g. websites, kiosks, PDAs, and telephone voice response units).
Desired
Be able to provide comprehensive Printing support for ALL functions listed in this document.
Ticketing Parameters Access. Access to e-Ticket must be available from both the RES and DCS systems. Mandatory
Ticketing Functionality. Functionality is required to allow e-Ticket exchanges, add collects, refunds, void and revalidation of host and OAL tickets.
Mandatory
Printing. The application must support the printing of coupons and receipts and itinerary/receipts. Itinerary/receipt and itinerary outputs must be converted from the ticket into a plain language itinerary.
Mandatory
Display Single ETR. Display Electronic Ticket Record (ETR) by ticket number, record locator, CC, FOID or name/flight/date/Segment.
Mandatory
Display Multiple ETRs. Display all Electronic Ticket Records (ETRs) by board point city, carrier/flight number, date (specific or range) or by frequent flyer number. Additional data can be used to limit the output such as FOP, CC, FOID.
Mandatory
OAL. Display single or multiple ETR from OAL database. The display must show the actual coupon status from other airlines’ e-Tickets.
Mandatory
Access. Allow on-line access to e-Ticket information for after use or exchange; unused or partially used
Mandatory
Manual Association. Functionality is required to allow for manual association of e-Ticket to name, coupons and segments for existing and new ETRs.
Desired
Compliance with Industry Standards. Compliance with all Industry standards is required from the Selected GDS, including but no t limited to:
Mandatory
1) Passing control of ETR coupons between carriers
2) Current IATA/PADIS EDIFACT 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 and paper tickets
6) Translate interline e-Ticket indicators received from OAG on SSIM (Standard Schedule Information Manual) file to display in city pair availability and PNR itinerary segments
7) The use of TKTREQ/TKTRES for GDSs
8) Use of TKCREQ/TKCRES for interlining
9) Control transfers of coupons
10) Coupon updates
11) Change of coupon status.
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 both manually and
Mandatory
50
automatically.
Parameters. Functionality is required to provide airline configurable business rules to control e-Ticketing parameters including, allowing activation/deactivation of markets, points of sale, user info, board point, off point, and flight numbers.
Mandatory
Interline Partners. Functionality is required to provide airline configurable, business rules to update interline e-Ticketing partner business relationship parameters, e.g. send ticket control immediately or not.
Mandatory
e-Ticket Coupon Association. The system must provide: Mandatory
1) e-Ticket coupon association by itinerary segment. Since a common PNR is required for RES & DCS this can also be utilized by the DCS system.
2) e-Ticket number and name association in the PNR
3) retention of associations in the event of a PNR split.
System Controls. Parameters are required to enable controls in regards to partners and GDSs, e.g. Carrier eligibility table.
Mandatory
E-TKT/DCS/RAS Interface. An interface is required between E-TKT, 3rd DCS and revenue accounting systems to provide availed coupon data.
Desired
Fares Interface. An interface is required between e-Ticketing and the RES/Fares systems to provide segment information and fare data. The selected GDS should provide the same
Mandatory
e-Ticket Supported. The RES & FARE systems must support e-Ticketing; e-Ticket for Free Sell and Block Space codeshare.
Mandatory
Support manual change coupon status and tools for monitoring. Mandatory
Manual TAT/ATB ticket supported. The system must have the functionality to issue ATB tickets.
Mandatory
Auto price all PNRs. All PNRs must be capable of being automatically priced by the system.
desired
PASSENGER BOOKING CONTROLS
Seat Characteristics Amendment. The application must provide 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.
Mandatory
SSR/OSI Codes. The application must process SSR/OSI elements (new or modified) 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 a request has been or can be fulfilled.
Mandatory
Aircraft & Aircraft Configurations. The application must be able to cater for all aircraft types which are utilized through the RES application but also cater for different seat configurations for all of these aircraft (many to one correlation). In addition the application must be able 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.
desired
Aircraft Types-View & Copy. The application must provide the 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.
desired
Day Change en Route. The application must support “day change en route” flights, i.e. The flight departs on one day and arrives on a subsequent day, to the same level as the
Mandatory
51
reservations system. The usual maximum is two days.
Seat Characteristics. The application must support at least ten types of seat characteristics. These should include window seat, aisle seat, over wing, forward, rear, restricted recline, exit row, basinet row, permanently blocked seat plus two seat characteristics which are user definable. Seats may have more than one characteristic if this is logical, e.g. window over wing seat.
Mandatory
Codeshare flights. The selected GDS should Support operating carrier and marketing carrier flight numbers and carrier codes for IATCI down-line connections.
Mandatory
Change Flight. The application should allow provision for the ability to check in a passenger (who has an e-Ticket) for one flight while adding the passenger into another flight’s standby list. All necessary data will be transferred to the standby flight. If the passenger is on-loaded to the standby flight, he will automatically be deleted from his original flight.
Mandatory
Change Seat Assignment. Provide ability to change seat assignment, including the optional automatic generation of new boarding pass(es). Specific seats or seat characteristics (i.e. any window, any aisle) may be requested. It should be possible to override the system (if the agent has the correct security level) and assign seats that would not normally be applicable to the passenger, or to upgrade/downgrade them into another cabin. The system should prompt the agent, e.g. “Collect old boarding pass” and also prompt for payment if fees are applicable.
Mandatory
Additional Information for Agents. The application must support special displays and interfaces to provide enhanced information to check-in agents (Help, TIMATIC, Internal Information pages, etc.).
Mandatory
Display flights list. The application must provide the ability to display all active flights out of a station by carrier for the current date and the following day’s date up to a system specified parameter, e.g. 06:00 hrs, or for the current date plus all flights for the following date.
Mandatory
Pseudo Groups/Parties. The application must provide the ability to identify passengers who have been checked-in together even though they are traveling on different PNRs (i.e. pooling).
Mandatory
Bulk Transfer. The application must provide the ability to bulk transfer passengers, with all their relevant information, from one flight to another. This is independent of the function to move standby passengers from one flight to another.
Mandatory
PNR access. The application must provide the ability to retrieve and display the passenger’s PNR from DCS, via a line number reference, or seat number reference, a boarding pass number or a bag tag number, PNR code.
Mandatory
Partial PNR acceptance. The application must 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 noshow. The application should automatically attempt to reserve suitable seats for other passengers in the PNR so that they will be seated together if possible.
Mandatory
Fares Management
Selected GDS system should be able to auto-pick / Maintain both published and private fares, footnotes, and rules.
Mandatory
Historical data – stores all fare related data for at least 14 months. Mandatory
Filing market/net fares to fare collector such as: GDS, ATPCo, CRS and websites. Mandatory
Single source access to historical fares with resolution to rules data, access to private Mandatory
52
fares and rules data.
IATA electronic online tariffs database for obtaining latest updates, extracting various industry standard information, e.g. Fare Basis listings with conditions/rules data and footnotes-by country, by city pair, etc.
Mandatory
Access to currency conversion rates Mandatory
Site Administration Tool. PIA Selected GDS must have the ability to customize Selected GDS with the look and feel of PIA Selected GDS’ brand. PIA Selected GDS must also be able to configure page layouts, booking flows, enable and disable features, preview changes & track changes
desired
desired
Full Web access should be available for all aspects. desired
Special Feature Handling
Branded Fares. Selected GDS must have the ability to sell branded fares, fare families, bundled or unbundled from ancillaries. Selected GDS must also have upsell capabilities. Award Shopping. Selected GDS must have the capability for award shopping and redemption, as points/miles, combination of points/miles and cash, or on a sliding scale with varying amounts of points/miles and cash.
desired
Car and Hotel. Selected GDS must have the ability to book cars and hotels in path. Promotional Codes. Selected GDS must have the ability to create, administer, and redeem promotional/coupon codes for either a flat rate dollar discount or a percent off of the fare. Codes must be able to be restricted to a specific Flight/Route/O&D. etc.. Payment Options. Selected GDS should be able to accept as forms of payment Visa, MasterCard, Discover, American Express, UATP, PayPal, and Debit Cards with pin and customer profile wallet/Travel bank Selected GDS should be able to integrate with third party payment gateways. Please list any additional Integration that has been implemented or supported such as Western Union, Paymaster, etc. Currency Conversion. Selected GDS should provide a Dynamic Currency Conversion where holders of credit cards have the cost of a transaction converted to their local currency when making a payment in a foreign currency and at the very least support a default currency configurable by Airline. Multi Language Support. Selected GDS should provide the capability to show in multiple languages. List the languages supported. Partner Flight Sales. The web site must have the ability to show and sell Interline partner airline flights, and be able to display those flights in an order that PIA Selected GDS chooses, and in cases of connecting flights, choose the routing based on the airline reference. Passenger Types. Selected GDS should support the passenger types of adult, infant, senior citizen. Provide a list of all passenger types supported. Web Check-In. Selected GDS should provide the capability to check-in online, provide seat selection, and provide for the in path sale of ancillary items. Itinerary. Selected GDS should provide the capability to email the itinerary and passenger receipt. The itinerary should be configurable by PIA Selected GDS to add dynamic promotional and destination information based on itinerary.The passenger receipt should contain a breakdown of all air and ancillary sales and their associated taxes. Fare Rules Display. Fare rules should be displayed as requested by the passenger either utilizing a hover over approach or the ability to click on the fare rule and have it display in another window. Shopping Cart. Selected GDS should employ a shopping cart feature that includes all ancillaries sold, air, hotel, and car charges and the appropriate breakdown of those taxes and fees associated to them. Seat Selection. Selected GDS should provide the choice to preview seats prior to flight selection or after flight selection, and to see the number of available seats left at that fare when capacity drops below a pre-defined threshold. Web Analytics. Selected GDS should employ the ability to report on web site statistical data to help drive traffic to Selected GDS and to convert traffic more effectively. If Selected GDS does not have this capability, it should be able to integrate with a third-party tool such as Google Analytics. Corporate Sales. Selected GDS should contain a corporate portal that provides targeted promotions and marketing messages, intelligent reporting capabilities, and the ability to incentify and reward corporate customers. Agency Sales. Selected GDS should contain an agency portal that provides agent enrollment and tracking, invoicing, extension of credit, and reporting capabilities. Multiple Storefronts. Selected GDS should have the capability to employ multiple Storefronts. Site(Commercial, Corporate/Agency) must be able to Integrate with a Wallet feature as form of payment or Refund source and if no existing wallet exists allow its creation based on airline defined rules
desired
53
EMD HANDLING
System Functionality. Proposed GDS should be able to handle Associated & Standalone EMDs with ease & provide functionality for all ancillary services and the availability at all customer touch points. This should include, but is not limited to, the following: bundling of ancillary products as a package as well as the ability to sell as stand-alone products.
Mandatory
The system should allow for the issuance and management of other electronic documents including EMDs to Industry Standards in a fully interactive manner.
Mandatory
Other Vouchers. The system should allow any accountable voucher including, but not limited to hotel, meal, lounge and taxi vouchers to be printed at airport counters for passengers subject to flight delays and cancellations.
Mandatory
Unbundled Services. The system should enable PIA Selected GDS to apply and account for charges for unbundled services including but not limited to seat allocation, checked baggage, meals, in-flight WiFi.
desired
Calendar Shopping. The system should support calendar shopping for any number of days up to one full month at any time including but not limited to car, hotel and insurance.
desired
Data Sources. Describe the EMD data sources captured including frequency, method of exchange and storage capabilities.
desired
General GDS Functionalities
Queues
Queue functionality including: Mandatory
Ability to display queue count for host city/office and other cities
Queue Manipulation- i.e. queue assign, delete, placement, start, change, next, hard copy…
Queue Monitoring
Queue move and bulk move
Queues. A number of queues designed to assist customer flow, e.g. General Queue, Boarding List, Through List, Terminating List, Duplicate Bookings List, Meal Service List, Passenger Manifest, Airport Ticket Lists, Electronic Ticketing Lists, Transfer Lists, FFP Lists, Schedule Change Lists, etc. Normal Queues must be easily set-up (parameter driven) based upon any characteristic within the PNR.
Mandatory
Teletype Message Handling
Quick user entries for message processing to be available. User friendly inputs which will be translated into the correct AIRIMP formats by the system.
Mandatory
Direct Access. The system must support Direct Access availability/translation of requests and responses.
Mandatory
EDIFACT compliant. All current versions of Interactive EDIFACT IATA message structure must be supported.
Mandatory
Guaranteed sell. The system must support guaranteed sell (KK/HK). Mandatory
Seamless Availability. The system must support seamless availability/sell for codeshare & Interline
Mandatory
ENCODE/DECODEUSER/SECURITY
54
Easy entries for all encode/decode- The functionality to encode and/or decode common airline entries must be simple. Methods such as drop down lists are anticipated, as is the ability to input one or two characters and receive a listing of probable.
Mandatory
Entries should include:
Countries/States
Cities/Airports
Airline Code/Equipment
Ability to check codeshare partner’s flight numbers. The ability to input a host flight number and segment and return a listing of all associated codeshare flight numbers for this flight.
Mandatory
Easy entries for industry standard codes. The functionality to encode and/or decode standard industry codes such as SSR, OSI & Meal codes must be simple. Methods such as drop down lists are anticipated as is the ability to input one or two characters and receive a listing of probable matches.
Mandatory
MESSAGE HANDLING
Generate commercial messages. Provide capability to generate commercial messages to any location via FAX, TELEX, and e-mail, SMS.
Mandatory
Redisplay commercial messages. Provide capability to redisplay, edit and retransmit commercial messages previously generated.
Mandatory
Online help. Provide the option of requesting help information for generating commercial messages.
desired
Display & Update functions. Provide real-time services to display and update tasks/functions/utilities defined for time-initiated activation.
desired
Nightly maintenance. Provide real-time service utilities to run nightly file maintenance of system records and resources.
desired
Industry standard messages. Provide airline customizable business rules to activate automatic time-initiated generation of industry standard messages.
Mandatory
Offline files. Indicate which offline files are available for offline viewing/ importing into on premise systems , Indicate options for how files can be transmitted to PIA Selected GDS.
Mandatory
Communication
Connectivity to Host. Internet Connectivity back to the Host system is preferred over Dedicated Circuits. Main Connectivity options available to PIA are: Dedicated Circuits, Internet via VPN/Router, Direct Internet access (no VPN router required)
Mandatory
Email. System MUST support the option to send hardcopy/telex messages to a printer address. It should have the ability to handle telex address so that they can be configured either in the host system or via a client side application/PC
desired
Support System – Chosen GDS should offer 24/7 Phone Line, email, web based helpdesk/ticket system so that PK team may approach its queries, regardless of the time in Pakistan or Country of Origin of request.
Mandatory
55
Loyalty Program Handling
Connectivity to LMS. System must have documented API to allow external Loyalty Management System to connect and interface with the host system regardless of any built-in native Loyalty interface.
Mandatory
Tier Level. Tier levels must be shown at time of pax booking for gold and platinum levels, so that priority levels may display at the check-in staffs end at time of pax boarding
Mandatory
USER/SECURITY FEATURES
Sign-in/Sign-out. The ability to access the system via a user name and user update-able password. The ability to sign out of the system, as well as auto sign-out after XX minutes of inactivity. Where XX is an airline defined parameter by pseudo City/system wide/specific to a user sign
Mandatory
Security Levels/Access/Duty Codes/Packages/Modes. The ability to specify certain types of functionality for certain user types, e.g. RES agent, DCS agent, fares agent, etc.
Mandatory
Password Security. Security measures for passwords, such as automatic password reset after x number of failed sign-on attempts.
Mandatory
TIMATIC Access. A facility to connect to the TIMATIC System is required. desired
Account Security. The ability for the system to automatically disable any account without any activity after XX days OR XX number of failed tries to log into the GDS system.
Mandatory
Boosting Sales
Selected GDS should establish a dedicated Service and Marketing Office in Pakistan's main cities KHI, ISB and LHE desired
Incentives should be offered through GDS for booking segments on PIA desired
Selected GDS should act as a partner for PIA & Promote PIA's weak sectors desired
Selected GDS should be asked to provide Annual Marketing Budget for PIA for promotional activities & functions desired
One Senior Staff to be sent on deputation to GDS Office in Pakistan, as Local G.M. to protect PIA interests at all times. PK staff salary shall be borne by the Selected GDS desired
Proper Training shall be imparted by the GDS to all GDS Subscribers/Travel Agents Mandatory
Selected GDS shall not provide Incentives to Other Carriers specially on PIA peak routes desired
GDS to provide Marketing Intelligence to PIA along with Joint Sales Calls to Travel desired
