Grid and market data
Describe electricity-system conditions and timing context.
Resolution, completeness and availability can vary by market and bidding zone.
Platform
From changing energy conditions to operational decisions.
EnvoPulse is designed to combine grid, weather, Earth-observation and site data in one workflow for planning flexible demand and documenting results.
Current stage: In development. Status labels are staged from the MVP baseline and require final reconfirmation before go-live.
Observe changing conditions
Predict useful operating windows
Act within site constraints
Measure local behaviour
Prove inputs and outcomes
One workflow from signal to evidence.
The platform is organized around a practical cycle: observe changing conditions, predict useful operating windows, act within constraints, measure what happened and prove the result with traceable evidence.
Platform workflow: Observe, Predict, Act, Measure and Prove.
-
01 Observe
Combine grid, weather, Earth-observation and site inputs into a readable operating context.
-
02 Predict
Estimate periods that may be more suitable for flexible demand and renewable-aware operation.
-
03 Act
Turn signals into recommended schedules or integration-ready actions within agreed limits.
-
04 Measure
Compare expected and observed site behaviour using meters and connected assets where available.
-
05 Prove
Document sources, assumptions, decisions and measured outcomes for traceable reporting.
Data foundations have distinct roles.
EnvoPulse combines approved source families without presenting volatile product names, API versions, latency promises or internal pipeline details as public commitments.
Weather and solar inputs
Support historical context, model development and renewable-aware decisions.
NASA POWER is not presented as a complete 6-24 hour forecast feed.
Earth-observation context
May support selected diagnostics, provenance and very-short-range context.
Meteosat, Sentinel and CAMS roles remain contextual unless site evidence supports a stronger method.
Site measurements
Provide the primary evidence of local operation and measured outcomes.
Meter, BMS and asset availability depend on permissions, protocols and data quality at each site.
Capabilities are labelled by maturity.
Each public capability is paired with a status and limitation so visitors can distinguish current development from planned or site-dependent functions.
Carbon Intensity Index
Prototype / preliminaryA signal for reading carbon-related energy conditions.
Combines source context and internal methodology for decision support.
Published without quantified model-performance claims until a reproducible dossier exists.
Renewable and carbon forecasting
In developmentForecast-oriented context for changing renewable and grid conditions.
Uses approved source families and internal modelling in development.
No public performance metric or product horizon is stated.
Carbon-aware scheduling
In developmentRecommended timing for flexible demand.
Maps signals to schedules or integration-ready actions within operating constraints.
Not presented as operational dispatch available at every site.
Curtailment Shield
In development / targetA target capability for using flexible load when renewable availability would otherwise be constrained.
Designed for pilot validation with measured load-shift events.
No recovery, financial result or emissions result is promised.
Asset and meter integration
PoC / in developmentConnection to site evidence and controllable assets.
Works by design without proprietary client hardware.
Hardware-independent does not mean automatic or no-effort integration.
PV diagnostic support
Prototype / in developmentSupport for identifying where photovoltaic operation may need review.
Uses selected context and benchmarks during validation.
Not a formal diagnostic service and no detection performance is promised.
Energy and emissions evidence
In developmentTraceable inputs for energy and emissions assessment.
Connects source references, assumptions, site data and reporting logic.
Supports assessment and reporting; it is not a formal assurance statement or audit opinion.
Tamper-evident audit trail
Planned / in developmentPlanned event traceability for decisions and evidence records.
Depends on architecture, security review and deployment evidence.
Not positioned as immutable regulatory assurance.
Capability status matrix.
The matrix records the minimum evidence expected before stronger public claims or broader availability language can be used.
| Capability | Status | Minimum evidence |
|---|---|---|
| Carbon Intensity Index | Prototype / preliminary | Internal method, API logs, backtest package |
| Renewable and carbon forecasting | In development | Model definition, true forecast inputs, validation dataset and metrics |
| Carbon-aware scheduling | In development | Protocol PoC, simulation, pilot evidence |
| Curtailment Shield | In development / target | Pilot design and measured load-shift events |
| Asset and meter integration | PoC / in development | Supported protocols and site-specific integration matrix |
| PV diagnostic support | Prototype / in development | Benchmark and false-positive / false-negative analysis |
| Energy and emissions evidence | In development | Methodology, data lineage and reviewer acceptance |
| Tamper-evident audit trail | Planned / in development | Architecture, security review and deployment evidence |
Integration is site-dependent by design.
The platform is designed to work without proprietary client hardware, but every deployment still depends on local permissions, source access, meter availability, protocol support, data quality and agreed operating constraints.
Technical questions.
No. EnvoPulse is hardware-independent by design. Practical integration still depends on site access, permissions, available meters, protocols and data quality.
No. Earth-observation and atmospheric data can provide context, diagnostics or provenance. Site-level outcomes require local measurements and a documented method.
No. Public capabilities are labelled by maturity. Scheduling and integration functions are being developed and validated through controlled use cases.
Reporting is designed to keep source references, assumptions, actions and measured site data together, so reviewers can understand how an assessment was produced.