<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://en.formulasearchengine.com/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=85.181.53.0%2F24</id>
	<title>formulasearchengine - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://en.formulasearchengine.com/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=85.181.53.0%2F24"/>
	<link rel="alternate" type="text/html" href="https://en.formulasearchengine.com/wiki/Special:Contributions/85.181.53.0/24"/>
	<updated>2026-09-24T18:51:47Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.47.0-wmf.7</generator>
	<entry>
		<id>https://en.formulasearchengine.com/w/index.php?title=Lieb%E2%80%93Liniger_model&amp;diff=24840</id>
		<title>Lieb–Liniger model</title>
		<link rel="alternate" type="text/html" href="https://en.formulasearchengine.com/w/index.php?title=Lieb%E2%80%93Liniger_model&amp;diff=24840"/>
		<updated>2014-01-25T12:41:24Z</updated>

		<summary type="html">&lt;p&gt;85.181.53.212: /* Definition and solution of the Model */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{technical|date=November 2010}}&lt;br /&gt;
&lt;br /&gt;
EMSR stands for Expected Marginal Seat Revenue and is a very popular [[heuristic]] in  [[Revenue Management]]. There are two versions: EMSRa&amp;lt;ref&amp;gt;Belobaba, P. P., Air Travel Demand and Airline Seat Inventory Management. Flight Transportation Laboratory. Cambridge, MIT. PhD, 1987&amp;lt;/ref&amp;gt; and EMSRb,&amp;lt;ref&amp;gt;Belobaba, P. P., Optimal vs. heuristic methods for nested seat allocation. Presentation at ORSA/TIMS Joint National Meeting, 1992&amp;lt;/ref&amp;gt; both of which were introduced by Belobaba. Both methods are for &#039;&#039;n&#039;&#039;-class, static, single-resource problems. Because the models are static some assumptions apply: classes are indexed in such a way that the fare for the highest class, &amp;lt;math&amp;gt;r_{1}&amp;lt;/math&amp;gt;, is higher than the fare for the next highest class, &amp;lt;math&amp;gt;r_{2}&amp;lt;/math&amp;gt;, so &amp;lt;math&amp;gt;r_{1}&amp;lt;/math&amp;gt; &amp;gt; &amp;lt;math&amp;gt;r_{2}&amp;lt;/math&amp;gt; &amp;gt; ... &amp;gt; &amp;lt;math&amp;gt;r_{n}&amp;lt;/math&amp;gt;; demand arrives in a strict low to high order in stages that are indexed with &#039;&#039;j&#039;&#039; as well; demand for class &#039;&#039;j&#039;&#039; is distributed with cdf &amp;lt;math&amp;gt;F_j(x)&amp;lt;/math&amp;gt;. For simplicity it is also assumed that demand, capacity and the distributions are continuous, although it is not very difficult to drop this assumption.&lt;br /&gt;
&lt;br /&gt;
==EMSRa==&lt;br /&gt;
EMSRa is the first version that Belobaba came up with. The idea behind the heuristic is to add the protection limits that are calculated by applying [[Littlewood&#039;s rule]] to successive classes. Suppose that we are in stage &#039;&#039;j+1&#039;&#039; and we want to calculate how much capacity we need to protect for stages &#039;&#039;j, j-1,..., 1&#039;&#039;. Then we are actually calculating protection limit &amp;lt;math&amp;gt;y&amp;lt;/math&amp;gt;&amp;lt;sub&amp;gt;j&amp;lt;/sub&amp;gt;. To do so we consider every class in &#039;&#039;j, j-1,..., 1&#039;&#039; and compare that class, indexed with &#039;&#039;k&#039;&#039;, with &#039;&#039;j+1&#039;&#039; in isolation. For every combination of &#039;&#039;k&#039;&#039; and &#039;&#039;j+1&#039;&#039; we compute the protection level for that class with [[Littlewood&#039;s rule]]:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;math&amp;gt;P ( D_k &amp;gt; y_k^{j+1}) = \frac{r_{j+1}}{r_k}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The idea of EMSRa then is to add all these protection limits to get the protection limit for &amp;lt;math&amp;gt;y_j&amp;lt;/math&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;math&amp;gt;y_j = \sum_{k=1}^j y_k^{j+1}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However, there is a problem with this method because it does not take the statistical averaging effect into account. Suppose, for example, that classes &#039;&#039;1&#039;&#039; to &#039;&#039;j&#039;&#039; have the same fare &#039;&#039;r&#039;&#039;, then EMSRa will calculate the protection limit for &amp;lt;math&amp;gt;y_{j+1}&amp;lt;/math&amp;gt; with&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;math&amp;gt; P( D_k &amp;gt; y_k^{j+1}) = \frac{r_{j+1}}{r}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However, because the fare for all these classes is the same they should be aggregated. EMSRa will calculate protection limits that are too conservative. In other words, it will reserve too many seats for the higher fares, thereby rejecting too many low fare bookings. Although having equal fares is not realistic this will also happen if the difference between fares is small. Therefore EMSRb was invented.&lt;br /&gt;
&lt;br /&gt;
==EMSRb==&lt;br /&gt;
One of the most widely used RM heuristics is EMSRb. It is simple and produces under certain conditions close to optimal results. Belobaba reports studies in which both EMSRa and EMSRb were compared. He shows that EMSRb is consistently within 0.5 percent of the optimal solution, while EMSRa under certain conditions can deviate more than 1.5 percent from the optimal solution. However, with mixed order of arrival and frequent reoptimization both methods perform well.&amp;lt;ref&amp;gt;Belobaba, P. P., Optimal vs. heuristic methods for nested seat allocation. Presentation at ORSA/TIMS Joint National Meeting, 1992&amp;lt;/ref&amp;gt; There is also study by Polt that shows mixed results.&amp;lt;ref&amp;gt;Polt, S., Back to the roots: New results on leg optimization. In 1999 AGIFORS Reservations and Yield Management Study Group Symposium, London, UK, 1999&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
EMSRb is also based on an approximation that compares two classes, but it does take the statistical averaging effect into account. Instead of aggregating protection levels, as EMSRa does, it aggregates demand. Suppose we are again in stage &amp;lt;math&amp;gt;j+1&amp;lt;/math&amp;gt; and we want to calculate the protection limit &amp;lt;math&amp;gt;y&amp;lt;/math&amp;gt;&amp;lt;sub&amp;gt;j&amp;lt;/sub&amp;gt;. Then first all future demand for classes &#039;&#039;j, j-1,…, 1&#039;&#039; is aggregated:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;math&amp;gt;S_j = \sum_{k=1}^j D_k&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
and the weighted revenues  are calculated:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;math&amp;gt; \overline{r}_j = \frac{\sum_{k=1}^j r_k \cdot D_k}{\sum_{k=1}^j D_k}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then, again with Littlewood’s rule, the protection limit for classes &#039;&#039;j&#039;&#039; and higher is calculated such that:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;math&amp;gt; P( S_j &amp;gt; y_j ) = \frac{r_{j+1}}{\overline{r}_j}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Usually demand is considered to be independent and distributed normally with a mean  and a variance . Using that the protection limits can be calculated as:&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;math&amp;gt; y_j = \mu_j + z_\alpha \cdot \sigma_j&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
with the mean and variance of the demand to come as &amp;lt;math&amp;gt;\mu_j = \sum_{k=1}^j \mu_k&amp;lt;/math&amp;gt; and &amp;lt;math&amp;gt;\sigma_j^2 = \sum_{k=1}^j \sigma_k^2&amp;lt;/math&amp;gt; respectively. &amp;lt;math&amp;gt;z_\alpha&amp;lt;/math&amp;gt; is calculated with the inverse of the normal distribution &amp;lt;math&amp;gt;z_\alpha = \phi^{-1}(1-\frac{r_{j+1}}{\overline{r}_j})&amp;lt;/math&amp;gt;. This is done for each j, giving the protection limit for every class.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;!--- See [[Wikipedia:Footnotes]] on how to create references using &amp;lt;ref&amp;gt;&amp;lt;/ref&amp;gt; tags which will then appear here automatically --&amp;gt;&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
* [[Yield management]]&lt;br /&gt;
* [[Littlewood&#039;s rule]]&lt;br /&gt;
&lt;br /&gt;
{{DEFAULTSORT:Expected Marginal Seat Revenue}}&lt;br /&gt;
[[Category:Pricing]]&lt;/div&gt;</summary>
		<author><name>85.181.53.212</name></author>
	</entry>
</feed>