Green Button and the standardized-data problem
Green Button promises interoperable energy data. In practice, ingestion is where programs stall. A look at how we normalize XML, PDFs and portals into one model.
Green Button was designed to make energy usage data portable and machine-readable. It is a genuine step forward, but the moment you run a real program across many utilities and customers, ingestion becomes the bottleneck: mixed XML profiles, partial intervals, PDF-only accounts and inconsistent metadata.
One model, many sources
MartinAI normalizes Green Button XML, uploaded PDFs and portal exports into a single utility intelligence model. Whether a customer arrives with a clean Download-My-Data file or a stack of scanned bills, the output shape is the same, and it is validated against tariffs and cross-field relationships on the way in.
- Green Button XML, both Download My Data and Connect My Data profiles
- PDF and scanned bills via the extraction core
- Bulk uploads and self-serve customer onboarding
Standardized in name is not the same as standardized in practice. The job of an intelligence layer is to absorb that variety so your program never has to.
How to get your energy data in Ontario: a plain guide to Green Button
Ontario law now requires utilities to hand over your energy data in a standard, machine-readable form. It is called Green Button. Here is what that means in plain terms, how to get your data (or your customers' data) automatically, and what you can do with it.
Getting clean data out of utility bills: manual entry vs OCR vs reasoning
Three ways to turn a stack of utility bills into usable data, and why the difference shows up the moment you scale past a handful of accounts. A practical comparison for anyone tired of re-keying bills.