I worked for a utility provider, to build out a pricing engine. Gathering data, and generating a kw/hr rate, and determining when product changes occurred, etc.

I worked for a utility provider, to build out a pricing engine. Gathering data, and generating a kw/hr rate, and determining when product changes occurred, etc. We worked with a number of national utility companies. A big portion was pulling data from the different utilities and coalescing it into a common record. In addition we need to make the records versioned. I.E. if the product for the product was updated changing the kw/hr rate, we would need to record the change and increment the version. We were actually trying to get a common API and make it public like this. Being utility agnostic, but still allowing viewing of customer information, when authenticated. But we hit a lot of roadblocks. These can be narrowed down to lack of interest. The team that maintained a lot of the customer relation management (SAP). Only wanted to use vendor provided services, and nothing developed in house. There was also a lot of in the weeds type analysis. There was a utility in new york, that had a tariff tax, and candle energy tax that had to be applied based upon a zip code to the kw/hr rate. I think it's a field that is rife for disruption. Definitely beneficial, but it's a bit of a work to encourage utility companies to utilize something like this.