Independent product case study / Public-data intelligence
Voltline
Voltline combines the latest available EIA-930 submissions for Texas with monthly residential aggregates for every U.S. state and D.C., while explaining why official ZIP-level electricity usage or a single ZIP rate is not available.
01 / Brief
EIA-930 exposes useful hourly balancing-authority submissions, while retail-sales data supports monthly state aggregates. Neither source provides household or ZIP-level usage, so the product must make scope as visible as the numbers.
The product supports someone checking Texas hourly movement, comparing a state’s monthly residential price and sales, or asking whether a ZIP can support an official electricity claim—not an operator or a household-bill estimator.
02 / Architecture
Each stage has a bounded responsibility. The interface preserves source context and leaves the final judgment with the person using it.
The server asks EIA for a four-day ERCO window containing demand, day-ahead forecast, net generation, and total interchange.
EIA API v2 primary · bounded four-day window · legacy fallback · 15-second timeoutRows are checked for a usable data array and finite numeric values, then sorted using their reported timestamps.
Invalid or absent demand ends the request with a visible errorDemand sets the current reporting hour. Forecast is matched to that exact timestamp; generation and interchange use their latest numeric observations and keep their own timestamps visible.
Latest demand + matching forecast + latest available adjacent signalsThe interface checks, in order, proximity to the displayed-window peak, forecast variance, and hour-over-hour movement before returning a neutral recent-range state.
95% of recent peak · 4% forecast variance · 5% hourly movementThe view shows the source, reported period, observation count, geographic level, limitations, and direct routes to official EIA documentation.
Hourly and monthly freshness · source links · explicit non-alert and non-household disclaimers03 / Product decisions
Tradeoffs made visible
The context labels are fixed thresholds over retrieved values. They are easy to inspect and challenge, but they do not forecast conditions or infer grid reliability.
Forecast is compared only when it shares the latest demand timestamp. Generation and interchange may lag, so their own latest timestamps remain visible instead of implying alignment.
The route allows a ten-minute shared cache with stale-while-revalidate support. That lowers repeated upstream load while reinforcing that this is an hourly public view, not operational telemetry.
The ZIP view validates the five-digit format, then explains that EIA does not publish consumption or average price by ZIP. It offers supported state and service-territory alternatives without implying a household, tariff, or utility match.
Failure is a designed state
The route attempts the bounded EIA API v2 feed first, then a legacy EIA dashboard fallback. If neither is usable, it returns a no-store error; the interface clears stale results, announces the failure, offers retry, and links to EIA.
Voltline stops rather than filling the dashboard with inferred values. Forecast, generation, and interchange can remain explicitly unreported without invalidating a valid demand observation.
The client prevents concurrent loads and ignores responses from superseded requests, keeping late network responses from replacing newer interface state.
04 / Evaluation
This is the evaluation surface documented by the implementation—not a claim that every target has already been met.
Check that the latest reported hour and every adjacent-signal timestamp remain visible, and that caching never masquerades as real-time telemetry.
Exercise malformed arrays, nonnumeric values, missing demand, and individually missing forecast, generation, or interchange observations.
Verify sorting, exact forecast alignment, independent latest timestamps, recent-history ordering, and boundary behavior across reporting dates.
Test every threshold and its priority order, then confirm the copy never upgrades a pattern into an alert, forecast, or reliability claim.
Verify every state plus D.C., state-versus-U.S. comparisons, aggregate per-customer math, and the ZIP view’s refusal to infer household usage, tariffs, or a unique utility.
05 / Provenance
The route retrieves EIA-930 region data for ERCO and exposes the official balancing-authority dashboard as the primary verification path.
The state explorer uses monthly residential sales, customer counts, and average retail price as state aggregates; recent months can be preliminary and revised.
EIA explicitly states that it does not publish electricity consumption or average retail price by ZIP Code, which is why Voltline does not manufacture a ZIP estimate.
Numeric validation, chronological ordering, signal selection, the 36-observation history, and cache headers are implemented locally in the site’s read-only API route.
Near-peak, forecast-variance, and hourly-movement labels are deterministic presentation logic—not EIA conclusions and not a model-generated forecast.
Implementation note
This case study was checked against the current Voltline client and /api/grid-live implementation on this date. Live values, upstream availability, and EIA revisions can change after the review; the product displays its own latest reported and retrieval context when run.
See the system under real conditions