Monday, February 23, 2015

[DMANET] CfP Journal of Revenue and Pricing Management

CfP Journal of Revenue and Pricing Management:
Special Issue on Robust Revenue Management
Guest Editor: Prof. Catherine Cleophas, RWTH Aachen University

In 2016, a special issue of the Journal of Revenue & Pricing Management
will publish a series of papers on Robust Revenue Management.

Beyond classically considered uncertain demand, sources of uncertainty
motivating robust revenue management include capacity changes, revenue
assigned to booking classes, technical or organizational constraints
affecting the implementation of dynamic pricing, service blackouts leading
to spill between physical products, changes in the competitive situation,
or economic shocks rendering historical data obsolete. As revenue
management is applied to novel application areas, new and adapted process
requirements may create new sources of uncertainty.

The research challenge motivating this call for papers is threefold: 1.
Research is needed to identify sources of uncertainty in revenue management
beyond demand. 2. The short- and long-term impacts of uncertainty depending
on the applied revenue management concept have to be quantified. 3. Making
revenue management more robust calls for new forecast and optimization
algorithms as well as process designs.

In considering robust approaches to revenue management, authors should
explore solutions that reduce uncertainty as well as those that strive to
make the best of uncertain outcomes through increased flexiblity.
Contributors are also particularly encouraged to consider the implications
of designing robust revenue management concepts and information flows with
a view toward human decision makers and behavioral operations research.

Find the call for papers here:

Deadline for submissions is 15 April 2015. Papers should be submitted by
email to
The subject line of the email should read "Robust Revenue Management".

* Contributions to be spread via DMANET are submitted to
* Replies to a message carried on DMANET should NOT be
* addressed to DMANET but to the original sender. The
* original sender, however, is invited to prepare an
* update of the replies received and to communicate it
* via DMANET.