<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Fisher.LimitedTableM — BattleActs Exam 8 Forum</title>
        <link>https://battleacts8.ca/8/forum/index.php?p=/</link>
        <pubDate>Sun, 05 Apr 2026 18:57:17 +0000</pubDate>
        <language>en</language>
            <description>Fisher.LimitedTableM — BattleActs Exam 8 Forum</description>
    <atom:link href="https://battleacts8.ca/8/forum/index.php?p=/categories/fisher-limitedtablem/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Lim M Infinite Calc Problem #2</title>
        <link>https://battleacts8.ca/8/forum/index.php?p=/discussion/189/lim-m-infinite-calc-problem-2</link>
        <pubDate>Mon, 25 Sep 2023 01:36:41 +0000</pubDate>
        <category>Fisher.LimitedTableM</category>
        <dc:creator>jmoore13</dc:creator>
        <guid isPermaLink="false">189@/8/forum/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Hi!  For the second Infinite Calc Problem on this section (the one that is not like the Source Text Ch 3 Q13 question), is this just calculating the Insurance Charge for the agg deductible?  I expected to need to add the charge for the per-occ deductible to it (E - E(Ad)) like in the Ch3 Q13 question.</p>]]>
        </description>
    </item>
    <item>
        <title>What are two reasons it may be preferable to price separately using approach 1?</title>
        <link>https://battleacts8.ca/8/forum/index.php?p=/discussion/182/what-are-two-reasons-it-may-be-preferable-to-price-separately-using-approach-1</link>
        <pubDate>Sat, 16 Sep 2023 13:59:21 +0000</pubDate>
        <category>Fisher.LimitedTableM</category>
        <dc:creator>downthesun01</dc:creator>
        <guid isPermaLink="false">182@/8/forum/index.php?p=/discussions</guid>
        <description><![CDATA[<p>The first bullet underneath this question is:</p><ul><li>There may be enough data to update the per-occurrence excess charge most often than the aggregate excess charge.</li></ul><p>I don't understand what this means. Should it be more often instead of most often? Even then, what's the reason that we'd like to update the per-occurrence limit more often than the aggregate limit? Is it because that's the limit getting hit more often?</p>]]>
        </description>
    </item>
    <item>
        <title>PowerPack Question 16</title>
        <link>https://battleacts8.ca/8/forum/index.php?p=/discussion/145/powerpack-question-16</link>
        <pubDate>Tue, 25 Oct 2022 01:50:25 +0000</pubDate>
        <category>Fisher.LimitedTableM</category>
        <dc:creator>jmoore13</dc:creator>
        <guid isPermaLink="false">145@/8/forum/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Is the State/Hazard Group Relativity strictly for use in the ICRLL method?  Would we ever use it in a Limited Table M Question?  I noticed it was given in the PowerPack Question 16 but didn't seem to be used and didn't see anything in the wiki about it for LimTableM so wanted to check.</p>]]>
        </description>
    </item>
    <item>
        <title>Chap 3 Question 10 part c</title>
        <link>https://battleacts8.ca/8/forum/index.php?p=/discussion/102/chap-3-question-10-part-c</link>
        <pubDate>Sun, 11 Sep 2022 15:26:27 +0000</pubDate>
        <category>Fisher.LimitedTableM</category>
        <dc:creator>pass8now</dc:creator>
        <guid isPermaLink="false">102@/8/forum/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Hi, </p><p><br /></p><p>In this question, there is a single loss of 150K.</p><p>The ratable loss is 100K (due to the incident limit of 100K).</p><p>The 50K in excess of the incident limit are already priced for through the excess loss premium.</p><p>Therefore, (and this is the question... more of a confirmation than a question): the insurer does pay the full 150K claim, but only adjusts the premium based on the ratable loss. I.e. the insured pays a difference in premium, but does not retain any part of the loss.</p><p><br /></p><p>Correct?</p>]]>
        </description>
    </item>
    <item>
        <title>Limited Table M vs. Table L</title>
        <link>https://battleacts8.ca/8/forum/index.php?p=/discussion/53/limited-table-m-vs-table-l</link>
        <pubDate>Sat, 16 Oct 2021 20:06:38 +0000</pubDate>
        <category>Fisher.LimitedTableM</category>
        <dc:creator>ph2warne</dc:creator>
        <guid isPermaLink="false">53@/8/forum/index.php?p=/discussions</guid>
        <description><![CDATA[<p>I believe the argument goes that Table L streamlines the process by allowing for a single insurance charge to be stored in a single Table that can be applied to a single expected loss estimate (E).  We do this by changing the aggregate insurance charge basis to be divided by total unlimited losses (E) instead of limited losses, so that it is now on the same basis as the per-occurrence excess ratio, k. Because they are both proportional to E, they can be summed and stored together as table L.</p><p>Limited Table M, on the other hand, expresses the aggregate insurance charge on the basis of limited expected losses in the denominator, and then (like Table L) adds the per-occurrence charge k, which is proportional to unlimited expected losses (E).  Because of this basis difference, we cannot add the two ratios and store them together in one table since they must each be applied to a different claim exposure base. I think this is why we call it a 2-step method even though Table L also must derive k as a second step then add it to the aggregate charge estimate.</p><p>To help verify my understanding of the linkage between the two methods, I tried estimating the Limited Table M insurance charge estimate for Source text: Chapter 3 Q14. Compared to the Table L estimate we get r_D = 1.5 x 250/200 = 1.875, and then integrating with a Uniform(0,2) limited entry ratio distribution (instead of U(0,1.6) for Table L), we get phi_D(1.875) = 1.25 x (phi*(1.5)-k) = E/E_D * (phi(1.5) - k), exactly the basis the change I was expecting. This then shows that both methods add the value of k on-top of this aggregate charge estimate, except that Limited Table M cannot add the 2 ratios together to store in a common table due to the basis difference.</p><p><br /></p><p>So this is where my question begins.  Table L overcame the basis difference between the aggregate and per-occurrence charge by expressing the aggregate charge on the basis of E to match k. Is there good reason why Limited Table M could not have alternatively re-expressed k on the basis of limited expected losses to match the base of its aggregate insurance charge? Then the 2 could be summed, and in theory applied to an estimate of limited expected losses instead of vs. unlimited claims like for Table L.</p><p>I'm trying to reason why this is not a considered alternative; I don't think I've seen justification for this in the reading, but this seems like an interesting comparison to draw.  Would the problem with this latter alternative be that excess per-occurrence claims relative to limited claims would not normalize for policy size or severity skewness as well, and thus contain too much over-dispersion to yield reliable estimates? I'm not totally certain on this reasoning yet, just trying to think my way through it now so I won't have to on the exam if needed.  Curious to hear what others' thoughts are, or if I've maybe gone astray while thinking my way through any of the above details.</p><p><br /></p><p>Thanks!</p>]]>
        </description>
    </item>
   </channel>
</rss>
