Reference · built on requestOperator by FibricEnergy & demand

Carbon Window

Flexible building loads and EV charging shifted into the hours the grid runs cleanest, with the estimate recorded for your reporting.

Request accessPricing ↗

About

The grid is not equally clean at every hour, and some of your load does not care when it runs. This operator reads hourly net generation by energy source for your balancing authority from EIA's Hourly Electric Grid Monitor, a marginal emissions forecast where a feed covers your grid, and the flexible loads you declare: pre-cooling, water heating, purge ventilation, and vehicle charging.

It proposes moving each load into the hours the mix or the forecast marks as lowest carbon, inside the window you allow. A person approves. The receipt records the hours moved, the series used, and the method behind the estimate, so the number can be cited later.

This is a reference listing. It documents what Fibric would read from Carbon Window and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Hourly net generation by energy source for your balancing authority from EIA's Hourly Electric Grid Monitor, published on a one- to two-day lag
  • Hourly demand, available about one hour after the hour ends, and the day-ahead demand forecast from the same EIA route
  • A marginal emissions forecast where one covers your grid, such as WattTime or the Carbon Intensity API for Great Britain
  • Flexible load schedules on the building management platform: pre-cooling, water heating, and ventilation purge windows
  • Charging sessions and the charging profile each station is running, through OCPP or the ChargePoint web services
  • The requested energy and anticipated departure time an EV sends over OCPP 2.0.1 with ISO 15118, where stations support it

Proposed actions

  • Target capability: propose moving a flexible building load into the hours the fuel mix or the forecast marks as lowest carbon
  • Target capability: propose a charging profile under OCPP Smart Charging that slows a station in high-carbon hours and restores it before departure
  • Target capability: propose a ChargePoint shedLoad for a station group across the highest-carbon hours, with a timeInterval
  • Target capability: propose the carbon estimate for each shift as a record: hours moved, the series read, and the method
  • Target capability: propose a monthly summary of shifted energy and estimated avoided emissions for your reporting

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Pre-cool on the midday solar

    The platform's pre-cooling window is moved into the hours EIA's mix shows the most solar for your balancing authority, with the afternoon setpoint held by the building's own controls.

    With BACnet / IP, Grid Demand & Prices

  • Fleet charging after the evening ramp

    Depot stations on OCPP are given a Smart Charging profile that slows charging during the hours the WattTime forecast marks highest, and restores full rate before each van's departure time.

    With Open Charge Point Protocol (OCPP), WattTime Data API

  • Sites in Great Britain

    For a site outside EIA's coverage, the Carbon Intensity API forecast drives the same proposals, with a ChargePoint shedLoad on the station group during the dirtiest half-hours.

    With Carbon Intensity API, ChargePoint Web Services API

Requirements

  • A free EIA API key and your balancing authority code
  • For same-day decisions, a forecast feed for your grid, or a pattern built from EIA history that you have accepted in writing
  • A building management platform over BACnet/IP, or a charging network over OCPP or ChargePoint, with the flexible loads named
  • A window per load: earliest start, latest finish, and the floor it must not cross
Authentication
It holds no account on your grid operator, platform, or charging network. EIA is read with your free API key; forecasts, buildings, and stations through the signal and connector credentials you attach.

Limits

  • EIA's generation-by-source data lags one to two days. Same-day shifts rely on a forecast feed or on a pattern you accept.
  • The estimate uses the average mix unless a marginal feed is attached. The two methods give different numbers, and the receipt names which.
  • An EV that must leave before the low-carbon window is charged on time. The departure constraint wins every time.
  • It buys no certificates, retires no credits, and files no report. It records an estimate you may cite.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Carbon Window ↗

Questions and answers

What is put in front of a person for approval?
A shift per load: the original window, the proposed hours, the series and hours it read, and the estimated difference with its method named. For charging, the profile and the departure times it respects. Approve, edit, or decline.
What is recorded for each shift?
A receipt: the load or station, the windows before and after, the EIA or forecast data and its timestamps, the estimate and method, who approved, and the write outcome. The previous window stays on the receipt.
Does a forecast update change anything by itself?
No. A new forecast produces a revised proposal. Loads move and profiles change only after approval, once; nothing is re-applied when the data refreshes.
Ask about Carbon Window

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy