Market/Airline/Class (MAC) Revenue Management RM2003

25
hopperstad Consulting Market/Airline/Class (MAC) Revenue Management RM2003 Hoppersta d May 03

description

Market/Airline/Class (MAC) Revenue Management RM2003. Hopperstad May 03. Issues. Model structure Background: PODS Functional form Some results Potential real-world application Lines of inquiry. Airline RM modeling assumptions a short (public) history. - PowerPoint PPT Presentation

Transcript of Market/Airline/Class (MAC) Revenue Management RM2003

Page 1: Market/Airline/Class (MAC)  Revenue Management RM2003

hopperstadConsulting

Market/Airline/Class (MAC) Revenue Management

RM2003

HopperstadMay 03

Page 2: Market/Airline/Class (MAC)  Revenue Management RM2003

2

hopperstadConsulting

Issues

• Model structure

• Background: PODS

• Functional form

• Some results

• Potential real-world application

• Lines of inquiry

Page 3: Market/Airline/Class (MAC)  Revenue Management RM2003

3

hopperstadConsulting

Airline RM modeling assumptionsa short (public) history

• 80’s – leg/fare class demand independence 6 to 8% revenue gains over no RM

• 90’s – path (passenger itinerary)/class demand independence 1 to 2% revenue gains over leg/class RM

• Current – excursions into path demand independence ½% revenue gain over path/class RM

Page 4: Market/Airline/Class (MAC)  Revenue Management RM2003

4

hopperstadConsulting

• Yet, anyone who has ever taken an air trip knows that flights are picked on a market basis– trading-off airlines, paths, fares and fare class

restrictions

• Thus, an ultimate RM system must be market-based

• However, market-based RM is a giant step– it is proposed here that a small next step is to assume

independent market/airline/class demand

Airline RM modeling assumptions

Page 5: Market/Airline/Class (MAC)  Revenue Management RM2003

5

hopperstadConsulting

• PODS is a full-scale simulation in the sense that:– passengers by type (business/leisure) generated by

their• max willing-to-pay (WTP)• favorite/unfavorite airlines & the disutility attributed to unfavorite airlines• decision window & the disutility assigned to paths outside their window• disutility assigned to stops/connects• disutility assigned to fare class restrictions

– passengers assigned to best (minimum fare + disutilities) available path with a fare meeting their max WTP threshold

– RM demand forecasts based on historical bookings

Background: PODSpassenger origin/destination simulator

Page 6: Market/Airline/Class (MAC)  Revenue Management RM2003

6

hopperstadConsulting

• Leg/class baseline: Expected Marginal Seat Revenue (EMSR)

• Three path/class RM systems available in the current version of PODS– NetBP– ProBP– DAVN

Background: PODS

Page 7: Market/Airline/Class (MAC)  Revenue Management RM2003

7

hopperstadConsulting

• EMSR processes (virtual) classes on leg in fare class order– solves for the forecast demand and average fare for

the aggregate of all higher classes– obtains a protection level of the aggregate against the

class– sets the booking limit for the class (and all lower

classes) as the remaining capacity – protection level

Background: PODS

Page 8: Market/Airline/Class (MAC)  Revenue Management RM2003

8

hopperstadConsulting

• NetBP solves for leg bidprices (shadow price) using a network flow LP equivalent– path/class is marked as available if the fare is greater

than the sum of the bidprices of the associated legs

Background: PODS

Page 9: Market/Airline/Class (MAC)  Revenue Management RM2003

9

hopperstadConsulting

• ProBP solves for leg bidprices by iterative proration– prorate path/class fare by ratio of bidprices of

associated legs– for each leg order the prorated fares and solve a leg

bidprice using standard (EMSR) methodology and re-prorate

– path/class is marked as available if the fare is greater than the sum of the bidprices of the associated legs

Background: PODS

Page 10: Market/Airline/Class (MAC)  Revenue Management RM2003

10

hopperstadConsulting

• DAVN uses the bidprices from NetBP as displacement costs and then for each leg– reduces path/class fare by the displacement from

other leg(s)– creates (demand equalized) virtual classes– uses standard (EMSR) leg/class optimizer to set

availability

Background: PODS

Page 11: Market/Airline/Class (MAC)  Revenue Management RM2003

11

hopperstadConsulting

• Embed NetBP/ProBP/DAVN in a MAC shell rather than develop a new optimizer (for now)

• Use current PODS forecasters and detruncators– pickup and regression forecasting – pickup, booking curve and projection detruncation– aggregate path/class observations into MAC observations

• Assumption: all spill is contained within a MAC until all paths (of index airline) are closed for the class

Architecture

Page 12: Market/Airline/Class (MAC)  Revenue Management RM2003

12

hopperstadConsulting

• Bidprice engine (NetBP, ProBP)

Optimizers

*Rule: no path/class can be re-opened

yes

no

allocate MAC forecasts to associated path/classes

solve for leg bidprices

close path/classes with fares less than sum of bidprices for the associated legs*

re-allocate spill from newly closed path/classes to open path/classes

any new path/classes closed?

quit

Page 13: Market/Airline/Class (MAC)  Revenue Management RM2003

