ENOM Release Notes

ENOM is constantly being developed and upgraded - adding new features and keeping up to date with market change. See below for the system Release Notes.

Return to ENOM Main Page

HomeENOM Release Notes

Call +44 (0) 1223 446160 or email enquiries@gmsl.co.uk

ENOM v7.34.1

Added support for BDEW APERAK v2.2 messages, as used by Trading Hub Europe from 1st October 2026.

ENOM v7.34.0

New features

Support for GMSL Comms API

ENOM can now integrate directly with the GMSL Comms service via API, streamlining and modernising the message routing process. Messages can be sent and received via the Comms service, and delivery confirmations are generated for delivered messages.

Improved handling of creation dates and times

Creation dates and times are now always displayed in the user’s local time. Creation dates and times in outgoing messages now handle messages sent by users in multiple time zones.

Fixes and improvements

  • Enhanced credentials storage has been added for GMSL Comms credentials.
  • Security improvements and updated security recommendations.
  • Fixed ‘Out of memory’ errors which could occur when extreme numbers of messages have been received during testing.

ENOM v7.33.3

Added support for BDEW APERAK v2.2 messages, as used by Trading Hub Europe from 1st October 2026. Note: this was released after v7.34.0, so this change is not present in ENOM v7.34.0 but was re-added in v7.34.1.

ENOM v7.33.1

New features

Support Capacity Type in Edigas v5.1 SDT and TDT with daily amounts

Capacity Types can now be used in Edigas v5.1 SDT (NOMINT) and TDT (NOMRES) messages. This allows different capacity types to be nominated to Storengy UK.

Fixes and improvements

  • Support for Windows Server 2025 and SQL Server 2025 has been officially added.
  • Changes have been made to the locking mechanism used by matching and balancing, so if ENOM+ loses connection while processing matching and balancing data, another ENOM can start processing messages more quickly.
  • Performance of matching and balancing processing has been improved by up to 95% in some cases.
  • Options available in the Encoding Overrides section of recipient maintenance have been simplified to make the behaviour clear.
  • Sizing of columns in a number of configuration screens has been improved.
  • ‘Waiting for Matching and Balancing task’ message when exiting ENOM+ now closes correctly once finished.

ENOM v7.32.0

New features

Added support for v6.1 MARSIT allocation messages

Standard versions of the following Edigas v6.1 MARSIT messages can now be imported.

  • Edigas v6.1 (95G) (Provisional Allocation Report) MARSIT messages. These appear in ENOM as TSO’s Daily Provisional Allocation Notice (TDPA) or as TSO’s Provisional Allocation Notice (TPA).
  • Edigas v6.1 (96G) (Definitive Allocation Report) MARSIT messages. These appear in ENOM as TSO’s Daily Definitive Allocation Notice (TDDA) or as TSO’s Definitive Allocation Notice (TDA).

Added support for additional v6.1 NOMRES messages

  • Edigas v6.1 NOMRES messages for interruptions. These appear in ENOM as Interruption Notice (INT).

Added new default Shipper screen for v5 REQRES messages

  • Added a new screen, found under Maintenance > Contract Default Shippers, to allow for the configuration of a default shipper code for Edigas v5 SDR (REQRES) messages. This will automatically populate the internal shipper when using the Respond button on a v5 BDR.

Fixes and improvements

  • Added support for use of namespaces in OTE APERAKs to allow continued processing following planned message format changes by OTE.
  • Removed support for Edigas v1 and v2 messages.
  • Added an (All) Network option to view Shipper Codes.

ENOM v7.31.1

New features

Added support for additional v6.1 NOMINT messages

Standard versions of the following Edigas v6.1 nomination messages can now be imported, viewed, created and used in matching and balancing:

  • Edigas v6.1 (02G) NOMINT messages containing daily data appear in ENOM as Customer Daily Transfer (CDT) messages and are used for virtual trading points.
  • Edigas v6.1 (01G) NOMINT messages containing hourly and daily data appear in ENOM as Shipper’s Daily Transit (SDT) messages and are used for interconnection points.
  • Edigas v6.1 (04G) NOMINT messages containing hourly and daily data appear in ENOM as Shipper’s Daily Non-Matching (SDN) messages and are used for locations where there is no adjacent shipper code (e.g. gas production, or end user offtakes).

Some minor features (e.g. capacity types for SDT messages) are not yet supported.

Added support for v6.1 NOMRES messages

