: Public <<Requirement>> Requirement
Created: |
06/08/2018 16:40:12 |
Modified: |
15/05/2020 16:16:03 |
|
Project: |
|
Author: |
C49278 |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Difficulty: |
Medium |
Priority: |
Medium |
Multiplicity: |
|
Advanced: |
|
UUID: |
{56397CC5-0CE7-46be-AA91-AA33642F125F} |
Appears In: |
Requirement Overview |
All the business rules described in IEC 62325-351 are also valid for this standard. Additional rules are provided hereafter.<br/>When a document is received, it shall be check at the application level to ensure that there are no faults in it that could prevent its normal processing. After this check, an acknowledgement document, as defined in IEC 62325-451-1, shall be generated either accepting in its entirety the document in question or rejecting it with the reasons for the rejection. <br/><b>Document instance implementation </b><br/>The XML documents described in this standard are to be used for the upload of information to a transparency platform managed by the information market aggregator; they may also be used for the download of information to market participants in order to enable automatic processing of the information within their systems. <br/>Consequently attributes that describe basic configuration information (such as name, voltage level, etc.) have been included in the XML documents as optional attributes that may be used only in the case where information is downloaded from the transparency platform. This information shall not be used in the case where information is uploaded to the platform. <br/>The implementation of a data exchange shall be based upon dependency tables that are constructed as outlines in Table 1. In case of the European market such tables are used to describe the different conditions in which all the optional attributes (i.e. the attributes that have a multiplicity of [0..1]) within a document structure are used. <br/>The table contains in the left hand column the mandatory coded attributes as well as the optional attributes.The top row provides the context where the contexts in which the use of the model is intended (i.e. installed production capacity aggregated per production type, day-ahead aggregated generation, transmission assets, etc.). <br/>Within each context row the possible values for the mandatory coded attributes are provided and an indication if the optional attributes are to be used (used, not used, used for upload only, etc.).<br/><b>Table 1 – Dependency table outline for the market information publication processes </b><br/><b>Information model attribute Usage context 1 Usage context 2 Usage context 3 Usage context n </b><br/><b>type (Document) Type code value 1 Type code value 2 Type code value 3 Type code value n </b><br/><b>process.processType Type code value Type code value Type code value Type code value </b><br/><b>businessType (TimeSeries) Type code value Type code value Type code value Type code value </b><br/><b>Attribute value 1 Usage indication Usage indication Usage indication Usage indication </b><br/><b>Attribute value n Usage indication Usage indication Usage indication Usage indication </b><br/><b>Table 2 provides a partial example of dependency table use for the transmission network market document. </b><br/><b>Table 2 – Example of dependency table use for the TransmissionNetwork_MarketDocument </b><br/><b>Information model attribute Article 9.1 </b><br/>Transmission infrastructure <b>Article 13(a) </b><br/>Redispatch <b>Article 13 (b) </b><br/>Countertrading <b>Article 13 (c)</b><br/>Congestion costs <br/><b>type (Document) A90 interconnector network expansion A63 redispatch notice A91 counter trade notice A92 congestion costs </b><br/><b>process.processType A35 network information A16 realised A16 realised A16 realised </b><br/><b>businessType (TimeSeries) B01 interconnector network evolution </b><br/><b>B02 interconnector network dismanteling A46 system operator redispatching </b><br/><b>A85 internal redispatch B03 counter trade B04 congestion costs </b><br/><b>B03 counter trade </b><br/><b>A46 system operator redispatch </b><br/><b>in_Domain.mRid used used used in_Domain same as out_Domain </b><br/><b>out_Domain.mRID used used used out_Domain same as in_Domain </b><br/><b>measurement_Unit.name MAW MAW MAW not used </b><br/><b>currency_Unit.name not used not used not used used </b><br/><b>mktPSRType.psrType not used used not used not used </b><br/><b>curveType used used used used </b><br/><b>end_Date.date used not used not used not used </b><br/><b>flowDirection not used used used not used </b><br/><b>etc.</b><br/><b>Such tables are to be provided in dedicated implementation guides for each relevant information to be delivered. </b><br/>
Tag |
Value |
modsarusUC::identifier |
1 |
 Details:
|