Request and order placement of values by the ESA — ESA view
The ESA requests the transmission of values and the associated costs from the MSB. If the values can be made available in the ordered granularity and scope by the MSB (from the back-end system or directly from the iMS), the MSB creates a quotation for this transmission of values and makes it available to the ESA. The ESA can then order the transmission of values. If the ESA wants to receive the values at market location level, it addresses its request and order placement to the MSB of the market location. If the ESA wants to receive the values at metering location level, it addresses its request and order placement to the MSB of the metering location. If the ESA wants to receive the values at grid location level, it addresses its request and order placement to the MSB of the grid location.
Process flow from the perspective of the ESA
Process steps
Request for values
ESA MSBCheck identifiers
- 35003 — Request for values · AS4
Flow
Message to MSB · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Quotation for / rejection of the request
ESA MSBCheck identifiers
Flow
Message from MSB · AS4
Response per decision tree
21033→ E_0252 · MSB · Check request
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Order placement
ESA MSBCheck identifiers
- 17007 — Order placement of values · AS4
Flow
Message to MSB · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Response to order placement
ESA MSBCheck identifiers
Flow
Message from MSB · AS4
Response per decision tree
19011,19012→ E_0256 · MSB · Check order placement
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Cancellation of a confirmed order placement
ESA MSBCheck identifiers
- 39002 — Cancellation of the order placement · AS4
Flow
Message to MSB · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Response to cancellation of a confirmed order placement
ESA MSBCheck identifiers
Flow
Message from MSB · AS4
Response per decision tree
19013,19014→ E_0257 · MSB · Check cancellation
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Decision trees of this process
| EBD | Name |
|---|---|
| E_0252 | Check request |
| E_0256 | Check order placement |
| E_0257 | Check cancellation |
Process information
Wording of the consolidated version, profile ch. 4.1.1, pp. 69–71.
Preconditions
- The assurance of ESA regarding compliance with the legal data protection requirements is available to MSB.
- The contractual basis for the request and transmission of the values and for the billing of the service provided from MSB to ESA is available to MSB.
- For a request for values at market location level:
- The metering point operation is carried out at all metering locations of the market location by the same MSB; i.e. the MSB of the market location is the MSB of the metering location(s).
- For a request for values at grid location level:
- The metering point operation is carried out at all metering locations of the grid location by the same MSB; i.e. the MSB of the grid location is the MSB of the metering location(s).
- The EDIFACT communication between MSB and ESA has been established.
- The existing device technology permits the transmission of the requested values.
- For the transmission of values from the iMS: all metering locations required to perform the transmission of values are equipped with a iMS.
Results
- The MSB provides the transmission of values ordered by the ESA (from the back-end system or directly from the iMS).
- In the case in which the metering location is equipped with iMS: If parameterisation of the measuring equipment is necessary in order to provide the transmission of values, MSB carries out the parameterisation of the measuring equipment.
Error case
Result in the error case
- The transmission of values cannot be provided.
Error cases
- The MSB is not assigned to the market location /metering location/grid location for the requested time period.
- The existing device technology does not permit the transmission of the requested values.
- The legal basis for the transmission of values does not exist.
Further requirements
- The request of values must always be addressed to the MSB assigned to the metering location/market location/grid location that is assigned to the market location/metering location/grid location for the time period for which the values are required. This also applies to historical values.
- The request of values can only be made for the time period for which the AN is assigned to the market location/metering location/grid location.
- Ordering other types of values/transmission of values not covered by this use case by the ESA towards the MSB by way of NON-EDIFACT communication (in text form) remains possible at any time.
- If the existing device technology does not permit the requested transmission of values, the change of the device technology is not to be ordered via this use case. ESA must transmit this request to MSB involving the AN outside the process standardisation (i.e. via NON-EDIFACT).
First message
The party involved on this page sends this itself: “Request for values” to MSB (step 1).
Objective
The ESA has ordered the transmission of values from the MSB.
Other views of the process
The same process through the eyes of the other parties involved: the same steps, each read from their point of view.
- View MSB — MSB
Notes on this page
The steps are the possible messages of this process, not a sequence — the source lists neither conditions nor alternatives. The small box on the step names the own view on the left: with ← it receives, with → it sends. Collapsed steps run between other market partners.
The source does not yet name the event that triggers these steps.
Applies to: 1
The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists.
For this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button.