Production plans

Chapter 1.2.1

Production plans for Polish grid operators, sent automatically

Every generator in Poland with a power generating module of 200 kW or more must submit an operating plan (plan pracy) to the grid operator: how much energy it will feed into the grid in every hour of at least the next 9 days. Leysa prepares and submits these plans automatically. The production model is fitted to each individual farm, the weather forecast refreshes daily, and the plan reaches the operator’s platform with no portal logins and no spreadsheets.

Book a call Energy at Leysa

Offer

Who it’s for: owners of PV farms and other type B, C and D power generating modules in Poland, including foreign investors, renewable aggregators, and companies that plan operation of many installations as a technical operator.

The problem: the plan has to be submitted for every hour at least 9 days ahead, weekends included, and updated whenever the weather changes or downtime is planned. Typing it into a portal by hand or using a fixed spreadsheet profile takes time and drifts away from reality, and since 2025 operators compare plans against meter readings.

What Leysa delivers:

  • an individual production model for each farm: clear-sky physics calibrated on your installation’s output and weather data,
  • forecasts from weather data up to about 20 days ahead, with accuracy levels (2, 5 and 20 days),
  • daily generation of plans about 4 weeks ahead, well beyond the required 9 days, weekends and holidays included,
  • an individual energy profile for each farm,
  • maintenance on subscription: submission monitoring, model recalibration and adjustment to changes on the operator’s side.

Regulations that require operating plans

The obligation does not come from a single act but from several layers of rules, from EU law down to the grid code of a specific operator.

  • Commission Regulation (EU) 2017/1485 (SO GL). Article 40(5) requires the TSO to agree the scope of data exchange with DSOs and significant grid users. Article 49 covers schedules and production forecasts.
  • “Scope of data exchange for planning and operating the KSE” (Zakres wymiany danych dla potrzeb planowania pracy i prowadzenia ruchu KSE). A PSE document approved by the President of URE (current version of 19 February 2021). It defines the data that generators with type B, C and D modules must provide.
  • Commission Regulation (EU) 2016/631 (NC RfG). Divides modules into types. Type B is a module connected below 110 kV with a capacity from 200 kW to less than 10 MW. Type C covers 10 MW to less than 75 MW, and type D is 75 MW or more, or a connection at 110 kV and above.
  • IRiESP and IRiESD. The operators’ grid codes turn these obligations into concrete rules: which values, how often and through which channel. Since 1 January 2021, generators with type B and C modules submit plans to their DSO’s platform.
  • TSO–DSO announcement of June 2025. The operating plan must reflect planned self-curtailment, e.g. switching a farm off at negative prices. Since 8 July 2025 PSE has used this information when managing the KSE and when redispatching renewable sources.

What an operating plan contains

Based on the rules of TAURON Dystrybucja:

  • net available capacity, maximum and minimum, over a 5-year horizon, updated for maintenance or downtime,
  • planned net generation for every hour, for at least 9 days, to 0.001 MW,
  • for installations with on-site consumption: the surplus fed into the grid after covering the plant’s own needs,
  • proposed outage plans, when needed.

How the operator checks plans

Since 14 April 2025 TAURON Dystrybucja has compared plans with meter readings. If 0 MW is planned for a given hour, the energy fed into the grid should be 0, with a tolerance of 5% of available capacity. If more than 0 MW is planned, the farm should feed something into the grid in that hour. The most common errors the operator points out are plans shorter than 9 days (especially at weekends), no updates after a weather change, and missing self-curtailment. For persistent violations the DSO calls on the owner or technical operator to stop them and takes further formal steps.

Platforms, formats and deadlines differ between operators. Before implementation Leysa checks the current grid code of the relevant DSO.

Who takes part in the process

  • Generator (owner of the PGM). Responsible for the plan, even when its preparation is outsourced. Knows about planned maintenance and decisions to switch off at low prices.
  • Technical operator. A company that prepares and submits plans on the generator’s behalf. The DSO addresses its remarks to it when plans are incorrect. Leysa can take this role.
  • DSO. TAURON Dystrybucja, PGE Dystrybucja, Enea Operator, Energa-Operator, Stoen Operator and smaller local operators. It receives plans through its platform (at TAURON Dystrybucja this is PGB, with file import and an API), compares them with meters, aggregates them and passes them on to PSE. It also issues redispatch orders and can control the installation remotely through its SCADA system.
  • TSO (PSE). Collects data from the whole country, plans operation of the KSE and decides where to curtail renewable output when there is too much energy in the system.
  • President of URE. Approves the scope of data exchange and the operators’ grid codes.

An operating plan for the DSO is not the same as a trading schedule submitted by the supplier or the balance responsible party. The operating plan serves grid security, the trading schedule serves market settlement. Both can use the same production forecast.

Advantages over other solutions

The usual alternatives are typing plans into the operator’s portal by hand, a fixed spreadsheet profile, or a generic forecast from an external provider, computed for a region rather than for a specific installation.

  • A model of one farm, not a regional average. Each installation has its own calibration of its output. Measured effect: about 30–40% lower daily error than “same as yesterday” or a climatological profile.
  • Error stated as a number. Before deployment the model is tested and compared with simple reference methods. You know what to expect before plans reach the operator.
  • Downtime does not spoil the model. All shutdowns and outages are filtered, labelled and taken into account.
  • Plan and farm control from one provider. Leysa also builds systems that stop farms at negative prices. The same self-curtailment information can feed into the operating plan, as the TSO–DSO announcement requires.
  • Submission with a margin. Plans about 4 weeks ahead, sent daily and checked on the operator’s side, so a weekend or holiday leaves no gap.
  • In production. The system is not a prototype: it sends plans to the operator’s API every day for many clients.
  • Direct contact with the engineer. You talk to the person who wrote and maintains the model, not to a support desk, in English or Polish.

How to start

  1. Call. About 30 minutes, in English: number and capacity of installations, grid operator, current planning method.
  2. Data. Production history (ideally the last year or longer), location and capacity of the installations, access to the DSO platform.
  3. Calibration and backtest. A model for each farm and its measured error on historical data, before you decide on deployment.
  4. Automatic submission and maintenance. Daily plans, monitoring and recalibration.

More on farm control and price forecasts: Energy. The implementation: Case studies.