Products
DataFlow collects the data and delivers the forecasts. DemandCast produces meter-level consumption forecasts. MetaCast optimises either the DemandCast forecast or the supplier's own forecast, taking the system direction into account.
Data and integration layer
DataFlow collects, cleans and prepares the data the models need, and delivers the forecasts to where they are used.
Included with the forecasting products.
Settled meter consumption and the current portfolio meter list are pulled from EPİAŞ automatically every month. Hourly consumption from OSOS and weather data are collected continuously. For meters inside organised industrial zones (OSB) that you cannot reach through OSOS, data is pulled from the OSB portals.
Missing data is filled in and faulty data is removed. Where there is no history, as with new meters, synthetic data is generated with AI.
Forecasts are submitted to EPİAŞ automatically and passed to trading platforms such as SmartPulse and Senkron in near real time.
Daily forecast and OSOS consumption reports arrive by email as Excel or CSV files. Data from different distribution regions is available in one place.
Forecast, actual consumption, imbalance volume and cost are shown on the same screen. Performance is tracked monthly across the portfolio and daily for OSOS meters.
Automates the KGÜP (finalised day-ahead generation schedule) and EAK (available capacity) notifications for suppliers serving OSBs. OSBs can also use it directly.
Consumption forecasting
Each meter in your portfolio is modelled separately, so differences in consumption behaviour feed directly into the forecast. The whole portfolio is covered, including meters without OSOS data.
2026, live operation. *The intraday effect depends on trading strategy and algorithmic trading rules.
The next day's hourly forecast is produced every day in line with the day-ahead (GÖP) submission schedule. It is sent to you, to your trading platform or directly to EPİAŞ.
Once the intraday market (GİP) opens, the forecast for each contract is revised every hour with the latest data. Revisions continue until the contract closes; the timing of submissions is set to your needs.
Which revision is sent, and when, is set by the supplier's rules. Trading decisions stay with the supplier.
Optimisation layer
Runs on top of the forecast and takes the system direction into account, that is, whether the system is in surplus (long) or in deficit (short) in a given hour. It has two modules that can be used together or separately.
Imbalance Optimisation: 2026, live operation. System direction accuracy: January–August 2026, 5,390 hours; 68.8% across all hours.
Corrects the forecasts you already use, whether they come from your own team or another provider, by learning from their past errors.
Works on day-ahead and intraday forecasts. Your workflow does not change; the corrected forecast is sent to you.
Predicts the system direction and adjusts the final forecast to minimise imbalance cost. It applies both to DemandCast forecasts and to forecasts that have been through Forecast Optimisation.
All modules together
−47.2%
In a portfolio using meter-level forecasting, Imbalance Optimisation and intraday revisions together, imbalance cost was brought down from 48 to 26 TL per MWh consumed over six months.
Packages
| Base product | Day-ahead | Day-ahead + Intraday | Day-ahead + Direction | Day-ahead + Direction + Intraday |
|---|---|---|---|---|
| DemandCast | ✓ | ✓ | ✓ | ✓ |
| MetaCast Forecast Optimisation | ✓ | ✓ | ✓ | ✓ |
"Direction" refers to Imbalance Optimisation. DataFlow is included in all packages. Pricing is set in a proposal based on portfolio size and modules.