IT Platform

June 17, 2022

  • Question - With which time server the platform.conexus.lv synchronizes its system clock? Is there a way to ask for current system time from the platform.conexus.lv server? It looks like some messages have been sent too late or early by Trader because of possible server system time difference.
  • Answer - Server platform.conexus.lv uses NTP protocol for time synchronisation. Based on the protocol, there can be different upstream time synchronisation data sources, based on upstream (lesser stratum level) server availability. Currently there are no standard way to ask for current system time from platform.conexus.lv server. On message processing it have to be taken into account that there might be simultaneously several messages received by the system, some time necessary for the message transmission and principle, that system operators allocate capacity for the network users on their backend systems in order of received messages according to capacity allocation windows.
  • Question - If the Trader system sends several Auction bid (ALN) messages after very short time intervals with the same business content (all the AuctionBid_Document XML structure sub-node values are the same in all the sent messages) to platform.conexus.lv server then which of them is taken into account as the real action bid? Let’s assume the action starts at 10:00:00. and Trader sends 2 ALN messages: message A arrives at 10:00:01, message B arrives at 10:00:03. Which of the 2 messages will be considered by platform.conexus.lv server as the final/correct bid and which of them will be discarded – A or B? What will be interpreted by the platform.conexus.lv server the official time at which the Trader bid came in: 10:00:01 or 10:00:03?
  • Answer - In general, all ALN messages will be processed and none will be discarded. Every ALN message will be checked for validity, based on ID and version of the message. In that case, general EDIG@S message processing guidelines will be followed. For example, in case if there would be already other message for the same capacity product and period with the higher version, the message will be rejected. There might be other reasons for message rejection. For each message received, arrival time of that message will be considered as the time received.
  • Question - If and how is it possible to determine if an action bid sent by Trader to platform.conexus.lv has passed all the business rules checks and is actually considered a valid business document and is allowed to participate in the auction? Is it correct to assume that the quick automatic accepted response from platform.conexus.lv means that the Auction bid (ALN) message has been checked only formally (if XML structure is OK and values are of correct datatype in the XML nodes) and not against all the business rules?
  • Answer - According to EDIG@S protocol and general message processing guidelines, every message will be first checked for syntactic validity and only afterwards will be checked according to the applicable business rules. Therefore, the first check done is only for technical validity of the message. For every message there are ACKNOW message, which is created based on EDIG@S processing guidelines, i.e – there can be either positive ACKNOW messages (mast commonly - 01G) and negative ACKNOW messages (different system codes are possible). However, AUCRES messages are used to provide the outcome  of the capacity allocation process based on received AUCBID (ALN). For the message exchange EDIG@S message format guidelines are followed.

For example if the Auction bid (ALN) message from Trader arrived into platform.conexus.lv server at 09:59:59 and cannot in business terms participate in the auction (because of arriving 1 second too early) then how will Trader system be notified about this or is there a way to ask about the acceptance of the Auction bid (ALN) message with a second message?

This can be checked by corresponding ACKNOW message

There seems to be a separate message type AUCRES in the specification, but it looks like this gives information after the action has ended, so too late in the business process to still try to send a new Auction bid (ALN) message.

AUCRES messages are used to provide the result of capacity allocation process.

Overall, EDIG@S message format and general implementation guidelines are followed and additional information about message processing principles can be obtained at www.edigas.org

April 29, 2022

  • Question - how IT Platform will work after May 1?
  • Answer - During confirmation of submitted nominations, the proportion of the technical capacity of Inčukalns UGS for the remaining hours of the day will be taken into account, while also nominations submitted by other storage users will be taken into account. Also, in cases where the direction of the nomination is changed during the gas day, the principle of proportionality according to the remaining hours of the gas day will be applied, as well as the capacity type (firm or interruptible) of the respective direction.