![]() |
|
07.06.09 ServiceBench: Data Hub For All Supply Chain Needs By James Taylor I saw ServiceBench when I presented at the Warranty Chain Management Conference and got a chance to get a more detailed presentation just recently. ServiceBench is aimed at the Service Supply Chain and is now part of NEW (who also presented at the conference). The service supply chain is often very complex because of the number of entities that are involved (i.e. retailer, service provider, manufacturer, TPA) and consumers often find it hard to determine where to go for help or service. It can also be very hard to determine who is responsible for the cost of the repair. Once you figure out that a service call is necessary then you have to select someone to do the service, find the parts, get the customer, servicer and parts all in the same place at the same time etc. Everyone is trying to improve customer service, reduce their costs and simplify the business process for service providers. ServiceBench creates a data hub for this information for service, repair, delivery, warranty, extended warranty. ServiceBench is a single internet-based system with access to a common set of data. It is designed to resolve more problems on first call and provide better and more complete data. This is all based on a common platform for Service Management and delivers what they call Service Intelligence across the products. • Service Call Management A subset of CRM call center functionality focused on service calls. Handles event capture, dispatch and ServiceLocator. Typically integrated with a major CRM system. • Field Service Management Contracts, surveys based on statistical model developed for each, territory management, coverage analysis etc. • Parts Management A lightweight product to make it easy to order parts from within the same portal. NEW is in the process of extending this to create a virtual inventory management product to handle shipping/ordering parts from one of several locations etc. • Claims Management The core product capturing registrations, claims, returns, payments. Claims is often the first module and drives adoption. Claims data is often the cleanest and most complete. As a result it drives a lot of analytics in the service supply chain.
I am not going to try and describe all the capabilities of ServiceBench but will focus on the analytics it provides - service analytics. All the transactional applications run on a common Oracle database. Lots of data is collected about service calls and service call / claim quality. Most customers are focused on a weekly analysis cycle when the collected data is transformed for analysis. Everything is customizable for a customer but typically customers focus on financial, performance and quality analysis. Performance analysis might include part or service provider performance for example. Analytics often cover fraud warnings, travel costs, labor costs, parts costs, claim trending and internal process improvement. Customers define KPIs and can see the trends across periods - percentage of claims with a bad address, for example. Dimensions for slicing are defined based on the customer's data e.g. product line or geography. The whole environment is very warranty and service focused and can be localized to a specific role. Besides this general analysis there is also a move to support pay for performance in the service supply chain. Pay for performance can be complex in terms of how service providers are rewarded. Others, like NEW itself, route more work to high quality service providers, using the analysis to identify those service providers who should get more work. While customers are not typically changing behavior from analytics directly they are updating data and rules based on analytics - the beginnings of a true analytic feedback loop. ServiceBench also collects business rules as part of the setup. Some rules are only changed by the administrators e.g. those to keep data clean. Customers can change some rules, particularly thresholds like time allowed to submit claims. ServiceBench uses a proprietary rules engine and some coding to provide this environment. Continue reading this article. About the Author: VP of Product Marketing with a passion for the technologies of decision automation. 15 years designing, developing, releasing and marketing advanced enterprise software platforms and development tools. Across the board experience in software development, engineering and product management and product marketing. http://www.edmblog.com |
|
| ||||||||||||||||
| -- SCMnews is an iEntry,
Inc. publication -- iEntry, Inc. 2549 Richmond Rd. Lexington KY, 40509 2009 iEntry, Inc. All Rights Reserved Privacy Policy Legal archives | advertising info | news headlines | free newsletters | comments/feedback | submit article |