Product Releases Notes

31 March 2026

• When registering an EAN that cannot be found in the grid connection register, any user can now manually enter the contracted capacity (optional) and the BRP’s EAN13 (mandatory).
• When registering an EAN, a grid operator or CSP can indicate that this is a BritNed registration. The user can then complete the registration immediately, without having to fill in any additional fields.
• For Capacity Steering Contracts with multiple versions, the version dropdown now also displays the date and time when each version was created.
• For Capacity Steering Contracts, the grid connection now also shows the name of the grid connection instead of only the EAN.

_

30 March 2026

• Bug fix for Capacity Steering Contracts using the compensation option “Fixed price per MW steering”. For the fields where the transport capacity for feed-in or offtake is entered, the system now correctly validates whether this falls within the contracted transport capacity of the grid connection.

_

17 March 2026

• It is now possible to submit Missed Feed-in via the GOPACS platform. This applies to feed-in congestion contracts for which Missed Feed-in is compensated. This functionality will be rolled out per grid operator once they are ready to do so. Separate market communication will follow as soon as this becomes available.

_

25 February 2026

• The registration, overview and detail screens for grid connections have been updated. The registration of new connections has been simplified. Data fields are better structured and fields that are not relevant to users have been removed.
• The functionality for MLOEA connections is temporarily limited. When registering a new MLOEA connection, redispatch cannot be selected. Secondary allocation points are no longer created automatically. This is related to a change in the underlying domain model.
• In email notifications related to the prequalification process, a link to the grid operator’s prequalification department is now displayed.
• The “contracted transport capacity – consumption” field, like the “contracted transport capacity – production” field, is mandatory and must be filled in by the grid operator. This field is no longer synchronized with the connection register (aansluitingenregister).

_

14 January 2026

• For Alternative Transport Rights, it is now possible to set the handling trading company. This allows it to differ from the market party of the connection.
• Alternative Transport Rights can now also be edited, allowing the handling trading company to be changed.

_

11 December 2025

• Capacity Steering Contracts can now be registered and viewed. With the introduction of the Capacity Steering Contract, it is now possible to register and activate the deployment of flexible capacity, in addition to capacity limitation. Trading companies can receive and process messages regarding deployment, just as they can with capacity limiation, via both the API and the GOPACS GUI. All updated documentation can be found at https://www.gopacs.eu/en/documents-and-manuals/.

_

8 December 2025

• GOPACS has been linked to the connection register. Connection data will now be synchronised daily with this register. If, after a change in the register, the connection no longer meets the prequalification criteria, it will be automatically deactivated. Users will receive an email notification of this happens.

_

14 November 2025

• The following fields have been removed from the grid connection details page: Balancing Responsible Party name, Flex capacity upwards, Flex capacity downwards.

_

17 October 2025

• Filters on the connections overview screen are now always visible and display the number of connections per status.

_

11 September 2025

• Removed API endpoints that were solely used for previously removed Redispatch archive pages.
• UFTP message broker rejects UFTP response messages while the request message is still being forwarded.

_

28 August 2025

• For grid operator users, authentication with an API key is now also possible via Keycloak.
• The menu item ‘Redispatch Archive’ with the underlying pages Trade History, Redispatch Volumes, and My Solution History has been removed from the frontend.

_

14 August 2025

• Grid connection service can handle the new RenR safety structure.
• Small improvements to the metrics page.

_

31 July 2025

• Minor improvements in the user interface.

_

17 July 2025

• Form in the GOPACS application through which Missed Transport Capacity can be reported by the Trading Company.
• An API for the grid operator to retrieve the reported Missed Transport Capacity.
• Change implemented so that the Trading Company is shown again on the overview page of the Capacity Limiting Contracts when there is no CSP.
• When an Alternative Transport Right (ATR) is created, it is now possible to modify the proposed ID if the ATR needs to be recreated.
• ATR details are only shown to the grid operator who has entered into the ATR.
• Redispatch e-mails are only sent to new users if the Trading Company has the Redispatch product active.

_

20 June 2025

• Resolved a bug that periodically caused delayed response times on GOPACS Redispatch.
• Resolved a bug where modifying the BRP during the pre-qualification of a grid connection did not work.

_

5 June 2025

• Grid operator users with the Grid administrator role can assign different trading companies for CBC and Redispatch on an active and prequalified connection. Adding a second trading company is only allowed for a product for which no trading company has yet been assigned.
• The ATR API has been implemented according to the API specifications.
• The ATR calls are registered and can be retrieved via the ATR API by the grid company.
• The ATR hours can be retrieved by the grid company via the ATR API (total, pending, remaining).

_

27 May 2025

• Introduction of a test button on the acceptance environment, allowing parties using the UFTP implementation to initiate a FlexRequest themselves as a Trading Company.

_

22 May 2025

• Introduced rate limiting on IDCONS. IDCONS’ combined endpoints be called 2000 times per minute by a single user.
• Technical preparation for the verification of delivery at the BritNed connection by checking the nominations.
• Calling a Time-Related Transport Right (TDTR) is now possible via Shapeshifter.
• Refactoring of the side menu functionality, implementation of the data model for multiple suppliers on a connection, and minor improvements in the user interface.