Standard versions of the following Edigas v6.1 confirmation messages containing hourly and daily data can now be imported, viewed and used in matching and balancing:

  • Edigas v6.1 NOMRES messages for virtual trading points. They appear in ENOM as Hub Confirmation Notice (HCN) messages.
  • Edigas v6.1 NOMRES messages for interconnection points. They appear in ENOM as TSO’s Daily Transit (TDT) messages.
  • Edigas v6.1 NOMRES messages for locations where there is no adjacent shipper code (e.g. gas production, or end user offtakes). They appear in ENOM as TSO’s Daily Non-Matching Confirmation (TDN) messages.

Show message version in properties

The message type and version for any message is now displayed in the message properties screen.

Fixes and improvements

  • Trading Hub Europe APERAK message with errors for specific line numbers can now be processed.
  • The Advanced settings form for Available Messages can now be resized.
  • Improved handling of invalid messages when a local path is not configured for a message box.
  • Fixed another issue where message box configuration changes can be reset.
  • Edigas v5.1 ACKNOWs should have unique identifications. Previously, this was not always the case.
  • Other minor improvements.

ENOM v7.30.2

Updated the directory release version in SDR (REQRES) messages to Trading Hub Europe, to match updated validation in their systems.

ENOM v7.30.1

New features

Added support for v6.1 NOMINT messages for virtual trading points

Edigas v6.1 (02G) NOMINT messages containing hourly data can now be imported, viewed and created. They appear in ENOM as Customer Daily Transfer (CDT) messages.

Added support for v6.1 ACKNOW messages

Edigas v6.1 ACKNOW messages can now be recieved and imported.

ENOM manual viewable in ENOM

The ENOM manual is now viewable in ENOM and is accessed via the Help menu.

Fixes and improvements

  • Fixed issue where location configuration changes were not replicated across open ENOMs.
  • Fixed issue with DELRES creation timestamps.
  • Improved ENOM default settings to align with common Edigas v5/v6 usage.

ENOM v7.29.0

New features

Import Edigas v6.1 Delivery Order (DELORD) messages

Edigas v6.1 Delivery Order messages containing hourly data can now be imported and viewed. They appear in ENOM as TCN (TSO’s Callup Notice) messages.

Create Edigas v6.1 Delivery Response (DELRES) messages

Edigas v6.1 Delivery Response messages can be created in response to an incoming DELORD message. They appear in ENOM as TIN (TSO’s Instruction Notice) messages.

Fixes and improvements

  • Fixed an issue where updated message box settings could be reset to their previous value in certain circumstances.
  • Edigas v5.1 ACKNOWs with a wider range of issuer and recipient roles can now be imported.
  • Improved error handling when some invalid incoming messages are received
  • Fixed an issue with the creation date/time in an Edigas v5 SDR created using the Respond button on a v5 BDR.
  • Locations can now be added to or removed from an Edigas v5 SDR created using the Respond button on a v5 BDR.

ENOM v7.28.0

New features

Allow import of additional Edigas v5 Request message types

Request messages identified with the following types can now be imported, as long as they are for a single gas day and amounts have a location and shipper code. They will all be treated as a Buyer’s Daily Request.

  • Offtake Forecast (35G)
  • Sales Offer (MAB)
  • Flexible Request (AMO)
  • Time swap (AMP)
  • Location swap (AMQ)

Outgoing messages will still be sent with a type of 38G (Offtake Notice).

Allow import of additional Edigas v5 Response message types

Response messages identified with the following types can now be imported. They will all be treated as a Seller’s Daily Response.

  • Flexible request confirmation (AMR)
  • Time swap confirmation (AMS)
  • Location swap confirmation (AMT)

Outgoing messages will still be sent with a type of AMD (Offtake Confirmation).

Support for Edigas v5.1 Account Synchronisation messages from Balansys

Edigas v5.1 Account Synchronisation ACCSIT messages can now be viewed. These appear as message type IMBNOTS (Imbalance Synchronisation). These are received by shippers using the Imbalance Pooling service in Belgium.

Provisional support for OTE Virtual Trading Point nominations

Provisional support has been added for OTE VTP messages, pending final testing with OTE.

  • A new “OTE v4 (XML)” Message Format has been added, as OTE messages do not follow Edigas standards.
  • It is now possible to create messages of type “Customer’s Daily Transfer (CDT)” with Message Format “OTE v4 (XML)”. These can be used to generate nominations for the OTE Virtual Trading Point.
  • Acknowledgement (ACKNOW) messages received from OTE can be imported.

