With local-based systems that we've used for decades, our work resided on our computers. The data we upload through the proprietary and third-party claims solution programs is limited to only those estimates we are bound by contractual relationships for specific insurers. Typically this data can represent a different total percentage to each organization. With local based systems, data is only accessible when an insurer or IP requires an upload.
Today, the aggregation of the data producing scorecards is a common occurrence for any one involved in a DRP relationship. How often is this data used to let us know how we are doing? After my presentation at CIC a couple of IP reps wanted to discuss what was presented. The first comment was, "We just sell the data, we aren't responsible for how it is used." This was the same comment that I had heard when the notorious bumper prompt was put back into an estimating system after taking two years to remove it.My analogy was, "If you are bartender and you continue to serve drinks to a customer after you know he can't drive home safely, and he kills/injures someone, you can be held responsible."
They pointed out that supplying data wouldn't kill anybody. While it may not kill repairers, it could kill or irreparably harm their business. If a repairer ends up losing business, having customers steered away, which cuts off the supply of work, that's as close to killing a business as you can get.
The IP reps pointed out that when you go to Costco or Safeway and swipe your card they know everything about your purchasing habits.
While that's true, I've never attempted to check out and have the cashier tell me I need to buy another dozen eggs and some other specific product, or I will not be allowed to shop there any longer.
These situations are different because the grocery store's intent of collecting data is to enhance my buying experience and tell manufacturers what's selling. That's not the intent of the IP scorecards.
With "cloud computing" all the work product is stored on Internet servers and essentially uploaded during the normal saving of the estimates/repair orders. According to the current terms of usage and data policies, the IPs can do just about anything they want with that data.
That is unacceptable for our industry's future. Since this article is due to be published prior to the next CIC meeting in July, I am hoping it will rekindle the need to move forward with the suggested task force that came from the last meeting.
There are three basic principles that our industry must demand as we move forward with "cloud computing" business applications. First, the only current choice at this time is to not subscribe to the systems. This is not an acceptable solution. There is not often a choice whether you can or cannot do without a specific system.
Second, the control of what estimates/repair orders are used by anyone other than the system user must be controllable on a profile-to-profile basis. And third, each estimate/repair order must have the ability to be "de-flagged" for aggregation regardless of the profile it was written for. These options provide the control the user of the software should have while still allowing the usage of the repairer's business data by previously approved agreements.
This is your private business – not anyone else's. Today is the right time to ensure it stays that way.
Contact info: [email protected]
