Requirements

Reviews

Tags

requirements management, software requirements, functional requirements, Requirements Engineering, Requirements analysis, Requirements Definition, Use cases, requirements specification, software engineering, Business Analysis

Stats

views:: 58
rating:: not rated
reviews:: 0
posted:: 11/6/2009
language:: ENGLISH
pages:: 0

Public Domain

National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5 5.1 5.1.1 Functional Requirements Application Security General Reservation Requirements The system offered by the Tenderer / Application Service Provider / Vendor / Systems Integrator must support System security features for: a) Secure Sign in 5.1.1.1 b) Sign-out c) Agent in / Agent out d) Duty codes / User Group / for ATO / CTO / GHA / Consolidators e Agents Assembly Area f) Sign in Text The system must have provision to create new access levels / duty codes The system must support multiple level of authentication during sign 5.1.1.3 in. 5.1.1.2 YES 10 YES YES 8 8 Requirements Confidential Proprietary Page 1 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must have multiple access levels for eg:- Various Types of Agents and Users a) PTA Agent b) Ticket Sales Agent c) Message Switching d) Cashier e) Reservation Supervisors f) Reservation Controllers g) Fare & schedule loading h) Teletype Reject i) Check-in Agents j) Ramp Supervisor k) DCS Controller / Service Controller - CCC l) Load Controllers m) Revenue Accountants n) Customer Engineer 5.1.1.4 o) System Analysts p) Programmers (Access level for programmers relates to the requirement to enable creation / maintenance of database for space controllers' activities in RES, Fares, Ticketing, DCS & other related modules.) / System Administrators q) Planning Analysts r) Sales Analysts s) Marketing Analysts t) Planning Analysts u) Performance Evaluation Analysts (The Access levels requested in this clause under various duty heads are tuned to the carriers requirements. The specific areas under these clauses can be understood in as much as a "Sales Analyst" may be required to monitor the effect of the Sales Promotion initiatives on flights/ routes on day to day basis for current and future periods; a 'Marketing Analyst' may require access to data on actual performance of flights to evaluate effectiveness of Market Planning inputs; a 'Planning YES 10 Requirements Confidential Proprietary Page 2 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must be capable of providing travel agency environment with : 5.1.1.5 a) Auto Sign in facility b) Permanent Sign in Facility c) Manual Sign in facility The System must have provision to dynamically create different new 5.1.1.6 user environment to differentiate between travel agency location, ATO/CTO location, Call Centres The system must be able to enforce all the restrictions at the Travel 5.1.1.7 agency terminal. e.g. PNR retrieval of another agent/airline / variation in Time limits/Large Party bookings. 5.1.1.8 The system must have the ability to provide password for each of the Sign-in code along with the facility to change the password. YES 8 YES 8 YES 10 YES 10 The system must have the capability to protect a Sign-in number 5.1.1.9 from being misused or hacked or pulled on a different monitor having a separate identity The system must be capable of hiding( encrypted ) the Sign-in 5.1.1.10 password from the monitor while signing-in The system must have the capability for Auto sign out if unused 5.1.1.11 beyond a period, the period being a parameter, specified by the airline. The system must provide historical data /usage report pertaining to 5.1.1.12 Sign-in numbers (date of allotment, change, authority, unsuccessful attempts of sign in) The system must have the capability to allot Sign-in numbers which 5.1.1.13 are city/office specific The system must have the ability to maintain sign in tables city / 5.1.1.14 office wise The system must have the capability to invalidate sign in number 5.1.1.15 after a pre-defined period of inactivity and pre-defined invalid attempts of sign-in. YES YES YES 10 8 10 NO NO NO NO 6 6 4 6 Requirements Confidential Proprietary Page 3 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must provide audit trails and reports of the transactions 5.1.1.16 (input / output) carried out for a given date / time range, agent-wise, terminal number wise. The system must provide information of active user(s) on a given 5.1.1.17 terminal or all terminals, available online. The system must have the facility to restrict certain functionality to 5.1.1.18 specific terminal Ids. The system must have input/output terminal monitor function facility 5.1.1.19 from designated supervisory terminals The system may have inter terminal switching (AAA)/ screen transfer facility. (Screen transfer facility requested under this clause means the capabilities of the system to facilitate a Controller to 5.1.1.20 transfer (pull) an earlier executed transaction awaiting processing/response from Host to another device in case of link failure on the first device on which the transaction had been fired, so as to avoid loss of transaction and the need to start afresh.) The system must have the facility of providing multiple screens on a single terminal The system must restrict allotment of Sign in numbers from only a 5.1.1.22 Control City with specific duty codes. 5.1.1.21 The system must provide restrictions on creation, updation and deletion of Sign in test as per: 5.1.1.23 a) Duty codes b) Control city The system shall have the capability to display city /country / region 5.1.1.24 specific information when an agent signs in based on office/duty codes The system shall have capability of providing scroll page facility in 5.1.1.25 case the Sign in text exceeds screen limitation. The system may have the facility of sending an alert / blink 5.1.1.26 whenever new information is fed in the Sign in text YES NO NO YES 10 6 10 10 NO 4 NO YES 6 10 YES 8 NO NO NO 8 4 4 Requirements Confidential Proprietary Page 4 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.1.1.27 5.1.1.28 5.1.1.29 5.1.1.30 5.1.1.31 5.1.1.32 5.1.1.33 The system may have the facility of inactivating the sign-in text automatically after specified number of days (configurable parameter) and the data held previously to be sent into history for future reference The system must have the facility to provide a supervisory agent to add Sign in text for their own city / office which is displayed to all agents in that city / office on sign in. The system must have the facility of wide Broadcast message on screen by city / flight / duty code / POS The system must have the facility to store a Sign in text for a future date/time for automatic display The System shall provide an alert on receipt of an unsolicited message on the receiver's screen The system must have the facility to restrict the Sign in text from being displayed by : a) Duty code / User Group b) By city c) By airport The System must be capable of hyper linking Sign-in text information to applicable chapter/page of Central Information System NO 4 NO NO NO YES 6 4 4 8 YES 10 NO 4 5.2 5.2.1 Reservation General Reservation Requirements The System must support all current and future travel components 5.2.1.1 via the management of dynamic records like PNR, Group PNR, Customer Record, Corporate Record The System must support a minimum of at least 99 passenger 5.2.1.2 names, 16 segments with the capability to expand beyond the specified number in the future The System must support create, copy, add, merge, modify, send, 5.2.1.3 cancel/delete and presentation functionality (e.g. print) for all travel records and associated functions Requirements YES 10 YES 10 YES 8 Confidential Proprietary Page 5 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support creation and retrieval of travel records 5.2.1.4 within system window for at least 340 days or more in the future and 3 days in the past The System must support use of structured data to allow 5.2.1.5 management of user-preferred output and reports The System must provide integrated reservation system performance management to obtain and compile current and 5.2.1.6 historical reservation transaction information (e.g. list of records, routings, sales) The System must provide for an integrated performance management system allowing for the production of reports, based 5.2.1.7 on specified details including but not limited to original booking/ticketing source, agent, agencies or outlet The System must provide functionality to auto and/or manual price, 5.2.1.8 ticket and service multiple trips across itineraries or within a single itinerary The System must meet all IATA standards when communicating 5.2.1.9 with outside sources The System must automatically apply mandatory fare quote on 5.2.1.10 itineraries built within the system The System must designate itinerary to be the basic repository used 5.2.1.11 for all passenger processes e.g. reservation, inventory management, fare quote/pricing rules, ticketing and check-in The System must support any type of married segment control, 5.2.1.12 based on the carrier specific and/or GDS rules The System must support modify, view and logically link PNRs to 5.2.1.13 customer records at time of creation and modification The System must provide logical linkage between Corporate 5.2.1.14 Records, Group Records, PNRs and Customer Records The System must allow a PNR that expires to become a past-date 5.2.1.15 PNR. If it was linked to a Customer Record, it must remain accessible through the Customer Record The System must support optional prompt/alert upon retrieval of 5.2.1.16 Customer Record and PNR (e.g. invalid phone/credit card, airport closure) Requirements YES YES 10 8 YES 8 YES 8 YES YES YES YES YES YES YES NO 10 10 10 10 10 8 8 8 NO 6 Confidential Proprietary Page 6 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.1.17 5.2.1.18 5.2.1.19 5.2.1.20 5.2.1.21 5.2.1.22 5.2.1.23 5.2.1.24 5.2.1.25 5.2.1.26 The System must provide the ability for logical links to enable the viewing and updating of all or any linked travel records The System must automatically link and provide the ability to manually link multiple PNRs (based on identical FQTV number or carrier employee ID) to an appropriate Customer Record based on carrier specific rules The System must automatically link and provide the ability to manually link several PNRs (including air and non-air products) for customers being booked together The System must automatically link and provide the ability to manually de-link PNRs, and PNRs from Customer Records based carrier specific rules The System must automatically link and provide the ability to manually link and de-link PNRs to/from their respective Group Records / Corporate Records, based on carrier specific rules The System must re-price and/or re-allocate inventory in the event modifications to PNRs cause links between PNRs and/or PNRs/Group Record and/or PNR/Corporate Record to be broken (e.g. cancellation results in loss of negotiated group fare, combined adult and companion fare quote) The System must maintain synchronization for all itinerary and passenger data at all touch points (e.g. reservation, ticketing, checkin) The System must maintain all travel/customer information in a single source of information that is accessible by all Managers of the carrier located at various locations around the world depending on the access level The System must provide the ability to restrict or allow access, modification, claim of travel records both from internal and external sources based on carrier specific and security rules and/or business policy The System must provide the ability to restrict or allow the viewing and modification of specified data on travel records both from internal and external sources based on carrier specific and security rules and/or business polity YES 6 NO 8 NO 6 NO 6 NO 6 NO 6 YES 10 YES 8 YES 10 YES 10 Requirements Confidential Proprietary Page 7 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.1.27 5.2.1.28 5.2.1.29 5.2.1.30 5.2.1.31 5.2.1.32 5.2.1.33 5.2.1.34 5.2.2 5.2.2.1 The System must provide the ability to access all reservation data, governed by security rules The System must support the ability to clearly identify and track the booking and/or ticketing source for both, internal (including individual agent) and external bookings The System must support a link to carriers sales management information tools and other databases, in order to identify and translate IATA agency/ERSP/PCC and others The System must provide the ability to organize all or portions of reservations data, as specified by carrier specific rules or agent input The System must provide a method of flagging elements and/or information within an PNR The System must support retrieval by each element and subsequent history (e.g. in a PNR show a specific flight segment with all previous modification) The System must automatically include change of aircraft/gauge information and flight details, e.g. airport terminal information or check-in time by segment The System must append real-time operational flight-movement information (FLIFO), e.g. delay, to the PNR Management of Customer and Travel Information The System must provide the ability to organize customer information and preferences in a structured format. This includes reformatting information from outside booking sources to align with travel records standards/logic. The System must provide the ability to add reminder (with free form text) to place PNR on queue at any future date for review The System must provide additional dynamic queue management for Group Records in order to receive and process group requests, as well as reviews at defined dates The System must provide a mechanism to identify from Customer Record or PNR, which PNRs are currently in a queue and provide the ability to remove from such queue YES YES 10 8 YES 8 YES YES YES 10 8 8 YES YES 8 10 YES 10 5.2.2.2 5.2.2.3 YES YES 8 10 5.2.2.4 NO 6 Requirements Confidential Proprietary Page 8 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide alerts when multiple actions are required 5.2.2.5 on a single PNR and automatically remove them from the various queues The System must support automatic creation of a Customer Record, regardless of booking source (e.g. Internet, IVRs, Call Center, kiosk, 5.2.2.6 ATO/CTO, CRM, GDS) by validated frequent flyer or carrier employee ID 5.2.2.7 Manage information from outside booking sources to conform with Customer Record (e.g. contact information, passport information) The System must retrieve and transfer information from/to internal and external customer data bases to the Customer Record The System must construct a Customer Record such that it contains customer data e.g. name, phone, passport data, The System must construct a Customer Record such that it contains customer data e.g. biometric data (e.g. fingerprint, retina scan etc.) The System must have the ability to interactively enroll new members, based on data in the PNR (e.g. name, phone number, address) and link to carriers frequent flyer system based on carrier specific rules The System must provide link to carrier employee database and transfer eligibility information (e.g. dependant/family members, seniority, companions) The System must update and transfer modifications to any or all components of the Customer Record to all associated sources (e.g. customer changes address via reservations office and Customer Record is updated) in a synchronized manner The System must manage modification and source of modification in Customer Record history The System must allow or restrict modifications based on carrier specific security rules (e.g. update contact data by authorized users only) NO 6 NO 8 NO 10 5.2.2.8 5.2.2.9 YES YES 10 10 5.2.2.10 NO 8 5.2.2.11 NO 8 5.2.2.12 NO 6 5.2.2.13 NO 10 5.2.2.14 5.2.2.15 YES YES 6 8 Requirements Confidential Proprietary Page 9 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.2.16 5.2.2.17 5.2.2.18 5.2.2.19 The System must find and replace changes/modifications from Customer Record to all selected or all associated PNRs (e.g. assigned seats through all associated PNRs), based on customers needs and/or carrier specific rules The System must support creation of PNRs regardless of booking source (e.g. carrier call centers, IVRS, ATO/CTO, IBE, SMS, ATM, GDS) The System must manage information from outside booking sources to conform with PNR standard (e.g. passenger contact information) The System must provide the ability to manage bookings for passengers traveling together (by dynamically linking multiple PNRs at time of creation, e.g. family of five traveling together). The System must also have the ability to create and link multiple PNRs via a single transaction at the time of creation NO 8 YES 10 YES 10 NO 6 5.2.2.20 The System must support creation of PNRs with or without air space The System must intuitively create and forward ticketing deadline 5.2.2.21 date messages to external booking sources, based on carrier specific rules and/or interfaces to fare database at time of creation 5.2.2.22 5.2.2.23 The System must automatically create a PNR of the customer if the carrier frequent flyer number is present The System must automatically link PNRs with a Customer Record at time of creation, if the carrier frequent flyer number is present NO 6 YES 10 YES YES 10 10 The System must support the ability to manage name variations for PNRs, that are linked to one Customer Record (e.g. Sunita Patel in 5.2.2.24 frequent flyer database vs. Sunitha Patel on travel document), based on carrier specific rules The System must provide the ability to retrieve and/or show all 5.2.2.25 PNRs controlled/owned by a single entity The System must link or transfer customer data/preferences from 5.2.2.26 Customer Record for the purpose of creating PNR content (e.g. name, address, language preference) Requirements NO 6 YES NO 10 8 Confidential Proprietary Page 10 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must apply customer preferences e.g. seats, frequent 5.2.2.27 flyer programs (from the Customer Record to the PNR) regardless of booking source, based on carrier specific rules The System must ensure that logical links support pricing and 5.2.2.28 ticketing across individual PNRs and enforce fare and ticketing rules (e.g. companion travel) The System must apply prompt/alert upon retrieval (e.g. runway 5.2.2.29 closure, or bandh at an origin or destination), based on operational requirements The System must provide the ability to create infant PNRs with or without inventory. Infant PNRs must not be created unless linked to an accompanying adult PNR. The System must also provide for 5.2.2.30 various infant pricing and ticketing options as defined by carrier specific rules (e.g. ”half-return” infant and “half-return” child in one PNR) The System must provide the ability to create PNR and associate 5.2.2.31 unused forms of payment e.g. ticket records (electronic and/or paper), coupons, credit vouchers 5.2.2.32 The System must support all modifications of all PNR data elements 5.2.2.33 The System must re-evaluate itinerary of all linked PNRs and invoke mandatory fare quote each time an PNR segment is cancelled or modified The System must allow modifications to PNR segments without fare quote re-evaluation, based on carrier specific rules (e.g. schedule change, waitlist clearance, duty responsibilities) The System must intuitively re-price and re-validate or exchange electronic ticket for all logical linked PNRs, whenever an PNR segment is cancelled or modified The System must provide prompt for fee collection at time of change or check-in, regardless of source of change The System must support all IATA-defined interactive cancellation (irreversible cancellation of flight segments), based on carrier specific rules NO 8 NO 6 YES 10 YES 10 NO YES NO 6 10 6 5.2.2.34 YES 10 5.2.2.35 5.2.2.36 5.2.2.37 NO YES YES 6 8 10 Requirements Confidential Proprietary Page 11 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.2.38 5.2.2.39 5.2.2.40 5.2.2.41 The System must support cancellation of one or several customers from logically linked PNRs (e.g. party of 4, reduce to party of 3) The System must support cancel/re-book of one or several customers from logically linked PNRs The System must provide the ability to auto-cancel un-ticketed PNR segments with optional preceding warning notification, based on ticketing deadline dates and/or carrier specific rules The System must automatically update logically linked PNRs, when modifications are made to any PNR element The System must provide automatic notification of flight status and changes to flights within an PNR (e.g. schedule change, waitlist clearance, irregular operations) at time specified by carrier specific rules The System must retain special service requests, e.g. seats, wheelchairs, meals, when changes are made on same flight, but in different class The System must synchronize all updates with external booking sources, based on carrier specific rules The System must intuitively synchronize all changes of passenger data to Customer Record (e.g. changes in passport data), based on carrier specific rules The System must manage modification and source of modification in PNR history The System must support functionality for waivers for tracking and accountability/back-office processing (e.g. fare restrictions) The System must allow/inhibit modifications to PNR elements (e.g. name changes), based on carrier specific rules The System must process name change and intuitively action, based on carrier specific rules, e.g.: - Action inventory space - Validate PNR/Customer Record links The System must ensure that cancelled PNR remains linked to the Customer Record, if applicable YES YES YES NO 10 10 10 8 5.2.2.42 YES 10 5.2.2.43 5.2.2.44 5.2.2.45 5.2.2.46 5.2.2.47 5.2.2.48 YES YES NO YES NO YES 10 10 8 10 8 10 5.2.2.49 YES 10 5.2.2.50 NO 8 Requirements Confidential Proprietary Page 12 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.2.51 The System must support creation of or link to a Customer Record, when FQTV number is added to the PNR at time of check-in YES 10 The System must provide the ability to auto-rebook selected passengers, based on specific criteria (e.g. origin and destination, 5.2.2.52 booking codes, flights) inhibiting misconnections and forwarding those for further action, which could not be rebooked 5.2.2.53 The System must support creation of or link to a Customer Record, when FQTV number is added to the PNR any time after departure Group Booking The System must provide the ability for Group Records to accommodate both, traditional group bookings (greater than 9) as well as the handling of allotments of any size for ad-hoc and recurring group business with the ability to differentiate between traditional groups and allotments The System must provide the ability for Group Records to contain group/allotment data and travel data e.g. group name, itinerary, contract details etc., The system must support incorporation of the Airline Business rules for Large party (Group) PNR handling like the Naming time limit, Ticketing Time limit etc The System must support automatic creation of a Group Record (request originating from outside source), holding inventory space on request and allow for responses, based on carrier specific rules (confirm, deny, place on queue) The System must provide the ability to create a carrier initiated Group Record for the purpose of holding and selling allotment/group space The System must provide the ability to pre-allocate inventory to a designated source, regardless of booking source YES 10 YES 10 5.2.3 5.2.3.1 YES 10 5.2.3.2 YES 10 5.2.3.3 YES 10 5.2.3.4 YES 10 5.2.3.5 5.2.3.6 YES NO 10 8 Requirements Confidential Proprietary Page 13 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to interactively sell from the 5.2.3.7 allotment from outside and/or inside. Manipulation of allotment inventory will be governed by carrier specific and security rules. The System must provide the ability to auto-cancel allotment/group 5.2.3.8 space with optional preceding warning notification, based on carrier specific ticketing and business rules The System must support automated sales processing of group inventory, forced bookings and forced waitlists (including partial space confirmation and waitlist reminders), based on carrier specific rules The System must provide the ability to build multiple linked inventory space which can only be sold as a unit (e.g. BOM-LHR-JFK can only be sold as BOM-JFK and not separately) The System must provide the ability to link Group Record to associated PNRs and their respective Customer Records (if applicable) The System must provide the ability to retrieve and/or show all Group Records controlled/owned by a single entity The System must provide auto-fare quote capability for group travel records and allow individual or group ticketing or any combination thereof The System must provide the ability to assign individual and/or group seats The System must provide the ability to support link and apply group contract rules via access to carriers‟ databases The System must provide the ability for outside sources to interact with and modify the Group Record subject to security rules and in accordance with current and future (e.g. for allotments) industry standards The System must provide the ability to support and interact with allotment space as a type of inventory maintained externally (e.g. GDS, wholesalers, cruise-lines) NO 8 YES 10 5.2.3.9 YES 10 5.2.3.10 YES 10 5.2.3.11 5.2.3.12 5.2.3.13 5.2.3.14 5.2.3.15 NO YES NO YES NO 6 10 8 10 6 5.2.3.16 YES 8 5.2.3.17 NO 8 Requirements Confidential Proprietary Page 14 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to support inventory and 5.2.3.18 business rules logic in synchronization with GDSs, based on carrier specific rules The System must provide the ability to apply automated reduction of 5.2.3.19 inventory and clearance of unsold space as defined as per airline specified rules The System must support management of charters (like Haj, 5.2.3.20 Umrah) using Group Record logic The System must provide the ability to create and link a PNR to the Group Record when a passenger name is added to the 5.2.3.21 group/allotment. The group inventory held in the Group Record is then reflected in the linked PNRs Modifications to the Group Records and their associated PNRs will 5.2.3.22 be governed by contract and carrier specific rules The System must provide the ability for cancellation of a Group Record which will lead to the cancellation of inventory space in the 5.2.3.23 Group Record and respective inventory space in all associated PNRs, based on carrier specific rules The System must provide the ability to cancel a Group Record while retaining PNRs for the purpose of re-sale/re-price of inventory 5.2.3.24 space. All associated Group Record data will be removed from the PNR, but appended in the PNR history. Functionality has to be restricted by carrier specific rules. The System must provide the ability to automatically update Group Records and all associated PNRs in the event of a schedule change 5.2.3.25 or any flight disruption. Customer/agency notification will be based on carrier specific rules The System must provide the ability to automatically process replies, 5.2.3.26 cancellations, reductions, name additions/deletions and splits, received from outside sources The System must provide the ability to automatically process replies, 5.2.3.27 advice and synchronization messages from other carriers, regarding their space The System must provide the ability to manage modification and 5.2.3.28 source of modification in Group Record history Requirements YES 10 YES NO 10 8 NO 6 YES 10 YES 10 NO 8 YES 10 YES 10 YES YES 10 10 Confidential Proprietary Page 15 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.3.29 5.2.3.30 5.2.3.31 5.2.3.32 5.2.3.33 The System must ensure that cancelled Group Records become past-date Group Records The System must provide the ability to fare-quote and ticket entire allotment or individual PNRs containing allotment space and/or additional segments, e.g. feeder-space The System must provide the ability to support the full manipulation and control (e.g. split) of inventory within a Group Record based on carrier specific rules The System must support functionality for Group Revenue Management System ( GRMS) to create new group bookings, show group bookings, suggest alternative bookings The System must provide the ability to synchronize all changed/modified Group Records to GRMS YES NO 10 8 YES 10 YES YES 10 10 The System must provide a special communication method between 5.2.3.34 agents and carrier GRMS, regardless of Group Record creation for the purpose of negotiation of group space and associated fares 5.2.3.35 5.2.3.36 The System must provide the ability to support synchronization of schedules and inventory data with GRMS The System must provide the ability to support queue placement on demand to GRMS for waitlisted Group Records (e.g. for review) NO 8 NO NO 8 8 The System must provide the ability to support revenue 5.2.3.37 management information in Group Record, with ability to be added manually The System must provide a mechanism which will reflect contract 5.2.3.38 information and rules negotiated between the carrier and the contracted customer Corporate Record must be linked to individual PNRs and their 5.2.3.39 respective Customer Records, if applicable, for the management and tracking of conventions and corporate accounts The System must provide the ability to manage modification and 5.2.3.40 source of modification in Corporate Record history YES 10 NO 6 YES YES 10 10 Requirements Confidential Proprietary Page 16 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability for cancellation of a Corporate 5.2.3.41 Record which may lead to a cancellation/re-pricing of associated PNRs, based on contractual obligations The System must ensure that cancelled Corporate Records become 5.2.3.42 past-date Corporate Records All components of the PNR/Corporate Record/Group Record/Corporate Record must be managed in the same format as 5.2.3.43 active PNRs/Customer Records/Group Records/Corporate Records and accessible within a system window preferable for 24 months (including the year of transaction) 5.2.3.44 The System must provide the ability to retain all components of past date PNRs in their respective Customer Record, if applicable YES YES 10 10 NO 6 NO 6 The System must provide the ability for automated process, which recognizes when travel has not been completed and sets indicator 5.2.3.45 in Customer Record. The associated unused ticket record is to be accessible via the Customer Record, based on carrier specific rules The System must support retrieval of individual PNRs/Customer Records/Group Records/Corporate Records for subsequent action 5.2.3.46 through structured data fields, including but not limited to frequent flyer number, phone number, ticket number The System must support retrieval of multiple PNRs/Customer 5.2.3.47 Records/Group Records/Corporate Records (via associated logical links) The System must support retrieval of all past date records, including PNRs which are not associated to Customer Records, through 5.2.3.48 structured data fields, including but not limited to unique identifier, flight information, name, date, phone number, ticket number The System must provide the ability to notify user when records in use by other users or the system (e.g. teletype updates) The System must provide the ability to retrieve and action 5.2.3.50 PNRs/Customer Records/Group Records/Corporate Records from a master query of travel records 5.2.3.49 Requirements NO 6 NO 6 NO 6 NO 6 YES NO 10 6 Confidential Proprietary Page 17 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support alerts/prompt upon retrieval, based on prompt criteria The System must provide the ability to retrieve a PNR via outside 5.2.3.52 source record locator The System must provide prompt when preference change has been made at time of retrieval of PNR/Customer Record for future 5.2.3.53 use (e.g. change in meal preferences within CRM, credit card expiration) and provide mechanism to transfer/apply new preferences to existing records 5.2.3.51 5.2.4 5.2.4.1 Reservation and Booking Process The System must provide the ability to manage sale of inventory using current and future interactive channels (e.g. VRU, CTI, call center, ATM, SMS, Web) The System must accept sale of inventory from outside channels via direct link or teletype messages with appropriate responses, if applicable (e.g. UC responses) The System must provide the ability to sell from all types of information sources such as tariff and availability and combinations thereof (e.g. round-trip availability) The System must provide the ability to sell from an automatically created source of flight options, based on shopper parameters and carrier specific rules The System must provide the ability to waitlist and overbook flights based on inventory, customer level and carrier specific rules The System must provide the ability to manually or automatically clear segments, based on change segment status functionality The System must provide the ability to add segments to an existing travel record NO NO 6 4 NO 6 YES 10 5.2.4.2 YES 10 5.2.4.3 NO 6 5.2.4.4 NO 8 5.2.4.5 YES 10 5.2.4.6 5.2.4.7 YES YES 10 10 The System must provide the ability to manage bookings of 5.2.4.8 individuals with partial different routings (e.g. party of 4 traveling on the same outbound with different return flights with a single entry) NO 6 Requirements Confidential Proprietary Page 18 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.4.9 The System must support canceling and rebooking inventory The System must include revenue management decision information within the flight segments (e.g. bid-price which lead to 5.2.4.10 confirmation of seat, O&D tracking information), based on carrier specific rules The System must support special action code to force a 5.2.4.11 confirmation, waitlist or priority waitlist for individual passengers at segment sell time The System must support special action code to identify a group 5.2.4.12 request, forced (confirmed and waitlist) group booking at segment sell time The System must provide the ability to automatically reorganize 5.2.4.13 segments in chronological sequence or allow manual rearrangement The System must provide the ability for canceling other carriers 5.2.4.14 space not actively held in the PNR using IATA AIRIMP standard communication (IX action code) 5.2.4.15 5.2.4.16 The System must support the removal of other carrier space, without sending a cancel message, based on carrier specific rules YES NO 10 8 YES 10 NO 6 YES 10 YES 10 YES YES YES 8 10 10 The System must provide the ability to manage marriage segment control and reflect indicator respectively in the PNRs The System must provide the ability to manually set or dissolve 5.2.4.17 married segment control logic and send subsequent NMC message, as defined by carriers specific rules 5.2.4.18 The System must support various types of inventory transactions, such as group space, exceptional bookings (e.g. stretcher) YES 10 The System must support recording, pricing and ticketing of 5.2.4.19 informational segments, which do not decrement inventory on other carriers regardless of booking source The System must provide the ability to include flight details by 5.2.4.20 segment, e.g. terminal information or check-in time YES YES 10 8 Requirements Confidential Proprietary Page 19 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.4.21 5.2.4.22 5.2.4.23 5.2.4.24 5.2.4.25 The System must provide the ability to sell from specific inventory/private classes on other carriers to support frequent flyer programs, entitlement program, ZED booking (e.g. special promo e.g. a free ticket out of a lottery) and marketing programs The System must provide the ability to allow frequent flyer partners to sell award inventory, based on carrier specific rules The System must provide the ability to sell from special inventory via identification of non revenue traveler (e.g. employee, vendor travel or marketing promos) The System must support standby listing, including support of schedule change The System must provide the ability to block inventory and seat assignments, based on operational needs (e.g. stretchers, crew rest, broken seats) YES 10 YES YES YES YES NO YES YES YES YES 10 10 10 10 6 8 10 10 10 5.2.4.26 The System must support bookings from crew scheduling system The System must support unique proprietary data elements and restricted remarks The System must support permanent remarks, which can never be 5.2.4.28 removed from the PNR The System must support temporary remarks, which can be 5.2.4.29 changed and removed from the PNR 5.2.4.27 5.2.4.30 The System must provide the ability to set reminders with free form text, including secured reminders for queue placement and review The System must support various ticket-related options for ticketing 5.2.4.31 deadlines and ticketing arrangements, e.g. ticket by mail, specific location, airport handling, revalidation The System must pro-actively support generation of customer 5.2.4.32 notification messages (e.g. flight alerts, travel advisories, schedule change) The System must provide the ability to create, send, receive and 5.2.4.33 action information (e.g. OSI, SSR) for specific business processes, e.g. airport ground handling YES 10 YES 8 YES 10 Requirements Confidential Proprietary Page 20 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support intuitive product for collection and standardization of information which is important/required for ground 5.2.4.34 handling and airport check-in (e.g. SSR, OSI, remarks, UM information), based on carrier specific requirements or business policy 5.2.4.35 The System must provide the ability to reflect payment indicators for miscellaneous fees in the PNR (for e.g SSR element in the PNR) The System must support collection and/or refund of miscellaneous product fees, including but not limited to UM, seat fee, name change YES 10 YES 8 5.2.4.36 NO 8 The System must support instant messaging of reservation 5.2.4.37 processing (e.g. while customer is on hold/enriched Call Center and IVRS) The System must provide an unique element to reflect involuntary 5.2.4.38 rebooking indicator (in the event of schedule change and/or irregularity) The System must reflect ticketless control/confirmation number in 5.2.4.39 PNR The System must provide the ability to associate/link existing 5.2.4.40 electronic ticket record to a new PNR The System must provide unique identifier for all travel records at 5.2.4.41 time of save and close The System must have the facility to transfer applicable data to 5.2.4.42 internal and external databases (e.g. customer database, ticketing database, revenue management) The System must allow third party processes for back office 5.2.4.43 systems (e.g. quality assurance) based on carrier specific rules The System must support automatic recap functionality to 5.2.4.44 summarize all actions and/or modifications (e.g. via IVRS) The System must support all ticketing rules including instant 5.2.4.45 ticketing and follow up documentation according to customer‟s preferred delivery method at time of save and close YES 10 YES YES YES NO YES YES NO NO 10 10 10 6 10 10 6 8 Requirements Confidential Proprietary Page 21 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide PNR validation and intuitive error assistance, e.g. validation of MCT/traffic restrictions and 5.2.4.46 enforcement of booking channel policies (e.g. inhibit mileage accrual for priceline bookings) 5.2.4.47 The System must provide flexibility to add additional validation rules 5.2.4.48 The System must enable PNR replication/cloning following Save and Close YES 10 YES YES 10 8 The System must have the facility to merge two Customer Records 5.2.4.49 if more than one Customer Record exist to a PNR based on multiple identification criteria (e.g. name, credit card, address, phone) 5.2.4.50 The System must provide the ability to disregard any changes made to an PNR prior to save and close, (e.g. seat assignment, inventory) NO 6 YES 10 The System must retain and apply previous entries to new 5.2.4.51 PNRs/Group Records (e.g. as a result of simultaneous changes, apply modifications to new PNR) The System must provide the ability to generate text message, voice 5.2.4.52 message, instant messaging, e-mail or any new communication devices, based on carrier specific rules The System must provide use preferred delivery method of 5.2.4.53 customer contact in language of choice, based on carrier specific rules The System must support acknowledgment (e.g. confirmation of 5.2.4.54 receipt) of customer notification and/or customer interaction (e.g. acceptance/denial of offering alternatives/options) 5.2.4.55 The system must support all PTA transactions GDS The System must have the capability to provide connectivity to all 5.2.5.1 the GDSs with whom the carrier has a Participating Carrier Agreement (PCA) 5.2.5 YES 10 NO 8 NO 6 NO YES 6 8 YES 10 Requirements Confidential Proprietary Page 22 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.5.2 5.2.5.3 5.2.5.4 5.2.5.5 The Carrier has the Participating Carrier Agreement with the following GDSs: Sabre Direct Connect Sell Galileo Interactive Sell Amadeus Access Sell Worldspan Direct Connect Sell Abacus Direct Connect Sell Axess Answerback Infini Full Availability Apollo Interactive Sell Topaz Access Sell Travel Sky Direct Connect Sell The System must provide Host to Host Direct connect level of participation to GDSs for real time Availability, Schedule and PNR display. The system must support the Type A (EDIFACT) and Type B connectivity with GDS for booking. The System must provide the ability to generate refund query, based on carrier specific rules YES 10 YES YES YES 10 10 10 The System must support products and links, including but not limited to: - Record locator return - Interactive sell - Seamless availability (100% and selective polling) - Interactive seat map - Interactive seat reservation 5.2.5.6 - Interactive passive validation - Married segment logic - Interline marriage - PNR claim - Push PNR - PNR synchronization - Mandatory fare quote - Journey data YES 10 Requirements Confidential Proprietary Page 23 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support “Claim PNR” from other carriers and 5.2.5.7 apply new PNR/Customer Record logic, based on carrier specific security rules The System must support “Push” of PNRs/Group Records to other 5.2.5.8 carrier or outside source (e.g. GDS) via IATA standardized messages The System must support all interactive products with other carrier 5.2.5.9 and GDSs or any other external systems Send and receive interactive requests and replies between other 5.2.5.10 carrier systems and GDSs or any other external systems 5.2.6 Seats YES 10 YES NO NO 10 8 8 The System must provide advanced seat request for all channels 5.2.6.1 (GDS, internet, call center), all/selected types of customers (first tier, second tier, no tier) and all/selected types of booking classes/fares 5.2.6.2 5.2.6.3 The System must provide intuitive functionality for requesting seat maps and seat assignments for change of aircraft/gauge flights The System must support functionality to accommodate seat maps and seat assignment for 3 digit row numbers YES 10 YES NO 10 8 The System must provide the ability to automatically block adjacent 5.2.6.4 seats for qualified customers in certain zones, including automated release of those seats, based on carrier specific rules The System must provide the ability to retrieve seat maps from an PNR seat assignment The System must provide the ability to retrieve all seat maps in the 5.2.6.6 same format, regardless of what is sent The System must provide the ability to retrieve real time dynamic 5.2.6.7 seat map with graphics by specific segment/flight/class/customer type The System must provide the ability to retrieve seat availability and 5.2.6.8 seat characteristics based on security/channel/customer type/booking class/fares/frequent flyer tier level 5.2.6.5 Requirements YES 10 NO NO YES 8 6 10 YES 10 Confidential Proprietary Page 24 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to retrieve seat map from 5.2.6.9 various types of flight related informational queries (e.g. availability/schedule) The System must provide the ability to receive and process 5.2.6.10 interactive seat map requests, as well as direct access display to and from outside sources like GDS or airlines The System must provide the ability to manage flexible seat 5.2.6.11 assignment to accommodate carrier specific rules, e.g. time restrictions or RBD The System must provide the ability to support seat assignments 5.2.6.12 across linked PNRs The System must provide the ability to manage seat requests for 5.2.6.13 marketing flights, operated by other carriers The System must provide the ability to manage seat inventory when 5.2.6.14 seats are assigned or cancelled 5.2.6.15 5.2.6.16 The System must provide the ability to automatically confirm seat requests or hold pending requests, based on carrier specific rules NO 6 YES 10 NO NO NO YES YES YES YES YES 8 6 8 10 10 10 10 8 The System must provide the ability to re-generate seat assignment to outside sources The System must support group seating without individual names, 5.2.6.17 based on carrier specific rules The System must provide the ability to waitlist automatically and 5.2.6.18 confirm seat assignment and requests, based on carrier specific rules 5.2.6.19 The System must provide the ability to assign, inhibit, modify and view specific and generic seats, based on carrier specific rules The System must provide the ability to send acknowledgement, that a seat is being held without disclosing the specific seat number. YES 10 5.2.6.20 5.2.6.21 NO YES YES 8 10 10 The System must support interactive seat assignment on other carriers based on bilateral agreements The System must provide the ability to process interactive requests 5.2.6.22 from outside sources like GDS or other airlines Requirements Confidential Proprietary Page 25 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.6.23 5.2.6.24 5.2.6.25 5.2.6.26 5.2.6.27 5.2.6.28 5.2.6.29 5.2.6.30 5.2.6.31 5.2.6.32 The System must support seat assignment on request/reply basis for other carriers not supporting interactive seats The System must synchronize data back to original booking source, when bookings originate outside source and seat is updated/entered by the carrier The System must support seat assignment preference as reflected in customer‟s Customer Record The System must support seat assignment, based on special service requests and/or seating restrictions (e.g. unaccompanied minors, wheelchair) The System must provide the ability to retain seat characteristics in the PNR to allow for re-accommodation processing (e.g. re-assign window seat, based on original preference) and forward for followup action, if applicable The System must support interactive seat inventory cancellation as well as non-interactive seat cancellation (e.g. at time of save and close), based on carrier specific rules The System must support cancellation and modification of seat assignments The System must support re-assignment of seats assignments across PNRs The System must provide the ability to retain original seat assignment when rebooking to different inventory class within the same cabin, based on carrier specific rules The System must provide the ability to automatically reinstate seat assignment in the event of involuntary changes, e.g. schedule change YES YES NO YES 10 10 8 10 YES 10 YES YES NO YES 10 10 6 10 YES 10 Special Services The System must provide the ability to automatically reflect ticket 5.2.7.1 number in the active PNR, when received via passive notification update messages 5.2.7 YES 10 Requirements Confidential Proprietary Page 26 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to manage SSR and OSI 5.2.7.2 information from outside booking sources to conform with Customer Record standard (e.g. ticket numbers, received via SSR TKNx) 5.2.7.3 5.2.7.4 5.2.7.5 The System must process and manage special service information requests (e.g. Ticket Number), received from third party The System must provide the ability to retrieve all segment related SSRs by specific segments The System must provide the ability to generate SSRs to third party bookings (e.g. SSR NAME, ADTK and others) The System must support functionality for inventory, pricing and ticketing, based on special service requirements (e.g. one passenger occupying more than one seat - EXST, CBBG) regardless of booking source The System must support input, additions, modifications, cancellation and deletion for all SSR elements as defined by IATA standard and/or any carrier specific SSRs (e.g. meals, fees, unaccompanied minors, wheelchairs, disabled customer) The System must support automatic reformatting to IATA standards to allow for future processing The System must support name and segment association, based on industry standards and bilateral agreements The System must provide the ability to auto-reject or accept requests from all channels based on carrier specific rules The System must provide the ability to identify and allow follow-up process for specific SSRs for manual handling (e.g. stretcher, oxygen equipment) NO 8 YES YES YES 10 10 10 5.2.7.6 YES 10 5.2.7.7 YES 10 5.2.7.8 5.2.7.9 5.2.7.10 5.2.7.11 YES YES YES YES 10 10 10 10 The System must provide functionality to set parameters for autoaction e.g. queue placement, authorization (customer upgrade in 5.2.7.12 advance, SSR clears upgrade within specific time rules), including customer notification, based on carrier specific rules, e.g. FQUG 5.2.7.13 The System must support interactive special service products (e.g. quota management for UMs , or pet in cabin) YES 10 NO 10 Requirements Confidential Proprietary Page 27 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Whenever a SSR UMNR has been entered, provide the ability to 5.2.7.14 prompt/flag, when escort data (EOA/EOD) is missing in PNR, at time of save and close The System must provide the ability to verify and enforce capacity 5.2.7.15 controls and/or restrictions based on carrier specific rules (e.g. pets, unaccompanied minors, meals) The System must support processing for complex SSRs (e.g. 5.2.7.16 electronic wheelchair, stretchers) The System must provide the ability to automatically retain or rebook SSR element in the event of schedule change (carrier driven) or a 5.2.7.17 rebooking to another class and/or flight (customer driven); synchronize with third party systems, when applicable The System must provide the ability to retain original SSR when 5.2.7.18 rebooking to different inventory class within the same cabin 5.2.7.19 The System must support cancellation and modification of SSRs 5.2.7.20 Reset capacity allotments upon cancellations 5.2.8 5.2.8.1 Frequent Flyer Customer Handling The System must provide the ability to view frequent flyer mileage account data, without any booking, based on carrier specific rules NO 8 YES YES 8 8 YES 10 YES YES YES 10 10 10 YES 10 The System must support link and dynamic search on frequent flyer 5.2.8.2 databases for the purpose of obtaining frequent flyer number, based on various data elements and carrier specific rules The System must support provision of either or both IATA standards 5.2.8.3 (Option 1: itinerary related and Option 2: segment related), based on carrier specific rules The System must support all accrual and redemption frequent flyer 5.2.8.4 products (e.g. companion travel, sponsoring) and provide the ability to add new products 5.2.8.5 The System must provide flexibility to create new frequent flyer tier levels and introduce new products (e.g. new types of upgrades) YES 10 YES 10 YES 10 NO 8 Requirements Confidential Proprietary Page 28 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to identify and provide preferred 5.2.8.6 customer benefits, based on tier level within frequent flyer programs (inventory booking guarantee, defined seats) The System must support application of all processes (validation, 5.2.8.7 recognition, accrual, redemption, upgrades), regardless of booking source The System must provide the ability to interactively enroll new members, based on data in the PNR (e.g. name, phone number, 5.2.8.8 address) and link to carriers frequent flyer system, based on carrier specific rules, The System must provide the ability to create Customer Records, 5.2.8.9 based on new enrollment information The System must provide the ability to interact with partner carriers frequent flyer systems and provide information of status (tier level) 5.2.8.10 to all business processes at time of segment sell, seat map and advance seat reservation The System must support recognition of all Global Alliance (like Star 5.2.8.11 / Oneworld / Skyteam) tier customers for the purpose of providing unique customer handling and benefits The System must support frequent flyer status at Customer Record 5.2.8.12 or PNR levels, based on carrier specific rules 5.2.8.13 The System must provide the ability to inhibit accrual/allow percent accruals based on carrier specific rules (e.g. priceline, award travel) The System must provide the ability to select frequent flyer program for mileage accrual by segment and/or trip. Provide handoff to appropriate databases in real time post departure (e.g. via FTL message), based on carrier specific rules The System must provide the ability to synchronize mileage accrual by segment and trip with appropriate databases, based on carrier specific rules The System must provide the ability to validate travel and handoff information for the purpose of retroactive credit accrual The System must provide the ability to validate eligibility against itinerary and mileage account YES 10 YES 10 NO 8 NO 8 YES 10 YES YES NO 10 10 6 5.2.8.14 YES 10 5.2.8.15 5.2.8.16 5.2.8.17 YES NO NO 10 8 8 Requirements Confidential Proprietary Page 29 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.8.18 5.2.8.19 5.2.8.20 5.2.8.21 5.2.8.22 5.2.8.23 5.2.8.24 5.2.8.25 5.2.8.26 5.2.8.27 5.2.8.28 5.2.9 The System must support sponsoring (e.g. pass on mileage award to other person), based on carrier specific rules The System must support verification of eligibility, calculation and deduction of miles from customers account for redemption at time of booking or ticketing, based on carrier specific rules The System must provide the ability to re-credit/void miles back to customers account at time of itinerary change/cancel, based on carrier specific rules The System must provide the ability to validate eligibility against itinerary and mileage account including class of service and frequent flyer tier level The System must support all upgrades types, including time initiated upgrades (e.g. FQUG) The System must provide the ability to grant award of mileage/upgrade, as per carrier specific rules (e.g. upgrade as a result of previous mishandling of passenger) The System must support access and viewing of electronic upgrades/awards (entitlements) via the Customer Record based on carrier specific and security rules The System must provide the ability to confirm upgrade to customer via SMS, email etc., The System must provide the ability to verify and calculate eligibility for upgrade at time of re-booking and synchronize deduction of miles from customer‟s account at time of ticketing, based on carrier specific rules The System must provide the ability to auto verify, calculate and synchronize deduction of miles from customer‟s account to accommodate award travel at time of upgrade and/or waitlist clearance The System must support all types of earned and purchased upgrades (paper or electronic) NO NO 6 8 NO 8 NO NO NO 8 8 8 NO NO 8 8 NO 8 NO 8 NO 8 General Third Party Processing The System must support parameters for automatically sending 5.2.9.1 messages regarding ticket deadline dates Requirements YES 10 Confidential Proprietary Page 30 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.2.9.2 5.2.9.3 5.2.9.4 5.2.9.5 5.2.9.6 5.2.9.7 The System must support ability to re-generate the PNR number (record locator) to outside sources The System must support ability to re-generate status (e.g. KK, KL, UC, UN) of to other carrier segment to a third party The System must support real-time synchronization products for all third party bookings The System must support all current and future interactive products with external booking sources and service providers The System must support processing of all follow up messages to/from external sources and service providers The System must support any booking created from outside source, in compliance with IATA standard/bilateral IATA standard or any future communication technology (e.g. XML) YES YES YES YES YES YES 10 10 10 10 10 10 The System must provide the ability to intuitively process incoming 5.2.9.8 messages and reject only those parts, that require additional intervention (e.g. create PNR and reject non-complaint SSR) The System must provide flexibility to handle rejects, based on parameters as outlined by carrier specific rules The System must provide diagnostic functionality, which provides 5.2.9.10 reject reason and date/time stamp The System must provide intuitive statistical and content/source 5.2.9.11 analysis of rejected messages, without interfering with message processing The System must provide the ability to capture and route reject 5.2.9.12 messages for robotic and manual processing including information about reject reason, based on carrier specific rules 5.2.9.9 5.2.9.13 5.2.9.14 The System must provide the ability for intelligent and efficient correction of rejected messages for final re-submission and action NO 8 YES YES NO 10 10 8 YES 10 NO NO NO 8 8 8 The System must provide a monitoring tool to identify source and methods of corrections, e.g. robotic vs. human The System must provide statistics regarding cause, source and 5.2.9.15 trends of rejected messages Requirements Confidential Proprietary Page 31 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to find and process any other 5.2.9.16 rejected messages from queue regarding the same PNR after the 1st rejected message has been handled The System must provide the ability to automatically identify and 5.2.9.17 correct multiple messages with same error logic The System must provide the ability to receive, validate, process and reflect PNM information in the corresponding active PNR(s) as 5.2.9.18 bilaterally agreed via interactive or teletype messages, as defined by carrier specific rules The System must provide the ability to process and add ticket 5.2.9.19 numbers, received via PNM and update active PNR The System must provide the ability to manage PNM and forward 5.2.9.20 for further action 5.2.10 History NO NO 8 8 YES 10 YES YES 10 10 The System must provide complete record (e.g. month, date, year, time, user) of all data transactions (original booking and all 5.2.10.1 modifications) and all modifications (including auto and manual queue placement) related to PNR/Customer Record/Group Record/Corporate Record retrievable in chronological order The System must provide the ability to retrieve and re-organize history by specific criteria (e.g. date, seats, flight number) The System must provide the ability to retain inbound/outbound 5.2.10.3 message traffic that updates a PNR. Message retrieval must be based on communication reference in PNR history. 5.2.10.2 5.2.11 Queries of Travel Records YES 10 YES NO 10 8 Requirements Confidential Proprietary Page 32 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to query travel records, based on a specified criteria and/or Customer Record/PNR/Group Record/Corporate Record data elements, e.g. Organize PNRs by frequent flyer tier status or show Customer 5.2.11.1 Records by Corporate Record corporate contract number - Show misconnections due to flight irregularities operations - Organize employee‟s boarding priority and/or date of hire by flight, based on carrier specific rules - Show cancelled PNRs, based on specified criteria (e.g. flight, date) YES 10 Block Space The System must provide functionality to block, auto-quote and ticket for a single passenger, holding multiple inventory space and 5.2.12.1 seats (e.g. for additional seats for stretcher, cabin baggage) and reflect to all appropriate processes (e.g. do not count as multiple passengers) 5.2.13 5.2.13.1 5.2.13.2 Quality Assurance-Revenue Integrity The System must enable carrier notification for PNR (linked to associated Customer Record) resulting in back-to-back ticketing 5.2.12 YES 10 NO NO YES 6 8 10 The System must provide the ability to inhibit multiple speculative bookings (less than 9) The System must provide the ability to support quality assurance as 5.2.13.3 well as providing identification and placement for follow-up action, based on carrier specific rules Prevent/monitor inventory abuse, including but not limited to: - Duplicate bookings, dummy bookings 5.2.13.4 - Repetitive sells and ignore/cancel - Blocking of booking source 5.2.13.5 The System must provide the ability to check duplicate bookings. YES 10 YES 10 Requirements Confidential Proprietary Page 33 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to auto-cancel duplicate bookings, based on carrier specific rules The System must provide an intuitive logic to identify similar names 5.2.13.7 and/or bookings, based on various criteria The System must provide the ability to support automated and manual duplicate booking check with ability to forward for follow-up 5.2.13.8 action, based on carrier specific rules (e.g. as soon as flight gets critical) The System must use customer centric approach, to allow or inhibit 5.2.13.9 booking of duplicate space (e.g. based on tier level) 5.2.13.6 5.2.13.10 The System must provide the ability to inhibit confirmation of duplicate space at time of booking, based on carrier specific rules YES YES 10 10 YES 10 YES NO 8 8 The System must provide the ability to automatically and/or 5.2.13.11 manually identify and manage fictitious names (e.g. Mickey Mouse, Test), based on carrier specific rules The System must provide the ability to search and identify abuse in 5.2.13.12 holding space (e.g. repetitive bookings) The System must p have the ability to identify no-show passengers 5.2.13.13 and auto-cancel onward and/or return reservations, based on check in information , based on carrier specific rules The System must provide the ability to search and auto-cancel 5.2.13.14 PNRs, that have not been ticketed and/or paid for, based on carrier specific rules Ground Handling Support Products The System must provide the ability to receive/ generate PNL/ADL 5.2.14.1 for ground handling support 5.2.14.2 The System must provide the ability to send and process any post departure message to multiple addresses (e.g. FTL, PFS,ETL) 5.2.14 YES YES YES 10 10 10 YES 10 YES YES 10 10 The System must create new Customer Record and/or link PNR to 5.2.14.3 Customer Record in case of being ground-handled by other carrier upon receipt of FTL message YES 10 Requirements Confidential Proprietary Page 34 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to transfer payment indicators for miscellaneous fees from the PNR to the PNL The System must update carrier frequent flyer databases with enriched customer information after customer has boarded a flight, 5.2.14.5 based on carrier specific rules Note: Enriched data may include, but is not limited to reservation channel, kiosk, electronic ticketing 5.2.14.4 The System must collect and manage customer (security) 5.2.14.6 information in the Customer Record/PNR and provide to ground handling, based on carriers specific rules and/or business policy 5.2.14.7 5.2.14.8 5.2.14.9 5.2.14.10 5.2.14.11 5.2.15 Ability to override auto-generated process (time or information dissemination) The system must support TIMATIC both through the host and website/ Credit Card approval facility The system must have links with the World Baggage Tracer system etc The system must support integration of Baggage Management System with RFIDs The system must have the ability to interface with any CRM or any other passenger profiling software Passenger Lists YES 10 YES 10 YES 10 YES YES YES NO YES 10 10 10 8 8 Requirements Confidential Proprietary Page 35 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must generate the following( but not limited to) lists: - Boarding Lists - Through List - Terminating List - Duplicate Bookings - Meal Service Lists - Passengers with active auxiliary service elements. - List of passengers whose names begin with 1 or 2 specified characters - List of passengers in a group of not less than specified number of passengers - Booked passengers with confirmed reservations (HK, KK, KL, RR). - All passengers, regardless of segment status. - Groups for which all names have been advised. - Incomplete Groups - Include block seat 5.2.15.1 - Airport ticket ticketing arrangement - Groups (group name only) - Groups (group and passenger name) - Passengers holding inbound connections to the flight - Passengers with ASR elements - Passengers with advance boarding pass authorization - Passengers with advance boarding pass issuance - Last booked passengers based on in order - Passengers with special meals - Passengers with active OSI elements - Includes any AUX, SSR, or OSI element of selected passengers in the list - Passengers holding outbound connections from this flight - Reconfirmed passengers - Passengers with active SSR elements - Passengers with specific SSR elements like FQTC, PETC, CHML, WCHR etc YES 10 Requirements Confidential Proprietary Page 36 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must generate a Transfer Lists containing the number, or numbers of and the names of all passengers transferring between flights. Four types of transfer lists must be provided: 5.2.15.2 - From any flight to a specific flight - To any flight from a specific flight - To a specific flight from one, two, or three specific flights - From a specific flight to one, two, or three specific flights YES 10 5.3 5.3.1 5.3.1.1 Schedules and Availability General The System must provide flight record information at the time of creation or modification of the PNR The System must support processing of incoming and outgoing IATA standard schedule and availability messages (AVS / AVN / RAS / MAS / AVS Avail / PAOREQ / PAORES / ASM / SSM /SSIM/ ASC) The System must provide various forms of recap capabilities The System must provide the ability to validate incoming schedule and availability messages and redirect those that cannot be processed on carrier specify rules The System must provide the ability to create and modify all schedules and availability reference data and business rules by flight/date range, time, frequency, and O&D, by effective and discontinue dates YES 10 5.3.1.2 5.3.1.3 5.3.1.4 YES YES YES 10 10 10 5.3.1.5 YES 10 The System must provide the ability to dynamically update basic 5.3.1.6 schedules and availability reference data (e.g. UTC, Airport codes, MCT, check-in deadlines, baggage acceptance, pets) The System must provide the ability to easily retrieve basic 5.3.1.7 schedules and availability reference data (e.g. MCT, check-in deadlines, meals, in-flight entertainment) YES 10 YES 10 Requirements Confidential Proprietary Page 37 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.3.1.8 5.3.1.9 5.3.1.10 5.3.1.11 5.3.1.12 5.3.1.13 5.3.1.14 5.3.1.15 5.3.1.16 5.3.1.17 5.3.1.18 5.3.1.19 5.3.1.20 5.3.1.21 The System must provide the ability to record and access schedule and availability statistical data The System must provide the ability to track history of customer queries and availability displayed for strategic planning/ decision purposes The System must provide a current report of inbound and outbound connections on a particular flight The System must provide manual intervention at any time during automated schedule and availability processes The System must provide system defaults for schedule and availability queries (e.g. - location, time, date default) The System must provide PNR information (e.g. ticketed/unticketed bookings including revenue generated on a flight/date range/flight range) for use in passenger re-accommodation, and schedule change processes The System must provide the ability to manage and apply check-in times based on location parameters for use in PNR, FLIFO (e.g. – airport, off-airport, home) The System must provide the ability to access other airlines schedules and availability information The System must provide the ability to manually add free-form information to PNRs related to specific flight and date ranges and queue to booking source The System must provide the ability to retrieve availability for auxiliary services information e.g. car, hotel and tour products The System must provide the ability to control schedules and availability products and functionality for other airlines (e.g. interactive availability, numeric availability, basic availability) The System must provide for direct access availability, FLIFO, Fares, DRS (e.g. – GDS or OA reservation system) The System must provide ability for all schedules and availability information to interface with all present and future distribution channel The system must provide facility of search by first available by forward / backward number of days vis a vis current day. NO NO YES YES YES 4 4 8 10 8 NO 10 NO YES NO NO YES YES YES YES 8 10 4 4 8 10 10 10 Requirements Confidential Proprietary Page 38 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide complete list of various types of 5.3.1.22 availability displays i.e. availability by date / day / week / flight number / class / time / fare / fare rules etc. The system must have the facility to provide first / last flights of the 5.3.1.23 day to any city / airport in the schedule/available display The system must have provision to provide terminal information for 5.3.1.24 a particular flight in availability/schedule display The system must have the provision for Repetitive PNR creation as 5.3.1.25 per day / date range / week etc. 5.3.2 5.3.2.1 5.3.2.2 5.3.2.3 5.3.2.4 5.3.2.5 5.3.2.6 Schedule Creation & Distribution The System must adhere to all aspects of IATA SSIM standard for schedule distribution The System must provide for a fully dated schedule for the length of the system window, minimum of 340 days The System must provide automated process for the creation of flight records (e.g. – flight details for each flight date) The System must support sell date with all related applications (e.g. schedules, availability) The System must identify discrepancies between schedule availability and fares (e.g. – new flight created with no fares loaded) YES YES YES YES 10 10 10 10 YES YES YES YES NO YES 10 10 10 8 8 10 The System must support a minimum of 6 alphanumeric characters for flight number assignment The System must provide the ability to create and modify carrierspecific tables for O&D, flight number, flight ranges, and effective & 5.3.2.7 discontinue dates for different purposes (e.g. Queuing, default classes, class mapping) The System must support various service types of passenger flights including, commuter, charter, low-cost carrier operations, as well 5.3.2.8 other modes of transportation that may or may not appear in the schedule The System must provide the ability to display all legs and segments 5.3.2.9 of a flight immediately after creation YES 10 NO 6 YES 10 Requirements Confidential Proprietary Page 39 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to display connections to a 5.3.2.10 newly created flight immediately after flight creation (including a new O&D) The System must provide the ability to process at any time, a fully 5.3.2.11 dated schedule and corresponding re-accommodation processes within 6-8 hours real time The System must provide the ability to handle and identify weight 5.3.2.12 load restrictions and passenger weight exception by market and flight date/range The System must support all types of flights including multi-leg, circle, funnel, codeshare, wet-lease, dry-lease, lollipop, round robin 5.3.2.13 sterile and change of gauge (subject to government restrictions) and multiple marketing flights on these flight types The System must have the capability to load flights (e.g. SSIM, OAG 5.3.2.14 and OAL files) other Airlines The System must support system window for availability, inventory 5.3.2.15 and reservation information of greater than 340 days (e.g. ability to book 500 days in advance) The System must provide a standard interface with schedule 5.3.2.16 planning systems for schedule updates up to departure (SSIM chapter 4/5/7/8) The System must ability to handle open end periods (dates through 5.3.2.17 infinity) 5.3.2.18 The System must handle arrival/departure day change +2/-1 The System must support the grouping of compartment codes and 5.3.2.19 RBDs The System must provide the ability to retrieve the source of 5.3.2.20 information for the construction of the flight records The System must provide the ability to load flights into the system 5.3.2.21 and to control access by user group or work function The System must support schedules for regional / feeder carriers 5.3.2.22 under their own carrier code and flight range The System must support schedules for codeshare on regional 5.3.2.23 partners, wetleases and virtual airlines (e.g. multiple carriers that operate under one designator code) Requirements YES 10 YES 8 YES 8 YES 10 YES NO 10 10 NO YES YES YES YES YES YES YES 10 10 10 10 6 8 10 10 Confidential Proprietary Page 40 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.3.2.24 5.3.2.25 5.3.2.26 5.3.2.27 5.3.2.28 5.3.2.29 5.3.2.30 5.3.3 5.3.3.1 The System must validate traffic restrictions for any follow-up process (e.g. connection build, segment sell, ticketing) The System must provide the ability to display operating flight ranges and associated marketing flight ranges and vice versa The System must handle all aircraft subtypes and general types and translate subtypes into general when retrieved by travel agents, other systems The System must provide the ability to create flights that may or may not be optimized by the revenue management systems The System must provide automatic creation of inventory with no restrictions on the numbers of legs, segments, classes/buckets from flight records and reference data The System must provide the ability to retain a record of all AVS messages sent and received to/from other carriers The System must support other carrier inventory and availability records for AVS processing, quota sales and other messages Schedule Update The System must provide automation of schedule change processing and all associated data (e.g. - seat maps, seat assignments, SSRs) The System must provide on-line access for duration of the system window, with a minimum of 12 months of historical schedule information including schedule changes The System must provide quality assurance functionality to validate and identify discrepancies in schedules between the host and external systems The System must provide various methods of monitoring and controlling the schedule change process (e.g. to stop, delay, change sequence or priority) The System must provide the ability to control the generation of AVS messages upon receipt of ACK messages in conjunction with schedule change activity YES YES YES NO NO NO YES 10 10 10 6 8 6 10 YES 10 5.3.3.2 YES 8 5.3.3.3 NO 10 5.3.3.4 YES 8 5.3.3.5 YES 10 Requirements Confidential Proprietary Page 41 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to run multiple real time 5.3.3.6 schedule changes in parallel (e.g. seasonal and ad hoc changes simultaneously) The System must support 24/7 real-time schedule update 5.3.3.7 capabilities for the entire system schedule window The System must provide the ability to send and request SSIM 5.3.3.8 recap to/from other systems for entire schedule or single flights (elimination of manual GDS updates) The System must provide the ability to use inventory data to support 5.3.3.9 / transfer / connect revenue management data from old to new flights in the event of schedule change The System must support automated process to update airport 5.3.3.10 terminal IDs by O&D, flight range, date range and other carrier specific rules The System must ensure that schedule change process must not 5.3.3.11 inhibit sales activities or flight optimization by revenue management systems The System must provide the ability to re-accommodate or not all 5.3.3.12 flight types, operating / marketing, commuters, on direct, connecting or on the same flight in different RBDs The System must provide the ability to automatically or manually reaccommodate all passenger types (e.g. single passenger, linked 5.3.3.13 passengers, groups, negotiated/block space, waitlist, confirmed, request space, space available, positive space) with different processing based on passenger types and carrier specific rules The System must provide the ability to re-accommodate marketing 5.3.3.14 passengers on the carrier operating flight subject to carrier specific rules The System must provide the ability to pre-determine passenger re5.3.3.15 accommodation before schedule change occurs (manual intervention vs. automated processes) The System must provide for consideration of married segment 5.3.3.16 logic during passenger re-accommodation YES YES YES 10 10 10 YES 8 YES 8 YES 10 YES 10 YES 10 YES 10 YES YES 10 10 Requirements Confidential Proprietary Page 42 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.3.3.17 5.3.3.18 5.3.3.19 5.3.3.20 5.3.3.21 5.3.3.22 The System must support flexible re-accommodation window (+1/-1 day, +1/-1 week, etc.) based on carrier specific rules The System must provide the ability to initiate waitlist clearance upon completion of passenger re-accommodation The System must perform PNR analysis, customer value analysis and alternate flight inventory analysis as part of the reaccommodation process The System must allow for one flight to be re-accommodated to multiple flights and vice versa (IROP) based on carrier/passenger specific criteria The System must store historical passenger re-accommodation information and make it accessible through PNR, and through active or historical flight and inventory records The System must provide passenger re-accommodation undo functionality, including sending ASC messages (identify affected PNRs, reverse change and advise) YES YES NO 10 10 6 YES 10 YES 10 NO 6 The System must provide the ability to reinstate inventory and PNR 5.3.3.23 segments resulting from a schedule change, on both operating or marketing flights that have their corresponding flights reinstated The System must provide full passenger re-accommodation 5.3.3.24 summary report based on carrier specific rules (e.g. following a schedule change, manual re-accommodation) The System must provide the ability to have all related service requests transferred according to flight specifications and 5.3.3.25 notification sent to the booking source when applicable or notification sent to a predetermined address when unable The System must maintain all ticketing and fare associated 5.3.3.26 information and notification issued 5.3.3.27 The System must support temporary schedule changes without modifying an PNR until completion of the process (e.g. park PNR) YES 8 YES 10 YES 6 YES NO 10 8 Requirements Confidential Proprietary Page 43 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.3.3.28 5.3.3.29 5.3.3.30 5.3.3.31 5.3.3.32 The System must provide an automated process to re-seat passengers upon completion of a schedule and/or equipment change based on retained seat characteristics in PNR, Customer Record preferences and other carrier-specific rules (e.g. fare level, FQTV status, O&D, time before departure). The System must provide the ability to identify the first available alternate flight with or without re-accommodation The System must provide the ability to re-accommodate to different booking classes and cabins based on carriers specific rules (e.g. Fare level, FQTV status, O&D, change of gauge, reference to class re-booking rules) The System must provide a manual entry for re-accommodation of segments and seat assignments The System must provide automated adjustment of inventory upon completion of schedule changes and advise revenue management systems based on carrier specific rules The System must provide the ability to control and identify potential overbooking situations resulting from planned schedule changes YES 10 YES 10 YES 10 YES YES 10 8 5.3.3.33 NO 6 The System must provide for passenger re-accommodation 5.3.3.34 information delivery by all current and future methods (e.g. e-mail, text message, wireless, fax, telephone) The System must provide the ability to produce one notification 5.3.3.35 message for several PNR segments affected by a single change or affected by multiple schedule changes over a specified period The System must provide the ability to have automated schedule 5.3.3.36 change messages redirected, deferred or inhibited (e.g. notification to be sent to a specific Call Centre) The System must provide the ability to control the generation of ASC 5.3.3.37 messages in conjunction with schedule change activity (e.g. defer the sending of ASC with a trigger mechanism) The System must provide the ability to update a MCT and check-in 5.3.3.38 times and to notify affected passengers The System must support passenger notification of airport terminal 5.3.3.39 change Requirements YES 10 NO 4 NO 6 NO YES YES 8 8 8 Confidential Proprietary Page 44 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide for the use of free form messages to PNR in order to advise schedule change related information The System must provide for schedule change indicator to be 5.3.3.41 automatically added to the PNR 5.3.3.40 5.3.3.42 The System must provide the ability to flag and action prior to PNR update, when suggested re-accommodation is inaccurate or illogical YES YES NO 10 10 4 The System must provide the ability to see where messages were 5.3.3.43 sent for passenger re-accommodation (e.g. booking source, call center, queue) The System must provide the ability to automatically default 5.3.3.44 notification to booking source or to re-direct to an alternate address for special handling Seat Maps The System must provide the capability to build or delete a seat map based on a variety of technical, business and legal 5.3.4.1 requirements. Must include the ability to assign specific characteristics to seats / rows (e.g. airport protected seats, crew seats, blocked/soft-blocked seats, exit row) 5.3.4.2 5.3.4.3 The System must support flexible cabins and cabin sizes including but not limited to moveable class dividers or convertible seats 5.3.4 NO 4 YES 8 YES 10 YES NO YES YES YES YES 10 4 10 10 10 10 The System must provide the ability to support flexible seats (e.g. 3 economy seats becomes 2 business seats) The System must support seat maps for change of gauge, round5.3.4.4 robin and funnel flights 5.3.4.5 5.3.4.6 The System must provide the ability to maintain dynamic individual seat maps, by aircraft type and sub-types and by flight date The System must provide the ability to control all advance seat reservations for specific flights based on the current seat maps The System must provide the ability to retrieve the characteristics of 5.3.4.7 each seat (e.g. seat blocked/broken, cabin baggage, soft-hold for incomplete party) Requirements Confidential Proprietary Page 45 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.3.4.8 5.3.4.9 5.3.4.10 5.3.4.11 5.3.4.12 5.3.4.13 5.3.4.14 5.3.5 The System must provide the ability to support seat map for other modes of transportation The System must support the retrieval of a variable seat map based on POS, customer information or other carrier specific rules (e.g. FQTV, fare level) The System must provide easy access to seat map from availability retrieval The System must provide the ability to retrieve and segment sell from a seat map The System must provide the ability to create a segment based on a seat request The System must provide the ability to interactively retrieve marketing & operating flight seat The System must provide the ability to inhibit advance seat selection and seat map retrieval based on carrier specific rules NO NO NO NO NO YES YES 2 8 4 4 4 10 10 Basic Availability The System must provide the ability to support at minimum: travel option number, carrier code, flight number, classes of service and available seats, board/off points, departure/arrival times, date/date 5.3.5.1 change indicator, equipment type (including change of gauge), electronic ticketing indicator, codeshare disclosure information, marketing/branding messages, operational statistics, traffic restrictions, type of access The System must provide the ability to create availability information 5.3.5.2 by citypair. Flight numbers would be required for segment sell transactions. 5.3.5.3 5.3.5.4 The System must provide the ability to support the option to retrieve interline connections based on OAL and/or pro-rate agreements YES 10 YES 10 YES YES YES 10 10 10 The System must provide the ability to support for both dynamic and pre built connection construction The System must provide automatic routing selection. The system 5.3.5.5 must be able to select the best routing available for neutral availability request Requirements Confidential Proprietary Page 46 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.3.5.6 5.3.5.7 5.3.5.8 5.3.5.9 5.3.5.10 5.3.5.11 5.3.5.12 5.3.5.13 5.3.5.14 5.3.5.15 5.3.5.16 5.3.5.17 5.3.5.18 5.3.5.19 5.3.5.20 The System must provide support for multi-airport cities for availability and connections (e.g. LGW & LHR, LGA & JFK) The System must support overnight layover connections The System must provide access to various availability requests (carrier-specific, internal, alliance, redemption, neutral, direct access, groups) by characteristic sorting The system must have the ability to set AVS thresholds by flight class, date range, O&D with manual update capability 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) The System must have no limitation to the number of available seats displayed based on carrier specific rules or the resulting inventory calculation upon receipt of an incoming AVS message The System must provide the ability to specify connect points, include/exclude airlines as options with basic availability entry The System must provide the ability to group airports to families for availability displays (e.g. pax want to go to South Florida, can group MIA, FLL, PBI in one retrieval request) The System must provide availability for past flights at close-out and for duration of the system window (greater than 350 days) The System must support availability retrieval with no limitation on the number of travel options and no limitation on the number of segments The System must support industry discount travel availability referencing employee information The System must provide an automated retrieval of alternate availability information following unsuccessful sell attempt The System must provide an availability retrieval by fare range and sorting by price range The System must provide the ability to request availability based on repeat trip patterns based on past or future travel Have the ability to provide traffic restriction information with an availability retrieval YES NO YES YES YES 10 8 10 10 10 YES YES NO NO NO NO YES NO NO YES 10 8 6 4 4 4 10 8 4 10 Requirements Confidential Proprietary Page 47 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.3.5.21 5.3.6 5.3.6.1 5.3.6.2 5.3.6.3 5.3.6.4 5.3.6.5 5.3.6.6 5.3.6.7 The System must provide the ability to regularly load industry standard MCT files with effective and open for sale dates Availability Information The System must provide the ability to retrieve the schedule/timetable of one or more carriers operating on a specific route, including period of operation The System must provide the ability to simultaneously retrieve outbound, inbound, round-trip and continuation availability The System must provide the ability to control availability retrieval based on specific preferences (e.g. time, connection point, direct, non-stop, aircraft type) The System must provide the ability to retrieve all or only available flights/classes The System must provide the ability to perform an extended availability search for next available travel option(s) over a specified period The system must have no limitation on the number of classes per flight item The System must provide the ability to control the retrieval and sale of flights/booking classes by POS, O&D, journey data and passenger details/profile The system must include all information from the flight record plus general information (free form text) in the availability retrieval YES 10 YES NO YES NO YES NO YES 10 8 10 8 10 10 10 5.3.6.8 5.3.6.9 YES YES NO NO 10 10 8 8 The System must provide controls for selection of marketing carriers to be retrieved on an availability request The System must provide the ability to retrieve flight availability and 5.3.6.10 fare information simultaneously 5.3.6.11 The System must support integrated fare-based and/or inventorybased availability requests (availability based on fares basis) The System must support the emulation of an availability retrieval 5.3.6.12 based on POS or other business rules (e.g. FQTV status, user security access) Requirements YES 10 Confidential Proprietary Page 48 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.3.6.13 5.3.6.14 5.3.6.15 5.3.6.16 5.3.6.17 5.3.6.18 5.3.6.19 5.3.7 Have the capability to reply to a direct access request from a GDS or OAL The System must provide carrier specific availability by POS (e.g. internet sites) The System must provide the ability to control the availability information by flight priority, flight range, POS, market and rule The System must provide the ability to obtain and modify the rules governing the availability information retrieved The System must provide for free form text information without affecting the number of flight items retrieved The System must provide the ability to retrieve charter and other non-schedule flights in a separate availability request The system must have no limitation to connect points per O&D YES YES YES YES NO NO NO 10 10 10 10 4 2 6 Interactive Availability The System must support the capability to interactively poll an other 5.3.7.1 airlines carrier for flight availability status The System must support selective polling (the ability to offer 5.3.7.2 Seamless Availability on selected flights, AVS; MR/MA) The System must support seamless availability with the GDSs and 5.3.7.3 other carriers. 5.3.7.4 5.3.7.5 5.3.8 5.3.8.1 The System must provide the ability to control the time window of sending AVS to other systems (e.g. 340 day window for GDS) The System must provide the ability to retrieve block/allotment availability owned by a specific POS Interactive Redemption Availability The System must provide redemption availability and upgrade availability for other carriers including extended search capabilities YES YES YES YES YES 10 10 8 10 10 NO 8 The System must provide the flexibility to control the redemption 5.3.8.2 availability information offered to the partner carriers based on frequent flier program agreements and carrier specific rules NO 8 Requirements Confidential Proprietary Page 49 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.3.8.3 5.3.8.4 5.3.8.5 5.3.9 5.3.9.1 The System must provide the ability to obtain direct access redemption availability from other carriers The System must support carriers mileage accrual and redemption ("earn & spend”) information available by flight and O & D The System must provide interactive access to carrier frequent flyer database for availability information FLIFO All flight record information must be available for FLIFO retrieval and easily understandable (e.g. SSIM traffic restriction 8/A is decoded as “No Local Traffic”) The System must provide the ability to retrieve flight-specific products and services, preceded by availability retrieval or PNR segment The System must provide the ability to control & modify FLIFO retrieval by POS (e.g. movies, products) The System must provide the ability to retrieve FLIFO historical and current information for the entire system window The system must provide the ability for other carriers to access flight information by direct access The System must provide real-time updates from other carrier operational systems (e.g. MVT) to update FLIFO information and PNRs FLIFO information must be accessible through all existing and future mediums (e.g. Web, WAP, fax) NO NO NO 8 8 8 YES 10 5.3.9.2 5.3.9.4 5.3.9.5 5.3.9.6 5.3.9.7 5.3.9.8 YES YES YES YES YES YES 10 8 10 10 10 10 5.4 5.4.1 Flight Inventory General Requirements Requirements Confidential Proprietary Page 50 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide inventory control capability for the carrier with further capabilities to interface with the 5.4.1.1 PSS platform of NACIL‟s regional/feeders operating under their own carrier code and/or flight range to provide interline e-ticketing, code share, through check-in etc The system must have the capability of creating Master Data tables for complete airline operations including inventory management of its flights as related to the PSS including but not limited to: - Equipment types with Compartments & Different Configuration for same A/c type - Percentage Control Table (PCT ) to change the values of inflation(Authorization Levels) on a flight at pre defined time periods - Route profile Table with flights clubbed route wise for route analysis activity - Region profile tables created for route analysis of flights clubbed 5.4.1.2 region wise. - City Pair tables - Wait list capping tables - MCT tables - SSIM/ASM/SSM tables - SMT tables - Telegraphic Address Tables - Group address Tables - O & D tables - DEI table The system must provide inventory with unlimited aircraft configurations within the same aircraft type 5.4.1.4 The system must support more than 5 legs per flight 5.4.1.3 The System must provide availability status from the carriers to third 5.4.1.5 parties (push or pull) to reduce the "look to book" ratios (e.g. caching channels). Ensure that O&D control integrity is maintained. YES 10 YES 10 YES YES NO 10 10 6 Requirements Confidential Proprietary Page 51 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.4.2 5.4.2.1 5.4.2.2 5.4.2.3 5.4.2.4 5.4.2.5 5.4.2.6 Flight Inventory Control The System must provide the ability for O&D (bid pricing), leg, and segment control that meet the needs of O & D revenue management systems The System must provide integration with the PROS Revenue Management system or any other Revenue Management system with O & D and network perspective The Vendor must provide integration with the Revenue Management as and when updated The System must provide the ability to set leg allocations by class at the flight leg level over a date or date range The System must provide the ability to set segment allocations by class at the flight leg level over a date or date range The System must provide the ability to set nested \segment limits (e.g. minimum, maximum) at the flight segment level over a date or date range YES 10 YES YES NO NO YES 10 10 10 10 10 The Inventory system must support Leg control, Segment control and both Leg and Segment control in a single flight with : 5.4.2.7 - Point of sale control - Market Control - Control by Origin & Destination The System must provide all nesting features viz. - Parallel Nesting - Virtual nesting - Serial Nesting - O & D Control 5.4.2.8 - Yield Management - Early Start / Late End - Minimum Booking Protection - POS aggregate - Bid price control - Group management The system must support minimum 26 numbers of Prime classes / 5.4.2.9 RBD‟s & 99 subclasses Requirements YES 10 YES 10 YES 10 Confidential Proprietary Page 52 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.4.2.10 5.4.2.11 5.4.2.12 5.4.2.13 5.4.2.14 5.4.2.15 5.4.2.16 5.4.2.17 5.4.2.18 Store the following information in the inventory record at flight leg/segment date level: - Schedule data (e.g. capacity, routing, flight number) - Inventory control parameters (e.g. authorized levels, protects/reserves, forecasts, waitlist indicators, wholesaler block space, class or nesting block bid price data, cabin displacement cost) - Booking data (e.g. confirmed, waitlisted, on request bookings for individuals, groups, and block seats) The System must ensure that the RMS system response matches the originating request from the inventory system The System must support ability to control inventory for a variety of flight types including direct, non-stop, multi leg The System must provide inventory controls for non-airline configuration like surface transport The System must allow 4 digit authorized levels and booking counts (e.g. A380 aircraft) The System must allow different cabin structures on each leg of a multi-leg flight (e.g. change of gauge, common leg, funnel flight) The System must support 1 and 2 digit alpha-numeric internal inventory classes The System must support nesting of inventory classes or buckets at the flight leg/segment level The System must support linear, parallel, and hybrid inventory class or bucket nesting structures at the flight leg/segment level and their combinability on single flight The System must provide the ability for different methodology for availability increment/decrement (top down nesting vs. bottom up nesting) The System must allow different booking class structures on each segment of a multi-leg flight The System must support convertible seat equipment (CVS) and movable class divider (MCD) on each leg as well as in a compartment / nesting block YES 10 YES YES NO NO YES YES YES YES 10 10 2 4 10 10 10 10 5.4.2.19 5.4.2.20 5.4.2.21 YES NO NO 10 6 4 Requirements Confidential Proprietary Page 53 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide ability to handle weight restrictions and 5.4.2.22 reduce seats available for sale based on load control (weight & balance requirements The System must provide ability to handle crew rest seats based on 5.4.2.23 carrier specific rules The System must provide ability to identify seats blocked for special 5.4.2.24 cases (e.g. stretcher, inoperable seats) and distinguish these from other revenue passengers Inventory Control Parameters The System must provide an automated update of inventory data 5.4.3.1 whenever inventory control parameters are changed The System must support various control parameters to allow flexibility and reduce the need for exception coding: - Airline core / generic airline parameters (e.g. inventory activation settings, bid price vs. virtual buckets or both) - Parameters for each GDS and other partners (e.g. marriage logic, electronic ticketing, rerouting or cascading codeshare methodology, 5.4.3.2 codeshare class conversion) - Parameters to control functionality (e.g. numeric AVS, marriage logic parameters, O&D control logic, segments excluded from O&D logic, joint O&D participation) - Availability modifiers (e.g. POS, customer value, strategic modifiers) The System must support parameters to provide selective availability by: 5.4.3.3 - POS (PCC, country, region, vendor, etc.) - Market hierarchy structure (flight/leg/date) - Class grouping 5.4.3.4 The System must provide the ability to update any O&D inventory control data with data from the revenue management system 5.4.3 YES YES YES 10 10 10 YES 10 NO 10 YES 10 YES 10 The System must provide class mapping rules for partner carriers 5.4.3.5 by O&D/market region/POS for product mapping across interline (codeshare) itineraries Requirements NO 10 Confidential Proprietary Page 54 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide functionality to close out inventory on a 5.4.3.6 partner marketing flight number for a cabin, nesting block or class level The System must provide ability to limit frequent flyer redemption 5.4.3.7 buy up by O&D, flight number, travel date, and days prior to departure The System must provide ability to limit frequent flyer redemption 5.4.3.8 based on RPMs (indicator to shut off all redemption bookings for a specific travel period) Availability / Sell Process The System must provide the ability to use full journey data or only 5.4.4.1 Interline / codeshare flight data in the availability/sell/waitlist clearance evaluation The System must provide the ability to use all available itinerary segments for constructing O&Ds for availability, sell, waitlist clearing 5.4.4.2 and simulation of O&D control considering carrier specific parameters (e.g. maximum connect time, online or interline connection) The System must determine availability and segment sell using bid price methodology for segments on O&D control using the O&D fare versus the sum of the bid prices of the legs traversed. The bid price calculation must use one of two methods: - The gradient/slope/adjustment factor approach - The bid price increment using an interpolation table 5.4.4.3 The process must also take into account recapture rate and other adjustment factors (e.g. customer value, POS). The default is based on leg and segment availability. Leg availability is based on the seats available in each booking class taking into consideration the class nesting hierarchy. Segment availability is determined from leg allocations and segment limits. 5.4.4.4 The System must provide the ability to limit Inventory to certain PCCs, ARC/IATA 5.4.4 NO 10 NO 10 NO 10 NO 8 NO 8 NO 8 YES 10 Requirements Confidential Proprietary Page 55 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the option to harmonize availability 5.4.4.5 throughout entire O&D (Do not allow booking of individual segments in an O&D unless the complete O&D has availability) The System must provide ability to limit availability for path/classes 5.4.4.6 with no valid fare (e.g. if the W fare has a 14 day advance purchase, W availability, should be inside of 14 days) The System must provide ability to calculate leg and segment AVS 5.4.4.7 as well as NAVS after schedule change, reoptimization, bookings and cancellations The System must support full and selective AVS (e.g. first closing, 5.4.4.8 sell and report) 5.4.4.9 The System must support both AIRIMP options for NAVS The System must provide multi-level NAVS (e.g. send NAVS 5.4.4.10 9,4,3,2,1,0 seat availability) The System must provide message batching for AVS and NAVS 5.4.4.11 according to defined parameters (e.g. number of flight items per message, time limit) The System must support the ability for AVS/NAVS recap based on 5.4.4.12 carrier specific rules for flight /date ranges The System must allow to manually tailor AVS/NAVS open and 5.4.4.13 close thresholds based on flight, O&D, date range, days from departure, class, differing by marketing partner or the vendor The System must allow carriers to automatically (parameter driven) 5.4.4.14 tailor AVS/NAVS open and close thresholds based on flight, O&D, date range, days from departure, and class The System must provide the ability to send / receive / store 5.4.4.15 AVS/AVN depending on GDS/carrier‟s system window The System must provide the ability to switch from automatic status 5.4.4.16 to manual status for AVS message generation (This allows AVS generation to be "turned off" for certain flight/date ranges) 5.4.4.17 The System must provide the ability to not send AVS on certain classes determined at the flight leg/segment date level NO 10 NO 8 YES YES YES YES NO YES 10 10 10 10 8 10 YES 10 YES YES 10 10 YES 10 YES 10 Requirements Confidential Proprietary Page 56 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.4.4.18 The System must provide functionality to calculate availability and sell based on round trip itinerary NO 8 The System must provide functionality to use published/private fares 5.4.4.19 instead of the estimated O&D fare data to evaluate availability, using fares rules to determine applicable fare for each class Inventory Sell The System must provide the ability to return inventory booked and 5.4.5.1 cancelled in the same session The System must provide married segment control (MSC) for 5.4.5.2 bookings made and with all external channels (e.g. GDSs, Travel Portals) based on GDS and/or carrier specific rules The System must support the use of journey data in availability and 5.4.5.3 segment sell 5.4.5.4 The System must provide marriage to journey data with all external channels (e.g. GDSs, ) based on GDS and/or carrier specific rules 5.4.5 NO 8 YES YES YES YES 10 10 10 10 The System must provide married segment control based on the 5.4.5.5 carrier's revenue management requirements for both codeshare rerouting and cascading methodologies The System must store in the PNR the revenue captured on the 5.4.5.6 flight by total trip, by O&D and by segment based on carrier specific Proration rules The System must provide the ability to waitlist passengers for flights 5.4.5.7 for which there is currently not any inventory available The System must have the facility to customize availability, confirmed and waitlisted sell based on customer attributes in the 5.4.5.8 PNR or from the carrier's frequent flyer system according to carrier specific rules (e.g. guaranteed sell for defined booking classes that are closed, time before departure) NO 8 NO NO 8 8 NO 8 Requirements Confidential Proprietary Page 57 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must allow redemption class oversell (e.g. redeem more miles to get better availability) when no seats are available in frequent flyer redemption classes. The carrier will book them in a 5.4.5.9 revenue class, lower the allocation of the revenue class, and automatically rebook into the redemption class at SAC and appropriately identify these bookings in the PNR. Exceptions must be allowed to limit the buy up by carrier, O&D, flight, date. 5.4.6 Waitlist Handling NO 8 The System must provide the ability for automated waitlist confirmation whenever inventory becomes available. The clearance 5.4.6.1 process must determine the O&D, prioritize the clearance of the waitlist, and marry connecting segments where appropriate. The System must provide the ability to inhibit automated waitlist 5.4.6.2 confirmation on single flight by cabin/nesting block and/or inventory class/bucket, even though there may be inventory available The System must provide the ability to manually remove the 5.4.6.3 inhibiting of waitlist clearance for a cabin/inventory class/bucket for a flight leg date The System must provide the ability to close waitlists on single flight 5.4.6.4 and/or cabin/inventory class/bucket even though there may be inventory available The System must provide the ability to manually open waitlists for a 5.4.6.5 cabin/inventory class/bucket for a flight leg date The System must provide the option to define the maximum number 5.4.6.6 of waitlisted bookings based on market, days from departure, date range for each carrier by cabin/Inventory class/bucket The System must provide the option to define waitlist clearance deadline for each carrier (e.g. inhibit waitlist within 12 hours of 5.4.6.7 departure) based on market, days from departure, cabin/Inventory class/bucket. 5.4.6.8 The System must allow waitlist bookings to be nested Requirements YES 10 YES 10 YES 10 YES YES 10 10 YES 10 YES NO 10 6 Page 58 of 253 Confidential Proprietary National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to separate group waitlisted bookings from single waitlisted bookings The System must provide the option to exclude PNRs from 5.4.6.10 automatic waitlist clearance (e.g. partially flown itineraries) based on carrier specific rules 5.4.6.9 5.4.7 5.4.7.1 Group Handling The System must support different options of group handling (e.g. on request, automatic confirmation in relation to individual class availability), depending on POS (e.g. airline bookings vs. agency bookings) The System must provide the ability to separate confirmed, waitlisted and pending group bookings The System must provide the ability for a partial confirmation of a group request The System must provide the ability to automatically separate the group requests depending on days prior to departure, booking class and requesting location The System must support the ability to automatically trigger flight reoptimization by the revenue management system or manual review if a confirmed group cancels The System must provide the ability to establish a time limit for each confirmed group. Any unused space may be returned to inventory if predetermined payment is not received or group firmed based on carrier specific rules. A warning is sent to the agent that holds the Group. The System must provide the option to view waitlisted group on demand The System must provide parameters to accept or deny group requests based on carrier specific rules Inventory Data Retrieval and Update NO YES 10 10 NO 10 5.4.7.2 5.4.7.3 5.4.7.4 NO NO NO 10 10 10 5.4.7.5 NO 10 5.4.7.6 YES 10 5.4.7.7 5.4.7.8 5.4.8 YES YES 10 10 Requirements Confidential Proprietary Page 59 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.4.8.1 5.4.8.2 5.4.8.3 5.4.8.4 5.4.8.5 The System must enable selected users to retrieve all information stored in the inventory record, including: - Inventory control data at leg, segment, and path level including codeshare - Confirmed, waitlist, pending bookings - Group information - Gated classes - Inventory history The System must enable selected users to update inventory control data, including: - Leg parameters (e.g. inventory classes, virtual buckets) - Segment parameters - Bid price data The System must allow selected users to copy inventory control data from a flight/leg/segment/date to another or same flight/leg/segment/date The System must allow selected users to rebook selected passengers from one flight to another flight or flights The System must allow selected users to emulate and track each step of availability calculations (e.g. ARC/IATA, PCC, POS) NO 10 NO 10 NO NO NO 10 10 10 The System must allow selected users to retrieve inventory data 5.4.8.6 based on thresholds (e.g. less than 5 seats available in Y class, 20 Days from departure) The System must allow for retrieval of no-show information by flight 5.4.8.7 and passenger The System must provide functionality to rebook space that was 5.4.8.8 cancelled due to a no-show on the first segment if passenger shows on a later flight The System must provide functionality to trigger SSR messages 5.4.8.9 (e.g. flight firming) to the owners of specific PNRs ( FIT / GIT) (e.g. unticketed) for a specific flight or flight date range 5.4.9 Inventory History NO YES NO 10 10 10 NO 10 Requirements Confidential Proprietary Page 60 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must record changes for each flight date including: - AVS/NAVS - Inventory Control parameters 5.4.9.1 - Schedule changes that impact inventory parameters - Passenger final sales data - Distinguish manual vs. automated update The System must preserve history for all flights including cancelled 5.4.9.2 flights with inactive inventory while the departure date is still in the inventory system range 5.4.10 5.4.10.1 5.4.10.2 5.4.10.3 5.4.10.4 5.4.11 Inventory Data Maintenance The System must provide the ability to initialize flights automatically when entering the inventory system window The System must automatically remove inventory control data at the time it exits the inventory system window. Handoff to internal carrier or external systems if required by a carrier The System must support maintenance of the O&D fare data and automatically remove past dated data The System must support all inventory gating processes (e.g. mark class / leg / segment in inventory, send AVS / AVN) YES 10 YES 10 YES NO NO YES 10 10 10 10 Inventory Statistics The System must provide inventory control statistics e.g.: - Number of inventory records 5.4.11.1 - Number of legs/segments on O&D control - Number of Bid Price Flights - Number of seamless legs/segments The System must provide transaction data statistics e.g.: - Inventory, booking figures, overbooking - Bid price (traffic, errors) 5.4.11.2 - Data transfers (ABK, gating) - Availability requests (PAOREQ/RES) - Segment sell (ITAREQ/RES) NO 10 NO 10 Requirements Confidential Proprietary Page 61 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must Provide a tool to ensure integrity of data between 5.4.11.3 inventory data and the revenue management systems based on the carrier specific rules The System must provide a tool to ensure integrity of data between inventory and PNR booking counts (e.g. confirmed, waitlist, and 5.4.11.4 group counts) for all flights/segments in the inventory system window Identify inventory / availability / fare inconsistencies based on carrier specific rules e.g.: - For each O&D POS, review booking class hierarchy and validate 5.4.11.5 that the O&D fare data and published fares are in same hierarchy - Sum of locals less than through fares - Fare filing errors or contradictions \ Inventory Updates The System must support real-time updates of inventory control 5.4.12.1 data from revenue management systems The System must allow selected users to send inventory data to the 5.4.12.2 revenue management system The System must record and allow retrieval of inventory control data 5.4.12.3 to be used in the revenue management systems 5.4.12 NO 10 YES 10 NO 10 YES YES YES 8 8 10 5.5 5.5.1 Ticketing General Requirements The System must provide the ability to issue either electronic or 5.5.1.1 paper documents in compliance with industry standards on carrier‟s stock (plating) The System must provide acknowledgement of successful completion of document issuance (e.g., stock control number, 5.5.1.2 document number) from devices including but not limited to printers, (ATB, laser, thermal), fax or email services YES 10 YES 10 Requirements Confidential Proprietary Page 62 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must have the facility for the agent to direct output to specific or alternate print location for delivery of document(s) The System must provide the ability to regenerate document in the 5.5.1.4 event of print failure 5.5.1.3 The System must provide the ability to regenerate on demand, (print, email, fax) documents including but not limited to receipts, 5.5.1.5 itineraries and informational documents as carrier rules allow. Document receipt must indicate “duplicate”, other non value documents may be regenerated without the “duplicate” notification. The System must support electronic ticket processing via structured data messages from alternate channels e.g. web, kiosk as well as 5.5.1.6 external GDS channels, PDA devices, telephone voice response units, mobile phones (SMS), ATM The System must provide the ability for the carrier to issue 5.5.1.7 documents in compliance with industry standards on neutral ticketing stock, validating on any carrier as bilaterally agreed. The System must provide non airline agents (general sales agents (GSA), direct agency connections) the ability to issue tickets on 5.5.1.8 behalf of the carrier with direct reporting to carrier revenue accounting system with or without application of commission The System must provide non airline agents (general sales agents 5.5.1.9 (GSA), direct agency connections) the ability to issue tickets on behalf of the carrier with reporting thru BSP The System must provide the ability to issue special fares including but not limited to Bulk, IT (inclusive tour), netfares or negotiated 5.5.1.10 fares (fare on the ticket differs from the fare collected). All the fare data must be available for down line processes e.g. refund, reissue and revenue accounting The System must have the facility to Electronically store all data for down line needs e.g. revenue accounting, check-in. Data must be 5.5.1.11 available to authorized agent to perform ticketing services based on carrier specific rules as bilaterally agreed YES YES 10 10 YES 10 YES 10 YES 10 NO 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 63 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.5.1.12 5.5.1.13 5.5.1.14 5.5.1.15 5.5.1.16 5.5.1.17 The System must have the facility to flag unpaid fees and charges due to check-in system and in individual travel record (PNR) for payment and processing prior to boarding pass issuance. The flag is automatically removed after payment received, and the method/amount of payment is kept for historical and receipt purposes. The System must provide the ability to support all passenger and ticket types (infant, open tickets) across all channels and all media types The System must enforce carrier policy and fare rules for type of ticket issued (e.g. electronic ticket only, ticketless) The System must provide automated validation of carrier ticketing agreements at issuance time The System must utilize current fares and fare rules at time of ticketing The System must enforce fare rule restrictions at time of ticketing including applicable surcharges e.g. last date to ticket, issuing location. NO 8 YES YES YES YES YES 10 10 10 10 10 The System must enforce carrier policy associated with travel authorization e.g. mileage accrual, denied boarding compensation, 5.5.1.18 ability to standby for non confirmed travel rules will vary by carrier and must be easily changeable. These restrictions must be available to all agents or processes needing the information (e.g. check in) The System must provide the ability to issue any “test” document in 5.5.1.19 production environment, with all issued output documents and revenue accounting reports indicating void The System must allow agent override of system rules with logging of data needed to track and report on such overrides. Where 5.5.1.20 appropriate, agent must include reason for override as part of process. Carrier specific rules will determine what rules can be overridden, as well as control who can override those rules YES 10 YES 10 NO 8 Requirements Confidential Proprietary Page 64 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must have the facility to make manual or automatic generation of fare construction data available to all downline 5.5.1.21 processes. Validation of manually entered data based on carrier specific rules The System must provide the ability to capture ticketing data from 5.5.1.22 magnetic stripe, manual input or any other source The System must provide acknowledgement for each message sent 5.5.1.23 between the internal applications and monitoring possibilities for specified users 5.5.2 Ticket Specification/ Ticket Data 5.5.2.1 The System must support at least 99 paid and unpaid taxes The System must support at least 16 coupons (4x4 coupon 5.5.2.2 conjunctive books) with ability to easily expand The System must provide for pricing indicator to be included in ticket 5.5.2.3 data and revenue accounting handoff. The System must provide the ability to add additional endorsement 5.5.2.4 remarks/rules according to carrier specific rules 5.5.3 5.5.3.1 5.5.3.2 Paper Ticket The System must provide the ability to issue an industry standard ATB1 or ATB2 document including magnetic stripe encoding YES 10 YES NO 10 8 YES YES YES YES 10 10 10 10 YES YES YES 10 10 10 The System must provide the ability to perform Direct Print (Status “P”) and Print Exchange (“X”) The System must provide the ability to issue an industry standard 5.5.3.3 TAT ticket 5.5.4 Electronic Ticketing The System must have the ability to set up flexible rules and enforce 5.5.4.1 electronic ticketing based on carrier defined parameters including but not limited to market, flight number and codeshare 5.5.4.2 The System must allow carrier specific rules for granting airport control YES 10 YES 10 Requirements Confidential Proprietary Page 65 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to associate existing electronic ticket to a PNR with validation of Itinerary and name and any other 5.5.4.3 carrier specific rules (e.g. FOID). Any electronic ticket coupon should only be associated with one PNR The System must automatically maintain association of electronic coupons to the itinerary through all voluntary and involuntary 5.5.4.4 changes, according to carrier specific rules. Change could result in a possible coupon association requiring agent decision. 5.5.4.5 The System must provide the ability to associate miscellaneous documents (electronic or paper, special service tickets, oxygen charges, change fee) to electronic ticket and/or PNR The System must support all industry standard search fields including optional criteria e.g. FOID or phone number, Credit card number, Record Locator, FFP Number, based on carrier specific rules The System must provide automatic revalidation with ability to enforce collection of fee based on carrier specific rules. If rules are not met, ticket must be reissued The System must fully support interline electronic ticket functionality, including codeshare flights, including carrier rules for transfer of control The System must fully support interline electronic ticket functionality, including codeshare flights between other carriers. The system must also support acceptance of e-Ticket coupons for IATCI partners and update coupon status The System must support FOID processing, based on carrier specific rules (e.g. market) for carriers wishing to use it internally or on a bilateral basis YES 10 YES 10 NO 8 5.5.4.6 YES 10 5.5.4.7 YES 10 5.5.4.8 YES 10 5.5.4.9 YES 10 5.5.4.10 YES 10 The System must fully support electronic document functionality at 5.5.4.11 station ground handled in compliance with ETL, interactive and control method of the GHA. YES 10 Requirements Confidential Proprietary Page 66 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support all industry electronic status indicators 5.5.4.12 according to relevant IATA resolution. Support status indicators for online use, carrier driven, e.g. forfeit 5.5.4.13 5.5.4.14 The System must have the facility to immediately reflect in the coupon status if any action on the electronic coupon takes place The System must provide the ability to manually update the coupon status as needed, based on carrier specific rules YES 10 YES YES 10 10 The System must provide the ability to use the non-endorseable indicator. This indicator will be sent in the EDIFACT message for control and display, as per the policies and criteria of the airline. 5.5.4.15 When other Airline who is not part of the eTicket itinerary, but with whom AI has an interline agreement, requests control of an AI coupon, AI will use this indicator to determine if control may be released. The System must provide a complete record of all changes to an electronic ticket including date/time stamp and source of action, 5.5.4.16 including all exchange related data. Ability to add comments to coupons (e.g., why a ticket was revoked) 5.5.5 5.5.5.1 Electronic Entitlement The System must have the facility to store entitlement value for a customer (e.g. MCO, refund due) with ability to associate to PNR and/or electronic ticket The System must provide for retrieval of electronic entitlements by document number, customer name, FOID or other criteria defined by carrier The System must provide the ability to access electronic entitlements with other carrier bilaterally agreed The System must provide the ability to associate electronic entitlement with other document (paper or electronic). This may be done manually or by system (e.g. special service ticket for change fee must reference associated ticket number) YES 10 YES 10 NO 8 5.5.5.2 5.5.5.3 NO NO 8 8 5.5.5.4 NO 8 Requirements Confidential Proprietary Page 67 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to store terms and conditions 5.5.5.5 defining usage and expiration with ability to deliver those terms and conditions to customer The System must provide statistics on usage for carrier to determine 5.5.5.6 cost and value The System must have the facility to purge expired entitlements to 5.5.5.7 the carriers revenue accounting system at frequency and in manner defined by carrier The System must provide a complete record of all changes to an 5.5.5.8 electronic entitlement with date/time stamp and source of action, including any waiver to terms and conditions The System must provide ability to add comments to coupons (e.g., 5.5.5.9 why a rule for usage was waived) 5.5.6 Electronic Ticket Storage NO NO NO 8 6 6 NO YES 6 10 The System must provide automated handoff of flight coupons in final status (e.g. exchanged, refunded, voided, used, revoked and 5.5.6.1 forfeited) to carrier revenue accounting system after flight close out. This could be real-time or based on carrier specific rules The System must provide automated handoff of flown coupons to 5.5.6.2 carrier revenue accounting system for flights that were not properly closed out The System must have the facility to archive/purge/remove 5.5.6.3 used/expired coupons and other electronic ticketing data based on parameters and carrier specific rules The System must provide integrity checks to internally monitor the 5.5.6.4 accuracy of the electronic coupon status between the different applications and revenue accounting 5.5.6.5 The System must provide integrity checks to monitor the accuracy of the electronic coupon status between Reservation and Check-in The System must provide a monitoring tool to ensure that pending coupon status is updated properly based on carrier specific rules YES 10 YES 10 YES 10 NO 8 NO 8 5.5.6.6 NO 8 Requirements Confidential Proprietary Page 68 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Voluntary Changes The System must provide fully automated determination of residual value for unused travel, validation of all fare rules, including application of service charges/fees in accordance with applicable 5.5.7.1 Industry Standards. Must include application of industry and fare rules for ticket validity. A detailed breakdown of charges and/or refund due must be available. The System must provide pricing without rebooking to enable 5.5.7.2 customer decision on whether to proceed with change. Price returned must include all fees and charges. The System must provide full exchange capability across all carrier 5.5.7.3 including validation of all fare rules/restrictions per bilateral agreement The System must ensure there are no fare discrepancies between 5.5.7.4 pricing and repricing modules. (Assumes different pricing engines used for pricing and exchange/reissue processes) The System must the facility to utilize electronic data where 5.5.7.5 available for paper ticket processing, providing ability to collect necessary missing information from agent/passenger The System must provide the ability for support documentation to 5.5.7.6 include coupons from multiple tickets in any combination of electronic and paper, requiring multiple residual value calculations 5.5.7.7 5.5.8 The System must allow exchange of paper to electronic, electronic to paper, electronic to electronic or any combination 5.5.7 YES 10 YES 8 YES 10 NO 8 NO 8 NO 6 YES 10 Involuntary Changes The System must provide the ability to exchange coupon(s) involved 5.5.8.1 in involuntary rerouting as per IATA resolution 735d The System must ensure that in cases of involuntary reissues the 5.5.8.2 validation on the fare calculations are omitted based on carrier specific rules YES YES 10 10 Requirements Confidential Proprietary Page 69 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.5.9 Irregular Operations (IROP) The System must provide system guided IROP ticket handling through all channels based on industry standards and carrier specific rules. YES The System must provide for supporting all changes/modifications/updates in industry standards as laid down by IATA 10 5.5.9.1 The System must provide for determination and processing of most 5.5.9.2 economic way of providing travel documents for rerouted customers (e.g. reissue vs. revalidation vs. FIM vs. push control) The System must provide the ability to defer electronic lift in the 5.5.9.3 event of irregular operations where flight may have been closed but not flown. May be agent entry or automatic system determination The System must provide automated determination & production of compensation (e.g. hotel/meal/ vouchers) per carrier policy. Compensation varies by carrier specific rules (including parameters e.g. passenger value and itinerary) and is easily changeable by carrier. Record of compensation must be retained with passenger record (Customer Record). The System must provide for system generated FIM with revenue accounting handoff either electronic or paper based on carrier specific rules and bilateral agreement. The System must provide for system generated online coupon for interrupted travel (revenue, industry) with revenue accounting handoff The System must provide the ability to perform all electronic ticketing functions for an individual passenger or a grouping of passengers (e.g. everyone on a flight, a subset of passengers) with a single entry YES 8 YES 10 5.5.9.4 NO 6 5.5.9.5 NO 8 5.5.9.6 NO 6 5.5.9.7 YES 10 Requirements Confidential Proprietary Page 70 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to send electronic vouchers to third parties (e.g. hotel) when the tenderer system able to 5.5.9.8 accommodate. Provide record of electronic entitlement to passenger and retain record of issuance in Customer Record The System must provide the ability to build a cost report on all 5.5.9.9 IROP situations. The report should be flight or station driven. 5.5.10 Refunds NO 8 NO 6 The System must provide fully automated determination (based on 5.5.10.1 automated fare rules) of refund value, including application of service charges/fees, recognizing voluntary vs. involuntary refunds 5.5.10.2 5.5.10.3 5.5.10.4 5.5.10.5 The System must provide for automated update of electronic ticket coupon status to refunded The System must provide automated cancellation of inventory upon completion of refund action, based on carrier rules The System must provide the ability to initiate refund of multiple tickets in one entry (same fare/same penalties) The System must provide automated collection of all data associated with a refund transaction, including pricing and ticket data with reporting to revenue accounting The System must support the ability to refund a sale at passenger request within 24 hours of payment, regardless of fare rules as required by government regulations The System must provide the ability to refund miscellaneous fees & charges The System must provide issue refund receipt via method of choice (e.g. e-mail, fax) Sales Reporting YES 10 YES YES YES YES 10 10 10 10 5.5.10.6 5.5.10.7 5.5.10.8 5.5.11 YES NO NO 10 8 6 Requirements Confidential Proprietary Page 71 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide for automated agent cash drawer accounting and closeout. Sales report for agent includes record of 5.5.11.1 all transactions, not just cash. Includes sales, refunds, vouchers Agent has ability to review transactions prior to close-out. Must be able to rollup to office level based on carrier and country rules. 5.5.11.2 5.5.11.3 The System must provide cashier functionality (e.g. in airports) where one agent has responsibility for all cash handling The System must provide the ability to modify selected refund data prior to agent closeout based on carrier‟s rules. Provide indicator if refund is modified The System must provide the ability to void and/or reinstate any transaction prior to agent closeout, including update to electronic coupon or electronic copy of paper ticket The System must provide indicator of private or public fare to sales reporting system The System must ensure that data passed to carrier revenue accounting system must be capable of generating invoices to credit card companies depending on the form of payment The System must ensure that data passed to carrier revenue accounting system includes booking and ticketing source and method for correct application of commission policy The System must provide for dynamic publication of sales data and other value transactions, including electronic entitlement, for use of revenue accounting system The System must provide the ability to enter data associated with manual sales/transactions for reporting to revenue accounting The System must have to facility to force sales report closure after defined period (ensures all sales reported) YES 10 YES NO 10 8 5.5.11.4 5.5.11.5 5.5.11.6 YES YES YES 10 10 10 5.5.11.7 YES 10 5.5.11.8 YES 10 5.5.11.9 5.5.11.10 YES YES 10 10 Requirements Confidential Proprietary Page 72 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide ticket sales in most current standard format (e.g. ATPCO or RET) to ATPCO and/or carrier revenue 5.5.11.11 accounting systems. Must include ERSP, booking and issuing office, commission and other data obtained from distribution agent (e.g. web site) as required by individual revenue accounting systems. The System must support sales, payment and reporting of multiple currencies The system must reflect the various taxes/ fees collected in the 5.5.11.13 automated sales report. 5.5.11.12 5.5.12 Commissions YES 10 YES YES 10 10 The System must provide data necessary to determine 5.5.12.1 commissions to be paid (e.g. booking, issuing office to allow variable rates by booking source). Could be flat rate or percentage. 5.5.12.2 5.5.13 The System must provide different commission rate as indicated by presence of ERSP. Acceptance of Currencies & Forms of Payment YES 10 YES 10 The System must support carrier controlled parameters for acceptable FOPs, including selected criteria, e.g. country/currency 5.5.13.1 of sale, valid formats, additional authorizations required. Must include support for commissionable forms of payment. The System must provide links to real-time authorization services 5.5.13.2 (e.g. credit/debit card approvals, address verification, check verification) The System must support additional data for selected form of 5.5.13.3 payment billings (e.g. credit card, invoice) The System must provide real-time verification/validation of internal certificates/vouchers, with usage updates at time of ticketing. May 5.5.13.4 include link to carrier or external systems including but not limited to mileage deduction. Covers both mileage type certificates and other entitlements. Requirements YES 10 YES YES 10 10 YES 10 Confidential Proprietary Page 73 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support customer entry of CID or other PIN number. Number must not be stored or retrievable. The System must allow multiple FOPs per transaction, maximum 5.5.13.6 variable by carrier The System must provide masking of personal FOP data per 5.5.13.7 industry standards, but retention and retrieval of data for downline functions/processes as required 5.5.13.5 5.5.14 Fraud Prevention YES YES YES 10 10 10 The System must provide real-time mechanism for risk assessment to identify potential fraudulent sales. May be based on combinations of characteristics per carrier specific rules (e.g. bypassing checks for good customers, screening of customers against carrier defined criteria to determine risk of payment failure). Carrier must be able to 5.5.14.1 define when to initiate analysis and what to do with results. The System must provide for setting up the Present Credit Card Indicator. When the indicator is set / sent by the Validating Carrier, the customer shall present the credit card used to purchase the eticket at the first point of check-in for each carrier in the itinerary. The System must provide check against stolen ticket database for paper tickets. Assumes usage of ARINC (ticket blacklist program) 5.5.14.2 stolen ticket database as a part of this function. If found, advise agent and record in PNR. The System must provide flag and necessary data to enforce carrier 5.5.14.3 specific rules for positive identification (e.g. credit card used for purchase or employee ID) Fees & Miscellaneous Documents The System must provide automated issuance of MPD/EMDs (multi purpose document/ electronic miscellaneous purpose document) 5.5.15.1 based on IATA standards (e.g. including but not limited to excess baggage, MCO, PTA and SST ) Requirements 5.5.15 YES 10 YES 10 YES 10 YES 10 Confidential Proprietary Page 74 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.5.15.2 5.5.15.3 5.5.15.4 5.5.15.5 The System must provide automated collection of miscellaneous fees. Differentiate between fare related and other, associate with ticket and/or customer as appropriate, prepare separate document if needed (electronic or paper). The System must support automated determination of document type (e.g., MCO, SST) based on criteria e.g. fee type, itinerary and carrier The System must support identification and automatic generation of fees by fare quote on services identified in PNR The System must provide the ability to give denied boarding compensation in the form of cash, MCO, or travel certificate based on carrier policy Receipts & Informational Documents The System must provide data necessary for receipt generation for funds collected/charged and refunds issued, including travel, miscellaneous fees. Receipt may be distributed via email, fax, ATB Itinerary receipt must comply with IATA/ATA standards. The System must have the facility to store and include on receipts, a summary of the rules or terms and conditions associated with ticketed fare. The information will also be available for agent retrieval. The System must provide the ability to include all related fees and charges on a single receipt or separated receipts The System must provide written information to customer based on carrier specific rules or government rules (e.g. lounge invitations, info to deaf passengers.). Allow all delivery methods. The System must have the facility to collect all required data for electronic storage of information needed for airline forms e.g. unaccompanied minors, firearms declaration, lost ticket applications. Make available for printing when necessary for customer signature. Ticketless YES 10 YES NO NO 10 10 10 5.5.16 5.5.16.1 YES 10 5.5.16.2 YES 10 5.5.16.3 5.5.16.4 YES NO 10 6 5.5.16.5 YES 10 5.5.17 Requirements Confidential Proprietary Page 75 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.5.17.1 The System must provide the ability to restrict booking by source The System must have to facility to reinforce payment processing at 5.5.17.2 time of booking according to carrier specific rules. Update of travel record to indicate payment process. (unique identifier) 5.5.17.3 The System must report all required sales data to carrier revenue accounting with specific identification for unique processing YES 10 YES 10 YES 10 The System must provide automated fare quote, one way pricing 5.5.17.4 including all taxes, fees and charges, with potential for multiple fare constructions per purchase The System must have to facility to pass data to fare quote system 5.5.17.5 which include booking source and method for correct application of discounts 5.5.17.6 5.5.17.7 The System must provide the ability to restrict itinerary changes based on fare rules (E.g. no change after flight departs) YES 10 YES 10 YES YES 10 10 The System must provide the ability to refund a sale based on carrier specific rules The System must retain data in the PNR until travel has been completed or travel authorization has expired, which ever comes 5.5.17.8 first. Rules are defined by the carrier and must be easily changeable 5.5.17.9 The System must have the facility to maintain a record of travel authorization which must be available for use by check in system NO 8 NO 8 The System must have the facility to archive all travel information 5.5.17.10 (e.g. usage, rebooking) in travel record (PNR) when travel authorization expires The System must provide the ability to assess and collect miscellaneous fees associated with special product offering (e.g., 5.5.17.11 advance seat assignments, special meals). Initiated by automated fare quote or manually NO 8 YES 10 Requirements Confidential Proprietary Page 76 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must have the capability to advise difference of fare 5.5.17.12 (collection or refund) during any itinerary/PNR modification to any external application (web booking/ ATM / Mobile etc) 5.5.18 5.5.18.1 Employee Ticketing The System must maintain employee data e.g. dependents, seniority, authorized travel types including boarding priority The System must provide automated feed of employee data from carrier human resources systems plus automated feeds or manual entry from other authorized entities. Source will vary by carrier or carrier subsidiary. Fully automated determination of eligibility and any associated charges for all industry ticketing. Rules/costs will vary by carrier/passenger relationship and may be mileage based (including ZED fares), sector charges, discounts from published fares, or flat fees. Payment for employee travel may be standard forms of payment e.g. cheque, cash or credit card Payment for employee travel may be processed through handoff to carrier revenue accounting for tax application and payroll deduction or billing. Pricing or informational request to determine cost of planned industry travel. Must apply carrier specific rules, including bilateral carrier agreements. Rules include parameters associated with individual traveler. May be initiated from a booking, or data may be supplied by agent/passenger with end result being a booking if so desired. Interface with pricing system to obtain all fares/taxes and fees. The System must provide automated process for generation of tickets (regardless of media) for crew travel The System must provide automated reporting and monitoring of issuance and/or usage information to carrier revenue accounting systems The System must permit ticketless if carrier policy and government rules allow YES 8 NO 8 5.5.18.2 NO 8 5.5.18.3 YES 10 5.5.18.4 5.5.18.5 YES NO 8 8 5.5.18.6 NO 8 5.5.18.7 5.5.18.8 5.5.18.9 YES YES YES 10 10 10 Requirements Confidential Proprietary Page 77 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support use of Electronic ticket for industry travel where a ticket is required and interline agreement supports 5.5.18.10 electronic processing. Electronic ticket should be standard for staff travel. Award travel ticketing The System must provide ticket, with auto pricing, of award travel 5.5.19.1 itineraries based on carrier specific rules The System must pricing and repricing of award travel tickets must 5.5.19.2 include automatic application of appropriate fees, service charges and taxes The System must provide interface to carrier frequent flyer systems 5.5.19.3 or external vendor as needed for queries to and debit or credit of customer mileage balance The System must provide the ability to determine value for handoff 5.5.19.4 to carrier revenue accounting where an internal payment is being done between frequent flyer program and carrier (transfer pricing) The System must provide the ability to autoprice in miles, money or a combination of miles and money The System must provide handoff to carrier systems (potentially 5.5.19.6 both revenue accounting and frequent flyer program) for all reporting/accounting needs The system must provide handoff to carrier systems (both revenue 5.5.19.7 accounting & FFP) for purchase of products other than air travel using FFP miles. 5.5.19.5 Additional Products The System must have the facility to recognize passenger traveling 5.5.20.1 for specific company 5.5.20.2 The System must provide automated fare quote for corporate fares 5.5.20.3 The System must provide automated electronic ticket issuance with FOID, according to carrier rules, a day before flight departure 5.5.20 5.5.19 YES 10 YES YES 10 10 YES 10 YES 10 YES YES 10 10 YES 10 NO NO NO 6 6 6 Requirements Confidential Proprietary Page 78 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.5.20.4 The System must provide automated refund for partially used tickets The System must provide automated sales report without agent intervention at a specific time The System must provide the ability to store under a Corporate Record/Group Record for a company multiple electronic tickets with 5.5.20.6 or without a passenger name/FOID. Electronic tickets to be updated with name/FOID at a later time and automatically linked to the PNR/Customer Record The System must provide the ability to use the non-endorseable 5.5.20.7 indicator. 5.5.20.5 NO NO 6 6 NO 6 NO 6 5.6 Fare and Pricing 5.6.1 General Requirements 5.6.1.1 The System must provide for all functionality to be automated The System must provide user friendly access to fares and rules for 5.6.1.2 internet users The System must provide a worldwide application of carrier 5.6.1.3 standard provisions 5.6.2 5.6.2.1 5.6.2.2 5.6.2.3 5.6.2.4 Fare Information The System must provide the ability to retrieve all fares for all passenger types The System must provide the ability to retrieve all fares and specific rules based on different criteria The System must provide the ability for integrated retrieval of nonpublic(private) and public-fares The System must provide the ability to retrieve fares created by category 25 (fare by rule) YES YES YES 10 10 10 YES YES YES YES 10 10 10 10 Requirements Confidential Proprietary Page 79 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to retrieve fares with multiple options, e.g. - Non-public fares - Passenger type - Adult / Child / Infant - Fare type - Global indicator - Global Alliance Carriers fares - Corporate ID 5.6.2.5 - Status fares - Air passes - Group fares - Round the world fares - Tour code - Electronic ticket fares - Internet (web) fares - Industry, staff and zonal employee discount (ZED) fares The System must provide the ability to retrieve fares from highest to lowest or reverse The System must p the ability to retrieve and identify fares with 5.6.2.7 special provisions, e.g. non-priceable fares, non-saleable fares, upgradeable fares 5.6.2.8 The System must provide the ability to retrieve joint fares 5.6.2.6 YES 10 YES YES NO 10 10 6 Requirements Confidential Proprietary Page 80 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.6.2.9 5.6.2.10 5.6.2.11 5.6.2.12 5.6.2.13 The System must provide the minimum requirements for basic fare information including but not limited to: - Fare basis code - Booking class - Carrier (s) - One way/round trip indicator - Currency of fare filed - Fare amount - Seasonality - Sales restrictions (e.g. time of ticketing) - First/last travel dates - First/last ticketing dates - Global indicator of fare filed - Routing / mileage indicator - Advance purchase - Minimum/maximum stay - Penalties - Ticketing requirements - Non-public fare indicator - Indicator to show pricing inhibited - Day/time restrictions - Unsaleable fare indicator - Flight application The System must provide the ability to retrieve additional information based on original entry e.g.: - RBD by carrier - Routing - Footnotes - Taxes / fees / other charges The System must provide ability to retrieve fares in more than one currency at one time sorted by currency The System must convert to any currency regardless of currency filed The System must provide the ability to retrieve fares in one given currency when multiple currency fares exist YES 10 YES 10 NO YES YES 6 10 10 Requirements Confidential Proprietary Page 81 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Rule Information The System must provide the ability to retrieve all rules associated 5.6.3.1 to fares for all passenger types 5.6.3.2 The System must provide the ability to retrieve carrier general rules 5.6.3.3 5.6.3.4 5.6.3.5 5.6.3.6 5.6.3.7 5.6.3.8 5.6.3.9 5.6.3.10 5.6.3.11 5.6.3.12 5.6.3.13 5.6.4 The System must provide the ability to automatically process all ATPCO categories and any future categories The System must ensure that rule content default is ATPCO The System must provide the ability to automatically process other relevant ATPCO data (e.g. footnotes) The System must provide the ability to process ATPCO‟s multilateral / bilateral fare product and any new applications which are introduced from time to time. The System must create complete rules for fares by category 25 (Fare by Rule) The System must provide stand alone specific rule entries by e.g.: fare-basis code, rule number, city pair The System must provide the ability to retrieve fare rules with associated fare amounts The System must provide the ability to retrieve full rule or multiple specific categories The System must provide abbreviated version of the full rule in user friendly language The System must provide differentiated content by distribution channel and/or user The System must provide the ability to retrieve rules in reverse direction or in both directions at the same time Auto-pricing 5.6.3 YES YES YES YES YES YES YES YES NO YES YES YES YES 10 10 10 10 10 10 10 10 4 10 10 10 10 Requirements Confidential Proprietary Page 82 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to price all types of passengers, itineraries and fares validating all rules and regulations, e.g. - Non-public fares - Passenger type - Fare type - Global indicator - Global Alliance Carriers fares - Corporate ID 5.6.4.1 - Status fares - Air passes - Group fares - Round the world fares - Tour code - Electronic ticket fares - Web (Internet) fares - Industry - Staff and zonal employee discount (ZED) fares 5.6.4.2 5.6.4.3 5.6.4.4 5.6.4.5 5.6.4.6 5.6.4.7 5.6.4.8 5.6.4.9 The System must provide the ability to validate all categories as defined by ATPCO today and any future developments) The System must provide the ability to validate all rule provisions provided through any other intermediary sources The System must provide the ability to validate other relevant ATPCO data (e.g. footnotes / routings) The System must include the free baggage allowance in the autopricing function The System must provide the ability to segment select The System must provide the ability to price at least 16 segments within a passenger itinerary The System must provide the ability to handle at least 99 taxes (paid and unpaid) The System must enforce marriage logic when pricing YES 10 YES YES YES YES YES YES YES YES 10 10 10 10 10 10 10 10 Requirements Confidential Proprietary Page 83 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must enforce carrier fare selection criteria by selecting 5.6.4.10 the appropriate carrier fare based on specific sectors of travel (e.g. transatlantic, transpacific, first international sector) The System must provide fare selection hierarchy when duplicate fares exist for the same origin and destination in the following sequence - Specified fares - One add-on construction fares - Two add-on construction fares The System must provide the ability to price open segments The System must inhibit auto-pricing of segments out of sequence in a single PNR The System must auto-price one ways as separate itineraries when specific carrier‟s product requires it The System must provide the ability to price PNRs which are manually linked after original creation The System must provide pricing for coupon booklet travel The System must 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) The System must provide the ability to use a fare basis code entry when itinerary does not price the fare as expected and state reason for failure (e.g. force the fare to price by using a specific fare basis code) The System must provide multiple fare storage history in PNR when pricing is changed or amended The System must enforce the carrier‟s rule YES 10 5.6.4.11 YES 10 5.6.4.12 5.6.4.13 5.6.4.14 5.6.4.15 5.6.4.16 5.6.4.17 YES NO YES NO YES YES 10 6 10 6 10 10 5.6.4.18 YES 10 5.6.4.19 5.6.4.20 YES YES YES 10 10 10 5.6.4.21 The System must provide the ability to override own carrier‟s rule Requirements Confidential Proprietary Page 84 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.6.4.22 5.6.4.23 5.6.4.24 5.6.4.25 5.6.4.26 The System must provide the ability to price all applicable taxes, fees and other charges including change and cancellation fees for all carriers using mileage or money (e.g. UMs , bikes, seat assignment fees, meal charges, PTAs, surcharges, excess baggage) The System must provide unique indicators for ancillary information for backoffice processing The System must provide a tax exempt entry by country code or carrier The System must provide different tax scheme by aircraft type when required The System must provide the ability to automatically price refunds and exchanges on ticketed PNR with or without flown segments including calculation of change or cancellation fees using mileage or money. The System must provide user-friendly calculation of new fare as per the passenger‟s revised routing taking into consideration the „Fare Break Point‟, historical fares, penalties and taxes, etc. The System must support itinerary re-pricing at any customer touch point e.g. online booking applications, self service check in applications The System must validate PCC for non-public fares at time of ticketing The System must provide the ability to turn on/off by carrier the mandatory fare quote and ticket time limit enforcement The System must provide the ability to receive fare quote information from other booking sources The System must provide the ability to price directional one way fares (e.g. do not automatically apply the outbound one way fare for the return portion) The System must provide the ability to price ZED fares and calculate the taxable amount for specific countries YES 10 YES YES YES 10 10 10 YES 10 5.6.4.27 5.6.4.28 5.6.4.29 5.6.4.30 5.6.4.31 5.6.4.32 YES YES YES YES YES YES 10 10 10 10 10 10 Requirements Confidential Proprietary Page 85 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to price a fare where a discount 5.6.4.33 is applicable and is booked in a different booking class than the base fare The System must utilize information contained in Corporate Record 5.6.4.34 (e.g. account code) when pricing PNRs The System must support all auto-pricing options for informative 5.6.4.35 pricing requests The System must provide the reason for failure when the itinerary does not price as booked and provide options for the itinerary (e.g. 5.6.4.36 minimum stay not met to qualify for the fare, minimum stay of first Sunday is required) The System must provide the ability to use a fare basis code entry when itinerary does not price the fare as expected and state reason 5.6.4.37 for failure (e.g. force the fare to price by using a specific fare basis code) The System must provide the ability to price all applicable taxes, fees and other charges using mileage or money (e.g. UMs , bikes, 5.6.4.38 seat assignment fees, PTAs, surcharges, excess baggage and any others) The System must provide the ability to re-price itinerary including 5.6.4.39 fees without actually making the change in the PNR The System must provide the ability to price in currency of choice 5.6.4.40 unless inhibited by the carrier specific rules or government regulation The System must provide the ability to price itineraries in any 5.6.4.41 currency regardless of the currency filed The System must provide the ability to allow or inhibit override 5.6.4.42 functionality by carrier(s) The System must have to facility to limit the override functions to 5.6.4.43 specific user group The System must provide the ability to create a set of common 5.6.4.44 numbers/indicators for pricing purposes (e.g. #1 indicates autopriced, #2 indicates manual priced) 5.6.4.45 The System must have the facility to apply FCMI to all type of tickets YES NO YES 10 8 10 YES 10 YES 10 YES 10 YES YES YES YES YES YES YES 10 10 10 10 10 10 10 Requirements Confidential Proprietary Page 86 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to retrieve the FCMI in the auto price response The System must provide one keystroke to price the itinerary with or 5.6.4.47 without modifiers The System must provide the ability to build a manual fare 5.6.4.48 calculation to drive a ticket applying industry standard formats The system must have the provision for reporting fare basis and 5.6.4.49 pricing information from a Non Host PNR to a Host PNR through the standard AIRIMP SPR/SPM messages 5.6.4.46 5.6.5 5.6.5.1 History The System must provide fare and rule history within system window of preferably 24 months and the flexibility to change timeframe YES YES YES NO 10 10 10 8 YES 10 The System must provide negotiated fare and rule history within 5.6.5.2 system window of preferably 24 months and the flexibility to change timeframe (e.g. cat 25 created fares) The System must provide history for all fare and rule transmissions 5.6.5.3 (e.g. ATPCO) If multiple fares exist for the same day, a time stamp is required The System must provide fare quote in past date PNR retrievals 5.6.5.4 within system window of preferable 24 months The System must have the facility for past date informative pricing 5.6.5.5 within system window (preferable 24 months) 5.6.5.6 5.6.5.7 5.6.6 The System must provide history of all exchanges rates e.g. ICH / BSR / BBR / IROE within system window of preferable 24 months The System must provide online query to access all historical fare and rule data YES 10 YES YES YES YES YES 10 10 10 10 10 Fare Loads / Transmission The System must provide the ability to file and receive fare data and 5.6.6.1 rules through ATPCO, through other intermediary sources or directly to/from the carrier YES 10 Requirements Confidential Proprietary Page 87 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must accept all ATPCO transmissions of fares for all carriers The System must provide ability to include instant subs as defined 5.6.6.3 by ATPCO when available The System must deliver industry leading turnaround times for 5.6.6.4 updating fares data 5.6.6.2 5.6.6.5 The System must provide the ability to inhibit fare data online (e.g. error in filing, 1000 INR filed when it should have been 10000 INR) The System must provide the ability to directly update fares, footnotes, rules etc., at any time (e.g. change the erroneous 1000 INR fare 10000 INR online) The System must provide the ability to directly update fares, footnotes, rules filed through ATPCO at any time between ATPCO transmissions The System must provide the ability to have easy global update capability (e.g. change multiple fare records for Germany to the USA vs. individual O&Ds) The System must provide the ability to supplement coding of non automated ATPCO data, e.g.: - Mileage exceptions - Higher intermediate point exceptions The System must provide the ability for web portals, corporates, GDSs and other channels to access directly host The System must provide the ability to distribute fare data from the HOST directly to web portals, corporates, GDSs, ATPCO and other channels YES YES YES NO 10 10 10 10 5.6.6.6 NO 10 5.6.6.7 NO 10 5.6.6.8 NO 10 5.6.6.9 YES 10 5.6.6.10 5.6.6.11 YES YES 10 10 Currency The System must update / process BSR / BBR according to industry 5.6.7.1 standards (IATA resolution 024 series) The System must default to the ICH 5 day rate for BSR/BBR, when 5.6.7.2 standard industry sources are not found in the IATA resolution 024e series 5.6.7 YES YES 10 10 Requirements Confidential Proprietary Page 88 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.6.7.3 5.6.7.4 5.6.7.5 5.6.7.6 5.6.7.7 5.6.7.8 5.6.7.9 The System must update / process IROE according to industry standards (IATA resolution 024 series) The System must provide the ability to retrieve all or specific current exchange rates for: ICH / BSR / BBR / IROE The System must process the rounding principles according to IATA resolution 024d for fares and other charges The System must default to the BSR for currency conversions The System must include effective date and rate used currency conversions The System must include all rounding principles and amounts truncated for currency conversions The System must provide user option input to select specific exchange rate or multiple exchange rates for currency conversions YES YES YES YES YES YES YES 10 10 10 10 10 10 10 Shopper Products The System must provide the ability to search and price the lowest 5.6.8.1 applicable fare validating all rules 5.6.8.2 The System must provide selection defaults as defined by carrier 5.6.8.3 The System must provide robust tool allowing customer to choose from wide variety of travel and pricing options 5.6.8 YES YES YES 10 10 10 Requirements Confidential Proprietary Page 89 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide low fare finder options with rebook options and inventory interrogation which include but are not limited to: - Default must be within a compartment - Flight booked - By PTC - Other flights - Global Alliance - Time frame - Extended search - Price to beat 5.6.8.4 - Multiple modifiers in any order - Multiple options returned - Number of passengers - One keystroke for LFF - First available for a specific fare - By number of stops - By time of day - Include companion fares with individual fare options - By discount/account code - By seat map or seat assignment The System must have the facility to calculation of a passengers 5.6.8.5 itinerary observing all fare construction principles for public and nonpublic fares The System must enforce all fare construction principles according 5.6.8.6 to the IATA resolution manual for composite The System must enforce all carrier fare construction exceptions to 5.6.8.7 the IATA standards The System must provide the ability to absorb taxes, fees and 5.6.8.8 surcharges (by carrier, city, city-pair, fare basis code, booking class, routing) 5.6.8.9 The System must provide the ability to retrieve information with separate stand alone entries (e.g. no primary entry is required first) YES 10 YES YES YES YES 10 10 10 10 NO 4 Requirements Confidential Proprietary Page 90 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.6.9 5.6.9.1 5.6.9.2 5.6.9.3 5.6.9.4 5.6.9.5 5.6.9.6 5.6.9.7 5.6.9.8 5.6.9.9 Baggage/ Special Charges The System must 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. The System must 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. The System must provide the ability to retrieve all carriers special charges (e.g. bikes, seat assignment fees) per carrier for all points or by city pair or by origin/destination countries. The System must provide the ability to calculate all applicable excess baggage and special charges with currency or frequent flyer miles The System must provide the ability to retrieve all applicable taxes by country or by city pair or by tax code The System must provide the ability to retrieve all applicable surcharges by carrier by country or by city pair The System must provide the ability to retrieve all applicable fees by carrier, by country or by city pair The System must have the facility to calculate mileage for a string of cities w/o PNR (including carrier, surface sectors, global indicators, fare amount) - Enforce carrier exceptions/IATA mileage exceptions - Follow IATA resolution 011series The System must provide a mileage explanation, after a mileage entry is requested, which includes: - Surcharged fare - Breakdown of TPMs - Calculation of TPM total - MPM - Percentage of the mileage increase (5M, 10M) - Number of miles exceeded for the resultant mileage increase - Number of miles permitted to the next mileage increase - Cumulative TPM and MPM and mileage increase for every city in the string YES 10 NO 8 NO 8 YES YES YES YES 10 10 10 10 YES 10 YES 10 Requirements Confidential Proprietary Page 91 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Miscellaneous The System must provide a report where duplicate specified and 5.6.10.1 constructed fares exist for the same origin/destination The System must provide the ability to expand the number of 5.6.10.2 characters in the FBC as required The System must provide the ability to support current and future 5.6.10.3 carrier competitive monitoring tools and revenue accounting systems as required 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 5.6.10.4 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) Ability to return fare corresponding to the available inventory 5.6.10.5 (availability of seats in the flight in the particular RBD). The system must price the lowest fare according to the RBD available. 5.6.10.6 Ability to provide 24/7 format helpdesk support for specially addressing fare related queries and problems 5.6.10 NO YES NO 6 10 10 YES 10 YES 10 YES 10 5.7 5.7.1 Codeshare General Requirements Requirements Confidential Proprietary Page 92 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to support the following codeshare approaches: - Automated freesale - Automated block space 5.7.1.1 - Manual codeshare - hardblock - Manual codeshare – softblock - Any additional code sharing approaches as per industry requirements The System must provide the ability to support one or more 5.7.1.2 codeshare approaches for the same partner. The System must provide the ability to support different codeshare 5.7.1.3 approaches with different partners on different legs/segments of a multi-leg flight. Number of partners should match IATA standards. The System must provide the ability to exchange request, reply and notification messages between marketing and operating carrier (e.g. 5.7.1.4 waitlist confirmation, advance seat request, special service request, segment sell, rebook information). 5.7.1.5 The System must provide the functionality to support all codeshare approaches with other modes of transportation (e.g. train, bus, boat) The System must ensure that operational information is automatically included with any marketing information retrieval based on carrier specific rules, and vice versa (e.g. itineraries , inventory data) The System must provide the ability to translate all flight numbers into their marketing or operating carrier flight number(s) for all codeshare arrangements The System must support the disclosure of operating carrier information (e.g. wetlease / regional) for all distribution channels, as required by law or as bilaterally agreed The System must support the disclosure of operating carrier information (e.g. carrier code, flight number, class) on all media types for the customer (e.g. tickets, boarding authority, itinerary documents) as determined by the carrier YES 10 YES 10 YES 10 YES 10 YES 8 5.7.1.6 YES 10 5.7.1.7 YES 10 5.7.1.8 YES 10 5.7.1.9 YES 10 Requirements Confidential Proprietary Page 93 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support all IATA standards regarding the exchange of codeshare data The System must support standard bilateral messaging agreed by 5.7.1.11 the partners (e.g. TRL messages, SPT messages, preferred customer information) 5.7.1.10 The System must provide interactive communication (e.g. availability, segment sell, seat assignment, seat maps) either directly with operating carrier, marketing carrier, or between marketing and operating carrier (e.g. interactive sell against 5.7.1.12 marketing flight results in inventory adjustment of operating carrier). Communication must be provided for all parameters (e.g. partner, market, days from departure, flight number, codeshare approaches) based on carrier specific rules The System must provide the ability to support multiple operating flight numbers of one carrier using the single marketing flight number of one partner 5.7.1.13 e.g. LAX-ORD-IAD (both AB operated, different flight numbers) 1) LAX-ORD = AI*9000/ AB890 2) LAX-IAD = AI*9000 / AB890 and AB892 The System must provide the ability to support multiple operating flight numbers of multiple carriers using the single marketing flight number of one partner 5.7.1.14 e.g. ORD-FRA-CPH (AB123 and BC456) 1) ORD-FRA = AI*9500/ AB123 2) FRA-CPH = AI*9500 / BC456 3) ORD-CPH = AI*9500 /AB123 and BC456 The System must provide the ability to support one marketing flight number on multiple legs of a single operating flight number of one partner 5.7.1.15 e.g. ORD-MEX-SJO (AB567) 1) ORD-MEX = AI*7000/ AB567 2) MEX-SJO = AI*7000/ AB567 3) ORD-SJO = AI*7000/ AB567 Requirements YES YES 10 10 YES 10 NO 6 NO 6 NO 6 Confidential Proprietary Page 94 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to codeshare on regional 5.7.1.16 partners, wetleases, and virtual airlines (e.g. multiple carriers operating under one designator code) The System must provide a single source for all information related 5.7.1.17 to marketing and operating flights. (e.g. one itinerary , one flight record, one inventory record) The System must provide the ability to easily set-up a new 5.7.1.18 codeshare agreement. 5.7.1.19 The System must provide the ability to support all valid AIRIMP options to exchange data between marketing and operating carriers YES 10 YES YES YES 10 10 10 The System must provide the ability to generate documents either in 5.7.1.20 marketing or operating carrier format, according to bilateral agreements 5.7.2 Codeshare Control The System must provide the ability to control and view the details and logic that support the automated processing of codeshare agreements (e.g. codeshare control parameters that identify codeshare AIRIMP option for message exchange, group bookings allowed) The System must provide class mapping functionality controlled by the marketing and operating carriers that allows the creation and application based on carrier specific rules (e.g. based on market, effective date, O&D) The System must provide class mapping functionality to be displayed by business rules (e.g. by equipment code type, by booking class, by cabin) The System must provide the ability to control and view the association of operating and marketing flights, subject to bilateral agreement. YES 10 5.7.2.1 YES 10 5.7.2.2 YES 10 5.7.2.3 YES 10 5.7.2.4 YES 10 Requirements Confidential Proprietary Page 95 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to allow/disallow the following types of passengers (but not limited to) on marketing flights: - Non-revenue (confirmed and listed/space available) - Groups 5.7.2.5 - Wholesaler / consolidator / allotments - Passengers using frequent flyer miles for travel (award/redemption) - Passengers requesting advanced confirmed upgrades - Others The System must provide the ability to identify and retrieve the 5.7.2.6 different codeshare approaches by leg/segment, whenever marketing or operating data is requested. The System must provide the ability to automatically validate the rules of the operating carrier regarding special service requirements 5.7.2.7 for the marketing flight and process the requests based on parameters defined by the partners regardless of the booking source. The System must provide the ability to automatically validate the rules of the operating carrier regarding advance seat reservation 5.7.2.8 requests for the marketing flight and process the requests based on parameters defined by the partners regardless of the booking source. Retrieval of Information The System must provide the flexibility to comply with all legal rules 5.7.3.1 that apply to airline systems or GDSs. The System must ensure that all information that exists for operating 5.7.3.2 flights is also available for marketing flights (e.g. schedule, time table availability, bookings) 5.7.3 YES 10 YES 10 YES 10 YES 10 YES YES 10 10 Requirements Confidential Proprietary Page 96 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must clearly identify data related to each marketing flight number and automatically include it in the marketing 5.7.3.3 information of the operating flight data (e.g. in the booking information of a AI operating flight passengers booked on EK*, MH* or any other marketing flight must be clearly identified). Provide the ability in a block space codeshare to retrieve partial seat 5.7.3.4 map information when the seats available are different than the block size (e.g. less seats than inventory allocation) 5.7.4 5.7.4.1 Schedule The System must support creation of marketing flight inventory and flight records for codeshare handling with other carriers for subsequent processing of incoming AVS, quota sales control and the sending of AVS The System must ensure that the source of FLIFO must be the operating flight with retrieval by either marketing or operating flight data. The System must provide the ability to automatically synchronize the marketing flight(s) with the operating flight based on criteria as mutually agreed by the partners. The System must ensure that ASM/SSM for an operating flight number sent out to systems outside must automatically create ASM/SSM for the related marketing flight number(s). YES 10 NO 6 YES 10 5.7.4.2 YES 10 5.7.4.3 YES 10 5.7.4.4 YES 10 The System must provide the ability to process a single inbound ASM/SSM sent by the operating carrier to one pre-designated point 5.7.4.5 (PDP) to be processed for all associated marketing flight numbers and generate ASM/SSM as appropriate. The System must provide the ability to have a simultaneous handoff of marketing and operating carrier‟s full schedule directly to the 5.7.4.6 GDSs, airline systems, and/or OAG. Provide the functionality to initiate the hand-off automatically as well as manually, based on carrier specific rules. NO 8 NO 8 Requirements Confidential Proprietary Page 97 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.7.4.7 5.7.4.8 The System must provide the ability to exchange SSIM files with partners Airlines on a frequency as determined by the partners. YES YES NO 10 10 8 The System must provide the ability to exchange ASM/SSM with partners Airlines for dynamic schedule update. The System must provide the ability to process schedule changes 5.7.4.9 (e.g. operational flight number changes) automatically without manual intervention for related marketing flight(s) The System must provide the ability to manually initiate new flight 5.7.4.10 relationship between partner Airlines and/or close an old flight relationship. 5.7.4.11 5.7.4.12 5.7.5 The System must provide the ability to assign one marketing flight number to different operating partners, defined by date range. The System must support traffic restrictions filed by the marketing carrier NO 8 YES YES 10 10 Passenger Re-accommodation The System must create re-book proposals for marketing flights 5.7.5.1 upon cancellation of a partner Airlines operating flight The System must support the notification of codeshare partners of 5.7.5.2 close-in schedule changes 5.7.5.3 The System must provide the flexibility for re-accommodation by either operating and/or marketing carrier, as bilaterally agreed. YES YES YES 10 10 10 The System must provide the ability for re-accommodation logic as defined by the partners, and initiated by the carrier who is in control of the inventory (e.g. availability, frequent flyer status, customer 5.7.5.4 value, unaccompanied minors, onward connections, time before departure, overbooking parameters, itinerary-based, economicbased) The System must provide the carrier in control of the inventory the 5.7.5.5 ability to override re-accommodation logic where necessary YES 10 YES 10 Requirements Confidential Proprietary Page 98 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to allow manual re5.7.5.6 accommodation of passengers on operating or marketing flights, according to re-accommodation logic. The System must provide the ability to allow automated reaccommodation of passengers on another flight, according to re5.7.5.7 accommodation logic, no matter if it is an operating or marketing flight, as part of schedule change process (e.g. SSIM or ASM/SSM) 5.7.6 5.7.6.1 5.7.6.2 5.7.6.3 5.7.6.4 5.7.6.5 5.7.6.6 5.7.6.7 5.7.6.8 5.7.6.9 Inventory The System must provide the ability to host multiple block codeshares on a single operating flight The System must have the facility to identify marketing partner bookings in operating carrier inventory The System must provide the ability for block codeshare to be handled same as an operating flight (e.g. optimize, setting of inventory controls) The System must provide the ability to support booking class conversion, with effective/discontinue date capability The System must have the ability to support the same number of RBDs and RBD concepts on marketing flight numbers as defined for operating flights. The System must provide the ability that the marketing carrier will use it‟s own RBD structure for marketing flights Provide the flexibility to define different quota sales per RBD and by cabin depending on the agreement with the partners Distinguish between a link or teletype booking according to IATA standard (CK, CS) The System must ensure that for link booking, provide the ability to accept a sell message from a marketing carrier against RBD availability, subject to bilateral agreement The System must ensure that for teletype booking, provide the ability to accept or reject a sell message from a marketing carrier depending on availability of operating carrier, subject to bilateral agreement YES 10 YES 10 YES YES YES YES YES YES YES YES YES 10 10 10 10 10 10 10 10 10 5.7.6.10 YES 10 Requirements Confidential Proprietary Page 99 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must ensure that the CS action code is treated as 5.7.6.11 teletype or guaranteed booking, depending on agreement with the partner, subject to bilateral agreement The System must support waitlist clearance based on carrier 5.7.6.12 specific rules (e.g. by booking class, tier status of partner) The System must provide the ability for the operating carrier to block 5.7.6.13 part of the inventory and/or seat map per compartment for the use of one or more marketing carriers. The System must provide the ability for the marketing carrier to sell 5.7.6.14 a subset of the operating carrier inventory and/or seat map The System must provide the ability to support automatic sending and receiving seat release messages for soft block codeshare 5.7.6.15 arrangements and update inventory records according to carrier specific rules The System must ensure that in block codeshare provide the ability 5.7.6.16 to retrieve marketing carrier bookings The System must provide the ability to exchange messages without 5.7.6.17 updating the inventory of the operating flight in an automated block codeshare The System must provide the ability to handle/reject specific action 5.7.6.18 codes for segment sell on marketing flights, based on bilateral agreements (e.g. forced bookings) The System must provide the ability to request additional or release 5.7.6.19 surplus inventory in an automated fashion for a soft block, based on carrier specific rules 5.7.6.20 The System must provide the ability to migrate from a block space agreement to a free-sale agreement using the same flight number YES YES NO NO 10 10 6 6 YES 10 NO NO 8 8 NO 10 NO 6 NO 8 Availability The System must support codeshare rerouting and cascading 5.7.7.1 (availability and sell allows O&D control for operating carrier) 5.7.7.2 The System must provide the ability for identification of the operating, regional or non-air partner, based on carrier specific rules 5.7.7 NO YES 8 10 Requirements Confidential Proprietary Page 100 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Availability Messages The System must provide AVS/AVN messaging information based 5.7.8.1 on either marketing flight/RBD or operating flight/RBD The System must provide the ability to handle inbound/outbound AVS/AVN open/close messages sent by operating carrier to 5.7.8.2 marketing carrier which might need distribution to the GDSs or any other airline systems The System must provide the ability to handle inbound/outbound RAS messages sent by the marketing carrier to operating carrier 5.7.8.3 with responses as appropriate. RAS messages can be based on marketing or operating carrier flight data The System must provide the ability to request AVS/AVN at time of 5.7.8.4 marketing flight creation, to synchronize inventory for operating flights with a longer booking window. The System must provide the ability to send AVS/AVN recap 5.7.8.5 messages depending on the marketing carrier booking range The System must provide the ability to process a single inbound AVS/AVN sent by the operating carrier to one PDP to be processed 5.7.8.6 for all associated marketing flight numbers, and generate AVS/AVN as appropriate. The System must provide the ability to allow a marketing flight to 5.7.8.7 generate and distribute AVS/AVN in a block codeshare. The System must provide the ability to distinguish between freesale 5.7.8.8 and block codeshare flights as only freesale flights are controlled by the operating carriers AVS/AVN. The System must ensure that changes of the carrier‟s operating flight automatically update associated marketing flight(s), and 5.7.8.9 generate AVS/AVN for both operating and marketing flights based on carrier specific rules 5.7.8 YES 10 YES 10 YES 10 YES YES 10 10 YES 10 YES YES 10 10 YES 10 Requirements Confidential Proprietary Page 101 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support creation of a new marketing flight number, related to an operating carrier, will synchronize from 5.7.8.10 AVS/AVN status stored on the associated operating flight and generate AVS/AVN for the marketing flights based on the rules of the carriers. The System must provide the flexibility to define rules and 5.7.8.11 parameters for the transmission of AVS/AVN handling (e.g. open /close levels, batch volume) The System must provide the ability for sending out AVS/AVN for 5.7.8.12 marketing flights should have the same capability as for operating flights. 5.7.8.13 Inbound/outbound AVS message to trigger seamless or selective polling – sent by operating carrier with the marketing flight number. YES 10 YES 10 YES 10 YES 10 The System must provide the ability to adapt the marketing flight to 5.7.8.14 the operating carrier‟s booking window. (e.g. when operating carries‟ booking window is shorter than that of marketing carrier) 5.7.8.15 5.7.9 5.7.9.1 The System must provide the ability for leg and segment based AVS/AVN for marketing flights. Airport Customer Service The System must support PNL/ADL for manual codeshare – PNL/ADL sent per marketing carrier some number of hours prior to departure to the operating carrier‟s reservation or check-in system, as agreed between partners. The System must support PNL/ADL from multiple marketing carriers for one operating flight. The System must support one combined PNL/ADL for multiple marketing partners and send to operating partner. The System must provide the ability to receive and process PNL/ADL messages sent to other Airlines , to automatically create or update PNRs. YES 10 YES 10 YES 10 5.7.9.2 5.7.9.3 5.7.9.4 YES NO YES 10 10 10 Requirements Confidential Proprietary Page 102 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must identify on the PNL/ADL the passengers booked 5.7.9.5 on marketing flights according to IATA resolution (e.g. .M/ element) in a ground handling situation 5.7.9.6 The System must provide the ability to send/receive and process automatically an PNL from or to a partner of ground handler The System must provide the ability to support and process complete or split post departure messages, split either for one or more marketing flight numbers as defined by the carrier. Messages should be sent to operating carrier as appropriate. The system must provide the ability to receive one combined post departure message for multiple marketing partners The System must provide the ability for post departure messages to automatically reconcile the PNR for both operating and marketing flights The System must provide capabilities for post departure reconciliation and reporting for all types of codeshare approaches (e.g. PFS or handoff to internal carrier systems) The System must provide the ability to support booking class conversion with effective/discontinue date capability Synchronization processes will apply to operating flights as well as marketing flights, in case changes are done to bookings before departure. The System must provide the ability for marketing carrier to check in passengers, booked on marketing flights, on behalf of the operating carrier. The System must provide the ability to check in a customer on an operating flight using either the operating carrier or the marketing carrier flight number The System must support indiscriminate check-in of marketing and operating carrier customers on first come first serve basis In block codeshare provide the ability to force passengers (either marketing or operating) to a standby list once that carrier reaches their specific allocation. YES 10 YES 10 5.7.9.7 NO 6 5.7.9.8 5.7.9.9 NO YES 10 10 5.7.9.10 5.7.9.11 5.7.9.12 YES YES YES 10 8 10 5.7.9.13 YES 10 5.7.9.14 5.7.9.15 5.7.9.16 YES NO NO 10 8 8 Requirements Confidential Proprietary Page 103 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.7.9.17 5.7.9.18 5.7.9.19 5.7.9.20 5.7.10 5.7.10.1 The System must provide the ability to overwrite block codeshare at check-in to accept a passenger in the block of the partner depending on bilateral agreement between operating and marketing partner. The System must provide the ability to generate an EDIFACT through check in request to the operating carrier for check in requests for a marketing flight. The System must provide the ability to check in a customer using operating or marketing flight information The System must support premium customer information data as part of PNL processing Codeshare Quality Control The System must provide the ability for automated reconciliation. (E.g. number of codeshare bookings against inventory). NO 8 YES YES YES 10 10 10 YES 10 The System must provide the ability to control acceptance of 5.7.10.2 codeshare bookings per partner and/or flight number controlled by the operating carrier, subject to bilateral agreement. The System must provide the ability to reconcile involuntary 5.7.10.3 upgrades with block codeshare partners, based on carrier specific rules The System must provide the ability for overbooking control (e.g. 5.7.10.4 AVS/AVN recap, queuing) The System must provide the ability to re-send bookings on marketing flight numbers and to reflect those bookings in operating 5.7.10.5 carrier inventory (e.g. passengers booked on marketing flight but not on corresponding operating flight) according to carrier specific rules The System must provide the ability to synchronize operating and marketing flight status by RBD. The System must provide the ability to re-send a message to the 5.7.10.7 marketing carrier, GDSs without rebooking (e.g. waitlist clearance, record locator, seat confirmation) 5.7.10.6 YES 10 NO YES 8 10 NO 8 NO YES 8 10 Requirements Confidential Proprietary Page 104 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to retrieve history of changes to 5.7.10.8 marketing flight information (e.g. schedule, PNR , marketing relationship) YES 10 5.8 5.8.1 5.8.1.1 Departure Control Data Synchronization The System must at any touch point, maintain synchronization between the electronic ticket, RES and DCS activities (consistent data for all access points) The system must support creation of All applicable Engineering Data base records and Station records and other static file maintenance data required for Online DCS check in and weight & balance The system must provide security for access and update of above records The system must have the capability for creating the flight schedule in DCS with the Aircraft type, configuration, class, seating zone, check in option, baggage, category loading, short haul/long haul information, payload, crew/pantry codes, departure terminal number, route, and other required features for flight check in and weight & balance The System must support Auto Edit facility and Manual Edit facility YES 10 5.8.1.2 YES 10 5.8.1.3 YES 10 5.8.1.4 YES 10 for FIT & Groups for services such as Meal Request / MEDA / WCHR / FQTV / Advance Seat Reservation / Lady with Infant / Un 5.8.1.5 accompanied Minor for NACIL Own flights and be capable of using the Carrier Edit Record of Handled Airlines‟ for Auto editing their flights. 5.8.2 Flight Management YES 10 Requirements Confidential Proprietary Page 105 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.8.2.1 5.8.2.2 5.8.2.3 5.8.2.4 5.8.2.5 The System must provide the ability to automatically activate flights for check-in (with manual override capability), including related characteristics, based on carrier specific rules: - APIS/NFL-SL/AQQ/ e-Borders/ APP/PTS/Canadian PPP/APIS India required - Equipment type with nose/tail number - Seat map, including free seating flights - Boarding time parameter - Departure time, including schedule and actual - Gate information - Round-trip check-in - Security question dialogue - Electronic ticket eligibility - Baggage allowance - Baggage loading details The System must provide the ability to automatically and manually open flight for check-in based on various factors, e.g. predetermined times, location, or inbound through check-in requests, based on carrier specific rules The System must be capable of creating flights at least 3 days in advance of the flight departure date and retain the flight on live system for 4 days after departure. The system must have an auto purge utility to purge departed flight data and store the purged data in an offline media for future reference The System must provide the ability to create new flights on demand with the full range of characteristics e.g. scheduled, charter, ground handled, test, pseudo flights, ground transportation flights, and flights that are not in the reservation schedule YES 10 YES 10 YES YES 10 10 YES 10 The System must provide the ability to manipulate one, some or all existing flights on demand, including the ability to change equipment 5.8.2.6 type or seat configuration without interference with check-in activities, and automatically reseat customers affected by the equipment change YES 10 Requirements Confidential Proprietary Page 106 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to manually suspend check-in 5.8.2.7 temporarily, e.g. due to weather conditions, and ability to reverse the suspension The System must provide the ability to automatically inhibit local 5.8.2.8 and/or through check-in, and/or issuance of baggage tags based on carrier specific rules The System must provide the ability to dynamically update flight 5.8.2.9 characteristics, including interface from backend systems as applicable, e.g. change in gate assignment, forecast departure time 5.8.2.10 5.8.3 The System must provide the ability to view flight data based on carrier specific rules YES 10 YES 10 YES 10 NO 8 Basic Check-in The System must provide the ability to automatically or manually 5.8.3.1 edit specific passengers characteristics continuously after flight creation and until flight close-out The System must have the facility to automatically recommend specific customers for VDB and/or alternate more cost effective 5.8.3.2 routing, or up/downgrade as appropriate based on passenger booking level and passenger profile. The System must automatically mark customers for upgrade when 5.8.3.3 sufficient mileage is available in their account. If accepted by customer, automatically deduct account The System must provide the ability to t support a variety of advance seating/check-in statuses e.g. but not limited to: - Preassigned seat based on passenger types and customer value - Restrict specific passenger types from selected areas, e.g. infants 5.8.3.4 in exit rows - Soft-hold seat assignment - Attempt to hold adjacent empty seats for high value customers - Guarantee acceptance even without seat assignment YES 10 NO 6 NO 8 YES 10 Requirements Confidential Proprietary Page 107 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must allow holding/blocking of specific seats for use by specified airport (applies to multi stop flights), establish and protect 5.8.3.5 designated seats on every flight for use by airport personnel (to ensure family/group seating), and baggage hold seats The System must automatically set limits for revenue and non5.8.3.6 revenue acceptance, weight restrictions, oversale, based on carrier specific rules The System must dynamically update limits based on inventory level 5.8.3.7 changes The System must provide the ability to differentiate customer processing at check-in based on carrier specific rules. Types of passengers include but are not limited to: - FQTV tier / type - Premium customer - Revenue & non-revenue - Goshow and Norec - Special service (UM, STCR) - Infants 5.8.3.8 - Children - Groups - Unsplittable groups - Families / parties - Jump seat passenger - Selectee - Air Marshall - Deadhead crew - Previously inconvenienced (e.g. DB) - High / Low yield YES 10 YES YES 10 10 YES 10 Requirements Confidential Proprietary Page 108 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to identify passengers by different means (e.g. card swipe, magnetic stripe reader, biometrics reader) and allowing different search criteria (e.g. name, credit card number, ticket number, identification card number, multiple frequent flyer numbers.). Upon successful match, initiate following subprocesses: - Check if coupon is in available status - Search for electronic ticket or if no corresponding electronic ticket can be found, search for alternative electronic ticket (e.g. open coupons) - Ticket verification (stolen ticket information) - Comparison of reservation data and passenger travel plan and 5.8.3.9 ticket data - Informational record creation for goshow/norec - Calculation of any required additional fees or refunds if applicable - Document verification, e.g. credit card for electronic tickets, passport/visa information - Upgrade validity, tier level (e.g. based on fare rule, mileage) - Passenger security verification including destination country, government regulatory requiremnts such as NFL/SL, APIS, AQQ, APP, PPP, PTS, e-borders - Undesirable customer verification - Previous customer inconveniences - Search for VDB possibility The System must provide the ability to automatically process 5.8.3.10 predetermined fee decisions, e.g. fee waivers, including applicable user prompts for customer notification purposes The System must provide the ability to link customers traveling 5.8.3.11 together so that they may be considered together at every touch point The System must automatically invoke next steps based on all automated validation results, e.g. proceeding with check-in, upgrade 5.8.3.12 processing, additional collection of fees based on carrier specific rules Requirements YES 10 NO 8 YES 10 YES 10 Confidential Proprietary Page 109 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to automatically or on demand, 5.8.3.13 edit, modify, cancel information related to a specific customer/baggage, party or group The System must provide the ability to edit information to selected 5.8.3.14 or all flights in the customer‟s itinerary subject to carrier specific rules The System must provide the ability to add/delete/modify special 5.8.3.15 service requests and other service information (SSR/OSI) according to IATA standards or carrier specific rules The System must provide the ability to automatically or manually capture current customer experience for local information and 5.8.3.16 handoff to CRM (e.g. DBC, voucher issued, involuntary up/downgrade, misconnection) The System must provide the ability to edit passenger type (e.g. UM, 5.8.3.17 senior citizen, family) to allow differentiation of service The System must provide the ability to split linked customers on 5.8.3.18 demand, automatically invoking system routines e.g. eliminating tier benefit, baggage group code cancellation The System must provide the ability to add / modify / delete 5.8.3.19 customers‟ desire to upgrade or downgrade (customer service) The System must provide the ability to add / modify / delete frequent 5.8.3.20 flyer numbers and types, (and tier level for ground handled carriers). Automatically update tier level The system must reflect the updated tier level of loyalty members 5.8.3.21 and update baggage information to reflect new status / priority (e.g. for BSM/BTM) The System must automatically generate and process RP1745 messages, e.g.: - Baggage transfer message (BTM) - Baggage source message (BSM) 5.8.3.22 - Baggage unload message (BUM) - Baggage process message (BPM) - Baggage change message (BCM) - Baggage manifest message (BMM) YES 10 YES 10 YES 10 NO 10 YES YES YES YES 10 10 10 10 YES 10 YES 10 Requirements Confidential Proprietary Page 110 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to add / modify / delete 5.8.3.23 baggage information, leading to automated baggage fee calculation and prompts, as well as generate special handling bag tag The System must provide the ability to manually add / modify / delete onward connection flights, with automatic validation of connection rules, e.g. MCT, ticketing and baggage check agreements The System must provide the ability to cascade selected information like APIS data, baggage data etc., between the flights (in both directions) The System must provide the ability to identify customer eligible for VDB/DBC and automatically calculate compensation as well as search for most cost efficient alternative flight The System must provide the ability to re-check passenger and baggage to a different flight/DESTINATION (offload from “old” and check-in on new flight)/ DIFFERENT DESTINATION ON SAME FLIGHT, copying pertinent passenger and baggage information to new record, and ensuring synchronization between reservations, baggage and availability ; automatically send bag change message to baggage handlers YES 10 5.8.3.24 YES 10 5.8.3.25 NO 10 5.8.3.26 NO 8 5.8.3.27 YES 6 The System must provide the ability to link all customers and baggage information on multiple flight records, (ability to check-in on 5.8.3.28 several flights at one time); upon boarding and departure of first flight, automatically offload customer from all alternate flights sending baggage change message, based on carrier specific rules The System must provide the ability to create an electronic image of a paper ticket coupon in order to handoff pertinent information to 5.8.3.29 revenue accounting system (e.g. ticket number, coupon number). Upon boarding mark coupon used to prevent future use or refund of the paper coupon NO 6 YES 10 Requirements Confidential Proprietary Page 111 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Upon successful completion of passenger & baggage check-in, automatically and dynamically update passenger, baggage & flight 5.8.3.30 data, , e.g. seat map, flight levels, BSM, weight & balance, triggering handoff to other systems based on carrier specific rules 5.8.3.31 5.8.3.32 5.8.3.33 5.8.3.34 5.8.3.35 The System must provide the ability to check-in customers on roundrobin flights The System must provide the ability to check-in customers on change of gauge flights The system must automatically generating change of gauge message to customer based on carrier specific rules. The System must provide the ability to check-in customers on funnel flights The System must automatically trigger check-in from incoming PTM, or combination of PTM and BTM The System must provide the ability to automatically check-in and accept (e.g. assign seat to) space available customers based on availability thresholds, and carrier specific rules. Once the threshold is met, subsequent customers must automatically be placed on the standby list The System must provide the ability to check customer to final destination (including other modes of transportation) YES 10 YES YES NO NO NO 10 8 6 8 4 5.8.3.36 YES 10 5.8.3.37 YES 10 The System must provide the ability to and check-in for full itinerary or short-check, based on carrier specific rules (check-in short of 5.8.3.38 final destination), automatically generating information card advising customer of the final destination of the bag The System must provide the ability to check customer on specified 5.8.3.39 (by flight, market, carrier) same-day return flights, based on carrier specific rules The System must provide the ability to check-in several customers 5.8.3.40 together to different final destinations, or to same destination in different cabins YES 10 YES 4 NO 6 Requirements Confidential Proprietary Page 112 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to through-check when there is a change of airport at the connection city, based on carrier specific 5.8.3.41 rules while ensuring that the baggage data remains linked to the passenger The System must provide the ability to automatically check 5.8.3.42 customer to final destination served by a supplier (including other modes of transportation ) across different CARRIERS or systems The System must provide the ability to support manual inter airline 5.8.3.43 through check-in requests by adding the on carriage edit of the other airlines manually The System must support interline local check-in (ILCI) using IATCI 5.8.3.44 messages, e.g. to allow a marketing carrier to check-in a customer on an ON AN operating flight The System must provide the ability to interface with carriers to: - Add or delete information (frequent flyer numbers, SSRs) - Modify seat assignments (by flight or by segment of a flight) 5.8.3.45 - View seat map (by flight or segment of a flight) - Offload seats - Exchange APIS/APP/ AQQ data - Reprint boarding passes The System must provide the ability to support inter airline through check-in when no more seats can be assigned, updating 5.8.3.46 standby/need seat information accordingly and producing appropriate boarding authority indicating that gate intervention is required The System must provide user accessible EDIFACT message 5.8.3.47 tracing capability, including statistics and reason for failure The System must provide the ability to support outgoing IFMs and 5.8.3.48 automated processing of incoming IFMs based on carrier specific rules The System must provide the ability to verify compliance with pre5.8.3.49 requisites before accepting passengers for boarding (e.g. APIS/NFLSL/AQQ/ e-borders/ APP/PTS/Canadian PPP/APIS India required) YES 10 YES 10 NO 6 NO 4 YES 10 NO 4 NO YES 4 10 YES 10 Requirements Confidential Proprietary Page 113 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to produce a boarding authority, 5.8.3.50 or if necessary, boarding document, which permits automated boarding Boarding authority must hold and encode, according to agreed standards, all relevant information for one or multiple flights, e.g.: - Boarding number or unique passenger identifier for flight (e.g. machine readable passport, credit card, biometric identification) - Boarding process related information (boarding sequence information) e.g. classes, zones, rows) - Flight number - Boarding and departure times - Gate number 5.8.3.51 - Operating carrier - Change of gauge - Lounge access - Tier-level - Security information - Duty-free - Ticket and coupon number - Seat number - Miscellaneous messages The System must provide boarding authority that will support 5.8.3.52 customers who deboard and reboard the same single or multi-leg flight The System must support production of boarding authority when 5.8.3.53 using alternate check-in channels The System must provide the ability to support various print 5.8.3.54 functions based on regulatory requirements The System must provide the ability to produce a standby authority 5.8.3.55 which includes all relevant information with the exception of seat number and boarding authority YES 10 YES 10 YES YES YES YES 10 10 10 10 Requirements Confidential Proprietary Page 114 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to verify compliance with pre5.8.3.56 requisites before production of boarding authority (e.g. APIS/NFLSL/AQQ/ e-borders/ APP/PTS/Canadian PPP/APIS India required) The System must provide the ability for alternate forms of check-in without boarding authority issuance, (e.g. telephone) potentially with 5.8.3.57 off-site baggage acceptance (e.g. Fed-ex) subject to carrier specific rules The System must provide the ability for alternate check-in with boarding authority issuance and baggage acceptance (e.g. curb5.8.3.58 side, day before check-in, at railway station, or hotel check-in, KIOSK, WEB CHECK-IN), subject to carrier specific rules 5.8.3.59 5.8.3.60 The System must provide procedural information for customer, depending on alternate check-in type Differentiate between confirmed space and space available and apply carrier specific rules (e.g. boarding priorities, baggage acceptability) Determine immediate acceptability or standby based on level of bookings and other criteria, based on carrier specific rules (e.g. standby limit) The System must provide the ability to track and handoff who/when/how/by whom any pax ( rev/non rev) employee is onloaded subject to carrier specific rules The System must provide the ability to translate and prioritize nonrevenue (duty travel or pleasure) priorities based on carrier specific rules YES 10 NO 6 YES 10 YES YES 10 10 5.8.3.61 YES 10 5.8.3.62 YES 10 5.8.3.63 YES 10 Based on carrier specific rules, provide the ability to query employee 5.8.3.64 data base (or other, e.g. the FBI passenger security database) to determine eligibility for flight deck or cabin jump seat The System must provide the ability to automatically generate a 5.8.3.65 boarding authority that contains all pertinent employee data for tracking purposes and incident handling NO 4 NO 4 Requirements Confidential Proprietary Page 115 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support electronic ticket travel for employees groups, based on carrier specific rules The System must support ticketless travel for employee groups, 5.8.3.67 based on carrier specific rules The System must support handoff to back end systems to record 5.8.3.68 employee travel and ensure appropriate employee billings, based on carrier specific rules 5.8.3.66 5.8.3.69 5.8.3.70 The System must support special employee baggage policy based on carrier specific rules, (e.g. special baggage allowance provisions) YES NO NO 10 4 4 NO YES YES YES YES 4 10 10 10 10 The System must provide the ability to check-in multiple passengers (identified as a group in the Group Record) The System must support advance check-in of groups including 5.8.3.71 their baggage, based on information captured from the Group Record, and carrier specific rules Allow check-in of group customers without their baggage, with 5.8.3.72 baggage information added later The System must support intuitive tool for baggage association (e.g. 5.8.3.73 from group leader to individual group members) The System must provide the ability to support individual preferences, including linking of two or more passengers together 5.8.3.74 and ability to choose specific seat characteristics (e.g. seat number, aisle, desire to sit with a particular member(s) of the group) The System must provide the ability to automatically accept customers (and baggage) with confirmed status tickets and no 5.8.3.75 corresponding check-in record, based on carrier specific rules. When no seats are available, place customer on standby, with carrier specific priority The System must provide the ability to query passenger security 5.8.3.76 databases to determine acceptability prior to checking-in the customer, based on carrier specific rules The System must provide the ability to place on standby or 5.8.3.77 automatically accept passengers and baggage, based on flight booking levels and carrier specific rules, e.g. boarding priority Requirements YES 10 YES 10 YES 10 YES 10 Confidential Proprietary Page 116 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to collect form of payment at 5.8.3.78 time of check-in and automatically process billing of fee at time of boarding, (e.g. standby fees, “pay as you fly”) 5.8.3.79 The System must automatically determine eligibility for standby, based on fare rules, and according to carrier specific rules The System must provide the ability to produce or print all documents from any touch point, including but not limited to electronic ticket itinerary / receipt, meal, ground transportation, or hotel vouchers and FIMs The System must provide the ability to synchronize data with reservation record and handoff required information, to backend systems, including but not limited to CRM The System must provide the ability to generate informational passenger cards, e.g.: - Lounge information - Airport information - Directions to codeshare partners - Security processing information - Denied boarding compensation The System must provide the ability to automatically validate ticket acceptability, fare rule, stolen ticket validation, credit card, back-toback ticketing abuse, including at re-check situations and electronic ticket revalidation The System must provide the ability to easily create, edit or modify and delete validation rules, with effective and discontinue times/dates, based on carrier specific rules The System must automatically inhibit check-in when validation fails and invalidate ticket if appropriate. The System must provide the ability to automatically collect fees, e.g. rebooking fees, producing documents, e.g. MCO, special service and revalidating ticket, when permitted, based on carrier specific rules Premium Customer Handling NO 6 YES 8 5.8.3.80 NO 6 5.8.3.81 YES 10 5.8.3.82 NO 8 5.8.3.83 YES 10 5.8.3.84 5.8.3.85 YES NO 10 8 5.8.3.86 NO 8 5.8.4 Requirements Confidential Proprietary Page 117 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.8.4.1 The System must provide the ability to recognize all tier levels at any touch point, including ground handled carriers YES 10 The System must provide the ability to differentiate tier levels and provide the agreed benefits to premium customers at any touch point, based on ground handled carriers‟ specific rules e.g.: - Excess baggage allowance 5.8.4.2 - Priority standby - Lounge access - Fast track immigration - Security 5.8.4.3 5.8.4.4 5.8.4.5 5.8.4.6 5.8.4.7 The System must provide the ability to automatically update the tier level whenever a frequent flyer number is added or modified The System must provide the ability to manually add/modify a frequent flyer number and/or tier level for all ground handled carriers‟ flights The System must provide the ability to add/modify/delete a frequent flyer number for all or selected flights of the itinerary The System must provide the ability to add a frequent flyer number for post departed and past date flights and publication to the Frequent Flyer system The System must provide the ability to differentiate FQTV, FQTR, FQTU, and correctly process benefits/service The System must provide the ability to allow more than one frequent flyer number with different service types per segment, e.g. FQTU associated to an IX frequent flyer number together with an FQTV associated to an AI frequent flyer number for the same segment, according to carrier specific rules The System must provide the ability to provide preferred benefits to selected customers (not identified as frequent flyers), based on carrier specific rules Seating NO 6 YES YES YES NO YES 10 10 10 6 10 5.8.4.8 NO 6 5.8.4.9 NO 10 5.8.5 Requirements Confidential Proprietary Page 118 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to retrieve a seat map by 5.8.5.1 various criteria (e.g. full aircraft, cabin, seat type, other modes of transportation), The System must provide the ability to retrieve seat map by 5.8.5.2 compartment, by one segment, multiple segments, or the entire flight The System must support different booking class structures on each 5.8.5.3 segment of a multi-leg flight The System must provide automated dynamic refresh of seat map 5.8.5.4 as seat selections occur The System must provide the ability to manually update seat 5.8.5.5 characteristics The System must provide the ability to manage seat assignment 5.8.5.6 logic based on carrier specific rules The System must provide the ability to offer seating based on 5.8.5.7 customer value and other carrier specific rules (e.g. fare level, FQTV status, O & D) 5.8.5.8 The System must provide the ability to assign boarding sequence criteria, e.g. boarding zones, based on carrier specific rules YES 10 YES YES YES YES YES YES 10 10 10 10 10 10 YES 10 The System must automatically block adjacent seats for qualified 5.8.5.9 customers in certain zones, including automated release of those seats, based on carrier specific rules In case of change of gauge / different aircraft version the system 5.8.5.10 must display both the seat maps Baggage Handling The System must provide the ability to generate automated bag tags 5.8.6.1 that are compliant with IATA resolutions and evolving industry standards 5.8.6.2 5.8.6.3 The System must automatically store bag tag numbers and weight in PNR and baggage records, based on carrier specific rules The System must support unique bag tag numbers which should not be recycled within any 13 month period per carrier 5.8.6 YES NO 10 10 YES 10 YES YES 10 10 Requirements Confidential Proprietary Page 119 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to cross reference online and 5.8.6.4 interline connections between carriers to inhibit printing of baggage tags that violate minimum connection time rules The System must provide the ability to support printing of “HOT” connection baggage tags in order to accommodate carrier 5.8.6.5 authorized sub-minimum connection times, including ad hoc situations The System must provide the ability to support printing of baggage tags when a customer agrees to voluntary separation, unless 5.8.6.6 restricted for security purposes (e.g. PPBM), based on carrier specific rules. This process will generate a customer confirmation thus preventing a PAWOB. The System must provide the ability to automatically translate 5.8.6.7 marketing flight number to operating flight number. Operating flight number should be sent to other carriers in IATCI messages The System must automatically generate / process RP1745 messages, e.g.: - Baggage transfer message (BTM) - Baggage source message (BSM) - Baggage unload message (BUM) - Baggage process message (BPM) - Baggage change message (BCM) The System must automatically inhibit the production of bag tags when there is no interline baggage agreement The System must support generation of special bag tags , e.g. special characters or graphics, and colored areas The System must provide the ability to generate on demand “Exception” (e.g. expedite, company material) bag tags to bag match rule (e.g. crew tags) based on carrier specific rules, including the creation of a baggage record The System must provide the ability to generate on demand bag tags for special baggage types, (e.g. limited release (damaged goods), skis, odd-sized pieces ) YES 10 YES 10 YES 10 YES 10 5.8.6.8 YES 10 5.8.6.9 5.8.6.10 YES NO 10 10 5.8.6.11 YES 10 5.8.6.12 YES 10 Requirements Confidential Proprietary Page 120 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to ensure bag tags are not 5.8.6.13 generated for any carrier stored in a carrier‟s exception table, based on carrier specific rules The System must automatically apply short check rule with ability to 5.8.6.14 manually override The System must provide the ability to manually add segments to 5.8.6.15 the bag tag itinerary The System must provide automated creation of baggage records at 5.8.6.16 bag tag issuance and processing of inbound BTMs The System must provide the ability to support evolving 5.8.6.17 technologies e.g. RFID and 2D-symbology, to produce a baggage loading authority, allowing for baggage sorting and reconciliation Baggage loading authority must hold and encode according to agreed standards, all relevant information for one or multiple flights, e.g.: - System generated or other unique baggage tag identifier - Passenger boarding number or unique passenger identifier for flight - Flight number(s) and routing - Operating carrier - Tier-level - Security information - Miscellaneous messages - Gate / aircraft delivery - Special baggage handling (AVIH, PRIO, RUSH) The System must support production of baggage loading authority when using alternate check-in channels, based on carrier specific rules The System must provide the ability to produce a standby baggage loading authority which includes all relevant information The System must provide alternate method to tag and track bags when system fails, and associate bag tag data to PNR upon system recovery YES YES YES YES 10 10 10 10 YES 10 5.8.6.18 YES 10 5.8.6.19 5.8.6.20 5.8.6.21 YES YES YES 10 10 10 Requirements Confidential Proprietary Page 121 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to manage checked baggage for “Party check-in” in order to control PPBM, based on carrier 5.8.6.22 specific rules. In case the head of pool is de-checked the baggage detail should cascade to the next person in the party pool. The System must provide the ability to track position and status of baggage at all times, including information on baggage attributes e.g.: - Passenger association - Security loading authority - Security screening - Message history - Event history The System must provide the ability to inform customer of position and status of baggage at all times and all touch points via technology, e.g. PDA, email, BIDS, self-service devices At detection of misdirected baggage, automatically find the most appropriate alternate routing which will allow for timely arrival of baggage at destination, including updates to corresponding customer and baggage record(s) The System must provide automated assessment of excess baggage fees and issuance of appropriate tag based on type of baggage YES 10 5.8.6.23 YES 10 5.8.6.24 NO 10 5.8.6.25 NO 8 5.8.6.26 YES 10 Upon issuance of exceptional bag tags or identification of exceptional baggage, automatically generate message to weight & 5.8.6.27 balance, crew, ramp, based on carrier specific rules; exceptional baggage includes items e.g. weapons, hazardous material, bicycles The System must provide the ability to automatically assess excess 5.8.6.28 baggage fees based on weight, and store weight and fee collected in check-in and baggage records 5.8.7 Immigration & Visa Documentation NO 8 YES 10 Requirements Confidential Proprietary Page 122 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC At first point of contact and based on complete itinerary, ability to automatically capture and handoff mandatory passenger information 5.8.7.1 to various authorities, at prescribed times, at departure, arrival, or intermediate points 5.8.7.2 The System must provide the ability to maintain historical records of generated APIS manifests, based on carrier specific rules NO 10 YES 10 The System must provide the ability to identify and store the source 5.8.7.3 of all captured data (e.g., PNR, Swipe/Scan of Passport, or manually entered) The System must support multiple versions of industry standard 5.8.7.4 messages, or non standard messages, based on carrier specific rules The System must provide the ability to share PNR and check-in 5.8.7.5 information with government authorities as mandated, based on carrier specific rules At first point of contact and based on complete itinerary, generate mandatory information to various governments for their approval of 5.8.7.6 customer‟s authority to travel (e.g. visa); inhibit check-in if approval denied The System must provide the ability to maintain historical records of 5.8.7.7 authorization The System must automatically halt boarding or prompt gate agent 5.8.7.8 if clearance has not been received The System must automatically prompt user to perform document 5.8.7.9 check and inhibit check-in until successfully completed, based on carrier specific rules The System must provide the ability to scan, capture or manually 5.8.7.10 record required data from official documents, e.g. OCR types ICAO 9303, or other acceptable documents (e.g. drivers license) The System must automatically query information providers (e.g. 5.8.7.11 TIMATIC for destination and transit rules, and automatically notify user of required documentation) YES 10 YES 10 YES 10 YES 10 YES YES YES 10 10 10 YES 10 YES 10 Requirements Confidential Proprietary Page 123 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to manually modify/delete, or 5.8.7.12 automatically update from a scanned document, stored passenger data, based on carrier specific rules The System must provide the ability to scan, capture or manually 5.8.7.13 record other mandated data, )e.g. address, place of birth), based on carrier specific rules 5.8.8 Baggage Reconcilliation System Tenderer must provide a centralized host based Baggage Reconcilliation System (BRS) connected with the Airport network for reconciliation of checked-in , transit baggages of passengers. This functionality can be provided by the tenderer as part of the Core PSS or as separate module The BRS system must provide the matching of all checked-in bags of a passenger for departing flights, ensuring that only bonafied baggage are loaded on an aircraft when the passenger is on board. The offered solution must comply with seven main functions: - Ensure loading of bonafide baggage of passaneger is loaded on a aircraft - Easy identification of unauthorized passenger baggage - Assignment of conatiner/bulk before baggage loading - Control of baggage loading before flight departure - Customizable baggage reports - Fast and efficient location of baggage in the aircraft in case of offloading - Tranfer/transit baggage reconciliation - Seamless baggage tracking When passengers are accepted in the airline Departure Control System (DCS), passenger boarding number, baggage count and baggage tag numbers will be updated automatically in BRS.. Before loading for each baggage item, respective baggage tag has to be scanned and after verification relevant sorting information such as “transfer”, “local” or “priority”, and the loading position should be recorded in the BRS YES 10 YES 10 5.8.8.1 YES 10 5.8.8.2 YES 10 5.8.8.3 YES 10 5.8.8.4 YES 10 Requirements Confidential Proprietary Page 124 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Before flight departure or any time upon request, passenger boarding and baggage data must be “reconciled”. The system must identify loaded baggage not authorized for transportation and provide its exact loading location for offloading. Also after matching, a report of missing baggage must be produced. Load reports 5.8.8.5 including reconciliation report must also be generated upon request and final loading information be available in the BRS. In case of the mismatched left out baggage, a message should be generated to the destination airport informing about the baggage misconnection and a message should be generated to the passenger's mobile number, if available. Depending on different user rights and user sign-ins, users must view different data according to their individual needs using the BRS workstations in the baggage make-up area and be able to carry out the following functions: - Register the ULD or CART to the BRS system by scanning the preprinted ULD / CART label / card - Scan bag tags before loading them into the container, providing a clear indication of the loading permission/status - Merge the contents of containers. - Close the container - Offloading bags as required. 5.8.8.6 - Registration of container (or just its contents) positions loaded onto an aircraft. - Loading an Expedite Bag - Processing a Duplicate Bag - Re-labeling a BAG - Re-flighting a BAG (with the option to re-print a new Baggage tag) - Generating of RUSH tags. - Displaying complete BRS statistics of a single flight or group of concurrent departing flights data like number of bags loaded, not loaded, to be offloaded etc. - Passenger and baggage enquiries and printing of reports - Printing of manifests and reconciliation status reports YES 10 YES 10 Requirements Confidential Proprietary Page 125 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must conform to ICAO Annex 17 providing a real-time interactive BRS which allows baggage handlers to make a bag load/no-load decision. - The BRS must handle 5.8.8.7 - locally checked bags - transfer baggage - gate baggage for both containerized and bulk loaded operations. - standby bags The BRS must be integrated with third party systems including the common use check-in system (SITA CUTE, ARINC MUSE,RESA CREWS,SITA CUPPS) 5.8.8.8 - IATA RP1745 message distribution (Bag Message) - IATA World Tracer - Flight information display system (FIDS – Auto Or Manual feed) The BRS system must - Track the movement of baggage from check-in to flight departure - Provide baggage handlers with real-time advice about whether or not a specific bag may be loaded (and if not, identifying the reason why) - Allocate containers and carts to specific flights, and recording details of bags as they are loaded into containers or holds 5.8.8.9 - Record the position of containers and loose baggage in the aircraft hold, thereby speeding up unloading and ensuring timely flight departure. - Determine which bags have been loaded, and produce flight reconciliation and flight manifest reports to highlight mismatches - Provide comprehensive tools for enquiry and management information YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 126 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC When Passengers Baggage items are accepted in the airline DCS, the check-in system must generate a Baggage Source Message 5.8.8.10 (BSM) with a mandatrory (.S) element as per IATA RP 1745 baggage reconciliation message. Therefore only BSM 1 and B messages must be used for this purpose. 5.8.8.11 The BRS shall handle and exchange the industry standard messaging complaint to IATA RP1745 baggage service messages. YES 10 YES 10 The BRS must be capable of receiving and processing - BSM (Baggage Source Message) 5.8.8.12 - BPM (Baggage Processed Message) - BUM (Baggage Unload Message) - BMM (Baggage Manifest Message) The BRS must be capable of generating and automatically transmitting 5.8.8.13 - BPM ( Baggage Processed Message ) - BNS ( Baggage Not Seen Message ) - BMM ( Baggage Manifest Message ) The system must store all relevant baggage data for a configurable period in a database. The following data must be captured per bag: - Baggage tag number - Flight number - Flight date - Inbound and onward flight number and date - Load authorization 5.8.8.14 - Destination - Load status - Load location i.e. container (ULD) and hold number - Loading position within the container and hold - Passenger information - Security information i.e. screening information or security number - Sorting criteria YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 127 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The BRS system must be capable of receiving and displaying the following data from FIDS System: - Flight number - Date 5.8.8.15 - Inbound/outbound - Gate - Scheduled time of departure/arrival - Expected time of departure/arrival and - Actual time of departure/arrival IATA World Tracer: The BRS system must have an interface with WorldTracer for 5.8.8.16 tracking passenger's mishandled babbage and shall transmit forward messages as appropriate during the handling of expedite baggage, including: FAH, FOH, FLZ, FWD etc. Reflighting: BRS must provide reflighting function to cater for the baggages which miss its flight and alternative arrangements are needed to 5.8.8.17 reunite the bag with its owner. Reflighting functionality is to automate choosing an alternative flight, issuing a new expedite tag, informing interested parties about the new routing. The BRS shall use real time flight data from FIDS from Airline Host when suggesting alternative onward carriage options for expedite 5.8.8.18 baggage, displaying gate number and departure time for the onward flight. Following the processing of expedite baggage, the BRS shall provide forward messaging to the WorldTracer system. The System must be capable of receiving and processing - BPM ( Baggage Processed Message ) 5.8.8.19 - BNS ( Baggage Not Seen Message ) - BMM ( Baggage Manifest Message ) The System must automatically generate and transmit e.g.: - Baggage transfer message (BTM) 5.8.8.20 - Baggage source message (BSM) - Baggage unload message (BUM) - Baggage change message (BCM) Requirements YES 10 YES 10 YES 10 YES 10 YES 10 YES 10 Confidential Proprietary Page 128 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.8.9 5.8.9.1 5.8.9.2 5.8.9.3 5.8.9.4 5.8.9.5 Collection of Misc. Fees & Customer Compensation At first customer touch point assess excess baggage, change fees, upgrade fees, service charges based on carrier specific rules, including inter airline journeys, restricting check-in until fee is paid or waived The System must provide the ability to collect change fees at time of check-in in both money or miles The System must provide the ability to waive miscellaneous fees and track override activities The System must provide the ability to collect form of payment for various fees at time of check-in but not actually bill until standby is accommodated The System must provide the ability to assess excess baggage fees based on baggage type and special sizes/weights YES 10 YES YES YES YES 10 10 10 10 The System must provide the ability to support different collection methods at any point e.g., but not limited to: - Cash - Credit cards - Debit cards - Smart cards 5.8.9.6 - Frequent flyer mileage or vouchers (electronic and paper) - Discount coupons - MCOs and/or travel certificates - Agency waivers Electronic compensation carrier owes customer (based on customer history (CRM), e.g. redemption of electronic inconvenience voucher) Automatic calculation of compensation, e.g. denied boarding compensation, including automatically inhibiting the issuance of 5.8.9.7 compensation when specific passenger or fare types do not allow compensation YES 10 NO 6 Requirements Confidential Proprietary Page 129 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to automatically issue customer 5.8.9.8 compensation, based on previous customer history information (CRM) The System must provide the ability to support customer incentives through: 5.8.9.9 - Publication to backend systems - Generating event driven action, e.g. free ticket voucher for a random SSD user The System must provide the ability to alert customer service representative or alternate touch point(s) to offer customer 5.8.9.10 compensation based on previous travel experience, and carrier specific rules The System must support different types of customer compensation , e.g. - Mileage 5.8.9.11 - Cash - MCO and/or travel certificates (paper and electronic) 5.8.9.12 5.8.10 The System must automatically handoff customer service history information (CRM) to reflect any compensation delivered Electronic Ticket Handling The System must provide the ability to support all passenger types, including: - Revenue & non-revenue - Special service (e.g. UM, STCR) - Goshows (open tickets) - Infants - Groups The System must support dynamic update of coupon status based on check-in status and boarded status The System must provide the ability to retrieve any coupon The System must provide the ability to manually adjust coupon status, based on carrier specific rules, (e.g. print, unprint (undo print), void) NO 6 NO 6 NO 6 NO 6 NO 6 5.8.10.1 YES 10 5.8.10.2 5.8.10.3 5.8.10.4 YES YES YES 10 10 10 Requirements Confidential Proprietary Page 130 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must automatically manage “ownership / control” of coupons among interline partners based on carrier specific rules The System must provide the ability for automatic association of 5.8.10.6 coupon to PNR The system must maintain association through IROP and involuntary changes including automatic stapling, splitting, and if 5.8.10.7 necessary, exchange to FIM, or issue a ground transportation voucher 5.8.10.5 Maintain association through voluntary changes, and automatically 5.8.10.8 calculate fare adjustments when required. If uncollected, inhibit check-in until payment is collected or waived The System must provide the ability to associate other electronic 5.8.10.9 documents to the electronic ticket (e.g. upgrade, change fee), and enable retrieval When ground handled, support dynamic access and update of 5.8.10.10 electronic ticket coupons by any other carrier or handler, based on multilateral agreements As a ground handler, provide the ability to dynamically access and 5.8.10.11 update electronic ticket coupons of any other carrier, based on multilateral agreements The System must provide the ability to support retrieval requests of 5.8.10.12 electronic ticket coupons for limited periods of time based on carrier specific rules The System must provide the ability to automatically generate ETL 5.8.10.13 to operating carrier at flight close-out 5.8.10.14 The System must provide the ability to automatically process incoming ETL from ground handlers to reconcile flight coupon usage YES YES 10 10 NO 8 NO 8 NO 8 YES 10 YES 10 YES YES YES 10 10 10 Allow interline through check-in of electronic ticket connecting 5.8.10.15 customers through to final destination, including mixture of paper and electronic ticket The System must provide the ability to send and receive electronic 5.8.10.16 data regarding collection of miscellaneous fees NO NO 10 6 Requirements Confidential Proprietary Page 131 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.8.10.17 5.8.10.18 5.8.10.19 5.8.10.20 5.8.10.21 The System must automatically identify most cost efficient way for re-ticketing of rerouted customers (e.g. push control of coupon rather than reissue ticket or FIM) and invoke appropriate subprocesses, e.g. automatically reissue ticket or FIM or accommodation vouchers. Ability to push an electronic FIM due to routing change (if push of coupon control is not possible) The System must support push or pull of coupon control to and from other carrier(s), for selected or all passengers based on carrier specific rules, - For a given date range - For any given flight(s) - For any given electronic ticket eligible station(s) The System must provide the ability to reset status of selected or all coupons if closed-out flight is re-opened The System must provide the ability to convert paper documents for miscellaneous fees to electronic records and associate to electronic tickets The System must provide the ability to issue all miscellaneous fees electronically and associate to electronic tickets, e.g. excess baggage YES 10 YES 10 YES NO 10 4 NO 4 Ticketless Handling The System must support processing of ticketless indicator and unique confirmation number based on reservations data, including 5.8.11.1 the ability to support airport customer services sub-processes without a paper or electronic flight coupon The System must provide the ability to issue a boarding authority 5.8.11.2 with a ticketless identifier The System must support all flight close-out activities for ticketless 5.8.11.3 customers, including automated reconciliation of checked-in to boarded ticketless customers, and close-out without a coupon lift 5.8.11 NO 8 NO 8 NO 8 Requirements Confidential Proprietary Page 132 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to generate, retrieve, and 5.8.11.4 transact from, and transmit ticketless customer information, and combinations of ticketless and other types of information The System must automatically identify most cost efficient way for re-ticketing of rerouted customers (e.g. push control of coupon rather than reissue ticket or FIM) and invoke appropriate sub5.8.11.5 processes, e.g. automatically reissue ticket or FIM or accommodation vouchers. Ability to push an electronic FIM due to routing change (if push of coupon control is not possible) For employee ticketless travel, support handoff to back end systems 5.8.11.6 to record flown segments and ensure appropriate employee billings, based on carrier specific rules Information Retrieval The System must provide automatic and dynamic update of all 5.8.12.1 passenger and baggage information The System must provide the ability to generate, retrieve and transact from, different information with views of passenger and baggage records based on carrier specific rules, e.g. - Departure management/ standby (need seats, revenue & nonrevenue standby, upgrades/downgrades, boarding priorities) - Information retrieval based on specified characteristics (inclusion, exclusion or combination of both, e.g. “All passengers WITH 5.8.12.2 baggage and NOT going to Miami”) Types of information retrievals include, but are not limited to: - All marketing flights associated to an operating flight - Passenger by marketing flight number or operating flight number - Baggage information - Misconnecting flights or misconnecting customers from a given flight 5.8.12 NO 8 YES 10 NO 8 YES 10 YES 10 Requirements Confidential Proprietary Page 133 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to retrieve and transmit single 5.8.12.3 passenger and baggage check-in data with all associated activities, according to user authorization The System must provide the ability to retrieve flight and passenger 5.8.12.4 summary information, (e.g. number of booked vs. checked-in customers, standby numbers, flight status) 5.8.12.5 The System must provide the ability to transact from or transmit any of the above information on demand or time initiated YES 10 YES 10 YES 10 Departure Management The System must provide the ability to generate dynamically updated standby lists including passenger and baggage information based on carrier specific prioritization policy, e.g.: - Customer status (tier level, disserviced, goshow) - Linking or splitting parties 5.8.13.1 - Booking class, fare basis, high/low yield - Destination - Non Revenue/Employee: Date of Employment - Time stamp - Customer value The System must provide the ability for time or event driven automated processing of standby lists based on carrier specific rules, with different options: - Automated onloading of the recommended standby list, including issuance of boarding authority 5.8.13.2 - Ability to manipulate seating proposals of onload recommendation list, including tracking of override usage (refer to requirements for performance metric tool) - Ability to manually override onload recommendation list for a limited set of users, including tracking of override usage (refer to requirements for performance metric tool) 5.8.13 YES 10 YES 10 Requirements Confidential Proprietary Page 134 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support the transfer from one flight to another of selected or all customers, with all relevant information , including 5.8.13.3 the ability to transfer the standby list from one flight to another, and immediate acceptance if capacity / limits allow, based on carrier specific rules Based on carrier specific rules, support standby on multiple flights (including multiple destinations), linking customer records across all flights; when a standby is accepted, automatically offload from the 5.8.13.4 confirmed flight, and send an alert to baggage handling; once customer is boarded automatically remove from any other standby flight(s) 5.8.13.5 The System must provide the ability to merge different standby lists with automated reprioritization, based on carrier specific rules YES 10 YES 10 NO 8 The System must provide the ability to invoke automated 5.8.13.6 communication of standby passenger status information (e.g. to PDA, customer information screens) The System must support boarding system / device in such a way that a new boarding authority is produced when reseated or 5.8.13.7 accepted customer boards, including all relevant information and miscellaneous undelivered message, (e.g. “call home for an important message”) The System must automatically process all types of upgrades and downgrades, based on carrier specific rules, including but not limited to: - Frequent flyer (mileage deduction) - Paid upgrade (electronic or paper) 5.8.13.8 - Involuntary upgrade or downgrade (e.g. oversale, mechanical) - Courtesy upgrade for commercial reason or customer recovery - Waitlist for paid class - Employee travel - Customer value After successful upgrade and change to passenger status 5.8.13.9 “boarded”, provide the ability to automatically update account (e.g. electronic upgrade bank or frequent flyer) Requirements NO 6 NO 6 YES 10 NO 8 Confidential Proprietary Page 135 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.8.13.10 The System must provide the ability to automatically process upgrades or downgrades on one or more legs of a multi-leg flight NO 8 The System must automatically and dynamically recommend 5.8.13.11 customers for class change when required for operational reasons, including logging for customer history. The System must provide the ability for automated compensation to 5.8.13.12 downgraded customers based on carrier specific rules, and update CRM system The System must provide the ability to capture information that passenger has boarded, utilizing traditional and evolving technologies e.g.: - Biometric boarding authority 5.8.13.13 - Radio frequency - Barcode scanning - Chip card - Magnetic encoding on boarding passes and other documents The System must provide the ability to combine ticket issuance & payment, check-in and boarding of passengers at point of boarding 5.8.13.14 control (e.g. pay as you board), where compliant with security and regulatory framework, and based on carrier specific rules The System must automatically inhibit boarding until all paper documents associated with this boarding authority have been collected, e.g.: 5.8.13.15 - Paper upgrade coupon - Paper ticket coupon (or FIM) - Excess baggage ticket The System must provide continuous reconciliation of boarding 5.8.13.16 process with passenger list, available seats and baggage information At defined times based on carrier specific rules, automatically 5.8.13.17 reconcile checked-in to boarded customers and generate message to board or offload baggage. Ability to manually reconcile if required. NO 8 NO 8 NO 8 NO 8 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 136 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.8.13.18 The System must automatically inhibit boarding to comply with security and regulatory requirements, based on carrier specific rules YES 10 Based on carrier specific rules, boarding of passenger will: - Automatically invoke billing of miscellaneous fees, (e.g. standby fee or upgrade charges) - Once customer is boarded automatically remove from any other 5.8.13.19 standby flight(s) - Automatically update baggage information and ensure baggage is cleared to board - Automatically mark electronic records of paper tickets as used The System must provide an Interface to provide all relevant information to the customer(s) in the airport environment via multiple channels based on carrier specific rules, e.g. - Automated time- and event-driven boarding announcements - Multimedia pre-recorded gate announcements - Self-service devices (self-service kiosks) - Gate information displays - Personal devices (e.g. personal digital assistants, mobile phones, laptops) Relevant information to communicate includes but is not limited to: - Seat change - Message to be delivered - Flight irregularities - Boarding sequence information (e.g. classes, zones, rows) based on carrier specific rules - Communicate passenger status versus boarding process state, (e.g. “we‟re about to offload your baggage”) YES 10 5.8.13.20 NO 8 Requirements Confidential Proprietary Page 137 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must automatically initiate time- and/or event-driven activities e.g.: - Restrict check-in activity to defined areas - Automatically release unclaimed seats e.g. pre-assigned seats that have not been claimed, and downline seats of no-show customers - Identify customers missing required data and prompt for collection (e.g. passport information) - Programmatic and dynamic update of bags that are cleared to 5.8.13.21 board - Prompt agent or initiate a sub-process to start boarding and to call bridge or bus driver - Automated update of gate information displays or prompt agent to update - Invoke hand-off to weight & balance system(s) if applicable, based on carrier specific rules - Interface with catering, (e.g. automatic placement of catering order) The System must provide the ability to add freeform text to a flight information to provide miscellaneous information The System must support intuitive flight close-out processes including: - Ability to automatically close-out flights at appropriate times based 5.8.13.23 on carrier specific rules - When automated flight close-out is not possible, generate alert to manually close-out flight The System must provide the ability to re-open closed-out flight(s) 5.8.13.24 for authorized users and/or at specific events, based on carrier specific rules The System must provide the ability to re-close flight(s) and automatically re-generate or suppress appropriate post departure 5.8.13.25 messages to reflect relevant changes, based on carrier specific rules 5.8.13.22 YES 10 YES 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 138 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must automatically reconcile checked-in to boarded 5.8.13.26 customers, and if counts do not match, alert and block flight from close-out; allow for ability to manually reconcile Automated alert if flight-close out is not executed within specified 5.8.13.27 timeframe based on carrier specific rules The System must provide the ability to automatically generate all necessary messages at flight close-out based on carrier specific rules, and according to IATA/ATA resolutions as applicable, e.g.: - BTM, PTM - Other baggage messages according to RP 1745 - PFS 5.8.13.28 - FTL - Electronic ticket messages for coupon status updates) - Government required data, (e.g. APIS, actual booking data, DOT) Requirement also includes the ability to manually generate messages as needed Once a flight has been reclosed, automatically re-generate or 5.8.13.29 suppress appropriate post departure messages, based on carrier specific rules YES YES 10 10 YES 10 YES 10 Requirements Confidential Proprietary Page 139 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability for automated and dynamic hand-off of relevant data to all carrier systems based on carrier specific rules, including but not limited to: - Revenue accounting (e.g. ticket and revenue data) - Frequent flyer programs (e.g. mileage accrual, redemption, actual class flown, actual class paid) - Marketing and revenue management systems (e.g. actual booking 5.8.13.30 class, Point of Sale, Goshow/Noshow, Denied boarding, electronic ticket usage, flight irregularities, self-service device usage) - CRM systems and data warehouse - Employee database (e.g. electronic ticket or ticketless usage, class flown, relevant fare information, entitlement) - Invoke hand-off to weight & balance system(s) if applicable, based on carrier specific rules The System must provide the ability to log activities and generate reports of all airport customer service, flight data and baggage activities, e.g.: - Measure employee performance and validate compliance, based on carrier specific rules(e.g. report on manual overrides of systems proposals (standby recommendation overrides, non-collection of 5.8.13.31 fees), statistics on number & type of transactions per employee) - Record compliance with government regulations, (e.g. APIS/NFLSL/AQQ/ e-borders/ APP/PTS/Canadian PPP/APIS India required data collection, security dialogue, document checks, DOT and other official bodies‟ requirements) YES 10 NO 10 IROPs Retain customer seat preference, location, seat characteristic 5.8.14.1 whenever possible and provide notification if unable to fulfill The System must automatically reseat customers based on carrier 5.8.14.2 specific rules, (e.g. value, tier level) 5.8.14 YES YES 10 10 Requirements Confidential Proprietary Page 140 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.8.14.3 5.8.14.4 5.8.14.5 5.8.14.6 5.8.14.7 5.8.14.8 5.8.14.9 5.8.14.10 5.8.14.11 5.8.14.12 5.8.14.13 5.8.14.14 5.8.14.15 Reassign alternate seat if seat preference is unavailable due to aircraft capacity/configuration The System must provide an interface with boarding system / device so that new boarding pass/authorization is printed when reseated customer attempts to board The System must provide automated identification of flights and customers affected by an IROP The System must provide automated Identification and rebooking of customers on alternate flights The System must automatically move (e.g. offload and recheck) customers and baggage from their original flight(s) to their new flight(s), including any onward segment(s), based on carrier specific priority rules The System must automatically move any special services to the new flight(s), e.g. wheelchairs; when service cannot be transferred to the new flight, The System must provide agent alert for procedural handling The System must automatically initiate sub-processes for handling of ticket, electronic coupon, FIM handling and issuance of any vouchers The System must provide automation to support management of hotel bookings, and issuance of vouchers The System must ensure that automated rebooking remains in compliance with any governmental requirements (e.g. EU rule for passenger protection onto full flights) Push customer notification via alternate channels (e.g. self-service devices, PDAs, pager, cell phones, to aircraft) Allow for manual overrides of customer protection, e.g. carrier chooses to allow for a sub-minimum connection The System must provide ability to differentiate rebooking by various criteria, (e.g. passenger value, number of alternate flights to destination according to carrier specific rules) When rebooking ensure catering is kept informed to enable correct meal ordering YES YES YES YES 10 10 10 10 YES 10 YES 10 YES NO YES NO YES NO YES 10 6 10 6 10 6 10 Requirements Confidential Proprietary Page 141 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must automatically update manifest (PIL) of protected 5.8.14.16 flight with information regarding ability or inability to carry forward special services from original flight The System must automatically provide compensation for customer inconvenience e.g. miles, future travel credit, and update the PNR 5.8.14.17 and CRM regarding services provided and compensation/vouchers issued The System must provide automated notification to flight catering of 5.8.14.18 flight delays/cancellations Keep baggage information linked to passenger record and updated 5.8.14.19 appropriately, automatically generating relevant messages to baggage handlers/systems The System must provide automated performance measurement tool to track cost of IROP per flight, agent, station, date, immediately 5.8.14.20 and dynamically; this includes tracking the cost of hotels, ground transportation and meals 5.8.15 5.8.15.1 Other Documents (FIMs, MPDs, MCOs, Meal Vouchers, etc.) The System must provide the ability to automate issuance of FIMs, EMDs, MPDs, MCOs, and vouchers, based on carrier specific rules YES 10 NO 8 YES YES 10 10 NO 4 YES 8 The System must have the capability to issue FIM when applicable or invoke appropriate sub-process, e.g.: 5.8.15.2 - Automatically push control or reissuing flight coupons - Inhibit issuance of FIM where not appropriate The System must provide the ability to support printing of emergency contact information based on PNR data, including 5.8.15.3 instructions on completing or updating the form as required, based on carrier specific rules (e.g. nationality) 5.8.16 Arrival Management NO 6 NO 4 Requirements Confidential Proprietary Page 142 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to automatically compile and generate arrival information, based on carrier specific rules, including but not limited to: - Special service, (e.g. Preferred Customer, wheelchair, cancelled flight(s) protection, vouchers) 5.8.16.1 - Communication to aircraft (including other modes of transportation), e.g. connection data, gates, missing baggage - Alert to gate agent of flight arrival - Interface for baggage retrieval information, (e.g. notification of baggage carousel, missing baggage) Ground Handling The System must provide optimal data synchronization between 5.8.17.1 ground handler and operating carrier systems The System must provide the ability to interface to other carriers 5.8.17.2 handling carriers on their own systems. Accept and process post departure messages including PTM, IDM, SOM, ETL 5.8.17.3 5.8.17.4 5.8.17.5 The System must provide the ability to support handling of multi-leg flights, The System must support full functionality for setting and updating flight characteristics based on operating carriers‟ requirements 5.8.17 NO 8 YES 10 YES 10 YES YES YES YES YES YES 10 10 10 10 10 10 The System must provide the ability to create ground handling flights with operating carrier‟s characteristics Allow for dynamic data synchronization between ground handler and 5.8.17.6 operating carrier, based on bilateral agreements Accept and process PNL / ADL ( dynamic/ time call) including 5.8.17.7 electronic ticket data 5.8.17.8 The System must automatically generate post departure messages, (e.g. PTM, IDM, SOM, ETL, based on bilateral agreements) The system must support advance release of available capacity 5.8.17.9 after taking into consideration the booked load, to the cargo division for cargo planning Requirements NO 8 Confidential Proprietary Page 143 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.9 5.9.1 5.9.1.1 5.9.1.2 5.9.1.3 5.9.1.4 5.9.1.5 5.9.1.6 5.9.1.7 5.9.1.8 5.9.1.9 Weight and Balance General Requirements The System must support communication with external systems using industry standard messages The System must support graphical aircraft loading capabilities The System must support multi-lingual The System must generates appropriate documents according to industry standards The System must differentiate different users like load control Supervisor / Agent etc and provide secure login feature The System must support IATA standard formats for load sheet and other load-planning related messages. The system must processes incoming LDM, LPM, and CPM messages from an upline non-mechanized station In case of a day change for transiting flights, the date should be out of the city and not from the originating city. The system must provide a customer-configurable table of passenger and baggage weights to be used for load planning purposes. The system must provide the carrier with the ability to choose the default baggage weight table source (load planning or check-in) for a flight. YES YES NO YES YES YES YES YES YES 10 10 8 10 10 10 10 10 10 5.9.1.10 YES 10 Calculation and Validation The System must automatically calculate and recalculates operation weights and executes validation functions as and when agent inputs, 5.9.2.1 or inputs from incoming messages are received from external system or departure control system The System must alert the agents for any out of balance conditions 5.9.2.2 and of any structural or capacity limitations. The System must automatically calculate industry standard 5.9.2.3 operating and limiting weights Requirements 5.9.2 YES 10 YES YES 10 10 Confidential Proprietary Page 144 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.9.2.4 The System must support the varying of the maximum weights on a flight-by-flight basis from the aircraft‟s certified maximum values. YES 10 The System must use estimated weights while the flight is open in 5.9.2.5 computing take-off, ramp, landing, and zero fuel weights for a flight. After flight closure, only actual weights are to be used. The System must validate that flights are within structural and 5.9.2.6 capacity limitations prior to flight close and Load Sheet Issue The System must provide calculation for industry standard structural 5.9.2.7 and capacity limitation weights The System must provide calculation for balancing information. The 5.9.2.8 balance information should be displayed in a graphical format, using different colors to depict different limits The System must be capable of capacity calculations/auto load 5.9.2.9 planning & distribution/Ideal Trim condition and generation of auto load sheet and NOTOC 5.9.2.10 The System must support trimming by class/cabin & seat row The System must be capable of incorporating the Dangerous Goods 5.9.2.11 conditions and generate suitable warnings in case of incorrect loading The System must support radio load sheet. The Radio Load sheet is used to provide the aircraft captain with a provisional load sheet 5.9.2.12 before the flight has been finalized. The final details are passed to the pilots by radio or directly to a printer onboard the cockpit prior to takeoff 5.9.3 5.9.3.1 5.9.3.2 5.9.3.3 5.9.3.4 Static Databases The System must provide display, update, add and deletion of static information. The System must restrict specific users to make static database modifications. The System must allow display, update, add, and deletion of station information for each station. The System must allow display, update, add, and deletion of airline information for each airline. YES YES YES YES 10 10 10 10 YES YES YES 10 10 10 YES 8 YES YES YES YES 10 10 10 10 Requirements Confidential Proprietary Page 145 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.9.3.5 5.9.3.6 The System must allow display, update, add, and deletion of fleet associated with a unique airline The System must allow display, update, add, and deletion of aircraft information for each aircraft associated with a unique fleet Flight Data The System must provide the facility to display, add, modify, and delete flight data. The System must accept booked, transit, checked passenger counts, passenger weights, bag weights/pieces from external sources, or from departure control system. The System must support acceptance of baggage, cargo, and mail data from external sources. The System must support manual modification of baggage data by the agent The System must support acceptance of fuel figures from agent input of density, total fuel on board, taxi fuel, burn-off fuel, landing fuel etc., The system must accept data relating to seats occupied by cargo (SOC). The System must accept any operational adjustment like changes in maximum take-off, ramp, landing, zero fuel weight, inclusion/exclusion of stored optional equipment etc., The System must support changes in aircraft registration when a particular registration is not available The System must support acceptance of NOTOC items Cargo, Mail, Baggage The System must provide functions to control placement and planning of payload items for both narrow and wide-bodied aircraft YES YES 10 10 5.9.4 5.9.4.1 5.9.4.2 5.9.4.3 5.9.4.4 5.9.4.5 5.9.4.6 5.9.4.7 5.9.4.8 5.9.4.9 5.9.5 5.9.5.1 YES YES YES YES YES YES YES YES YES 10 10 10 10 10 10 10 10 10 YES 10 The System must calculate and validate the control parameter as 5.9.5.2 and when any cargo, mail, baggage weight or placement data is added, modified, or deleted. Requirements YES 10 Confidential Proprietary Page 146 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must take the expected number of containers and 5.9.5.3 pallets by segment from the agent and select a deck version that best fits the mix of containers and pallets The System must provide a graphical display to display the valid 5.9.5.4 aircraft loading positions the vacant loading positions and a list of payload items yet to be loaded The System must provide a graphical presentation of balance 5.9.5.5 conditions The System must provide functions to assign/de-assign loading 5.9.5.6 positions for payload items The System must support to move/swap/drag/drop items from one 5.9.5.7 position to another onto the aircraft, within the aircraft, or off the aircraft The System must support non-graphical display as an alternate 5.9.5.8 method to load the aircraft. The System must provide automatic load distribution so that the following can be achieved: - Higher priority payload is considered first. For example, baggage may have a higher priority than cargo, and first-class baggage may have priority over economy baggage. 5.9.5.9 - Attempt to achieve the optimum center of gravity - Minimize door-side and internal blocking for multi-leg flights - Structural and capacity limitations are not exceeded - NOTOC item placement checking - Optimize offload/onload procedures The System must support automatic load distribution for both 5.9.5.10 containerized and non-containerized aircraft. The System must interface with the carrier schedule and departure control system on real time basis for flight number, flight date, flight itinerary, departure and arrival times, passenger configuration, 5.9.5.11 aircraft type or aircraft registration etc., Any change in the itinerary, aircraft type, aircraft registration, departure or arrival times, passenger configuration etc., should reflect in the load control immediately for update control parameters NO 10 YES YES YES YES YES 10 10 10 10 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 147 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.9.5.12 The System must archive flown flight data The System must provide the facility to lock and unlock a flight and 5.9.5.13 cancel a flight from the system 5.9.6 5.9.6.1 Flight Flow The System must provide a display of the status of various milestones in the life of a flight/leg. The milestones include (but not limited to): - Upline release - Aircraft registration - Transit passenger details - LDM/CPM from non-mechanized - Load Instruction generated - Fuel Sheet generated - Check-in linked - Passenger seating completed - Flight Status (Open, Closed, Released) - Check-in Status (Open, Closed, Released, Unavailable) - Load Sheet generated - Close out messages sent The System must provide a display and update of the flight status of the various mile stones The System must interface with the departure control system to communicate the current available check-in weight allowance The system must automatically sends close-out messages when the flight is either closed or released based on carrier specific rules YES YES 10 10 YES 10 5.9.6.2 YES 10 5.9.6.3 5.9.6.4 5.9.6.5 YES YES YES 10 10 10 The system support manual close-out messages at the agents 5.9.6.6 request when the flight is either closed or released based on carrier specific rules YES 10 Requirements Confidential Proprietary Page 148 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The Close-out Messages include (but not limited to): - CPM – Container Pallet Message - LDM – Load Message 5.9.6.7 - LPM – Load Planning Message - UCM – ULD Control Message - SLS – Statistical Load Summary 5.9.6.8 The System must support display and update of supplementary information that may be associated with each of these messages. YES 10 YES 10 The System must provide generation and printing of various load control documents like (not limited to): - Load Instruction Sheet 5.9.6.9 - Provisional Load Sheet - Final Load Sheet - Fuel Loading Instruction - NOTOC documents The system must provide the facility of sending load sheets via 5.9.6.10 ACARS (Aircraft Communication Addressing and Reporting System). The System must support the transfer payload from one flight to 5.9.6.11 another. 5.9.7 5.9.7.1 5.9.7.2 5.9.7.3 5.9.7.4 5.9.7.5 5.9.7.6 Informational Displays The system must provide a list of payload items that are marked as canceled and will not be carried on that flight. The System must provide a display of payload items that are to be offloaded at a downline station. The system must provide a list of flights that depart or arrive from a given city for a given airline and departure date. The System must shows the complete flight itinerary while providing a display containing the payload distribution The system must provide a display that contains the seats occupied in each row. The system must provide a display containing the city codes of all the airline‟s stations in the load control database. YES 10 YES YES 10 10 NO YES YES YES YES YES 10 10 10 10 10 10 Requirements Confidential Proprietary Page 149 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide a display of valid configurations for a 5.9.7.7 given fleet identifier, for a specific fleet, or for all fleets for a given airline YES 10 5.10 5.10.1 5.10.1.1 Flight Information & Flight Tracking System Flight Information and Flight Tracking system The system must have the provision to create flight information (FLIFO) to record conditions about specific flight/dates which need to be advised immediately to user/passenger. The system must support the following categories of flight information: a) Forecast Messages b) Decision Messages c) Flight or Airport no-op messages d) Flight progress message with timings for preliminary estimated time of departure, estimated time of departure, actual time of departure, air borne time, preliminary estimated time of arrival, estimated time of arrival, actual time of arrival. The system must have the capability to display flight information based on the following conditions: a) A specific display of Flight information requested for. b) Passengers are booked or waitlisted on a flight c) A PNR is retrieved d) when a specific schedule is displayed e) When passenger boarding information is requested in DCS f) SMS broadcast g) Web update The system must have the capability to update flight progress message via movement message originated by regional operational control /station office control The system must allow manual updating of flight progress status at various stages. YES 10 5.10.1.2 YES 10 5.10.1.3 YES 10 5.10.1.4 5.10.1.5 YES YES 10 10 Requirements Confidential Proprietary Page 150 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must allow viewing of flight progress status by the airline users The system must have the capability to receive flight tracking 5.10.1.7 requests through Mobile phones and respond the status as per flight information system against the requested flight The tenderer must integrate with the carriers IVRS facilities and 5.10.1.8 other application 5.10.1.6 YES NO YES 10 4 10 5.11 5.11.1 Message Switching General Requirements The System must be capable of Interline message handling through 5.11.1.1 SITA (AIRIMP, CARIMP and Administrative messages). The system must be capable of Online and Offline retrieval of messages. Online retrieval of messages should be available for at 5.11.1.2 least 5 days (Offline retrieval of messages would mean retrieval of messages from Offline storage devices e.g. tapes.) 5.11.1.3 The system must be capable of Historical retrieval of messages. 5.11.1.4 The system must handle incorrect messages. The system must process Group addressing („Group addressing' 5.11.1.5 refers to clubbing of a group of addresses under a single address for teletype messaging.) 5.11.1.6 The system must have Address stripping features. 5.11.1.7 The system must Support for 8 character addresses. The system must have the Facility for sending multi pages of 5.11.1.8 messages. The system must have a Provision for configuring airlines max of 3 5.11.1.9 characters. 5.11.1.10 The system must support Various reports like printer wise, all devices wise etc for checking up the messages in different queues. YES 10 YES 10 YES NO YES YES NO YES NO NO 10 6 10 10 10 10 10 10 Requirements Confidential Proprietary Page 151 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.11.1.11 5.11.1.12 5.11.1.13 5.11.1.14 5.11.1.15 5.11.1.16 5.11.1.17 5.11.1.18 5.11.1.19 The system must have an Aging mechanism support for old messages. (The 'ageing mechanism' refers to escalation of a message from a lower priority queue to a higher priority queue if it remains un-actioned for a pre-defined length of time.) (Aging mechanism is meant only for the moving of messages to a higher priority queue after a pre-assigned period.) The system must Support alternate printing of messages. The system must have a Message purge program. The system must have a Printer message handling support. The System must support Alpha Numeric SITA addresses for sending PNL / ADL's to 3rd Party Ground Handler DCS system and similarly receive PNL / ADL from an Alpha numeric SITA address into the Host airline system for Handled Airlines The System must support (Incoming / outgoing) PNL / ADL generation into multiple addresses The system must provide for exchange of administrative messages within the Airline administrative messages are not in AIRIMP/CARIMP format. The administrative messages are generally sent for official communication.) Online Retrieval of TTY messages based on Date/time, sequence no, terminal id (Message Repeat Facility) The TTY message retrieved shall contain terminal ID, agent information, date, time along with the message. NO 6 YES YES YES YES 10 10 10 10 YES 10 NO 8 NO NO 10 10 5.12 5.12.1 Global Alliances Requirement General Requirements The System must provide connectivity to Data Networks or any 5.12.1.1 other networks of Global alliances Redemption Availability & Sell The System must allow an agent at one alliance member carrier to 5.12.2.1 view redemption inventory on other member carriers' flights. 5.12.2 YES 10 YES 10 Requirements Confidential Proprietary Page 152 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must allows alliance member carrier employees to 5.12.2.2 check award availability, access award itineraries, book Alliance award travel FLIFO The System must support FLIFO Query Response allows alliance 5.12.3.1 member carriers to request and view up to date flight information in their native formats The System must support real-time query/response transmission 5.12.3.2 (FLQRSP) (type A messaging) for receipt and response to a Host-toHost (H2H) query/response transaction. The FLIFO response when requested by the operating Flight number should include the following: - Carrier code and flight number of the operating flight; - Scheduled, estimated and actual departure and arrival times, in 5.12.3.3 local times; - Flight routing (origin, destination and all intermediate stops); - Gate and terminal information, when available; - Delay codes when applicable The System must support dynamic update (publish/subscribe) to/from all alliance member carriers and initiation of sub-processes 5.12.3.4 based on subscription data, e.g. ability to update inbound/outbound connection information and re-accommodate customers The System must transmit and publish FLIFO data, via Type B 5.12.3.5 message protocol, to defined gateway when the FLIFO data is updated in the operational host system. The System must support the update of FLIFO data via ASM/MVT/DIV messages for the following “change events”: - Estimated Time of Departure (ETD) changes; 5.12.3.6 - Actual Departure Times updated Airborne (Off Field); - Estimated Arrival Time (ETA) changes; - Actual Arrival Time updates (On Blocks); - Routing Changes 5.12.3 YES 10 YES 10 YES 10 YES 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 153 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the facility to send FLIFO dynamic update 5.12.3.7 on real-time from carrier to carrier on a subscription basis (Subscribe) Bilateral message exchange The System must provide the ability to send, receive and process “selective PTM” to/from all alliance member carriers, e.g. separate 5.12.4.1 PTMs to each connecting carrier containing only their customer‟s information The System must provide the ability to send, receive and process 5.12.4.2 “selective BTM” to/from all alliance member carriers. (The BTM must be sent in accordance with IATA standards (IATA RP 1745). 5.12.5 5.12.5.1 5.12.5.2 Premium customer identification The System must provide the facility to identify Tier 1/Tier2 level type customer of the alliance member carriers in the PNR The System must provide the facility to update the SSR FQTV in the PNR after checking all frequent flyer numbers in the PNR against the alliance members premium customer database The System must support the verification of Tier Level against the central repository of the alliance member carrier and update the PNR as specified by the carrier specific rules The System must provide the facility to flag premium customers with tier level in the passenger name list and print the same on the boarding pass 5.12.4 YES 10 YES 10 YES 10 YES YES 10 10 5.12.5.3 YES 10 5.12.5.4 YES 10 Priority waitlist The System must provide the facility for priority waitlist at 5.12.6.1 reservation for Tier1/Tier2 level customers(Premium customers) The System must provide the facility of priority confirmation for 5.12.6.2 Tier1/Tier2 level customers (Premium customers) 5.12.7 Through check-in 5.12.6 YES YES 10 10 Requirements Confidential Proprietary Page 154 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support inter-airline through-check-In 5.12.7.1 (IATCI/EDIFACT) links to all alliance member carriers according to IATA / PADIS Standard Version 94:1. The System must provide the facility of issuing boarding cards at the 5.12.7.2 first point of departure The System must provide the ability to handle code share, translate 5.12.7.3 marketing flight details and support single operating flights with one single flight. The System must ensure through-check-in when marketing flight 5.12.7.4 numbers and city codes are used. The System must ensure through-check-in message sent 5.12.7.5 regardless of status on ticket. The system must ensure that flights are always for through-check-in 5.12.7.6 considering the time difference between the origin and the departure of the connecting flight(s). 5.12.8 5.12.8.1 Upgrade and Award The System must allow alliance member carrier FFP to use award redemption for upgrade on another alliance member carrier flight YES YES YES YES YES YES 10 10 10 10 10 10 YES 10 Document Check The System must support the ability to interface with XML/SOAP or 5.12.9.1 EDIFACT or any other industry standard protocol to external system to determine the validity of travel documents. The System must have the capability to provide passenger, itinerary 5.12.9.2 and document information via the interface The System must support data from machine readable documents 5.12.9.3 for validity checks 5.12.10 Codeshare The System must support freesale (i.e. real-time or dynamic) 5.12.10.1 codeshare functionality with all alliance member carriers The system must support all codeshare functionalities listed in the 5.12.10.2 codeshare section Requirements 5.12.9 YES YES NO 10 10 10 YES YES 10 10 Confidential Proprietary Page 155 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 5.11.11 Alliance Tools The System must provide tools to generate the sold ticket/coupon 5.12.11.1 data of alliance members in TCN 4.05 format or any other format which might change from time to time The System must provide tools to generate flown ticket/coupon data 5.12.11.2 of alliance members in IDEC B9 format or any other format which might change from time to time YES 8 YES 8 6 6.1 6.1.1 6.1.1.1 6.1.1.2 6.1.1.3 6.1.1.4 Technical Requirements IT Infrastructure Data Centre Infrastructure - Requirements The Applications to be hosted should be housed in data center(s) that have state-of-art infrastructure. The Data Center should be certified and /or audited by Uptime Institute or SunTone or any other reputed agency. Tenderer shall ensure redundancy for various sub-systems of data center infrastructure. Tenderer is required to provide details of System; physical, logical and network security deployed at the various data centers used for housing the airline‟s applications. Tenderer is required to provide detailed description of the various data center computing facilities used for hosting the various applications used for the airline. This should include information about current capacity in terms of processing power, memory utilization, disk utilization and transaction processing per second, the scalable capacity for the various above parameters for each of the systems to be used for providing the application services to the airline. YES NO YES NO 10 8 10 8 6.1.1.5 NO 8 Requirements Confidential Proprietary Page 156 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC tenderer must provide details regarding their data center facilities like Power Conditioning / Power back up / Climate Control / Rodent 6.1.1.6 Control, Fire Detection and Suppression / Protection from natural calamities / willful acts of human. 6.2 System Infrastructure - Requirements Core Passenger Services Applications The tenderer shall provide the offered solution for the following core PSS application modules using a Graphical User Interface (GUI) browser based front end Reservations Schedules Availability Inventory Fares Ticketing e-Ticketing Advanced Seat Reservation Check-in Weight and Balance Baggage Reconcilliation System Message Switching The tenderer shall provide the offered solution for the core PSS application modules developed using an Open Platform Architecture supporting Relational Database. The architecture should also support the latest available standards of IP based communication and messaging. Reservations Schedules Availability Inventory Fares Ticketing e-Ticketing NO 8 6.2.1 6.2.1.1 6.2.1.2 6.2.1.3 6.2.1.4 6.2.1.5 6.2.1.6 6.2.1.7 6.2.1.8 6.2.1.9 6.2.1.10 6.2.1.11 6.2.1.12 YES YES YES NO YES YES YES YES YES YES NO YES 8 8 8 10 8 8 8 8 8 8 10 8 6.2.2 6.2.2.1 6.2.2.2 6.2.2.3 6.2.2.4 6.2.2.5 6.2.2.6 6.2.2.7 YES YES YES NO YES YES YES 8 8 8 8 8 8 8 Requirements Confidential Proprietary Page 157 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.2.2.8 6.2.2.9 6.2.2.10 6.2.2.11 6.2.2.12 6.2.3 6.2.4 Advanced Seat Reservation Check-in Baggage Reconcilliation System Weight and Balance Message Switching Tenderer shall provide for a separate environment and access for Production, Testing and Training for the various core PSS applications. Tenderer shall provide for a separate Disaster Recovery (DR) environment for the various core PSS applications and Surround Modules on a different system. This system shall be setup as specified in the DR Requirements Criteria. Tenderer shall provide for a separate Production, Testing environment for the various surround applications such as FFP /Data Mart/IBE. This could be achieved through setting up of different instances of database on the same System. The Tenderer shall ensure that the data for the surround applications has proper back up and a copy is kept in a safe location away from the production site to ensure that the instances of CRM and data mart could be restored at a short notice. The Tenderer is required to provide detailed information about Server(s) and related peripherals hardware with Model name, benchmark ratings (if published) and OS details with version number at both Main Data Centre and Disaster Recovery Centre where offered applications are hosted. The system must have one synchronized time and date for all applications offered to the airline. The application shall have a date and time set to synchronize with Indian Standard Time (IST). The application shall have the day change done at 00:01 IST, followed by the Night File Maintenance (NFM) activity for the core PSS applications. YES YES NO YES YES YES 8 8 10 8 8 10 YES 10 6.2.5 YES 10 6.2.6 YES 8 6.2.7 NO 6 6.2.8 6.2.9 6.2.10 YES NO NO 10 10 10 Requirements Confidential Proprietary Page 158 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.2.11 Tenderer is required to provide detailed information about hardware, software, database and application design and also the detailed architecture and standards followed in offered solution. Tenderer is required to ensure scalability of the systems to meet the airline projected annual growth rate of 10 % of the passenger booked and boarded during the contract. The projected growth rate of the passenger booking and the passenger boarded would have to be agreed upon between tenderer and airline during the last quarter of each year for the ensuing calendar year. The Tenderer must provide the "name" and "make" and details of each and every Application Module with Version number as offered by the Tenderer including third party Application Modules as per specified format in APPENDIX VI. Interfaces from and to Core PSS Applications - Requirements The Tenderer‟s system used for various applications offered to the airline shall support these interfaces :Interfacing with Fare Quote and Pricing systems Interfacing with industry standard systems such as OAG, ATPCO and other airline systems for exchange of relevant information. Interfacing with external message switching systems for exchange of teletype (airline Type B) messages. The message switching interface shall preferably use BATAP MATIP Type B protocol. Interfacing with various GDS systems using various IATA EDIFACT message types over MATIP Type A protocol for enabling implementation of Direct Access / Direct Connect and e-ticketing. NO 8 6.2.12 YES 10 6.2.13 NO 8 6.2.14 NO 6 6.3 6.3.1 6.3.2 6.3.3 6.3.4 YES YES YES NO 10 8 10 6 6.3.5 YES 10 The tenderer's core PSS systems shall interface with the following SITA / ARINC hosted applications:6.3.6.1 Lost Document Checks 6.3.6.2 World Tracer System 6.3.6 Requirements YES YES 10 10 Page 159 of 253 Confidential Proprietary National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.3.6.3 TIMATIC The tenderer's core PSS systems must interface with Credit Card 6.3.7 Companies for Credit Card authorization The above applications interface shall preferably use underlying 6.3.8 MATIP protocol. E-Ticketing interface with Interline partner airline ET systems 6.3.9 existing at the time of cutover PNL / ADL message interface with various Ground Handlers' 6.3.10 Departure Control Systems E-Ticketing interface during check-in with Ticketing database 6.3.11 system & other ET database systems 6.3.12 Flight closeout messages generation and processing E-ticketing message interface with other Ground Handling Agency Systems used to check-in NACIL airline passengers. Other airline 6.3.13 passengers whose flight check-in is handled by NACIL using the hosted Passenger Services. E-ticketing message interface with the other airline ticketing system to handle check-in of e-ticket passengers of those airlines whose 6.3.14 check-in is handled by NACIL using the hosted PSS application of the tenderer. Passenger Services host application shall interface with the airline external Web server and Internet Booking Engine (IBE) for 6.3.15 implementation of web based Reservations, Check-in, Availability, PNR retrieval, PNR booking and e-ticketing. The interface from the Passenger Services Application Systems and host application to the airline web server and internet booking 6.3.16 engine for enabling web based applications shall be based on industry standard XML messaging interface. 6.3.17 Interfacing with external portal systems 6.3.18 Interfacing with airline‟s alliance partner application systems Enabling interfacing with NACIL network equipments and peripheral 6.3.19 devices such as hardcopy, ticket printers, boarding pass / baggage tag printers used by the airline on its network. 6.3.20 Interfacing with mobile devices using standard messaging services YES YES NO YES YES YES YES YES 10 10 6 10 10 10 10 10 YES 10 YES 10 NO YES YES YES YES 8 10 10 10 10 Requirements Confidential Proprietary Page 160 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.3.21 6.3.22 Interfacing with airport kiosk systems Interfacing with airline Interactive Voice Response Systems (IVRS) for exchange of flight schedule information Interface for Revenue Management system: - Vendor should have the interface program to upload reference, schedule, Inventory and post departure data from PSS reservation system to PROS Revenue Management system as per the PROS System Interface Document. - Vendor should have the interface to transfer data from Revenue Accounting system to PROS Revenue Management system as per the PROS System Interface Document. - Vendor should have the interface to upload recommendation from PROS Revenue Management System to PSS reservation system Interface for Revenue Accounting System: - Vendor should have the interface program to generate sale data (Ticket) in the standard TCN format to Revenue Accounting System. - Vendor should have the interface program to generate passenger flown data to Revenue Accounting System Interfacing with Frequent Flyer Program System chosen by the airline and used for accumulation, redemption of FFP mileage through standard interfaces Interfacing with the airline data warehousing systems through standard interfaces The core PSS system shall have standard messaging and data interface with the data mart application system being used by the airline either that offered by the tenderer or that of 3rd party vendor system. Interfacing with airline Executive Dashboard System through standard interfaces using File Transfer Protocol by providing required data files. Interfacing with airline FTP server(s) and other airline authorized FTP servers YES YES 10 10 6.3.23 YES 10 6.3.24 YES 10 6.3.25 6.3.26 YES NO 10 8 6.3.27 YES 10 6.3.28 6.3.29 NO YES 8 10 Requirements Confidential Proprietary Page 161 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.3.30 6.3.31 6.3.32 6.3.33 6.3.34 6.3.35 Interfacing with internal airline cargo system for exchange of flight schedule information using standard IATA messages and handling of other CARIMP messages,.and LDP system. Interfacing with bar code readers at airports. Interfacing with various 2D bar code readers. Interfacing with RFID devices. Interfacing with various devices used for smart card readers used for passenger services. Interfacing with internal airline MRO system for exchange of flight schedule information messages using standard IATA messages The tenderer shall provide interfacing for home grown/other applications by using defined APIs to access tenderer's hosted applications. This shall preferably be achieved by using industry standard messaging such as XML. The tenderer shall provide the detailed information on the various APIs that are available for use by external applications to access core PSS applications systems offered by the tenderer and the data therein. The system must have ability to interface with systems using standard XML/SOAP/EDIFACT protocols or other industry standard protocols as and where applicable. The system must support data read from machine readable documents. The system provide for above standard interface with proposed Hub Control System to be used by NACIL. Network Infrastructure - Requirements Tenderer has to provide dedicated network connectivity from host site to at-least two entry level Points of Presence (PoPs) of NACIL, one each at Mumbai and New Delhi in India, for end-user connectivity. Tenderer shall provide for additional PoPs in the future if required by NACIL. NO YES YES NO NO NO 8 10 8 8 8 8 6.3.36 YES 10 6.3.37 YES 8 6.3.38 6.3.39 6.3.40 6.4 YES YES YES 8 8 8 6.4.1 YES 10 6.4.2 YES 8 Requirements Confidential Proprietary Page 162 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.4.3 Initially the Point of Presence (Entry level points from the tenderer's system to the airline network point) (PoPs) shall be in India at the following locations. 1) DIT Network room, Air India Finance Building, Old Airport, Santa Cruz ( East) , Mumbai 400 029 2) Network Room, Computer Centre Bldg Indian Airlines Limited, IGI Airport Terminal - 1B, New Delhi 110 037 Tenderer shall ensure that the PoPs configured would be of resilient nature. Data would be shared between the PoPs in a parallel redundant fashion i.e. in case data is not made available through one PoP, the same is made available through the other PoP. The tenderer shall ensure that the PoPs are also inter-connected. Network diagram (Diagram 4) provides for information on the proposed network connectivity diagram between host and NACIL. Tenderer shall provide for adequate bandwidth for the dedicated data circuit between the host & each PoP; and between the PoPs to ensure that transaction mean response time at either PoP is not more than 1.5 seconds. Tenderer shall provide for the required data circuit between HOST & each PoP and between the PoPs. The tenderer shall be responsible for its installation, commissioning, maintenance and monitoring. Tenderer shall supply, install, configure, manage, maintain & monitor their own equipments with redundancy (including network equipments) provided for host connectivity at each of the PoP. Tenderer shall bear all expenses (one time & recurring) related to all dedicated data circuits, and related network equipments provided by the tenderer at each of the PoP. Tenderer shall provide detailed information about network equipment with make, model name, benchmark ratings (if published) with version number for both Production and DR data center where offered applications will be hosted. YES 10 6.4.4 YES 10 6.4.5 YES 10 6.4.6 YES 10 6.4.7 YES 10 6.4.8 YES 8 6.4.9 YES 10 Requirements Confidential Proprietary Page 163 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.4.10 6.4.11 6.4.12 Tenderer shall facilitate connection by NACIL to its subsidiaries and other airlines to which NACIL provides partial/complete PSS Host access. Tenderer shall facilitate Host to Host Connectivity to all GDSs with whom NACIL has a Participating Carrier Agreement (PCA) for Direct access, Direct Connect Sell, Dynamic Availability (Direct Connect Availability), E-ticketing, Interline ET using IATA interactive / noninteractive EDIFACT. Tenderer system shall ensure that the GDS connectivity is achieved using MATIP type A protocol over TCP/IP. Tenderer system shall ensure that Type B connectivity using preferably BATAP protocol (MATIP Type B) is made available for the airline core PSS applications for use as additional channel of communications, especially for teletype interface with other GDS systems and other partner airline systems, where ever it is required. The costs accruing due to, all Host to Host data communications and application access costs from the Tenderer‟s hosted system to other 3rd party systems ( such as GDSs, SITA, ARINC, OAG, ATPCO, other airline systems) required for providing core PSS application service, shall be borne by the tenderer. Tenderer shall provide Host to Host Connectivity to all other countries immigration authority systems such as US, UK Canada, Japan, India, China, Baharin, Kuwait etc. The cost accruing due to these connections and communication cost shall be borne by the tenderer. Tenderer shall facilitate Host access to travel agents and authorized end users connected through various GDSs with whom NACIL has a Participating Carrier Agreement (PCA). Tenderer shall allow and facilitate access to IP / Legacy CUTE users at Domestic / International CUTE workstations using appropriate Terminal Emulator (TE) to establish connectivity with various applications provided by the tenderer to the airline. TE will be provided by the tenderer. YES 8 YES 10 YES 8 6.4.13 YES 8 6.4.14 YES 10 6.4.15 YES 10 6.4.16 YES 10 6.4.17 YES 10 Requirements Confidential Proprietary Page 164 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.4.18 6.4.19 6.4.20 6.4.21 6.4.22 6.4.23 6.4.24 Tenderer shall allow and facilitate access to IP / Legacy MUSE users at Domestic / International MUSE workstations using appropriate Terminal Emulator (TE) to establish connectivity with various applications provided by the tenderer to the airline. TE will be provided by the tenderer. Tenderer shall allow and facilitate access to IP / Legacy RESA CREWS users at Domestic / International airport workstations using appropriate Terminal Emulator (TE) to establish connectivity with various applications provided by the tenderer to the airline. TE will be provided by the tenderer. Tenderer shall allow and facilitate access to any IP / Legacy CUTE systems provided by vendors other than SITA, ARINC and RESA CREWS for users at Domestic / International airport workstations using appropriate Terminal Emulator (TE) to establish connectivity with various applications provided by the tenderer to the airline. TE will be provided by the tenderer. Tenderer shall commit to allow and facilitate connectivity to other shared departure control systems being used at airports across the globe as and when required. Tenderer shall commit to provide Host access to any end user device at any location inside or outside India where connectivity to host is required in future (say hotels, GSAs / PSA‟s (who are not provided with any alternate connectivity), kiosks, fairs, conferences etc.) Tenderer shall allow and facilitate secure and adequate Web to Host connectivity for all internet user transactions currently and in future, including but not limited to NACIL website, partner websites like portals, payment gateways, auction sites. Tenderer shall allow and facilitate integration with any Mobile service provider‟s network using appropriate protocol for various information and booking services. Tenderer shall allow and facilitate integration with portable wireless equipment, which could facilitate check-in, web check-in and printing of boarding passes through Internet (for roving check-in agent). YES 10 YES 10 YES 10 YES 10 YES 10 YES 8 YES 8 6.4.25 YES 8 Requirements Confidential Proprietary Page 165 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The tenderer shall provide diagrams with complete details in respect of network connectivity schemas for the following:Connectivity between hosted Solution and the PoPs at Mumbai & 6.4.26.1 New Delhi, including network equipments at PoPs. Host Access by end user / Travel agents connected to GDS and 6.4.26.2 accessing hosted application. ATO / CTO, airport terminals, other equipments and also partner 6.4.26.3 airline system GHA systems connectivity to hosted application system. 6.4.26 6.4.27 The tenderer shall provide for appropriate tools required to measure response times of various business functions to ensure that they meet the requested response times at the various Point of Presence User Interface to Hosted Applications - Requirements The system shall support standard Microsoft Windows browser based Graphical User Interface for client access to all hosted applications offered by the tenderer to the airline. The tenderer's core PSS applications system shall be accessible from client's PCs on the airline IP based network, using suitable PC based emulation software if required. If it is essential to use emulation software on client PC for accessing tenderer‟s offered core PSS applications, then the tenderer shall supply, install, configure and maintain "Emulator Software", at all end user PC terminals across the airline network at no cost to the airline. It is clarified that 'end user' terminals would mean all end user terminals including terminals at ATO / CTO and office / service locations, Call Centre , Cargo , and at a very limited number of GSA's/ PSA's. Approximately 5600 such Terminals are configured in the current IC and AI environments. The terminal emulation software used for accessing the core PSS applications shall be installable on existing airline PCs on its IP network. The client user interface shall be purely browser based. YES YES YES 10 6 10 YES 10 6.5 6.5.1 NO 8 6.5.2 NO 8 6.5.3 YES 10 6.5.4 6.5.5 YES NO 8 8 Page 166 of 253 Requirements Confidential Proprietary National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.5.6 6.5.7 6.5.8 6.5.9 The application shall support latest version of the browser and also up-to two previous levels Application display should normally not require to use horizontal scroll bar. The tenderer ASP system shall provide command line interface for core PSS applications. The system shall also support a mouse-less environment for user terminal functions. The application shall support a confirmation of action taken when action such as Create / Update / Delete function is completed. This would have to be consistent across applications The application shall ask for verification of action when a Delete action is requested in any input across all applications. The GUI screens shall support minimum of 800 x 600 pixel resolution across all applications. Help Screens (Reference Information) - Requirements The tenderer system provides help screens for various business functions with the provision for search by keyword. Tenderer systems shall have a provision of Reference Information Screens to be populated by NACIL for the purpose of dissemination of information to the airline authorized personnel. The modification of the Reference Information Screens shall be permitted to authorized airline personnel only. The display of the reference information screens shall be based on roles and be user specified. Error Messages - Requirements Tenderer applications offered to the airline shall provide for error messages in clear simple terms that are understandable by relevant users of the system. NO NO NO NO 6 8 6 6 6.5.10 NO 6 6.5.11 6.5.12 6.6 6.6.1 NO NO 6 8 NO 8 6.6.2 NO 6 6.6.3 6.6.4 6.7 6.7.1 NO NO 6 6 NO 6 Requirements Confidential Proprietary Page 167 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.7.2 Tenderer application error messages should also provide information on the reason for the failure with possible corrective action to be taken to resolve the error. Alert Messages - Requirements Tenderer system shall provide alerts for large volumes of transaction, generated by specific user or logical connection to the application system. . The system shall provide the ability to control the various agencies creating unusually high volume activities. The system shall provide the ability to generate alert messages if threshold values are reached in various business areas The tenderer's system shall provide the facility of broadcast messages to various users or set of users of the system. Technical and User Documentation - Requirements The tenderer shall provide detailed write-up / technical information (architecture and technology) and system architecture diagrams of the server(s) hardware / system software / system and other related utilities deployed at the Production / Training / Test site. The tenderer shall provide the Complete Technical information along with architecture including details of database in respect of each application Software offered to the airline. The tenderer shall provide six (6) copies of comprehensive User/Technical manuals and training material in Hard copy formats in addition to corporate license for unlimited Soft copies. The tenderer required to provide all documentation in paper as well as electronic form. The tenderer system shall have a provision for online documentation available to the end-users. NO 6 6.8 6.8.1 6.8.2 6.8.3 6.8.4 6.9 NO NO NO NO 6 6 6 8 6.9.1 NO 8 6.9.2 NO 8 6.9.3 YES 6 6.9.4 6.9.5 YES NO 6 6 Requirements Confidential Proprietary Page 168 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 6.9.6 The tenderer must commit to provide in future also any changes to the documentation, new documentation that are relevant to the applications which are provided for the airline. This will ensure that the documentation provided to the airline is always current. Site Inspection - Requirements The tenderer shall arrange the demonstration of its technical infrastructure / data centre(s) facilities to the technical evaluation team for verification of tenderer‟s claims to these effects. Note:- A Checklist Template is provided as part of RFP in the APPENDIX V YES 8 6.10 6.10.1 YES 10 6.11 6.11.1 6.11.2 6.11.3 6.11.4 6.11.5 6.11.6 6.11.7 IT Infrastructure related Reports - Requirements Tenderer shall provide monthly reports containing the following information: Availability of previous month (per application) with comparative figures of earlier months. Outage Reports (even if there is no downtimes a NIL Down Time Report) would have to be provided. Help desk calls and their response times Trouble Ticket for Problem reporting with Problem resolution time. Transaction Volumes and Peak Time Transaction Volumes with the peak time information. Reports providing details of Type of Problems and their frequency. Tenderer shall provide reports and statistics of Transaction Summary made by user for accessing various applications which requires the tenderer to access other 3rd party systems. Tenderer shall provide reports and various statistics for transmission of characters for accessing various GDSs using Type A traffic message exchange. . YES YES YES YES YES YES YES 8 8 6 8 6 6 6 6.11.8 YES 6 Requirements Confidential Proprietary Page 169 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Tenderer shall provide reports and statistics in terms of transmission of characters for all TYPE B messages. Tenderer shall provide monthly reports on service levels must be 6.11.10 provided within ten working days in the following month. Tenderer shall provide for on-line access to problem reports, system 6.11.11 health status reports. The Tenderer shall provide software program / utility / tools for 6.11.12 creating management reports as per required format. 6.11.9 YES YES YES YES 6 8 8 8 7 Migration Requirements for Core PSS Applications The tenderer shall provide for two dedicated teams, one stationed at New Delhi for the IC system data migration and the other team stationed at Mumbai for the AI system data migration. The tenderer teams shall be available at both New Delhi and Mumbai locations during the entire period of migration and also for providing post migration support for a period of one year. The tenderer teams in consultation with airline teams shall finalize the various “Static data” elements such as aircraft types and configuration, flight number, booking classes, Online / Offline cities, City Pairs, country code, ATO / CTO, airports, partner airline information and agreement details, details of code share airlines, configuration of input terminal ids, teletype addresses, output devices such as printers and configuration of agent information, functional group ids. The tenderer teams in consultation with airline teams shall finalise “Dynamic data” such as PNR data, customer information, PNL / ADL, e-Ticket data that needs to be migrated by tenderer. The tenderer experts shall conduct training sessions for the airline team members on the offered applications to enable speedier realization of the benefits of the functionality. 7.1 YES 10 7.2 YES 10 7.3 YES 10 7.4 YES 10 7.5 YES 10 Requirements Confidential Proprietary Page 170 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 7.6 The tenderer would assist the airline in identifying the gaps in the functionality available in the tenderer system compared to the functionality specified in the RFP. Accomplishment of Migration: NOTE: Requirement at Serial Number 7 can be met by compliance to 7.7A points (a thru l) or met by compliance as mentioned in point 7.7B. It may be noted that there is no difference in maximum marks that are allotted or that can be obtained under 7.7A or 7.7B. YES 10 7.7A The tenderer will provide a complete document on accomplishment of core PSS Data migration from existing IC PSS and AI PSS Systems on to Tenderers Host System mentioning therein compliance to following points a thru l. The tenderer must provide the utilities, procedures for ETL and execute them for data migration. a. The tenderer shall carry out activities related to Extraction, Transformation and Loading (ETL) of data onto the destination tenderer test system setup for AI from AI‟s current production system. b. The tenderer shall ensure establishment of the requisite interfaces required for the airline core PSS functionalities for the AI environment. c. The tenderer shall coordinate User Acceptance Test (UAT) on the functionality / interface and data quality of the AI data migration. d. The tenderer shall carry out activities related to Extraction, Transformation and Loading (ETL) of data onto the destination tenderer test system setup for IC from IC‟s current production system. A separate test environment for IC shall be created. e. The tenderer shall ensure establishment of the requisite interfaces required for the airline core PSS functionalities for the IC environment. YES 10 YES 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 171 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC f. The tenderer shall coordinate User Acceptance Test (UAT) on the functionality / interface and data quality of the IC data migration. g. The tenderer would assist the airline in identifying the gaps in the functionality available in the tenderer test environment compared to functionality specified in the RFP. h. The tenderer shall amalgamate the IC data from the tenderer‟s IC test environment and the AI data from the tenderer‟s AI test environment onto a separate unified test environment. i. The tenderer shall assist the airline in the testing of data integrity of the combined airline environment to ensure no loss of data due to the creation of the unified environment, and also check and remove any duplication of data. j. The tenderer shall coordinate User Acceptance Test on the functionality / Interface and the data quality of the unified airline environment. k. The tenderer shall perform required iterations of the steps involving ETL, UAT and amalgamation of environment and UAT of unified airline environment till such time that there are no errors. Note:- During each iteration exercise, it would be required to have the Control Totals of Data Items Extracted, Transferred, Loaded and Listed. This report should be for each application involving data exchange and be available from the destination environment(s) to be checked against the source system Control Totals l. The tenderer shall obtain appropriate User sign-offs of all the UATs, relevant for the changes done, on the individual airline environments created and also on the unified airline environment as and when any changes is done on the environment. YES 10 YES 10 YES 10 YES 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 172 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 7.7B In Case the Tenderers solution for Migration differs in toto or in part with respect to points mentioned above at 7.7A (point a thru point l ), then the offered methodology must be clearly detailed in a document by keeping the above points as reference to the extent possible for appreciation of NACIL technical evaluation team.The tenderer must provide the utilities, procedures for ETL and execute them for data migration. Please see Note specified in point 7.7A. The tenderer experts shall conduct “Train the Trainer” sessions for the airline team members on the offered applications to enable speedier realization of the benefits of the functionality of the offered applications. The airline IT personnel would also be required to be trained in the various functionalities to ensure better IT delivery at the end user level. The tenderer shall provide all those functionalities also which had been identified during Gap Analysis, between the functionality requested and that provided by the tenderer. This shall be made available initially on the tenderer‟s unified test environment and subsequently would have to be carried over to the production system of the tenderer. The changes to the standard product should be such that the customization should be kept to minimum. The tenderer shall use to the extent possible a parameter driven process with possible “user exits” in the software program logic with minimum code modifications so that changes are manageable. This shall ensure future upgrades are possible with maximum ease. The tenderer shall design, develop the code and test the changes to the various applications due to the customization, before making it available on production systems. 7.8 YES 10 7.9 YES 10 7.10 YES 10 7.11 YES 10 7.12 YES 10 Requirements Confidential Proprietary Page 173 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 7.13 The tenderer shall obtain appropriate User sign-offs of all the UATs, relevant for the changes done on the unified airline environment as and when any changes is done on the environment. The tenderer shall conduct “train the trainer” final round of training for the airline personnel on the unified airline environment, customized for NACIL specific requirements before commissioning of the hosted service. The tenderer shall provide for appropriate tools required to measure response times of various business functions to ensure that they meet the requested response times at the various Point of Presence The tenderer shall conduct at least two dry runs during ETL and amalgamation of data sets of the airlines, to ensure error free data. Describe in detail the “rollout” process for core PSS ( mentioning concerns also if any ) that would be adopted for the following :- Distribution Channel wise - Application wise - Station wise - Flight wise - Airport wise or GHA wise - All applications at one go Note:- Provide details as an attachment The tenderer shall also provide for time estimates for migration of data, applications and the interfaces required for the above migration processes and for the “rollout” processes. This should also include the expected blackout period when the application would be unavailable. The tenderer shall provide for a detailed fallback mechanism that would be adopted, in case the migration is not successful or exceeds agreed time limits of blackout. YES 10 7.14 YES 10 7.15 YES 10 7.16 YES 10 7.17 YES 8 7.18 YES 8 7.19 YES 8 Requirements Confidential Proprietary Page 174 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 7.20 7.21 7.22 7.23 The tenderer shall provide for post migration tenderer support structure with details of expertise of tenderer personnel both at user key locations and also at application hosted location to meet airline requirements. The tenderer shall provide for details of implementing surround applications for which the specifications is provided. The tenderer shall also provide for time estimates and the process to be adopted by the tenderer for implementation of the surround applications. The tenderer shall provide for post migration tenderer support structure with details of tenderer personnel both at user key locations and also at application hosted location to meet airline requirements. YES 8 NO NO 10 6 NO 6 8.1 Internet Booking Engine ( IBE ) 8.1.1 General Requirements 8.1.1.1 The IBE solution should be on a turn-key basis The online booking process should start from the home page of the 8.1.1.2 airline website The Tenderer will integrate the IBE with NACIL website. It may be 8.1.1.3 noted that NACIL website is hosted on a server in India which is a Government of India requirement. The Passenger Details Page, the Payment page and the 8.1.1.4 confirmation page should be on a secure site. FAQs/Trip Summary should be displayed on every page, pertaining 8.1.1.5 to the relevant details on that page. The IBE must come with a web based application that provides a 8.1.1.6 comprehensive list of travel related content and applications in multiple languages. The IBE must support country specific languages such as English, 8.1.1.7 Hindi, French, German, Spanish, Japanese, Chinese as specified by the airline. YES YES YES YES YES YES 10 10 10 10 10 10 YES 10 Requirements Confidential Proprietary Page 175 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Routine maintenance, modifications, enhancements and update activities will have to be scheduled in advance and will be carried out 8.1.1.8 / implemented during holidays / lean periods. Logistics for emergency troubleshooting, updates, enhancements and modifications should be detailed out by the vendor in their response. The IBE must be designed and developed to be compatible to all 8.1.1.9 widely used leading browsers in the market such as Internet Explorer, Netscape, Mozilla, Firefox. The pages, which need to be secured, should be identified in 8.1.1.10 consultation with the designated AI team and these pages must be accessible through secured http. Features like online booking, reconfirmation or e-check-in should 8.1.1.11 have a demo section on the website where the user can familiarize himself with the procedure. Day-to-day changes in content and features will be done by the 8.1.1.12 vendor. All ongoing content updates and feature enhancements will have to 8.1.1.13 be carried out within a time frame as advised by the airline depending on the priority and nature of work. All industry upgrades (both Functionality & Technology) related to 8.1.1.14 IBE and the Fares Database should be provided on no-charge basis. Post installation updates, enhancements, maintenance, monitoring, 8.1.1.15 administration and trouble shooting of the IBE are required on 24 x 7 basis with on-site support for a period of 10 years. 8.1.1.16 The IBE Shall support WAP enablement for booking and viewing YES 10 YES 10 YES 10 YES YES YES 10 10 10 YES 10 YES NO 10 10 Requirements Confidential Proprietary Page 176 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Context Links to be provided : - Weather (with 5 day forecast) for the cities within the itinerary - Aircraft information - Currency Conversion Table 8.1.1.17 - Event Guides month-wise - Airport Guides - Dialing Codes - Subway Maps Content links to be provided : - Destination Guides with city maps - Event Guides 8.1.1.18 - World Clock - Airport Links - Metric Conversion Tool The IBE shall provide for a link for extensive search facility through 8.1.1.19 popular search engine/s If there is a time-lapse of several seconds while awaiting the information on the next page, there should be a notation which should appear immediately e.g.” Please wait... processing booking”. There should also be a provision to display promotional matter/ images during the above time-lapse along with the above notation. 8.1.1.21 The airline should have a user interface for updating the above notation/ promotional matter including images YES 10 YES 10 NO 6 8.1.1.20 YES 10 YES 10 Requirements Confidential Proprietary Page 177 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.1.1.22 8.1.1.23 8.1.1.24 8.1.1.25 The IBE must be in a position to target different fares to different channels. A breakdown of the separate set up fee per channel to be provided, if applicable. The airline may undertake to do this in a phased manner. - Passengers - Corporate Clients-log in should be through individual office ids, to a fully dedicated user friendly corporate website, with payment made through corporate travel card. - Consolidators-log in should be through individual office ids - FFP Member The entire booking process should follow a logical path (industry standard) with clear cut demarcation of steps on top of the pageTrip Planning, Confirm Flight and Fare, Passenger details, Payment, Confirmation. The IBE should interface with the IATA Web Link for internet sales by travel agents as and when decided by the airline at no additional cost The system must send news letters through e-mails regarding promotional schemes etc as and when specified by the airlines to the user database. YES 10 YES 10 YES 10 YES 8 Booking Process – Air The web-booking engine must support up to nine passengers in the 8.1.2.1 same booking. 8.1.2 8.1.2.2 It should also support different passenger types based on fare basis such as adult, child, infant, student, senior citizen, companion YES YES 10 10 It should support different journey types like one way, return, stop 8.1.2.3 over, open jaw, multi segment, (up to 6 city pairs with 4 unique cities) mixed class and multiple carriers (interline and code share). 8.1.2.4 Itinerary selection should also have the option for multiple destinations, stopovers and return to a different airport YES 10 YES 10 Requirements Confidential Proprietary Page 178 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC There should be an option to select the itinerary for a specific date or flexible dates (+ or – 3days) 8.1.2.5 This option shall allow users to view a Fares Calendar (grid) that shows the lowest applicable fares with real time flight availability within a date range +/- 3 days for a return flight, or +/- 7 days for a one-way flight. There should be links to city maps, city info, and weather for origin, 8.1.2.6 destination, transit and stopover points. In addition, the IBE shall provide the options for users to search for 8.1.2.7 flights “By Schedule” or “By Fares”, as described below: a) Search by Schedule or Schedule-Driven Booking : - Based on the city pair and travel dates entered by the users, this option shall display a screen that allows users to select their itineraries for a list of outbound and inbound flights (with real time 8.1.2.8 availability). - On selection of the itinerary, the applicable Fare and Taxes for the selected itineraries will be shown on the same page in a pop-up screen b) Search by Fares / Fares-Driven Booking : - There should be a provision to opt for lowest fares or all fares. - Option should be provided to display lowest fares in different 8.1.2.9 categories like non-refundable / refundable. - Based on the city pair and travel dates entered by the users, this option shall display a screen that combines both Fares and - Available flights into one single screen for selection by the users. 8.1.2.10 Flight specific fares should be displayed in an ascending order The system must be capable of identifying, calculating and applying 8.1.2.11 discounts against particular payment modes like Co-branded credit cards, cash cards etc where airline has specified discount offers. 8.1.2.12 The system must have the facility to accept payment through EMI in cases specified by the airline. YES 10 YES YES 8 10 YES 10 YES 10 YES YES 10 10 YES 10 Requirements Confidential Proprietary Page 179 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC IBE must be able to support interlining and code share. The 8.1.2.13 technology and the solution should be made available. Both e-tickets & paper tickets should be supported. Confirm Flight and Fare For interline connections, the software should check for minimum 8.1.3.1 connection time to prevent unrealistic connections. The flight & seat availability based on the above criteria is displayed 8.1.3.2 for the applicable classes of service only for flights, which are open for sale thru the web e.g. economy, executive, first. The availability display should include information fields like flight number, departure and arrival times, elapsed flight time, a/c type, 8.1.3.3 terminal information, stopovers, fare for the lowest available fare class and baggage information. The IBE must be able to advise passenger as per sector requested, 8.1.3.4 the number of Frequent Flyer miles for his journey. The IBE shall be able to display Fares and Rules and calculate the 8.1.3.5 applicable Taxes from published fares database (i.e. ATPCO and SITA) for sales on the Air India website. Additionally, the IBE shall provide a Private Fares Database, taking into consideration factors like type of journey, type of passenger, class of service, taxes, duration of stay, seasonality, days of week and times of day etc. Mixed class within one segment should be 8.1.3.6 priced e.g. BLR BOM (G class) and BOM LON (M class) for one leg of journey. The vendor should carry out the entire activity of loading and maintaining private fares and taxes and/or Internet-only fares. These Private Fares and the applicable Taxes shall be retrievable on a real time basis by the IBE for sales on the Air India website. There should be a provision to select a combination of private & published fare based on Point of Sale There should be a provision to offer country specific fares and 8.1.3.8 discounts based on POS (Point of Sale) in local currency, when a viewed from a particular country 8.1.3.7 Requirements 8.1.3 YES 10 YES 10 YES 10 YES 10 YES YES 8 10 YES 10 YES YES 10 10 Confidential Proprietary Page 180 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Air India shall have the flexibility to decide the type of fares to be displayed for sales on the Air India website (e.g. published fares only, private fares only, or the lower of published and private fares). 8.1.3.9 There should be an immediate distribution of these fares and rules to the selected channels. The rules should be displayed in a simple, condensed text based on IBE systems parameters 8.1.3.10 The IBE must support agency ticketing There should be a provision to take the conversion rates from a 8.1.3.11 specified site. A currency converter should display fare charges in the currency of 8.1.3.12 the passenger‟s choice. Passenger Details There should be a provision to allow customers to complete the 8.1.4.1 ticketing with or without log-in at airlines discretion. The log-in page should appear after the customer has chosen the 8.1.4.2 itinerary and fares. 8.1.4.3 8.1.4.4 8.1.4.5 8.1.4.6 8.1.4.7 The IBE must pickup the relevant passenger details from the database after login and incorporate in the passenger detail boxes. Relevant details may also be picked up from the FFP record if the FFP No. is given on the 1st page. The subsequent pages may address the passenger with his/her name in case a FFP no. is mentioned. Automated e-mail should be generated after registration proving all details. The no./ type of fields for registration should be flexible and left to the airlines discretion. Also there should be facility for “forget password”. There should be a provision to request for Special Services like wheelchair, ambu-lift etc with a provision to collect payment if applicable. 8.1.4 YES 10 YES YES YES 10 10 10 YES YES YES YES NO YES YES 10 10 10 10 8 10 10 8.1.4.8 YES 10 Requirements Confidential Proprietary Page 181 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC If there is more than 1 passenger, the name, gender, Frequent Flyer no, meal request and additional service request like bassinet or 8.1.4.9 wheelchair of the accompanying passengers should be asked for on the same page. For First and Business class passengers, an option of requesting for 8.1.4.10 Limo Service should be made available (as per airline requirements) with an SSR For all passengers an option to Select Seats should be made 8.1.4.11 available. On clicking on this link, an interactive seat map should reflect. 8.1.4.12 The passengers should be able to proceed to the payment stage only after he has read and accepted the Terms and Conditions. Payment YES 10 NO 8 YES 10 YES 10 8.1.5 There should be seamless integration by the vendors with the payment gateway where the credit card details are taken on the 8.1.5.1 airline website and the passenger is not redirected to the payment gateway site. Payment may be collected in different currencies. 8.1.5.2 Application should support payment though a Visa, MasterCard, Amex , JCB, diners and other credit card being accepted in India and abroad. The site should be integrated to various banks (selected by Air India) providing Internet Banking facility for payment through direct debit The system must support payment through through prepaid cash cards available in India and abroad There should be a provision for cash on delivery module where the PNR is booked without collecting payment and is cancelled if the payment is not received. A complete tracking system must be provided with an interface to the COD vendor to receive and send status. YES 10 YES 10 8.1.5.3 8.1.5.4 YES NO 10 8 8.1.5.5 YES 10 Requirements Confidential Proprietary Page 182 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The vendor may be required to integrate with other payment options and currencies as and when required by the airline in future at no 8.1.5.6 additional cost. The IBE must be able to support multiple payment gateways. The software will integrate with Air India‟s existing Payment Gateway Providers (PGP) & banks (for Internet Banking). The mode of payment when a travel agent books through the IBE can be any of the 3 methods listed below, which will be decided by 8.1.5.7 the airline. This would require maintaining the profile and transaction & payment record of each agent. Provision to accept payment thru Agents Credit Card for those 8.1.5.8 agencies that have been given a login id by the airline. Provision to calculate and display the agent‟s commission/handling fee. Agent must also have a facility of Advance payment with the designated bank. The module must handle the amount deposited and the threshold amount to with hold. The airline would update the data id with the credit amount. Once, this is in place the agent can book online. When the amount gets depleted to a minimum, the 8.1.5.9 agent will have to top up the balance. The agent should be able to view the balance amount. There should be a provision to offer concessions or flat amounts to agents. Provision for two stage authorization for further transaction based on payment records should be made available. For foreign currency payment gateway, a provision for two stage authorization should be made for the agents to make fortnightly 8.1.5.10 payments. The module should permit further booking only after the settlement of the previous fortnight accounts. There should be a mechanism to switch between the payments 8.1.5.11 gateways automatically in order to provide uninterrupted service if a particular PG is down. 8.1.6 Booking Confirmation YES 10 YES 10 YES 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 183 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC On receiving of successful authorization code from the PG. the IBE will create a confirmed PNR and display a complete summary of the 8.1.6.1 booking along with a secure E-Ticket link on a printable page and send booking confirmation e-mails & SMS to the passenger. (as specified by the airline) In case of E-Tickets, an email with the E-Ticket link will be 8.1.6.2 forwarded to the passenger. A single Itinerary Receipt should be generated for the entire PNR as per the desired format of airline. In case of paper tickets a notation should appear regarding ticket 8.1.6.3 delivery within the stipulated no. of working days. Schedule Change The IBE database should be updated to reflect the change in 8.1.7.1 schedule based on changes in the host PNR. There should be a provision to inform passengers vide email /SMS 8.1.7.2 when there is a rescheduling or cancellation of flight along with the option of advising the alternate flight details. Online Rebooking The IBE must have provision for online rebooking and have the 8.1.8.1 facility to adjust the balance either by refunding or accepting the difference. 8.1.9 8.1.9.1 8.1.9.2 8.1.9.3 8.1.9.4 8.1.10 Online cancellation/Refund The IBE must have provision to cancel and auto-refund booking online, after checking the applicable refund rules/penalties. The IBE must have auto-refund facility in case the booking fails after payment is realized successfully. The system must allow manual refunds in cases where specified by the airlines. Online Cancellation/ Refund alerts should be sent to the customer via email, SMS etc Reports 8.1.8 8.1.7 YES 10 YES YES 10 10 YES YES 10 10 YES 10 YES YES YES YES 10 10 10 10 Requirements Confidential Proprietary Page 184 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC All booking details will be stored in the database. The software should provide site activity reports such as: - No. of PNRs created, - No. of hits, - No of visitors, - No of page views, - Fare and break-up of taxes, daily/monthly sector-wise, class wise booking report. - Detailed MIS and Reconciliation reports and refund reports and formats of the required reports may be provided after vendor 8.1.10.1 selection. - Day/Month wise sales / cancellation / refund / duplicate booking/ No - show reports should be provided. - Response time monitoring tool - User log-in report - E-check-in reports - Payment gateway wise reports - Ability to create other customized reports as and when required. - Ability to export the reports in MS office format. - Dashboard facility providing customizable graphical display of critical statistics All required data of passengers email ids/telephone etc should be stored and made available as required. The travel agents should be able to view their reports and corporate should be able to view their reports for bookings generated thru 8.1.10.3 them including separate reports for bookings made thru deposits and credit cards. 8.1.10.2 8.1.11 Non-Air YES 10 YES 10 YES 10 The vendor should have arrangements/tie-ups for hotels, car rentals, travel insurance, rail, cruises, etc. which must be made 8.1.11.1 available for passengers booking through Air India website on a real time basis and all such bookings must be in one single PNR. NO 6 Requirements Confidential Proprietary Page 185 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Hotel-The IBE must be linked to online real time booking for hotel with published (rack-rate) and negotiated rates. The IBE must 8.1.11.2 provide a commission collection service so that the airline does not need to follow up for commission from the hotel providers. Car- The IBE must be linked to support online real time car booking. For car booking, the IBE must have a direct link to the Car providers 8.1.11.3 for accessing the latest car inventory and car rental rate (including published and negotiated rates) The IBE must support the display of car images provided by the car rental companies. Cruise-The IBE must be linked to support real time cruise bookings 8.1.11.4 and provide the content for several world cruise liners, including Star cruises. Rail –The IBE must linked to real time rail bookings and should provide an interface for easy linking with online booking engines 8.1.11.5 such as Indian Railways. There should also be provision for links with other rail services such as Eurail, Amtrak etc. 8.1.11.6 Travel Insurance - linked to online real time travel insurance. Tour Packages - linked to online real time booking for tour 8.1.11.7 packages. E-Check-in E-Check-In will be done between x to y hrs before the time of departure. The passenger enters booking reference number or the PNR and other details for verification, the software checks his 8.1.12.1 booking, displays the seat map (based on different criteria) for him to choose his seat(s) and completes check-in. This facility should also be capable of printing of bar coded boarding cards 8.1.12.2 Check-in through SMS to be introduced On the above lines. Booking Status The passenger enters booking reference number or the PNR and 8.1.13.1 the software shows the current status of his/her booking. Requirements 8.1.13 8.1.12 YES 10 YES 10 YES 10 YES YES YES 10 10 10 YES 10 YES 10 YES 10 Confidential Proprietary Page 186 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must have an interactive Online complaint and 8.1.13.3 feedback management module for Customer to log complaints and generate responses from a centralised NACIL locations Booking Reconfirmation The passenger enters booking reference number or the PNR and 8.1.14.1 the software re-confirms his/her booking after establishing his/her identity. Option for including seat/meal request and contact numbers should 8.1.14.2 be made available on real time database. Flight Information The user enters the flight number and date of travel and the software shows the last updated status of that flight. It should also 8.1.15.1 have other relevant information like terminals, etc. This data needs to be updated from DCS on real time basis. Arrival/Departure Information The user enters the city and date for which he/she wants 8.1.16.1 arrival/departure information and the software retrieves the relevant information and shows it to the user. Daily/Weekly Timetable The user enters the date and city pair for which he/she wants to 8.1.17.1 view the daily or weekly schedule and the software retrieves the relevant information and shows it to the user. 8.1.18 3rd Party Integrations 8.1.17 8.1.16 8.1.15 8.1.14 NO 10 YES YES 10 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 187 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC IBE must provide integration facilities with external channels including but not limited to the following for booking, cancellation & refund and report generation/reconciliation: - Mobile 8.1.18.1 - Travel portals - eAuctions - Kiosks - Dial-A-Ticket - ATMs Fraud Prevention Tools Industry standard fraud prevention tools like - Velocity Check - Alerts for High Value transaction / repeated use etc - Credit Card blocking 8.1.19.1 - Creation of negative database should be available in the IBE and new tools should be loaded as and when developed Should be capable of mapping and generating reports based on 8.1.19.2 client IP geographical location The IBE must be integrated to „Verified By Visa‟ (VBV), „MasterCard 8.1.19.3 Secure Code‟ (MSC), „Automatic Address Verification‟ (AAV) for Amex cards and any other security feature available in the industry. 8.1.20 Error Response management 8.1.20.1 Proper and well defined error messages should be displayed. A logging mechanism for error reporting should be provided which 8.1.20.2 defines logging time, resolution time, escalation procedure, categorization of errors and report generation etc. 8.1.19 YES 10 YES 10 YES 10 YES 10 YES YES 10 10 8.2 Frequent Flyer Programme (FFP) Application Requirements Confidential Proprietary Page 188 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.2.1 General Requirement FFP Loyalty Solution with capabilities of accommodating business rules of Frequent Flyer Programme - Flying Returns. The FFP Solution to be integrated with the Airline PSS system with APIs support to Call Centres, reservations, check-in , Kiosks, website , Interactive voice response (IVR) systems and Member Service Centres / Airport Extension Counters– enabling CRM at all touch points. The system must support Partner Management including interfacing, data exchange in user defined formats, transactional processing of accruals and redemptions including reconcilliations, billing, elite level benefits, status miles, upgrades and CRM. The key objective is to improve service to loyal members, increase frequency of customers purchase as also reward and recognize frequent flyers / premium club members. 8.2.1.1 Requirements Confidential Proprietary Page 189 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must offer a highly flexible and scalable software solution with features of: - Online membership support ( profile creation, maintenance, start and end dates, point accrual – air and non air, redemption, activity history, balance history and contact management) and Member Servicing ( active, inactive, fraud, cancelled, suspended, deceased) . This includes real time servicing through multiple touch points i.e. Member Service Centre , Call Centre, DCS, Airline Offices, response handling and analysis - capability to undertake tiers change automatically when the necessary criteria is met. - Generate automatic welcome letters/ regret letters/renewal letters and card fulfillment. - handling lapsing / rollover of mileage points, bonus and rewards, Add on mileage points, Top Up Mileage Points, Vouchers, Point expiration, Mileage Point Statements, promotion/demotion between tiers - Generation of MIS and Point Liability Statement - Updating member‟s name in PNL and Boarding Passes with tier level indicator for premium club members - letter templates for communication - security at group and user level with desired administrative access - Interface with external systems on diverse platforms . - Upgrade at boarding point, lounge access, upgrade coupons, relaxation of baggage weight restrictions - Billing and compensation for flown award ticket segments in global alliance - Store, report, and retrieve all member and program information from a centralized database The system support to include multiple program - Management of a Family Programme, Corporate Programme, Youth Programme, 8.2.1.2 Partner Programme Seniors, Specific Country and others as and when required. YES 10 YES 10 Requirements Confidential Proprietary Page 190 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.2.1.3 8.2.1.4 8.2.1.5 8.2.1.6 The system must have the capability to capture FFP data through on-line screens, process instant enrolment, mileage accruals / redemption requests after automatically validating the FFP number, member‟s name, and flight details i.e. class of travel, fare/discount code/schedule. The system must have Online / Batch Modules to effect data interexchange with different sources (like website, call center, Reservation, Departure control,etc) as per agreed format. The system must support maintenance of records of FFP members and realtime interaction with website www.flyingreturns.co.in, www.airindia.in , and multiple (internal or external) systems. The system must have the capability to capture the FFP member travel data from the DCS FQT lists from different sources in the form of FTL messages . The system must also be able to capture FFP information from Frequent Traveler List (FTL) data from the partner airlines in the system as per the IATA format and access member‟s information from various point of contact. YES 10 YES 10 YES 10 YES 10 Enrolment The system must have provisions of enrolment to over the web and batch enrolments through uploading data files, Online by a Member 8.2.2.1 Service Centre personnel agent while talking to the customer or through the reservation system. The system must have the ability to interactively capture data pertaining to customer from ITR/ PNR (e.g. name, phone number, 8.2.2.2 contact address etc) for enrolling as a new member based carrier specific rules post validation. The system must be able to create and maintain customer profile, 8.2.2.3 dynamic in its interaction and support regular updation of member records. 8.2.3 Customer Profile 8.2.2 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 191 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.2.3.1 8.2.3.2 8.2.3.3 8.2.3.4 The system must have Concise and enhanced customer information view with alerts facility. The Member Service Personnel can query multiple members in one session as also view customer contact history. The system must have a module that monitors all incoming and outgoing customer communication. The System must provide interactive access to carrier frequent flyer database. The System must provide interface to carrier frequent flyer systems or external vendor as needed for queries to debit or credit customer mileage balance. Basic The System must provide the ability to view frequent flyer mileage account data, without any booking, based on carrier specific rules. YES 10 YES YES YES 10 10 10 8.2.4 8.2.4.1 YES 10 The System must support link and dynamic search on frequent flyer 8.2.4.2 databases for the purpose of obtaining frequent flyer number, based on various data elements and carrier specific rules. The System must support provision of both IATA standards (Option 1: itinerary related and Option 2: segment related), using IATA 8.2.4.3 FQT based on carrier specific rules with technical ability to accrue mileage points on a segment basis on all global alliance member carrier operated flights The System must support all accrual and redemption frequent flyer 8.2.4.4 products (e.g. companion travel, sponsoring) and with ability to add new products across carriers and other non-airline partners. The system must support provision to handle other carriers who are 8.2.4.5 hosted on other systems and who participate in the airline frequent flyer programme. 8.2.4.6 The System must provide flexibility to create new frequent flyer tier levels and introduce new products (e.g. new types of upgrades) YES 10 YES 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 192 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must have ability to identify and provide preferred 8.2.4.7 customer benefits, based on tier level within frequent flyer programs (inventory booking guarantee, defined seats). The System must support application of all processes (validation, 8.2.4.8 recognition, accrual, redemption, upgrades), regardless of booking source The system must have the ability to interact with partner carriers frequent flyer systems and provide information of status (tier level) 8.2.4.9 to all business processes at time of segment sell, seat map and advance seat reservation The System must support recognition of all Global Alliance (like Star / One world/ Sky team) tier customers for the purpose of providing 8.2.4.10 unique customer handling, upgrades, awards, promotions and benefits The System must support frequent flyer status at Customer Record 8.2.4.11 or PNR levels, based on carrier specific rules 8.2.5 8.2.5.1 Accrual The system must have provisions to provide the ability to inhibit accrual, based on carrier specific rules (e.g. price line, award travel) YES 10 YES 10 YES 10 YES 10 YES 10 YES 10 The system must have the ability to select frequent flyer program for mileage points accrual by region/airline/segment and/or trip. 8.2.5.2 Provide handoff to appropriate databases in real time post departure (e.g. via FTL message), based on carrier specific rules. The system must have the ability to synchronize mileage point‟s 8.2.5.3 accrual by fare class,region,airline,segment and trip with appropriate databases, based on carrier specific rules. The System must have the ability to re-credit/void miles back to 8.2.5.4 customers account at time of itinerary change/cancel, based on carrier specific rules The system must have the ability to validate travel and handoff 8.2.5.5 information for the purpose of retroactive credit accrual YES 10 YES 10 YES YES 10 10 Requirements Confidential Proprietary Page 193 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.2.5.6 The system must have provisions of Configuration of expiry period of mileage points/ add on mileage points YES 10 The system must have the ability to capture the Mileage points and 8.2.5.7 be automatically credited to the member‟s account via the PNR repository and through text file uploads for partner activities: 8.2.5.8 8.2.6 Bonus mileage points through marketing campaigns. Support multiple user defined tiers configured for individual markets. YES 10 YES 10 Redemption The system must have the ability to validate eligibility against 8.2.6.1 itinerary and mileage points account. The system must support sponsoring (e.g. pass on mileage points 8.2.6.2 award to other person), based on carrier specific rules. The system must support verification of eligibility, calculation and 8.2.6.3 deduction of mileage points from customers account for redemption at time of booking or ticketing, based on carrier specific rules. The system must have the ability to re-credit/void mileage points 8.2.6.4 back to customers account at time of itinerary change/cancel, based on carrier specific rules. The system must capture redemption of mileage points in real time. 8.2.6.5 Members can redeem multiple activities in one transaction. For example, a flight and hotel accommodation. Upgrades The system must have the ability to validate eligibility against 8.2.7.1 itinerary and mileage account including class of service and frequent flyer tier level The System must support all upgrades types, including time initiated 8.2.7.2 upgrades (e.g. FQUG). The system must have the ability to re-credit/void mileage points 8.2.7.3 back to customers account at time of itinerary change/cancel, based on carrier specific rules 8.2.7 YES YES 10 10 YES 10 YES 10 YES 10 YES YES YES 10 10 10 Requirements Confidential Proprietary Page 194 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must have the ability to grant award of 8.2.7.4 mileage/upgrade, as per carrier specific rules (e.g. upgrade as a result of previous mishandling of passenger) The System must support access and viewing of electronic 8.2.7.5 upgrades/awards (entitlements) via the Customer Record based on carrier specific and security rules 8.2.7.6 The system must have the ability to confirm upgrade to customer via preferred communication method and in preferred language. YES 10 YES 10 YES 10 The system must have the ability to verify and calculate eligibility for upgrade at time of re-booking and synchronize deduction of mileage 8.2.7.7 points from customer‟s account at time of ticketing, based on carrier specific rules. The system must have the ability to auto verify, calculate and synchronize deduction of mileage points from customer‟s account to 8.2.7.8 accommodate award travel at time of upgrade and/or waitlist clearance. The System must allow all types of earned and purchased upgrades 8.2.7.9 (paper or electronic) PNR Database The system must have a comprehensive database of PNR records, which can be used for: - Automated updating of FFP data 8.2.8.1 - Automatic accrual - Verification of retro claims - Confirmation of actual travel - Identification of FFP and premium customers 8.2.8 YES 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 195 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must have the ability to create a PNR of the customer if the carrier frequent flyer number is present and also have the ability to link PNRs with a Customer Record at time of creation, based on 8.2.8.2 frequent flyer number. Must support the ability to manage name variations for PNRs, that are linked to one Customer Record (e.g. Sunita Patel in frequent flyer database vs. Sunitha Patel on travel document), based on carrier specific rules with validation. The System must apply customer preferences e.g. seats, frequent flyer programs (from the Customer Record to the PNR) regardless of booking source, based on carrier specific rules. It should allow 8.2.8.3 retrieval of individual PNRs/Customer Records/Group Records/Corporate Records for subsequent action through structured data fields, including but not limited to frequent flyer number, phone number, contact address, ticket number. The system must have ability to grant award of mileage/upgrade, as per carrier specific rules (e.g. upgrade as a result of previous 8.2.8.4 mishandling of passenger) while supporting access and viewing of electronic upgrades/awards (entitlements) via the Customer Record based on carrier specific and security rules. 8.2.8.5 8.2.9 The system must generate Reports based on the travel patterns of each passenger. YES 10 YES 10 YES 10 YES 10 Billing The system must generate several accounting and billing reports 8.2.9.1 that can be used to provide billing information to the Host Carrier's accounting systems. Partnership Management The system have the capability to inter-exchange of information 8.2.10.1 with airlines and non-airlines partners (partnership relationship management) and coalition loyalty 8.2.10 YES 10 YES 10 Requirements Confidential Proprietary Page 196 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must have the ability to generate Liability Reporting 8.2.10.2 system that summarizes the point balances, which exist between the Host Carrier and its various partners. The system must have the ability to generate Accruals and Redemption reports that indicate the point accruals by Partner and 8.2.10.3 their cost as well as reports on redemptions by Partner and their cost. Website system must provide an interface with website which allows for, - Display of all information pertaining to the programme - Dynamic updation of information regarding new promotion/schemes launched from time to time - Online enrollment and generation of a membership - Generation of welcome letters providing the account details 8.2.11.1 - Viewing of account activities/updation of personal details/redemption of award tickets / promotional schemes et al - Submission of missing activities - Acceptance of feedback and maintenance of such records - Form downloads. - Online Redemption through website of airline and non-airline partners CRM and Analytics The system must provide vital current customer information and customer value at the point of each customer interaction; booking In8.2.12.1 flight, Website, Member Service Centres, Airport Extension Counters, Mobile Telephony, Call Centre, Booking Offices, Airport Check –in counters, Alliance Partners etc. The system must customer Profile to include (Name, Address History, Phone Number History, Affiliations, Lifestyles, and 8.2.12.2 Preferences), Activity History (Air, Non-Air, Awards, and Goodwill), Collateral Request History, and Communication Contact History. 8.2.12 8.2.11 YES 10 YES 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 197 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.2.12.3 The system must provide flexible, dynamic support of marketing programs and promotions. YES 10 The system must offer easy-to-use graphical screens to manage 8.2.12.4 Tier Structure (i.e. Normal, Silver, Gold, Platinum, etc.), Member Status (Active, Inactive, Fraud, Cancelled, Suspended, Deceased) The system able to forecast marketing ROI, member segmentation, 8.2.12.5 measure customer value and customer attrition and intervene prior to their departure. The system must support customer's seating and meal preferences, interest, preferred contact methods, travel patterns. Value to be 8.2.12.6 stored, tracked and used with any transaction that customer performs. The system must have segmentation capability that enables approaching customers in logical target groups/ based on 8.2.12.7 demographic information, business patterns, membership details or interests. The system must be able to parameterize valuable information to be 8.2.12.8 sent to members. i.e. any change in their flight timings or promotional messages upon qualification to a higher tier. The system must be able to optimize the customer journey on 8.2.12.9 website and leverage through targeted marketing campaigns. The system must be able to generate detailed reports on all aspects of their web activities, including: traffic analysis, visitor click stream 8.2.12.10 analysis, campaign performance tracking, and technical and content analysis. The System must update carrier frequent flyer databases with enriched customer information after customer has boarded a flight, 8.2.12.11 based on carrier specific rules (Note: Enriched data may include, but is not limited to reservation channel, kiosk, electronic ticketing.) 8.2.13 RES/DCS YES 10 YES 10 YES 10 YES 10 YES YES 10 10 YES 10 YES 10 Requirements Confidential Proprietary Page 198 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to sell from specific inventory/private classes on other carriers to support frequent flyer 8.2.13.1 programs, entitlement program, ZED booking (e.g. special promo e.g. a free ticket out of a lottery) and marketing programs The System must provide the ability to allow frequent flyer partners 8.2.13.2 to sell award inventory, based on carrier specific rules The System must provide the ability to retrieve seat availability and 8.2.13.3 seat characteristics based on security/channel/ customer type/booking class/fares/frequent flyer tier level The System must provide the ability to query travel records, based on a specified criteria and/or Customer Record/PNR/ Group Record/Corporate Record data elements, e.g. - Organize PNRs by frequent flyer tier status or show Customer 8.2.13.4 Records by Corporate Record corporate contract number - Show misconnections due to flight irregularities operations - Organize employee‟s boarding priority and/or date of hire by flight, based on carrier specific rules - Show cancelled PNRs, based on specified criteria (e.g. flight, date) The System must provide carrier specific frequent flyer rules that 8.2.13.5 are accessed during the inventory sell process (e.g. booking guarantee) The System must provide ability to limit frequent flyer redemption buy up (redeming at higher booking class by payment of cash / 8.2.13.6 miles) by O&D, flight number, travel date, and days prior to departure The System must provide ability to limit frequent flyer redemption 8.2.13.7 (indicator to shut off all redemption bookings for a specific travel period) The System must have the facility to customize availability, confirmed and waitlisted sell based on customer attributes in the 8.2.13.8 PNR or from the carrier's frequent flyer system according to carrier specific rules (e.g. guaranteed sell for defined booking classes that are closed, time before departure) YES 10 YES YES 10 10 YES 10 YES 10 YES 10 YES 10 NO 8 Requirements Confidential Proprietary Page 199 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.2.13.9 8.2.13.10 8.2.13.11 8.2.13.12 8.2.13.13 8.2.13.14 8.2.13.15 The System must allow redemption class oversell (e.g. redeem more miles to get better availability) when no seats are available in frequent flyer redemption classes. The carrier will book them in a revenue class, lower the allocation of the revenue class, and automatically rebook into the redemption class and appropriately identify these bookings in the PNR. Exceptions must be allowed to limit the buy up by carrier, O&D, flight, date. The System must provide ticket, with auto pricing, of award travel itineraries, both online and with other carriers The System pricing and repricing of award travel tickets must include automatic application of appropriate fees, service charges and taxes The System must provide the ability to autoprice in miles, money or a combination of miles and money The System must provide handoff to carrier systems (potentially both revenue accounting and frequent flyer program) for all reporting/accounting needs The system must provide handoff to carrier systems (both revenue accounting & FFP) for purchase of products other than air travel using FFP miles. The System must provide the ability to calculate all applicable excess baggage and special charges with currency or frequent flyer miles NO 8 YES YES YES YES 10 10 10 10 YES 10 YES 10 The System must provide the ability to allow/disallow the following types (but not limited to) of passengers on marketing flights: - Non-revenue (confirmed and listed/space available) - Groups 8.2.13.16 - Wholesaler / consolidator / allotments - Passengers using frequent flyer miles for travel (award/redemption) - Passengers requesting advanced confirmed upgrades YES 10 Requirements Confidential Proprietary Page 200 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability for re-accommodation logic as defined by the partners, and initiated by the carrier who is in control of the inventory (e.g. availability, frequent flyer status, customer 8.2.13.17 value, unaccompanied minors, onward connections, time before departure, overbooking parameters, itinerary-based, economicbased) The System must provide the ability to identify passengers by different means (e.g. card swipe, magnetic stripe reader, biometrics reader) and allowing different search criteria (e.g. name, credit card number, ticket number, identification card number, multiple frequent flyer numbers.). Upon successful match, initiate following subprocesses: - Check if coupon is in available status - Search for electronic ticket or if no corresponding electronic ticket can be found, search for alternative electronic ticket (e.g. open coupons) - Ticket verification (stolen ticket information) 8.2.13.18 - Comparison of reservation data and passenger travel plan and ticket data - Informational record creation for go show / no record - Calculation of any required additional fees or refunds if applicable - Document verification, e.g. credit card for electronic tickets, passport/visa information - Upgrade validity, tier level (e.g. based on fare rule, mileage) - Passenger security verification - Undesirable customer verification - Previous customer inconveniences - Search for VDB possibility The System must provide the ability to add a frequent flyer number 8.2.13.19 for post departed and past date flights and publication to the Frequent Flyer system The System must provide the ability to differentiate FQTV, FQTR, 8.2.13.20 FQTU, FQTS, and correctly process benefits/service YES 10 YES 10 YES YES 10 10 Requirements Confidential Proprietary Page 201 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability to allow more than one frequent 8.2.13.21 flyer number with different service types per segment according to carrier specific rules The System must provide the ability to support different collection methods at any point e.g., but not limited to: - Cash - Credit cards - Debit cards - Smart cards 8.2.13.22 - Frequent flyer mileage or vouchers (electronic and paper) - Discount coupons - MCOs and/or travel certificates - Agency waivers Electronic compensation carrier owes customer (based on customer history (CRM), e.g. redemption of electronic inconvenience voucher) The System must automatically process all types of upgrades and downgrades, based on carrier specific rules, including but not limited to: - Frequent flyer (mileage deduction) - Paid upgrade (electronic or paper) 8.2.13.23 - Involuntary upgrade or downgrade (e.g. oversale, mechanical) - Courtesy upgrade for commercial reason or customer recovery - Waitlist for paid class - Employee travel - Customer value After successful upgrade and change to passenger status 8.2.13.24 “boarded”, provide the ability to automatically update account (e.g. electronic upgrade bank or frequent flyer) NO 8 YES 10 YES 10 NO 8 Requirements Confidential Proprietary Page 202 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide the ability for automated and dynamic hand-off of relevant data to all carrier systems based on carrier specific rules, including but not limited to: - Revenue accounting (e.g. ticket and revenue data) - Frequent flyer programs (e.g. mileage accrual, redemption, actual class flown, actual class paid) - Marketing and revenue management systems (e.g. actual booking 8.2.13.25 class, Point of Sale, Goshow/Noshow, Denied boardings, electronic ticket usage, flight irregularities, self-service device usage) - CRM systems and data warehouse - Employee database (e.g. electronic ticket or ticketless usage, class flown, relevant fare information, entitlement) - Invoke hand-off to weight & balance system(s) if applicable, based on carrier specific rules YES 10 8.3 Data Mart applications for Passenger Related Information The Tenderer must provide a Datamart with Data-warehouse capabilities and data mining tools to NACIL mantained and managed by the tenderer. 8.3.1 General Requirements The system should have ease of Use - The product should support cue cards and wizards to help a novice user. - The product should have common MS Windows like interface with the ability to have window control, minimize and maximize buttons, 8.3.1.1 short cut keys, vertical and horizontal scroll bars, point and click interface, etc.. - The product interface should have the facility to provide the user with business definitions of data. - The product should have MS Windows-like online help functions. YES 10 Requirements Confidential Proprietary Page 203 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system should have the capability to capture the purged booking data on daily basis & store it in a data warehouse, with features to query - Passenger reservation record with complete activity history in the PNR on any flight/date/sector, - Inventory record historical data of all flights – RES / DCS, 8.3.1.2 - Ticketing details with complete activity history - Various passenger lists - Complete passenger history data from RES and DCS - Post departure list from DCS - Flight delay information such as STD, ATD, STA, ETA and reason code for delay if any. This system must cover the various business areas of the airlines like (but not limited to) Finance, engineering, operations, Human Resources, etc., - Planning: including route network, fleet and schedules. 8.3.1.3 - Customer: covering sold and flown tickets, departure control data, corporate accounts and customer loyalty data, including a customer valuation model. - Operations: covering actual flight information including schedule disruptions and payload, as well as air traffic control data. 8.3.1.4 The system should deliver a Business Data Warehouse to address the requirement of data extraction, storage, analysis and reporting YES 10 YES 10 YES 10 The system should provide a phase-wise approach for DW design 8.3.1.5 and implementation that would address the most critical of operational entities of the business. The system should provide a middleware backbone, if required, that 8.3.1.6 allows integrated multi-platform applications to communicate and integrate with each other over a real-time environment. 8.3.1.7 The system should provide a customer analytics and reporting tool that provides dynamic and multi-dimensional Airline analysis. YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 204 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Data Source The system should have flexibility to take data in various input forms 8.3.2.1 from various data sources Various modes of input (push/ pull, batch, trickle-feed) should be 8.3.2.2 supported, as the source systems are able to support In case of change/ upgrade of source systems, the strategy in such 8.3.2.3 case needs to be provided 8.3.3 ETL Layer Extract Functionality 8.3.2 YES YES YES 10 10 10 - Tool should support various data source systems, and various extract mechanisms. 8.3.3.1 - This tool should identify and extract only changed data (incremental vs. full loads). - This tool should use sources from different databases as sources within the same ETL process. YES 10 Requirements Confidential Proprietary Page 205 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Transformation - The tenderer should list out the transform functions available out of this tool. The capabilities in defining the transform function may also be listed on an attached sheet. - The functionality that's performed within them should get captured automatically in the tool's metadata repository. - The system should perform 1:N; N:N; N:1 transformations. The tools should be robust with a capability to aggregate or summarize data, using sums, averages and other functions. - This tool should be able to manipulate data through validation checks, derivation of values, calculations, conditional logic - This tool should generate sequence numbers. - This tool should use native database functions when accessing through a native connection. - This tool should be able to embed stored procedures. 8.3.3.2 - This tool should be able to cleanse data using filters. - This tool should be able to easily setup data mapping structure to map data from source structure to created target structure - This tool should be able to sort files for ascending/descending and ASCII/EBCDIC sorting - This tool should be able to filter data in specified range - This tool should provide API to special logic linkage to other tool integration - This tool should be able to cache the lookup tables. - This tool should be able to perform multi-column lookup processes. - This tool should be able to reference any record from current record using record index. - This tool should be able to provide various date function capabilities. - This tool should be able to provide transpose or pivot functions. - This tool should have input/output checkpoints. YES 10 Requirements Confidential Proprietary Page 206 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Load - The system should provide support for many targets (DBMSs Tables or servers). - The system should provide connector support for various systems in the proposed stack. - This tool should be able to load the changed data directly to the target database. 8.3.3.3 - This tool should be able to take advantage of external "fast load" utilities (e.g. SQL Loader/ DB Load). - This tool should be able to support the different load types that will also need data options such as insert, update or delete. - This ETL tool should offer connectivity options to the different target to load the data (on site or remote) RDBMS (flat file, DB2/UDB, ORACLE, SQL etc). - This tool should be able to populate multiple targets through the same transform. Data Quality - This tool should be able to provide error report facility. - This tool should be able to provide Total Control Balancing function for Record Counting. 8.3.3.4 - This tool should be able to provide Total Control Balancing function for Amount Balancing. - This tool should be able to provide RI (Referential Integration) Checking between tables. - This tool should be able to provide data formatting transformation checking YES 10 YES 10 Requirements Confidential Proprietary Page 207 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Metadata Management - This tool should be able to provide a central metadata repository. - This tool should be able to provide for a metadata repository stored in an open format. - This tool's metadata repository should be able to integrate with metadata repositories of leading BI and Data Modelling tool vendors e.g. Business Objects, Brio, Actuate, PowerDesigner, ERWin, etc. - The data movement should be driven by metadata. 8.3.3.5 - The system should provide support for metadata reporting. - This tool should be able to synchronize metadata cross platforms, Operating Systems, RDBMSs and Databases (on site and remote site) - This tool should be able to provide the synchronization function to sync its metadata repository with an enterprise metadata repository - This tool should be able to manage multiple tier metadata structure and support different stages of the developing, testing and production environments. YES 10 Requirements Confidential Proprietary Page 208 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Scheduling - This tool should be able to support end to end ETL data processes scheduling across various hardware / Software platforms. - This tool should be able to schedule batch jobs within the tool. Please detail the platform. - This tool should be able to integrate schedules with standard scheduling software. - Tenderer should specify the number of job dependent layers that the scheduler of this tool can manage 8.3.3.6 - This tool should be able to provide a GUI job scheduling monitoring functions. - This tool should be able to support various types of scheduling e.g. Event, calendar, interval, one-off, appearance of file - This tool should be able to do conditional split of jobs/tasks - This tool should be able to support real time scheduling, such as non batch and transactional jobs. - An alert function should be in place to notify administrators when the error occurred such as e-mail, paging, voice messaging to multiple people Generic Requirements - Manpower availability and Support. - Product Development and Maintenance Support Offering 8.3.3.7 - Compatibility/ Vendor Alliances with other vendors. - The tenderer should provide the implementation methodology. - The tenderer should provide the Local training programs. Data Model Layer The Logical Data Model should be a single enterprise wide data 8.3.4.1 model capable of supporting detail atomic level data (preferably in 3rd Normal form) related to all Airline industry requirements.. 8.3.4 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 209 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC It should not be an application centric or Data mart centric data model. The data model should be primarily a customer-centric data model to support Airline in managing customer relationship as well as operations. The following are the subject areas that should be captured by the data warehouse: - Carrier - Aircraft - Individual Customer Profile - Corporate Customer Profile - Route Network - Distribution - Planned Schedule - Inventory - Reservation - Ticketing - Finance 8.3.4.2 - Passenger Travel - Flown Schedule - Customer Feedback - Customer Service - Individual Customer Derived Information - Loyalty - Campaign Management - Web Activity - ATC Advisory - ATPCO - Check-in history - Lost/ mishandled baggage information - Post departure list from DCS - Complete passenger history data from RES and DCS. - Flight delay information such as STD, ATD, STA, ETA and reason code for delay if any. YES 10 Requirements Confidential Proprietary Page 210 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The Data Model should provide the foundation for customer information as well as operations information to help client to 8.3.4.3 achieve a competitive advantage in keeping with existing and future business requirements. The Data Model should provide the following benefits: - An easy-to-use and easy-to-customize blueprint for scaling the data warehouse by adding new subject areas - The flexibility to build a Data Warehouse that will grow with changes in the business - Help to create a common business language - Capability to support large amounts of detailed data for long periods of time. - Capable of providing “single view” of the enterprise and customer. - Be expandable with facility of increasing functions customizable for 8.3.4.4 the Indian conditions. - Serve the needs of cross-functional business users - Adequately interpretable by a non-technical user. - Should have support for emerging trends in Airline industry. - Capability to interface with call center for customer data - The data model should include the ability to hold a complete history of customer and other important changes: including name, address, and other parameters. - The data model should include the ability to store all changes in status and value of customers and other important parameters over time. YES 10 YES 10 Requirements Confidential Proprietary Page 211 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Other Important Features - The tool should have capability to integrate with the SOA/ Web Services layer. - The System must provide a tool to inter operate with any EAI / ESB layer that is suggested/ could come up in future. Related features 8.3.4.5 are – - Could the tool interact with any EAI/ ESB option suggested, to optimize on single place of data definitions/ data dedup/ data governance - The System must provide a tool interoperate with the EAI/ ESB Layer to move towards near-real time availability of data in future. Data Base Layer - RDBMS should have recoverability features - RDBMS should have data compression facility - RDBMS should have OLAP structures in the DB 8.3.4.6 - Should have mining and campaign management tools. - Ability to integrate to third Party application such as web based Applications. - Database should support parallelism for Query, insert, update and delete. - Database should support data federation technology 8.3.5 Reporting & Data Mart Layer NO 8 YES 10 Requirements Confidential Proprietary Page 212 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC DW should support typical reporting for the following: - Route planning, schedule development, route profitability analysis - Pricing & yield management - Distribution & sales force - Loyalty programme design and optimisation - CRM - customer acquisition, development, retention - Product development 8.3.5.1 - Fraud and abuse - Security and blacklisting - Revenue analysis and forecasting - Manpower and resource planning - Cost management - Operations - analysis of delays, cancellations, fuel burn, - Analytics on analysing Frequent Flyer Program - Customer Value Modeling 8.3.6 Analysis Features YES 10 Requirements Confidential Proprietary Page 213 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The Product should have ad hoc / customized query capabilities. - The Product should have the ability to dynamically change data selection criteria at runtime. - The Product should allow the user to specify user defined calculations and data types (such as whole percentages, decimals to the 4th place, etc.). For example, users should be able to create their own calculations using existing measures in the data mart. - The Product should support standard statistical functions. - The tool should have the ability to calculate mean, median, and frequency. - The access tool should be integrated with a statistical package (for purposes of advanced analytics). - The product should allow the dimensions (aspects of the business) to be related and data retrievals based on these relationships. 8.3.6.1 - The System must provide a tool drill down to greater detail, drill up to consolidated data or across dimensional relationships. - The Product should support drag and drop of data selection criteria on to existing reports. - The System must provide a tool to highlight predefined critical success factors. For example, it should be able to highlight differences between budget and actual in red. - The System must provide a tool score, rank, and group results into ranges. - The tool should support sorting by column. It should be able to define multiple sort orders within a report. - The access tool should support what-if scenarios and forecasting. - The Product should support closed loop analysis, e.g. marking of a group of customers so that the same group may be analyzed in subsequent analyses. YES 10 8.3.7 Query Execution Requirements Confidential Proprietary Page 214 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The Product should have the ability to execute a query in background. - The Product should have the capability of handling more than one query at a time per user. - The Product should have the ability to take the results of a query executed in background and push the results to an end-user via email or alerts. - The user workstation should be locked up when the queries are running - The system should have the facility to provide the user with response time estimates 8.3.7.1 - The system should have the ability to restrict the number of rows returned by a query. - The system should have the capability for users to cancel or abort queries that they have requested - The system should be able to save results so the query does not have to be rerun or results are not refreshed - The System must provide a tool to save query results as relational tables. - The users of the tool should be able to share analyses, if required. - The product should provide tools for execution of user configurable dynamic queries. 8.3.8 Report & Charting Features NO 8 Requirements Confidential Proprietary Page 215 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must support various report types e.g. free form, tabular, cross-tab. - The System should have sophisticated report-painting capabilities, for example, highlighting rows / columns, changing fonts, bolding, inserting page breaks, etc. - The users should be able to mark specific rows for exporting to a relational database, flat file, Excel, or MS Access. - The package should allow multiple charting features such as pie charts, bar charts, columns, lines, and / or area graphs. - The tool should support printing of reports and charts.The printing should be customizable. 8.3.8.1 - The product should have the ability to define headers and footers at page level, and different headers, footers and content for the first and last page of the report. - The Product should have standard report templates that can be used to create reports easily. - The Product should allow for multiple page layouts within a report. - The Product should have the ability to place multiple query result sets in a report. - The Product should allow the additional columns not part of crosstabulations in the report. - The Product should allow allow embedded graphs, text and objects. NO 8 Requirements Confidential Proprietary Page 216 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The Product should have the ability to enter and edit data selection parameters for a report. - The Product should have the ability to define interdependencies between parameters within a report. - The product should have extensive product ability to perform calculations within a report. - The Product should have the ability to restrict the number of rows returned to a query. - The Product should have the ability to control the number of records a report may access. 8.3.8.2 - The Product should have the ability to control the time a report can take to run. - The Product should have the ability to re-use selection code in other reports similar to a stored procedure functionality. - The Product should have the ability to access multiple ODBC compliant databases at the same time in the one query. - The Product should have the ability to format the report results how user prefers - The product should provide tools for dynamic report generation by end users as per his requirements. 8.3.9 Multiple Concurrent Users NO 8 The system should efficiently support access to multiple concurrent 8.3.9.1 users in a real customer production environment. Number of users may be estimated based on information provided in RFP. 8.3.10 Desktop / Application Integration YES 10 Requirements Confidential Proprietary Page 217 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The System must provide a tool to - Export report output to ASCII files. - Export report output via Dynamic Data Exchange (DDE) - current "live" data. - Export report output via Object Linking and Embedding (OLE) static data. - Export report output via HTML. - Export report output / graphs Excel spreadsheets. - Export report output / graphs Word documents. 8.3.10.1 - Export report output / graphs PowerPoint presentations. - Export report output to MS Access. - The System must provide support for sending and receiving reports by email. - The above report should be convertable into Excel, bitmap or other format at time of sending. - The product should allow "cut and paste" operations with other windows applications - The product should allow for seamless integration with Campaign Management, Data mining, ERP, and e-commerce tools. 8.3.11 Portal Integration YES 10 The system should incorporate a web tool for data delivery and reporting - The system should support Internet Expolorer browser. - The System must provide a product publish data to a web page 8.3.11.1 - The system should integrate with other Reporting/BI tools - The system should incorporate a portal - The system should have the flexibility to integrate with Userdesigned Enterprise portal 8.3.12 Automation of Routine Processes YES 10 Requirements Confidential Proprietary Page 218 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The tool should support scheduling of batch reports, for example, scheduling dependencies, time-based scheduling, event-based scheduling, etc.. - The tool should support automatic alerts based on events, for 8.3.12.1 example, predefined issues for immediate attention. - The System must provide a product automatically send messages to specified person(s) based on a particular situation. - The System must provide a product automatically mail the generated reports (run in background) to a specified list of users. NO 8 8.3.13 Security Features Application level security. For example, access is restricted to specific files or directories created by the tool. - The tool should have own Security features like logins to database. - The tool should have integrated data security features such as 8.3.13.1 restricted access by user groups. - The tool should be integrated with a third party security product. - The System must provide a product support LDAP for security. - The product should be tightly integrated with DBMS security YES 10 8.3.14 Other Features Requirements Confidential Proprietary Page 219 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Please mention on the following - Technical Features - Query Execution - Client Server Architecture - End-User Customization - Hardware / Operating System - Network Features 8.3.14.1 - Administration - Metadata - Product Track Record - Product Support - Trained Consultants - Maintenance Support - Vendor Relationships – other vendors The tenderer must use the latest and state of art tools to address data duplication Hardware Used by tenderer for providing hosted DW solution to NACIL 8.3.14.3 The proposed solution hardware for data warehouse server should be scalable to support data volume growth as mentioned in this document. 8.3.14.2 Sample Management Information Reports The System must provide a standard Management Information 8.3.15.1 System Module with capability to provide Online Management Reports 8.3.15.2 Dynamic Flight operation report (scheduled vs. actual operations) The system must have the capability to store planned schedule for a 8.3.15.3 day with complete flight routing viz routings, and scheduled departure at each leg. 8.3.15 YES 10 YES 10 NO 8 YES NO YES 10 10 10 Requirements Confidential Proprietary Page 220 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must have the capability to develop codes for various 8.3.15.4 types of delays due to operational / technical /natural / consequential / miscellaneous reasons The system must have the capability to allow updating of 8.3.15.5 unscheduled operation, extra section flights, deviation from the normal routing of the flights etc to the days' operation The system must have the capability to capture actual operational 8.3.15.6 details of each flight at each leg with actual time of departure and reasons of delays /diversion/cancellations if any. The system must have the capability to compare the planned operation with actual operation and generate management reports 8.3.15.7 under various pre defined criteria viz % of operation accomplished, % of flights operated on time, % of flights delayed, ex each station, region or on the entire network The system must have the capability to generate technical dispatch reliability report based on the number of aircrafts planned for 8.3.15.8 operation vis a vis the number of aircrafts available for operation at the start of each day The system must have the capability to generate flight operation 8.3.15.9 report with delays attributable to each department based on time parameters with reason code The system must generate reports based on Sector wise increase/Decrease load statement based on current month/same 8.3.15.10 month of the previous year/percentage increase or decrease/current year to the month/previous year to the month The system must generate reports based on route performance for the month based on flight number/route/sector/aircraft/seat 8.3.15.11 offered/frequency operated in a month/sector traffic of the month/route seat factor The system must generate reports based on sector wise 8.3.15.12 increase/decrease of load statement for baggage/ mail/newspaper/ freight for current month vis a vis same month of previous year 8.3.15.13 The system must generate station wise embarking/disembarking passenger report on monthly basis YES 10 YES 10 YES 10 NO 6 NO 6 NO 6 YES 10 YES 10 NO 10 YES 10 Requirements Confidential Proprietary Page 221 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must generate reports for seat factor/load factor based 8.3.15.14 on Aircraft type/number of departures for current month and previous eleven months. The system must generate revenue reports based on 8.3.15.15 flight/sector/number of passenger/excess baggage/mail/freight. The system must generate reports based on city pair market 8.3.15.16 performance on a monthly basis The system must have the capability to generate flight performance 8.3.15.17 statistics based upon booked / travelled information for specific date / Date range The system must have the capability to generate sector 8.3.15.18 performance statistics based upon booked / travelled information for specific date / date range The system must be able to generate Point of Sale wise 8.3.15.19 performance statistics based upon booked / travelled information for specific date / date range 8.3.15.20 The system must provide information on seat / load factor / capacity utilization / flight delays / cancellations / on time performance The system must be able to provide information on total system load over a period or for a day with seat / load factor / revenue passenger / total freight / excess baggage / RPKM / ASKM / RTKM / ATKM. The system must be able to provide information on aircraft type wise load with seat / load factor / total revenue passenger / RPKM/ ASKM / RTKM / ATKM. The system must provide flight information based on flight wise total revenue passenger / percentage seat factor / percentage load factor / cargo carried and excess baggage. The system must provide sector information on for instance from station A to station B number of revenue passenger class wise / excess baggage / mail / news / cargo The system must provide station information on seat allocation / revenue passengers / excess baggage / mail / freight / newspaper / cargo carried, etc. YES YES YES YES 10 10 10 10 YES 10 YES 10 YES 10 8.3.15.21 YES 10 8.3.15.22 YES 10 8.3.15.23 NO 10 8.3.15.24 YES 10 8.3.15.25 YES 10 Requirements Confidential Proprietary Page 222 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must provide flight wise freight information on free 8.3.15.26 baggage / excess baggage / mail / newspaper / cargo and total freight The system must provide station wise freight information on free 8.3.15.27 baggage / excess baggage / mail / newspaper / cargo and total freight The system must provide key sector information on daily passenger 8.3.15.28 traffic on selected sectors for a day or period with number of seats allotted / revenue passenger / seat utilization factor / etc. The system must provide class wise flight information on service number / date of operation / station from / station to / seat allocation / payload / non revenue passenger / free baggage / excess baggage / newspaper / mail / freight / cargo / passenger kilometre / seat kilometre / RTKM / ATKM / flight type ( scheduled / additional / charter / etc ). The system must provide aircraft load over a period or for a particular aircraft with the options for extracting data exclusively for domestic, international or all sectors for a day or period. The system must provide information on daily / periodic seat factor / flight pair wise with the options to select data on the basis of parameters such as less than / greater then / and between in percentage. The system must provide information class wise flight analysis with flight number and sum of total passenger in all the classes The system must generate No show/Go show/ Denied boarding report YES 10 YES 10 YES 10 8.3.15.29 YES 10 8.3.15.30 NO 10 8.3.15.31 YES 10 8.3.15.32 8.3.15.33 YES YES NO YES NO YES YES 10 10 4 10 10 10 10 Page 223 of 253 8.3.15.34 The system must generate information pertaining to market trends. The system must provide Sector wise increase / decrease load statement for passengers. The system must provide sector wise seat allotment and passenger 8.3.15.36 load 8.3.15.37 The system must provide region wise, sector wise seat factor 8.3.15.38 The system must provide sector wise passenger carriage 8.3.15.35 Requirements Confidential Proprietary National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must provide sector wise passenger carried vis a vis 8.3.15.39 passenger carried over the same period/day in previous year / month / day The system must provide details of top "N" number of stations as 8.3.15.40 per the carriage vis a vis previous period The system must provide Area wise / Country wise / City wise 8.3.15.41 statistical information for booking / Revenue over a date or date range, based on travel data. The system must provide market performance route wise based on 8.3.15.42 booked / travelled data The system must provide market performance city pair wise based 8.3.15.43 on booked / travelled data. The system must provide seat factor in ascending / descending 8.3.15.44 order The system must provide statement on booking / waitlist / carriage / 8.3.15.45 inflation after flight departure, flight wise / class wise The system must provide total network booking vis a vis carriage 8.3.15.46 and waitlist The system must provide a no show statement date wise / flight 8.3.15.47 wise The system must provide statement on total number passenger 8.3.15.48 booked in groups vis a vis seat offered and network booking day wise/flight wise The system must provide statement on actual seat offered vis a vis 8.3.15.49 inflated capacity flight wise/date wise etc. The system must have the capability to generate the following 8.3.15.50 revenue reports from the revenue accounting system: The system must have the capabilities generating revenue load reports based on flight number/aircraft type/Sector/Number of passengers carried/Excess baggage/Excess weight/Baggage 8.3.15.51 weight/Freight/Mail/Passenger kilometre/Seat kilometre/RTKM/ATKM/Seat factor/Load factor/Distance flown and number of departures YES YES YES YES YES YES NO YES YES YES NO YES 10 10 10 10 10 10 10 10 10 10 10 10 YES 10 Requirements Confidential Proprietary Page 224 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The system must pick up the flight route, TNB and all revenue/Gratis passenger data class wise with gender break up ( Male, female, child counts) the total payload available on the flight along with the total traffic load ( break up of free baggage and total 8.3.15.52 excess baggage wt / total cargo / mail / newspaper ) Actual Time of arrival, actual time of departure, total delay from the Departure Control System along with the Fleet type & Aircraft Registration after flight departure from all board points. The system must provide details of top "N" number of Point of Sale 8.3.15.53 (Travel agents) as per the booking / Revenue over a date range, based on travel data 8.3.15.54 The system must provide details of various type of form of payments collected on Sale, on a date or date range based on travel data The system must provide booking pattern reports with regard to seats booked / seats available and wait list, flight wise / sector wise at defined date range or snap shots such as D-30, D-21, D-15, D-7, etc. The system must have the facility to provide the utilization of promotional / discounted fare basis, based on booking / traveled data for specific date / date range. The system must provide a statement of total carriage flight wise/date wise vis a vis total number of passengers under FFP / APEX / EASY Fares etc The system must provide a statement on utilization of special promotional packages The system must have the facility to generate NACIL v/s Competitor Airlines, carriage based information viz. capacity offered, seats sold, market share on specific sector, ex-specific station on a specific date / date range. YES 10 YES 10 YES 10 8.3.15.55 YES 10 8.3.15.56 YES 10 8.3.15.57 8.3.15.58 YES NO 10 6 8.3.15.59 NO 2 8.4 Revenue Accounting Requirements Confidential Proprietary Page 225 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Sales Accounting (including Refunds and reissues) Processing of data where data of sale & payment is provided electronically or otherwise including but not restricted to; 8.4.1.1 - BSP / ARC - Internet sales involving different Payment Gateways. Processing of data of sale & payment involved including but not restricted to; - NACIL Booking offices sales. 8.4.1.2 - Sales by Agents / GSAs abroad. - Sales by agents in India. - BSP India sales. 8.4.1.3 Maintenance of sales return control and tracking of unreported sales Processing of reissues /refunds and void documents; derivation of 8.4.1.4 commission and adjustment thereto from the reference agency set up; end to end sales processing Converting the provisional coupon to actual values based on sales, 8.4.1.5 once the sale is received per coupon that are processed using provisional values Processing of other passenger documents like EBT, MCO, & PTAs, 8.4.1.6 BDR‟s, ADMs ACMs and MPDs. 8.4.1.7 Raising of Invoices on credit parties and credit card Companies, raising of debit and credit notes on NACIL booking Offices / Agents. Document Collection The vendor will be responsible to collect manual revenue documents, coupons & attachments from NACIL offices at Delhi and Mumbai where all the manual documents will be collected across our network by NACIL. 8.4.1 YES 10 YES 10 YES YES 10 10 YES YES YES 10 10 10 8.4.2 8.4.2.1 YES 10 Document collection is required to be done on regular intervals so 8.4.2.2 that invoices on credit parties are raised and reports for the previous month are generated as per the time schedule advised by NACIL. YES 5 Requirements Confidential Proprietary Page 226 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.4.3 8.4.3.1 8.4.3.2 8.4.3.3 8.4.3.4 8.4.3.5 Data Preparation, Processing, Report Generation & Handling Of Documents Processing of reporting forms along with documents and generation of approximately 180 reports. The report number is indicative only and not exhaustive. YES The formats and detailed specification of the reports would be provided as and when NACIL decide to make this module mandatory All the relevant fields of the tickets have to be captured using super YES long format The data processing would be carried out at preferably at Mumbai or YES Delhi The data will include data processing from all types of pax documents tickets issued including EBT, MCO, PTAs etc., and the YES same may be manual, automated or paperless. The vendor may be required to integrate the data/information of all the modules like BSP /ARC/ Interline Billing/GSAs/ consolidators YES etc. for purposes of generation of reports. YES 10 10 10 10 10 Provide backup of all the captured and processed data / images to 8.4.3.6 NACIL on electronic media like client server/CD or on any suitable electronic media along with retrieval mechanism of the same. Compiled invoices along with copy of the authorization letters and 8.4.3.7 charge slips / credit-slips. will be delivered at designated point for forwarding to sundry parties including credit cards companies After processing, the revenue documents have to be properly sorted 8.4.3.8 stationwise /periodwise and delivered to NACIL designated offices electronically. 8.4.4 Revenue documents Stock Control 10 YES 10 YES 10 Requirements Confidential Proprietary Page 227 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC System for revenue documents stock control for paper tickets and etickets needs to be in place, 8.4.4.1 Ticket Stock & distribution tracking at all NACIL locations at CTOs/ATOs/GSAs and consolidators. 8.4.5 Matching Of Auditors Coupons With Utilisation Control and receipt of Flight Manifests along with flown documents and tracking non receipts of the same. The solution should include a module of matching the auditor‟s coupons with the flight coupons (flown, refunded, cancelled and exchanged and voided) for the purposes of detection and reporting of mismatches on travel documents, and report mismatches for investigation and recovery. 8.4.5.1 In case sales data is not reported while processing matching the flown coupon, the sales details will be created from flown coupon but the sales details would remain in provisional suspense account staging area till actual sales is matched from the sales documents. Detection of discrepancies matching key parameters (e.g. fare basis, booking class, itinerary etc.) between sale & utilization wherever applicable. 8.4.6 Processing of uplift data (including outward billing) YES 10 YES 10 Requirements Confidential Proprietary Page 228 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Processing of passenger uplift data for the Normal Scheduled flights, marketing flights and code share flights(Self and OC) - Using deal codes to arrive at provisional revenue for uplift coupons where sale is not received - Loading of Passenger TCN (self and OC and using the loaded data as provisional information for processing - Processing of delayed incentive reported in the form of ACM,ADM and BDR and affecting the same on revenue rationally wherever applicable. - Creating Passenger Outward Billing outputs from the processed OC uplift, reissue, refunds and rejections arising out of verification of 8.4.6.1 incoming rejections - Calculation of coupon and sector value based on fare & prorates rules etc. - Calculation and booking of agency commission as per Master provided showing market wise commission applicable - Calculation of Airline taxes including Fuel Surcharge-coupon wise - Interline outward and inward billing including proration, SPAs and MPAs - The various interfaces / download mechanism for the above to be provided. - Data processing and validation. - MIS reports (as per agreed format periodicity) from time to time as required by NACIL from the data processed. BSP/ARC NACIL subscribes to iiNET/BSPlink/ATPCO/CRSs/TCN from where the service provider will be given access to download data for 8.4.7.1 processing of sales and other activities across the network of NACIL. 8.4.8 Interline- Inward and Outward 8.4.7 YES 10 YES 10 Requirements Confidential Proprietary Page 229 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.4.8.1 The processing will be carried out covering the following activities : Other Carriers (OC) Coupons uplifted by NACIL – Outward Billing - Receiving the coupons either in physical or electronic form flight wise – as per IET requirements - Data Entry of uplifted manual coupons. - Verification of data entered. - FIM billing and processing. - Processing of uplifted coupons on Proration Software. 8.4.8.2 - Application of MPA and SPA rules. - Creating outward IDEC for airlines identified as IDEC members - Generation of Invoice carrier-wise ICH Forms & NCH Forms i.e. in Form-1, Form-2, etc. and attaching coupons with the invoices ready for dispatch through IDEC tapes to ICH. Other inputs like Cargo and Miscellaneous billing provided by the airline at the invoice level will also be included. - Generation of various MIS reports Billing received from other Airlines- Inward billing - Receipt of coupons/digitized images. - Download of IDEC tape for inward invoice verification of passenger coupons using incoming Form 3, form 1, invoices and coupon listing provided by the airline ( including incoming . 8.4.8.3 - Accounting of billed coupons. - Validation of data. - Processing of coupons on Proration Software. - Matching of prorate values with the billed values. - Generating rejection advice and prorate slips for unmatched values as per RAM rules. - Generation of various MIS reports YES 10 YES 10 Requirements Confidential Proprietary Page 230 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Rejection Process - Receipt of coupons/digitized images of rejected coupons with supporting documents. - Verification of Rejection memo through software & manually. 8.4.8.4 - If rejection is found correct, acceptance of the same and in case found to be incorrect then preparation of rejection memo along with prorate slip and attaching the same with relevant invoice and dispatch. - Assist NACIL in correspondence cases by providing required data. Reconciliation of Accounts Reconciliation of form of payment wise collections of reported sales - Account reconciliation of accounts such as Forward Sales, 8.4.8.5 Discount, Commission accounts etc. - Reconciliation of credit card billing against the credit card companies electronic payment file with detailed mismatch reports for the invoicing done. Masters 8.4.8.6 NACIL shall provide various Masters like PFM, MPM, CITY, AOS, AGENT, AIRLINE, LOST TICKET, GSA, FLIGHT SCHEDULE & AIRCRAFT, ACCOUNT CODES, commission, deal codes,RBDs etc. either directly or through interface with existing systems. Software Solution For The Above Modules 8.4.8.7 A brief write up on technical and functional features of the software solution including procedures should be provided with the technical bid. 8.4.9 Data-Base Maintenance - Post implementation support YES 10 YES 10 YES 10 YES 10 Requirements Confidential Proprietary Page 231 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.4.9.1 After implementation, the vendor will be responsible to maintain all database tables required for carrying out validation and checks to capture input and processing. These data sets / tables should be upto-date as per the notifications issued by all the relevant agencies. These masters may be flight master, fares masters, Fare basis, concession/ promotional fares, stations master and any other master as indicated in 8.7.9 above. YES 10 SPAs / MPAs, proration and modifications in existing procedures by the agencies responsible for framing such guidelines have to be 8.4.9.2 accommodated as per the implementation target notified in the circulars issued from time to time. Any change in the logistics in the application software, after 8.4.9.3 implementation, due to change in procedures have to be incorporated in the system accordingly. Implementation Schedule - The offer should contain a complete implementation plan with milestones/time frames defining the various activities / stages in 8.4.9.4 sequence including installation, testing, trial run, acceptance and training. - A detailed procedure of system tests and acceptance of complete functionality including interface / down loading mechanism shall be agreed by the vendor in mutual consultation with NACIL. 8.4.9.5 8.4.9.6 The party should clearly specify its requirements from NACIL. System Audit 8.4.9.7 NACIL reserves the right to carry out system audit at any time by any agency / source deemed fit. The vendor has to extend all cooperation in this regard. Requirements Daily back up of production data on site as well as well as off site to ensure business continuity Requirements From NACIL YES 10 YES 10 YES 10 YES YES 10 10 YES 10 Confidential Proprietary Page 232 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC Deliverables - Work flow and logistics validation checks incorporated in the system. - Hard/ soft copy of all the tables maintained in the system as and 8.4.9.8 when asked for by NACIL. - Documentation – user manual / Technical reference manual. - The scope and the details of Services to be provided by the vendor and the deliverables specifying Vendors/ NACILs responsibilities to the scope of services to be specified by the vendor. The offer should include the following details of the vendor - The background of the company along with company profile. - Expertise and existing infrastructure to implement such projects. - Airline domain knowledge and expertise in the area of revenue 8.4.9.9 accounting. - Turnover of the company in last three years. - Copies of Annual Reports of the Company for the last three years. - Quality standards adopted by the company. - Methodology and project team structure for implementation of such projects. YES 10 YES 10 MIS The MIS module should be on line, user friendly and query based 8.4.10.1 with comparative analysis with previous periods. MIS module must be installed and implemented at the stations and 8.4.10.2 departments at Corporate and regional Offices of NACIL and any other location decided accordingly. The vendor is required to integrate the information of other modules 8.4.10.3 as desired by NACIL for MIS purposes, even if that module(s) does not form the part of this contract. 8.4.10 YES YES 10 10 YES 10 Requirements Confidential Proprietary Page 233 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC The existing NACIL network connectivity is required to be used for MIS Connectivity Obtaining and processing of flight operating and traffic inputs for non pax traffic such as Cargo and Mail provided by NACIL at flight 8.4.10.5 sector level. Obtaining and processing of landing and handling and navigation costs from NACIL at flight sector level. 8.4.10.4 YES 10 YES 10 8.6 Customer Relationship Management ( CRM ) 8.5.1 8.5.2 The tenderer must offer a flexible, scalable CRM solution provide a Single View of the Customer in the following manner:Multi-Department – The system shall have facility for profile based usage of system for various customer-facing departments such as marketing, sales, and customer service. Multi-Channel – The system shall provide the ability to track multi channel customer interactions including telephone, web, email, mail, fax, and in-person meetings Online/Offline – - The customer management system should support offline work, such as entering contact notes on a laptop and then synchronizing at the end of the day - The system should have the capability to support wireless online work, such as quickly updating customer records via a PDA or smart phone Internal/External – The customer management system should manage all customer interactions, whether driven by customerfacing employees, self-service customers, prospects, or channel partners Robust Integration – The system should support integration with other sources of customer data like PSS, FFP, Call Centre etc. The System shall offer Customer Process Improvement:YES YES 10 10 8.5.3 YES 10 8.5.4 YES 10 8.5.5 YES 10 8.5.6 8.5.7 YES 10 Requirements Confidential Proprietary Page 234 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.5.8 8.5.9 8.5.10 8.5.11 8.5.12 8.5.13 8.5.14 8.5.15 8.5.16 8.5.17 8.5.18 8.5.19 8.5.20 Process Platform – The customer management system shall enable airline to automate, manage, analyze and evolve key customer processes e.g.- New client setup, customer service escalation, compliance with rules and policies. Cross-Departmental – The customer management system shall enable to automate and orchestrate processes that extend across departments and touch multiple systems Single Interface – The system shall support single familiar interface for frontline airline employees. Complex Processes – The customer management system shall enable improvement of the efficiency of processes that involve a high volume of transactions and improve the execution of processes requiring complex rules or personalized handling Ease of Change – The customer management system shall provide for intuitive, graphical interfaces that business analysts can use to quickly create and modify process flows and business rules as the airline‟s business changes. IT Independent – The system shall allow business analysts to modify processes on their own without requiring IT personnel introduce code changes to achieve the same. Analytical Tools - The system shall provide for analytical tools to monitor the working of various processes. The System must offer Executive Value:Key Reports – The customer management system shall provide key reports for business executives helping run the business Analytics – The system shall provide for drill down facility from highlevel reports to analyze additional detail. Comprehensive Insight – The system shall provide for reports by integrating with data from other systems such as financial accounting and ERP. The system shall provide an executive dashboard facility and e-mail alert functionality for executives who prefer not to access the system directly The system shall offer employee value by :- YES 10 YES YES 10 10 YES 10 YES 10 NO YES 8 10 YES YES NO 8 8 6 NO 8 Requirements Confidential Proprietary Page 235 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.5.21 8.5.22 8.5.23 8.5.24 8.5.25 8.5.26 Personalization – The system shall provide for personalization in a manner that it suits the individual user needs or method of working. Streamlined Data Entry – The system shall provide for automating commonly performed actions. Update Facility – The system shall provide for update using both online as well offline mode. Support – The system provide for access to timely, effective training materials and support resources The system shall provide for standard IT resource requirements :Industry Standards – The system shall leverage XML and other industry standard technologies instead of any proprietary tools for interfacing Web Services – The System shall be Web Services enabled allowing other applications to use the Internet-standard protocols such as XML and SOAP to access the entire set of customer management capabilities Ease of Upgrades – The system shall allow us to upgrade the CRM system quickly and painlessly The system must provide a Platform for Business Growth and Change Expansion – While intial rollout would be for single or multiple sales teams or call centre groups, the system shall provide for expansion to meet the needs of additional departments and groups in the future. Scalability – The system shall support support thousands of users with sub-second response times Global – The system shall support multiple time zones, currencies and languages The system offered shall provide for risk mitigation Client References – The tenderer shall provide for client information for reference NO YES YES YES 4 8 8 10 YES 10 8.5.27 NO 8 8.5.28 8.5.29 YES 10 8.5.30 YES 10 8.5.31 8.5.32 8.5.33 8.5.34 YES YES 10 8 YES 8 Requirements Confidential Proprietary Page 236 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.5.35 8.5.36 8.5.37 8.5.38 8.5.39 8.5.40 8.5.41 8.5.42 8.5.43 8.5.44 8.5.45 8.5.46 8.5.47 8.5.48 8.5.49 Proven Methodology – The Tenderer shall provide for a strong ecosystem of third-party and vendor consultants with deep product knowledge and a library of best practices gathered from many years of successful deployments Total Cost of Owenership – The vendor shall provide for track of low ongoing maintenance, integration, upgrade and administrative costs Future Vision – The vendor shall have a technology vision to provide our business with a source of competitive advantage The system should provide for direct access and indirect access to a wide range of backend and legacy systems The system should provide access both in real time and via batch load. The system should provide for system security through - Authorized sign-ins - Adherence to standard airline security architecture - Software tools for easy administration The system should provide for audit trail for activities carried out on the CRM system The system should provide for administration which - Is centrally managed - Has easily updatable client workstation - Is highly configurable The system should provide for Integrated Source for Customer Information which has One Enterprise wide Data Store for all customer information The solution based on Enterprise Service Bus architecture to provide easy (plug/play) integration. The system should provide for cater for at least 2500 users and 20 million queries per year The system should be J2EE compliant The system should provide for Screen Design which is: GUI based Uncluttered Easy to navigate and use YES 8 YES YES YES YES 8 8 8 10 YES 10 YES 10 YES 10 YES 10 YES YES YES YES YES 10 10 8 6 6 Page 237 of 253 Requirements Confidential Proprietary National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.5.50 The CRM should be integrated to the following passenger service applications :- Airline inventory and reservation system - Airline departure control system - Airline Frequent Flyer Program (Loyalty Program) module - Airline Lost Baggage Tracer systems - Airline Internet Booking Engine - Airline Data Warehouse Module - Airline Call Centre - Airline Customer Servicing Units - In-flight Customer Feedback System The CRM module should be capable of capturing following information (but not limited to) from the Customer Profile maintained in the airline inventory and reservation system and build a database - Name (first & last) - Date of Birth - Address - Pin Code - City - Country - Meal Preference - Seat Preference - Hobbies - Residence Phone No. - Office Phone No. & extn. - Mobile No. - e-mail address - Log-in ID - Password - Passport Details - FFP No. - Any other loyalty Program No. YES 10 8.5.51 YES 10 Requirements Confidential Proprietary Page 238 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.5.52 8.5.53 The system shall have the capability to create Corporate Profiles The system should have the capability to provide corporate preferences that are enforceable at the time of booking and alerts/ Auto pop up during retrieval of passenger record in DCS System should have the capability to create Agency/ Agent profile with distinctive data such as corporate profile descriptive information / individual profile descriptive & personal information / preference data for airlines , service class , hotel and car rental preferences and useful reservation data for use of PNR creation System should have the capability to create Family data / profiles System should have the capability to maintain travel history within the profile and cumulate the travel history of frequent travelers System should have the capability to display list of all active PNR‟s in the system that are associated with a profile The CRM module should offer Campaign Management System The module should support various communication channels like SMS, e-mail, IVR, voice messages etc. viz. diverse contact management System should have the capability to create client selective mailing lists and generate statistical reports on the profiles created per office The system should be able to create a comprehensive Knowledgebase and provide a knowledgebase management system The CRM module should identify the most valued customers by tracking flights,co-brand activities etc. The CRM module should track customers‟ flying experience and provding information at any touch point through a feedback management system. YES YES 10 10 8.5.54 YES 10 8.5.55 8.5.56 8.5.57 8.5.58 8.5.59 YES YES YES YES YES 8 10 10 10 10 8.5.60 YES 8 8.5.61 8.5.62 8.5.63 YES YES YES 10 10 10 Requirements Confidential Proprietary Page 239 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.5.64 8.5.65 8.5.66 8.5.67 8.5.68 8.5.69 8.5.70 8.5.71 8.5.72 8.5.73 8.5.74 8.5.75 The system should provide data mining tools and have the capability of data access and reporting, statistical modelling etc for targeting campaigns,segmentation and profiling Does the system support: - Simultaneous login by all users (approx. 3000) - Co-browsing facilities - Integrated audit trails across media - Provide data integrity - Create work flows Does the system capture an individual's transactional data and filter this data through a "rules engine”. It should support proactive and reactive campaigns. The system should provide a chat module The system should provide quality monitor tools like remote barge-in The system should be able to create workflows The system should have a customer feedback, complaint handling systems & escalation mechanism The system should give alerts and reminders to supervisors in case laid down parameters are not met The system should have the provision for routing of mails, calls etc with categorization for auto assignments, event based assignment The system should provide for data integrity & security The system should provide for up-sell & cross sell capabilities by providing alerts The system should provide for opportunity tracking The system should provide for advance customer analytics including: - Current Value - Future Value - Behavioral segmentation - Behavior Change YES 10 YES 10 YES NO YES YES YES YES YES YES YES NO 10 6 10 10 10 10 8 10 10 8 8.5.76 YES 10 Requirements Confidential Proprietary Page 240 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 8.5.77 The system should be able to provide any customer data/ information to any preferred device (either via a PC to the front-line staff or to the customer's own mobile phone etc.) Architecture Diagram of offered hosted CRM solution to NACIL - The tenderer must provide a complete architecture diagram (layerwise) with detailed explanations in attached sheets stating there in - Hardware & software (operating system as well as database system and other software) platform of the solution - Interconnectivity and interface with hosted PSS system. - Synchronization mechanism with the hosted PSS database - Interconnectivity & interface mechanisms with other systems as and if applicable. NO 8 8.5.78 YES 10 9 9.1 9.2 Disaster Recovery Requirements The tenderer shall provide for an alternate Disaster Recovery (DR) / Business Continuity Planning (BCP) Site. The Tenderer must have an operational Disaster Recovery Data Centre for all the offered services. The alternate site should be at a location different from the primary site. The tenderer must have a DR/BCP solution to ensure no data loss for core PSS applications. Recovery up-to the last committed transaction is required for core PSS applications. The tenderer must have a DR/BCP solution to ensure no data loss for surround applications (like IBE, Data Mart, FFP). Recovery up-to the last committed transaction is required for these surround applications. DR preparedness and technical strategy will be reviewed onsite by NACIL team once every year. Tenderer shall provide details of the DR policy, architecture, methodology and details of the work process. YES YES 10 10 9.3 YES 10 9.4 YES 10 9.5 9.6 YES YES 10 10 Requirements Confidential Proprietary Page 241 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 9.7 tenderer must have an on-site backup system, at the production data centre location. This would take over the functioning of the production system, without any performance degradation and zero data loss in case of its unavailability due to failure. YES 10 10 Training & Training System Requirements The Tenderer must provide comprehensive training on the product to the required users/ IT personnel as designated by the airline in the form of ”train the trainer“ module of training which must cover training of all the features of the system and include hands on training and exercises. The Tenderer must make a provision for imparting user training under „train the trainer‟ module for minimum of 150 participants estimated at 100 for Reservation, Fare & Ticketing and 50 from Departure Control (including Weight and Balance) The tenderer must provide 25 (twenty five) copies of comprehensive User/Technical manuals and training material in Hard copy formats in addition to corporate license for unlimited Soft copies. The tenderer must conduct Familiarization program for middle and senior levels functionaries from various departments of merged entity at no additional costs. The tenderer must agree to impart User Training in India at NACIL Training Centre in Mumbai and Hyderabad. The Tenderer must agree to provide a facility of online tutor /help package for self-help/training in the form of a Computer Based Training (CBT) having self paced courses for all applications and modules. It should have different levels of Training such as Beginner, Normal User, and Expert User. The tenderer shall provide a Training System which shall be a reflection of the Production System 10.1 YES 10 10.2 YES 10 10.3 NO 4 10.4 10.5 NO YES 4 10 10.6 NO 10 10.7 YES 8 Requirements Confidential Proprietary Page 242 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 10.8 10.9 10.10 10.11 10.12 10.13 10.14 The Training System database shall be populated from the Production System without any need for Production System downtimes. The Training System database shall be refreshed at regular intervals which is mutually agreed by between airline and tenderer and also when specifically requested. The training system shall have facility of providing for external links to other systems of other airlines and various other GDS. The training system must be available to the airline personnel for training on the various offered applications round the year. The training system shall have the facility to advance the date or have the date set backward in case there is a need. The training system shall be on a different system or partition of the system than the one used for Production purposes. The tenderer, as part of the turnkey project, must provide for Technical training in the area of Networking/System and Data Centre Infrastructure and System / Database / Application Architecture including DR methodology and processes to technical team of the airline. A total of 60 trainer days at Tenderer‟s Data Centre location must be earmarked (Six batches of NACIL technical personnel, each batch having 10 personnel and 10 days training for each batch). YES 8 YES NO YES NO YES 8 6 8 6 8 YES 10 11 11.1 11.2 11.3 Testing and Test System Requirements The tenderer shall provide for a Testing System which shall be a reflection of the Production System The test system data shall be populated from the production system without any need for production system downtimes. The test system database shall be refreshed at regular intervals which is mutually agreed by between airline and tenderer and also when specifically requested. YES YES YES 8 8 8 Requirements Confidential Proprietary Page 243 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 11.4 11.5 11.6 11.7 11.8 The test system shall have facility of providing for external links to other systems of other airlines and various other GDS. The test system must be available to the airline personnel for testing on the various offered applications round the year. The test system shall have the facility to advance the date or have the date set backward in case there is a need. The test system shall be on a different system or partition of the system than the one used for Production purposes. The tenderer must provide a utility to prepare a test script and execute the same to conduct repetitive testing in the system. YES YES NO YES YES 10 8 6 8 10 12 Project Implementation The tenderer shall provide for a detailed Project Management methodology stating the various phases with proper time lines involved in the migration of the core PSS applications from the IC RTB system and the AI USAS system to a common unified database on the tenderer‟s hosted system. The tenderer shall provide for a dedicated team, one stationed at New Delhi for the IC system data migration and another team stationed at Mumbai for the AI system data migration, to ensure close coordination with the NACIL project management team. The Tenderer must commit to set up a full fledged office in New Delhi and Mumbai for the project with the project team available during the implementation and migration period, and till one year after the cutover is done on to the last module of the offered solution. The tenderer shall provide details of the tenderer team members roles and responsibilities The complete data of future bookings is required to be provided on daily basis to NACIL. 12.1 YES 10 12.2 YES 10 12.3 YES 10 12.4 12.5 YES YES 10 8 Requirements Confidential Proprietary Page 244 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 12.6 The Tenderer must provide a comprehensive change management procedure to be adopted in the course of implementation of the project, and thereafter for the term of the contract. YES 10 13 13.1 13.1.1 Service Level Agreement Availability of Production Systems - Requirements The Tenderer is required to provide scheduled operations 24 hours a day, 7 days a week, as measured in any time zone The tenderer is required to provide 99.97 % system availability uptime over a calendar month based on a 24 hour day for the core PSS application and surround modules calculated at the designated PoPs. The downtime will be measured on a non-cumulative basis. Availability includes planned and unplanned outages. Any outages, planned or unplanned shall be counted against the SLA Response Times for Production Systems - Requirement The response time at the PoPs for 80% of transactions need to be within 1 second on round the clock basis. The response time at the PoPs for 10% of transactions need to be within 2 seconds on round the clock basis. The response time at the PoPs for 10% of transactions need to be within 4 second on round the clock basis. YES 10 13.1.2 13.1.3 13.1.4 YES YES YES 10 10 10 13.2 13.2.1 13.2.2 13.2.3 YES YES YES 10 10 10 Requirements Confidential Proprietary Page 245 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 13.2.4 The tenderer must provide the expected avareage response times for the following business functions at the NACIL PoPs in the following table format. Business-Functions Expected Average Response Times 1. Availability 2. Passenger Booking 3. Passenger Check-in 4. Passenger Lists 5. Schedule Change 6. e-Ticketing 7. Interline e-Ticketing 8. IATCI Check-in 9. Baggage Reconcilliation System 10. Automated Boarding Control 11. Weight & Balance The response would be measured at each PoPs separately. The Tenderer shall provide adequate online/log-based performance monitoring tools in the offered Solution, which among others would provide a measure of linkwise network performance (current & historical) like uptime, utilization, latency, packet loss, and response time from Host systems. The utility should be provided to the airline also. Tenderer shall provide for an application / utility to check and monitor the SLA status for various parameters with daily, weekly and monthly information. It shall have a provision for status comparative reports across weekly , monthly , quarterly and yearly periods.The utility should be provided to the airline also. The tenderer must provide on daily basis application-wise list of aborts to airline for monitoring the system performance Database Backup, Recovery & Maintenance Requirements YES 10 13.2.5 YES 10 13.2.6 YES 10 13.2.7 YES 10 13.2.8 YES 10 13.3 Requirements Confidential Proprietary Page 246 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 13.3.1 13.3.2 13.3.3 13.3.4 13.3.5 The Application Service Provider (ASP) shall have defined industry standard policies for data backup and restore of all relevant databases maintained for the airline. The procedures followed should adhere to the defined policies for database backup and recovery. Tenderer shall provide for a detailed information about the plan for database backup, recovery and maintenance tenderer must provide for seven cycles of database backup and corresponding audit trails to be made available for the airline. Tenderer shall ensure that all data must be backed-up on a continuous daily basis (e.g. no data older than 24 hours) in an offsite location Tenderer shall provide for adequate database and application level security. Detailed policy regarding the same shall be made available to the airline as part of the response to the RFP. Help Desk Support – Requirements Tenderer shall provide 24 x 7 help desk support services both for NACIL end user and technical support. Tenderer shall provide with well-defined escalation process. Tenderer provide for a Toll Free Number(s) accessible from various stations within India and also from stations outside India. Tenderer shall provide for answer rates for help desk calls by a live person with 85% within 15 seconds, 05% within 20 seconds, and remaining 10% within 60 seconds Tenderer shall support first call resolution for NACIL end-user help desk of 95% or greater Tenderer shall provide information about problem resolution response times for every month Tenderer shall make available a team comprising of functional experts / Technical specialists / product specialist personnel at NACIL designated sites (one team each in Mumbai and New Delhi) during the implementation and for a period which will be mutually decided based on the system performance and the support team. YES 10 YES YES YES 10 10 8 YES 10 13.4 13.4.1 YES 10 13.4.2 13.4.3 13.4.4 YES YES YES 10 10 10 13.4.5 YES 10 Requirements Confidential Proprietary Page 247 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 13.5 Problem Management - Requirements Tenderer shall additionally have an application providing facility to report or open a trouble ticket detailing the nature of problem and reporting details. The application shall provide with all possible statistics of the status and history of the various trouble tickets Support defined response times (in point 13.5.7 mentioned below) to attend to a call based on different severity levels ( defined in points 13.5.3 thru 13.5.6) Note:- Response Time for problem reported is measured in terms of time taken from the tenderer's reciept of the notification of the problem until work begins on the problem resolution Level 1 Severity : Major Service Outage - Direct Impact on operations Impact - Critical 13.5.1 YES 10 13.5.2 Level 2 Severity : Major Service Outage - Indirect impact on operations Impact - Critical, Restricted functionality, Operational Degradation Level 3 Severity : Service Unusable - Some impact Impact - Some impact, Work Around available Level 4 Severity : Partly Service Degraded Impact - Not Critical, Deffered maintenance acceptable YES 10 Requirements Confidential Proprietary Page 248 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 13.5.3 Tenderer shall support response time for problem reported Level 1 Severity cases - 100 % within five minutes Level 2 Severity cases - 100 % within ten minutes Level 3 Severity cases - 100 % within an hour of problem reporting. Support Mean Time to Repair ( MTTR ) requirements Level 1 Severity cases - 05 minutes , work around should be provided so that actual operation not getting affected Level 2 Severity cases - 20 minutes , Level 3 Severity cases- One hour Level 4 Severity cases- Based on agreed time frame on a case to case Tenderer shall provide updates for Level 1 Severity Cases- every 5 minutes Level 2 Severity Cases - every 15 minutes Level 3 & Level 4 Severity cases - every half an hour Tenderer shall provide a Plan to meet these service levels. Tenderer shall provide an Escalation Process (Matrix containing Levels, Time Range, Contact Information) to help raise / resolve operational issues as regards business applications, systems and network. Tenderer shall provide expectation of extent of airline involvement in the problem management process. Availability of Training System & Test System – Requirements The Tenderer is required to provide scheduled operation of test system and training system, 24 hours a day, 6 days a week, as measured in any time zone The tenderer is required to provide 99.0% system availability uptime over a calendar month based on a 24 hour day X 6 day week test and training system for core PSS applications calculated at the designated PoPs. YES 10 13.5.4 YES 10 13.5.5 13.5.6 13.5.7 YES YES YES 10 10 10 13.5.8 13.6 13.6.1 YES 8 YES 10 13.6.2 YES 10 Requirements Confidential Proprietary Page 249 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 13.6.3 13.6.4 13.6.5 13.7 13.7.1 13.7.2 13.7.3 The downtime will be measured on a non-cumulative basis. Availability includes planned and unplanned outages. Any outages, planned or unplanned shall be counted against the SLA Refresh of the training database on a regular basis in consultation with the airline. Response Times for Training & Test Systems - Requirement The response time at the PoPs for 80% of transactions need to be within 1 second on round the clock basis. The response time at the PoPs for 10% of transactions need to be within 2 seconds on round the clock basis. The response time at the PoPs for 10% of transactions need to be within 4 second on round the clock basis. The tenderer must provide the expected avareage response times for the following business functions at the NACIL PoPs in the following table format. The tenderer must provide the expected avareage response times for the following business functions at the NACIL PoPs in the following table format. Business-Functions Expected Average Response Times 1. Availability 2. Passenger Booking 3. Passenger Check-in 4. Passenger Lists 5. Schedule Change 6. e-Ticketing 7. Interline e-Ticketing 8. IATCI Check-in 9. Baggage Reconcilliation System 10. Load control 11 Automated Boarding Control YES YES YES 10 10 10 YES YES YES 10 10 10 13.7.4 YES 10 Requirements Confidential Proprietary Page 250 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 13.7.5 13.7.6 The response would be measured at each PoP separately. The Tenderer shall provide adequate online/log-based performance monitoring tools in the offered Solution, which among others would provide a measure of linkwise network performance (current & historical) like uptime, utilization, latency, packet loss, and response time from Host systems. Tenderer shall provide for an application / utility to help check and monitor the SLA status for various parameters with daily, weekly and monthly information. It shall have a provision for status comparative reports across weekly , monthly , quarterly and yearly periods. YES 10 YES 10 13.7.7 YES 10 13.8 Availability and Response time of Surround Modules (IBE, FFP and CRM) The Tenderer is required to provide system availability/uptime for the Surround Modules over 365 day period of 99.97 % average based on a 24 X 7 basis. (including network connectivity between tenderer 's systems and PoPs and equipments at PoPs) . The Tenderer must commit to an average Response Time of 1.5 seconds at the NACIL‟s Points of Presence (PoPs) for the Surround Modules The Tenderer shall provide information on respective MTTR, Problem Esclation Procedure, Help Desk Support and Problem Management methodology in detail for each of the Surround Modules General Requirements ( for all Application SLA ) The selected Tenderer will be required to enter into a detailed Service Level Agreement with NACIL based on the Performance parameters of the offered solution. The Tenderer must commit to maintain Service Level Agreements / Back to Back arrangements with all it's Hardware/Network/Third Party Vendors/Solution Providers from the award of contract by NACIL till the term of the contract. 13.8.1 YES 10 13.8.2 YES 10 13.8.3 YES 10 13.9 13.9.1 YES 10 13.9.2 YES 10 Requirements Confidential Proprietary Page 251 of 253 National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 13.9.3 The tenderer must facilitate NACIL's interaction on functionality/technicality/development/industry update related matters directly with Tenderer's third party solution providers on an on going basis, and as and when required by NACIL. Customization: YES 10 13.10 The Tenderer must commit to customize the offered solution to fulfil the specific requirements of NACIL as stated in the RFP within the 13.10.1 price quoted. This would also include the customization of functionalities responded under 'CC' within the timeframe indicated The Tenderer must commit to provide within the quoted price 500 mandays of customization support per year for Core PSS, Related Application and Surround Modules during the term of the contract 13.10.2 over and above the customization as necessary to meet the requirements as specified in this RFP. Unutilized mandays will be carried forward through the term of the agreement. 13.10.3 The Tenderer must continue to pass on Global Technological upgrades, if any, to NACIL at no additional cost YES 10 YES 10 YES 10 14 Technical Bid Tenderer Profile The tenderer has experience in migrating in-house applications a. RTB database of an airline on to a hosted platform of the tenderer? b. UNISYS USAS database of an airline onto the hosted platform of the tenderer? c. E-ticket database from ETDB service provider to the tenderer hosted system? d. E-ticket database from airline ET database on the hosted system ET DB? ASP should be SEI CMMI level 5 certified. 14.1 14.2 14.3 14.4 14.5 14.6 NO NO NO NO NO 8 8 8 8 6 Page 252 of 253 Requirements Confidential Proprietary National Aviation Company India Ltd Assigned Priority 1 to 10 Tenderer’s Response YES / NO PSS RFP S.No Requirements Mandatory YES / NO Time line for CC FC1 FC2 CC NC 14.7 14.8 14.9 The tenderer shall have an escrow agreement in place The Tenderer shall provide information as regards the future Roadmap for products and services. The Tenderer shall provide during the last quarter of each year, information as regards the future Roadmap for products and services. As part of product evaluation, tenderer is required to provide for demonstration of areas of functionalities of core PSS applications. The Tenderer is required to provide the draft copy of Final Agreement to be signed with NACIL for this turnkey project YES YES YES 10 10 10 14.10 14.11 YES YES 10 10 Requirements Confidential Proprietary Page 253 of 253