Environment specifics for BSP SYNTAX hos Statnett
The BSP Test Environment is set up for message validation for bid submission, activation request/response and heartbeat request/response. The supported messages types and some other details are described below.
Bid Submission
Description | |
---|---|
BSP Gate Closure Time is set to "Go Live for mFRR EAM". |
BSP Gate Closure time (GCT) is set to 45 minutes relative to the hour to which the delivery period belongs (H-45). |
Supported ReserveBid versions |
Currently these versions of the ReserveBid_MarketDocument are supported in the SYNTAX environment: urn:iec62325.351:tc57wg16:451-7:reservebiddocument:7:4 urn:iec62325.351:tc57wg16:451-7:reservebiddocument:7:2 urn:iec62325:ediel:nbm:reservebiddocument:7:2 |
Earliest time for submission of bids |
Bid messages for a given time interval can currently be submitted to the BSP Test Environment two days in advance. This will change in the near future. More details will come when this is updated. |
Day Ahead Price validation |
In the BSP syntax/SIT test environment, the validation of bids against Day Ahead Prices is turned off. |
Heartbeat |
In the BSP syntax/SIT test environment, Heartbeat is turned off. |
Reports |
In the BSP syntax/SIT test environment, no BidAvailability or ReseveAllocationResult reports are sent. |
Simple bids |
Submission of simple bids is supported. |
Complex bids |
Submission of the following complex bids are supported: - Exclusive - Multipart - Inclusive Please note: To validate inclusive bids, urn:iec62325.351:tc57wg16:451-7:reservebiddocument:7:4 or urn:iec62325:ediel:nbm:reservebiddocument:7:2 must be used. |
Linked bids |
Submission of the following linked bids are supported: - Technically linked bids - Conditionally linked bids |
Non-standard bids |
Submission of mFRR-D/Disturbance reserve (code Z74), see Implementation guide for mFRR EAM, v1.1.4, s.29 and 42. |
National bid attributes |
The following national bid attributes are supported: - Maximum duration - Resting time - Period shift - Faster activation |
Activation
Header | Description |
---|---|
Activation in the test environment |
In the test environment, activation is done by a simple simulator that activates the bid. If a bid is available for several types of activation, the simulator will choose to activate the bid using the following priority: 1. Faster activation 2. Period shift 3. Direct activation 4. Scheduled activation Note: The simple simulator does not support updated bids. Bid updates are received, validated and acknowledged accordingly, but the activation request will contain the quantity from the first version of the bid even if the bid is updated before the activation request is received. |
Faster activation |
Activation is supported using the automation simulator. Note: Activation request will be sent when the bid is received. |
Period shift |
Activation is supported using the automation simulator. Note: Activation request will be sent 7,5 minutes prior to MTU. |
Direct activation |
Activation is supported using the automation simulator. Note: Activation request will be sent when the bid is received. |
Scheduled activation |
Activation is supported using the automation simulator. Note: Activation request will be sent 7,5 minutes prior to MTU. |
Slower activation |
Not supported in BSP test environment. |
The BSP Test Environment is set up with the product characteristics as described for "Go-live for mFRR EAM" in chapter 3.3.1 of the Implementation Guide, however values that defer from this table in the implementation guide are described below.
Description | |
---|---|
Maximum bid price |
Bid messages are validated so that only bid messages that contain bid time series with price 10000 EUR or lower are accepted. |
Minimum bid price |
Bid messages are validated so that only bid messages that contain bid time series with price -10000 EUR or higher are accepted. |