This section proposes a commitment schedule generation method. Net load, defined as system load minus available renewable generation, directly reflects the residual demand that is supplied by conventional units. Therefore, days with similar net-load trajectories usually have similar peak-valley patterns, ramping requirements, reserve requirements, and unit commitment structures. This provides the basis for reusing historical commitment schedules for a target day.
Based on this idea, we first construct a historical commitment schedule library from historical UC cases, where each historical net-load trajectory is paired with its feasible commitment schedule. Before retrieval, identical or near-identical commitment schedules are merged in the historical library to remove redundant candidates. For the target day, the Top-K most similar historical days are retrieved according to the standardized net-load trajectory, and their commitment schedules are used as candidates. The candidates are then evaluated by a verification model with fixed binary variables, and infeasible or high-cost candidates are further adjusted through a limited-perturbation repair model. Therefore, given the load demand and available renewable power sequences of the target day, the proposed method outputs a feasible hourly unit ON/OFF schedule by reusing and adapting historical unit commitment patterns rather than generating binary commitment variables from scratch.
3.1. Construction of the Historical Commitment Schedule Library
We use to denote the set of historical days and use to index them. For each historical day , the load demand and available renewable power are input into the full UC model to obtain the optimal unit ON/OFF statuses, start-up and shut-down statuses, and operating cost of the historical day.
The historical commitment schedule library can be expressed as follows:
In (25), denotes the historical commitment schedule library; collects the 24 h net-load trajectory of historical day ; , , and are the matrices of optimal commitment schedules, the matrices of start-up and shut-down indicators obtained from the full UC model, respectively; and is the corresponding optimal operating cost. In fact, , and can be uniquely determined by .
The matrix of commitment schedules of historical day
can be expressed as shown in (26).
In (26), indicates that unit is ON at hour on historical day , whereas indicates that the unit is offline.
Identical and highly similar commitment schedules are removed to reduce redundancy. For each historical day, the binary commitment matrix is reshaped into a unit-hour vector. The distance between two schedules is measured by the normalized Hamming distance, i.e., the proportion of unit-hour positions with different ON/OFF statuses. If the distance between a schedule and an existing representative is smaller than a preset threshold, the schedule is assigned to the same group rather than stored as an independent candidate. Within each group, the historical day with the lowest full UC operating cost is retained as the representative schedule. Therefore, the historical commitment schedule library contains distinct commitment schedules.
3.2. Net-Load-Based Candidate Generation and Feasibility Repair
After the historical commitment schedule library is constructed, net-load standardization is first performed on both the historical days and the target day to obtain comparable trajectory features for day-to-day similarity-based retrieval. Based on the retrieved candidate schedules, verification with fixed binary variables is then conducted by fixing the binary commitment-related variables and optimizing only the continuous dispatch variables, so as to assess feasibility and operating cost of the target day. If no candidate schedule satisfies the feasibility or economic requirement, a limited-perturbation repair model is further applied to restore feasibility with minimal changes to the candidate commitment schedule.
- (i)
Net-load standardization
For any operating day
, the system net load is defined as the total system load minus the available renewable output, as shown in (27).
In (27), denotes the system net load of operating day at hour .
For the target day, the load demand and available renewable power sequences are available as input information. Then, the net-load trajectory constructed by (27) can serve as the basic feature for retrieving similar operating days.
Because the mean level and fluctuation range of the net load differ significantly across hours, directly measuring Euclidean distance on the raw net-load sequence may overemphasize high-load periods and weaken the contribution of valley periods or ramping periods. In a time-series similarity measurement, Z-score normalization makes Euclidean distance less sensitive to absolute magnitude and more closely related to correlation-based shape similarity [
21]. Therefore, before calculating the distance between operating days, this paper performs hour-wise standardization of the net-load trajectory, as shown in (28).
In (28), denotes the standardized net load; and are the mean and standard deviation of the net load at time interval over all operating days in the historical commitment schedule library, respectively; and is a small positive number used to avoid division by zero. After hour-wise standardization, the similarity measure is less dominated by absolute load magnitude and better reflects the intra-day shape, peak-valley structure, and ramping pattern of the net-load curve.
- (ii)
Euclidean similarity and Top-K similar operating day retrieval
After the standardized net-load trajectories of the target day and the historical days are obtained, Euclidean distance is used to measure their similarity. We use
to denote the target day. The distance between the two net-load trajectories is defined as follows:
In (29), denotes the Euclidean distance. A smaller indicates that the two standardized net-load curves are more similar, and that the residual supply task, intra-day ramping pressure, and reserve requirement of conventional units are also more similar.
During retrieval, the Top-K historical days with the smallest distances are selected to form the candidate set:
In (30), denotes the set of historical days most similar to the target day. Owing to factors such as network power flows, initial unit statuses, minimum ON/OFF time, and reserve constraints, the nearest single historical day may be infeasible or economically inferior for the target day. The Top-K mechanism provides multiple candidates for subsequent verification with fixed binary variables and therefore reduces the risk of mismatch.
- (iii)
Dispatch verification with fixed binary variables
The obtained Top-K candidates are not necessarily feasible under the specific load, renewable power output, and network conditions of the target day. Let
, where
denotes similar historical day
. The commitment schedule of each retrieved historical day is then transferred as a candidate schedule for
, as shown in (31).
In (31), , , and respectively denote the candidate commitment variables, start-up indicators, and shut-down indicators set by historical day . It is worth noting that as these candidates are selected from historical days, their commitment schedules already satisfy the logical links between commitment, start-up, and shut-down decisions, as well as the minimum ON/OFF time constraints.
On this basis, a verification model with fixed binary variables is further introduced to evaluate each candidate. In this model, all binary variables are fixed, and the MILP problem is reduced to a linear programming problem. For candidate
, the verification model can be written as follows:
In (32), denotes the operating cost. , , and are respectively the slack variables for load shedding, spinning reserve shortage, and operating reserve shortage. The coefficients and are set to and , respectively, and are far larger than the cost coefficients of the economic terms such as the renewable curtailment penalty (). In this way, load shedding and reserve shortage are avoided unless no feasible dispatch exists. A candidate commitment schedule is considered feasible if no load shedding or reserve shortage occurs, while renewable curtailment is allowed as an economic adjustment.
The feasible candidate set can be represented as shown in (33):
In (33),
denotes the set of feasible candidates. If
is nonempty, the candidate with the lowest verification operating cost is selected as the final unit commitment schedule:
In (35), denotes the final generated commitment schedule of the target day. This ensures feasibility under the target day settings, while selecting the minimum-cost feasible candidate avoids the economic loss of adopting only the nearest candidate.
- (iv)
Limited-perturbation repair of infeasible candidates
If all Top-K candidates are infeasible or the feasible candidates exceed the preset cost deviation threshold, historical commitment schedule transfer alone is insufficient for the target day. In this case, a limited-perturbation repair model is introduced to make bounded adjustments around the candidate commitment schedule. Unlike solving the full UC problem, the limited-perturbation repair does not re-optimize all commitment variables. Instead, it penalizes deviations from the candidate schedule, so that only limited changes are introduced when restoring feasibility.
We use
to denote the candidate schedule selected for repair. When no feasible candidate exists,
can be chosen as the nearest retrieved candidate. The repair model re-optimizes the binary commitment variables, while penalizing deviations from the candidate commitment schedule. The objective function is written as (36).
In (36), , , and are the deviation variables for unit commitment variables, start-up indicators, and shut-down indicators, respectively. , , and are the corresponding deviation penalty coefficients. They are set to 5000, 1000, and 1000, respectively, which are also larger than the economic cost coefficients, so that the candidate schedule changes only when necessary. The repair model enforces all original operating constraints.
The deviation of unit commitment variables can be represented as follows:
The deviation of start-up indicators can be written as follows:
The deviation of shut-down indicators can be written as follows:
In (37)–(39), , and denote the commitment, start-up, and shut-down statuses of the selected schedule. The repair model tends to restore operating feasibility while changing the original candidate commitment schedule as little as possible.
Therefore, the final generated schedule can be expressed as (40), where
denotes the commitment schedule obtained by the limited-perturbation repair model, and
is a binary indicator that equals one if the economic repair criterion is triggered and 0 otherwise.
It should be noted that net-load similarity alone can hardly guarantee optimality, since multiple factors, such as reserve requirements, maintenance availability, and network structures, may lead to different commitment decisions even under similar net-load profiles. However, net-load similarity provides a useful and computationally efficient basis for identifying promising historical schedules, because it captures the residual demand and ramping requirements faced by conventional units. In fact, all retrieved candidates are re-evaluated under the actual target-day settings. The Top-K mechanism reduces the risk of relying on a single matched historical schedule, while the limited-perturbation model adjusts the binary decisions when none of the retrieved candidates is feasible or economically acceptable.
In practical operation, factors such as maintenance availability and network structure change are usually limited to a finite set of predefined and known configurations rather than changing arbitrarily from day to day. Historical schedules can therefore be classified according to these structural features, with a separate library established for each configuration, so that for a target day, the applicable configuration is first identified before candidate schedules are retrieved. For days that require a full UC or SCUC solution, their results are then added to the library. The library can thus be maintained as a rolling database, in which newly obtained feasible schedules are continuously added and redundant records are removed.