Business Requirements Document

Booking Flexibility (Self Insurance)

Version: 0.32

Document Identification
Document ID JQ_SINS_BR Version 0.32 Author David Galovic Issue Date 19 January 2010

Revision History
Author David Galovic Version 0.1 Description Initial Draft Date updated 19 January 2010

David Galovic

0.2

Added requirement for 7 day and 28 day cancellation products Clarified requirement around SSR and fee

2 February 2010

David Galovic

0.3

3 February 2010

Table of Contents
1. Overview ................................ ................................ ................................ ................................ .......... 3 1.1. 1.2. 1.3. 2. Document Purpose and Scope ................................ ................................ ................................ . 3 Introduction ................................ ................................ ................................ .............................. 3 Project Scope ................................ ................................ ................................ ........................... 3
Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed Field Code Changed

Business Requirements and Features ................................ ................................ ............................... 4 2.1. 2.1.1 2.1.2 2.1.3 2.2. 2.3. Booking Engine ................................ ................................ ................................ ........................ 4 Price Protection ................................ ................................ ................................ .................... 4 Change Protection ................................ ................................ ................................ ................ 4 Cancel Protection ................................ ................................ ................................ ................. 5 Price Protection Claim Page ................................ ................................ ................................ ... 65 Retrieve Booking ................................ ................................ ................................ ...................... 6

3.

Project Stakeholders ................................ ................................ ................................ ......................... 7 3.1. 3.2. Business Owners................................ ................................ ................................ ...................... 7 Business Stakeholders ................................ ................................ ................................ ............. 7

1.

Overview

1.1. Document Purpose and Scope

The purpose of this document is to describe the business requirements for the website implementation of the Jetstar Booking Flexibility product. This document should serve as a reference for suppliers to produce more detailed technical specifications and work breakdown structure (Statement of Work) as necessary.

1.2. Introduction
The goal of Booking Flexibility is to offer several new self insurance ancillary products for customers to pre-purchase online. These products will include protection against future reductions in fare price and waiving of change and cancellation fees.

1.3. Project Scope

The products that will be offered are: Price Protection Refund the fare difference between the fare paid and any sale fare Jetstar subsequently offers. Change Protection Allow date, time and flight (route) changes on a JetSaver fare for a limited period of time without incurring a change fee. Cancellation Protection Allow cancellation of a flight without incurring cancellation fees, and a voucher refund of the full fare value.

2.

Business Requirements and Features

The following is a high-level description of the business requirements. A full set of technical specifications will be created by BCS and approved by Jetstar Airways. These requirements will be reviewed and approved by the Business Owners and Technical Stakeholders before the commencement of the design phase. Adjustments can be made at a second review at the end of the design phase, in consultation with the stakeholders.

2.1. Booking Engine

1. The protection products will be offered for purchase on the payment page 2. The panel will contain a product description and a checkbox 3. When the protection option is chosen, the available products will become visible 4. All products apply to all passengers on all journeys

2.1.1 Price Protection

1. Fee price is per pax per journey 2. Available for all domestic fare products (JetSaver Light, JetSaver or JetFlex) 3. Opt-in (checkbox not selected by default) 4. The product will only be offered when the following conditions are met: 4.1. The booking is POS AU (AUD is the booking currency) 4.2. The route is one of the following (bi-directional): 4.2.1.MELOOL 4.2.2.MELHBA 4.2.3.MELADL 4.2.4.SYDOOL 4.2.5.SYDHBA 4.2.6.SYDADL 5. When selected, an SSR/fee (SSR name to be defined) is added to all segments for all passengers on the booking 5.6. A service fee (fee code name to be defined) is also added to each passenger on the booking 6.7. The fee is displayed under the Extras section in the booking summary
Formatted: Highlight

2.1.2 Change Protection

1. Fee price is per pax per journey 2. Available for all domestic fare products (JetSaver Light, JetSaver or JetFlex) 3. JetFlex fares will have a $0 fee rule attached (ie. JetFlex get the SSR for free) 4. Opt-in (checkbox not selected by default) 5. The product will only be offered when the following conditions are met: 4

5.1. The booking is POS AU (AUD is the booking currency) 5.2. The route is one of the following (bi-directional): 5.2.1.MELOOL 5.2.2.MELHBA 5.2.3.MELADL 5.2.4.SYDOOL 5.2.5.SYDHBA 5.2.6.SYDADL 6. When selected, an SSR/fee (SSR name to be defined) is added to all segments for all passengers on the booking 6.7. A service fee (fee code name to be defined) is also added to each passenger on the booking 7.8. The fee is displayed under the Extras section in the booking summary 8.9. Not offered for sale if departure date is within 28 days
Formatted: Highlight

2.1.3 Cancel Protection (7 day and 28 day)

1. Two cancellation products will be offered, one for 7 days and one for 28 days 2. The only difference between the two products is the SSR that gets applied 3. Fee price is per pax per journey 4. Available for all domestic fare products (JetSaver Light, JetSaver or JetFlex) 5. JetFlex fares will have a $0 fee rule attached (ie. JetFlex get the SSR for free) 6. Opt-in (checkbox not selected by default) 7. The product will only be offered when the following conditions are met: 7.1. The booking is POS AU (AUD is the booking currency) 7.2. The route is one of the following (bi-directional): 7.2.1.MELOOL 7.2.2.MELHBA 7.2.3.MELADL 7.2.4.SYDOOL 7.2.5.SYDHBA 7.2.6.SYDADL 8. When selected, an SSR/fee (SSR name to be defined) is added to all segments for all passengers on the booking 8.9. A service fee (fee code name to be defined) is also added to each passenger on the booking 9.10. The fee is displayed under the Extras section in the booking summary

10.11. Not offered for sale if departure date is within 28 days 11.12. Not offered if any fares on the booking are C or E class fares (sale fares). That includes C[1-9], CL[1-9], E[1-9] and EL[1-9]

2.2. Price Protection Claim Page

1. A custom price claim page needs to be developed that sites outside of SkySales 2. The page will be hosted on a separate web server running IIS and .NET 3.5 3. The page will contain text and a form to capture customer claim data 4. Data required to be captured: 4.1. PNR 4.2. Flight Number 4.3. Flight Departure Date 4.4. Customer Name 4.5. Customer Email Address 4.6. Date/Time stamp when form is submitted 5. The page will perform standard server side validation on the data format for each field (all are required) 6. On successful form submission, the application will do an API availability call to New Skies to retrieve the cheapest fare in each fare product category available (JetSaver, JetFlex etc) for the particular flight date and flight number supplied. 7. The form data and API response will be stored in a MySQL database running on the server 8. The form data should always be stored, even if the API call is unsuccessful 9. On submission of the form, a thank you message is displayed to the customer along with some information text

2.3. Retrieve Booking

1. On the first My Booking page a message is displayed to the customer if either the Change or Cancel protection SSRs are detected on the booking (text to be provided). The message will direct the customer to call the call centre to make a claim.

3.

Project Stakeholders

3.1. Business Owners

y y Kevin Ger Head of Pricing and Revenue Management Chris Brown Project Manager

3.2. Business Stakeholders

y y y y y y y y y y David Galovic eCommerce Project Manager Emma Gibson Manager Offline Channels Charles Gibson Commercial Information Manager Cathryn Morris Manager Reservation Systems Marco Vetter eCommerce Manager Lisa Christodoulou Offline Channels Policy Analyst Osanda Ranasinghe Distribution Analyst Gary Iakovidis Flight Analyst Shafeeq Ahmed Test Analyst Kelly Powell - Revenue & Forecast Analyst