Code Administrators Code of Practice

 

Code Administration Code of Practice

The Joint Office is committed to operating in line with the Code Administration Code of Practice, published by Ofgem.  Any comments on the Code of Practice or how we can better comply with this would also be very welcome at any time  - email enquiries@gasgovernance.co.uk

What is the CACoP?

As part of Ofgem’s Code Governance Review, the Code Administration Code of Practice (CACoP), was established.

The CACoP is a cross energy industry code document and aims to provide consistency in the approach and level of service associated with Codes modification processes. 

The CACoP contains a number of key principles to facilitate consistency, convergence and transparency in code Modification processes and to help protect the interests of small market participants and consumers through various means including increased use of plain English in Change Reports.

Cross Code Engagement (Modifications affecting multiple Codes)

In order to encourage Cross Code Engagement across the industry, Code Administrators have agreed how they will support any modifications affecting two or more Codes.  This is detailed in the Code Administration Joint Working Practice available at: https://www.mrasco.com/changes/code-administration-code-of-practice

The Master Registration Agreement (MRA) website also publishes a regsiter of modifications which may have cross code impacts at: http://mrasco.com/change-proposals/code-administration-code-of-practice 

CACoP Committee

The Chair and Secretariat services for the CACoP changes every 12 months between each Code Administrator in alphabetical order per Code. From 01 January 2018 to 31 December 2018, this will be the responsibility of DCUSA.  Information with regards to the CACoP Committee meetings and activities can be found via the DCUSA website here

 

CACoP Committee News (October 2018)

Brexit

Code Administrators (CAs) have identified areas of their respective Codes that will likely require changing following our departure from the EU (Brexit).  Ofgem carried out an equivalent exercise for industry licences and consulted on the joint findings in February 2018.

 

At present, we have not identified any Code provisions that would be inoperable on exit day. The outcome of the negotiations with the EU is not yet finalised nor do we know what implications the EU Withdrawal Bill will have for each Code. 

 

However, each Code has identified a number of non-substantive changes that would be required, for example, to remove references to EU law. Until the Government publishes details of how EU legislation will be incorporated into UK law, we will not know the full detail of the changes required. 

 

The extent of the changes will vary from one Code to another. Where changes may be required to ensure fitness for purpose from the day the UK leaves the EU, we will undertake those requisite changes via the normal Code Modification process. We anticipate that, as far as possible, such modifications will follow self-governance. and, similarly, the level of input required from Ofgem will vary also. 

 

CAs will continue to work with Ofgem to ensure Ofgem and BEIS are aware of Code specific issues and concerns that may require legislative or regulatory support. This will help to ensure continuity from 30 March 2019 onwards, and in the longer term, depending upon the UK’s relationship with the EU.

 

CAs will ensure that their stakeholders are informed of any announcements that will impact Industry Codes as soon as possible.  National Grid will be raising the UNC Modification Proposal and further details will be shared once they are available.

 

Horizon Scan

 

Please find attached the CACoP Horizon Scan (September 2018), which provides the Code Administrators combined view of the key the key legislative and regulatory changes expected to impact the industry. These are true at the time of publication and are intended for indicative purposes only. The horizon Scan will be used by Code Administrator's to co-ordinate any changes that have cross code impacts.