Note that it is not currently possible to process incoming confirmation notices from OTE, or to submit nominations to OTE for other activities.

Fixes and improvements

  • Changed validation of Edigas v5 contract messages to allow incoming messages from counterparties based on older (pre-2018) versions of the Edigas guidelines.
  • Fixed an error configuring Available Messages for some message types, affecting customers without ENOM+.

ENOM 7.27.3

Fixes and improvements

  • Corrected Code to code in Edigas v5 BDR messages added in v7.27.0. This fix is required to send or receive Edigas v5 BDR messages.
  • Updated the namespace in the Edigas v5 OFFERS messages (SMA, SWA, SDDA and SDA) added in v7.27.0, to to reference the latest release of the documentation (5.1.4). This allows communication with counterparties who only support the most recent release of these messages.
  • If the optional Contractual Offtake section is included Edigas v5 OFFERS messages (SMA, SWA, SDDA and SDA), it now appears after the location-specific quantities in the Edigas XML.

ENOM 7.27.1

Fixes and improvements

Fixed an issue in Edigas v5.1 contract messages in ENOM v7.27.0 affecting users with Swiss German regional settings, who use the ’ symbol as a thousand separator.

ENOM 7.27.0

New features

Support for Edigas v5 contract messages

Support has been added for a range of Edigas v5 contract messages. See below for further details.

Support Edigas v5 availability messages (OFFERS)

A range of Edigas v5 OFFERS messages can be sent and received. The following ENOM messages types can be used to create a v5 OFFERS message:

  • Seller’s Monthly Availability Forecast (SMA)
  • Seller’s Weekly Availability Forecast (SWA)
  • Seller’s Changed Daily Availability Notice (SDA)
  • Seller’s Declared Daily Availability Notice (SDDA)

Support Edigas v5 BDR messages

Single day Edigas v5 Request (REQEST) messages containing hourly or daily values can be sent and received. These appear as ENOM message type Buyer’s Daily Request (BDR). REQEST notices that contain a location and shipper code are supported.

Support Edigas v5 SDR messages (REQRES)

Single day Edigas v5 Request Response (REQRES) messages containing hourly or daily values can be sent and received. These appear as ENOM message type Seller’s Daily Request Response (SDR). Outgoing messages can be created by clicking the Respond button on an incoming Edigas v5 BDR message.

Use Edigas v5 BDR and SDR in Matching & Balancing

For ENOM+ customers, Edigas v5 BDR and SDR messages are used in Matching & Balancing.

Support Edigas v5 SDT messages with capacity type

A Capacity Type column can now be added to Edigas v5 SDT messages which contain hourly values. This creates “Decomposition Quantities” in the Edigas message. These are primarily used by GATE LNG.

Import Edigas v5 TDT messages with capacity type

Edigas v5 TDT messages which contain hourly values with capacity types can now be imported. These are primarily used by GATE LNG.

Don’t zero amounts when changing row properties

When one of the main properties of a row in a message is changed (e.g. shipper code, quantity type, capacity type), the amounts in that row will be preserved, and will no longer by set to zero. This affects manual editing of all message types in ENOM.

Fixes and improvements

  • Clearing the Matching & Balancing queue from the Bulk Operations screen now also stops any processing that is already running.
  • A Total row and column has been added for quantities in CLRCON messages.
  • ENOM will no longer send “ENOM database connection restored” when it has recovered from a lost database connection.
  • Some customers encountered errors after attempting to replicate encrypted passwords between machines. Handling of errors if passwords cannot be decrypted has been improved, so users can still log in manually if this happens.
  • If you use the ENOM XML interface, new checks have been added to make sure that the direction is not ambiguous in XML imported for Edigas v5 nomination messages. E.g. you cannot import negative amounts with a direction of INPUT. If you do not include the direction attribute in your XML, there is no impact.

ENOM 7.26.0

New features

Support DVGW ALOCAT v5.11a

Added support for the new allocation messages which will be used by Trading Hub Europe from 1st October 2024, including the sending of control messages to acknowledge receipt.

Support “Accepted, Received after Deadline” code in v5.1 ACKNOWs

A new status has been added to the Edigas specification for these acknowledgement messages, and will now be processed with a status of “Remarks”.