_

8 May 2025

• Email notification settings added for changes to organisation data, pre-qualification updates, and changes to connections.
• Add the product “Reactive Power” as an option for a connection and for a trading company. (Product is not yet active)
• Improved error responses when uploading an incorrect Excel file with effectivities. It’s now clearly communicated what the problem is and where this problem is located.
• Bug fix: When creating a CLC in the GUI, the grid connection drop down now only shows grid connections that are from the own grid company.
• Bug fix: A draft CLC can be edited and saved with all fields optional.
• Bug fix: Changes on a CLC are now directly visible without the need to reload the page.
• Read-only fields are now shown as a text block instead of fields. This has also fixed several bugs like the need to refresh a page to see updated field values and sometimes an incorrect validation was shown on read-only field.

_

29 April 2025

• Bugfix: Calling a flex request at the 1st hour of the first possible day no longer gives an error message.
• Remaining UI elements in the frontend aligned with the new design.

_

10 April 2025

• Bugfix: Difference in time between the prognosis data and the measurement data in VVL has been resolved.
• Implement new design elements in GOPACS web application (release 1 of 2).
• Backend: move email notifications to Notification microservice.
• Solving Feedback goes live. This provides an operator with information on -why- a problem could not or could only partially be solved.

_

27 March 2025

• Bugfix: Reset pagination when using the search function.
• Bugfix: An adjustment has been made to prevent an incorrect Trading Company from being shown on the contract overview page in cases where the Trading Company is not a Congestion Service Provider (CSP). As a temporary solution, no Trading Company is shown for connected parties. A more comprehensive fix is planned for a later stage.
• Enhancement: Adjust colors of areas on the history map based on the number of market announcements.

_

20 March 2025

• Contract overview has been further optimized; Search within a filter, add filter options via multi-select in a filter, Grid Connection EAN added, an option to clear the filters.
• From now on, GDSs and MLOEAs can be qualified in GOPACS. In addition to registration, the connection is also immediately verified when used to resolve a congestion issue. An important milestone that is expected to unlock more liquidity in the congestion market.
• NMCM (non-marketbased congestion manamagement) goes live.
• The ability to create non-marketbased problems, and use NMCM-flagged orders from EPEX and ETPA to resolve these problems.
• The ability to use Netelement + Area to define the exact area for the NMCM regime.
• Communication to CSP’s based on this area definition.
• Configuration options regarding NMCM.
• Solver feedback goes live.
• Information for the Operator stating the reason a problem has not been (fully) resolved. This information helps the Operator to make decisions on next actions.
• Many code clean-up tasks performed.
• Synchronize information from MAR (BRP, supplier) on grid connections. Behind feature toggle.
• Bugfix frontend: Show Voltage level in kV instead of MW

_

5 March 2025

• Sent activation mail to CSP after aggregation had been madeRetrieve additional information such as address from CAR
• Show user a confirmation dialog when a PAP with SAP’s is pre-filled from CAR
• Announcement page now explains Buy/Sell, and has an infinite scroll option
• Added sorting, filtering and three new columns (direction of the CLC, Trading Company and Grid Company) on the Contracts Overview page.
• Added scope as parameter for OAuth 2.0 authentication
• Documentation for UFTP implementation is updated to be more clear on maxPower and minPower and that a grid connection can be limited to 0,0MW
• On creating a contract by API request, cspEan and gridCompanyEan do not have to be provided in the data. These are now derived from the added grid connection

_

• Resolved small issues in the announcement e-mail.
• Resolved issues in the IDCONS Swagger interface.
• When registering a connection (PAP) in an MLOEA construction, the corresponding (SAP) connections are automatically registered.Historical data has been made available in the beta map for announcements.
• Fix for CSV download for trading companies, as it was no longer working.
• The overview page for aggregations is now also accessible to trading companies, allowing them to view their own grid connection aggregations.
• CSV upload for grid connection has support for GDS fields on a grid connection.
• Incoming UFTP endpoints are now optionally equipped with OAuth 2.0 for more secure communication
• All UFTP endpoints are now required to be reached via HTTPS. HTTP is no longer usable
• Warning added in the GOPACS User Interface when a Trading Company switches from its own UFTP implementation to the GOPACS User Interface and vice versa
• Technical preparation to enable delivery verification on GDS/MLOEA connections.

4 February 2025

• It is now possible to choose a start date in the past for a Capacity Restricting Contract (CRC).
• The end date of a CRC is no longer automatically filled in when a contract does not have an unknown end date.
  
• Fixed a bug where a ContractID was not displayed for a concept CRC, preventing it from being activated.
  
• Improvements made to market messages, such as adding a filter and supporting mobile view.
  
• Additional fields added to the connections for Closed Distribution System (CDS) and transfer points.
  
• We unlock an order if the order call group is not called. Since the lock time is now set to 7 minutes, it is important to perform the unlock correctly.
  
• Several bugs fixed and performance improvements implemented.