13

hopperstadConsulting

• Path/class availability solver (DAVN)

Optimizers

yes

no

allocate original MAC forecasts to associated path/classes and create virtual classes using final MAC bidprices

solve for leg/virtual class availability

close path/classes that have been assigned to closed virtual classes on associated legs re-allocate spill from newly closed

path/classes to open path/classes

any new path/classes closed?

quit

recalculate leg/virtual class demand

Page 14: Market/Airline/Class (MAC)  Revenue Management RM2003

14

hopperstadConsulting

• First-choice preference estimation for paths of a MAC– constructed from historical bookings for open paths– iterative procedure to account for partial observations

(not all paths open for a class)

• Assumption: second-choice, third-choice,…… preference can be calculated as normalized (removing closed paths) first-choice preference

Additional technology

Page 15: Market/Airline/Class (MAC)  Revenue Management RM2003

15

hopperstadConsulting

• Estimation of spill-in rate from, spill-out rate to competitor(s)– Key idea: equilibrium

• if the historical fraction of weighted paths open for time frame for the index airline (hfropa) and the competitor(s) (hfropc) is observed

• and if the the current fraction of weighted paths open is observed for both the index airline and the competitor(s) (fropa, fropc)

• then when fropc is less than hfropc, spill-in must occur• and when fropc is greater than hfropc, spill-out must occur

• Fraction of competitor paths open inferred from local path/class availability (AVS messages)

Additional technology

Page 16: Market/Airline/Class (MAC)  Revenue Management RM2003

16

hopperstadConsulting

• Competitor demand estimation– based on observed historical market share

(which is also a function of equilibrium)– uses booking curves to adjust for limited (input) time

horizon

• Spill-in/spill-out defined by adjusted competitor demand and maximum spill-in rate across classes

• Assumed that once MAC demand modified for spill to/from competitor, all spill is contained within a MAC

Additional technology

Page 17: Market/Airline/Class (MAC)  Revenue Management RM2003

17

hopperstadConsulting

• PODS network D– 2 airlines– 3 banks each– 252 legs– 482 markets– 2892 paths– 4 fare classes

• Demand – demand factor = 1.0– 50/50 business/leisure

Some results

20 CITIES

HUBAL 1

HUBAL 2

20 CITIES

Page 18: Market/Airline/Class (MAC)  Revenue Management RM2003

18

hopperstadConsulting

• Airline 1 uses one of the path/class systems– without a MAC shell– with a MAC shell

• Airline 2 uses the PODS standard leg/class system (EMSR)

• Results quoted as % revenue gains compared to both airlines using EMSR

Results 1

Page 19: Market/Airline/Class (MAC)  Revenue Management RM2003

19

hopperstadConsulting

Results 1

-1.50%

-1.00%

-0.50%

0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

3.00%

3.50%

Airline 1

Airline 2

NetBP ProBP DAVN

+MAC +MAC +MAC

reve

nue

gain

Page 20: Market/Airline/Class (MAC)  Revenue Management RM2003

20

hopperstadConsulting

• Airlines 1 and 2 follow a sequence of RM using DAVN– start with both using EMSR– move 1: airline 1 adopts DAVN– move 2: airline 2 adopts DAVN– move 3: airline 1 adopts DAVN + MAC– move 4: airline 2 adopts DAVN + MAC

• Results quoted as % revenue gains compared to both airlines using EMSR

Results 2

Page 21: Market/Airline/Class (MAC)  Revenue Management RM2003

21

hopperstadConsulting

Results 2

-1.00%

-0.50%

0.00%

0.50%

1.00%

1.50%

2.00%

Airline 1

Airline 2

AL1 DAVN AL2 DAVN AL1 MAC AL2 MAC

reve

nue

gain

Page 22: Market/Airline/Class (MAC)  Revenue Management RM2003

22

hopperstadConsulting

• Components of MAC revenue gain– optimizer (NetBP, ProBP, DAVN) by itself– MAC without spill-in/spill-out– MAC spill-in/spill-out

• Results quoted as % revenue gains compared airline 1 using EMSR

Results 3

Page 23: Market/Airline/Class (MAC)  Revenue Management RM2003

23

hopperstadConsulting

Results 3

NetBP ProBP DAVN0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

3.00%

3.50%

MAC spill

MAC

Optimizer

reve

nue

gain

Note: Mac spill gain dominated by spill-in compared to spill-out

Page 24: Market/Airline/Class (MAC)  Revenue Management RM2003

24

hopperstadConsulting

• Can’t say how difficult

• But can propose it will provide for a new level of technical integration of RM and the rest of the airline– use of external path preference models to determine first-

choice preference, conditional second, third,…. preference and account for the effect of schedule changes

– use of external marketing data, econometric models, etc. to define at least components of market demand

Potential real-world application of MAC

Page 25: Market/Airline/Class (MAC)  Revenue Management RM2003

25

hopperstadConsulting

• New optimizer that integrates the MAC arguments– rather than embedding in a shell

• Model vertical/diagonal buy-up– requires the new optimizer

• Market-based RM– pessimistic unless competitor RM itself is modeled

Lines of inquiry