Allow Matching and Balancing queue to be cleared

If there is a large queue of messages to be processed for matching and balancing (e.g. because ENOM hasn’t been used for a long time), this can now be cleared from the Bulk Operations screen.

ENOM 7.25.0

New features

Support Edigas v5 ‘Account Position’ MARSIT messages

Edigas v5 MARSIT messages of type 94G (Account Position) are now supported.

Improve handling of different MARSIT message types

MARSIT messages will now appear as one of the following ENOM message types depending on the type attribute in the message:

  • Imbalance Notice (IMBNOT)
  • Reconciliation Notice (IMBNOTR)
  • TSO’s Daily Provisional Allocation (TDPA)
  • TSO’s Daily Definitive Allocation (TDDA)
  • TSO’s Provisional Allocation (TPA)
  • TSO’s Definitive Allocation (TDA)
  • Account Position Report (APR)

This makes it easier to identify the purpose of each message, and “Only Latest” now filters the messages using this type. Note that this will affect any Message Rules configured for these message types.

Update ‘type’ attribute in ENOM XML for Edigas v5 MARSITs

The type attribute in the ENOM XML for v5 MARSITs has been updated to reflect the message types above. E.g. type="14G" becomes type="imbalance". If you use the ENOM XML for these messages, please contact us for more details.

Fixes and improvements

  • Fixed an issue where email alerts about message box errors could include the local path instead of the remote path.
  • If ENOM XML for an Edigas v5 nomination notice is received with no nomination elements, this will now be rejected instead of sending an empty message to the recipient. This was already invalid according to the XSD, but is now strictly enforced.
  • Improved behaviour if database connection is lost. ENOM should now attempt to reconnect without opening large numbers of error message boxes.

ENOM 7.24.0

New features

Support for DVGW v5.7a Imbalance Notice

Added support for the latest version of imbalance notice (IMBNOT) that will be used by Trading Hub Europe from 1st October 2023. You will need this version of ENOM to be able to read imbalance notices from Trading Hub Europe after this date, and to send CONTRL messages to acknowledge receipt of the message.

Fixes and improvements

  • ENOM Service logging has been improved to make troubleshooting easier in case of problems with database connections, or when polling for new messages or files.
  • Upgraded Oracle.ManagedDataAccess (a third-party dependency) to address a potential security vulnerability (CVE-2023-21893).

ENOM 7.23.0

New Features

Improvements to Windows Authentication

The login form has been updated to make it easier to log in for users using Windows authentication. If your Windows account has been added as an ENOM user, you can tick the “Use Windows Authentication” check box and log in without re-entering your Windows credentials. This also applies to GMSL Hosting users.

Sort connection strings alphabetically in Select Database dialog

If your ENOM can connect to multiple databases and the shortcut to launch ENOM does not specify the connection to use, the Select Database dialog will list all available databases alphabetically.

Fixes

Connection String Tool should always run as Administrator

The Connection String Tool, provided with ENOM for encrypting connection strings in ENOM config files, now checks it is running as an Administrator to avoid errors.

Correctly display outgoing ACKNOWs sent in response to Edigas v5 MARSITs

Fixed an issue identifying the outgoing message type.

ENOM 7.22.0

New Features

Support for additional MARSIT message structures

Support has been added for a range of extra Edigas v5.1 MARSIT messages, including:

  • MARSIT messages with no Area or Connection Point, as Energinet are now sending.
  • MARSIT messages with an Area and/or Connection Point, but no Account (shipper).
  • MARSIT messages with a mixture of data structures.

ENOM 7.21.0

New Features

Support for German APERAK v2.1h

  • Added support for the German APERAK v2.1h, including a new date/time format. These APERAKs are now in use by Trading Hub Europe.
  • Trading Hub Europe are now sending error code Z31 for shipper NOMINTs containing an exchange counterparty like EEX. As these nominations are single-sided, the nomination against EEX is ignored and the rest of the nomination message is still accepted. This will now appear as “Accepted with remarks” instead of “Rejected” in ENOM. For EuroRunner users, these messages will also show as “Accepted with Remarks” in EuroRunner after ENOM is upgraded.
  • A number of new APERAK error codes are also now supported.

Support for sending ACKNOWs in response to v5 notices

We have two new acknowledgement rules in the Acknowledgements tab of ENOM, to configure ENOM to send ACKNOWs for v5 MARSIT messages, which Energinet are starting to use, or for all v5 messages.

