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 |
BSP Gate Closure time (GCT) for each bid time series is set to QH-45, i.e. 45 minutes before the start of the bid time series time interval. |
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 |
Gate Opening Time (GOT) for each bid time series is set at 13:00 3 days in advance. Please note that this is special for the SIT environment. |
Day Ahead Price validation |
In the SIT test environment, the validation of bids against Day Ahead Prices is turned off. |
Heartbeat |
In the SIT test environment, Heartbeat may be available, but only upon request. |
Reports |
In the SIT test environment, BidAvailability or ReserveAllocationResult reports are NOT 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) - Submission of Other non-standard bids (code Z83) |
National bid attributes |
The following national bid attributes are supported: - Maximum duration - Resting time - Faster activation - Please note that period shift is not going to be supported. |
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. Direct activation 3. Scheduled activation - Please note that period shift activation is no longer supported 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. |
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. |
The BSP Test Environment is set up with the product characteristics as described for "Today" in chapter 3.3.1 of the Implementation Guide v.1.2.0.