Operations Management: Manzana Insurance: Fruitvale Branch
Operations Management: Manzana Insurance: Fruitvale Branch
Operations Management: Manzana Insurance: Fruitvale Branch
Case Analysis:
Section C - Team 12 Sameer Kumar Gupta Saurabh Kumar Supriya S. K. Sehgal Shanmuga Sundaram P Rajesh D Shashank Shekhar (1311195) (1311196) (1311197) (1311198) (1311188) (1311200)
done because new policies were considered more profitable as compared to renewals. The direct implication of this was that Manzana now had a huge backlog of renewals to be cleared which seemed impossible with the current modified FIFO in place. 4) Increasing Renewal Loss A huge pile of backlogs in clearing renewals led to increasing renewal losses for Manzanas Fruitvale Branch. The renewal loss rate inceased to 30.79% in the year 1991. Out of 2081 RERUNS, Fruitvale lost 926 renewals losing out on the corresponding revenue. 5) Inefficient Labour Distribution Manzanas Fruitvale Branch has 3 underwriting teams which together serve 76 agents. However the capacity utilization across the 3 branches is uneven. Underwriting Team 3 is underutilised while Team 1 is highly loaded and hence the workload distribution needs correction for Manzanas Fruitvale Branch. 6) Salary Scheme Manzana introduced a new salary scheme called Salary/Plus in 1990 with a view to retaining senior underwriters, being courted by their competitor. However this scheme created new problems. Under this scheme every employee got an annual salary plus an extra incentive payment for each new policy written. This factor could have contributed to new policies being favoured over renewals leading to backlogs and renewal losses. This issue hence required looking into.
Capacity Utilization
Currently, Manzana uses 95th percentile of SCT for turnaround time and capacity calculation. It is a very conservative measure and may not be representative of the actual time taken on an average for processing the requests. To prove this, the capacity utilization for the complete cycle of process is calculated by using the 95th percentile of SCT as the time taken by each functional unit (such as Distribution, Underwriting, etc.) for completing a request and found to be 124.2% (Appendix-1). Mean time taken for processing the request could be an alternative measure (as it makes more sense intuitively) and when that is used for calculating the capacity utilization, it turns out to be 74.75% (Appendix-2). To check whether each individual functional unit is being either over or under-utilized we can use the WAT (weighted average time taken by each unit in processing a request). It is evident from the capacity utilizations of each unit (Appendix-3), that there is no bottleneck in the whole process, as none of them has a utilization of more than 100%. It can also be observed that the utilization level across the units is not uniform which gives room for possible idle time for few employees. UT1 is loaded to the maximum extent (97%), while UT3 team is underutilized, being loaded only 70%. Further, the Policy Writing (PW) team is utilized only 64% of its available labour time. TAT calculations: For calculating the TAT, we should consider the mean time, since 95% SCT will account for so much of leeway, while the intent is to reduce the service time. The time considered to clear out the pending processes is estimated based on the mean time for each process: Distribution 570 minutes / (4 Dc * 7.5 * 60 minutes ) = 0.3 day
Underwriting 0.89 day to clear the existing inventory and 0.59 day to clear the inventory from DC There is no wait time for the underwriters Rating 1.6 days totally The rating clerks need not wait for the inputs from the previous operations. Rating inventory - 0.2 From Underwriting 1.1 From distribution 0.3 Policy writing If the entire process is available at the policy writing desk, then there is no waiting time. However, there are cases when the clerks are waiting for the input from the previous rating desk. Hence, there is a delay. We calculate the service time, assuming that there is an incoming batch here from 3 sets of sources 1. 2. 3. 4. Inventory 0.1 + waiting time 0.1 Rating inventory 0.2 + 0.9 waiting Underwriting inventory 1.0 Distribution inventory 0.3
So, the total time taken to process the 82 existing processes is 2.6 days. We will get intermittent output at various timeframes because of balancing. Also, it takes on an average 70 more minutes to pass a new incoming RUN while 54 more minutes to process a new RAIN and 50.1 more minutes for rerun. For a RAP, since it does not involve the policy writing stage, a new RAP can be done in 1.6 days and 64.7 minutes.
Recommendations:
The recommendations are: 1. Pooling of the Underwriting Teams so as to distribute the workload more evenly across the three teams. Appendix 3 shows the calculations in detail 2. Redistribution of the workforce to 3. The calculations in Appendix-10 show
APPENDICES
Appendix-1
Request DIST Type (m/r) RUN RAP RAIN RERUN 128.1 107.8 68.1 43.2
UW (m/r)
107.2 87.5 49.4 62.8
R (m/r)
112.3 88.7 89.4 92.2
PW (m/r)
89.3 0 72.1 67
Total (m/r)
436.9 284 279 265.2
UW (m/r)
43.6 38 22.6 18.7
R (m/r)
75.5 64.7 65.5 75.5
PW (m/r)
71 0 54 50.1
Total (m/r)
258.6 152.7 185.6 172.3
No of reqs.
350 1798 451 2081
Workforce Mean times Underwriting Quantity Total Time Required Weighted Average Time Available Time (labour minutes per day) %age Utilization of labour time Underwriting Team 3 Workforce Mean times Underwriting Quantity Total Time Required Weighted Average Time Available Time (labour minutes per day) %age Utilization of labour time Underwriting (Pooled Teams) Workforce Process Mean times Quantity Total Time Required Weighted Average Time Available Time (labour minutes per day) %age Utilization of labour time Rating Clerks Process Mean times Quantity Total Time Required Weighted Average Time Available Time (labour minutes per day) %age Utilization of labour time Policy Writing Writers Process
RAPs
RAINs
RERUNs
Total
Mean times Quantity Total Time Required Weighted Average Time Available Time (labour minutes per day) %age Utilization of labour time
Appendix-4
Revenue calculations (per unit labour time) RUNs originating as RUNs originating as Process RERUNs RUNs RAPs Amount Head ($) Amount($) Amount($) Total Net Income Earned 12009090 1765144 1381856 Total Renewals processed 2081 350 274 Average Revenue per renewal 5770.827 5043.269 5043.269 Labour Time Spent per renewal 191 302.2 1073.024 Average Revenue per renewal per unit time 30.21375 16.68851 4.700052
Appendix-5
Mean times Distribution Underwriting Rating Policy Writing Mean Policy Processing Times by Departments RUNs RAPs RAINs 68.5 50 43.5 43.6 38 22.6 75.5 64.7 65.5 71 0 54 RERUNs 28 18.7 75.5 50.1
Appendix-6
6 months consolidated data for various processes 1991 data (6 Process months) RUNS Policies Processed (RUNS originating as RUNS) 350 Policies Processed (RUNS or. As RAPS) 274 Total RUNS processed 624 Late 0 RAPS (Total, including RAPs completed as RUNs) Requests Processed 1798 Late 0 RAINS (Total, including RAPs completed as RUNs) Per day values 2.92 2.28 5.20 0.00 14.98 0.00
Requests Processed Late RERUNS Requests Processed Late Total Requests Processed Late Renewals-number lost
Appendix-7
Revenues New policies Endorsements Renewals Total Revenue from different processes Total Total Comm. Total Net Income 4196 1049 3147 291 0 291 12913 903.91 12009.09 17400 1952.91 15447.09
Appendix-8
Revenue calculations (per unit labour time) RUNs originating as RERUNs RUNs RUNs originating as RAPs Amount ($) Amount($) Amount($) 12009090 2081 1765144 350 1381856 274
Process Head Total Net Income Earned Total Renewals processed Average Revenue per renewal Labour Time Spent per renewal Average Revenue per renewal per unit time
5770.827
5043.269
5043.269
645.2328
191
302.2
1073.024
185.6
30.21375
16.68851
4.700052
3.47647