Bilateral Transactions Programme: News and updates

Production environment

The planned outage went ahead successfully on 8 August to perform upgrades within the environment.

Releases coming up:

To facilitate the final phase, MOSL will implement the upcoming releases outlined below. If further releases are required to the pre-production environment we will communicate these dates in advance. These deployments are designed to provide bug fixes, helping to remove blockers and support trading party testing activities, leading to production releases as outlined below. 

Please note that release 13.6 and 14.0 will be promoted to pre-production together on the release dates above so that all code for both releases is held together to aid Trading Party testing

Promotion to the Production environment will be Release 13.6 on the 28 November 25 and will contain functionality relating to the new/amended SLAs for Processes B7, J2 and G2 (CPW139i – SLAs). Release 14 will be promoted to the Production environment on the 16 December 25 and will include all other features included in CPW139i and CPW164.

Pre-production environment

The next pre-prod release is scheduled for 14 August, please refer to release notes for further information.

Assurance testing

The Assurance testing window for the final phase of the Bilateral program is now closed.  The period between assurance testing and go live enables a second development cycle to account for any bug fixing and/or issues in the pre-production environment during the integration and assurance testing. This will allow us to confidently deliver the release later this year. 

Transition to Business as Usual (BAU) 

The Program and Development teams are hard at work as we approach the delivery of Final Phase 15. With this milestone, the Bilateral Transactions Program begins its transition from an improvement initiative to business-as-usual operations. As highlighted during the recent Contract Managers’ Update meeting, several important changes are now coming into effect in preparation for this final phase. Please take note of these updates to ensure a smooth transition:

• All queries about changes, future releases and requests for support should be directed to the MOSL Service Desk - moslservicedesk.uk@cgi.com, rather than HALO.
• All current HALO tickets will be processed to conclusion.
• Future requests for changes to the Bilateral Hub should follow the same process as for CMOS and will be subject to the same code change process.
• A new navigation tab, called 'Market Systems' will be created on the MOSL website. This will include links to CMOS and the Bilateral Hub. This new page will retain links to the program pages until the final release is live.

Phase 15 - additional functionality

Scope for Phase 15 has been confirmed as follows:

Scheduled for release on 28 November 2025:

• Additional Service Level Agreements (SLA's) in the hub - The priority processes for tracking SLAs were identified by the OAG (Operational Advisory Group) as B7, G2 and J2 processes. 

Scheduled for release on 16 December 2025:

• Additional information character limit increase - The character limit for data item 'Additional Information' (D8213) will be increased from 1024 characters to 3000 characters for all relevant processes and transactions.
• B1, B3, B5 and B7 – Additional data items - This functionality will give opportunities to provide additional meter read information when carrying out the installation of a new meter, a meter exchange or meter change through the additional data items. 
• Data Logging Process (B2) - The new B2 process has been created to enable retailers and wholesalers to raise service requests relating to logging services.  There are no SLAs associated with this process tracked in the hub.
• Process B7 'Request Meter Change' - This has been amended to include a new route for retailers to request a wholesaler carries out enabling works for the installation of a logging device.
• C3 Process (Gap Sites) - A new wholesaler transaction that will enable a SPID to be assigned to a 'No-SPID' service request.
• Escalation functionality - This will enable trading parties to escalate service requests for F4, F5, H1 and M1 processes
• GSS payment notification (new route via M1 process) - A new valid set option of 'Notification of GSS payment' has been introduced in the M1 process, enabling a wholesaler to advise a retailer that they intend to make a GSS payment, the reason for that payment and the value of the payment.
• Efficiency changes for deferrals - These changes will mean a trading party can defer in less clicks and the addition of pop-up prompts will remind users to review deferrals.

Scheduled for release as part of the MPF program, release date will be communicated when known:

• Additional reporting - High level summary report, including reports relating to deferrals, cancellations, rejections, resubmissions and escalations.

Get in touch

If you have any questions or concerns, please raise a query in My MOSL. A member of our team will be happy to help you.