SUPPORT CALL US AT 650-479-5641 DOWNLOAD

Insights and Updates

Read the HarperDB teams’ thoughts on database technology topics such as SQL, NOSQL, Schema-less architecture, IoT, Big Data, and more

Using HarperDB to Integrate Insurance Data

Posted by Jacob Cohen on October 16, 2018
Jacob Cohen
Find me on:
 
e2value blog-1
*e2Value UI powered by the HarperDB database (Street addresses blurred out for privacy)
 
You never know where you’re going to meet your next business connection. Fred (COO) and Stephen (CEO) met on an airplane years ago and founded HarperDB years later. This year, we met Todd Rissel, CEO of e2Value, at the IoTBuild conference in Santa Clara, CA. A little less of a chance encounter than a plane, but an introduction nonetheless. 
 
At some point during the conference Todd and I got to talking about his business, what data they rely on, and where it all lives. At this point it was just friendly banter of two neighboring exhibitors. We also ribbed each other over the Orioles versus the Red Sox, but I’m not going to bore you with that since the Orioles are clearly the superior team. Over the course of the conference I came to the realization that Todd had accepted long ago: home insurance data is siloed. So siloed in fact, that if you want to get the full picture of what’s going on in a home you need to check many different systems. No one had ever integrated them, and not for lack of trying. Now our conversation changed from friendly banter to business. Could HarperDB solve the home insurance data problem?
 
After returning home from the conference, HarperDB started working with Todd to understand his vision of the future of the home insurance data market. e2Value is the leader in the web-based property valuation market, but their vision doesn’t stop there. Todd wanted to see all insurance data living in a single database where users can log in and gather everything they need for a single source of truth. But it can’t just be for today, the database needs to be future proof. IoT is on the horizon in home insurance and they need a database that will be ready to collect data directly from IoT devices living in a home. HarperDB is the perfect foundation for this application.
 
Once the decision was made to build this unified database, the e2Value team began working with HarperDB to develop their unified database. The first phase consisted of integrating with the e2Value Pronto valuation software API. Data is requested to be entered into the database through an API call via a custom UI. Once this request is received the application will pull data from all silos and store it in the new database. While the development seemed daunting at first the team was impressed with how quickly they were able to get external data written to HarperDB. What made this so easy was HarperDB’s Dynamic Schema. Once tables were created, the development team simply pointed the API at the HarperDB table and pressed go. On write, all Pronto fields were immediately available in HarperDB, and as an added bonus, they were fully indexed as well. 
 
The team saw a big win early by integrating their first data source, but there was still more to do. The next phase of the project involved integrating with Pruvan Direct, an application designed to help organization source, manage, and capture field data. The Pruvan API uses different technology than e2Value, but the team saw similar results in how quickly they were able to get data into HarperDB. Once the connection was established between the two applications, data began flowing quickly and the HarperDB Dynamic Schema proved to accelerate development once again. 
 
Data from these two sources are both related to homes, but that’s pretty much the extent of their similarities. e2Value data contains valuation data such as replacement costs, square footage, structural details, and maps. Pruvan contains field monitoring data such as photos, tasks, observations, and other notes. HarperDB consumes all of this data with ease, enabling Todd and e2Value to achieve their goal of a unified insurance database where users can gather the full picture of their property through a single interface, and that is IoT ready.
 
I guess what we’ve learned here is that the next time you’re at a conference and you see a company with a purple dog logo and some t-shirts, you should stop by and say hi! We may just be able to help you achieve your data goals. 
 
Want to learn more about this solution and how HarperDB can help you unify your data? Schedule some time to chat with us!

Schedule a Call
 

Topics: Use Cases, Dynamic Schema, data warehouse


Comments: