From meter read to approved dispatch, in one loop.
The Prelko engine ingests your load history, weather feeds and demand signals, forecasts continuously, flags the peaks that matter and proposes the actions to meet them. Your operators approve every step that touches the grid.
Four stages. One of them is always a person.
Prelko reads from your systems and returns forecasts and recommendations. It never writes to grid equipment.
Inputs
- Historical load (SCADA, historian)
- AMI and sub-meter reads
- Weather observations and forecasts
- Tariff, calendar and demand signals
Forecasting engine
- Ensemble load models per site
- Solar and wind generation models
- Probabilistic confidence bands
- Continuous re-training on actuals
Detection & recommendations
- Peak windows with lead time
- Deviation and ramp alerts
- Dispatch and balancing proposals
Operator approval
- Approve, modify or decline
- Executed in your SCADA / EMS
- Outcome logged for reporting
What each part of the engine does.
Load Forecasting
Rolling forecasts at 15-minute resolution from the next hour out to seven days, per site, feeder or portfolio.
- Probabilistic bands (P10 / P50 / P90)
- Weather-driven and calendar-aware
- Re-forecast on every new read
Peak Demand Detection
Peak windows and abnormal deviations surfaced with magnitude, lead time and confidence.
- Thresholds per asset or contract
- Deviation alerts in-day
- Lead time shown on every alert
Dispatch Recommendations
Balancing actions proposed against the forecast and routed to your operators for approval.
- Storage, flexible load, imports
- Approve, modify or decline
- Full audit trail
Renewable Integration
Solar and wind output forecast alongside demand, so net load and evening ramps are visible early.
- Behind-the-meter solar
- Utility-scale solar and wind
- Net-load ramp alerts
Grid Performance Reports
Forecast accuracy, peak capture and balance outcomes tracked over time and exportable.
- MAPE and peak error by site
- Recommendation outcomes
- Scheduled PDF and CSV exports
Reads from the systems you already run.
Prelko sits beside your SCADA, EMS or BMS rather than replacing it. Data comes in through read-only connectors or scheduled file drops, and forecasts go back out the same way.
| Source | How it connects |
|---|---|
| SCADA / historian | Read-only export via OPC UA, historian API or scheduled CSV |
| AMI / meter data | MDM export or SFTP interval files (15 or 30 min) |
| Weather | Managed by Prelko: observations plus numerical forecasts for each site |
| Renewables | Inverter or plant SCADA output, installed capacity registers |
| Outputs | Web console, REST API, CSV and PDF exports, email alerts |
Weather-aware
Temperature, humidity, cloud cover and wind at each site.
Signal-aware
Tariff periods, holidays, shifts and demand-response events.
Self-correcting
Every interval scored against actuals and fed back.
Human-approved
No dispatch leaves Prelko without an operator's decision.
Bring a month of load data. Leave with a forecast.
In a demo we run Prelko against a sample of your own history and show where the next peaks sit.