STREAM FI01_09 FCR Group Bid

This data set contains the information that is sent to the TSO when making a bid. The bid is done every day for each hour of the day. It consists of 5 tables which are part of a relational database. The tables contain the bid used during the tests with the pilot customers. The table flexdb_flexgroup contains information about the flex groups, including the correlation between the flex group and the related market (FCR-D-up, FCR-D-down). Each entry consists of the following fields: · id is the flex group id, an integer which is the primary key of the table · name is a text containing the name of the flex group · flex_market_id refers to the service (1 for FCR-D-up and 2 for FCR-D-down) · description is a text containing information about the flex group · active_first_day is the first day the flex group can be used · active_last_day is the last day the flex group can be used · created is a timestamp indicating when the flex group has been created · updated is a timestamp indicating the time of the last update The table flexdb_flex_simulation contains the input data used in the simulations such as the amount of rooms and the installed power as well as the correlation between the simulation and the used flex group. Each entry consists of the following fields: · id is the flex simulation id, an integer which is the primary key of the table · flex_group_id indicates the flex group used in the simulation (the id of the table flexdb_flexgroup) · market_day indicates for which market day the simulation has been done · rooms_count is used to track the simulation progress (once the simulation is finished, it shall be equal to roms_total) · rooms_total indicates the total amount of rooms designated for flexible usage in the simulation · total_power_w is the total installed power within the Flex Group. It is the total installed power of all rooms designated for flex use within this flex group (the flex group the simulation is run for) · state indicates the state of the simulation (40 means success) · fail_reason contains the failure reason of the simulation is not successful · exp_data_count is the expected data count per room (288 because the simulations are done with 5 minutes intervals) · iter_step_s contains the iteration steps of the simulation in seconds (300 seconds, that is, 5 minutes) · sequence is the sequence number of the simulation. It is used to tell apart simulations should there be multiple runs for the same market day and Flex Group · created is a timestamp indicating when the entry has been created · updated is a timestamp indicating the time of the last update The table flexdb_flex_periodic_result contains the output data of the simulations such as the power baseline as well as the correlation with the simulation id. Each entry consists of the following fields: · id is the flex simulation result id, an integer which is the primary key of the table · result_start is the timestamp when the simulation has started · result_end is the timestamp when the simulation has ended · duration_s is the period of the simulation (1 hour) · flex_simulation_id is the id of the simulation (the id of the table flexdb_flex_simulation) · power_forecast_w is the power baseline in watt · created is a timestamp indicating when the entry has been created · updated is a timestamp indicating the time of the last update The table flexdb_flex_bid contains the information for the bids, including the correlation between the flex bid and the used flex group. There is an entry for each day and for each service (market) for which a bid has been made. Each entry consists of the following fields: · id is the flex bid id, an integer which is the primary key of the table · flex_group_id is the id of the flex group used in the bid (the id of the table flexdb_flexgroup) · flexgroup_name is the name given to the flex group · market is the market for which the bid has been made · market_day is the day for which the bid has been made · ready_at is the time and day when the bid was ready for sending to the TSO · submitted_at is the time and day when the bid was submitted to the TSO · ack_at indicates when the acknowledgment from the TSO has been received · rejection_reason is the reason why the TSO has rejected the bid when the bid is not successful · mdir is a unique identifier of the bid document in UUID format. It is used to identify bids between TSO and the aggregator. · sequence is the bid sequence number. It is used to tell apart bids internally. It is used in case multiple bid documents are sent to TSO for the same market day and market. For example, there are two Bids for 2025-11-26 in alfa-flex db: SEQ=1 is ACCEPTED, yet SEQ=2 is REJECTED which from TSO's point of view means that we have tried to update the Bid, but (for some reason) TSO has rejected the update. Note that the mRID is equal for both of them. · created is a timestamp indicating when the bid has been created · updated is a timestamp indicating the time of the last update The table flexdb_flex_bid_period contains the detailed information of the bids, hour by hour, including the correlation with the bid id. There are 576 entries related to the tests with real load from the pilot customers. Each entry contains the details of a single hour for a certain bid for a certain market and consists of the following fields: · id an integer which is the primary key of the table and indicates the id of the bid period · bid_id is the id of the bid (the id of the table flexdb_flex_bid) · period_start is a timestamp indicating when the bid period starts · period_end is a timestamp indicating when the bid period ends · duration_s is the period duration in seconds · scaling_factor is a safety measure for the aggregator which indicates how much of the baseline power is used for making the bid (from 0 to 1) · raw_capacity_w is the total available flexible capacity for the bid interval. This is the value that is multiplied by the scaling_factor and converted to MW. · capacity_mw is the offered flexible capacity in MW · unit_price is the used price in EUR per MW · amount_price_eur is the offered price in EUR · created is a timestamp indicating when the entry has been created · updated is a timestamp indicating the time of the last update