At GOPACS, we strive for continuous improvement of our platform. Our developers release new features daily. If we expect downtime during this process, we announce it via email. And once a month, we publish an overview of all releases on this page.
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
_
19 February 2025
- 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.
_