Roadmap

This is the roadmap for further development of the FlexMeasures EMS.

Current & next

These are our ongoing developments and things we'll tackle soon (see history below). Let us know if you want to collaborate!

[Q2 2026 - in progress]  Automations, for server-side recurrent execution of jobs (forecasts, schedules, reports, plugin-specific), manageable via UI and API

[Q1 2026 - in progress] manage multiple FlexMeasures instances towards shared constraints, a light-weight CommunityEMS

[Q3 2026 - in progress] Enable participation in the aFRR market 

[Q2 2023 - in progress]  Build out the flexibility modelling, by supporting TNO's energy flexibility asset interface (S2).

Ideas

Here we collect ideas that might be interesting. Contact us if this matters to you or you want to add an idea.

[tbd] Tell local EMS / gateway what the current goal of the schedule is (e.g. "fill battery to sell later"), so their short-notice adaptations will match. 

[tbd] A general mechanism for reserving flex capacity (within the behind-the-meter schedules), which can be used for any flex mechanism (e.g. other than aFRR)

[tbd] Scheduler compatible with ShapeShifter (based on USEF flex trading protocol), to be able to provide congestion support to network companies.

Historic achievements

[Q3 2026] Integration with OpenADR events, e.g. power limitations.

[Q1 2026 - Q3 2026]] Multi-commodity: different energy sources (e.g. gas & electricity), also feeding into a shared storage if needed.

[Q3 2026] Intermediate (group) constraints in a site hierarchy.

[Q2 2026] Schedules return unfulfilled demand, e.g. soc-minima on EVs that could not be charged

[Q1 2026 - in progress] Let users provide annotations on time series (e.g. for feedback) by API and UI.

[2025 - 2026] Support adapting schedules based on earlier commitments. E.g. passive imbalance based on day-ahead purchase, or grid congestion signals.

[Q2 - Q4 2025] More practical fixed-view-point forecasting (fixed-point etc).

[Q1 2025 - in progress] Adding new VPP-focused scheduling algorithm (by TNO)

[Q2 - Q3 2025] Flex-model and flex-context can be stored on assets and are fully editable in the UI.

[Q2 2025] Multi-device scheduling

[Q2 2025] let some accounts (e.g. meter data companies, consultants) add data to other accounts.

[2024 - done] Multi-asset sites

[2024 - done] Sector coupling (optimize e-mobility and heating in one site)

[2024 - done] Multi-tenant architecture

[2024 - done] more fine-grained model of behind-the-meter dynamics & limitations (e.g. w.r.t. grid congestion, dynamic limits and soft targets) and multi-asset optimization

[Q3 + Q4 2024] UI enhancements (sensor stats, customize data graphs, pagination etc...)

[Q4 2024] White-labeling

[Q2 2024] Enterprise features (status page, audit log)

[Q1 2024] (Even) better documentation & tutorials.

[Q4 2023] Authorization model for allowing "super-accounts" to manage other accounts (e.g. for ESCos)

[2023 - done] Model & pilot heating optimization (price-based, also with heat buffers)

[Q3 2023] Scheduling algorithm for heat buffering

[Q2 2023] Dedicated algorithm for scheduling shiftable processes

[Q2 2023] KPIs support (e.g. reporting of daily totals), customizable

[Q4 2022] Custom scheduling algorithms.

[2022 - done] Model & pilot e-mobility optimization (price-based, V2G)

[Q4 2022] Better data views for sensor and assets. 

[Q2 2022] Dockerization – allow to start a FlexMeasures node quickly without local installation (and deploy in cloud environments).

[Q1 2022] Improve developer experience (CLI commands, out-of-the-box tutorial) 

[Q1 2022] Data model migration to support all kind of sensors (more than power, weather & prices), as well as units.

[Q3 2021] Support for multi-tenancy.

[Q2 2022] Allow for annotations on time series, e.g. to model processes and operator feedback.

[Q2 2021] Allow developers to write custom logic and styles in plugins.

[Q2 2021] Public release.