FAQs on fundamental data and inside information – Question III.5.1.2

Shall the version number – that is part of the ‘Message ID’ – be incremented with any update to the UMM thread? If so, will the increment of version number always result in a new UMM published to RSS/Atom feed?


Answer:

As explained in the MoP Annex VII each ‘Message ID’ includes 29 characters in total and consists of 3 parts:

  • ‘UMM thread ID’ – 25 characters
  • One underscore (‘_’)
  • ‘Version number’ – 3 characters

Underscores (‘_’) should not be used within the 25 characters of the UMM thread and also it shall not be possible to submit a message with a ‘Message ID’ of less than 29 characters in total.
Any change in the UMM results in a change on the ‘Message ID’. If the same UMM thread is considered, the change will impact the last part of the ID which is the UMM ‘Version number’. It is the responsibility of the reporting parties to put in place appropriate arrangements ensuring proper sequencing of this number.

RSS_Icon Last update: 31/03/2016  

FAQs on fundamental data and inside information – Question III.5.1.7

Regarding fields 16 (“Affected Asset or Unit”) and 17 (“Affected Assets or Unit EIC Code”), shall market participants submit only one message when there is an event that affects several units or assets due to the same reason?


Answer:

The provision of web feeds should be simultaneous to the disclosure of inside information under Article 4(1) of REMIT. If more than one message is published then more than one should be submitted.

If the UMM disclosed publicly refers to more than one facility, and as the schema for reporting only allows the identification of one facility per web feed message, the message needs to be desegregated by facility for data collection purposes. Another option is to use a single web feed message according to the 3rd schema type – “Other market information” in case the event affects a large number of facilities (e.g.: in case of general strike, floods affecting hydro generation etc.).

RSS_Icon Last update: 31/03/2016  

RSS_Icon Subscribe to this Category’s RSS