Bat Case Report

Executive abbreviation lap is a technology that sells financial softw be to individuals and organizations. cricket bats success had attracted a enactment of competitors. BAT differentiated itself by committing to disembarrass tech victuals for the life of the product. BAT started its prefigure totality trading operations in 1987 with 6 technicians which grew to everywhere a 100 technicians by 2002. However, the augur center has been under pressure in terms of long delay times for nodes. Such poor run was beginning to take its cost on the comp alls reputation.We recommend that BAT should implement the troubled steer proposal in order to improve guest aid and the companys bottom line. We understand that free technical concomitant is BATs value proposition and central to its business model, un little we allow show with our analysis why this is the best approach to follow. Qualitatively, 1. BAT will still maintain free software documentation with prompt give chas e. unfluctuating track will only create market segmentation. Customers on round top of the market pyramid who argon readily willing to pay asshole be tapped. . quick bounce back will convert the call center from a cost center into a profit center. With the revenue enhancement enhancement organism generated out of Fast Track calls, BAT can staff the call center with much technicians to improve help levels for standard callers. Current fact BOP Team 1 is consists of 8 customer renovation technicians and the arrival rate of customers is 22. 5 customers/hour. The norm time to deal with unitary customer is 18. 2 snatchs. Therefore, the service rate capacity per technician is 3. 2967 customers/hour.After running the Steady-State, Infinite message Queues model, the average waiting time of customers is 0. 14979 hour, which equals to about 9 minutes and thither will be in average 3. 37 customers waiting in the queue. Please refer to Appendix 1 for details. Since the arrival r ate and the service capacity rate cannot be shortened, increasing number of technician is the only counsel to shorten the average waiting time down to less than 1 minute. We ran the model again by adding more technicians one by one, and we put up that the average waiting time decrease down to about half(a) minutes at 11 technicians.Please refer to Appendix 2 for details. Fast Track We considered different staffing plans and ran Queuing Macro for average wait time. We considered adding servers and conserveing one queue, and other scenarios with dedicated Fast Track Servers. We ran Queuing Macro under five different staffing scenarios (Please note that we have dedicated Fast track servers in Scenarios 4 and 5) Scenario No No of Standard Servers No of Fast Track Servers 1 8 0 2 9 0 3 10 0 4 7 1 5 7 3 The following results were observedRefer to Appendix 3 for spreadsheet calculations. As observed in the data, Scenario 2 and 3 succeed in keeping Average waiting for track customers to less than 1 minute. Scenario 2 uses less number of resources. Scenario 2 (9 technicians) is the best staffing level, without dedicated servers for Fast Track. Economics of Fast Track Weve now established that Scenario 2 and 3 keep average wait time to less than 1 minute to help make for the Fast Track Guarantee. In Scenario2, The average server utilization is 75%, which is an adequate level.The additional yearly bread revenue that can be obtained ranges from $54,325 to $376,300 depending if 10% or 40% of customers become Fast Track customers. In Scenario 3, The average server utilization is 68%, which is not as near(a) as in the previous scenario. The additional yearly net revenue that can be obtained is also less attractive, ranging from $1,325 to $323,300. Also considering a scenario where we keep 11 technicians, The average server utilization decreases to 62%. The additional net revenue/loss that can be obtained per year is now not so attractive, ranging from a net loss of 51,675 to a net revenue of $270,300. Scenario 2 (9 Servers) put forwards the best revenue opportunities. Free Service for Fast customers waiting over 1 minute. We did some simulations to see what happens if BAT offers Fast Track service, charging $2 / minute, but giving the service for free if the customer waits over 1 minute. According to the Queuing macro, with 1 additional server there is a 30. 7% chance that any given customer (whether Fast Track or Standard) will wait more than 1 minute.Considering that 10% of these customers are Fast Track individuals, we obtain an arrival rate of 30. 7% * 10% * 22. 5 customers/hr = 0. 69 customers / hr. On the other hand, considering that 40% of customers are Fast Track individuals, we obtain an arrival rate of 30. 7% * 40% * 22. 5 customers/hr = 2. 7 customers / hr This means that, on average, the number of Fast Track customers who will wait over 1 minute ranges from 0. 69 / hr to 2. 7 / hr. In other words, roughly anyplace from 1 to 3 Fast Track customers per hour will be waived from the Fast Track fee.As seen on Appendix xxxxx (Table 4), this represents a loss of annual revenue ranging between $2,197 and $8,786. However, despite declines in revenue, this fee-waiver option will sure enough improve customers experience and customer loyalty. Therefore, we recommend Scenario 2 (hiring 1 additional server) in order to implement Fast Track, charging $2 / minute and including the fee-waiver option if waiting time exceeds 1 minute. Service Contracts vs ease up per call There are several aspects to consider when deciding if BAT should offer service contracts or just pay-per-call.Firstly, offering charged technician support goes against BATs original value proposition, however, pay-per-call maintained free service option. Also, pay-per-call could differentiate itself from the industry norm. It is easier for customers to accept. BAT has been offering free technician service to support its product since the founding of the c ompany. Free technician support is part of BATs value proposition to customers. While charging pay-per-call service is already deviating from BATs core value, following the industry norm to offer service contracts could negatively impact the value proposition of BAT.Secondly, offer service contracts require higher(prenominal) investment caused by increased volume of customer calls. With pay-per-call service, customer will only call technician support when they are encountering problems that are urgent and customer can not only solve by themselves in a timely fashion. And since the call is charged on the minute basis, customers are more likely to keep the call short. Whereas, with service contracts, customers could call technician support with any question, and tend to stay on the line longer that they actually indispensableness to.There will be an increase of number of phone calls if BAT decides to offer service contracts. The increase of number of phone calls and prolonged time fo r separately phone call will require BAT to invest intemperately in terms of human resource and training. Overall, in terms of scotch value and flexibility in operation, the Pay-per-call option is more preferable than service contracts. Pay-per-call requires less investment in human resource and training, also it has the flexibility to not charge customer, if their waiting time exceeds 1 minute.