Support for import of v5.1 (Release 3) ALOCAT

AGGM v5.1 ALOCATs can now be imported with the implementation of support for the v5.1 (Release 3) namespace.

Added export user list functionality

Added new Export User List button on the User Maintenance screen. This allows a list of users in ENOM to be exported to a CSV file.

Fixes

Incorrect attribute order in outgoing CONTRL messages

Fixed a bug where some data in CONTRL messages to Trading Hub Europe was sent in the incorrect order. Note that THE still accept the messages with the incorrect order, so this doesn’t currently cause any issues.

Improved support for incoming Trading Hub Europe CONTRL messages

Fixed an issue where some CONTRL messages with additional error information cannot be matched to the correct outgoing notice.

ENOM 7.19.0

New Features

Support sending of v2.0b CONTRL messages to Trading Hub Europe

As required by Trading Hub Europe, CONTRL messages sent to THE from 1st October 2022 will have version number 2.0b. Without this change, you may receive email alerts from THE that they have not received CONTRL messages from you.

Support Edig@s v5 messages from AGGM

ALOCAT and MARSIT message processing has been extended to support receiving these messages from AGGM. The ENOM XML XSDs “GMSL_XSD_AllocationReport_V5_Output.xsd” and “GMSL_XSD_MARSIT_V5_Output.xsd” have been updated accordingly.

Usability improvements to message formats on Available Messages and Recipients screens

The “Enagas v5 (XML)” message format has been renamed to “Enagas (Spain) v5 (XML)” to avoid confusion with “Edigas v5 (XML)”. The default message formats on these screens have also been changed to match the most commonly-selected options.

ENOM Service message processing improvements

Improvements have been made to the ENOM Service to increase the speed at which it processes incoming messages.

Fixes

Matching and Balancing processing occasionally gets stuck

Fixed a bug where Matching and Balancing could in some situations get stuck processing a particular message.

Incorrectly-sent user expiry warning emails

Fixed a bug where ENOM would continuously send out user expiry warning emails for users that had been deleted by another ENOM instance. Also stopped ENOM sending warnings for Windows-authenticated users that never expire.

Message processing fails if the creation time stamp has more than 3 decimal places

ENOM now supports up to 6 decimal places in message creation time stamps, as present in ACKNOW messages sent by Plinovodi.

ENOM 7.18.0

New Features

Support PSV NOMINT

ENOM now encodes version 5.1 Edig@s NOMINTs as required by Snam to nominate Punto di Scambio Virtuale (Virtual Trading Point - PSV).

Fixes

Support for UTC offsets in ENOM input XML

ENOM now correctly uses the UTC offset in the created_dts attribute of ENOM XML if it is present.

ENOM 7.17.0

New Features

Support MARSIT messages as used by Energinet

ENOM now decodes MARSIT (Market Situation) messages of types 95G (TSO’s Daily Provisional Allocation Report), 96G (TSO’s Daily Definitive Allocation Report), 16G (TSO’s Daily Reconciliation Report) and 14G (TSO’s Daily Imbalance Notification Report) as used by Energinet.

ENOM 7.16.0

New Features

Configurable acknowledgement of messages from Trading Hub Europe (THE)

It is possible to disable responding to messages from THE with CONTRL messages. This is useful if CONTRL messages are already being sent by another system.

Importing TRANOT (Transfer Notice) messages

TRANOT messages can be imported into ENOM. The EDI content can be viewed. TRANOT messages from THE will be responded to with CONTRL messages (if these are not disabled - see above).

Code signing

The ENOM application files and installers are now digitally signed.

ENOM 7.15.0

New Features

Automatic acknowledgement of messages from Trading Hub Europe (THE)

ENOM now responds to any message from THE with a CONTRL message (excluding CONTRL messages received from THE).

Fixes

Error stopping the ENOM Service

Fixed a bug that occasionally prevented the ENOM Service from being stopped.

ENOM 7.13.2

New Features

Support for Edig@s v5.1 messaging with TAP

ENOM now supports sending Edig@s v5.1 NOMINT messages and receiving Edig@s v5.1 ACCSIT messages in the formats specified by Trans Adriatic Pipeline (TAP).

Removal of legacy data access components

Legacy data access components have been removed from both the ENOM Client and Service. For Oracle, ENOM no longer requires Oracle client software to be installed. For SQL Server, ENOM no longer requires the SQL Server Native Client.