<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Wind NI</title>
	<atom:link href="http://www.windni.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.windni.com</link>
	<description>Wind Power Development Northern Ireland</description>
	<lastBuildDate>Thu, 17 May 2012 09:29:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Northern Ireland Environment Agency &#8211; SPECIFIC REQUIREMENTS FOR WINDFARM PROPOSALS</title>
		<link>http://www.windni.com/2012/03/09/northern-ireland-environment-agency-specific-requirements-for-windfarm-proposals/</link>
		<comments>http://www.windni.com/2012/03/09/northern-ireland-environment-agency-specific-requirements-for-windfarm-proposals/#comments</comments>
		<pubDate>Fri, 09 Mar 2012 11:14:53 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Advice]]></category>
		<category><![CDATA[Environmental]]></category>

		<guid isPermaLink="false">http://www.windni.com/?p=1740</guid>
		<description><![CDATA[Northern Ireland Environment Agency November 2011 BAT SURVEY &#8211; SPECIFIC REQUIREMENTS FOR WINDFARM PROPOSALS Bats are afforded a high level of strict protection under The Conservation (Natural Habitats etc.) Regulations (Northern Ireland) 1995 as amended. On assessing your application NIEA ...]<br /><a href="http://www.windni.com/2012/03/09/northern-ireland-environment-agency-specific-requirements-for-windfarm-proposals/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: medium;">Northern Ireland Environment Agency November 2011</span><br />
<span style="font-size: medium;">BAT SURVEY &#8211; SPECIFIC REQUIREMENTS FOR WINDFARM PROPOSALS</span><br />
Bats are afforded a high level of strict protection under The Conservation (Natural Habitats etc.) Regulations (Northern Ireland) 1995 as amended. On assessing your application NIEA consider that there is reasonable likelihood of bats being present on the proposed site. In order to meet national and international statutory obligations, NIEA has recommended to Planning Service that appropriate bat surveys should be carried out prior to the consideration of your planning application. The surveys should be carried out by a professional ecological consultant with relevant experience and qualifications in bat survey techniques. Once we have received the survey information we will be in a position to comment further on your proposal.<br />
The applicant should be aware that due to the seasonal and highly mobile nature of bats, further survey work may be required where timing constraints and/or poor weather conditions occur.</p>
<ul>
<li>All survey work and survey reports must be carried out according to the Bat Conservation Trust (BCT) ‘Bat Surveys Good Practice Guidelines’, the BCT ‘Surveying for onshore wind farms’ document and Eurobats guidance</li>
<li>The applicant must ensure that the commissioned bat surveyor(s) have the necessary experience and qualifications to carry out this work. It is preferable that the surveyor(s) is a member of the Institute of Ecology and Environmental Management (IEEM)</li>
<li>The date and time of the survey and the qualifications and experience of the surveyor(s) should be included in the survey report</li>
<li>The surveyor should ensure that equipment used is sufficient to identify all species of bat. We consider that both static and broadband detectors must be used to fully assess the spatial and temporal distribution of activity for different species. Please refer to page 13 and 14 of the BCT ‘Surveying for onshore wind farms’ document</li>
<li>The survey report must include a map (at least A4 size) showing the location/ transect walked by each surveyor. The location of any other recording equipment must also be illustrated</li>
<li>The survey should take advantage of any opportunity to survey at maximum proposed hub height</li>
<li>Temperature and wind speed at 2 metres above ground at the time of surveying should be provided in the survey report for both manual and static surveys</li>
<li>Transects should be completed within 2-3 hours after sunset and recordings taken at specified locations must be at least 3 minutes in length</li>
<li>Surveys should be carried out within one year of submission to the department</li>
<li>Northern Ireland Environment Agency November 2011</li>
<li>The survey must identify the site risk level for bats and justify their conclusions within the survey report.</li>
<li>Survey methodology and frequency must be proportional to the site risk level (see Table 2 of the BCT minimum survey standards for Surveying for onshore wind farms’ document)</li>
<li>There should be an appropriate number of both dusk &amp; dawn surveys</li>
<li>The entire site and any suitable habitat within 200 metres of the red line boundary should be surveyed</li>
<li>Approximate numbers of bats must be specified using the BCT bat activity index calculation</li>
<li>Species of bats must be specified</li>
<li>Approximate flying height should be specified if possible</li>
<li>The survey should identify and map the presence of any established commuting and foraging paths within the survey area and any connectivity between the proposed site and potential/ known roosting sites</li>
<li>Type of behaviour/activity of bats using the site should be identified. The survey should establish whether bats have established roosts, (active or inactive) or use the area for commuting, foraging, migrating or for breeding purposes, e.g. advertising posts for individual males. Swarming sites or significant hibernation sites should also be investigated and recorded</li>
<li>The information should be presented in a written report and should include a large scale map. The exact location of roosts, roost entrances, advertising posts, swarming activity foraging and commuting movements should be shown. All evidence of use by bats found, for example droppings, should be included</li>
<li>Further survey effort may be required if the proposed windfarm poses a high risk to the local bat population</li>
<li>If necessary, the survey should recommend the most appropriate ways in which the Bats can be protected from the impacts of development throughout the duration of the development</li>
<li>In the event that the planning application goes to appeal or public inquiry, the person(s) contracted to carry out survey work may be required to appear at, or give evidence to, the inquiry</li>
<li>All located roosts should be reported to the Northern Ireland Bat Group*</li>
</ul>
<p>Northern Ireland Environment Agency November 2011<br />
<br />
For more guidance and information on survey methodology and bat ecology please refer to the following publications and websites<br />
NIEA Development Management website;<br />
http://www.ni-environment.gov.uk/land-home/plan/advice_and_information.htm<br />
NIEA Wildlife Management and Licensing<br />
http://www.doeni.gov.uk/niea/biodiversity/wildlife_management_and_licensing/wildlife.htm<br />
NIEA Development Management publication – Bats and Development<br />
http://www.ni-environment.gov.uk/bats__development_booklet.pdf<br />
*NI Bat group<br />
http://www.bats-ni.org.uk/index.html<br />
Bat Conservation Trust website and Best Practice Guidelines<br />
http://www.bats.org.uk<br />
Bat Conservation Trust – Bat Surveys Good Practice Guidelines<br />
http://www.bats.org.uk/publications.php?keyword=Bat+surveys&amp;month=&amp;year=&amp;category=&amp;search=Search<br />
Bat Conservation Trust – Surveying for Onshore Windfarms<br />

http://www.bats.org.uk/download_info.php?id=379&file=BCT_Survey_Guidelines_web_final_version.pdf&referer=http%3A%2F%2Fwww.bats.org.uk%2Fpages%2Fpublications_and_resources.html</p>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2012/03/09/northern-ireland-environment-agency-specific-requirements-for-windfarm-proposals/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Grid Code 2010</title>
		<link>http://www.windni.com/2012/02/21/grid-code-2010/</link>
		<comments>http://www.windni.com/2012/02/21/grid-code-2010/#comments</comments>
		<pubDate>Tue, 21 Feb 2012 21:36:39 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Grid]]></category>

		<guid isPermaLink="false">http://www.windni.com/?p=1720</guid>
		<description><![CDATA[NORTHERN IRELAND ELECTRICITY PLC DISTRIBUTION CODE 1 MAY 2010 &#160; Introduction 1 The Distribution Code is designed to permit the development, maintenance and operation of an efficient, co-ordinated and economical Distribution System and generally to facilitate competition in the generation ...]<br /><a href="http://www.windni.com/2012/02/21/grid-code-2010/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<p><strong>NORTHERN IRELAND ELECTRICITY PLC</strong></p>
<p><strong>DISTRIBUTION CODE</strong></p>
<p><strong>1 MAY 2010</strong></p>
<p>&nbsp;</p>
<p>Introduction</p>
<p>1 The Distribution Code is designed to permit the development, maintenance and</p>
<p>operation of an efficient, co-ordinated and economical Distribution System and</p>
<p>generally to facilitate competition in the generation and supply of electricity. It is</p>
<p>conceived as a statement of what is optimal (particularly from a technical point of view)</p>
<p>for all Users and the DNO itself in relation to the planning, operation and use of the</p>
<p>Distribution System. It seeks to avoid any undue discrimination between Users and</p>
<p>categories of Users.</p>
<p>2 The operating procedures and principles governing the DNO’s relationship with all</p>
<p>Users of the Distribution System, be they Generators, Suppliers, or Demand</p>
<p>Customers, are set out in the Distribution Code. The Distribution Code specifies</p>
<p>day-to-day procedures for both planning and operational purposes and covers both</p>
<p>normal and exceptional circumstances.</p>
<p>3 The Distribution Code is divided into the following sections:-</p>
<p>(a) a Planning Code which provides generally for the supply of certain information</p>
<p>by Users in order that the planning and development of the Distribution System</p>
<p>may be undertaken;</p>
<p>(b) Connection Conditions which specify the minimum technical, design and</p>
<p>certain operational criteria which must be complied with by Users connected to</p>
<p>or seeking connection with the Distribution System;</p>
<p>(c) an Operating Code which is split into a number of sections and deals with:-</p>
<p>(i) Generation and Demand forecasting (OC1);</p>
<p>(ii) the co-ordination of the Outage planning process in respect of</p>
<p>Generating Units and Power Station Equipment and Outages of</p>
<p>equipment on the Distribution System for construction, repair and</p>
<p>maintenance (OC2);</p>
<p>(iii) different methods of reducing Demand (OC3);</p>
<p>(iv) the reporting between the DNO and Users of scheduled and planned</p>
<p>actions and unexpected occurrences such as faults (OC4);</p>
<p>(v) the provision of written reports on occurrences such as faults in certain</p>
<p>circumstances (OC5);</p>
<p>(vi) the co-ordination, establishment and maintenance of Isolation and</p>
<p>Earthing in order that work and/or testing can be carried out safely</p>
<p>(OC6);</p>
<p>(vii) certain aspects of contingency planning (OC7);</p>
<p>(viii) the procedures for determining the number and nomenclature of Plant</p>
<p>and Apparatus at Connection Sites (OC8);</p>
<p>Distribution Code 1 May 2010</p>
<p>Introduction Page 2</p>
<p>(ix) the procedures for the establishment of System Tests (OC9); and</p>
<p>(x) Testing, Monitoring and Investigations in relation to User’s Plant and</p>
<p>Apparatus (OC10);</p>
<p>(d) General Conditions which are intended to ensure, so far as possible, that the</p>
<p>various sections of the Distribution Code work together and work in practice</p>
<p>and which include provisions relating to the establishment of a Distribution</p>
<p>Code Review Panel and other provisions of a general nature; and</p>
<p>(e) a Distribution Metering Code which deals with the basic requirements for</p>
<p>metering.</p>
<p>4 A matrix is provided as Appendix 1 to this section which sets out, for information only,</p>
<p>a guide to the applicability of each section of the Distribution Code to different</p>
<p>categories of Users. It is, however, for each User to review the relevant sections of the</p>
<p>Distribution Code to decide itself with which sections it must comply.</p>
<p>5 This Introduction is provided to Users and to prospective Users for information only</p>
<p>and does not constitute part of the Distribution Code</p>
<p>Distribution Code 1 May 2010</p>
<p>Introduction Page 3</p>
<p>Appendix 1</p>
<p>This matrix provides, for information only, a guide to the applicability of each section of the Distribution Code to different categories of Users. It</p>
<p>is, however, for each User to review the relevant sections of the Distribution Code to decide itself with which sections it must comply.</p>
<p>GC PC CC OC1 OC2 OC3 OC4 OC5 OC6 OC7 OC8 OC9 OC10 MC</p>
<p>Generator with a CDGU             </p>
<p>Generator with a Controllable WFPS             </p>
<p>Generator with a connection at 33kV              </p>
<p>Generator with a connection at 11kV          </p>
<p>Generator with a connection at 6.6kV          </p>
<p>Generators with a rating of 70kVA and above              </p>
<p>Generator with Independent Generating Plant &gt;1MW              </p>
<p>Suppliers         </p>
<p>Demand Customer             </p>
<p>Demand Customer with a connection at 33kV              </p>
<p>Demand Customer with a connection at 11kV            </p>
<p>Demand Customer with a connection at 6.6kV            </p>
<p>Demand Customer &gt;1MW              </p>
<p>Demand Customer &gt;10MW              </p>
<p>Demand Customer ≥70kVA              </p>
<p> &#8211; Users in this category have relevant information but no specific obligations set out in this section.</p>
<p> &#8211; Users in this category have specific obligations set out in this section.</p>
<p>Distribution Code 1 May 2010</p>
<p>General Conditions Page 4</p>
<p>General Conditions</p>
<p>1 Introduction</p>
<p>1.1 The General Conditions contain provisions which are of general application to all</p>
<p>sections of the Distribution Code. Their objective is to ensure, to the extent possible,</p>
<p>that the various sections of the Distribution Code work together and work in practice</p>
<p>for the benefit of all Users.</p>
<p>2 Scope</p>
<p>2.1 The General Conditions apply to the DNO and to all Users. The term “Users” in</p>
<p>these General Conditions means all persons (other than the DNO and the TSO)</p>
<p>referred to in any individual section of the Distribution Code is expressed to apply.</p>
<p>2.2 Some Users whose Plant and Apparatus are connected to the Distribution System</p>
<p>may also be required to comply with the Grid Code. Users should therefore check the</p>
<p>Grid Code to see whether they are required to comply with the Grid Code as well as</p>
<p>the Distribution Code. It is intended by the DNO that there should be no provision in</p>
<p>the Distribution Code which would require a User to act in a way which would require</p>
<p>it to be in breach of its Grid Code obligations.</p>
<p>2.3 The Distribution Code affects any person whose Plant and/or Apparatus is connected</p>
<p>to the Distribution System or who otherwise uses the Distribution System, even</p>
<p>where they are not expressed to be “Users” under any individual section of the</p>
<p>Distribution Code. Anything done by the DNO under or pursuant to the Distribution</p>
<p>Code which affects, or which may affect such persons, shall be deemed to be</p>
<p>undertaken under the Distribution Code in relation to those persons.</p>
<p>3 Assistance in Implementation</p>
<p>3.1 The Licence held by the DNO imposes a duty upon the DNO to implement the</p>
<p>Distribution Code and it is accepted by the DNO and all Users that the Distribution</p>
<p>Code must, therefore, be capable of being enforced by the DNO. In certain cases the</p>
<p>DNO may need access across boundaries, services and facilities from Users or to issue</p>
<p>instructions to Users in order to be able to implement and enforce the Distribution</p>
<p>Code. It is hoped that these cases would be exceptional and it is not, therefore, possible</p>
<p>to envisage precisely or comprehensively what the DNO might reasonably require in</p>
<p>order to put it in a position to be able to carry out its duty to implement and enforce the</p>
<p>Distribution Code, in these cases.</p>
<p>3.2 Accordingly, all Users are required not only to abide both by the letter and the spirit of</p>
<p>the Distribution Code, but also to provide the DNO with such rights of access,</p>
<p>services and facilities and to comply with such instructions as it may reasonably require</p>
<p>to implement and enforce the Distribution Code.</p>
<p>4 Unforeseen Circumstances</p>
<p>4.1 If circumstances arise which the provisions of the Distribution Code have not</p>
<p>foreseen, the DNO shall, to the extent reasonably practicable in the circumstances,</p>
<p>Distribution Code 1 May 2010</p>
<p>General Conditions Page 5</p>
<p>consult promptly and in good faith all affected Users in an effort to reach agreement as</p>
<p>to what action should be taken. If agreement between the DNO and such Users cannot</p>
<p>be reached in the time available, the DNO shall determine what is to be done.</p>
<p>Whenever the DNO makes a determination, it shall do so having regard, wherever</p>
<p>possible, to the views expressed by Users and, in any event, to what is reasonable in all</p>
<p>the circumstances. Each User shall comply with all instructions given to it by the DNO</p>
<p>following such a determination provided that the instructions are consistent with the</p>
<p>then current technical parameters of the relevant User’s System registered under the</p>
<p>Distribution Code. The DNO shall, as soon as reasonably practicable following the</p>
<p>occurrence of unforeseen circumstances, notify all relevant details thereof to the Panel</p>
<p>for consideration in accordance with paragraph 6.2 (e).</p>
<p>5 Hierarchy</p>
<p>5.1 In the event of any conflict between the provisions of any direction of the Secretary of</p>
<p>State or the Minister on the one hand and any provisions of the Distribution Code on</p>
<p>the other, the provisions of such direction shall prevail (provided that such direction or</p>
<p>ruling is binding upon the person to whom it is addressed), and neither the DNO nor</p>
<p>any User shall be liable for failing to comply with the conflicting provision of the</p>
<p>Distribution Code.</p>
<p>5.2 In the event of any conflict between the provisions of the Distribution Code unless</p>
<p>otherwise specified and any contract, agreement or arrangement between the DNO and</p>
<p>a User, the provisions of the Distribution Code shall prevail unless the Distribution</p>
<p>Code expressly provides otherwise.</p>
<p>6 The Distribution Code Review Panel</p>
<p>6.1 The DNO shall establish and maintain the Panel, which shall be a standing body</p>
<p>carrying out the functions referred to in paragraph 6.2.</p>
<p>6.2 The Panel shall:</p>
<p>(a) keep the Distribution Code and its working under review;</p>
<p>(b) review all suggestions for amendments to the Distribution Code which the</p>
<p>Authority or any User may submit to the DNO for consideration by the Panel</p>
<p>from time to time;</p>
<p>(c) determine recommendations for amendments to the Distribution Code which</p>
<p>the DNO or the Panel feels are necessary or desirable and the reasons for the</p>
<p>recommendations;</p>
<p>(d) issue guidance in relation to the Distribution Code and its implementation,</p>
<p>performance and interpretation upon the reasonable request of any User; and</p>
<p>(e) consider what changes are necessary to the Distribution Code arising out of any</p>
<p>unforeseen circumstances referred to it by the DNO under paragraph 4.1.</p>
<p>6.3 The Panel shall consist of the following persons, each of whom shall have the right to</p>
<p>vote:-</p>
<p>Distribution Code 1 May 2010</p>
<p>General Conditions Page 6</p>
<p>(a) a chairman appointed by the DNO;</p>
<p>(b) four persons representing the DNO;</p>
<p>(c) three persons representing Generators;</p>
<p>(d) one person representing Demand Customers with large energy usage;</p>
<p>(e) three persons representing electricity Suppliers; and</p>
<p>(f) one person appointed by and representing the Authority.</p>
<p>6.4 The Chairman may invite a representative of the TSO to attend meetings of the Panel.</p>
<p>6.5 The Panel shall establish and comply at all times with its own rules and procedures</p>
<p>relating to the conduct of its business, which shall be approved by the Authority.</p>
<p>6.6 The DNO shall submit all proposed amendments to the Distribution Code (regardless</p>
<p>of which party proposes such amendment) to the Panel for discussion prior to fulfilling</p>
<p>any obligations under its Licence in relation to wider consultation.</p>
<p>7 Communication between the DNO and Users</p>
<p>7.1 Unless otherwise specified in the Distribution Code, all instructions given by the DNO</p>
<p>and communications (other than those relating to the submission of data and notices)</p>
<p>between the DNO and Users (other than Generators) shall take place between the Duty</p>
<p>Shift Manager and the relevant User’s Responsible Engineer/Operator or such other</p>
<p>person as the DNO or the User (as the case may be) may from time to time notify to</p>
<p>the other for such purposes.</p>
<p>7.2 Unless otherwise specified in the Distribution Code, all instructions given by the DNO</p>
<p>and communications (other than those relating to the submission of data and notices)</p>
<p>between the DNO and a Generator shall take place between the Duty Shift Manager</p>
<p>and the Generator&#8217;s Power Station Manager or such other person as the DNO or the</p>
<p>Generator (as the case may be) may from time to time notify to the other for such</p>
<p>purposes.</p>
<p>7.3 Unless otherwise specified in the Distribution Code, all instructions given by the DNO</p>
<p>and communications (other than relating to the submission of data and notices which</p>
<p>shall be submitted pursuant to paragraph 8.2) between the DNO and Users will be by</p>
<p>means of telephone with a facility to record messages permanently or by electronic mail</p>
<p>(using only e-mail addresses which have either been previously communicated to the</p>
<p>User by the DNO or to the DNO by the User.). Any responses required to a</p>
<p>communication shall make use of the same means, telephone with a facility to record</p>
<p>messages permanently or by electronic mail, as the original communication.</p>
<p>7.4 Where instructions or communications are given under the Distribution Code by</p>
<p>means of a communications system with a facility to record (by whatever means)</p>
<p>messages permanently, such recording shall be accepted by the DNO and Users as</p>
<p>evidence of those instructions or communications.</p>
<p>Distribution Code 1 May 2010</p>
<p>General Conditions Page 7</p>
<p>8 Data and Notices</p>
<p>8.1 Data collected by, or otherwise passed to, the DNO under the Distribution Code may</p>
<p>be given to the TSO under the Grid Code or under the Transmission Interface</p>
<p>Agreement, where the DNO is required or permitted to pass that data across.</p>
<p>8.2 Data and notices to be submitted to the DNO under the Distribution Code (other than</p>
<p>data which is the subject of a specific requirement of the Distribution Code as to the</p>
<p>manner of its delivery) shall be delivered in writing either by hand or sent by registered</p>
<p>first class pre-paid post, or by facsimile transmission, or by electronic mail (using only</p>
<p>an e-mail address which has been previously communicated to the User by the DNO).</p>
<p>8.3 Data delivered pursuant to paragraph 8.2 shall:</p>
<p>(a) in the case of data to be submitted by a User prior to the connection of its Plant</p>
<p>and/or Apparatus to the Distribution System, in relation to that Plant and/or</p>
<p>Apparatus, be addressed to the Network Risk and Investment Manager at the</p>
<p>address notified by the DNO to the User following receipt of an application for</p>
<p>connection to the Distribution System, or to such other department within the</p>
<p>DNO or address as the DNO may notify to the User from time to time; and</p>
<p>(b) in the case of data to be submitted by a User in respect of Plant and/or</p>
<p>Apparatus connected to the Distribution System, be addressed to the</p>
<p>Distribution Service Centre Manager at the address notified by the DNO to the</p>
<p>User prior to connection to the Distribution System, or to such other</p>
<p>department within the DNO or address as the DNO may notify to the User from</p>
<p>time to time.</p>
<p>8.4 Notices submitted to Users shall be addressed to such person as may be notified in</p>
<p>writing to the DNO from time to time by the relevant User at its address(es) notified by</p>
<p>the User to the DNO in writing from time to time for submission of data and service of</p>
<p>notices under the Distribution Code (or failing which to the registered or principal</p>
<p>office of the User).</p>
<p>8.5 Where applicable all data items will be referenced to nominal voltage and Frequency</p>
<p>unless otherwise stated.</p>
<p>9 Ownership of Plant and/or Apparatus</p>
<p>References in the Distribution Code to Plant and/or Apparatus of a User include</p>
<p>Plant and/or Apparatus used by a User under any agreement with a third party.</p>
<p>10 Emergency Situations</p>
<p>Users should note that the provisions of the Distribution Code may be suspended in</p>
<p>whole or in part pursuant to any directions given and/or orders made by the Secretary</p>
<p>of State under Article 58 of the Order.</p>
<p>11 Illegality and Partial Invalidity</p>
<p>Distribution Code 1 May 2010</p>
<p>General Conditions Page 8</p>
<p>If any provision of the Distribution Code should become or be declared unlawful or</p>
<p>partially invalid for any reason, the validity of all remaining provisions of the</p>
<p>Distribution Code shall not be affected. If part of a provision of the Distribution Code</p>
<p>is invalid or unlawful but the rest of such provision would remain valid if part of the</p>
<p>wording were deleted, the provision shall apply with such modifications as may be</p>
<p>necessary to make it valid and effective but without affecting the meaning or validity of</p>
<p>any other provision of the Distribution Code.</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 9</p>
<p>Planning Code</p>
<p>1 Introduction</p>
<p>1.1 The Planning Code (&#8220;PC&#8221;) specifies the requirements for the supply of information to</p>
<p>the DNO by persons connected or persons seeking a new or modified connection to the</p>
<p>Distribution System in order to enable the planning and development of the</p>
<p>Distribution System and, where required, the co-ordinated planning and development</p>
<p>of the Transmission System.</p>
<p>1.2 It also specifies the technical and design criteria and procedures to be applied in the</p>
<p>planning and development of the Distribution System and to be taken account of by</p>
<p>persons connected or seeking connection to the Distribution System in the planning</p>
<p>and development of their own Systems.</p>
<p>1.3 The DNO has obligations under the Grid Code planning code to provide data to the</p>
<p>TSO in order for the development of the Transmission System to be planned. Certain</p>
<p>information received by the DNO from Users under this PC may be passed on to the</p>
<p>TSO in accordance with the DNO’s obligations under the Grid Code.</p>
<p>1.4 System developments must be planned with sufficient lead time to allow any necessary</p>
<p>consents to be obtained and detailed engineering design and construction works to be</p>
<p>completed. Therefore, the PC and the relevant Connection Agreement impose</p>
<p>appropriate timescales on the exchange of information between the DNO and Users</p>
<p>subject to all parties having regard, where appropriate, to the confidentiality of such</p>
<p>information</p>
<p>2 Objectives</p>
<p>2.1 The objectives of the PC are to:-</p>
<p>(a) provide for the supply of information from Users to the DNO which is required</p>
<p>by the DNO in order for the development (including reinforcement and</p>
<p>extension) of the Distribution System to be planned;</p>
<p>(b) provide for the supply of information from Users to the DNO which is required</p>
<p>by both the DNO and the TSO in order to enable the planning and development</p>
<p>of the Transmission System;</p>
<p>(c) reflect the Licence requirements for the supply of information from the DNO to</p>
<p>Users in the form of Statements on Distribution System Capacity;</p>
<p>(d) set out the requirements for the supply of information from Users to the DNO in</p>
<p>respect of any proposed development on a User’s System which may impact on</p>
<p>the performance of the Distribution System or the Transmission System; and</p>
<p>(e) specify the technical and design criteria and procedures which will be applied by</p>
<p>the DNO in the planning and development of the Distribution System and</p>
<p>which are to be taken into account by Users in the planning and development of</p>
<p>their own Systems.</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 10</p>
<p>3 Scope</p>
<p>3.1 The PC applies to the DNO and to Users, which in the PC means:-</p>
<p>(a) Generators in respect of their Plant and/or Apparatus connected to the</p>
<p>Distribution System;</p>
<p>(b) Suppliers; and</p>
<p>(c) Demand Customers in respect of their Connection Sites with a Demand of</p>
<p>1MW and above.</p>
<p>3.2 Persons whose prospective activities would place them in any of the above categories of</p>
<p>User will, as a result of the application procedure for a Connection Agreement,</p>
<p>become subject to the PC prior to their generating, supplying or consuming electricity,</p>
<p>as the case may be, and references to the various categories (or to the general category)</p>
<p>of User should, therefore, be taken as referring to them in that prospective role as well</p>
<p>as to Users actually connected.</p>
<p>4 Categories of planning data</p>
<p>4.1 Planning data required under the PC from Users is allocated to one of two categories:-</p>
<p>(a) Standard Planning Data; and</p>
<p>(b) Detailed Planning Data.</p>
<p>4.2 Lists of Standard Planning Data and Detailed Planning Data are set out in</p>
<p>Appendices A and B to this PC.</p>
<p>5 Manner of provision by Users</p>
<p>5.1 All data to be supplied by Users to the DNO pursuant to this PC shall reflect the best</p>
<p>possible estimate or measurement available to the User in the circumstances, shall be</p>
<p>supplied in writing by the date specified for the purpose of the PC or, where no date is</p>
<p>so specified, in a prompt and timely manner. The DNO shall be entitled to require any</p>
<p>User to submit further information in the event that it considers any data supplied to it</p>
<p>by such User to be unclear or incomplete.</p>
<p>5.2 Failure by a User to comply with its obligation under paragraph 5.1 may result in the</p>
<p>Distribution System, and, in certain circumstances, the Transmission System, being</p>
<p>planned in accordance with incorrect data and/or a delay in the offer of terms being</p>
<p>made to the User by the DNO for connection.</p>
<p>6 Distribution System Planning Criteria</p>
<p>The DNO shall ensure that the relevant Licence Standards are applied in the planning</p>
<p>and development of the Distribution System and these shall be taken into account by</p>
<p>Users in the planning and development of their own Systems.</p>
<p>7 Statement on Distribution System Capacity</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 11</p>
<p>7.1 By way of information for Users, and generally without imposing any other or further</p>
<p>obligation to that contained in the Licence of the DNO, this paragraph 7 sets out a brief</p>
<p>description of the position regarding the provision by the DNO to Users of Statements</p>
<p>on Distribution System Capacity.</p>
<p>7.2 One of the means by which Users and intending Users are able to assess available</p>
<p>Distribution System capacity is the Statement on Distribution System Capacity,</p>
<p>prepared by the DNO under its Licence where requested by any person, showing</p>
<p>present and future circuit capacity, forecast power flows and loading on the part or</p>
<p>parts of the Distribution System specified in the request and fault levels for each</p>
<p>network node covered by the request.</p>
<p>7.3 A Distribution System Capacity Statement will, unless the DNO is relieved of its</p>
<p>obligation by the Authority pursuant to its Licence, be prepared if requested by any</p>
<p>person and the DNO will, subject to paragraph 7.4, give or send such statement to the</p>
<p>person making the request. Where a User requested a Distribution System Capacity</p>
<p>Statement the User must provide sufficient information to the DNO to enable the</p>
<p>statement to be made, including, but not limited to, the relevant Standard Planning</p>
<p>Data. The statement shall, in addition to those matters set out in paragraph 7.2 include:</p>
<p>7.3.1 such further information as shall be reasonably necessary to enable the person</p>
<p>requesting it to identify and evaluate the opportunities available when connecting</p>
<p>to and making use of the part or parts of the Distribution System specified in</p>
<p>the request; and</p>
<p>7.3.2 if so required, a commentary prepared by the DNO indicating its view as to the</p>
<p>suitability of the part or parts of the Distribution System specified in the</p>
<p>request for new connections and transport of further quantities of electricity.</p>
<p>7.4 The DNO may within 10 days after receipt of the request for a Distribution System</p>
<p>Capacity Statement provide the requester with an estimate of its reasonable costs in</p>
<p>the preparation of the statement and the provision of the statement under paragraph 7.3</p>
<p>shall be conditional upon the person requesting the statement agreeing to pay the charge</p>
<p>(or such other amount as the Authority may direct). The statement shall be given or</p>
<p>sent within 28 days (or, where the Authority so approves, such longer period as the</p>
<p>DNO may reasonably request, having regard to the nature and complexity of the</p>
<p>request) of the later of the date of receipt of the request or the date on which the DNO</p>
<p>receives agreement from the requester to pay the charge estimated or the date on which</p>
<p>the amount is determined by the Authority. Where no charge is to be levied, the</p>
<p>statement shall be given or sent within 28 days of the receipt of the request.</p>
<p>8 Status of Planning Data</p>
<p>8.1 For Planning Code purposes, planning data supplied by Users is allocated to one of</p>
<p>three status levels which provide a progression related to degrees of confidentiality,</p>
<p>commitment and validation, as follows:-</p>
<p>8.2 Preliminary Project Planning Data</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 12</p>
<p>8.2.1 Data supplied by a User in conjunction with an application for connection to the</p>
<p>Distribution System shall be considered as Preliminary Project Planning</p>
<p>Data until such time as a binding Connection Agreement is established</p>
<p>between the DNO and the User.</p>
<p>8.2.2 Subject to paragraph 8.2(c), this data shall not be disclosed by the DNO unless</p>
<p>and until it becomes Committed Project Planning Data and/or Registered</p>
<p>Project Planning Data whereupon the following applicable disclosure</p>
<p>provisions of this paragraph 8 will apply.</p>
<p>8.2.3 The DNO may disclose Preliminary Project Planning Data to the TSO for the</p>
<p>purposes of consideration of developments such as, for example, reinforcement</p>
<p>or upgrading of the Transmission System.</p>
<p>8.2.4 Preliminary Project Planning Data will normally contain only Standard</p>
<p>Planning Data, unless Detailed Planning Data is specifically requested by the</p>
<p>DNO to permit more detailed Distribution System or Transmission System</p>
<p>studies.</p>
<p>8.3 Committed Project Planning Data</p>
<p>When the offer for a Connection Agreement is accepted, the data relating to the</p>
<p>User’s development submitted as Preliminary Project Planning Data and data</p>
<p>required or received subsequently by the DNO under this PC shall have the status of</p>
<p>Committed Project Planning Data. Until such time as Registered Project Planning</p>
<p>Data is received for a new or modified connection to the Distribution System,</p>
<p>Committed Project Planning Data, together with other data held by the DNO relating</p>
<p>to the Distribution System, shall form the background against which new applications</p>
<p>from Users shall be considered and against which planning of the Distribution System</p>
<p>and the Transmission System shall be undertaken. Accordingly, Committed Project</p>
<p>Planning Data may be disclosed by the DNO to the extent that the DNO:-</p>
<p>(a) needs to disclose it in Statements of Distribution System Capacity and in any</p>
<p>further information which the DNO is required to provide together with</p>
<p>Statements of Distribution System Capacity;</p>
<p>(b) needs to disclose it when considering and/or advising on applications (or</p>
<p>possible applications) of Users, including disclosure of it or data from it both</p>
<p>orally and in writing, to other Users making an application (or considering or</p>
<p>discussing a possible application) which is, in the DNO’s view, relevant to that</p>
<p>application or possible application;</p>
<p>(c) needs to disclose it to the TSO for the purposes of the planning and/or the</p>
<p>development of the Transmission System; or</p>
<p>(d) needs to disclose it for operational purposes.</p>
<p>Committed Project Planning Data may contain both Standard Planning Data and</p>
<p>Detailed Planning Data.</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 13</p>
<p>8.4 Registered Project Planning Data</p>
<p>8.4.1 The Connection Conditions require that, before an agreed connection to the</p>
<p>Distribution System may be physically established, any estimated values</p>
<p>contained within the Committed Project Planning Data shall be replaced,</p>
<p>where practicable, by validated actual values and as appropriate by updated</p>
<p>forecasts for future data items such as Demand. Data provided at this stage is</p>
<p>termed Registered Project Planning Data.</p>
<p>8.4.2 Registered Project Planning Data may contain both Standard Planning and</p>
<p>Detailed Planning Data.</p>
<p>8.4.3 Registered Project Planning Data, together with other data held by the DNO</p>
<p>relating to the Distribution System will form the background against which new</p>
<p>applications by any User will be considered and against which planning of the</p>
<p>Distribution System and the Transmission System will be undertaken.</p>
<p>Accordingly, Registered Project Planning Data may be disclosed by the DNO</p>
<p>to the extent that the DNO:-</p>
<p>(a) needs to disclose it in the preparation of Statements of Distribution</p>
<p>System Capacity and in any further information which the DNO is</p>
<p>required to provide together with the Statement of Distribution System</p>
<p>Capacity;</p>
<p>(b) needs to disclose it when considering and/or advising on applications (or</p>
<p>possible applications) of Users, including disclosure of it or data from it</p>
<p>both orally and in writing, to other Users making an application (or</p>
<p>considering or discussing a possible application) which is, in the DNO’s</p>
<p>view, relevant to that application or possible application;</p>
<p>(c) needs to disclose it to the TSO for the purposes of the planning and/or</p>
<p>the development of the Transmission System; or</p>
<p>(d) needs to disclose it for operational purposes.</p>
<p>8.5 For the avoidance of doubt, the DNO may additionally use the data supplied for the</p>
<p>purposes referred to in this PC, in complying with the requirements of its Licence and</p>
<p>for operational purposes and nothing herein shall limit the DNO’s rights to disclose</p>
<p>information pursuant to any provisions relating to confidentiality in any Connection</p>
<p>Agreement or in the Licence held by the DNO.</p>
<p>9 Application for a new or modified Connection Agreement</p>
<p>9.1 Any person seeking to establish a new or modified Connection Agreement pursuant to</p>
<p>the Licence held by the DNO must make application on the standard application form</p>
<p>which is available from the DNO on request. The application shall include:-</p>
<p>(a) a description of the Plant and/or Apparatus to be connected to the Distribution</p>
<p>System or, as the case may be, of the modification relating to the User’s Plant</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 14</p>
<p>and/or Apparatus already connected to the Distribution System each of which</p>
<p>shall be termed a &#8220;Development&#8221; in this PC;</p>
<p>(b) the relevant Standard Planning Data as listed in Appendix A; and</p>
<p>(c) the desired completion date of the proposed Development.</p>
<p>9.2 A User must, within 28 days after acceptance of an offer made by the DNO for a new</p>
<p>Connection Agreement (or such longer period as the DNO may reasonably agree in a</p>
<p>particular case), supply (to the extent not already supplied) to the DNO the relevant</p>
<p>Detailed Planning Data as listed in Appendix B.</p>
<p>9.3 Any User seeking to establish modified arrangements for connection to the</p>
<p>Distribution System must, in addition to the provisions set out above, apply to the</p>
<p>DNO in accordance with the procedure set out in the relevant Connection Agreement.</p>
<p>10 Offers Conditional on Consents and Statutory Obligations</p>
<p>10.1 An offer by the DNO to a User for connection to the Distribution System may be</p>
<p>conditional upon the obtaining of or compliance with any necessary consents,</p>
<p>approvals, permissions, wayleaves, or other external requirements (whether of a</p>
<p>statutory, contractual or other nature).</p>
<p>10.2 A User whose Development requires the DNO to obtain any of the consents,</p>
<p>approvals, permissions and wayleaves or to comply with any other requirements</p>
<p>referred to in paragraph 10.1 shall:-</p>
<p>(a) provide any necessary assistance, supporting information or evidence; and</p>
<p>(b) ensure attendance by such witness as the DNO may reasonably request.</p>
<p>10.3 If any planning or other consent or approval is granted, but is conditional upon a</p>
<p>change in the design arrangements originally offered by the DNO (e.g.</p>
<p>undergrounding), then the DNO shall make a revised offer to the User, including</p>
<p>revised terms and timing. This revised offer shall form the basis of any Connection</p>
<p>Agreement.</p>
<p>10.4 The Connection Agreement will deal with the consequences if any necessary consent</p>
<p>is not granted.</p>
<p>11 Annual Planning Data Requirements</p>
<p>11.1 Requirement to provide annual planning data</p>
<p>11.1.1 Users must provide sufficient planning data annually as set out below, or as</p>
<p>reasonably requested by the DNO from time to time, to enable the DNO to</p>
<p>comply with the requirements under its Licence and under the Grid Code.</p>
<p>11.1.2 Planning data submissions must be:-</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 15</p>
<p>(a) provided by the categories of Users specified in paragraph 11.2.1 on a</p>
<p>routine annual basis by the end of calendar week 9 of each year or such</p>
<p>other annual date as the DNO may, upon not less than 6 months&#8217; notice,</p>
<p>notify to such Users in writing; and</p>
<p>(b) provided by a User at the time that it notifies the DNO of any proposed</p>
<p>significant changes to its operating regime.</p>
<p>11.1.3 Annual planning data submissions must be in respect of the remainder of the</p>
<p>current year and each of the seven succeeding calendar years (other than in the</p>
<p>case of Registered Project Planning Data which will reflect the current</p>
<p>position).</p>
<p>11.1.4 In the case of submission on a routine annual basis, where from the date of one</p>
<p>annual submission to another there is no change in the data (or some of the data)</p>
<p>to be submitted, instead of re-submitting the data a User may submit a written</p>
<p>statement that there has been no change from the data (or the relevant data)</p>
<p>submitted the previous time.</p>
<p>11.1.5 In the case of submissions under paragraphs 11.1.2(b), the notification must</p>
<p>include the time and date at which the proposed change will become, or is</p>
<p>expected to become, effective. Notice must be given as soon as practicably</p>
<p>possible in advance to enable the DNO to implement properly any necessary</p>
<p>System modifications. In the event of unplanned changes in a User’s operating</p>
<p>regime the User shall notify the DNO as soon as is practicably possible to</p>
<p>ensure that any contingency measures, which the DNO considers necessary, can</p>
<p>be implemented by the DNO.</p>
<p>11.2 Data to be provided</p>
<p>11.2.1 Standard Planning Data in every case, and Detailed Planning Data if</p>
<p>required by the DNO, by reasonable notice in advance of the submission</p>
<p>(&#8220;reasonableness&#8221; being judged in this context by reference to the amount of</p>
<p>time which it may take to collate the required data), shall (unless there has been</p>
<p>no change from the data submitted the previous time, in which case the</p>
<p>provisions of paragraph 11.1.4 shall apply) be submitted to the DNO annually</p>
<p>by Users in the following categories:-</p>
<p>(a) in respect of all Generators with distribution connected Generating</p>
<p>Units which have an Output of 1MW and above; and</p>
<p>(b) Demand Customers in respect of their Connection Sites with a</p>
<p>Demand of 1MW and above.</p>
<p>11.2.2 Standard Planning Data shall be provided by Users at the time that they notify</p>
<p>the DNO of any significant changes to their System or operating regime.</p>
<p>Detailed Planning Data shall be provided by Users in these circumstances if</p>
<p>required by the DNO.</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 16</p>
<p>Appendix A &#8211; Standard Planning Data Requirements</p>
<p>1 Introduction</p>
<p>1.1 This Appendix A specifies the Standard Planning Data to be submitted to the DNO by</p>
<p>Users pursuant to the Planning Code.</p>
<p>1.2 Data marked thus “‡“ is only required where the Registered Capacity of a Generating</p>
<p>Unit is 100kW or more.</p>
<p>2 Connection Site and User System data</p>
<p>2.1 General</p>
<p>All Users shall provide the DNO with the details as specified in paragraphs 2.2 and 2.3</p>
<p>relating to their User System.</p>
<p>2.2 User System layout</p>
<p>2.2.1 Single line diagrams of existing and proposed arrangements of main connections</p>
<p>and primary distribution systems showing equipment ratings and if available</p>
<p>numbering and nomenclature.</p>
<p>2.3 Short Circuit Infeed</p>
<p>(a) The maximum 3-phase short circuit current infeed into the Distribution</p>
<p>System.</p>
<p>(b) The minimum zero sequence impedance of the User System at the Connection</p>
<p>Point.</p>
<p>3 Demand data</p>
<p>3.1 General</p>
<p>3.1.1 All Users with Demand shall provide the DNO with the Demand data, both</p>
<p>current and forecast, as specified in paragraphs 3.2 to 3.4.</p>
<p>3.1.2 So that the DNO is able to estimate the diversified total Demand at various</p>
<p>times throughout the year each User shall provide such additional forecast</p>
<p>Demand data as the DNO may reasonably request (&#8220;reasonableness&#8221; being</p>
<p>judged in this context by reference to the level of forecast Demand data which</p>
<p>may be required in order to estimate the diversified total Demand at various</p>
<p>times throughout the year).</p>
<p>3.2 Demand (Active and Reactive Power) Data Requirements</p>
<p>(a) Forecast peak day Demand profile (Active and Reactive) and monthly peak</p>
<p>Demand variations net of the output profile of all Independent Generating</p>
<p>Plant in time marked half hours throughout the day.</p>
<p>(b) Type and electrical loading of equipment to be connected:-</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 17</p>
<p>(i) number and size of motors;</p>
<p>(ii) types of drive and control arrangements; and</p>
<p>(iii) other large items of equipment.</p>
<p>(c) The sensitivity of the Demand to any variations in voltage and Frequency on</p>
<p>the Distribution System.</p>
<p>(d) The maximum harmonic content which the User would expect its Demand to</p>
<p>impose on the Distribution System.</p>
<p>(e) The average and maximum phase unbalance which the User would expect its</p>
<p>Demand to impose on the Distribution System.</p>
<p>3.3 Fluctuating Loads &gt; 5 MVA</p>
<p>(a) Details of the cyclic variation of Demand (Active Power and Reactive Power).</p>
<p>(b) The rates of change of Demand (Active Power and Reactive Power) both</p>
<p>increasing and decreasing.</p>
<p>(c) The shortest repetitive time interval between fluctuations in Demand (Active</p>
<p>Power and Reactive Power).</p>
<p>(d) The magnitude of the largest step changes in Demand (Active Power and</p>
<p>Reactive Power), both increasing and decreasing.</p>
<p>(e) Maximum Energy demanded per half hour by the fluctuating load cycle.</p>
<p>(f) Steady state residual Demand (Active Power) occurring between Demand</p>
<p>fluctuations.</p>
<p>3.4 User’s abnormal Loads</p>
<p>3.4.1 Details should be provided on any individual Loads which have characteristics</p>
<p>differing from the normal typical range of Loads in the domestic, commercial</p>
<p>or industrial fields. In particular, details on arc furnaces, rolling mills, traction</p>
<p>installations etc which are liable to cause flicker problems.</p>
<p>4 Generating Unit and Power Station Data</p>
<p>4.1 General</p>
<p>All Generating Unit and Power Station data submitted to the DNO shall be in the</p>
<p>form of:-</p>
<p>(a) one set of Generating Unit and Power Station data where it is connected to the</p>
<p>Distribution System via a busbar arrangement which is not normally operated</p>
<p>in a split configuration; and</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 18</p>
<p>(b) separate sets of Generating Unit and Power Station data where they are</p>
<p>connected to the Distribution System via a busbar arrangement which is, or is</p>
<p>expected to be, operated in a split configuration.</p>
<p>4.2 Power Station data requirements</p>
<p>(a) Point of connection to the Distribution System in terms of geographical and</p>
<p>electrical location and system voltage.</p>
<p>(b) Capacity of Power Station (being an aggregate of all Generating Units in the</p>
<p>Power Station) in MW sent out for Registered Capacity, Minimum</p>
<p>Generation (which in the case of WFPSs shall be assumed to be zero unless a</p>
<p>different value is notified by the User).</p>
<p>(c) In the case of Controllable WFPSs or Dispatchable WFPSs, a diagram that</p>
<p>shows for the Controllable WFPS or Dispatchable WFPS wind speed and</p>
<p>direction against electrical output in MW, in ‘rose’ format.</p>
<p>(d) Maximum auxiliary Demand (Active Power and Reactive Power).</p>
<p>(e) Where Generating Units form part of a User’s System, the output from these</p>
<p>units is to be taken into account by the User in his Demand profile submissions</p>
<p>to the DNO. In such cases the User must inform the DNO of the number of</p>
<p>such Generating Units together with their total capacity. On receipt of such</p>
<p>data the User may be further required, at the DNO’s discretion, to provide</p>
<p>details of the Generating Units together with their Energy output profile.</p>
<p>(f) Operating regime of Generating Units not subject to Central Dispatch (e.g.</p>
<p>continuous, intermittent, peak-lopping).</p>
<p>4.3 Generating Unit data requirements</p>
<p>In relation to Generating Units other than the wind turbines comprised within a</p>
<p>WFPS:</p>
<p>(a) Prime mover type;</p>
<p>(b) Generating Unit type;</p>
<p>(c) Generating Unit rating and terminal voltage (MVA &amp; kV);</p>
<p>(d) Generating Unit rated power factor;</p>
<p>(e) Registered Capacity sent out (MW);</p>
<p>(f) Minimum Generation capability (MW);</p>
<p>(g) Reactive Power capability (both leading and lagging) at the lower voltage</p>
<p>terminals of the Generator Transformers, where applicable at Registered</p>
<p>Capacity;</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 19</p>
<p>(h) Maximum auxiliary demand in MW and MVAr;</p>
<p>(i) Inertia constant (MWs/MVA) ‡;</p>
<p>(j) Short circuit ratio ‡;</p>
<p>(k) Direct axis transient reactance ‡;</p>
<p>(l) Direct axis sub-transient time constant ‡; and</p>
<p>(m) Generator Transformer rated MVA, positive sequence reactance, and tap</p>
<p>change range ‡.</p>
<p>In relation to the wind turbines comprised within a WFPS, such data equivalent to that listed in</p>
<p>paragraph 4.3 (a) to (m) as the DNO shall reasonably require and such additional data as the</p>
<p>DNO may reasonably require relating to the combined performance where more than one</p>
<p>Generating Unit is connected at the Connection Site.</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 20</p>
<p>Appendix B – Detailed Planning Data Requirements</p>
<p>1 Introduction</p>
<p>1.1 This Appendix B specifies the Detailed Planning Data to be submitted to the DNO by</p>
<p>Users pursuant to the Planning Code, some of which by its nature is also Standard</p>
<p>Planning Data.</p>
<p>1.2 Data marked thus “‡“ is only required where the Registered Capacity of a Generating</p>
<p>Unit is 100kW or more.</p>
<p>2 Connection Site and User System data</p>
<p>2.1 General</p>
<p>2.1.1 All Users shall provide the DNO with the details as specified in paragraphs 2.2</p>
<p>to 2.8 relating to their Users System.</p>
<p>2.2 HV User System layout</p>
<p>Single line diagrams of existing and proposed arrangements of main connections and</p>
<p>primary distribution systems including:-</p>
<p>(a) Busbar layouts</p>
<p>(b) Electrical circuitry (i.e. lines, cables, transformers, switchgear etc)</p>
<p>(c) Phasing arrangements</p>
<p>(d) Earthing arrangements</p>
<p>(e) Switching facilities and interlocking arrangements</p>
<p>(f) Operating voltages</p>
<p>(g) Numbering and nomenclature</p>
<p>2.3 HV reactive compensation equipment</p>
<p>For all independently switched reactive compensation equipment on the User’s System</p>
<p>at 11kV and above, other than power factor correction equipment associated directly</p>
<p>with the User’s Plant and Apparatus, the following information is required:</p>
<p>(a) Type of equipment (e.g. fixed or variable);</p>
<p>(b) Capacitive and/or inductive rating or its operating range in MVAr;</p>
<p>(c) Details of any automatic control logic to enable operating characteristics to be</p>
<p>determined;</p>
<p>(d) The point of connection to the User’s System in terms of electrical location and</p>
<p>voltage.</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 21</p>
<p>2.4 Short circuit infeed to the Distribution System</p>
<p>Each User is required to provide the total short circuit infeeds calculated in accordance</p>
<p>with good industry practice into the Distribution System from its User System at the</p>
<p>Connection Point as follows:</p>
<p>(a) the maximum 3-phase short circuit infeed including infeeds from any</p>
<p>synchronous motor or Generating Units forming part of the User’s System;</p>
<p>(b) the additional maximum 3-phase short circuit infeed from induction motors or</p>
<p>Generating Units on the User’s System; and</p>
<p>(c) the minimum zero sequence impedance of the User’s System.</p>
<p>2.5 Lumped System susceptance</p>
<p>Details of equivalent lumped network susceptance of the User’s System at normal</p>
<p>Frequency at the Connection Point. This should include any shunt reactors which are</p>
<p>an integrated part of a cable system and which are not normally in or out of service</p>
<p>independent of the cable (i.e. they are regarded as part of the cable). It should not</p>
<p>include:-</p>
<p>(a) independent reactive compensation plant on the User’s System; or</p>
<p>(b) any susceptance of the User’s System inherent in the Active and Reactive</p>
<p>Power Demand data given under subsection paragraph 3.</p>
<p>2.6 System data</p>
<p>Each User with an existing or proposed User System connected at HV shall provide</p>
<p>the following details relating to that HV System:-</p>
<p>(a) Circuit parameters (for all circuits):</p>
<p>Rated voltage (kV)</p>
<p>Operating voltage (kV)</p>
<p>Positive phase sequence reactance</p>
<p>Positive phase sequence resistance</p>
<p>Positive phase sequence susceptance</p>
<p>Zero phase sequence reactance</p>
<p>Zero phase sequence resistance</p>
<p>Zero Phase sequence susceptance</p>
<p>(b) Switchgear including circuit breakers, switch disconnectors and isolators on all</p>
<p>circuits connected to the Connection Point including those at Power Stations:</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 22</p>
<p>Rated voltage (kV)</p>
<p>Operating voltage (kV)</p>
<p>Rated short-circuit breaking current,3-phase (kA)</p>
<p>Rated short-circuit breaking current,1-phase (kA)</p>
<p>Rated load-breaking current, 3-phase (kA)</p>
<p>Rated load-breaking current, 1-phase (kA)</p>
<p>Rated short-circuit making current, 3-phase (kA)</p>
<p>Rated short circuit making current, 1-phase (kA)</p>
<p>2.7 Protection data</p>
<p>The information essential to the DNO relates only to Protection which can trip or</p>
<p>intertrip or close any Connection Point circuit breaker or any circuit breaker on the</p>
<p>DNO System. The following information is required:-</p>
<p>(a) a full description of the Protection philosophy, including estimated settings, for</p>
<p>all relays and protection systems installed or to be installed on the User’s</p>
<p>System;</p>
<p>(b) a full description of any auto-reclose facilities installed or to be installed on the</p>
<p>User’s System, including type and time delays;</p>
<p>(c) a full description, including estimated settings, for all relays and Protection</p>
<p>systems installed or to be installed on the Generating Unit, Generator</p>
<p>Transformer, station transformer and their associated connections;</p>
<p>(d) for Generating Units having (or intended to have) a circuit breaker on the</p>
<p>circuit leading to the Generating Unit terminals, at the same voltage, clearance</p>
<p>times for electrical faults within the Generating Unit zone; and</p>
<p>(e) the most probable fault clearance time for electrical faults on the User’s</p>
<p>System.</p>
<p>2.8 Earthing arrangements</p>
<p>Full details of the means of connecting the User System to earth, either temporarily or</p>
<p>permanently, including impedance values.</p>
<p>3 Demand data</p>
<p>3.1 General</p>
<p>(a) All Users with Demand shall provide the DNO with the Demand data both</p>
<p>current and forecast as specified in paragraphs 3.2 and 3.3.</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 23</p>
<p>(b) So that the DNO is able to estimate the diversified total Demand at various</p>
<p>times throughout the year, each User shall provide such additional forecast</p>
<p>Demand data as the DNO may reasonably request.</p>
<p>3.2 User’s System Demand (Active and Reactive Power)</p>
<p>Forecast daily Demand profiles net of the output profile of all Independent</p>
<p>Generating Plant directly connected to the User’s System in time marked half hours</p>
<p>throughout the day as follows:-</p>
<p>(a) peak day on the User’s System;</p>
<p>(b) day of peak NI Demand (Active Power); and</p>
<p>(c) day of minimum NI Demand (Active Power).</p>
<p>3.3 User Demand management data</p>
<p>The potential reduction in Demand available from the User in MW and MVAr, the</p>
<p>notice required to put such reduction into effect, the maximum acceptable duration of</p>
<p>the reduction in hours and the permissible number of reductions per annum.</p>
<p>4 Generating Unit and Power Station Data</p>
<p>4.1 General</p>
<p>All Generators with Power Stations which have a Registered Capacity of 2MW and</p>
<p>above shall provide the DNO with the details as specified in paragraphs 4.2 to 4.6.</p>
<p>4.2 Auxiliary Demand</p>
<p>(a) The normal Generating Unit-supplied auxiliary Load is required for each</p>
<p>Generating Unit at rated MW output.</p>
<p>(b) The Power Station auxiliary Load, if any, additional to the Generating Unit -</p>
<p>supplied auxiliary Load, where the Power Station auxiliary Load is supplied</p>
<p>from the NI System, is required for each Power Station.</p>
<p>4.3 Generating Unit parameters</p>
<p>(a) Rated terminal voltage (kV)</p>
<p>(b) Rated MVA</p>
<p>(c) Rated MW</p>
<p>(d) Minimum Generation (MW)</p>
<p>(e) Short circuit ratio</p>
<p>(f) Direct axis synchronous reactance ‡</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 24</p>
<p>(g) Direct axis transient reactance ‡</p>
<p>(h) Direct axis sub-transient reactance ‡</p>
<p>(i) Direct axis transient time constant ‡</p>
<p>(j) Direct axis sub-transient time constant ‡</p>
<p>(k) Quadrature axis synchronous reactance ‡</p>
<p>(l) Quadrature axis transient reactance ‡</p>
<p>(m) Quadrature axis sub-transient reactance ‡</p>
<p>(n) Quadrature axis transient time constant ‡</p>
<p>(o) Quadrature axis sub-transient time constant ‡</p>
<p>(p) Stator time constant ‡</p>
<p>(q) Stator resistance ‡</p>
<p>(r) Stator leakage reactance ‡</p>
<p>(s) Turbo-generator inertia constant (MWs/MVA), or, for wind turbines comprised</p>
<p>within a WFPS, plant inertia constant (MWs/MVA) ‡</p>
<p>(t) Other than for wind turbines comprised within a WFPS, rated field current ‡</p>
<p>(u) Other than for wind turbines comprised within a WFPS, field current (amps)</p>
<p>open circuit saturation curve for voltages at the Generating Unit terminals</p>
<p>ranged from 50% to 120% of rated value in 10% steps as derived from</p>
<p>appropriate manufacturers&#8217; test certificates ‡</p>
<p>4.4 Parameters for Generating Unit step-up transformers</p>
<p>(a) Rated MVA</p>
<p>(b) Voltage ratio</p>
<p>(c) Positive sequence reactance (at max, min, &amp; nominal tap)</p>
<p>(d) Positive sequence resistance (at max, min, &amp; nominal tap)</p>
<p>(e) Zero phase sequence reactance</p>
<p>(f) Tap changer range</p>
<p>(g) Tap changer step size</p>
<p>(h) Tap changer type: on Load or off circuit</p>
<p>4.5 Auxiliary transformer parameters, if applicable</p>
<p>Distribution Code 1 May 2010</p>
<p>Planning Code Page 25</p>
<p>(a) Rated MVA</p>
<p>(b) Voltage ratio</p>
<p>(c) Zero sequence reactance as seen from the higher voltage side</p>
<p>4.6 Excitation control System parameters (not for WFPSs)</p>
<p>(a) DC gain of excitation loop ‡</p>
<p>(b) Rated field voltage ‡</p>
<p>(c) Maximum field voltage ‡</p>
<p>(d) Minimum field voltage ‡</p>
<p>(e) Maximum rate of change of field voltage (rising) ‡</p>
<p>(f) Maximum rate of change of field voltage (falling) ‡</p>
<p>(g) Details of excitation loop described in block diagram form showing transfer</p>
<p>functions of individual elements ‡</p>
<p>(h) Dynamic characteristics of over-excitation limiter ‡</p>
<p>(i) Dynamic characteristics of under-excitation limiter ‡</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 26</p>
<p>Connection Conditions</p>
<p>1 Introduction</p>
<p>1.1 The Connection Conditions specify the technical, design and certain operational</p>
<p>criteria which must be complied with by the DNO and by Users whose Plant and</p>
<p>Apparatus is connected to, or who are seeking a connection to, the Distribution</p>
<p>System.</p>
<p>1.2 They also set out the procedures by which the DNO shall seek to ensure compliance</p>
<p>with these criteria as a prerequisite to granting approval for the connection of a User’s</p>
<p>Plant and Apparatus.</p>
<p>1.3 Procedures by which the DNO and Users may conclude a Connection Agreement are</p>
<p>reflected in the Planning Code. Each Connection Agreement shall require Users to</p>
<p>comply with the terms of the Distribution Code and the DNO will not grant approval</p>
<p>to connect the User’s installation to the Distribution System unless and until it is</p>
<p>satisfied that the criteria laid down by the Connection Conditions have, subject to any</p>
<p>derogations issued by the Authority, been met. The DNO’s grant of approval to</p>
<p>connect a User’s installation to the Distribution System shall also be subject to the</p>
<p>provisions of paragraph 5 of Condition 30 of the Licence held by the DNO as amended</p>
<p>from time to time.</p>
<p>1.4 Some Users may also be required to comply with the Grid Code. Where this is the</p>
<p>case the DNO will not energise the connection prior to the TSO confirming its</p>
<p>agreement to the connection being energised.</p>
<p>2 Objectives</p>
<p>2.1 The Connection Conditions are designed to ensure that:-</p>
<p>(a) no new or modified connection will impose unacceptable effects on the</p>
<p>Distribution System, on any User System or on the Transmission System nor</p>
<p>will it be subject itself to unacceptable effects by its connection to the</p>
<p>Distribution System; and</p>
<p>(b) the basic rules for connection treat all Users of an equivalent category in a nondiscriminatory</p>
<p>fashion, in accordance with the DNO’s statutory and Licence</p>
<p>obligations.</p>
<p>3 Scope</p>
<p>3.1 The Connection Conditions apply to the DNO and to Users which, in the Connection</p>
<p>Conditions, means:-</p>
<p>(a) Generators to the extent further specified in these Connection Conditions; and</p>
<p>(b) Demand Customers in respect of their Connection Sites with a Demand of</p>
<p>1MW and above.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 27</p>
<p>3.2 Persons whose prospective activities would place them in any of the above categories of</p>
<p>User will, as a result of the application procedures for a Connection Agreement,</p>
<p>become bound by the Connection Conditions prior to their generating or consuming</p>
<p>electricity, as the case may be, and references to the various categories (or to the</p>
<p>general category) of User should, therefore, be taken as referring to them in that</p>
<p>prospective role as well as to Users actually connected.</p>
<p>4 Connection Design</p>
<p>4.1 The design of connections between the Distribution System and Users&#8217; Systems shall</p>
<p>be in accordance with the Licence Standards where such standards are applicable.</p>
<p>4.2 The DNO will determine the point, including the voltage, at which each User may be</p>
<p>connected to the Distribution System.</p>
<p>5 Distribution System Electrical Parameters</p>
<p>5.1 General</p>
<p>5.1.1 The Frequency, voltage, harmonic content and phase unbalance design criteria</p>
<p>of the Distribution System are set out in paragraphs 5.2 to 5.5. Users should</p>
<p>take these factors into account in the design of Plant and Apparatus.</p>
<p>5.1.2 Each User shall ensure that its Plant and Apparatus connected to the</p>
<p>Distribution System are capable of operating under any variation in the</p>
<p>Distribution System Frequency and voltage as set out in paragraphs 5.2 and</p>
<p>5.3.</p>
<p>5.2 Distribution System Frequency and Frequency variations</p>
<p>The Frequency of the Distribution System is outwith the control of the DNO but, as</p>
<p>set out by the TSO in the Grid Code:</p>
<p>5.2.1 The Frequency is nominally 50 Hz and shall normally be within the limits of</p>
<p>49.5 Hz to 50.5 Hz in accordance with the Electricity Supply Regulations (N.I.)</p>
<p>1991.</p>
<p>5.2.2 In exceptional circumstances, System Frequency could rise to 52 Hz or fall to</p>
<p>47 Hz but sustained operation outside the range specified in the Electricity</p>
<p>Supply Regulations (N.I.) 1991 is not envisaged.</p>
<p>5.3 Voltage variations</p>
<p>5.3.1 The voltage variation to Demand Customers, as measured at the Connection</p>
<p>Point, shall comply with the Electricity Supply Regulations (N.I.) 1991, that is,</p>
<p>will normally remain within ± 6% of the nominal value or as otherwise agreed.</p>
<p>5.3.2 The design criteria in respect of voltage fluctuations shall be in accordance with</p>
<p>Engineering Recommendation P28.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 28</p>
<p>5.3.3 The design criteria in respect of voltage unbalance shall be in accordance with</p>
<p>Engineering Recommendation P29.</p>
<p>5.3.4 Under fault and circuit switching conditions the rated Frequency component of</p>
<p>voltage may fall or rise transiently. The fall and rise in voltage will be affected</p>
<p>by the method of Earthing of the respective system voltage neutral point.</p>
<p>5.3.5 Each connection to the Distribution System must not adversely affect the</p>
<p>method of Voltage Control employed by the DNO. Information on the voltage</p>
<p>regulation and control arrangements will be made available by the DNO on</p>
<p>request by the User.</p>
<p>5.4 Harmonic content</p>
<p>5.4.1 The design criteria in respect of harmonic distortion shall be in accordance with</p>
<p>Engineering Recommendation G5/4.</p>
<p>6 General Technical Criteria for Plant and Apparatus Connected to the Distribution</p>
<p>System</p>
<p>6.1 The User’s Plant and Apparatus shall comply with the principles outlined in</p>
<p>Regulation 28 of the Electricity Supply Regulations (N.I.) 1991 and Regulations 4-12</p>
<p>and 15 of the Electricity at Work Regulations (N.I.) 1991 or any amendments to or restatements</p>
<p>of those provisions.</p>
<p>6.2 All Users&#8217; Plant and Apparatus which are connected to the Distribution System shall</p>
<p>meet the technical design and operational criteria set out in this paragraph 6. Detailed</p>
<p>information relating to a particular connection will, where indicated below, be made</p>
<p>available by the DNO on request by the User.</p>
<p>6.3 Plant and Apparatus</p>
<p>6.3.1 The DNO shall ensure in respect of its equipment, and Users shall ensure in</p>
<p>respect of their own equipment, that subject as provided in paragraph 6.3.2</p>
<p>below, the principles of design, manufacture, installation and testing of</p>
<p>overhead lines, underground cables and other Plant and Apparatus designed</p>
<p>after 31 March 1992 shall conform to (and such equipment shall comply with)</p>
<p>all applicable statutory obligations and the applicable requirements of the</p>
<p>following standards, each as current at the date of design of such Plant and</p>
<p>Apparatus, which shall apply (to the extent of any inconsistency) in the</p>
<p>following order of precedence:-</p>
<p>(a) relevant European Technical and Quality Assurance Standards or</p>
<p>European Specification;</p>
<p>(b) relevant IEC Publications or other international standards; and</p>
<p>(c) relevant British Standards or other equivalent national standard.</p>
<p>6.3.2 In the case of Plant or Apparatus:-</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 29</p>
<p>(a) designed prior to 31 March 1992 and in use or awaiting re-use at such</p>
<p>date (or about to be used at such date); and</p>
<p>(b) designed after 31 March 1992 and subsequently re-used;</p>
<p>the applicable standards under paragraph 6.3.1 above shall be those which were</p>
<p>current at the date when the Plant or Apparatus was originally designed,</p>
<p>provided that the DNO reasonably considers the Plant and/or Apparatus to be</p>
<p>fit for its purpose having full regard to the respective obligations of the DNO</p>
<p>and the relevant User, and otherwise shall be those current at the date of re-use.</p>
<p>6.4 The short circuit rating and insulation level of a User’s Apparatus at the relevant</p>
<p>Connection Point shall not be less than that specified in the relevant Connection</p>
<p>Agreement.</p>
<p>6.5 Each of the DNO and a User shall ensure that the specification of their respective Plant</p>
<p>and Apparatus at the Connection Site shall be such as to permit operation within the</p>
<p>applicable Local Safety Instructions.</p>
<p>6.6 Metering</p>
<p>6.6.1 The requirements to be met by each User in respect of metering equipment are</p>
<p>set out in the Distribution Metering Code.</p>
<p>6.7 Protection</p>
<p>6.7.1 All User Systems and the Distribution System must incorporate Protection in</p>
<p>accordance with the requirements of the Electricity Supply Regulations (N.I.)</p>
<p>1991 as amended or re-stated.</p>
<p>6.7.2 The basic requirement in all cases is that Users’ arrangements for Protection at</p>
<p>the Connection Point, including types of equipment and Protection settings</p>
<p>must be compatible with standard practices on the Distribution System from</p>
<p>time to time, whilst maintaining necessary discrimination and co-ordination.</p>
<p>Relevant details of the application of these requirements to a particular</p>
<p>connection will be made available to the User upon request pursuant to</p>
<p>paragraph 6.2.</p>
<p>In particular:-</p>
<p>(a) maximum fault clearance times (from fault inception to arc extinction)</p>
<p>must be within the limits established by the DNO in accordance with the</p>
<p>Protection and equipment short circuit rating policy adopted by the</p>
<p>DNO from time to time for the Distribution System;</p>
<p>(b) auto reclosing or sequential switching features may be in use on the</p>
<p>Distribution System. The DNO will on request provide details of the</p>
<p>auto-reclose or sequential switching features;</p>
<p>(c) the Protection arrangements on some parts of the Distribution System</p>
<p>may cause disconnection of, or low voltages on, one or more phases</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 30</p>
<p>only of a three phase supply for certain types of fault. Users should</p>
<p>make provision to safeguard their equipment from the effects of such</p>
<p>events; and</p>
<p>(d) in the case of a three phase and neutral supply system, a fault</p>
<p>disconnecting the neutral can lead to higher than normal voltage</p>
<p>appearing on one or more phases.</p>
<p>6.8 During the course of an application for a Connection Agreement the DNO shall</p>
<p>specify the Protection standards applicable to the Distribution System and agree with</p>
<p>the User (or, in the event that agreement cannot be reached, the DNO will determine</p>
<p>acting reasonably) any conditions for compatibility with the DNO’s Protection</p>
<p>arrangements which shall be complied with by the User.</p>
<p>In particular:-</p>
<p>(a) in order to ensure satisfactory operation of the Distribution System, Protection</p>
<p>systems, operating times, discrimination and sensitivity at the Connection Point</p>
<p>shall be agreed between the DNO and the User (or, in the event that agreement</p>
<p>cannot be reached, shall be determined by the DNO) and may be reviewed from</p>
<p>time to time by the DNO. If, as a consequence of such review, the DNO</p>
<p>identifies a requirement for some variation to such Protection arrangements, the</p>
<p>relevant provisions of the Connection Agreement shall apply;</p>
<p>(b) in order to cover a circuit breaker or equipment having a similar function failing</p>
<p>to operate correctly to interrupt fault current on a High Voltage System, backup</p>
<p>Protection by operation of other circuit breakers or equipment having a</p>
<p>similar function must normally be provided by the User. The DNO will inform</p>
<p>the User if it is not required. If the back-up circuit breaker is owned by the</p>
<p>DNO, it may be equipped with Protection that is limited to that required to</p>
<p>provide excess Energy Protection to the Distribution System; and</p>
<p>(c) unless the DNO specifies otherwise, it is not acceptable for Users to limit the</p>
<p>fault current infeed to the Distribution System by the use of Protection and</p>
<p>associated equipment if the failure of the Protection and associated equipment</p>
<p>to operate as intended in the occurrence of a fault could cause equipment owned</p>
<p>by the DNO to operate outside its short-circuit rating.</p>
<p>Certain provisions on working on certain Protection equipment are included in</p>
<p>paragraph 9.</p>
<p>6.9 Intertripping</p>
<p>6.9.1 In all circumstances where the isolation of faults or System abnormalities is</p>
<p>dependent upon the operation of both the DNO’s and the User’s circuit</p>
<p>breakers, Intertripping facilities may be required. These Intertripping</p>
<p>facilities shall be in accordance with the requirements of the relevant</p>
<p>Connection Agreement.</p>
<p>6.10 Automatic reclosure</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 31</p>
<p>6.10.1 Where automatic reclosure of the DNO circuit breaker is required following</p>
<p>faults on a User’s System, automatic switching equipment shall be provided in</p>
<p>accordance with the requirements of the relevant Connection Agreement.</p>
<p>6.11 Voltage fluctuations and unbalance and harmonic distortion</p>
<p>6.11.1 The design criteria to be applied to Users’ Loads connected to the Distribution</p>
<p>System to limit voltage fluctuations and unbalance and harmonic distortion will</p>
<p>be notified to the User in the course of an application for connection to the</p>
<p>Distribution System and will be in accordance with the Licence Standards,</p>
<p>which are listed in Appendix 3 to these Connection Conditions. In the event</p>
<p>that a User causes any such limits to be breached, the DNO shall be entitled to</p>
<p>require the User to take such steps as the DNO reasonably considers to be</p>
<p>necessary in order to prevent such breach from continuing and the User shall</p>
<p>comply with the DNO’s instructions without delay.</p>
<p>6.12 Neutral Earthing</p>
<p>6.12.1 The specification of a User’s Apparatus shall meet the voltages which will be</p>
<p>imposed on the Apparatus as a result of the method of Earthing of the</p>
<p>Distribution System as specified in the relevant Connection Agreement.</p>
<p>6.12.2 The Earthing of a User’s Apparatus at the Connection Point must be in</p>
<p>accordance with current DNO practice which will be notified to the User,</p>
<p>initially, during the course of an application for connection to the Distribution</p>
<p>System. In the event that the DNO wishes to change its current practice, the</p>
<p>DNO will notify the User as soon as reasonably practicable in advance of the</p>
<p>change and any modifications which such change will require to be undertaken</p>
<p>on the User’s System will be implemented in accordance with the modifications</p>
<p>procedure set down in the User’s Connection Agreement, if it is applicable.</p>
<p>6.12.3 Users shall take all reasonable precautions in relation to a particular Connection</p>
<p>Point to limit the occurrence and effects of circulatory currents in respect of</p>
<p>neutral points of any interconnected system (e.g. where there is more than one</p>
<p>source of Energy).</p>
<p>6.13 Superimposed signals</p>
<p>6.13.1 Where a User proposes to use mains borne signalling equipment to superimpose</p>
<p>signals on the Distribution System, the prior written agreement of the DNO is</p>
<p>required (which agreement will not be unreasonably withheld).</p>
<p>7 Additional Technical Criteria for Generating Units</p>
<p>7.1 All Generating Units shall, in addition to the requirements of paragraph 6, meet the</p>
<p>technical design and operational criteria in this paragraph 7, insofar as each</p>
<p>requirement is applicable to them, which contains more detailed requirements for</p>
<p>Generating Units than those set out in paragraph 6 and is intended to be</p>
<p>complementary to paragraph 6. However, in the event of any conflict between the</p>
<p>requirements of paragraph 6 and the requirements of this paragraph 7, the provisions of</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 32</p>
<p>this paragraph 7 shall prevail. Detailed information relating to a particular connection</p>
<p>will, where indicated below, be made available by the DNO on request by the</p>
<p>Generator.</p>
<p>7.2 Each connection between a Generating Unit and the Distribution System, unless</p>
<p>specified otherwise in the Connection Agreement, must be controlled by a circuit</p>
<p>breaker capable of interrupting the maximum short circuit current at the Connection</p>
<p>Point. The short circuit current design values at a Connection Point will be set out in</p>
<p>the Connection Agreement.</p>
<p>7.3 All Generating Units must comply with the requirements of NIE Engineering</p>
<p>Recommendation G59/1/NI, Recommendations for the connection of embedded</p>
<p>generating plant to Public distribution systems above 20kV G75/1 or with outputs over</p>
<p>5MW, and Engineering Recommendation G83/1, each as applicable and as amended,</p>
<p>supplemented, varied or replaced from time to time and with all other relevant</p>
<p>Engineering Recommendations and relevant regulations and the particular requirements</p>
<p>of the DNO which will take account of the conditions prevailing on the Distribution</p>
<p>System at the Connection Point at the relevant time. The DNO will notify its</p>
<p>particular requirements to the Generator during the course of the Generator’s</p>
<p>application for connection to the Distribution System.</p>
<p>7.4 Reactive Power capability</p>
<p>7.4.1 Each Generating Unit must be capable of operating at its Registered Capacity</p>
<p>in a stable manner within the following power factor ranges:</p>
<p>Range</p>
<p>Type A Generating Units 0.95 absorbing &#8211; 0.98 absorbing</p>
<p>Type B Generating Units 0.95 absorbing – 0.98 generating</p>
<p>7.4.2 In this paragraph 7 Type A Generating Units means Induction Generating</p>
<p>Units.</p>
<p>7.4.3 In this paragraph 7 Type B Generating Units means:</p>
<p>(a) Synchronous Generating Units;</p>
<p>(b) Generating Units of all types connected in part or in total through</p>
<p>convertor technology with a Registered Capacity of 100kW and above;</p>
<p>and</p>
<p>(c) Generating Units within a WFPS with a Registered Capacity of 5MW</p>
<p>and above.</p>
<p>7.4.4 Each Generating Unit with a Registered Capacity of 100kW or more shall</p>
<p>have a minimum Reactive Power capability at its Registered Capacity as</p>
<p>described in the following diagrams:-</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 33</p>
<p>Voltage</p>
<p>Generating</p>
<p>MVAr at</p>
<p>rated MW</p>
<p>Absorbing</p>
<p>MVAr at</p>
<p>rated MW</p>
<p>90% 95% 100% 105%</p>
<p>1.0</p>
<p>0.95</p>
<p>0.95</p>
<p>0.98</p>
<p>94% 106% 110%</p>
<p>0.98</p>
<p>Power</p>
<p>Factor</p>
<p>Type A Generating Units</p>
<p>Voltage</p>
<p>Generating</p>
<p>MVAr at</p>
<p>rated MW</p>
<p>Absorbing</p>
<p>MVAr at</p>
<p>rated MW</p>
<p>90% 95% 100% 105%</p>
<p>1.0</p>
<p>0.95</p>
<p>0.95</p>
<p>0.98</p>
<p>94% 106% 110%</p>
<p>0.98</p>
<p>Power</p>
<p>Factor</p>
<p>Type B Generating Units</p>
<p>7.4.5 The short circuit ratio for each Generating Unit shall not be less than 0.5.</p>
<p>7.4.6 For the avoidance of doubt, all Generating Units must be capable of delivering</p>
<p>the power factor performance at the Connection Point. However, where</p>
<p>complex User Systems involve Generating Units and Load, the User may</p>
<p>submit calculations to support compliance.</p>
<p>7.5 Co-ordination with existing Protection</p>
<p>7.5.1 Each Generator must meet, in relation to each of its Generating Units, the</p>
<p>target clearance times for fault current interchange with the Distribution</p>
<p>System in order to reduce to a minimum the impact on the Distribution System</p>
<p>of faults on circuits owned by a Generator. The target clearance times are</p>
<p>measured from fault current inception to arc extinction and will be specified by</p>
<p>the DNO to meet the requirements of the relevant part of the Distribution</p>
<p>System. A Generator may obtain relevant details specific to its Generating</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 34</p>
<p>Units pursuant to paragraph 6.2. The DNO shall ensure that (subject to any</p>
<p>necessary discrimination) the same target fault clearance times can be achieved</p>
<p>by its own Apparatus at each Connection Point.</p>
<p>7.5.2 Unless otherwise agreed, the fault clearance times required by the Connection</p>
<p>Agreement shall not be faster than 120 ms but, if otherwise agreed, nothing in</p>
<p>this paragraph 7.5.2 shall prevent a Generating Unit or the DNO’s Apparatus</p>
<p>at the Connection Point from having faster clearance times (subject to</p>
<p>necessary discrimination being maintained). The times specified in the</p>
<p>Connection Agreement will reflect the DNO’s view of the requirements of the</p>
<p>Distribution System, and the User’s System, for the expected life time of the</p>
<p>Protection (for example, 15 years). The probability that the fault clearance</p>
<p>times stated in the Connection Agreement will be exceeded by any given fault</p>
<p>must be less than 2%.</p>
<p>7.5.3 To cover for failure of the above Protection systems to meet the above fault</p>
<p>clearance times, the Generator may be required to provide back up Protection.</p>
<p>The back up Protection shall be required to discriminate with other Protections</p>
<p>fitted on the Distribution System. Relevant details will be made available to a</p>
<p>Generator upon request pursuant to paragraph 7.1.</p>
<p>7.5.4 The setting of any Protection controlling a circuit breaker or the operating</p>
<p>values of any automatic switching device at any Connection Point shall have</p>
<p>been agreed between the DNO and the User during the course of the application</p>
<p>for a Connection Agreement. The settings and operating values will only be</p>
<p>changed if both the DNO and the User agree provided that neither the DNO nor</p>
<p>the User shall unreasonably withhold their consent.</p>
<p>7.5.5 If in the opinion of the DNO following an overall review of Distribution</p>
<p>System Protection requirements improvements to any Generating Unit</p>
<p>Protection scheme are necessary, the relevant provisions of the Connection</p>
<p>Agreement shall be followed.</p>
<p>7.5.6 The Generating Unit Protection must co-ordinate with any auto reclose policy</p>
<p>specified by the DNO.</p>
<p>7.6 Minimum connected impedance</p>
<p>7.6.1 For Generating Units which do not form part of a WFPS the minimum</p>
<p>connected impedance applicable to the generator and Generator Transformer</p>
<p>will be specified in the Connection Agreement. The DNO’s requirements for</p>
<p>the impedances will reflect the needs of the Distribution System from the fault</p>
<p>level and stability points of view.</p>
<p>7.6.2 For WFPSs the minimum connected impedance applicable to the whole WFPS</p>
<p>as a single unit will be specified in the Connection Agreement. The DNO’s</p>
<p>requirements for the impedance will reflect the needs of the Distribution</p>
<p>System from the fault level and stability points of view.</p>
<p>7.7 Variations in System Frequency</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 35</p>
<p>7.7.1 In order to comply with its Grid Code obligations, the DNO requires that, apart</p>
<p>from those circumstances set out in sub-paragraph 7.7.2, all Independent</p>
<p>Generating Plant with an Output of 100kW or more shall stay connected and</p>
<p>operate:</p>
<p>(a) continuously where the Distribution System Frequency varies within</p>
<p>the range 49.5 to 52.0 Hz;</p>
<p>(b) for a period of up to one hour where the Distribution System</p>
<p>Frequency varies within the range 48.0 to 49.5 Hz; and</p>
<p>(c) for a period of up to 5 minutes where the Distribution System</p>
<p>Frequency varies within the range 47.0 to 48.0 Hz.</p>
<p>7.7.2 The requirements of paragraph 7.7.1 do not apply where:</p>
<p>(a) the G59 relay has operated correctly, consistent with the settings agreed</p>
<p>pursuant to paragraph 7.8; or</p>
<p>(b) The Distribution System Frequency has changed at a rate greater than</p>
<p>0.5 Hz/s; or</p>
<p>(c) there is manual intervention by the Generator.</p>
<p>7.8 Agreement of rate-of-change-of-frequency settings</p>
<p>7.8.1 Where Generating Units are equipped with rate-of-change-of-frequency relays</p>
<p>or other devices which measure and operate in relation to a rate-of-change-of</p>
<p>frequency the procedure in paragraphs 7.8.2 to 7.8.5 below will be followed to</p>
<p>ensure satisfactory operation of the Generating Unit.</p>
<p>7.8.2 At a reasonable time prior to a Generating Unit being connected to the</p>
<p>Distribution System, and prior to any relevant modification to a Generating</p>
<p>Unit or any relevant Power Station Equipment, the Generator shall contact</p>
<p>the DNO with details of the proposed rate-of-change-of-frequency setting.</p>
<p>7.8.3 The DNO shall, within a reasonable period and in any case no more than 28</p>
<p>days after being contacted pursuant to paragraph 7.8.2, discuss with the</p>
<p>Generator whether the proposed settings are satisfactory. The agreed settings</p>
<p>shall be specified in the Connection Agreement.</p>
<p>7.8.4 In relation to any Generator which has agreed the settings with the DNO under</p>
<p>these provisions, the DNO shall notify that Generator of any change of which it</p>
<p>is aware in the expected rate-of-change-of-frequency on the Distribution</p>
<p>System which may require new settings to be agreed.</p>
<p>7.8.5 Each Generator shall be responsible for protecting the Generating Unit owned</p>
<p>or operated by it against the risk of damage which might result from any</p>
<p>Frequency excursion outside the range 52 Hz to 47 Hz and for deciding</p>
<p>whether or not to interrupt the connection between its Plant and/or Apparatus</p>
<p>and the Distribution System in the event of such a Frequency excursion.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 36</p>
<p>7.9 Generating Unit control arrangements</p>
<p>7.9.1 All Generating Units in use after 1 January 2010 must be fitted with a device</p>
<p>capable of setting the power factor of the Generating Unit within the relevant</p>
<p>range, as set out in paragraph 7.4.</p>
<p>7.9.2 All Generating Units first connected on or after 1 January 2010 with an</p>
<p>Output of 100kW or more, all WFPSs with an Output of 5MW or more first</p>
<p>connected on or after 1 November 2007 and all Generating Units with an</p>
<p>Output of 10 MW or more (other than WFPSs) connected to the Distribution</p>
<p>System since 31 March 1992, must be fitted with a fast acting control system</p>
<p>capable of being switched between Voltage Control mode and power factor</p>
<p>control mode within a voltage band as specified within the Connection</p>
<p>Agreement for the particular site, and in any case within statutory limits as</p>
<p>specified under paragraph 5.3. If the voltage is outside the specified limit the</p>
<p>power factor control must revert to Voltage Control. The control of voltage and</p>
<p>power factor must ensure stable operation over the entire operating range of the</p>
<p>Generating Unit. In the event that action by the Generating Unit Active and</p>
<p>Reactive Power control functions is unable to achieve a sustained voltage within</p>
<p>the statutory limits, the Generating Unit must detect this and immediately shut</p>
<p>down.</p>
<p>7.9.3 Where a WFPS is connected to the Distribution System through the same</p>
<p>transformer as a Demand Customer or Demand Customers, the Generator</p>
<p>may be required to install a power factor control loop as further provided in the</p>
<p>Connection Agreement. The power factor control loop should be designed to</p>
<p>be slow acting to allow the Voltage Control loop to respond to transient voltage</p>
<p>changes. Where a transient voltage change occurs, the power factor control loop</p>
<p>must restore the voltage to the set value over a period of 1 minute.</p>
<p>7.9.4 Other Voltage Control schemes may be possible, but agreement between the</p>
<p>Generator and the DNO must be reached at the application stage for connection</p>
<p>about their suitability. If Voltage Control is implemented for the Controllable</p>
<p>WFPS or Dispatchable WFPS, rather than on individual wind turbines, then</p>
<p>the range of power factor available should not be less than that which would</p>
<p>have been available if Voltage Control had been on individual wind turbines.</p>
<p>Voltage Control schemes based upon equipment located on the DNO’s side of</p>
<p>the connection may be possible, but such schemes are considered special, and</p>
<p>the details, responsibilities and cost schedule must be agreed between the</p>
<p>Generator and the DNO in the Connection Agreement.</p>
<p>7.10 Generating Unit SCADA and control</p>
<p>7.10.1 Generators shall in respect of their Generating Units in any of the following</p>
<p>three categories comply with the SCADA signal requirements set out in this</p>
<p>paragraph 7.10 and, in addition, such other SCADA signal requirements as the</p>
<p>DNO may require because of network reasons, which will be specified prior to</p>
<p>entry into the Connection Agreement:</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 37</p>
<p>(a) Generating Units with an Output of 1MW or more which are first</p>
<p>connected after 1 January 2010;</p>
<p>(b) Generating Units with an Output of 100kW or more up to 1MW which</p>
<p>are first connected after 1 January 2010 where the DNO decides that</p>
<p>SCADA is required because of local network reasons; and</p>
<p>(c) Generating Units with an Output of 5MW or more which were</p>
<p>connected prior to 1 January 2010.</p>
<p>7.10.2 The DNO shall issue control instructions by means of the SCADA signals set</p>
<p>out below or, in the event of a SCADA malfunction, such other means as are</p>
<p>determined by the DNO in consultation with the User.</p>
<p>7.10.3 The User shall acknowledge, where relevant, receipt of a control instruction</p>
<p>issued under this paragraph 7.10 and shall comply promptly with the control</p>
<p>instruction.</p>
<p>7.10.4 The following signal formats shall be used where required by the particular</p>
<p>connection:</p>
<p>(a) Analogue signals: 4 to 20 mA</p>
<p>(b) Digital pulse from the DNO: 24V dc</p>
<p>(c) Digital input from the User: 0 and 24V dc</p>
<p>7.10.5 Analogue signals:</p>
<p><em>Ref Quantity Comment From To</em></p>
<p>1 Voltage Voltage set point instruction DNO User</p>
<p>2 Voltage Confirmation of voltage set point User DNO</p>
<p>3 Set Point Power factor set point instruction DNO User</p>
<p>4 Set Point</p>
<p>Confirmation of power factor set point</p>
<p>instruction</p>
<p>User DNO</p>
<p>7.10.6 Digital signals:</p>
<p><em>Ref Quantity Comment From To</em></p>
<p>1</p>
<p>Voltage Control</p>
<p>Select</p>
<p>To operate in Voltage Control mode DNO User</p>
<p>2</p>
<p>Voltage Control</p>
<p>Selected</p>
<p>Acknowledgement signal that the</p>
<p>Generating Unit is in Voltage Control</p>
<p>mode.</p>
<p>User DNO</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 38</p>
<p><em>Ref Quantity Comment From To</em></p>
<p>3 PF Control Select</p>
<p>To operate in power factor control</p>
<p>mode</p>
<p>DNO User</p>
<p>4 PF Control Selected</p>
<p>Acknowledgement signal that the</p>
<p>Generating Unit is in power factor</p>
<p>control mode.</p>
<p>User DNO</p>
<p>5</p>
<p>Voltage Control</p>
<p>Auto Change Over</p>
<p>Indication that the control mode has</p>
<p>changed to Voltage Control.</p>
<p>User DNO</p>
<p>6 Island Detected Trip</p>
<p>Indication that the G59 protection has</p>
<p>operated.</p>
<p>User DNO</p>
<p>7.10.7 Analogue signals applicable to WFPSs with Registered Capacities of less than</p>
<p>5MW and greater than or equal to 1MW:</p>
<p><em>Ref Quantity Comment From To</em></p>
<p>1 Wind Speed</p>
<p>Indication of wind speed at WFPS, measured</p>
<p>at a location agreed between the generator</p>
<p>and the DNO.</p>
<p>User DNO</p>
<p>2 Wind Direction</p>
<p>Indication of wind direction at WFPS,</p>
<p>measured at a location agreed between the</p>
<p>generator and the DNO.</p>
<p>User DNO</p>
<p>7.11 Neutral Earthing</p>
<p>7.11.1 The winding configuration and method of Earthing of Generating Units and</p>
<p>associated Generator Transformers shall be agreed with the DNO or, if</p>
<p>agreement cannot be reached, determined by the DNO.</p>
<p>8 Technical Criteria for Communications</p>
<p>8.1 Communications equipment</p>
<p>8.1.1 Where required by the DNO in order to ensure control of the Distribution</p>
<p>System, communications between Users and the DNO shall be established in</p>
<p>accordance with the relevant Connection Agreement.</p>
<p>8.2 Telemetry</p>
<p>8.2.1 In addition to the requirements of the Distribution Metering Code, each User</p>
<p>shall provide such voltage, current, Frequency, Active and Reactive Power</p>
<p>measurements and status points and alarms and controls at the DNO telemetry</p>
<p>outstation interface (if any) as required and specified by the DNO in the relevant</p>
<p>Connection Agreement.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 39</p>
<p>8.2.2 If it is agreed between the DNO and a User that the DNO will telecontrol the</p>
<p>User’s switchgear on the User’s Site, the DNO shall install the necessary</p>
<p>telecontrol facilities. It shall be the responsibility of the User to provide the</p>
<p>necessary control interface for the switchgear of the User which is to be</p>
<p>controlled.</p>
<p>8.3 Telecontrol connection standards</p>
<p>8.3.1 All communication connections between each User and the DNO shall conform</p>
<p>to:</p>
<p>(a) appropriate Telecommunication Standardization Sector (ITU-T)</p>
<p>standards and other standards required by licensed public telephone</p>
<p>operators; and/or</p>
<p>(b) appropriate standards for radio systems as required by Ofcom from time</p>
<p>to time.</p>
<p>8.3.2 In respect of (b) above, each User shall, except to the extent that an alternative</p>
<p>means of communication has been agreed with the DNO in a Connection</p>
<p>Agreement, provide where required by the DNO, as set out in the DNO’s</p>
<p>connection offer, facilities on which a small radio aerial can be mounted and</p>
<p>shall obtain where necessary any planning permissions required therefor.</p>
<p>9 Site Related Conditions</p>
<p>9.1 Ownership, control, operation &amp; maintenance at the Connection Point</p>
<p>9.1.1 The ownership boundary between the Distribution System and a User’s System</p>
<p>shall be agreed between the User and the DNO. For supplies at Low Voltage</p>
<p>the general rule is that the ownership boundary will be at the User’s terminals of</p>
<p>the DNO owned metering equipment. For High Voltage supplies and busbar</p>
<p>connected supplies at Low Voltage, the ownership boundary will be subject to</p>
<p>specific agreement between the DNO and the User in each case.</p>
<p>9.1.2 In the absence of a separate written agreement between the parties to the</p>
<p>contrary, construction, commissioning, control, operation and maintenance</p>
<p>responsibilities follow ownership.</p>
<p>9.1.3 For connections to the Distribution System for which a Connection</p>
<p>Agreement is required and those covered by regulation 26 and parts 1 and 2 of</p>
<p>schedule 3 of the Electricity Supply Regulations (N.I.) 1991, as amended or restated</p>
<p>from time to time, a Site Responsibility Schedule shall be prepared by</p>
<p>the DNO (reflecting the details agreed between the DNO and the User) in</p>
<p>respect of each Connection Site pursuant to the relevant Connection</p>
<p>Agreement and signed by both parties (by way of confirmation of its accuracy),</p>
<p>detailing the division of responsibilities at interface sites in respect of</p>
<p>ownership, control, operation, maintenance and safety. The format, principles</p>
<p>and basic procedure to be used in the preparation of Site Responsibility</p>
<p>Schedules are set down in Appendix 1.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 40</p>
<p>9.1.4 An Ownership Diagram shall be included in the above Site Responsibility</p>
<p>Schedule. The diagram shall show all HV Apparatus and the connections to all</p>
<p>external circuits and shall incorporate numbering, nomenclature and labelling as</p>
<p>set out in OC9. A guide to the types of HV Apparatus to be shown in the</p>
<p>Ownership Diagram is shown in Appendix 2 together with the principles to be</p>
<p>followed in the preparation of the diagram and the preferred graphical symbols</p>
<p>to be used.</p>
<p>9.1.5 A copy of the Site Responsibility Schedule and any Ownership Diagrams</p>
<p>shall be retained by the DNO and by the User.</p>
<p>9.1.6 The User shall notify the DNO of any changes at or relating to the Connection</p>
<p>Site which may affect the Site Responsibility Schedule or Ownership</p>
<p>Diagrams and the DNO shall carry out any necessary updating and the</p>
<p>principles set out in paragraph 9.1.3 shall apply to such updating.</p>
<p>9.2 Access to Sites</p>
<p>The provisions relating to access to DNO Sites by Users and to User’s Sites by</p>
<p>members or representatives of the DNO shall be set out in the relevant Connection</p>
<p>Agreement and/or lease.</p>
<p>9.3 Work on Protection at Connection Points</p>
<p>No busbar Protection, mesh corner Protection, circuit breaker fail Protection, AC or</p>
<p>DC wiring (other than power supplies or DC tripping associated with a Generating</p>
<p>Unit) at a Connection Point shall be worked upon or altered by or on behalf of a User</p>
<p>unless the DNO has been given a reasonable opportunity to arrange for a DNO</p>
<p>representative to attend. The DNO shall not work upon or alter any Generating Unit</p>
<p>Protection unless it has given the Generator a reasonable opportunity for a</p>
<p>representative of the Generator to attend.</p>
<p>9.4 Standard of maintenance</p>
<p>9.4.1 It is a requirement that all User’s Plant and Apparatus on DNO Sites is</p>
<p>maintained adequately for the purpose for which it is intended and to ensure that</p>
<p>it does not pose a threat to the safety of any of DNO’s Plant, Apparatus or</p>
<p>personnel on the DNO Site.</p>
<p>9.4.2 The DNO shall ensure that all of the Distribution System Plant and Apparatus</p>
<p>on Users&#8217; Sites is maintained adequately for the purpose for which it is intended</p>
<p>and to ensure that it does not pose a threat to the safety of any User’s Plant,</p>
<p>Apparatus or personnel on the User’s Site.</p>
<p>9.4.3 The DNO or the User (as the case may be) will have the right to inspect the test</p>
<p>results and maintenance records relating to such Plant and Apparatus at any</p>
<p>time.</p>
<p>9.5 Responsibility for safety</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 41</p>
<p>9.5.1 The Site Responsibility Schedule referred to in paragraph 9.1.3 shall detail the</p>
<p>demarcation of responsibility for safety of persons carrying out work or testing</p>
<p>at Connection Sites and on circuits which cross a Connection Site at any point.</p>
<p>9.5.2 More detailed information on procedures and responsibilities involved in the</p>
<p>provision of Safety Precautions is set out in OC6.</p>
<p>10 Approval To Connect</p>
<p>10.1 Readiness to connect</p>
<p>10.1.1 A User whose development is under construction in accordance with the</p>
<p>relevant Connection Agreement and who wishes to establish a connection, or to</p>
<p>modify an existing connection, to the Distribution System shall apply to the</p>
<p>DNO by submitting a standard connection card or otherwise in writing, stating</p>
<p>readiness to connect and giving the following:-</p>
<p>(a) confirmation that the User’s installation complies with the principles</p>
<p>outlined in Regulation 28 of the Electricity Supply Regulations (N.I.)</p>
<p>1991 and Regulations 4-12 and 15 of the Electricity at Work Regulations</p>
<p>(N.I.) 1991 (or as amended or re-stated);</p>
<p>(b) where relevant, updated Planning Code data based on actual values; and</p>
<p>(c) a proposed connection date.</p>
<p>10.1.2 The DNO may require a User to provide in addition to its written application to</p>
<p>the DNO for connection in accordance with paragraph 10.1.1, a report,</p>
<p>prepared by such person as the DNO may reasonably consider to be competent</p>
<p>to issue the same, certifying to the DNO that all matters required by paragraph</p>
<p>5 have been considered and that paragraphs 6 to 8 inclusive have been complied</p>
<p>with by the User and incorporating:-</p>
<p>(a) all available type test reports and test certificates produced by Nationally</p>
<p>Accredited Laboratories (or other equivalent testing organisations)</p>
<p>showing that the Plant and Apparatus specified in the Connection</p>
<p>Conditions meets the criteria specified;</p>
<p>(b) copies of the manufacturer&#8217;s test certificates relating to Plant and</p>
<p>Apparatus referred to in the Connection Conditions, including</p>
<p>measurements of positive and zero sequence impedance of Apparatus</p>
<p>which will contribute to the fault current at the Connection Point;</p>
<p>(c) details of Protection arrangements and settings;</p>
<p>(d) a certificate declaring the maximum short circuit current in amperes</p>
<p>which the User’s System would contribute to a three-phase short circuit</p>
<p>at the Connection Point, and the minimum zero sequence impedance of</p>
<p>the User’s System at the Connection Point and taking into account the</p>
<p>contributions of any Generating Unit or Power Station motors and</p>
<p>transformers; and</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 42</p>
<p>(e) confirmation that designs conform to the standards referred to in</p>
<p>paragraph 6.</p>
<p>10.1.3 A User shall supply the following information to the DNO together with its</p>
<p>notification under paragraph 10.1.1:-</p>
<p>(a) a list of persons proposed to be appointed by the User to undertake, and</p>
<p>to be responsible for, the application and removal of Safety Precautions</p>
<p>on those parts of the User’s System which are directly connected to the</p>
<p>Distribution System, in accordance with OC6;</p>
<p>(b) a list of persons appointed by the User to undertake operational duties on</p>
<p>the User’s System and to issue and receive operational messages and</p>
<p>instructions in relation to the User’s System;</p>
<p>(c) a list of names and telephone numbers of responsible management</p>
<p>representatives in accordance with OC7;</p>
<p>(d) site common drawings as specified in the Connection Agreement;</p>
<p>(e) a single line diagram of the User’s Apparatus showing all items to</p>
<p>which these Connection Conditions apply; and</p>
<p>(f) information to enable the DNO to prepare a Site Responsibility</p>
<p>Schedule.</p>
<p>10.1.4 In order that the DNO may verify that the requirements of these Connection</p>
<p>Conditions can be met, the User shall provide a proposed commissioning</p>
<p>programme, giving at least six weeks (or such longer period as the DNO may</p>
<p>reasonably consider to be appropriate in the circumstances) notice of the</p>
<p>proposed connection date, and detailing all proposed site testing of main and</p>
<p>ancillary equipment, together with the names of the organisations which are to</p>
<p>carry out such testing and the proposed timetable for such testing. The required</p>
<p>period of notice will be notified to the User by the DNO during the course of an</p>
<p>application for connection. The DNO will consider the proposed commissioning</p>
<p>programme and, as soon as reasonably practicable, will notify the User:-</p>
<p>(a) that it approves the programme, in which case the DNO and the User</p>
<p>shall take all reasonable steps to ensure that the</p>
<p>Commissioning/Acceptance Testing is undertaken in accordance with</p>
<p>the commissioning programme (subject to Distribution System</p>
<p>conditions); or</p>
<p>(b) that it considers that the Commissioning/Acceptance Testing proposed</p>
<p>in the programme may involve the application of irregular, unusual or</p>
<p>extreme conditions and which may have a material effect on the</p>
<p>Distribution System, beyond the User’s System and that such testing</p>
<p>therefore falls within the scope of OC10, &#8220;System Tests&#8221;, in which</p>
<p>event the proposed commissioning programme shall be treated as a</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 43</p>
<p>Proposal Notice submitted under paragraph 4.1 of OC10 and the</p>
<p>relevant provisions of OC10 shall apply to the proposed testing; or</p>
<p>(c) that it requires the proposed commissioning programme to be amended</p>
<p>in which event the User and the DNO shall endeavour to agree an</p>
<p>appropriate amendment to the commissioning programme, failing which</p>
<p>the programme will be as determined by the DNO acting reasonably and,</p>
<p>in either case, the DNO and the User shall take all reasonable steps to</p>
<p>ensure that the Commissioning/Acceptance Testing is undertaken in</p>
<p>accordance with the commissioning programme as amended; or</p>
<p>(d) that it rejects the proposed commissioning programme and the reasons</p>
<p>for such rejection in which event, subject to the resolution of any dispute</p>
<p>in accordance with the relevant Connection Agreement, the proposed</p>
<p>Commissioning/Acceptance Testing shall not take place but the User</p>
<p>shall be entitled to submit a revised commissioning programme for the</p>
<p>DNO’s consideration.</p>
<p>10.1.5 The DNO shall be entitled to witness site testing of equipment whose</p>
<p>performance can reasonably be regarded as affecting the integrity of the</p>
<p>Distribution System. The User shall provide the DNO with certified results of</p>
<p>all such tests and the DNO may withhold agreement to energise the User’s</p>
<p>Equipment where test results establish that the Connection Conditions have</p>
<p>not been complied with.</p>
<p>10.1.6 Where in advance of the proposed connection date, a Generator requires</p>
<p>connection to the Distribution System for the purpose of testing, the Generator</p>
<p>will be required to satisfy the DNO of the following:-</p>
<p>(a) compliance with those requirements of the Connection Conditions and</p>
<p>Connection Agreement necessary to give assurance that it is safe to</p>
<p>connect; and</p>
<p>(b) where applicable, provision of a commissioning programme in</p>
<p>accordance with paragraph 10.1.4.</p>
<p>10.2 Confirmation of approval to connect</p>
<p>10.2.1 Within 30 days of notification by a User pursuant to paragraph 10.1.1 the DNO</p>
<p>shall (except where it has rejected the User’s application in accordance with</p>
<p>paragraph 10.1.4(d)) inform the User whether or not the requirements of</p>
<p>paragraph 10.1 and the other requirements of the Connection Conditions are</p>
<p>satisfied and the making of the connection is approved subject to satisfactory</p>
<p>results of those tests (including Commissioning/Acceptance Tests) which</p>
<p>cannot be performed prior to energisation of the User’s Plant and Apparatus.</p>
<p>Where approval is withheld, reasons shall be stated by the DNO.</p>
<p>10.2.2 Where the notification given by the DNO pursuant to paragraph 10.2.1 is in the</p>
<p>affirmative, the DNO will in addition supply to the User the following</p>
<p>information:-</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 44</p>
<p>(a) a list of persons appointed by the DNO to undertake, and to be</p>
<p>responsible for, the application and removal of Safety Precautions in</p>
<p>relation to the Connection Site, in accordance with OC6;</p>
<p>(b) a list of persons appointed by the DNO to undertake operational duties</p>
<p>on the Distribution System and to issue and receive operational</p>
<p>messages and instructions in relation to the User’s System; and</p>
<p>(c) list of names and telephone numbers of responsible management</p>
<p>representatives in accordance with OC7.</p>
<p>10.2.3 When indicating agreement to the energising of a connection, the DNO shall, to</p>
<p>the extent not previously determined in a commissioning programme, specify</p>
<p>the contents and sequence of the energising programme and associated testing.</p>
<p>In either case, the DNO shall be entitled to postpone or suspend the programme</p>
<p>where, due to circumstances which could not reasonably have been foreseen by</p>
<p>the DNO, continuation of the programme would impose an unacceptable level of</p>
<p>risk to the integrity of the Distribution System.</p>
<p>10.3 Approval of staff</p>
<p>10.3.1 At the same time that the User submits to the DNO in relation to safety</p>
<p>requirements the list of information pursuant to paragraph 10.1.3, it shall submit</p>
<p>to the DNO a list of staff which will be used to implement Safety Precautions.</p>
<p>The DNO may ask the User questions to clarify the suitability of persons named</p>
<p>on the list.</p>
<p>10.3.2 At the same time that the DNO submits to the User the list of information</p>
<p>pursuant to paragraph 10.2.2 it shall submit to the User a list of DNO staff</p>
<p>which will be used to implement Safety Precautions. The User may ask the</p>
<p>DNO questions to clarify the suitability of persons named on the list.</p>
<p>10.3.3 The DNO and each User have the right to object to the inclusion of particular</p>
<p>members of staff on the other&#8217;s list, on technical grounds, and in the event of</p>
<p>objection which is accepted by the other, that member of staff will not be used</p>
<p>to implement Safety Precautions.</p>
<p>10.3.4 A party must accept an objection to the extent it is reasonable to do so. In the</p>
<p>event of a disagreement, the disputes resolution procedure in the relevant</p>
<p>Connection Agreement will be used.</p>
<p>10.3.5 As part of the approval process, each party may (upon reasonable notice and at</p>
<p>reasonable times) interview members of staff on the other&#8217;s list or the parties</p>
<p>may agree to hold joint interviews.</p>
<p>10.3.6 If the list of the DNO or a User, as the case may be, changes, the relevant party</p>
<p>must notify the other without delay and the relevant provisions of this paragraph</p>
<p>10.3 shall apply to any new names included as part of that change.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 45</p>
<p>10.3.7 Neither the DNO nor any User shall have any liability to the other by reason of</p>
<p>or arising from their approval under this paragraph 10.3 of the other&#8217;s list of</p>
<p>staff entitled to implement Safety Precautions.</p>
<p>11 Connection Conditions compliance testing</p>
<p>11.1 The DNO will specify to each User the testing to be undertaken to demonstrate</p>
<p>compliance with the Connection Conditions in relation to a particular connection. The</p>
<p>specification and the timing of the test will be consistent with the overall requirements,</p>
<p>including timing of the Connection Agreement. The following sets out the</p>
<p>requirements for testing for Generators and Demand Customers.</p>
<p>11.2 Generator Testing</p>
<p>11.2.1 The testing will be undertaken in three phases:</p>
<p>(a) Phase 1 – Pre-energisation</p>
<p>(b) Phase 2 – Post-energisation</p>
<p>(c) Phase 3 – Post-energisation monitoring.</p>
<p>11.3 Phase 1 – Pre-energisation</p>
<p>11.3.1 The testing in Phase 1 will require the Generator to demonstrate, in the</p>
<p>presence of a representative of the DNO, compliance with requirements</p>
<p>specified by the DNO as being the relevant parts of the Connection Conditions</p>
<p>against which compliance needs to be demonstrated.</p>
<p>11.3.2 A Pre-energisation Connection Report shall be completed by the Generator to</p>
<p>the satisfaction of the DNO, demonstrating compliance, which will include such</p>
<p>information as the DNO may reasonably specify.</p>
<p>11.4 Phase 2 – Post-energisation</p>
<p>11.4.1 Phase 2 covers certain tests which require to be witnessed by a representative of</p>
<p>the DNO within six months (or such other period may reasonably be specified</p>
<p>by the DNO) of energisation. The tests will be specified by the DNO, and will</p>
<p>be based on the individual test descriptions as set out in the Connection</p>
<p>Agreement, and such further tests as the DNO may reasonably specify to</p>
<p>demonstrate compliance with the Connection Conditions.</p>
<p>11.4.2 The tests in Phase 2 will be based on an on-site demonstration of the operation</p>
<p>of the Power Station. Any test which relies upon some level of generation may</p>
<p>be replaced with either a simulated power output signal or be demonstrated</p>
<p>through the analysis of individual turbine event logs to confirm receipt of the</p>
<p>appropriate control signal, in each case subject to the reasonable agreement of</p>
<p>the DNO to such alternative approach.</p>
<p>11.4.3 In the event that conditions (relating to wind or the conditions on the network</p>
<p>generally) do not allow the test to be performed, then a demonstration of the</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 46</p>
<p>control functionality would normally be sufficient to demonstrate compliance</p>
<p>with Phase 2, subject to the agreement of the DNO. The DNO may agree that</p>
<p>any physical tests were not completed as part of the Phase 2 witness tests will be</p>
<p>included in the Phase 3 monitoring phase.</p>
<p>11.5 Phase 3 – Post-energisation Monitoring</p>
<p>11.5.1 The operation of the Power Station over a range of conditions will be</p>
<p>confirmed by operational monitoring in Phase 3. During the twelve month</p>
<p>period after energisation, a number of operations, as specified by the DNO, will</p>
<p>be required. The results of monitoring the performance of those operations will</p>
<p>be included in the Final Connection Report. The operational monitoring period</p>
<p>of Phase 3 will be required to confirm to the DNO’s reasonable satisfaction the</p>
<p>Power Station’s and its individual Plant and/or Apparatus’ behaviour and</p>
<p>capability under various conditions and subject to disturbances, which generally</p>
<p>cannot be simulated during the commissioning tests. The undertaking of the</p>
<p>operational monitoring will require the installation of an event recorder or</p>
<p>similar device by the DNO at or near to the Connection Point.</p>
<p>11.5.2 If the relevant conditions necessary to complete the Phase 3 are not experienced</p>
<p>during the twelve months following energisation, then nevertheless the final</p>
<p>compliance certificate will be issued by the DNO at the expiration of that twelve</p>
<p>month period.</p>
<p>11.6 Demand Customer Testing</p>
<p>In the case of Demand Customers a Pre-energisation Connection Report will be</p>
<p>completed by the User to the satisfaction of the DNO, which includes such information</p>
<p>as may be reasonably specified by the DNO to demonstrate compliance with the</p>
<p>Connection Conditions and any other relevant part of the Distribution Code.</p>
<p>12 Fuel Security Code</p>
<p>Each Generator agrees to comply with the Fuel Security Code to the extent that it is</p>
<p>expressed to apply to it and with any instructions from the DNO or the TSO pursuant</p>
<p>to the Fuel Security Code.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 47</p>
<p>APPENDIX 1</p>
<p>FORMAT, PRINCIPLES AND BASIC PROCEDURE TO BE USED IN THE PREPARATION OF SITE</p>
<p>RESPONSIBILITY SCHEDULES</p>
<p>1 Principles</p>
<p>1.1 Site Responsibility Schedules shall be drawn up covering the following:</p>
<p>(a) Schedule of HV Apparatus;</p>
<p>(b) Schedule of Plant, LV/MV Apparatus, services and supplies;</p>
<p>(c) Schedule of telecommunications and measurements Apparatus.</p>
<p>Other than at Generating Unit and Power Station locations (including WFPSs), the</p>
<p>schedules referred to in (b) and (c) may be combined.</p>
<p>1.2 Each Site Responsibility Schedule for a Connection Site shall be prepared by the</p>
<p>DNO in consultation with other Users at least 2 weeks prior to the date for connection</p>
<p>proposed by the User pursuant to paragraph 10.1.1(c) in the Connection Conditions.</p>
<p>Each User shall provide information to the DNO to enable it to prepare the Site</p>
<p>Responsibility Schedule.</p>
<p>1.3 Each Site Responsibility Schedule shall detail for each item of Plant and Apparatus:-</p>
<p>(a) Plant/Apparatus ownership;</p>
<p>(b) Site Manager;</p>
<p>(c) Safety (applicable Safety Rules and Control Person or other responsible person</p>
<p>(Safety Co-ordinator), or such other person who is responsible for safety);</p>
<p>(d) Operations (applicable Operational Procedures and control engineer);</p>
<p>(e) Responsibility to undertake maintenance.</p>
<p>Each Connection Point shall be precisely shown.</p>
<p>1.4 In the case of Site Responsibility Schedules referred to in paragraph 1.1 (b) and (c),</p>
<p>with the exception of Protection and Intertrip Apparatus operation, it will be</p>
<p>sufficient to indicate the responsible User or the DNO as the case may be. In the case</p>
<p>of the Site Responsibility Schedule referred to in 1.1 (a) for Protection and Intertrip</p>
<p>Apparatus, the responsible management unit must be shown in addition to the User or</p>
<p>the DNO as the case may be.</p>
<p>1.5 The HV Apparatus Site Responsibility Schedule for each Connection Site must</p>
<p>include lines and cables emanating from the Connection Site.</p>
<p>1.6 Every page of each Site Responsibility Schedule shall bear the date of issue and the</p>
<p>issue number.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 48</p>
<p>1.7 When a Site Responsibility Schedule is prepared it shall be sent by the DNO to the</p>
<p>Users involved for confirmation of its accuracy</p>
<p>1.8 The Site Responsibility Schedule shall then be signed on behalf of the DNO by the</p>
<p>Manager responsible and on behalf of each User involved by its Responsible Manager</p>
<p>(see paragraph 3.1), by way of written confirmation of its accuracy if they agree on its</p>
<p>accuracy.</p>
<p>1.9 Once signed, two copies will be distributed by the DNO, not less than two weeks prior</p>
<p>to its implementation date, to each User which is a party on the Site Responsibility</p>
<p>Schedule, accompanied by a note indicating the issue number and the date of</p>
<p>implementation.</p>
<p>1.10 The DNO and Users must make the Site Responsibility Schedules readily available to</p>
<p>their respective operational staff at the Site.</p>
<p>2 Alterations to existing Site Responsibility Schedules</p>
<p>2.1 Without prejudice to the provisions of paragraph 2.4, when a User identified on a Site</p>
<p>Responsibility Schedule becomes aware that an alteration is necessary, it must inform</p>
<p>the DNO immediately and in any event 8 weeks prior to any change taking effect (or as</p>
<p>soon as possible after becoming aware of it, if less than 8 weeks remain when the User</p>
<p>becomes aware of the change).</p>
<p>2.2 Where the DNO has been informed of a change by a User, or itself proposes a change,</p>
<p>it will prepare a revised Site Responsibility Schedule by not less than six weeks prior</p>
<p>to the change taking effect (subject to it having been informed or knowing of the change</p>
<p>eight weeks prior to that time) and the procedure set out in paragraph 1.7 shall be</p>
<p>followed with regard to the revised Site Responsibility Schedule.</p>
<p>2.3 The revised Site Responsibility Schedule shall then be signed in accordance with the</p>
<p>procedure set out in paragraph 1.8 and distributed in accordance with the procedure set</p>
<p>out in paragraph 1.9, accompanied by a note indicating where the alteration(s) has/have</p>
<p>been made, the new issue number and the date of implementation.</p>
<p>2.4 When a User identified on a Site Responsibility Schedule, or the DNO, as the case</p>
<p>may be, becomes aware that an alteration to the Site Responsibility Schedule is</p>
<p>necessary urgently to reflect, for example, an emergency situation, the User shall notify</p>
<p>the DNO, or the DNO shall notify the User, as the case may be, immediately and will</p>
<p>discuss:</p>
<p>(a) what change is necessary to the Site Responsibility Schedule;</p>
<p>(b) whether the Site Responsibility Schedule is to be modified temporarily or</p>
<p>permanently; and</p>
<p>(c) the distribution of the revised Site Responsibility Schedule.</p>
<p>The DNO will prepare a revised Site Responsibility Schedule as soon as possible and</p>
<p>in any event within seven days of it being informed of or knowing the necessary</p>
<p>alteration. The Site Responsibility Schedule will be confirmed by Users and signed on</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 49</p>
<p>behalf of the DNO and Users (by the persons referred to in paragraph 1.8 of this</p>
<p>appendix) as soon as possible after it has been prepared and sent to Users for</p>
<p>confirmation.</p>
<p>3 Responsible Managers</p>
<p>3.1 Each User and the DNO shall, prior to the date for connection proposed by the User</p>
<p>pursuant to paragraph 10.1.1(c), exchange names and status of managers with authority</p>
<p>to sign Site Responsibility Schedules.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 50</p>
<p>APPENDIX 2</p>
<p>PROCEDURES RELATING TO OWNERSHIP DIAGRAMS</p>
<p>1 Basic Principles</p>
<p>(a) Where practicable, all the HV Apparatus on any Connection Site shall be</p>
<p>shown on one Ownership Diagram. Provided the clarity of the diagram is not</p>
<p>impaired, the layout shall represent as closely as possible the geographical</p>
<p>arrangement on the Connection Site.</p>
<p>(b) Where more than one Ownership Diagram is unavoidable, duplication of</p>
<p>identical information on more than one Ownership Diagram must be avoided.</p>
<p>(c) The Ownership Diagram must show accurately the current status of the</p>
<p>Apparatus, e.g. whether commissioned or decommissioned. Where</p>
<p>decommissioned, the associated switch bay will be labelled &#8220;spare bay&#8221;.</p>
<p>(d) Provision will be made on the Ownership Diagram for signifying approvals,</p>
<p>together with provision for details of revisions and dates.</p>
<p>(e) Ownership Diagrams will be prepared in A4 format or such other format as</p>
<p>may be agreed with the DNO.</p>
<p>2 Apparatus to be shown on Ownership Diagrams</p>
<p>1 Busbars</p>
<p>2 Circuit Breakers</p>
<p>3 Disconnector (Isolator) and Switch Disconnectors (Switching Isolators)</p>
<p>4 Disconnectors (Isolators) &#8211; Automatic Facilities</p>
<p>5 Bypass Facilities</p>
<p>6 Earthing Switches</p>
<p>7 Maintenance Earths</p>
<p>8 Overhead Line Entries</p>
<p>9 Overhead Line Traps</p>
<p>10 Cable and Cable Sealing Ends</p>
<p>11 Generating Unit</p>
<p>12 Generator Transformers</p>
<p>13 Generating Unit Transformers, Station Transformers, including the lower</p>
<p>voltage circuit-breakers</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 51</p>
<p>14 WFPS Transformers, including the lower voltage circuit-breakers</p>
<p>15 Synchronous Compensators</p>
<p>16 Static Variable Compensators</p>
<p>17 Capacitors (including Harmonic Filters)</p>
<p>18 Series or Shunt Reactors</p>
<p>19 Supergrid and Grid Transformers</p>
<p>20 Tertiary Windings</p>
<p>21 Earthing and Auxiliary Transformers</p>
<p>22 Three Phase VTs</p>
<p>23 Single Phase VT &amp; Phase Identity</p>
<p>24 High Accuracy VT and Phase Identity</p>
<p>25 Surge Arrestors/Diverters</p>
<p>26 Neutral Earthing Arrangements on HV Apparatus</p>
<p>27 Fault Throwing Devices</p>
<p>28 Quadrature Boosters</p>
<p>29 Arc Suppression Coils</p>
<p>30 Current Transformers (where separate items)</p>
<p>31 Wall Bushings</p>
<p>3 Recommended Graphical Symbols</p>
<p>Where appropriate, the recommended graphical symbols shown in the attachment to this</p>
<p>Appendix 2 shall be used in the preparation of an Ownership Diagram.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 52</p>
<p>APPENDIX 3</p>
<p>LIST OF LICENCE STANDARDS</p>
<p>1. ER-P2/5 &#8211; Security of Supply, dated October 1978, and NIE amendment sheet, Issue 2,</p>
<p>dated 7 August 1992.</p>
<p>2. PLM-SP-1 &#8211; Planning Standards of Security for the Connection of Generating Stations</p>
<p>to the System Issue 1, dated September 1975, and NIE amendment sheet Issue 2, dated</p>
<p>7 August 1992.</p>
<p>3. PLM-ST-4 &#8211; CEGB Criteria for System Transient Stability Studies Issue 1, dated</p>
<p>September 1975, and NIE amendment sheet Issue 2, dated 7 August 1992.</p>
<p>4. PLM-ST-9 &#8211; Voltage Criteria for the Design of the 400kV and 275kV Supergrid System</p>
<p>Issue 1, dated 1 December 1985 and NIE amendment sheet Issue 2, dated 7 August</p>
<p>1992.</p>
<p>5. ER-P28 &#8211; Planning limits for Voltage Fluctuations.</p>
<p>6. ER-P16 &#8211; EHV or HV Supplies to Induction Furnaces.</p>
<p>7. ER-P29 &#8211; Planning limits for Voltage Unbalance.</p>
<p>8. ER-G5/4- Limits for Harmonics.</p>
<p>9. ER-G12/2 &#8211; Application of Protective Multiple Earthing to Low Voltage Networks.</p>
<p>10. EPM-1 &#8211; Operational Standards of Security of Supply Issue 2, dated 30 June 1980.</p>
<p>Distribution Code 1 May 2010</p>
<p>Connection Conditions Page 53</p>
<p>Recommended Graphical Symbols</p>
<p>Distribution Code 1 May 2010</p>
<p>OC1 – Generation and Demand Forecasting Page 54</p>
<p>Operating Code 1 – Generation and Demand Forecasting</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 1 (“OC1”) is concerned with the provision of generation and</p>
<p>Demand forecasts by Users to the DNO in order for the DNO to ensure the proper,</p>
<p>safe and efficient operation of the Distribution System.</p>
<p>1.2 The DNO has an obligation under the Grid Code to provide generation forecasts to the</p>
<p>TSO in order that the TSO can match generation output with Demand. The forecasts</p>
<p>provided by Users under this OC1 will therefore also enable the DNO to comply with</p>
<p>those Grid Code requirements.</p>
<p>1.3 The DNO will be receiving data in respect of Generating Plant connected to the</p>
<p>Distribution System from the TSO under the Grid Code, and will be using that in</p>
<p>relation to the operation of the Distribution System.</p>
<p>2 Objective</p>
<p>2.1 The objectives of OC1 are to set out the requirements for Users to provide estimates to</p>
<p>the DNO to:-</p>
<p>(a) enable the DNO to operate the Distribution System in a proper, safe and</p>
<p>efficient manner and in accordance with its statutory and licence obligations;</p>
<p>and</p>
<p>(b) enable the DNO to comply with its obligations under the Grid Code to provide</p>
<p>generation forecasts to the TSO.</p>
<p>3 Scope</p>
<p>3.1 OC1 applies to the DNO and to Users. Users in OC1 means:</p>
<p>(a) Generators in respect of their Independent Generating Plant connected to the</p>
<p>Distribution System with a Registered Capacity of 1MW and above; and</p>
<p>(b) Demand Customers in respect of their Connections Sites with a Demand of</p>
<p>1MW and above.</p>
<p>4 Procedure</p>
<p>4.1 Each User must provide the following data to the DNO at the time and in the manner</p>
<p>specified:</p>
<p>4.1.1 Generator Loading profiles</p>
<p>Each Generator must, at the request of the DNO, in respect of each of its</p>
<p>Independent Generating Plants with a Registered Capacity of 1MW and</p>
<p>above, submit to the DNO in writing by 0900 hours on the day following the</p>
<p>day on which the request was made an estimate of the Generator Loading</p>
<p>profiles for such Independent Generating Plant for the following Schedule</p>
<p>Distribution Code 1 May 2010</p>
<p>OC1 – Generation and Demand Forecasting Page 55</p>
<p>Day, save that it will be for the following three Schedule Days when submitted</p>
<p>on a Friday and the next two Schedule Days when submitted on a Saturday (no</p>
<p>notice being required on a Sunday) and shall be for such longer period as the</p>
<p>DNO may specify, at least one week in advance, to cover holiday periods. Such</p>
<p>estimate will be in the form of half hourly output in MW for such Independent</p>
<p>Generating Plant; and</p>
<p>4.1.2 Demand profile</p>
<p>Each Demand Customer shall at the request of the DNO, in respect of each of</p>
<p>its Connection Sites with a Demand of 1MW and above, submit to the DNO in</p>
<p>writing by 0900 hours on the day following the day on which the request was</p>
<p>made an estimate of its Demand profiles for such Connection Sites for the</p>
<p>following Schedule Day, save that it will be for the next three Schedule Days</p>
<p>when given on a Friday and the next two Schedule Days when given on a</p>
<p>Saturday (no notice being required on a Sunday) and shall be for such longer</p>
<p>period as the DNO may specify, at least one week in advance, to cover holiday</p>
<p>periods. Such estimate will be in the form of half hourly Demand in MW for</p>
<p>such Connection Site.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC2 – Outage Planning Page 56</p>
<p>Operating Code 2 – Outage Planning</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 2 (“OC2”) is concerned with the co-ordination by the DNO of</p>
<p>planned Generating Unit Outages and Distribution System Outages through various</p>
<p>timescales to enable the efficient operation of the Distribution System.</p>
<p>1.2 OC2 sets out the data required by the DNO from Generators in order for the DNO to</p>
<p>carry out co-ordinated Outage planning and also sets out the information that will be</p>
<p>supplied by the DNO to certain Users.</p>
<p>1.3 In OC2 &#8220;Year 0&#8243; means the current calendar year at any time, Year 1 means the next</p>
<p>calendar year at any time, Year 2 means the calendar year after Year 1, etc.</p>
<p>2 Objective</p>
<p>2.1 The objectives of OC2 are to:</p>
<p>(a) set out the procedures, timetables and data exchange requirements for the coordination</p>
<p>of Generating Unit and Distribution System Outages in order to</p>
<p>enable the DNO to operate the Distribution System in accordance with its</p>
<p>statutory and licence obligations;</p>
<p>(b) set out the procedures, timetables and data exchange requirements regarding</p>
<p>information to be supplied by the DNO to Users; and</p>
<p>(c) enable the DNO to comply with its Grid Code requirements regarding the</p>
<p>provision of Generating Unit and Distribution System Outage information to</p>
<p>the TSO.</p>
<p>3 Scope</p>
<p>3.1 OC2 applies to the DNO and to Users. Users in OC2 means:</p>
<p>(a) Generators in respect of their Independent Generating Plant with a</p>
<p>Registered Capacity of 1MW and above, CDGUs and Controllable WFPSs,</p>
<p>in each case where connected to the Distribution System;</p>
<p>(b) Demand Customers in respect of their Connection Sites with a Demand of</p>
<p>10MW and above; and</p>
<p>(c) such other Demand Customers as the DNO decides should be informed of</p>
<p>Outage information.</p>
<p>4 Summary</p>
<p>4.1 Under OC2 the interaction between the DNO, Generators and Demand Customers</p>
<p>will be as follows:-</p>
<p>Distribution Code 1 May 2010</p>
<p>OC2 – Outage Planning Page 57</p>
<p>(a) each Generator and the DNO in respect of Outages of distribution</p>
<p>connected Independent Generating Plant</p>
<p>with a Registered Capacity of 1MW and</p>
<p>above;</p>
<p>(b) the DNO and each Generator in respect of Distribution System Outages</p>
<p>which may operationally affect Generators</p>
<p>with Independent Generating Plant with a</p>
<p>Registered Capacity of 1MW and above,</p>
<p>CDGUs or Controllable WFPSs connected</p>
<p>to the Distribution System; and</p>
<p>(c) the DNO and Demand Customers in respect of Distribution System Outages</p>
<p>which may operationally affect Demand</p>
<p>Customers with a Demand of 10MW and</p>
<p>above and such other Demand Customers</p>
<p>as the DNO may decide.</p>
<p>4.2 Each User must, in relation to all matters to be undertaken pursuant to this OC2, act</p>
<p>reasonably and in good faith.</p>
<p>4.3 The DNO must, in relation to all matters to be undertaken pursuant to this OC2, act</p>
<p>reasonably and in good faith in the discharge of its obligations.</p>
<p>5 Outage planning procedures for Generators with Independent Generating Plant</p>
<p>with a Registered Capacity of 1MW and above</p>
<p>5.1 Planning for Year 1</p>
<p>5.1.1 By the end of July in each calendar year each Generator in respect of its</p>
<p>Independent Generating Plant with a Registered Capacity of 1MW and</p>
<p>above connected to the Distribution System shall provide the DNO in writing</p>
<p>with its indicative Outage programmes for Year 1.</p>
<p>5.1.2 The indicative Outage programme shall contain the planned Start Date,</p>
<p>planned Finish Date and the Output reduction.</p>
<p>5.2 Planning for Year 0</p>
<p>5.2.1 Each Generator in respect of its Independent Generating Plant with a</p>
<p>Registered Capacity of 1MW and above connected to the Distribution System</p>
<p>shall develop and keep up to date its Outage programme for Year 0.</p>
<p>5.2.2 On request by the DNO, each Generator in respect of its Independent</p>
<p>Generating Plant with a Registered Capacity of 1MW and above connected to</p>
<p>the Distribution System shall as soon as reasonably practicable following the</p>
<p>request provide the DNO in writing with the most up to date version of its</p>
<p>Outage programme for Year 0.</p>
<p>5.2.3 The Outage programme shall contain the planned Start Date, Finish Date and</p>
<p>the Output reduction.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC2 – Outage Planning Page 58</p>
<p>6 Outage Planning Procedures for Distribution System Outages</p>
<p>6.1 Planning for Year 1</p>
<p>6.1.1 By the end of May in each calendar year the DNO shall have prepared a plan of</p>
<p>Distribution System Outages scheduled to take place in Year 1 relating to</p>
<p>construction, refurbishment and maintenance works.</p>
<p>6.1.2 By the end of June in each calendar year the DNO shall notify in writing:</p>
<p>(a) each Generator with Independent Generating Plant with a Registered</p>
<p>Capacity of 1MW and above connected to the Distribution System;</p>
<p>(b) each Generator with a CDGU or a Controllable WFPS connected to</p>
<p>the Distribution System;</p>
<p>(c) each Demand Customer with a Demand of 10MW or above; and</p>
<p>(d) such other Demand Customers as the DNO may decide,</p>
<p>of those aspects of the plan which may operationally affect such Users in Year</p>
<p>1. The notification shall include proposed Start Dates and Finish Dates of</p>
<p>relevant Distribution System Outages.</p>
<p>6.1.3 The DNO will indicate to each Generator where a need may exist to use</p>
<p>Intertripping or other measures to allow the security of the Distribution</p>
<p>System to be maintained within the Licence Standards.</p>
<p>6.2 Planning in Year 0</p>
<p>6.2.1 The DNO shall develop and keep up to date the Distribution System Outage</p>
<p>plan for Year 0.</p>
<p>6.2.2 By 11.00 hours each Thursday the DNO shall notify in writing:</p>
<p>(a) each Generator with Independent Generating Plant with a Registered</p>
<p>Capacity of 1MW and above connected to the Distribution System;</p>
<p>(b) each Generator with a CDGU or a Controllable WFPS connected to</p>
<p>the Distribution System;</p>
<p>(c) Each Demand Customer with a Demand of 10MW or above; and</p>
<p>(d) such other Demand Customers as the DNO may decide,</p>
<p>of those aspects of the plan which may operationally affect such Users in the</p>
<p>following one week period beginning on the following Monday. The notification</p>
<p>to the User shall include proposed Start Dates and Finish Dates of relevant</p>
<p>Distribution System Outages.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC2 – Outage Planning Page 59</p>
<p>6.3 The DNO will indicate to each Generator where a need may exist to use Intertripping</p>
<p>or other measures to allow the security of the Distribution System to be maintained</p>
<p>within the Licence Standards.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC3 – Demand Control Page 60</p>
<p>Operating Code 3 – Demand Control</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 3 (&#8220;OC3&#8243;) sets out the procedures to be followed by the DNO to</p>
<p>permit a reduction in Demand, which in many instances will be initiated by the TSO</p>
<p>acting in accordance with the TSO Licence:</p>
<p>(a) in the event that there are insufficient Generating Plant, Independent</p>
<p>Generating Plant, Demand Side Units or transfers across any Interconnectors</p>
<p>and the Inter-jurisdictional Tie Lines between Northern Ireland and the</p>
<p>Republic of Ireland available to meet Demand in all or any part of the NI</p>
<p>System; and/or</p>
<p>(b) in the event of problems on any part of the NI System, including, without</p>
<p>limitation, unacceptable voltage levels and thermal overloads; and/or</p>
<p>(c) where there are insufficient Generating Plant, Independent Generating Plant,</p>
<p>Demand Side Units or transfers to meet Demand in all or any part of the</p>
<p>Other Transmission System and/or in the event of problems on the Other</p>
<p>Transmission System in circumstances where the TSO is able to assist the</p>
<p>Other TSO and where doing so would not have a detrimental effect on the</p>
<p>security of the NI System.</p>
<p>1.2 It covers both transient shortfalls of generation following a sudden loss of generation</p>
<p>and steady state shortfalls of generation.</p>
<p>1.3 The Demand Control arrangements provide for the utilisation of controllable Load</p>
<p>blocks on the NI System, for example, by radio teleswitching implemented by the</p>
<p>TSO.</p>
<p>1.4 OC3 deals with the following:-</p>
<p>(a) Demand Customer Voltage Reduction initiated by the TSO or the DNO and in</p>
<p>each case implemented by the DNO;</p>
<p>(b) Planned Manual Disconnection (including Rota Load Shedding) initiated by</p>
<p>the TSO and implemented by the DNO;</p>
<p>(c) Emergency Manual Disconnection initiated and implemented by the TSO;</p>
<p>(d) protection of supply to any part of the NI System where system security is</p>
<p>weak; and</p>
<p>(e) Disconnection of Load blocks by operation of Automatic Load Shedding</p>
<p>Devices to preserve overall NI System security.</p>
<p>Some Users will be affected by some or all of the above actions, whether implemented</p>
<p>by the TSO or the DNO.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC3 – Demand Control Page 61</p>
<p>1.5 The term &#8220;Demand Control&#8221; is used in OC3 to describe any of the methods of</p>
<p>controlling Demand set out in paragraph 1.4.</p>
<p>1.6 The type of Demand Control utilised in any particular case will depend upon the</p>
<p>amount of time between the TSO or the DNO becoming aware of the need to</p>
<p>implement Demand Control and the time at which it needs to be implemented. In the</p>
<p>event of a sudden and unexpected loss of generation and/or NI System problems and,</p>
<p>subject to the circumstances set out in paragraph 1.1.3, in the event of a sudden and</p>
<p>unexpected loss of generation on the Other Transmission System and/or Other</p>
<p>Transmission System problems, the requisite Demand Control will normally be</p>
<p>achieved by means of Automatic Load Shedding but, occasionally, Emergency</p>
<p>Manual Disconnection may be required. The amount of time available in which to</p>
<p>implement Demand Control will also determine whether Demand Control will be</p>
<p>implemented before voltage reduction. In all cases when Demand Control is</p>
<p>necessary, Demand Disconnection will normally be the last option.</p>
<p>1.7 Demand Control shall not, so far as possible, be exercised in respect of Protected</p>
<p>Demand Customers. OC3, therefore, applies subject to this exclusion.</p>
<p>2 Objective</p>
<p>The objective of OC3 is to detail the provisions to be undertaken by the DNO required</p>
<p>to achieve a reduction in Demand to avoid or relieve operating problems on all or any</p>
<p>part of the NI System and, subject to the circumstances set out in paragraph 1.1.3, on</p>
<p>the Other Transmission System. Subject to paragraph 1.7, the DNO will utilise</p>
<p>Demand Control in a manner which does not unduly discriminate against, or unduly</p>
<p>prefer, any one or any group of Demand Customers.</p>
<p>3 Scope</p>
<p>3.1 This section applies to the DNO and to Users. Users in OC4 means:</p>
<p>(a) Suppliers;</p>
<p>(b) Generators; and</p>
<p>(c) Demand Customers.</p>
<p>4 Procedures</p>
<p>4.1 Demand Customer Voltage Reduction</p>
<p>4.1.1 The DNO will, insofar as it is able, organise the Distribution System and make</p>
<p>such other arrangements as are necessary so that a 6 per cent reduction of</p>
<p>voltage supplied to all or any group of Demand Customers on a particular part</p>
<p>of the Distribution System can be implemented.</p>
<p>4.1.2 The arrangement will provide for two 3 per cent stages of voltage reduction,</p>
<p>which can be applied to all or selected groups of Demand Customers.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC3 – Demand Control Page 62</p>
<p>4.1.3 The DNO will, when instructed by the TSO and/or when it considers it</p>
<p>necessary, implement Demand Customer Voltage Reduction of either 3 per</p>
<p>cent or 6 per cent.</p>
<p>4.1.4 The DNO will, when instructed by the TSO and/or when it considers it</p>
<p>necessary, remove the voltage reduction implemented pursuant to paragraph</p>
<p>4.1.3.</p>
<p>4.2 Planned and Emergency Manual Disconnection</p>
<p>Planned Manual Disconnection</p>
<p>4.2.1 Planned Manual Disconnection is the procedure adopted by the DNO when the</p>
<p>TSO, in accordance with the Grid Code, notifies the DNO that insufficient</p>
<p>generation will be available to meet Demand in all or any part of the NI System</p>
<p>and that Demand Control is required.</p>
<p>4.2.2 Where the TSO has notified the DNO in accordance with the Grid Code that</p>
<p>Demand Control is required, the TSO may then instruct the DNO in</p>
<p>accordance with the Grid Code to implement Planned Manual Disconnection</p>
<p>and the DNO shall implement such Planned Manual Disconnection in</p>
<p>accordance with this OC3.</p>
<p>4.2.3 The DNO will restore the connections removed by Planned Manual</p>
<p>Disconnection pursuant to paragraph 4.2.2 when instructed by the TSO in</p>
<p>accordance with the Grid Code to do so.</p>
<p>4.2.4 Where Demand Control is required to continue for a protracted period rotation</p>
<p>of Disconnection under a Rota Load Shedding procedure may be required to</p>
<p>ensure equitable treatment, insofar as practicable, for all Demand Customers as</p>
<p>further detailed in paragraphs 4.2.5 and 4.2.6.</p>
<p>4.2.5 The DNO, in conjunction with the TSO, will arrange for the purposes of Rota</p>
<p>Load Shedding, insofar as it is able, that the Demand on the NI System is</p>
<p>arranged in groups of approximately 5 per cent of total Demand (as a</p>
<p>percentage at time of winter peak) so that any or all such groups can be</p>
<p>Disconnected when the TSO issues instructions to the DNO in accordance with</p>
<p>the Grid Code.</p>
<p>4.2.6 Where Disconnection is to be prolonged, the DNO will, where possible, utilise</p>
<p>Disconnection rotas where approximately 5 per cent groups are interchanged to</p>
<p>ensure (so far as possible) equitable treatment of Demand Customers.</p>
<p>Emergency Manual Disconnection</p>
<p>4.2.7 Emergency Manual Disconnection is utilised by the TSO when a loss of</p>
<p>generation or a mismatch of generation output and Demand is such that there is</p>
<p>an operational requirement to shed Load in circumstances where it is not</p>
<p>possible to give reasonable notice in order to maintain a Regulating Margin</p>
<p>between generation output and Demand and in certain circumstances to deal</p>
<p>Distribution Code 1 May 2010</p>
<p>OC3 – Demand Control Page 63</p>
<p>with operating problems such as unacceptable voltage levels and thermal</p>
<p>overloads.</p>
<p>4.2.8 The TSO will, when it considers it necessary, implement Emergency Manual</p>
<p>Disconnection.</p>
<p>4.3 Demand Control with weak or reduced NI System capabilities</p>
<p>4.3.1 This section covers the situation where the DNO or the TSO may wish to</p>
<p>initiate Demand Control to maintain partial supplies to a part of the NI System</p>
<p>which cannot support the full area Demand of that part of the NI System.</p>
<p>4.3.2 It applies to circumstances where the DNO or the TSO wish to allow for fault</p>
<p>contingencies more severe than envisaged in the Licence Standards because the</p>
<p>impact of these contingencies on the NI System would be unacceptable.</p>
<p>4.3.3 Where the DNO or the TSO considers that arrangements should be put in place</p>
<p>to enable Demand Control to be effected in the circumstances outlined in</p>
<p>paragraph 4.3.1, either may effect such arrangements.</p>
<p>4.3.4 Load shedding caused by these arrangements will be assimilated into Load</p>
<p>shedding caused by the Automatic Load Shedding scheme detailed in</p>
<p>paragraph 4.4 to ensure no Demand Customer or group of Demand</p>
<p>Customers is unfairly discriminated against.</p>
<p>4.4 Automatic Load Shedding</p>
<p>4.4.1 Under generation shortfall conditions a Frequency graded Automatic Load</p>
<p>Shedding scheme is utilised by the TSO to prevent Frequency collapse on the</p>
<p>NI System and to restore the balance between generation output and Demand.</p>
<p>4.4.2 The Demand on the NI System subject to Automatic Load Shedding will be</p>
<p>split into discrete blocks. The number, location, size and the associated low</p>
<p>Frequency settings of these blocks will be as determined by the TSO on a rota</p>
<p>basis insofar as possible and communicated to the DNO.</p>
<p>4.4.3 Where conditions are such that, following Automatic Load Shedding, and the</p>
<p>subsequent recovery of Frequency on the NI System, it is not possible to</p>
<p>restore a large proportion of the total Demand so Disconnected within a</p>
<p>reasonable period of time, the DNO may receive an instruction from the TSO to</p>
<p>implement additional Disconnection manually to restore an equivalent amount</p>
<p>of the Demand which has been Disconnected automatically. It will then effect</p>
<p>that instruction.</p>
<p>4.4.4 For the avoidance of doubt, no Demand shed by operation of Automatic Load</p>
<p>Shedding Devices will be restored by the DNO without the specific instruction</p>
<p>of the TSO in accordance with the Grid Code.</p>
<p>4.5 General</p>
<p>Distribution Code 1 May 2010</p>
<p>OC3 – Demand Control Page 64</p>
<p>Suppliers should note that although implementation of Demand Control in respect of</p>
<p>their Demand Customers is not, in general, exercisable by them, their Demand</p>
<p>Customers may be affected by Demand Control. The contractual arrangements of</p>
<p>Suppliers with their Demand Customers may, accordingly, need to reflect this.</p>
<p>5 Fuel Security Code</p>
<p>Each Supplier agrees to comply with the Fuel Security Code to the extent it is</p>
<p>expressed to apply to it and with any instructions issued by the TSO or the DNO</p>
<p>pursuant to the Fuel Security Code.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC4 – Operational Liaison Page 65</p>
<p>Operating Code 4 – Operational Liaison</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 4 (“OC4”) sets out the requirements for the exchange of</p>
<p>information between the DNO and Users in relation to Operations and Events on the</p>
<p>Total System which will have (or may have) or have had (or may have had) an</p>
<p>Operational Effect:-</p>
<p>(a) on a User System in the case of an Operation and/or Event occurring on the</p>
<p>Distribution System or the Transmission System; and</p>
<p>(b) on the Distribution System in the case of an Operation and/or Event occurring</p>
<p>on a User System;</p>
<p>where there is no other requirement for exchange of information or liaison specified in</p>
<p>any other part of the Distribution Code.</p>
<p>1.2 Where there is an obligation on the DNO under the Grid Code to report an Operation</p>
<p>and/or Event on the Distribution System to the TSO, the DNO may include in that</p>
<p>report information which it has been given by a User relating to an Operation and/or</p>
<p>Event on the User System which caused or contributed to the Event on the</p>
<p>Distribution System or, in the case of an Operation on the User System, caused the</p>
<p>DNO to undertake an Operation on the Distribution System.</p>
<p>1.3 Where the Grid Code contains an equivalent provision allowing the DNO to pass on</p>
<p>information it has received under the Grid Code in relation to Operations and/or</p>
<p>Events on the Transmission System, or on the system of users under the Grid Code,</p>
<p>that will form part of the information communicated to Users under this OC4. The</p>
<p>provisions of this OC4 allowing the DNO to pass information it has received under the</p>
<p>Grid Code will only have effect to the extent that the DNO is allowed to pass that</p>
<p>information on to Users pursuant to the Grid Code.</p>
<p>2 Objective</p>
<p>2.1 The objective of this OC4 is to set out the requirements and procedures for the</p>
<p>exchange of information between the DNO and Users in order that the implications of</p>
<p>an Operation and/or Event can be considered and the possible risks arising from it can</p>
<p>be assessed and appropriate action taken by either the DNO or the User as applicable in</p>
<p>order to maintain the integrity of the Distribution System and the relevant User</p>
<p>System. OC4 does not seek to deal with any actions arising from the exchange of</p>
<p>information, but merely with that exchange.</p>
<p>3 Scope</p>
<p>3.1 OC4 applies to the DNO and to Users. Users in this OC4 means:</p>
<p>(a) Generators in respect of their Generating Units connected to the Distribution</p>
<p>System at 33kV; and</p>
<p>Distribution Code 1 May 2010</p>
<p>OC4 – Operational Liaison Page 66</p>
<p>(b) Demand Customers in respect of their Connection Sites connected to the</p>
<p>Distribution System at 33kV; and</p>
<p>(c) Regarding notification to the DNO, Users in respect of their User Systems</p>
<p>connected to the Distribution System at 6.6kV or 11kV.</p>
<p>4 Procedure</p>
<p>4.1 Requirement to notify Operations</p>
<p>4.1.1 DNO notification</p>
<p>In the case of an Operation on the Distribution System which will have, or</p>
<p>may have, an Operational Effect on a 33kV User System, the DNO will</p>
<p>(unless the notifying requirement arises under any other part of the Distribution</p>
<p>Code) notify the User, or Users, whose System(s) will, or may in the opinion</p>
<p>of the DNO, be so affected in accordance with this OC4. The provisions of this</p>
<p>paragraph 4.1.1 shall also apply to circumstances where an Operation on the</p>
<p>Transmission System will have, or may have, an Operational Effect on a</p>
<p>User System where the DNO has been notified of such an Operation by the</p>
<p>TSO under the Grid Code.</p>
<p>4.1.2 User Notification</p>
<p>In the case of an Operation on a 33kV User System which will have or may</p>
<p>have an Operational Effect on the Distribution System the User will (unless</p>
<p>the notifying requirement arises under any other part of the Distribution Code)</p>
<p>notify the DNO in accordance with this OC4. Following notification by the</p>
<p>relevant User, the DNO will notify any other User or Users on whose</p>
<p>System(s) the Operation will (or, in the DNO’s reasonable opinion, may) have</p>
<p>an Operational Effect. The DNO may also notify the TSO if the Operation</p>
<p>will (or, in the DNO’s reasonable opinion, may) have an Operational Effect on</p>
<p>the Transmission System, in accordance with its obligations under the Grid</p>
<p>Code.</p>
<p>4.1.3 Examples</p>
<p>Whilst in no way limiting the general requirement to notify in advance as set out</p>
<p>in paragraphs 4.1.1 and 4.1.2, the following are examples of scheduled or</p>
<p>planned actions for which notification will be required under this OC4 if they</p>
<p>will, or may, have an Operational Effect:-</p>
<p>(a) the planned operation (other than, in the case of a User, at the</p>
<p>instruction of the DNO) of any circuit breaker or isolator or any</p>
<p>sequence or combination of the two; and</p>
<p>(b) Voltage Control.</p>
<p>4.1.4 Nature of notification</p>
<p>Distribution Code 1 May 2010</p>
<p>OC4 – Operational Liaison Page 67</p>
<p>(a) A notification under paragraph 4.1.1 or 4.1.2 (save where the</p>
<p>notification is to be given to a Demand Customer, in which event the</p>
<p>provisions of paragraph 4.1.5 shall apply) must be of sufficient detail to</p>
<p>describe the Operation (although it need not state the cause) and to</p>
<p>enable the recipient of the notification reasonably to consider and assess</p>
<p>the implications and risks arising. It must include the name of the</p>
<p>individual reporting the Operation on behalf of the DNO or the User, as</p>
<p>the case may be. The recipient may ask questions to clarify the</p>
<p>notification and the notifying party shall use its reasonable endeavours to</p>
<p>provide the necessary information.</p>
<p>(b) A notification which is to be given under paragraph 4.1.1 or 4.1.2 to a</p>
<p>Demand Customer will not contain the information specified in</p>
<p>paragraph 4.1.4 but may indicate that there will be, or is likely to be, an</p>
<p>incident on the Distribution System, the general nature of the incident</p>
<p>(but not the cause of the incident) and, if known, in circumstances where</p>
<p>power supplies are thought likely to be affected, the estimated time of</p>
<p>cessation and return to service.</p>
<p>4.1.5 Timing</p>
<p>A notification under paragraph 4.1.1 or 4.1.2 must be given as far in advance as</p>
<p>practicable and in any event shall be given in sufficient time as will reasonably</p>
<p>allow the recipient to consider and assess the implications and risks arising.</p>
<p>4.1.6 Recording</p>
<p>The notification shall be given in writing whenever possible. If there is</p>
<p>insufficient time before the Operation is scheduled to take place for notification</p>
<p>to be given in writing, then notification shall be given orally and, if either party</p>
<p>requests, it shall be written down by the sender and dictated to the recipient who</p>
<p>shall write it down and repeat each phrase as received and, on completion, shall</p>
<p>repeat the notification in full to the sender and check that it has been accurately</p>
<p>recorded.</p>
<p>4.1.7 User notification in respect of 6.6kV and 11kV connections</p>
<p>The DNO may, acting reasonably, require Users in respect of their User</p>
<p>Systems connected to the Distribution System at 6.6kV or 11kV, to notify the</p>
<p>DNO of an Operation on their Systems, such notification to be in accordance</p>
<p>with the provisions of paragraphs 4.1.2 to 4.1.6 inclusive.</p>
<p>4.2 Requirement to notify Events</p>
<p>4.2.1 DNO notification</p>
<p>In the case of an Event on the Distribution System which has had (or may have</p>
<p>had) an Operational Effect on a User System, the DNO will (unless the</p>
<p>notifying requirement arises under any other part of the Distribution Code)</p>
<p>notify the User or Users whose System(s) have been (or in the reasonable</p>
<p>Distribution Code 1 May 2010</p>
<p>OC4 – Operational Liaison Page 68</p>
<p>opinion of the DNO may have been) so affected, in accordance with this OC4.</p>
<p>The provisions of this paragraph 4.2.1 shall also apply to circumstances where</p>
<p>an Operational Effect on the User System was caused by an Event on the</p>
<p>Transmission System, provided that the DNO’s duty to notify a User shall be</p>
<p>solely a duty to pass on the information that the DNO has received from the</p>
<p>TSO.</p>
<p>4.2.2 User notification</p>
<p>In the case of an Event on a User System which has had (or may have had) an</p>
<p>Operational Effect on the Distribution System the User will (unless the</p>
<p>notifying requirement arises under any other part of the Distribution Code)</p>
<p>notify the DNO in accordance with this OC4. Following notification by the</p>
<p>relevant User, the DNO will notify any other User or Users on whose System</p>
<p>the Event has had (or, in the DNO’s reasonable opinion, may have had) an</p>
<p>Operational Effect. The DNO may also notify the TSO if the Event has had</p>
<p>(or, in the DNO’s reasonable opinion may have had) an effect on the</p>
<p>Transmission System, in accordance with its obligations under the Grid Code.</p>
<p>4.2.3 Examples</p>
<p>Whilst in no way limiting the general requirement to notify set out in paragraphs</p>
<p>4.2.1 and 4.2.2, the following are examples of situations where notification will</p>
<p>be required under this OC4 if they have had, or may have had, an Operational</p>
<p>Effect:-</p>
<p>(a) where Plant and/or Apparatus is being operated in excess of its</p>
<p>capability or may present a hazard to personnel;</p>
<p>(b) the activation of any alarm or indication of any abnormal operating</p>
<p>condition;</p>
<p>(c) adverse weather conditions being experienced;</p>
<p>(d) breakdown of, or faults on, or temporary changes in the capabilities of,</p>
<p>Plant and/or Apparatus;</p>
<p>(e) breakdown of, or faults on, control, communications or metering</p>
<p>equipment;</p>
<p>(f) increased risks of Protection operation.</p>
<p>4.2.4 Nature of notification</p>
<p>(a) A notification under paragraphs 4.2.1 or 4.2.2 (save where the</p>
<p>notification is to be given to a Demand Customer, in which event the</p>
<p>provisions of paragraph 4.2.5 shall apply) will be of sufficient detail to</p>
<p>describe the Event (although it need not state the cause) and so enable</p>
<p>the recipient of the notification reasonably to consider and assess the</p>
<p>implications and risks arising. The recipient may ask questions to clarify</p>
<p>Distribution Code 1 May 2010</p>
<p>OC4 – Operational Liaison Page 69</p>
<p>the notification and the notifying party shall use its reasonable</p>
<p>endeavours to provide the necessary information.</p>
<p>(b) A notification which is to be given under paragraph 4.2.1 or 4.2.2 to a</p>
<p>Demand Customer will not contain the information specified in</p>
<p>paragraph 4.2.4 but may indicate that there has been an incident on the</p>
<p>Distribution System, the general nature of the incident (but not the</p>
<p>cause of the incident) and, if known, in circumstances where power</p>
<p>supplies have been affected, an estimated time of return to service.</p>
<p>4.2.5 Recording</p>
<p>Notification shall be given orally and, except in the case of emergency, if either</p>
<p>party requests, shall be written down by the sender and dictated to the recipient</p>
<p>who shall write it down and repeat each phrase as received and, on completion,</p>
<p>shall repeat the notification in full to the sender and check that it has been</p>
<p>accurately recorded.</p>
<p>4.2.6 Timing</p>
<p>A notification under paragraph 4.2.1 or 4.2.2 shall be given as soon as possible</p>
<p>after the occurrence of the Event, or the time that the Event is known of or</p>
<p>anticipated by the giver of the notification under this OC4, and in any event</p>
<p>within 15 minutes of such time.</p>
<p>4.2.7 User notification in respect of 6.6kV and 11kV connections</p>
<p>The DNO may, acting reasonably, require Users in respect of their User</p>
<p>Systems connected to the Distribution System at 6.6kV or 11kV, to notify the</p>
<p>DNO of an Event on their Systems, such notification to be in accordance with</p>
<p>the provisions of paragraphs 4.2.2 to 4.2.6 inclusive.</p>
<p>4.3 Significant Incidents</p>
<p>4.3.1 Where the DNO notifies a User of an Event under paragraph 4.2.1 which the</p>
<p>User considers has had or may have had a significant effect on that User’s</p>
<p>System, that User may require the DNO to report that Event in writing in</p>
<p>accordance with the provisions of OC5 in which event it will, within one</p>
<p>Business Day, notify the DNO accordingly.</p>
<p>4.3.2 Where a User notifies the DNO under paragraph 4.2.2 of an Event which the</p>
<p>DNO considers has had or may have had a significant effect on the Distribution</p>
<p>System, the DNO may require the User to report that Event in writing in</p>
<p>accordance with the provisions of OC5 in which event it will, within one</p>
<p>Business Day, notify that User accordingly.</p>
<p>4.3.3 Events which a User requires the DNO to report in writing pursuant to</p>
<p>paragraph 4.3.1 and Events which the DNO requires a User to report in writing</p>
<p>pursuant to paragraph 4.3.2 are known as &#8220;Significant Incidents&#8221;.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC4 – Operational Liaison Page 70</p>
<p>4.3.4 Without limiting the general description set out in paragraphs 4.3.1 and 4.3.2, a</p>
<p>Significant Incident will include an Event having an Operational Effect which</p>
<p>results in, or is likely to result in, the following:-</p>
<p>(a) tripping of Plant and/or Apparatus either manually or automatically;</p>
<p>(b) voltage outside statutory limits;</p>
<p>(c) System Frequency outside statutory limits;</p>
<p>(d) System instability; or</p>
<p>(e) System overloads.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC5 – Operational Event Reporting and Information Supply Page 71</p>
<p>Operating Code 5 – Operational Event Reporting and Information Supply</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 5 (“OC5”) sets out the requirements for reporting in writing and,</p>
<p>where appropriate, more fully those Significant Incidents which initially were reported</p>
<p>to the DNO or a User orally under OC4 and the requirements for the provision to the</p>
<p>DNO of information to enable it to prepare analyses and assessments of policies in the</p>
<p>Distribution Code.</p>
<p>1.2 Where the Grid Code contains a provision allowing the DNO to pass on information it</p>
<p>has received under the Grid Code in relation to Significant Incidents on the</p>
<p>Transmission System, or on the system of users under the Grid Code, that will form</p>
<p>part of the information communicated to Users under this OC5. The provisions of this</p>
<p>OC5 allowing the DNO to pass information it has received under the Grid Code will</p>
<p>only have effect to the extent that the DNO is allowed to pass that information on to</p>
<p>Users pursuant to the Grid Code.</p>
<p>2 Objective</p>
<p>2.1 The objective of OC5 is to facilitate:-</p>
<p>(a) the provision of more detailed information in writing of Significant Incidents;</p>
<p>(b) the provision of information aimed at enabling the Distribution System to be</p>
<p>operated in accordance with the Distribution Code; and</p>
<p>(c) the assessment of the effectiveness of policies adopted in accordance with the</p>
<p>Distribution Code.</p>
<p>3 Scope</p>
<p>4.4 OC5 applies to the DNO and to Users. Users in this OC5 means:</p>
<p>(a) Generators in respect of their Generating Units connected to the Distribution</p>
<p>System at HV; and</p>
<p>(b) Demand Customers in respect of their Connection Sites connected to the</p>
<p>Distribution System at HV.</p>
<p>4 Procedure</p>
<p>4.1 Written reports of Events</p>
<p>4.1.1 In the case of a Significant Incident which has been notified as an Event by the</p>
<p>DNO to a User pursuant to OC4, the DNO shall provide a written report to the</p>
<p>User in accordance with this OC5.</p>
<p>4.1.2 In the case of a Significant Incident which has been notified as an Event by a</p>
<p>User to the DNO pursuant to OC4, the User shall provide a written report to</p>
<p>the DNO in accordance with this OC5.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC5 – Operational Event Reporting and Information Supply Page 72</p>
<p>4.1.3 Form of Report</p>
<p>(a) A report under paragraph 4.1.1 or 4.1.2 shall, in the case of a report by</p>
<p>a User, be addressed to the DNO and marked for the attention of the</p>
<p>Distribution Service Centre Manager and, in the case of a report by the</p>
<p>DNO to a User, be addressed to the User and marked for the attention of</p>
<p>the person notified to the DNO by the User in writing from time to time</p>
<p>for this purpose (or in the absence of notification, to the Company</p>
<p>Secretary).</p>
<p>(b) In either case, the report will contain a written confirmation of the oral</p>
<p>notification given under OC4 together with such further information</p>
<p>which has become known relating to the Significant Incident since the</p>
<p>oral notification under OC4. The report shall, as a minimum, contain</p>
<p>those matters specified in Appendix 1 to this OC5. Appendix 1 is not</p>
<p>intended to be exhaustive.</p>
<p>(c) Whilst the report need not state the cause of the Significant Incident, it</p>
<p>shall contain an indication as to whether the cause has been ascertained</p>
<p>and whether it is thought likely by the party issuing the report that the</p>
<p>matter which caused the Significant Incident will recur. The recipient</p>
<p>may raise questions to clarify the report.</p>
<p>4.2 Timing</p>
<p>4.2.1 Where the DNO is required to produce a written report under paragraph 4.1.1,</p>
<p>it shall do so as soon as possible and in any event within two Business Days</p>
<p>after notification by the User under paragraph 4.3.1 of OC4. In the event that</p>
<p>the DNO is unable to provide a full report within this timescale, it shall provide</p>
<p>to the User a preliminary report containing such information as is then known to</p>
<p>the DNO not later than two Business Days after the notification by the User</p>
<p>under paragraph 4.3.1 of OC4 and shall provide such up-dates thereafter as the</p>
<p>User may reasonably require. A full report shall then be provided to the User as</p>
<p>soon as the DNO is able.</p>
<p>4.2.2 Where a User is required to produce a written report under paragraph 4.1.2, it</p>
<p>shall do so as soon as possible and in any event within two Business Days after</p>
<p>notification by the DNO under paragraph 4.3.2 of OC4. In the event that the</p>
<p>User is unable to provide a full report within this timescale, it shall provide to</p>
<p>the DNO a preliminary report containing such information as is then known to</p>
<p>the User not later than two Business Days after the notification by the DNO</p>
<p>under paragraph 4.3.2 of OC4 and shall provide such updates thereafter as the</p>
<p>DNO may reasonably require. A full report shall then be provided to the DNO</p>
<p>as soon as the User is able.</p>
<p>4.3 Responsible officers</p>
<p>The DNO and each User shall nominate responsible officers in order to establish</p>
<p>communication channels to enable timely and adequate flows of information between</p>
<p>the DNO and Users to be maintained and thus to ensure the effectiveness of this OC5.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC5 – Operational Event Reporting and Information Supply Page 73</p>
<p>4.4 Provision of reports to other Users and the TSO</p>
<p>Whenever a User has provided a written report in respect of a Significant Incident to</p>
<p>the DNO in accordance with paragraph 4.1.2, the DNO shall consider whether the</p>
<p>System of another User (or Users) or the Transmission System has been or is likely to</p>
<p>have been materially affected. If the DNO considers that another User System (or</p>
<p>Systems) or the Transmission System has been or is likely to have been so affected,</p>
<p>the DNO shall notify the User which prepared the report accordingly and the User shall</p>
<p>supply an extract from its report, containing only the technical information (and no</p>
<p>information of commercial value) which was set out in the report, to the other Users</p>
<p>and/or the TSO identified by the DNO.</p>
<p>4.5 The provision of information to the DNO</p>
<p>4.5.1 The DNO may require (to the extent not supplied under any other provision of</p>
<p>the Distribution Code) information of a technical (but not of a commercial)</p>
<p>nature to be supplied by Users under this paragraph 4.5 to enable it to undertake</p>
<p>the following:-</p>
<p>(a) the preparation of Distribution System and/or User System appraisal</p>
<p>statements;</p>
<p>(b) surveys of Distribution System and/or User System conditions;</p>
<p>(c) analysis and validation of policies in the Distribution Code; and</p>
<p>(d) analyses of the DNO equipment performance;</p>
<p>insofar as such information is necessary to enable the DNO to fulfil its</p>
<p>obligations relating to the operation of the Distribution System.</p>
<p>4.5.2 When the DNO requires information from a User or Users for the purposes set</p>
<p>out in paragraph 4.5.1 it shall send a written request to the User or Users</p>
<p>setting out the information it reasonably requires, the reasons (in such detail as</p>
<p>the DNO reasonably considers to be appropriate) why such information is</p>
<p>required and the time by which it reasonably requires a response. Normally this</p>
<p>will be within two Business Days.</p>
<p>4.5.3 The User or Users will use all reasonable endeavours to respond in writing</p>
<p>within the time stated. However, a User will not be obliged to supply the</p>
<p>information requested by the DNO to the extent that it considers that it is not</p>
<p>reasonable to comply with the request. In such circumstances, the User must, in</p>
<p>its written response to the DNO, state such reason in sufficient detail to enable</p>
<p>the DNO to consider whether the User is acting reasonably in refusing to supply</p>
<p>the information.</p>
<p>4.5.4 Although the request will set out the information required, an indication of the</p>
<p>sort of information that may be requested is set out in Appendix 2 to this OC5.</p>
<p>The list contained in Appendix 2 shall not limit the information which may be</p>
<p>requested, but is merely given by way of example.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC5 – Operational Event Reporting and Information Supply Page 74</p>
<p>4.5.5 The information supplied to the DNO pursuant to this paragraph 4.5 will be</p>
<p>used by the DNO only for the purposes set out in paragraph 4.5.1.</p>
<p>5 Statutory event reporting procedure</p>
<p>Nothing in this OC5 shall be construed as relieving Users from their duty to report</p>
<p>events in accordance with the Electricity Supply Regulations (N.I.) in so far as they</p>
<p>apply to Users.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC5 – Operational Event Reporting and Information Supply Page 75</p>
<p>OC5 &#8211; Appendix 1</p>
<p>Matters, if applicable to the Significant Incident, to be included in a written report given in</p>
<p>accordance with paragraph 4.1</p>
<p>1 Time and date of Significant Incident.</p>
<p>2 Location.</p>
<p>3 Plant and/or Apparatus involved.</p>
<p>4 Brief description of Significant Incident.</p>
<p>5 Estimated time and date of return to service.</p>
<p>6 Supplies/generation interrupted and duration of interruption.</p>
<p>7 Generating Unit &#8211; MVAr performance achieved.</p>
<p>8 Any other information which either the DNO or the User reasonably considers that the</p>
<p>other might reasonably require in relation to the Significant Incident.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC5 – Operational Event Reporting and Information Supply Page 76</p>
<p>OC5 &#8211; Appendix 2</p>
<p>Indication of the sort of information that may be requested under paragraph 4.5</p>
<p>1 VOLTAGE</p>
<p>Time and date</p>
<p>Location</p>
<p>Target volts</p>
<p>Actual volts</p>
<p>Reason if different</p>
<p>2 MW/MVAr CAPABILITY</p>
<p>Time and date</p>
<p>Location</p>
<p>Set identification</p>
<p>Generating Unit performance parameters (List to be included)</p>
<p>3 TRANSFERS AT CONNECTION POINT</p>
<p>Time and date</p>
<p>Location</p>
<p>Direction and magnitude of MW and MVAr flows</p>
<p>4 FAULT LEVELS AT CONNECTION POINT</p>
<p>Time and date</p>
<p>Location</p>
<p>Fault infeed</p>
<p>The necessary data to enable (single phase to earth and three phase symmetrical) fault</p>
<p>levels to be calculated</p>
<p>5 PROTECTION PERFORMANCE UNDER FAULT CONDITIONS</p>
<p>Time and date</p>
<p>Location</p>
<p>Differences between anticipated and actual performance.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 77</p>
<p>Operating Code 6 &#8211; Safety Co-ordination</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 6 (&#8220;OC6&#8243;) specifies the standard procedures which are to be</p>
<p>followed by the DNO and Users for the co-ordination, establishment and maintenance</p>
<p>of necessary Safety Precautions when work and/or testing (other than System Tests,</p>
<p>which are covered by OC9 and the type of tests covered in OC10) is to be carried out</p>
<p>on or near the Distribution System or a User System and when, for this to be done</p>
<p>safely, Safety Precautions are required on the Distribution System and on the User’s</p>
<p>System.</p>
<p>1.2 Where, by reason of the design of any HV Apparatus on which Safety Precautions</p>
<p>are to be applied, it is not practicable to apply Safety Precautions on such HV</p>
<p>Apparatus, the Safety Precautions shall be applied at the most appropriate point(s) on</p>
<p>the User’s Plant and Apparatus to achieve Safety From The System on the HV</p>
<p>Apparatus on which Safety From The System is to be achieved.</p>
<p>1.3 OC6 does not apply to a situation in which Safety Precautions need to be agreed solely</p>
<p>between Users and other persons connected to the Distribution System.</p>
<p>1.4 OC6 does not seek to impose a particular set of Safety Rules on the DNO or Users; the</p>
<p>Safety Rules to be adopted and used by the DNO and each User shall be those chosen</p>
<p>by each.</p>
<p>1.5 The procedures set out in this OC6 do not refer expressly to a situation in which both</p>
<p>the DNO and a User require the other to implement Safety Precautions at the same</p>
<p>time. In such circumstances the relevant procedures of this OC6 should be applied</p>
<p>twice, once with the DNO acting as Implementing Safety Co-ordinator and once with</p>
<p>the User acting in that role.</p>
<p>2 Objective</p>
<p>2.1 The objective of this OC6 is to achieve Safety From The System when work and/or</p>
<p>testing on or near either a User’s System or the Distribution System necessitates the</p>
<p>provision of Safety Precautions on the Distribution System and a User’s System..</p>
<p>3 Scope</p>
<p>3.1 OC6 applies to the DNO and to Users. Users in OC6 means</p>
<p>(a) Generators in respect of their Generating Units connected to the Distribution</p>
<p>System at HV; and</p>
<p>(b) Demand Customers in respect of their Connection Sites connected to the</p>
<p>Distribution System at HV.</p>
<p>4 Procedure</p>
<p>4.1 The procedures set out in the remainder of this OC6 apply to the DNO and to Users in</p>
<p>respect of Generating Units or Connection Sites connected to the Distribution System</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 78</p>
<p>at 33kV or above. In the event of any inconsistency between the procedures set out in</p>
<p>this OC6 and the procedures (if any) set out in such User’s Connection Agreement,</p>
<p>the procedures set out in this OC6 shall prevail.</p>
<p>4.2 For Users in respect of Generating Units or Connection Sites connected to the</p>
<p>Distribution System below 33kV, such Users and the DNO shall apply the processes</p>
<p>and procedures set out in Safety Rules Guidance Document 4 (“SRG 4”) of the NIE</p>
<p>Safety Rules. In the event of any inconsistency between the processes and procedures</p>
<p>set out in SRG 4 and the procedures (if any) set out in such User’s Connection</p>
<p>Agreement, the procedures set out in SRG 4 shall prevail save where such Connection</p>
<p>Agreement makes it explicit that the procedures therein shall prevail.</p>
<p>5 Approval of Local Safety Instructions</p>
<p>5.1 In accordance with the timing requirements of its Connection Agreement, each User</p>
<p>shall supply to the DNO a copy of its Local Safety Instructions, if any, relating to its</p>
<p>side of the Connection Point at each Connection Site. In accordance with the timing</p>
<p>requirements of each Connection Agreement, the DNO shall supply to each User a</p>
<p>copy of the DNO’s Local Safety Instructions, if any, relating to the DNO side of the</p>
<p>Connection Point at each Connection Site. Prior to connection and in accordance with</p>
<p>the timing requirements of the relevant Connection Agreement, the DNO and the User</p>
<p>must have approved each other&#8217;s Local Safety Instructions dealing with Isolation and</p>
<p>Earthing.</p>
<p>5.2 If the party required to give approval requires, for that approval to be given, more</p>
<p>stringent provisions relating to Isolation and/or Earthing (including relating to</p>
<p>Earthing Devices) (and to the extent that these are not unreasonable), the other party</p>
<p>will make such changes as soon as reasonably practicable to the provisions in its Local</p>
<p>Safety Instructions relating to Isolation and/or Earthing (including relating to</p>
<p>Earthing Devices) affecting the Connection Site (which may of course need to cover</p>
<p>the application of Isolation and/or Earthing at a place remote from such Connection</p>
<p>Site, depending upon the System layout). There is no right to withhold approval on the</p>
<p>grounds that the party required to approve reasonably believes the provisions relating to</p>
<p>Isolation and/or Earthing (including Earthing Devices) are too stringent.</p>
<p>5.3 If, following approval, a party wishes to change the provisions in its Local Safety</p>
<p>Instructions relating to Isolation and/or Earthing (including Earthing Devices), it</p>
<p>must inform the other party. If the change is to make the provisions more stringent,</p>
<p>then the other party merely has to note the changes. If the change is to make the</p>
<p>provisions less stringent, then the other party needs to approve the new provisions and</p>
<p>the procedures referred to in paragraph 5.2 will apply.</p>
<p>6 Safety Co-ordinators</p>
<p>6.1 The DNO and each User will at all times have nominated a person or persons to be</p>
<p>responsible for the co-ordination of Safety Precautions at each Connection Point,</p>
<p>when work and/or testing is to be carried out on or near a System which necessitates</p>
<p>the provision of Safety Precautions on (or relating to) HV Apparatus, pursuant to this</p>
<p>OC6 (&#8220;Safety Co-ordinator(s)&#8221;). A Safety Co-ordinator may be responsible for the</p>
<p>co-ordination of safety on (or relating to) HV Apparatus at more than one Connection</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 79</p>
<p>Point. It should be noted that, for the purposes of this OC6, the Safety Co-ordinator&#8217;s</p>
<p>role is limited to the co-ordination of Safety Precautions. The Safety Co-ordinator</p>
<p>will not necessarily but may undertake the physical implementation of Safety</p>
<p>Precautions.</p>
<p>6.2 Each User shall, prior to its Plant and Apparatus being connected to the Distribution</p>
<p>System, in accordance with any timing provisions of the Connection Agreement or, in</p>
<p>the absence of such provisions, as far in advance as possible, give notice in writing to</p>
<p>the DNO of the identity of its Safety Co-ordinator(s), along with contact details, and</p>
<p>shall update the written notice (i) whenever there is a change to the identity or contact</p>
<p>details of its Safety Co-ordinator(s), and (ii) annually on 1 April each year.</p>
<p>6.3 The DNO shall at the time of a User being connected to the Distribution System, in</p>
<p>accordance with the timing provisions of the Connection Agreement or, in the absence</p>
<p>of such provisions, as far as possible in advance, give notice in writing to that User of</p>
<p>its Safety Co-ordinator(s), along with contact details, and shall update the written</p>
<p>notice (i) whenever there is a change to the identity or contact details of the Safety Coordinator(</p>
<p>s), and (ii) annually on 1 April each year.</p>
<p>6.4 If work and/or testing is to be carried out on or near a System which necessitates the</p>
<p>provision of Safety Precautions on (or relating to) HV Apparatus in accordance with</p>
<p>the provisions of this OC6, the Safety Co-ordinator who is identified on the relevant</p>
<p>Site Responsibility Schedule as responsible for the HV Apparatus on which or in</p>
<p>relation to which Safety From The System is to be achieved (the &#8220;Requesting Safety</p>
<p>Co-ordinator&#8221;) shall contact the Safety Co-ordinator who is identified on that same</p>
<p>Site Responsibility Schedule as being responsible for the HV Apparatus which is</p>
<p>connected at the Connection Point to the HV Apparatus on which Safety From The</p>
<p>System is required (the &#8220;Implementing Safety Co-ordinator&#8221;), to co-ordinate the</p>
<p>Safety Precautions.</p>
<p>7 RISSP</p>
<p>7.1 OC6 sets out the procedures for utilising the Record of Inter-System Safety</p>
<p>Precautions (&#8220;RISSP&#8221;).</p>
<p>7.2 The form set out in Appendix A and designated as &#8220;RISSP-A&#8221;, shall be used by the</p>
<p>Requesting Safety Co-ordinator, and that in Appendix B and designated as &#8220;RISSPB&#8221;,</p>
<p>shall be used by the Implementing Safety Co-ordinator.</p>
<p>7.3 RISSP-A shall have written or printed on it an identifying number, comprising a unique</p>
<p>prefix which identifies the location at which it is issued, and a unique (for each User or</p>
<p>the DNO, as the case may be) serial number consisting of four digits and the suffix</p>
<p>&#8220;R&#8221;.</p>
<p>7.4 At the time that the User first gives notice to the DNO of its Safety Co-ordinators,</p>
<p>each User shall apply in writing to the DNO for the DNO’s approval of its proposed</p>
<p>prefix. The DNO shall consider the proposed prefix to see if it is the same as (or</p>
<p>confusingly similar to) a prefix used by the DNO or another User and shall, as soon as</p>
<p>possible (and in any event within ten days), respond in writing to the User with its</p>
<p>approval or disapproval. If the DNO disapproves, it shall explain in its response why it</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 80</p>
<p>has disapproved and will suggest an alternative prefix and the User shall either notify</p>
<p>the DNO in writing of its acceptance of the suggested alternative prefix or it shall apply</p>
<p>in writing to the DNO with revised proposals and the above procedure shall apply to</p>
<p>that application.</p>
<p>8 Safety Precautions on or Relating to HV Apparatus</p>
<p>8.1 Safety Precautions</p>
<p>For the purpose of the co-ordination of safety under OC6 relating to HV Apparatus,</p>
<p>the term &#8220;Safety Precautions&#8221; means Isolation and/or Earthing.</p>
<p>8.2 Agreement of Safety Precautions</p>
<p>8.2.1 When the DNO or a User wishes to carry out work and/or testing on its System</p>
<p>and it is of the opinion that, for this to be done safely, Safety Precautions are</p>
<p>required on the DNO’s HV Apparatus (in the case of a User), or on or relating</p>
<p>to the HV Apparatus of a User (in the case of the DNO), the Requesting</p>
<p>Safety Co-ordinator will contact the Implementing Safety Co-ordinator for</p>
<p>the part of the System on which (or relating to which) the Safety Precautions</p>
<p>are, in his reasonable opinion, required, in order to agree in accordance with the</p>
<p>procedure contained in this paragraph 8, the Location at which the Safety</p>
<p>Precautions will be implemented or applied.</p>
<p>8.2.2 When the DNO wishes to carry out work and/or testing on the Distribution</p>
<p>System and it is of the opinion that, for this to be done safely, Safety</p>
<p>Precautions are required on (or relating to) the System of more than one User</p>
<p>the provisions of this paragraph 8 shall be followed with regard to each User</p>
<p>separately.</p>
<p>8.3 Agreement of Isolation</p>
<p>8.3.1 The Requesting Safety Co-ordinator shall inform the Implementing Safety</p>
<p>Co-ordinator of the HV Apparatus on which Safety From The System is to</p>
<p>be achieved and they will need to reach agreement on the Location(s) at which</p>
<p>Isolation is to be established on (or relating to) the Implementing Safety Coordinator&#8217;s</p>
<p>System.</p>
<p>8.3.2 The Implementing Safety Co-ordinator shall then promptly inform the</p>
<p>Requesting Safety Co-ordinator of the following:</p>
<p>(a) for each Location, the identity (by means of name and numbering or</p>
<p>position, as applicable) of each point of Isolation; and</p>
<p>(b) whether Isolation is to be achieved by an Isolating Device in the</p>
<p>isolating position or by an adequate physical separation or sufficient gap</p>
<p>or by disablement (by means of switching or dismantling) of Plant</p>
<p>and/or Apparatus so that electrical energy cannot pass from the</p>
<p>Apparatus (or, in the case of Plant, from the associated Apparatus) to</p>
<p>the HV Apparatus, other than by an Isolating Device.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 81</p>
<p>8.3.3 The Implementing Safety Co-ordinator shall maintain and secure each point of</p>
<p>Isolation in accordance with the relevant Local Safety Instructions.</p>
<p>8.4 Agreement of Earthing</p>
<p>8.4.1 If, in addition to the Isolation requested under paragraph 8.3, the Requesting</p>
<p>Safety Co-ordinator requires Earthing, he shall notify this requirement to the</p>
<p>Implementing Safety Co-ordinator and they will need to reach agreement on</p>
<p>the Location(s) at which Earthing is to be established on the Implementing</p>
<p>Safety Co-ordinator&#8217;s System.</p>
<p>8.4.2 The Implementing Safety Co-ordinator shall then promptly inform the</p>
<p>Requesting Safety Co-ordinator for each Location, the identity (by means of</p>
<p>HV Apparatus name and numbering or position, as is applicable) of each point</p>
<p>of Earthing.</p>
<p>8.4.3 The Implementing Safety Co-ordinator shall maintain and secure each point of</p>
<p>Earthing in accordance with the relevant Local Safety Instructions.</p>
<p>8.5 In the event of disagreement</p>
<p>8.5.1 In any case where the Requesting Safety Co-ordinator and the Implementing</p>
<p>Safety Co-ordinator are unable to agree the Location of the Isolation and (if</p>
<p>requested) Earthing, it shall be at the closest available points on the infeeds to</p>
<p>the HV Apparatus on which Safety From The System is to be achieved as</p>
<p>indicated on the Ownership Diagram or, in the case where, by reason of the</p>
<p>design of any HV Apparatus on which Safety Precautions are to be applied, it</p>
<p>is not practicable to apply Safety Precautions on such HV Apparatus, it shall</p>
<p>be at the most appropriate point(s) on the User’s Plant and/or Apparatus to</p>
<p>achieve Safety From The System on the HV Apparatus on which Safety From</p>
<p>The System is to be achieved, as determined by the DNO.</p>
<p>8.6 Implementation of Isolation and Earthing</p>
<p>8.6.1 Once the Location of Isolation and (if requested) Earthing are agreed in</p>
<p>accordance with paragraphs 8.3 and 8.4 above, the following procedure will</p>
<p>apply:</p>
<p>(a) the Implementing Safety Co-ordinator will ensure the implementation</p>
<p>of the Isolation;</p>
<p>(b) the Implementing Safety Co-ordinator will confirm to the Requesting</p>
<p>Safety Co-ordinator that the Isolation has been established on his</p>
<p>System;</p>
<p>(c) when the Implementing Safety Co-ordinator has confirmed the</p>
<p>establishment of Isolation in accordance with (b) above, the Requesting</p>
<p>Safety Co-ordinator shall confirm to the Implementing Safety Coordinator</p>
<p>the establishment of relevant Isolation on his System and</p>
<p>request, if it has been required, the implementation of the Earthing;</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 82</p>
<p>(d) the Implementing Safety Co-ordinator will ensure the implementation</p>
<p>of the Earthing on his System; and</p>
<p>(e) the Implementing Safety Co-ordinator will confirm to the Requesting</p>
<p>Safety Co-ordinator that Earthing has been established on his System.</p>
<p>8.7 Recording of Safety Precautions</p>
<p>8.7.1 Following confirmation by the Implementing Safety Co-ordinator to the</p>
<p>Requesting Safety Co-ordinator that all of the agreed Safety Precautions have</p>
<p>been established on or relating to the System of the Implementing Safety Coordinator,</p>
<p>the Implementing Safety Co-ordinator will record the details of the</p>
<p>HV Apparatus on which he has been told that Safety From The System is</p>
<p>required and the Safety Precautions established on or relating to the System of</p>
<p>the Implementing Safety Co-ordinator onto parts 1.1 and 1.2 of his RISSP-B.</p>
<p>Where Earthing was not requested (either because Earthing was possible but</p>
<p>was not required or because Earthing was not possible), part 1.2(b) of the</p>
<p>RISSP-B will be completed with the words &#8220;not earthed&#8221;.</p>
<p>8.7.2 The Implementing Safety Co-ordinator shall then contact the Requesting</p>
<p>Safety Co-ordinator and confirm, by reading out the details entered on parts</p>
<p>1.1 and 1.2 of RISSPB, to the Requesting Safety Co-ordinator, that the Safety</p>
<p>Precautions have been established.</p>
<p>8.7.3 The Requesting Safety Co-ordinator will then complete parts 1.1 and 1.2 of</p>
<p>RISSP-A with the precise details received from the Implementing Safety Coordinator</p>
<p>and then read back all those details to the Implementing Safety Coordinator.</p>
<p>If both confirm that the details entered are the same, the Requesting</p>
<p>Safety Co-ordinator shall issue the RISSP identifying number, as stated on the</p>
<p>RISSP-A, to the Implementing Safety Co-ordinator who shall ensure that the</p>
<p>number, including its prefix and suffix, is correctly entered on the RISSP-B.</p>
<p>8.7.4 The Requesting Safety Co-ordinator and the Implementing Safety Coordinator</p>
<p>shall then respectively complete part 1.3 of RISSP-A and RISSP-B</p>
<p>(which relates to the identity and location of the Implementing Safety Coordinator</p>
<p>and the Requesting Safety Co-ordinator respectively). Each Safety</p>
<p>Co-ordinator shall then complete the issue of the RISSP by signing part 1.3 of</p>
<p>their respective RISSPs and then enter the time and date. Once signed, no</p>
<p>alteration to the RISSP is permitted; the RISSP may only be cancelled.</p>
<p>8.7.5 The Requesting Safety Co-ordinator is then free to authorise work, but not</p>
<p>testing. Where testing is to be carried out, the procedure set out below in</p>
<p>paragraph 9 shall be implemented. The procedure to carry out the work is</p>
<p>entirely an internal matter for the party which the Requesting Safety Coordinator</p>
<p>is representing.</p>
<p>9 Testing</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 83</p>
<p>9.1 Where the Requesting Safety Co-ordinator wishes to authorise the carrying out of a</p>
<p>test to which the procedures in this paragraph 9 apply he may not do so and the test will</p>
<p>not take place unless and until the following procedures have been followed:</p>
<p>(a) confirmation is obtained from the Implementing Safety Co-ordinator that no</p>
<p>person is working on, or testing, or has been authorised to work on, or test, any</p>
<p>parts of the Systems within the points of Isolation identified on the RISSP form</p>
<p>relating to the test which is proposed to be undertaken (the &#8220;original RISSP&#8221;),</p>
<p>and the points of Isolation on the Requesting Safety Co-ordinator&#8217;s System,</p>
<p>and will not be so authorised until the proposed test has been completed (or</p>
<p>cancelled) and the Requesting Safety Co-ordinator has notified the</p>
<p>Implementing Safety Co-ordinator of its completion (or cancellation) and</p>
<p>thereby the cancellation of the requirements;</p>
<p>(b) all current RISSPs (except for the original RISSP) between the Requesting</p>
<p>Safety Co-ordinator and the Implementing Safety Co-ordinator which relate</p>
<p>to those parts of the Systems between the points of Isolation identified on the</p>
<p>original RISSP and the points of Isolation on the Requesting Safety Coordinator&#8217;s</p>
<p>System, have been cancelled in accordance with the procedures set</p>
<p>out in paragraph 9; and</p>
<p>(c) the Implementing Safety Co-ordinator agrees with the Requesting Safety Coordinator</p>
<p>to permit the testing on those parts of the Systems between the points</p>
<p>of Isolation identified in the original RISSP and the points of Isolation on the</p>
<p>Requesting Safety Co-ordinator&#8217;s System.</p>
<p>9.2 The Requesting Safety Co-ordinator will inform the Implementing Safety Coordinator</p>
<p>as soon as the test has been completed or cancelled. Where Earthing has</p>
<p>been removed during a test and has not been restored at the original position upon</p>
<p>completion or cancellation of the test, the original RISSP shall be cancelled</p>
<p>immediately in accordance with the procedure set out in paragraph 10.</p>
<p>10 Cancellation</p>
<p>10.1 When the Requesting Safety Co-ordinator decides (having followed all relevant</p>
<p>internal procedures) that Safety Precautions are no longer required, he will contact the</p>
<p>Implementing Safety Co-ordinator and inform him of the RISSP identifying number</p>
<p>(including the prefix and suffix). The Requesting Safety Co-ordinator shall read out to</p>
<p>the Implementing Safety Co-ordinator the details entered on parts 1.1 and 1.2 of his</p>
<p>RISSP-A, and the Implementing Safety Co-ordinator shall confirm that the details</p>
<p>entered on parts 1.1 and 1.2 of the RISSP-B are the same. The Requesting Safety Coordinator</p>
<p>shall then confirm to the Implementing Safety Co-ordinator that the Safety</p>
<p>Precautions are no longer required.</p>
<p>10.2 The Requesting Safety Co-ordinator and the Implementing Safety Co-ordinator</p>
<p>shall then respectively complete part 2.1 of RISSP-A and RISSP-B (which relates to</p>
<p>the identity and location of the Implementing Safety Co-ordinator and the Requesting</p>
<p>Safety Co-ordinator respectively). Each Safety Co-ordinator shall then complete the</p>
<p>cancellation of the RISSP procedure by signing part 2.1 of their respective RISSPs and</p>
<p>then entering the time and date.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 84</p>
<p>10.3 Subject as provided in paragraph 10.4, the Implementing Safety Co-ordinator is then</p>
<p>free to arrange the removal of the Safety Precautions, the procedure to achieve that</p>
<p>being entirely an internal matter for the party which the Implementing Safety Coordinator</p>
<p>is representing. The only situation in which any Safety Precautions may be</p>
<p>removed without first cancelling the RISSP in accordance with paragraph 10 is when</p>
<p>Earthing is removed in the situation envisaged in paragraph 9.2.</p>
<p>10.4 Where Earthing has been requested neither Safety Co-ordinator shall instruct the</p>
<p>removal of any Isolation forming part of the Safety Precautions until it is confirmed to</p>
<p>each by the other that all Earthing has been removed.</p>
<p>11 Loss of Integrity of Safety Precautions</p>
<p>In any instance when any Safety Precautions may be ineffective for any reason the</p>
<p>relevant Safety Co-ordinator shall without delay inform the other Safety Coordinator(</p>
<p>s) of that being the case and, if requested, of the reasons why.</p>
<p>12 Safety Log</p>
<p>The DNO and each User shall maintain a safety log which shall be a chronological</p>
<p>record of all messages relating to safety co-ordination under this OC6 sent and received</p>
<p>by the Safety Co-ordinator(s). The safety log must be retained for a period of not less</p>
<p>than 3 years.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 85</p>
<p>OC6 SAFETY CO-ORDINATION &#8211; APPENDIX A</p>
<p>Northern Ireland Electricity</p>
<p>DISTRIBUTION CONTROL CENTRE/USER</p>
<p>RECORD OF INTER-SYSTEM SAFETY PRECAUTIONS (RISSP-A)</p>
<p>(Requesting Safety Co-ordinator&#8217;s Record)</p>
<p>RISSP NUMBER _</p>
<p>PART 1</p>
<p>1.1 HV APPARATUS IDENTIFICATION</p>
<p>Safety Precautions have been established by the Implementing Safety Co-ordinator to achieve (in so far as it is</p>
<p>possible from that side of the Connection Point) Safety From The System on the following HV Apparatus on</p>
<p>the Requesting Safety Co-ordinator&#8217;s System: [State identity - name(s) and, where applicable, identification of</p>
<p>the HV circuit(s) up to the Connection Point]:</p>
<p>1.2 SAFETY PRECAUTIONS ESTABLISHED</p>
<p>(a) ISOLATION</p>
<p>[State the Location(s) at which Isolation has been established. For each Location, identify each point of</p>
<p>Isolation. For each point of Isolation, state the means by which the Isolation has been achieved and whether</p>
<p>immobilised and Locked, Caution Notice affixed or other safety procedures applied, as appropriate.]</p>
<p>(b) EARTHING</p>
<p>[State the Location(s) at which Earthing has been established. For each Location, identify each point of</p>
<p>Earthing. For each point of Earthing, state the means by which the Earthing has been achieved and whether</p>
<p>immobilised and Locked or other safety procedures applied, as appropriate].</p>
<p>1.3 ISSUE</p>
<p>I have received confirmation from ______________________________ (name of Implementing Safety Coordinator)</p>
<p>at ___________________________________ (location) that the Safety Precautions identified in</p>
<p>paragraph 1.2 have been established and that instructions will not be issued at his location for their removal until</p>
<p>this RISSP is cancelled.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 86</p>
<p>Signed &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..(Requesting Safety Co-ordinator)</p>
<p>at &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. (time) on &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.(date)</p>
<p>PART 2</p>
<p>2.1 CANCELLATION</p>
<p>I have confirmed to _________________________________ (name of the Implementing Safety Co-ordinator) at</p>
<p>_______________________________ (location) that the Safety Precautions set out in paragraph 1.2 are no</p>
<p>longer required and accordingly the RISSP is cancelled.</p>
<p>Signed &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;(Requesting Safety Co-ordinator)</p>
<p>at &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.(time) on &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..(Date)</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 87</p>
<p>OC6 SAFETY CO-ORDINATION &#8211; APPENDIX B</p>
<p>Northern Ireland Electricity</p>
<p>DISTRIBUTION CONTROL CENTRE/USER</p>
<p>RECORD OF INTER-SYSTEM SAFETY PRECAUTIONS (RISSP-B)</p>
<p>(Implementing Safety Co-ordinator&#8217;s Record)</p>
<p>RISSP NUMBER _</p>
<p>PART 1</p>
<p>1.1 HV APPARATUS IDENTIFICATION</p>
<p>Safety Precautions have been established by the Implementing Safety Co-ordinator to achieve (in so far as it is</p>
<p>possible from that side of the Connection Point) Safety From The System on the following HV Apparatus on</p>
<p>the Requesting Safety Co-ordinator&#8217;s System: [State identity - name(s) and, where applicable, identification of</p>
<p>the HV circuit(s) up to the Connection Point]:</p>
<p>1.2 SAFETY PRECAUTIONS ESTABLISHED</p>
<p>(a) ISOLATION</p>
<p>[State the Location(s) at which Isolation has been established. For each Location, identify each point of</p>
<p>Isolation. For each point of Isolation, state the means by which the Isolation has been achieved and whether</p>
<p>immobilised and Locked, Caution Notice affixed or other safety procedures applied, as appropriate.]</p>
<p>(b) EARTHING</p>
<p>[State the Location(s) at which Earthing has been established. For each Location, identify each point of</p>
<p>Earthing. For each point of Earthing, state the means by which the Earthing has been achieved and whether</p>
<p>immobilised and Locked or other safety procedures applied, as appropriate].</p>
<p>1.3 ISSUE</p>
<p>I have confirmed to ______________________________ (name of Requesting Safety Co-ordinator) at</p>
<p>___________________________________ (location) that the Safety Precautions identified in paragraph 1.2 have</p>
<p>been established and that instructions will not be issued at my location for their removal until this RISSP is</p>
<p>cancelled.</p>
<p>Signed &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..(Implementing Safety Co-ordinator)</p>
<p>at &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. (time) on &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.(date)</p>
<p>Distribution Code 1 May 2010</p>
<p>OC6 &#8211; Safety Co-ordination Page 88</p>
<p>PART 2</p>
<p>2.1 CANCELLATION</p>
<p>I have received confirmation from _________________________________ (name of the Requesting Safety Coordinator)</p>
<p>at _______________________________ (location) that the Safety Precautions set out in paragraph</p>
<p>1.2 are no longer required and accordingly the RISSP is cancelled.</p>
<p>Signed &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;(Implementing Safety Co-ordinator)</p>
<p>at &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.(time) on &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..(Date)</p>
<p>(Note: This form to be a different colour from RISSP-A)</p>
<p>Distribution Code 1 May 2010</p>
<p>OC7 – Contingency Planning Page 89</p>
<p>Operating Code 7 – Contingency Planning</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 7 (&#8220;OC7&#8243;) covers the following:-</p>
<p>(a) The DNO’s role in the implementation of recovery procedures in the event of a</p>
<p>Total Shutdown or Partial Shutdown; and</p>
<p>(b) the procedure to be followed when the Distribution Service Centre is</p>
<p>incapacitated for any reason.</p>
<p>It recognises that the main role in the event of any of those situations arising will be</p>
<p>undertaken by the TSO, and that under the Grid Code and the related emergency</p>
<p>procedures the DNO will principally be acting in accordance with the instructions of</p>
<p>the TSO.</p>
<p>1.2 It should be noted that, under Article 58 of the Order, the Department may give</p>
<p>directions to the DNO, the TSO and/or any Generator and any Supplier for the</p>
<p>purpose of, &#8220;mitigating the effects of any civil emergency which may occur&#8221; (i.e. for</p>
<p>the purposes of planning for dealing with a civil emergency); a civil emergency is</p>
<p>defined in the Order as &#8220;any natural disaster or other emergency which, in the opinion</p>
<p>of the Department, is or may be likely to disrupt electricity supplies&#8221;.</p>
<p>1.3 Additionally, under the Energy Act 1976, the Secretary of State has powers to make</p>
<p>orders and give directions controlling the production, supply, acquisition or use of</p>
<p>electricity, where an Order in Council under Section 3 is in force declaring that there is</p>
<p>an actual or imminent emergency affecting electricity supplies. In the event that any</p>
<p>such directions are given or orders made under the Energy Act 1976, the provisions of</p>
<p>the Distribution Code will be suspended insofar as they are inconsistent with them.</p>
<p>2 Objective</p>
<p>The overall objectives of OC7 are:</p>
<p>(a) to outline and enable co-ordination between the DNO and Users in the situation</p>
<p>where the TSO under the Grid Code is seeking to recover from a Total or</p>
<p>Partial Shutdown to achieve, as far as possible, restoration and Re-</p>
<p>Synchronisation of the Total System and to enable Demand once again to be</p>
<p>satisfied in the shortest possible time; and</p>
<p>(b) to ensure that the NI System can continue to operate in the event that the</p>
<p>Distribution Service Centre is incapacitated for any reason.</p>
<p>3 Scope</p>
<p>3.1 OC7 applies to the DNO and to Users. Users in this OC7 means:</p>
<p>(a) Generators;</p>
<p>(b) Suppliers; and</p>
<p>Distribution Code 1 May 2010</p>
<p>OC7 – Contingency Planning Page 90</p>
<p>(c) Demand Customers in respect of Connection Sites with a Demand of 1MW</p>
<p>and above.</p>
<p>4 Black Start Procedure</p>
<p>4.1 Total Shutdown</p>
<p>When a &#8220;Total Shutdown&#8221; occurs, namely where all generation has ceased and there is</p>
<p>no electricity supply across any Interconnectors and the Inter-jurisdictional Tie Lines</p>
<p>between Northern Ireland and the Republic of Ireland resulting in the Total System</p>
<p>having shutdown, it is not possible for the Total System to begin to function again</p>
<p>without the TSO’s directions relating to a Black Start.</p>
<p>4.2 Partial Shutdown</p>
<p>When a &#8220;Partial Shutdown&#8221; occurs, namely a situation which is the same as a Total</p>
<p>Shutdown except that all generation has ceased in a separate part of the Total System</p>
<p>and there is no electricity supply to that part of the Total System and, therefore, that</p>
<p>part of the Total System is shutdown, it is not possible for that part of the Total</p>
<p>System to begin to function again without the TSO directions relating to a Black Start.</p>
<p>4.3 Licence Standards</p>
<p>During a Total Shutdown or Partial Shutdown and during the period leading up to</p>
<p>such shutdowns and the subsequent recovery, the Licence Standards may not be met</p>
<p>and the whole or any part of the Total System may be operated outside normal voltage</p>
<p>and/or Frequency.</p>
<p>4.4 Black Start situation</p>
<p>In the event of a Total Shutdown or Partial Shutdown, the DNO will inform Users</p>
<p>which in the DNO’s opinion need to be informed that a Total Shutdown or, as the case</p>
<p>may be, a Partial Shutdown, exists and that it has been notified by the TSO that the</p>
<p>TSO intends to implement a Black Start.</p>
<p>4.5 Black Start</p>
<p>4.5.1 The procedure necessary for a recovery from a Total Shutdown or Partial</p>
<p>Shutdown is a &#8220;Black Start&#8221;. The procedure for a Partial Shutdown is the</p>
<p>same as that for a Total Shutdown except that it applies only to a part of the</p>
<p>Total System. It should be noted that a Partial Shutdown may affect parts of</p>
<p>the Total System which are not themselves shutdown.</p>
<p>4.5.2 The overall strategy for recovery from a Total Shutdown or Partial Shutdown</p>
<p>will, in general, include the overlapping phases of establishment by the TSO of</p>
<p>isolated Power Stations, together with complementary local Demand, termed</p>
<p>&#8220;Power Islands&#8221;, step by step integration of these Power Islands into larger subsystems</p>
<p>and, eventually, complete re-establishment of the Total System.</p>
<p>4.5.3 The TSO will, in accordance with the Grid Code, be instructing the DNO to</p>
<p>assist in relation to this process and under this OC7 the DNO may contact Users</p>
<p>Distribution Code 1 May 2010</p>
<p>OC7 – Contingency Planning Page 91</p>
<p>to discuss and instruct Users in relation to the role they are to play as part of the</p>
<p>recovery.</p>
<p>4.5.4 The conclusion of the Black Start and the time of the return to normal</p>
<p>operation of the Total System will be determined by the TSO which shall</p>
<p>inform the DNO, in accordance with the terms of the Grid Code. The DNO</p>
<p>will then inform Users which in the DNO’s opinion need to be informed, that</p>
<p>the Black Start situation no longer exists and that normal operation of the Total</p>
<p>System has begun.</p>
<p>5 Loss of the Distribution Service Centre</p>
<p>If the event of the temporary loss of the Distribution Service Centre the DNO will</p>
<p>have arrangements in place whereby the DNO may transfer the functions of the</p>
<p>Distribution Service Centre to an alternative control facility whereupon the DNO will</p>
<p>inform Users of the communications details for the new location.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC8 – Numbering and Nomenclature of Plant and Apparatus at Connection Sites Page 92</p>
<p>Operating Code 8 – Numbering and Nomenclature of Plant and Apparatus at Connection</p>
<p>Sites</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 8 (“OC8”) sets out the responsibilities and procedures for</p>
<p>determining and notifying the DNO and Users of the numbering and/or nomenclature</p>
<p>of the other&#8217;s Plant and/or Apparatus at Connection Sites. For clarification,</p>
<p>nomenclature shall include the selection of Substation names.</p>
<p>1.2 The numbering and/or nomenclature of Plant and/or Apparatus is to be included in an</p>
<p>Ownership Diagram prepared for each Connection Site as provided in the</p>
<p>Connection Conditions.</p>
<p>2 Objectives</p>
<p>The prime objective embodied in this OC8 is to ensure that at any Connection Site</p>
<p>items of Plant and/or Apparatus has numbering and/or nomenclature that, so far as</p>
<p>possible, has been mutually agreed and that has been notified between the DNO and</p>
<p>Users to ensure, so far as is reasonably practicable, the safe and effective operation of</p>
<p>the Distribution System and the User System by minimising the risk of error in</p>
<p>identifying Plant and/or Apparatus.</p>
<p>3 Scope</p>
<p>3.1 OC8 applies to the DNO and to Users. Users in this OC8, means:</p>
<p>(a) Generators in respect of their Generating Units connected to the Distribution</p>
<p>System at 33kV; and</p>
<p>(b) Demand Customers in respect of their 33kV Connection Sites; and</p>
<p>(c) those further Generators and Demand Customers in respect of their HV</p>
<p>Connection Sites as notified by the DNO in writing.</p>
<p>4 Procedure</p>
<p>4.1 General requirement</p>
<p>4.1.1 Plant and/or Apparatus of a User at a Connection Site shall have numbering</p>
<p>and/or nomenclature which cannot be confused with that of the DNO’s Plant</p>
<p>and Apparatus at that Connection Site.</p>
<p>4.1.2 In furtherance of the general requirement set out in paragraph 4.1.1 above, no</p>
<p>User will install, or permit the installation of, any Plant and/or Apparatus</p>
<p>which has numbering and/or nomenclature which could be confused with that of</p>
<p>the DNO which is either already on that Connection Site or which the DNO has</p>
<p>notified the User will be installed on that Connection Site. The procedure for</p>
<p>determining the applicable numbering and nomenclature for new and existing</p>
<p>Connection Sites is set out in paragraphs 4.2.1 and 4.2.2 respectively.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC8 – Numbering and Nomenclature of Plant and Apparatus at Connection Sites Page 93</p>
<p>4.2 Plant and Apparatus</p>
<p>4.2.1 New Connection Sites</p>
<p>When a User intends to install or the DNO intends to install Plant and/or</p>
<p>Apparatus as part of the construction and commissioning of a new Connection</p>
<p>Site, the proposed numbering and/or nomenclature shall be notified as part of</p>
<p>the production of the Ownership Diagram in accordance with the provisions of</p>
<p>the Connection Conditions. The principles to apply to determine whether that</p>
<p>proposed numbering and/or nomenclature is acceptable will be those set out in</p>
<p>this OC8 (including, for the avoidance of doubt, the provisions of paragraph</p>
<p>4.2.2(e)).</p>
<p>4.2.2 Existing Connection Sites</p>
<p>(a) When a User intends to install or the DNO intends to install Plant</p>
<p>and/or Apparatus at an existing Connection Site the proposed</p>
<p>numbering and/or nomenclature to be adopted for the Plant and/or</p>
<p>Apparatus shall be notified to the other.</p>
<p>(b) The notification shall be made in writing to the other and will consist of</p>
<p>a revised Ownership Diagram incorporating the proposed new Plant</p>
<p>and/or Apparatus to be installed and its proposed numbering and/or</p>
<p>nomenclature.</p>
<p>(c) The notification shall be made at least six months (or such shorter period</p>
<p>as the DNO or the User, as the case may be, may agree) prior to the</p>
<p>proposed installation of the Plant and/or Apparatus.</p>
<p>(d) The recipient of the notification shall respond in writing within one</p>
<p>month of the receipt of the notification confirming receipt and</p>
<p>confirming whether the proposed numbering and/or nomenclature is</p>
<p>acceptable or, if not, what would be acceptable.</p>
<p>(e) In the event that agreement cannot be reached between the DNO and the</p>
<p>User, the DNO acting reasonably, shall have the right to determine the</p>
<p>numbering and nomenclature to be applied at the Connection Site.</p>
<p>4.3 Changes to existing Plant and Apparatus</p>
<p>Where there needs to be a change of the existing numbering or nomenclature of any of</p>
<p>the DNO’s Plant and/or Apparatus at a Connection Site or a User needs to change</p>
<p>the existing numbering or nomenclature of any of its Plant and/or Apparatus at a</p>
<p>Connection Site, the provisions of paragraph 4.2.2 shall apply, with any amendments</p>
<p>necessary to reflect that only a change is being made.</p>
<p>4.4 Clear labelling</p>
<p>The DNO shall be responsible for ensuring the provision, erection and maintenance of</p>
<p>clear and unambiguous labelling showing the numbering and nomenclature of the</p>
<p>DNO’s Plant and/or Apparatus at Connection Sites and each User shall be</p>
<p>Distribution Code 1 May 2010</p>
<p>OC8 – Numbering and Nomenclature of Plant and Apparatus at Connection Sites Page 94</p>
<p>responsible for the provision, erection and maintenance of clear and unambiguous</p>
<p>labelling showing the numbering and nomenclature of the User’s Plant and/or</p>
<p>Apparatus at Connection Sites.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC9 – System Tests Page 95</p>
<p>Operating Code 9 – System Tests</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 9 (&#8220;OC9&#8243;) relates to the following types of test (all of which are</p>
<p>referred to as &#8220;System Tests&#8221;):-</p>
<p>(a) tests to be carried out by a User or the DNO which involve or may involve</p>
<p>simulating conditions or the controlled application of irregular, unusual or</p>
<p>extreme conditions on the User’s System or the Distribution System (as the case</p>
<p>may be) which may have a material effect on the Total System, beyond the</p>
<p>User’s System or the Distribution System (as the case may be);</p>
<p>(b) tests to be carried out by the TSO or a user under the Grid Code which involve</p>
<p>or may involve simulating conditions or the controlled application of irregular,</p>
<p>unusual or extreme conditions on the NI System or that user&#8217;s system (as the case</p>
<p>may be) which may have a material effect on the Distribution System and the</p>
<p>System of a User under this Distribution Code, and which the DNO therefore</p>
<p>decides, in its view, should be raised as a connected system test (a “Connected</p>
<p>System Test”) under this OC9 to ensure that Users under this Distribution Code</p>
<p>are included within the consideration of the system test being proposed under the</p>
<p>Grid Code; and</p>
<p>(c) Commissioning/Acceptance Tests of Plant and Apparatus to be carried out by a</p>
<p>User or the DNO which involve or may involve the application of irregular,</p>
<p>unusual or extreme conditions and which may have a material effect on the Total</p>
<p>System, beyond the User’s System or the Distribution System (as the case may</p>
<p>be).</p>
<p>1.2 OC9 only deals with the responsibilities and procedures for arranging and carrying out</p>
<p>tests which have (or may have) a material effect on the Systems of both the DNO and</p>
<p>Users. Accordingly, where a test proposed by a User will not have a material effect on</p>
<p>the Distribution System or where a test proposed by the DNO will not have a material</p>
<p>effect on a User System, such test will not fall within this OC9 and OC9 shall not apply</p>
<p>to it.</p>
<p>1.3 OC9 does not cover Commissioning/Acceptance Tests of a User’s Plant and</p>
<p>Apparatus which will have no material effect on the Distribution System beyond the</p>
<p>User’s System; such tests will be undertaken solely pursuant to paragraph 10 and 11 in</p>
<p>the Connection Conditions. Neither does it cover the type of tests which are dealt with</p>
<p>in OC10, &#8220;Testing, Monitoring and Investigation&#8221;.</p>
<p>1.4 The Grid Code contains provisions relating to system tests under the Grid Code, which</p>
<p>will be initiated by the TSO or users under the Grid Code. The DNO is a user under the</p>
<p>Grid Code and certain Users under the Distribution Code will also be users under the</p>
<p>Grid Code. A system test under the Grid Code may therefore involve, and affect, the</p>
<p>Distribution System, and the TSO is required under the Grid Code to obtain agreement</p>
<p>from all affected Grid Code users. In that instance if the DNO was a user so affected</p>
<p>under the Grid Code, the DNO may decide that it should initiate a Connected System</p>
<p>Test under this OC9 in order to ensure that Users are involved in the Grid Code system</p>
<p>Distribution Code 1 May 2010</p>
<p>OC9 – System Tests Page 96</p>
<p>test.</p>
<p>2 Objective</p>
<p>2.1 The overall objectives of OC9 are:-</p>
<p>(a) to ensure, so far as possible, that tests proposed to be carried out:</p>
<p>(i) by a User which may have a material effect on the Total System or any</p>
<p>part of the Total System (in addition to that User’s System) including the</p>
<p>Distribution System;</p>
<p>(ii) by the DNO which may have a material effect on a Users’ System (in</p>
<p>addition to the Distribution System); or</p>
<p>(iii) under the Grid Code in certain circumstances;</p>
<p>do not threaten the safety of personnel or threaten to damage Plant and/or</p>
<p>Apparatus and cause minimum detriment to the DNO and Users. These tests will</p>
<p>not affect the Transmission System and therefore the reference to Total System</p>
<p>above excludes the Transmission System; and</p>
<p>(b) to set out the procedures to be followed for establishing and where appropriate</p>
<p>reporting such tests and to set out guidelines for which tests need to be notified to</p>
<p>the DNO prior to the test being carried out.</p>
<p>3 Scope</p>
<p>3.1 OC9 applies to the DNO and to Users which, in this OC9 means:</p>
<p>(a) Generators, and</p>
<p>(b) Demand Customers.</p>
<p>4 Procedure</p>
<p>4.1 Proposal Notice</p>
<p>4.1.1 The level of Demand on the Distribution System varies substantially according</p>
<p>to the time of day and time of year and, consequently, certain System Tests</p>
<p>which may have a significant impact on the Distribution System (for example,</p>
<p>tests of the Full Load capability of a Generating Unit over a period of several</p>
<p>hours) can only be undertaken at certain times of the day and year. Other System</p>
<p>Tests, for example, those involving substantial MVAr generation, may also be</p>
<p>subject to timing constraints. It therefore follows that notice of System Tests</p>
<p>should be given as far in advance of the date on which they are proposed to be</p>
<p>carried out as reasonably practicable.</p>
<p>4.1.2 Where a User wishes to carry out a System Test it shall submit a notice (a</p>
<p>&#8220;Proposal Notice&#8221;) to the DNO as far in advance as is reasonably practicable of</p>
<p>the date it would like to undertake the proposed System Test. In the event that a</p>
<p>Distribution Code 1 May 2010</p>
<p>OC9 – System Tests Page 97</p>
<p>User submits to the DNO a programme for proposed</p>
<p>Commissioning/Acceptance Testing pursuant to paragraph 10.1.4 in the</p>
<p>Connection Conditions which the DNO considers may involve the application of</p>
<p>irregular, unusual or extreme conditions and which may have a material effect on</p>
<p>the Distribution System, beyond the User’s System, such programme shall be</p>
<p>treated as a Proposal Notice for the purposes of this OC9.</p>
<p>4.1.3 The Proposal Notice shall be in writing, or in such other form as the DNO and</p>
<p>the relevant User may otherwise agree (such agreement not to be unreasonably</p>
<p>withheld), and shall contain details of the nature and purpose of the proposed</p>
<p>System Test and shall indicate the identity and situation of the Plant and/or</p>
<p>Apparatus involved. In the case of a System Test involving a CDGU, the User</p>
<p>shall state in the Proposal Notice the level of Availability and the values for</p>
<p>Technical Parameters which will be declared for the CDGU for the period of the</p>
<p>test in accordance with SDC1 of the Grid Code and shall also include details of</p>
<p>the planned operation by the User as part of the test. In the case of a Generating</p>
<p>Plant, it will also confirm that the User will be arranging with the TSO for a</p>
<p>relevant Dispatch Instruction to be issued to it for the purposes of the test. For the</p>
<p>purposes of this paragraph 4.1, “Dispatch Instructions”, “Availability” and</p>
<p>“Technical Parameters” shall have the meaning given to such terms in the Grid</p>
<p>Code.</p>
<p>4.1.4 If the DNO is reasonably of the view that the information set out in the Proposal</p>
<p>Notice is insufficient, it will contact the person who submitted the Proposal</p>
<p>Notice (the &#8220;Test Proposer&#8221;) as soon as reasonably practicable, with a written</p>
<p>request for further information. The DNO shall not be required to do anything</p>
<p>under this OC9 until it is satisfied with the details supplied in the Proposal Notice</p>
<p>or pursuant to a request for further information.</p>
<p>4.1.5 If the DNO wishes to undertake a System Test or a Connected System Test, the</p>
<p>DNO shall be deemed to have received a Proposal Notice for that System Test.</p>
<p>4.1.6 The DNO will use all reasonable endeavours to accommodate requests for System</p>
<p>Tests but has absolute discretion as to the timing of such tests (which discretion</p>
<p>will be exercised reasonably consistently with previous practice) to ensure the</p>
<p>proper operation of the Distribution System and so as to ensure that the Licence</p>
<p>Standards are not breached.</p>
<p>4.1.7 Without prejudice to the general description of the types of System Tests which</p>
<p>have to be dealt with under this OC9, as set out in paragraph 1.1 above, each</p>
<p>Generator must submit a Proposal Notice to the DNO if it proposes to carry out</p>
<p>any of the following tests, each of which is therefore a System Test:-</p>
<p>(a) VAr limiter tests; and</p>
<p>(b) Load rejection tests.</p>
<p>4.2 Establishment of Test Panel</p>
<p>(a) Using the information supplied (or deemed to have been supplied) to it under</p>
<p>Distribution Code 1 May 2010</p>
<p>OC9 – System Tests Page 98</p>
<p>paragraph 4.1, the DNO will determine, in its reasonable estimation, which</p>
<p>Users, other than the Test Proposer, may be materially affected by the proposed</p>
<p>System Test and will notify such Users accordingly.</p>
<p>(b) The DNO will then determine, in its reasonable opinion, whether a Test Panel is</p>
<p>required taking into account the degree of severity of its possible effect on the</p>
<p>Systems of the DNO and Users. A Test Panel will not generally be needed for a</p>
<p>routine test and, since the majority of System Tests are routine, the establishment</p>
<p>of a Test Panel will be the exception rather than the rule. If the DNO, in its</p>
<p>reasonable discretion, decides that a Test Panel is necessary, the provisions set</p>
<p>out in the Appendix to this OC9 will apply.</p>
<p>4.3 The DNO Supervision</p>
<p>(a) If the DNO determines that no Test Panel is required, it will determine, acting</p>
<p>reasonably, whether and, where appropriate, when the proposed System Test can</p>
<p>take place and it will consider:-</p>
<p>(i) the details of the nature, technical reasons for and timing of the proposed</p>
<p>System Test and other matters set out in the Proposal Notice (together</p>
<p>with any further information requested by the DNO under OC9.4.1.4);</p>
<p>(ii) the economic, operational and risk implications of the proposed System</p>
<p>Test; and</p>
<p>(iii) the possibility of combining the proposed System Test with any other tests</p>
<p>and with Plant and/or Apparatus Outages which arise pursuant to the</p>
<p>Outage Planning requirements of the DNO and Users.</p>
<p>If the DNO determines that the proposed System Test cannot take place, it will,</p>
<p>insofar as it is able to do so without breaching any obligations regarding</p>
<p>confidentiality contained either in the Licence held by the DNO or in any</p>
<p>agreement, notify the Test Proposer of the reasons for such decision in such</p>
<p>degree of detail as the DNO considers reasonable in the circumstances.</p>
<p>(b) Users identified by the DNO under paragraph 4.2.1 (and the Test Proposer) shall</p>
<p>be obliged to supply the DNO, upon written request, with such details as the</p>
<p>DNO reasonably requires in order to consider the proposed System Test.</p>
<p>(c) The DNO will consult with each User identified by it under paragraph 4.2.1</p>
<p>regarding the proposed System Test including, in particular, the effects which</p>
<p>such test is likely to have on such User’s System.</p>
<p>4.4 The DNO Test Programme</p>
<p>(a) As soon as practicable the DNO shall, if it approves of the proposed System Test</p>
<p>taking place (of which it will notify the Test Proposer), taking into account the</p>
<p>factors specified in paragraph 4.3.1, prepare a programme (the &#8220;Test</p>
<p>Programme&#8221;), in such detail as the DNO considers, in its reasonable opinion, to</p>
<p>be appropriate for the test, which will include:-</p>
<p>Distribution Code 1 May 2010</p>
<p>OC9 – System Tests Page 99</p>
<p>(a) the procedure to be adopted for carrying out the System Test, including</p>
<p>the switching sequence and proposed timings of the switching sequence;</p>
<p>(b) the manner in which the System Test is to be monitored;</p>
<p>(c) a list of those members of staff to be involved in carrying out the System</p>
<p>Test, including those who will be responsible for site safety; and</p>
<p>(d) such other matters as the DNO considers appropriate including (without</p>
<p>limitation) matters suggested by Users identified by the DNO pursuant to</p>
<p>paragraph 4.2.1.</p>
<p>(b) The DNO, the Test Proposer and each User identified by the DNO under</p>
<p>paragraph 4.2.1 will determine by agreement the basis on which the costs of the</p>
<p>System Test (including unanticipated costs, for example, costs arising from</p>
<p>modifications etc) shall be borne as between the affected parties (the general</p>
<p>principle being that the Test Proposer will bear such costs). If agreement cannot</p>
<p>be reached (each party having acted in good faith), the System Test will be</p>
<p>cancelled.</p>
<p>(c) Without prejudice to the provisions of paragraph 4.1, the DNO shall be entitled to</p>
<p>require the proposed System Test to be modified, delayed or cancelled if, in its</p>
<p>reasonable opinion, it considers that such test would impose unacceptable effects</p>
<p>on the Distribution System or any User System.</p>
<p>(d) If the DNO requires the proposed System Test to be cancelled or if it requires</p>
<p>such test to be delayed or modified but the Test Proposer considers that such</p>
<p>delay or modification is not possible, the proposed System Test shall not take</p>
<p>place.</p>
<p>(e) The Test Programme will, subject to paragraph 4.4.6, bind the Test Proposer to</p>
<p>act in accordance with the provisions of the Test Programme in relation to the</p>
<p>proposed System Test.</p>
<p>(f) Any problems with the proposed System Test perceived by the Test Proposer or</p>
<p>any affected User or the DNO which arise or are anticipated after the issue of the</p>
<p>Test Programme and prior to the day of the proposed System Test must be</p>
<p>notified by the Test Proposer or affected User or the DNO (as the case may be)</p>
<p>to the others as soon as possible in writing. If, in any such case, the DNO decides</p>
<p>that these anticipated problems merit an amendment to, or postponement of, the</p>
<p>System Test, it shall notify the Test Proposer and affected Users accordingly.</p>
<p>(g) If, on the day of the proposed System Test, operating conditions on the</p>
<p>Distribution System are such that any of the DNO, the Test Proposer or an</p>
<p>affected User wishes to delay or cancel the start or continuance of the System</p>
<p>Test, they shall immediately inform the others of this decision and the reasons for</p>
<p>it. The DNO shall then postpone or cancel, as the case may be, the System Test</p>
<p>and another suitable time and date shall be arranged in accordance with this</p>
<p>paragraph 4.4.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC9 – System Tests Page 100</p>
<p>Appendix</p>
<p>1 Test Panel supervision</p>
<p>1.1 If the DNO determines pursuant to paragraph 4.2.2 that a Test Panel is required, it will</p>
<p>appoint a representative to co-ordinate the System Test (the &#8220;Test Co-ordinator&#8221;) as</p>
<p>soon as reasonably practicable after it has, or is deemed to have, received a Proposal</p>
<p>Notice and in any event prior to the distribution of the Preliminary Notice referred to</p>
<p>below. The Test Co-ordinator shall act as Chairman of the Test Panel and shall be a full</p>
<p>member of the Test Panel.</p>
<p>1.2 The DNO will notify all Users identified by it under paragraph 4.2.1 of the proposed</p>
<p>System Test by a notice in writing (a &#8220;Preliminary Notice&#8221;) and will send a copy of the</p>
<p>Preliminary Notice to the Test Proposer. The Preliminary Notice will contain:</p>
<p>(a) the details of the nature and purpose of the proposed System Test, the identity</p>
<p>and situation of the Plant and/or Apparatus involved, the identities of the Users</p>
<p>identified by the DNO under paragraph 4.2.1 and the identity of the Test</p>
<p>Proposer;</p>
<p>(b) an invitation to nominate within one month a suitably qualified representative (or</p>
<p>representatives if the Test Co-ordinator considers that it is appropriate for a</p>
<p>particular User to nominate more than one representative) to be a member of the</p>
<p>Test Panel for the proposed System Test; and</p>
<p>(c) the name of the DNO representative whom the DNO has appointed as the Test</p>
<p>Co-ordinator and who will be a member of the Test Panel for the proposed</p>
<p>System Test together with the names of any other representatives whom the DNO</p>
<p>has nominated to be members of the Test Panel.</p>
<p>1.3 The Preliminary Notice will be sent within one month of the later of either the receipt by</p>
<p>the DNO of the Proposal Notice, or of the receipt of any further information requested</p>
<p>by the DNO under paragraph 4.1.3. Where the DNO is the proposer of the System Test,</p>
<p>the Preliminary Notice will be sent within one month of the proposed System Test being</p>
<p>fully formulated.</p>
<p>1.4 Replies to the invitation in the Preliminary Notice to nominate a representative to be a</p>
<p>member of the Test Panel must be received by the DNO within one month of the date on</p>
<p>which the Preliminary Notice was sent to the User by the DNO. Any User which has</p>
<p>not replied within that period will not be entitled to be represented on the Test Panel. If</p>
<p>the Test Proposer does not reply within that period, the proposed System Test will not</p>
<p>take place and the DNO will notify all Users identified by it under paragraph 4.2.1</p>
<p>accordingly.</p>
<p>1.5 The DNO will, as soon as possible after the expiry of that one month period, appoint the</p>
<p>nominated persons to the Test Panel and notify all Users identified by it under paragraph</p>
<p>4.2.1 and the Test Proposer, of the composition of the Test Panel.</p>
<p>2 Test Panel</p>
<p>Distribution Code 1 May 2010</p>
<p>OC9 – System Tests Page 101</p>
<p>2.1 A meeting of the Test Panel will take place as soon as possible after the DNO has</p>
<p>notified all Users identified by it under paragraph 4.2.1 and the Test Proposer of the</p>
<p>composition of the Test Panel, and in any event within one month of the appointment of</p>
<p>the Test Panel.</p>
<p>2.2 The Test Panel shall consider:</p>
<p>(a) the details of the nature, technical reasons for and timing of the proposed System</p>
<p>Test and other matters set out in the Proposal Notice (together with any further</p>
<p>information requested by the DNO under paragraph 4.1.3);</p>
<p>(b) the economic, operational and risk implications of the proposed System Test;</p>
<p>(c) the possibility of combining the proposed System Test with any other tests and</p>
<p>with Plant and/or Apparatus Outages which arise pursuant to the Operational</p>
<p>Planning requirements of the DNO and Users; and</p>
<p>(d) whether, at the conclusion of the System Test, the Test Proposer should be</p>
<p>required to prepare a written report on the System Test (a &#8220;Final Report&#8221;) in</p>
<p>accordance with paragraph 4 in the Appendix and, if so, the period within which</p>
<p>the Final Report must be prepared.</p>
<p>2.3 Users identified by the DNO under OC9.4.2.1, the Test Proposer (whether or not they</p>
<p>are represented on the Test Panel) and the DNO shall be obliged to supply the Test</p>
<p>Panel, upon written request, with such details as the Test Panel reasonably requires in</p>
<p>order to consider the proposed System Test.</p>
<p>2.4 The Test Panel shall be convened by the Test Co-ordinator as often as he considers</p>
<p>necessary to conduct its business.</p>
<p>3 Test Panel Test Programme</p>
<p>3.1 As soon as practicable after its first meeting, the Test Panel shall, taking into account the</p>
<p>factors specified in paragraph A.2.2 in the Appendix, prepare a programme (the &#8220;Test</p>
<p>Programme&#8221;) which will include:-</p>
<p>(a) the procedure to be adopted for carrying out the System Test, including the</p>
<p>switching sequence and proposed timings of the switching sequence;</p>
<p>(b) the manner in which the System Test is to be monitored;</p>
<p>(c) a list of those members of staff to be involved in carrying out the System Test,</p>
<p>including those who will be responsible for site safety; and</p>
<p>(d) such other matters as the Test Panel considers to be appropriate.</p>
<p>3.2 The Test Panel shall also determine the basis on which the costs of the System Test</p>
<p>(including unanticipated costs) shall be borne as between the affected parties (the general</p>
<p>principle being that the Test Proposer will bear such costs). If the Test Panel cannot</p>
<p>agree on this (each party having acted in good faith), the System Test will be cancelled.</p>
<p>Distribution Code 1 May 2010</p>
<p>OC9 – System Tests Page 102</p>
<p>3.3 The Test Co-ordinator shall be entitled to require the proposed System Test to be</p>
<p>modified, delayed or cancelled if, in his reasonable opinion, he considers that such test</p>
<p>would impose unacceptable effects on the Distribution System or on any User System.</p>
<p>3.4 If the Test Co-ordinator requires the proposed System Test to be cancelled or if he</p>
<p>requires such test to be delayed or modified but the Test Proposer considers that such</p>
<p>delay or modification is not possible, the proposed System Test shall not take place and</p>
<p>the Test Panel will disband automatically.</p>
<p>3.5 If the Test Co-ordinator requires the proposed System Test to be modified or delayed</p>
<p>and such modification or delay is possible, the Test Panel shall, as soon as practicable,</p>
<p>revise the Test Programme accordingly.</p>
<p>3.6 The Test Programme will, subject to paragraph 3.7 in this Appendix, bind all recipients</p>
<p>to act in accordance with the provisions of the Test Programme in relation to the</p>
<p>proposed System Test.</p>
<p>3.7 Any problems with the proposed System Test which arise or are anticipated after the</p>
<p>issue of the Test Programme and prior to the day of the proposed System Test must be</p>
<p>notified to the Test Co-ordinator as soon as possible in writing. If the Test Coordinator</p>
<p>decides that these anticipated problems merit an amendment to, or</p>
<p>postponement of, the System Test, he shall notify the Test Proposer (unless the test was</p>
<p>proposed by the DNO) and each User identified by the DNO under paragraph 4.2.1</p>
<p>accordingly.</p>
<p>3.8 If, on the day of the proposed System Test, operating conditions on the Distribution</p>
<p>System are such that any party involved in the proposed System Test wishes to delay or</p>
<p>cancel the start or continuance of the System Test, they shall immediately inform the</p>
<p>Test Co-ordinator of this decision and the reasons for it. The Test Co-ordinator shall</p>
<p>then postpone or cancel, as the case may be, the System Test and shall, if possible, agree</p>
<p>with the Test Proposer (unless the test was proposed by the DNO) and all Users</p>
<p>identified by the DNO under paragraph 4.2.1 another suitable time and date. If he cannot</p>
<p>reach such agreement, the Test Co-ordinator shall reconvene the Test Panel as soon as</p>
<p>practicable, which will endeavour to arrange another suitable time and date for the</p>
<p>System Test, in which case the relevant provisions of this OC9 shall apply.</p>
<p>4 Connected System Tests</p>
<p>4.1 In the case of a Connected System Test, the timings and process outlined in this</p>
<p>Appendix may be amended by the DNO to co-ordinate with the process being undertaken</p>
<p>under the Grid Code.</p>
<p>5 Test Panel Final Report</p>
<p>5.1 At the conclusion of the System Test, the Test Proposer shall, if so decided by the Test</p>
<p>Panel pursuant to paragraph 2.2(d) in the Appendix, prepare a Final Report for</p>
<p>submission to the DNO and the other members of the Test Panel. The Final Report</p>
<p>shall be submitted within the period agreed by the Test Panel pursuant to paragraph</p>
<p>2.2(d).</p>
<p>Distribution Code 1 May 2010</p>
<p>OC9 – System Tests Page 103</p>
<p>5.2 The Test Proposer may omit from the Final Report matters which, in its reasonable</p>
<p>opinion, are confidential to it and the Final Report shall not be submitted to any person</p>
<p>who is not a member of the Test Panel unless the Test Panel, having considered the</p>
<p>confidentiality issues arising, shall have unanimously approved such submission.</p>
<p>5.3 The Final Report shall include a description of the Plant and/or Apparatus tested and</p>
<p>a description of the System Test carried out, together with the results and, where</p>
<p>appropriate, the conclusions and recommendations of the Test Panel.</p>
<p>5.4 When the Final Report has been prepared and submitted in accordance with paragraph</p>
<p>4.1 in this Appendix, the Test Panel will disband automatically. If a Final Report is</p>
<p>not required by the Test Panel then it will disband automatically upon the conclusion of</p>
<p>the System Test.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 104</p>
<p>Operating Code 10 – Testing, Monitoring and Investigation</p>
<p>1 Introduction</p>
<p>1.1 Operating Code No. 10 (&#8220;OC10&#8243;) specifies the procedures to be followed by the DNO</p>
<p>in carrying out:</p>
<p>(a) Monitoring of the compliance of Generating Units and Demand Customers’</p>
<p>Plant and/or Apparatus with the Connection Conditions;</p>
<p>(b) Testing:-</p>
<p>(i) in certain circumstances, (whether by means of a formal test or</p>
<p>verification by inspection) to ascertain whether the Connection</p>
<p>Conditions are being complied with in respect of Generating Units and</p>
<p>Demand Customer’s Plant and/or Apparatus; and</p>
<p>(ii) at the request of a User, in certain circumstances; and</p>
<p>(c) Investigations in relation to equipment and operational procedures at Power</p>
<p>Stations and other User Sites.</p>
<p>1.2 It should be noted that Testing and Monitoring under this OC10 are two different</p>
<p>procedures with, in general terms, DNO representatives being present at the Power</p>
<p>Station or User Site for a Test, but not for Monitoring.</p>
<p>2 Objectives</p>
<p>2.1 The objectives of OC10 are to establish whether Generating Units and Demand</p>
<p>Customers’ Plant and/or Apparatus comply with the Connection Conditions.</p>
<p>3 Scope</p>
<p>3.1 OC10 applies to the DNO and to Users. Users in this OC10 means:</p>
<p>(a) Generators; and</p>
<p>(b) Demand Customers in respect of their Connection Sites with a Demand of</p>
<p>1MW and above.</p>
<p>4 Procedure for Monitoring</p>
<p>4.1 Monitoring may be carried out at any time by the DNO and involves the analysis of</p>
<p>the output of Monitoring equipment (as required or permitted under the Connection</p>
<p>Conditions and/or the Connection Agreement) to show the output and/or performance</p>
<p>of a User’s Equipment in order to see whether the User’s Equipment is meeting the</p>
<p>requirements of the Connection Conditions. The output from such Monitoring</p>
<p>equipment installed may, amongst other uses, be used to Monitor the performance of</p>
<p>User’s Equipment in the event of variations in NI System Frequency.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 105</p>
<p>4.2 In determining whether a User’s equipment is meeting the requirements of the</p>
<p>Connection Conditions the DNO shall in each case give due regard to operating</p>
<p>conditions on the Distribution System.</p>
<p>4.3 If a User’s Equipment is not meeting the requirements of the Connection Conditions,</p>
<p>the DNO will, submit a Monitoring Notice to the User which will identify the</p>
<p>Connection Conditions requirements which have been Monitored and which have not</p>
<p>been met.</p>
<p>4.4 Consequences of Monitoring</p>
<p>4.4.1 The User will provide the DNO as soon as possible with an explanation of the</p>
<p>reasons for the failure and the actions it is proposing to undertake to enable its</p>
<p>equipment to meet the requirements of the Connection Conditions which it has</p>
<p>not met within a reasonable period.</p>
<p>4.4.2 The DNO and the User will then discuss the action which the user proposes to</p>
<p>take and will seek to reach agreement on any short term operational matters</p>
<p>necessary to protect the Distribution System and the Systems of other Users</p>
<p>and the time by which the requirements will be met. In the absence of</p>
<p>agreement between the User and the DNO on this, the DNO shall refer the</p>
<p>Distribution Code non-compliance to the Authority.</p>
<p>4.4.3 Once the User confirms to the DNO, in the agreed timescale, that its equipment</p>
<p>meets the relevant Connection Conditions requirements, the DNO may verify</p>
<p>that either by further Monitoring or by undertaking a Test under this OC10.</p>
<p>5 Procedure for Testing</p>
<p>5.1 In circumstances where the DNO reasonably considers that, in relation to User’s</p>
<p>Equipment, a User might be failing to comply with the Connection Conditions (or</p>
<p>where it wishes to verify that the equipment now meets the requirements where</p>
<p>Monitoring or a previous test has demonstrated non-compliance) the DNO may, upon</p>
<p>giving reasonable notice identifying the requirement concerned, send representatives to</p>
<p>the relevant User Site in order to verify by Testing or inspection (in the case of</p>
<p>Testing, conducted by the User) whether in relation to the item of User’s Equipment,</p>
<p>the Connection Conditions requirements are being met.</p>
<p>5.2 Each User must allow the DNO representatives access to all relevant parts of its User</p>
<p>Site for the purposes of this OC10.</p>
<p>5.3 The procedure for the Test, and the criteria for passing the Test, will, if not agreed</p>
<p>between the DNO and the User, be as determined by the DNO acting reasonably and as</p>
<p>notified to the User at the time and the User will comply with all reasonable</p>
<p>instructions of the DNO in carrying out the Test.</p>
<p>5.4 In determining whether the item of User’s Equipment, as the case may be, has passed</p>
<p>a Test, due regard will be given by the DNO to operating conditions on the NI System.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 106</p>
<p>5.5 If in relation to the item of User’s Equipment the User fails the Test then: it must</p>
<p>provide the DNO with a written report specifying in reasonable detail the reasons for</p>
<p>the failure, such report to be submitted within 5 Business Days of the Test. The User</p>
<p>must then within five further Business Days submit in writing to the DNO for approval</p>
<p>the date by which the User proposes to have brought the equipment to a condition</p>
<p>where it would meet the requirements of the Connection Conditions. The DNO may</p>
<p>either accept this period, or suggest a shorter period. In the absence of agreement</p>
<p>between the User and the DNO on this, the DNO shall refer the Distribution Code</p>
<p>non-compliance to the Authority.</p>
<p>5.6 Once the User confirms to the DNO, in the agreed timescale, that its equipment meets</p>
<p>the relevant Connection Conditions requirements, the DNO may verify that either by</p>
<p>Monitoring or by undertaking a further Test under this OC10.</p>
<p>6 Investigations</p>
<p>6.1 The DNO may, upon giving reasonable notice (in any event not less than 2 Business</p>
<p>Days), send representatives to a Power Station or User Site in order to investigate any</p>
<p>equipment or operational procedure.</p>
<p>6.2 An Investigation may take place only for the purposes of enabling the DNO to fulfil its</p>
<p>obligations relating to the operation of the Distribution System (and where in the</p>
<p>reasonable opinion of the DNO in the absence of an Investigation it would be unable</p>
<p>properly to fulfil such obligations).</p>
<p>6.3 An Investigation shall not take place during or less than 2 days before or after a Test in</p>
<p>respect of Plant or equipment at the relevant Power Station or User Site.</p>
<p>6.4 The DNO’s notice under paragraph 6.1 shall specify:</p>
<p>(a) the nature and purpose of the Investigation and the reasons therefor;</p>
<p>(b) the equipment or operational procedure subject to the Investigation; and</p>
<p>(c) the procedure (as reasonably determined by the DNO) for the Investigation.</p>
<p>6.5 The scope of an Investigation and the information and parts of the Power Station or</p>
<p>User Site to which the DNO shall be entitled to access shall be limited to that required</p>
<p>for the purposes of the Investigation as specified in the DNO’s notice under paragraph</p>
<p>6.4.</p>
<p>6.6 The User shall comply with the reasonable requests of the DNO in carrying out the</p>
<p>Investigation, and allow the DNO representative access to all relevant parts of the</p>
<p>Power Station or User Site to conduct the Investigation.</p>
<p>6.7 An Investigation shall not of itself result in consequences for the User under the</p>
<p>Distribution Code or Connection Agreement.</p>
<p>6.8 These provisions shall be without prejudice to DNO’s rights of access under any other</p>
<p>document or agreement.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 107</p>
<p>7 Testing at the request of a User</p>
<p>7.1 A User shall, subject to paragraph 7.2, be entitled, by notice in writing setting out the</p>
<p>desired procedure (or, if the DNO acting reasonably so agrees, taking into account the</p>
<p>nature of the test being requested, by oral request specifying the desired procedure,</p>
<p>such oral request to be confirmed in writing as soon as reasonably practicable</p>
<p>thereafter), to request the DNO to assist it in carrying out a test on any of its Plant</p>
<p>and/or Apparatus as such User, acting reasonably in accordance with Prudent</p>
<p>Operating Practice, may request.</p>
<p>7.2 The DNO shall be entitled to refuse to conduct any test requested under paragraph 7.1</p>
<p>(or refuse to conduct it in accordance with the procedure or at the time requested) if, in</p>
<p>the DNO’s reasonable opinion, it is unsafe for the Distribution System to conduct such</p>
<p>a test or if it is otherwise not practicable to do so (or to do so in accordance with the</p>
<p>procedure or at the time requested) for Distribution System or any other reasons,</p>
<p>including if all reasonable costs and expenses of the DNO are not, in the DNO’s</p>
<p>reasonable view, adequately covered by the User. The DNO may only continue to</p>
<p>refuse to conduct the test (or to conduct it in accordance with the procedure) for so long</p>
<p>as these reasons continue.</p>
<p>7.3 If the DNO refuses to conduct the test, either at all or in accordance with the procedure</p>
<p>or at the time requested, the DNO and the User may discuss an alternative form of test</p>
<p>or procedure for conducting the test or timing of the test to see whether agreement can</p>
<p>be reached.</p>
<p>7.4 If the DNO agrees to the test taking place, to the procedure for conducting the test and</p>
<p>to the time of the test, either in response to the original request or following the</p>
<p>discussion referred to in paragraph 7.3, it will notify the User accordingly.</p>
<p>7.5 If the DNO does not (following the discussion referred to in paragraph 7.3) agree to the</p>
<p>test taking place, then it will not take place, provided that as indicated in paragraph 7.2</p>
<p>above, the DNO may only continue to refuse to conduct the test for so long as the</p>
<p>reasons set out in that paragraph continue to apply.</p>
<p>7.6 If the DNO does not (following such discussion) agree to the procedure for conducting</p>
<p>the test, then if the test is to go ahead, the DNO’s requirements relating to the</p>
<p>procedure will prevail, unless the reasons set out in paragraph 7.2 above no longer</p>
<p>continue.</p>
<p>7.7 If the DNO does not (following such discussion) agree to the timing of the test, then if</p>
<p>the test is to go ahead, the DNO’s requirements relating to timing will prevail.</p>
<p>7.8 The DNO may then, in accordance with the agreed (or otherwise settled) procedure and</p>
<p>timing and if agreed by the User, send representatives to the User Site in order to</p>
<p>witness the test.</p>
<p>7.9 The User must, if agreed under paragraph 7.8 above, allow the DNO witnesses access</p>
<p>to all relevant parts of its User Site in order to witness such a test.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 108</p>
<p>7.10 The DNO shall take all reasonable steps to ensure that any representatives that it sends</p>
<p>to the User Site pursuant to paragraph 7.9 above comply at all times with all relevant</p>
<p>safety requirements of the User of which they are made aware and with all reasonable</p>
<p>directions of the User and (but subject to paragraph 7.8) any reasonable restrictions on</p>
<p>access whilst at the User Site in question.</p>
<p>8 Commissioning/Acceptance Testing</p>
<p>1.1 The Connection Conditions reflect the Commissioning/Acceptance Testing which</p>
<p>will be required under each Connection Agreement for User’s Equipment prior to</p>
<p>being certified as acceptable to be and remain connected (or to be reconnected) to the</p>
<p>Distribution System and for modifications to existing User’s Equipment.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 109</p>
<p>Distribution Metering Code</p>
<p>Table of Contents</p>
<p>Page</p>
<p>1 Introduction &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.110</p>
<p>2 Objectives&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.111</p>
<p>3 Scope &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;112</p>
<p>4 Procedure &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.112</p>
<p>5 Ownership and Meter Responsible Person&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.112</p>
<p>6 Data Collection &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;113</p>
<p>7 Accuracy&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..114</p>
<p>8 Calibration&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;114</p>
<p>9 Proper Order, Testing, Sealing and Reading &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.114</p>
<p>10 Access &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..119</p>
<p>11 Disputes &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;120</p>
<p>12 Information &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..122</p>
<p>13 Ownership of Metering Data &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..122</p>
<p>14 New Connection Registration and Change of Supplier &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.123</p>
<p>15 Notices &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.123</p>
<p>SUB-CODE D1 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..126</p>
<p>SUB-CODE D2 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..136</p>
<p>SUB-CODE D3 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..146</p>
<p>SUB-CODE D4 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..156</p>
<p>Agreed Procedure No. 1 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;166</p>
<p>Agreed Procedure No. 2&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..175</p>
<p>Agreed Procedure No. 3&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..184</p>
<p>Agreed Procedure No. 4&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..195</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 110</p>
<p>1 Introduction</p>
<p>1.1 This Distribution Metering Code sets out the requirements for Metering and for</p>
<p>Generator Metering Circuits for Apparatus with a rating of 70 kVA and above</p>
<p>connected to the Distribution System. It covers in relation to such Apparatus:</p>
<p>(a) Metering for Active and Reactive Energy; and</p>
<p>(b) Generator Metering Circuits.</p>
<p>The Distribution Metering Code deals with Metering at Relevant Connection Sites,</p>
<p>as further provided in this Distribution Metering Code.</p>
<p>1.2 The Distribution Metering Code does not apply in respect of Imports below 70kVA</p>
<p>at Power Stations and in such circumstances the relevant Connection Agreement will</p>
<p>specify the Metering requirements.</p>
<p>1.3 Prior to the introduction of the Single Electricity Market (SEM) on the Island of</p>
<p>Ireland on 1 November 2007, the requirements for Metering for Users, whether they</p>
<p>were connected to the Transmission System or to the Distribution System, were</p>
<p>contained in the Grid Code Metering Code.</p>
<p>1.4 With the full licence separation of the TSO from the DNO at the introduction of the</p>
<p>SEM in November 2007, the DNO became responsible for a separate Distribution</p>
<p>Code.</p>
<p>1.5 The Grid Code Metering Code continues to specify the metering requirements for:</p>
<p>(a) Apparatus connected to the Transmission System; and</p>
<p>(b) Power Stations which are subject to Central Dispatch and are connected to the</p>
<p>Distribution System.</p>
<p>1.6 Users shall, in respect of Plant and Apparatus described in paragraph 1.5(b) above,</p>
<p>also be required to comply with the requirements of the Grid Code Metering Code.</p>
<p>Unless otherwise specifically provided in this Distribution Code, the provisions of</p>
<p>both the Grid Code and the Distribution Code have been designed so that compliance</p>
<p>with the metering requirements in the Grid Code Metering Code should ensure that</p>
<p>there will be compliance with the relevant parts of this Distribution Metering Code.</p>
<p>1.7 In addition to the requirements for Metering and Generator Metering Circuits set out</p>
<p>in this Distribution Metering Code there may be provisions in each of the Trading</p>
<p>and Settlement Code, Market Registration Code (“MRC”), Schedule 7 of the</p>
<p>Order, Connection Agreement, Grid Code and other industry documentation that</p>
<p>apply to certain Users connected to the Distribution System in respect of their</p>
<p>Apparatus.</p>
<p>1.8 The Distribution Metering Code specifies the requirements in respect of:</p>
<p>(a) technical, design and operational criteria;</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 111</p>
<p>(b) accuracy and calibration;</p>
<p>(c) approval, certification and testing; and</p>
<p>(d) meter reading and data management.</p>
<p>1.9 The Distribution Metering Code is divided into:</p>
<p>- the Main Code;</p>
<p>- the Sub-Codes; and</p>
<p>- the Agreed Procedures.</p>
<p>1.10 In general, the Main Code contains the broader principles applying to Metering and</p>
<p>the Sub-Codes, Agreed Procedures and, in certain cases, the relevant Retail Market</p>
<p>Procedures under the MRC contain the more detailed technical requirements and/or</p>
<p>procedures. The Sub-Codes, Agreed Procedures and relevant Retail Market</p>
<p>Procedures cover, amongst other things, the following matters:</p>
<p>(a) Metering Sub-Codes:</p>
<p><em>Sub Code No Subject</em></p>
<p>1 For the Metering of circuits &gt; 100 MVA</p>
<p>2 For the Metering of circuits &gt; 10 MVA and ≤ 100 MVA</p>
<p>3 For the Metering of Circuits &gt; 1 MVA and ≤ 10 MVA</p>
<p>4 For the Metering of Circuits ≥ 70 kVA and ≤ 1 MVA</p>
<p>(b) Agreed Procedures</p>
<p><em>AP No Subject</em></p>
<p>AP1</p>
<p>Maintenance, testing, inspection and sealing of Metering</p>
<p>(Generation) and Generator Metering Circuits.</p>
<p>AP2 Maintenance, testing, inspection and sealing of Metering.</p>
<p>AP3 Meter advance reconciliation (Generation).</p>
<p>AP4</p>
<p>Validation, estimation and substitution rules for half-hourly</p>
<p>data</p>
<p>2 Objectives</p>
<p>2.1 The objective of the Distribution Metering Code is to ensure that Metering</p>
<p>requirements are specified for Users’ Apparatus with a rating of 70 kVA and above</p>
<p>connected to the Distribution System.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 112</p>
<p>3 Scope</p>
<p>3.1 This Distribution Metering Code applies to the DNO and to Users, which in the</p>
<p>Distribution Metering Code means:</p>
<p>(a) Generators in respect of Apparatus with a rating of 70kVA and above</p>
<p>connected to the Distribution System; and</p>
<p>(b) Suppliers in respect of the supply they make to their Demand Customers</p>
<p>whose Apparatus is of a rating of 70 kVA and above connected to the</p>
<p>Distribution System.</p>
<p>4 Procedure</p>
<p>4.1 Active and Reactive Energy and Active and Reactive Power Exported or Imported</p>
<p>by Users shall be metered as required by this Distribution Metering Code.</p>
<p>4.2 Metering must be designed and installed so as to measure both Exports to and Imports</p>
<p>from the Distribution System and, in the case of Generating Unit(s) registered under</p>
<p>the Trading and Settlement Code, output from each Generating Unit. Where a</p>
<p>number of Generating Units have been registered as one unit under the Trading and</p>
<p>Settlement Code the combined output, rather than the individual outputs, from those</p>
<p>Generating Units may with the agreement of the DNO be measured with a single set of</p>
<p>Metering.</p>
<p>4.3 Data from Metering required under this Distribution Metering Code shall be</p>
<p>collected:</p>
<p>(a) in the case of Users not subject to Central Dispatch, by the DNO; and</p>
<p>(b) in the case of Users subject to Central Dispatch, by the TSO,</p>
<p>in each case through the relevant DNO Data Collection System.</p>
<p>4.4 Description of Metering:</p>
<p>(a) Metering subject to this Distribution Metering Code shall comply with the</p>
<p>requirements set out in the relevant Metering Sub-Code.</p>
<p>(b) All Metering for Apparatus connected to the Distribution System which is</p>
<p>required to comply with the Grid Code Metering Code shall be compatible</p>
<p>with the TSO Data Collection System.</p>
<p>(c) All Generator Metering Circuits must be compatible with the relevant</p>
<p>Metering.</p>
<p>5 Ownership and Meter Responsible Person</p>
<p>5.1 All Metering shall be owned by the DNO.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 113</p>
<p>5.2 The DNO shall ensure that all such Metering complies with this Distribution</p>
<p>Metering Code, other than:</p>
<p>(a) all Metering relating to Demand Customers which shall, for the purposes of</p>
<p>this Distribution Metering Code, be the responsibility of the relevant Supplier.</p>
<p>(b) all Generator Metering Circuits which shall, for the purposes of this</p>
<p>Distribution Metering Code, be the responsibility of the Generator which</p>
<p>operates the Generating Unit to which they relate; and</p>
<p>(c) all Metering relating to Interconnectors, responsibility for which shall be</p>
<p>governed by the provisions of the relevant Interconnection Agreement.</p>
<p>The DNO or the User responsible for Metering shall be known in this Distribution</p>
<p>Metering Code as the Meter Responsible Person in respect of such Metering.</p>
<p>5.3 Metering</p>
<p>(a) Each of the DNO and each User acting in its capacity as a Meter Responsible</p>
<p>Person or as a Generator shall, by the date such person becomes bound by this</p>
<p>Distribution Metering Code (and in respect of that Metering or those</p>
<p>Generator Metering Circuits for which it is responsible), ensure such</p>
<p>Metering or Generator Metering Circuits are properly installed and that they</p>
<p>comply with the requirements of this Distribution Metering Code.</p>
<p>(b) Details of such Metering or Generator Metering Circuits shall be provided by</p>
<p>the relevant Meter Responsible Person or Generator to the DNO on request</p>
<p>for the purposes of maintaining the register pursuant to paragraph 9.5.</p>
<p>Maintenance and replacement of Generator Metering Circuits in the ordinary</p>
<p>course shall be the responsibility of the relevant Generator.</p>
<p>5.4 Position</p>
<p>5.4.1 All current and voltage transformers associated with Metering must be installed</p>
<p>as close as reasonably practicable to the Connection Point taking into account</p>
<p>physical location and cost.</p>
<p>5.4.2 CTs and VTs which are part of Generator Metering Circuits must be installed</p>
<p>in positions which will enable the measurement of Settlement Values.</p>
<p>5.4.3 Generator Metering Circuits and Metering shall comply with the applicable</p>
<p>sections of Sub-Codes Nos. 1 to 4.</p>
<p>6 Data Collection</p>
<p>6.1 DNO</p>
<p>The DNO shall have the right to collect data relating to Active Energy and Reactive</p>
<p>Energy Imported and Exported by remote interrogation (either direct or through the</p>
<p>TSO) or manual on-site interrogation in accordance with the terms of this Distribution</p>
<p>Metering Code.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 114</p>
<p>6.2 Generators</p>
<p>For the purposes of remote interrogation the DNO may use its own data</p>
<p>communications network or failing this, shall enter into, manage and monitor contracts</p>
<p>to provide for the maintenance of all data links by which data is passed from System</p>
<p>Data Collectors to the DNO. In the event of any fault or failure on such</p>
<p>communication lines or any error or omission in such data the DNO shall, if possible,</p>
<p>retrieve such data by manual on-site interrogation in accordance with Agreed</p>
<p>Procedure No.4 or, as the case may be, Retail Market Procedure MP NI 105 failing</p>
<p>which it shall estimate the same in accordance with Agreed Procedure No.4 or Retail</p>
<p>Market Procedure MP NI 105a as appropriate.</p>
<p>6.3 Each of the DNO and all Users shall use communications protocols in relation to</p>
<p>Metering in accordance with the relevant Sub-Code.</p>
<p>7 Accuracy</p>
<p>Metering shall be accurate within the prescribed limits set out in the relevant Sub-</p>
<p>Codes. These prescribed limits shall be applied after adjustments have been made in</p>
<p>accordance with the relevant Sub-Code to compensate for any errors due to measuring</p>
<p>current and voltage transformers and connections thereto and/or due to Generator</p>
<p>Metering Circuits.</p>
<p>8 Calibration</p>
<p>Each Meter Responsible Person shall ensure that all Metering for which it is</p>
<p>responsible and each Generator shall ensure that all Generator Metering Circuits for</p>
<p>which it is responsible shall be calibrated or compensated in accordance with this</p>
<p>Distribution Metering Code in order to meet the accuracy requirements in the Sub-</p>
<p>Codes. The Meter Responsible Person in the case of Metering or the DNO in the</p>
<p>case of Generator Metering Circuits shall be granted access to such Metering or</p>
<p>Generator Metering Circuits by the relevant User upon reasonable notice and at</p>
<p>reasonable times, in order to make or inspect any adjustments to them and to attend any</p>
<p>tests or inspection of them required pursuant to this Distribution Metering Code.</p>
<p>9 Proper Order, Testing, Sealing and Reading</p>
<p>9.1 Proper Order:</p>
<p>(a) Each Meter Responsible Person shall at its own cost and expense keep in good</p>
<p>working order, repair and condition all Metering in respect of which it is the</p>
<p>Meter Responsible Person to the extent necessary to ensure the correct</p>
<p>recording and transmission of the requisite data relating to or in respect of the</p>
<p>quantity of Active and Reactive Energy measured by the relevant Metering.</p>
<p>(b) Each Generator shall at its own cost and expense keep in good working order,</p>
<p>repair and condition all Generator Metering Circuits for which it is</p>
<p>responsible.</p>
<p>9.2 Testing:</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 115</p>
<p>(a) Any new or replacement meters shall be calibrated prior to installation in</p>
<p>accordance with the provisions of the relevant Sub-Code.</p>
<p>(b) Any new, replacement or modified Metering shall be tested by the Meter</p>
<p>Responsible Person as soon as is reasonably practicable after installation or</p>
<p>modification of such Metering. Metering for consumers will be tested in</p>
<p>accordance with the Meters (Certification) Regulations (NI) 1998.</p>
<p>(c) No less frequently than every five years (or more frequently if required by the</p>
<p>relevant Sub-Code) each Meter Responsible Person shall carry out a periodic</p>
<p>calibration of all Metering in respect of which it is the Meter Responsible</p>
<p>Person.</p>
<p>(d) The Meter Responsible Person in respect of Metering at a Power Station shall</p>
<p>give the DNO or (in the case of Metering of which the DNO is the Metering</p>
<p>Responsible Person), the Generator at least one month’s prior written notice of</p>
<p>a routine test and 5 Business Days’ prior written notice in the case of every site</p>
<p>test of new, replacement or modified Metering. The notice must state the date,</p>
<p>time, work required and estimated duration of every such test except where such</p>
<p>test is carried out as a result of an emergency or equipment failure in respect of</p>
<p>Metering which is already in service.</p>
<p>(e) The DNO or the Generator, as the case may be, shall have the right to attend</p>
<p>any such test should it so require. Any such test shall comply with the relevant</p>
<p>Sub-Code.</p>
<p>(f) If the DNO or any User has reason to believe that Metering or Generator</p>
<p>Metering Circuits are not performing properly or within the prescribed limits</p>
<p>of accuracy referred to in the relevant Sub-Code then such person (where it is</p>
<p>not the DNO) shall promptly notify the DNO accordingly. An ad-hoc test may</p>
<p>then be arranged which will only be chargeable to the requesting party if no</p>
<p>fault is found.</p>
<p>(g) The costs and expenses of testing carried out under paragraph 9.2(b) and</p>
<p>calibration carried out under paragraph 9.2(c) shall be borne by the Meter</p>
<p>Responsible Person. The costs and expenses of testing carried out under</p>
<p>paragraph 9.2(f) shall to the extent that testing reveals no fault, be borne by the</p>
<p>party requesting such test and, to the extent that such test reveals faults, by the</p>
<p>Meter Responsible Person.</p>
<p>(h) If all or any part of a Generator Metering Circuit is replaced, the relevant</p>
<p>Generator Metering Circuit shall be recalibrated if calibration is possible. If</p>
<p>required, the DNO and the Generator shall agree any change that may be</p>
<p>necessary to the existing compensation for that Generator Metering Circuit.</p>
<p>(i) Calibration certificates for test equipment shall be made available by the DNO</p>
<p>for inspection by the relevant Generator and the relevant User.</p>
<p>9.3 Testing: General</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 116</p>
<p>(a) Any testing of any Metering or Generator Metering Circuits will be carried</p>
<p>out by the Meter Responsible Person in the case of Metering, or by the</p>
<p>Generator in the case of Generator Metering Circuits, on the relevant</p>
<p>Metering or Generator Metering Circuits mounted in their operational</p>
<p>position.</p>
<p>(b) Both the Generator and the Meter Responsible Person and (where the DNO is</p>
<p>not the Meter Responsible Person) the DNO shall have the right to attend all</p>
<p>such tests. All testing will be carried out in accordance with the relevant Sub-</p>
<p>Code. Any breaking of seals and sealing on Metering will be carried out in</p>
<p>accordance with Agreed Procedure No.1 or, as the case may be, Agreed</p>
<p>Procedure No. 2. The test performance of any Metering or Generator</p>
<p>Metering Circuits shall be compared with calibrated test equipment by one of</p>
<p>the following methods:</p>
<p>(i) injecting into the measuring circuits (i.e. excluding the primary current</p>
<p>and voltage transformers) and comparing the readings or records over</p>
<p>such period as may reasonably be required by the DNO or, where a</p>
<p>Generator has instigated the test, by that Generator to ensure a reliable</p>
<p>comparison; or</p>
<p>(ii) where practicable, operating the calibrated test equipment from the same</p>
<p>primary current and voltage transformers as the meter under operating</p>
<p>conditions. The readings or recordings of the meter and the calibrated</p>
<p>test equipment shall be compared over such period as may reasonably be</p>
<p>required by the DNO or, where an Generator has instigated the test, by</p>
<p>that Generator to ensure a reliable comparison; or</p>
<p>(iii) in any other circumstances, such other method as may be reasonably</p>
<p>specified by the DNO or, where a Generator has instigated the test, by</p>
<p>that Generator.</p>
<p>9.4 Test Failures</p>
<p>(a) Any meter which fails any test whilst in its operational position shall be</p>
<p>removed by the Meter Responsible Person forthwith and tested by the DNO</p>
<p>under laboratory conditions in accordance with the relevant Sub-Code in the</p>
<p>presence of the Meter Responsible Person or the Generator if either wishes to</p>
<p>attend. The DNO shall give the Meter Responsible Person or the Generator,</p>
<p>as the case may be, prior notice of such test.</p>
<p>(b) For meters removed in accordance with paragraph 9.4(a) on circuits that are</p>
<p>required to remain in service either:</p>
<p>(i) the meter shall be replaced by the Meter Responsible Person forthwith</p>
<p>with a previously recalibrated meter suitably prepared and compensated</p>
<p>for the circuit; or</p>
<p>(ii) where the Metering includes both main and check meters for the</p>
<p>affected circuit, and the meter (main or check) which is to remain on site</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 117</p>
<p>is within its calibration period, such other meter may be removed</p>
<p>provided it is returned to site or replaced within 10 Business Days.</p>
<p>(iii) In such circumstances where the remaining meter is the check meter it</p>
<p>shall, for all estimation or retrieval purposes, be regarded as the main</p>
<p>meter until replacement or return to site of the main meter.</p>
<p>9.5 Records:</p>
<p>(a) Each Meter Responsible Person shall at its own cost and expense maintain a</p>
<p>register in relation to Metering for which it is the Meter Responsible Person.</p>
<p>(b) Each Generator shall at its own cost and expense maintain a register in relation</p>
<p>to Generator Metering Circuits for which it is responsible.</p>
<p>(c) Each such register shall detail any relevant Compensation Factors,</p>
<p>specification details, e.g. serial number and accuracy class, and all relevant</p>
<p>matters as may be required by the relevant Sub-Code relating to testing and</p>
<p>calibration including the dates, location and results of any tests, readings,</p>
<p>adjustments or inspections carried out, any temporary or permanent replacement</p>
<p>of meters and the dates on which any seal was applied or broken, the reason for</p>
<p>any seal being broken and the persons carrying out and attending any such tests,</p>
<p>readings, inspections or sealings. Such records shall also include any other</p>
<p>details as may be reasonably required by the DNO.</p>
<p>(d) Any such records shall be complete and accurate and retained for a minimum</p>
<p>period of 7 years whilst the Metering or Generator Metering Circuit continues</p>
<p>to be in service at the Relevant Connection Site and for 12 months or such</p>
<p>longer period as may be required under any other relevant industry document</p>
<p>following the permanent removal of the relevant Metering or Generator</p>
<p>Metering Circuits.</p>
<p>(e) Any data which forms part of such records shall be made available to the</p>
<p>Generator in the case of Metering and the DNO in the case of Generator</p>
<p>Metering Circuits. Copies of the results of all manual readings, adjustments,</p>
<p>tests and inspections shall be provided to the Meter Responsible Person or</p>
<p>Generator in accordance, where appropriate, but without limitation, with the</p>
<p>Agreed Procedures.</p>
<p>(f) Each Meter Responsible Person shall on request pass such records or copies of</p>
<p>the same to its successor as Meter Responsible Person in relation to any</p>
<p>Metering.</p>
<p>9.6 Sealing:</p>
<p>(a) All Metering as is capable of being made secure shall be sealed by or on behalf</p>
<p>of each Meter Responsible Person and either the DNO or the Generator as is</p>
<p>appropriate and following any test or inspection thereof in accordance with</p>
<p>Agreed Procedure No.1 or, as the case may be, Agreed Procedure No. 2</p>
<p>except, where sealing is impractical in the reasonable opinion of such Meter</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 118</p>
<p>Responsible Person and either the DNO or the Generator as is appropriate</p>
<p>having regard to the physical and electrical configuration at each Relevant</p>
<p>Connection Site.</p>
<p>(b) Each Generator and the DNO shall make arrangements for all Generator</p>
<p>Metering Circuits as are capable of being made secure to be sealed by or on its</p>
<p>behalf in accordance with Agreed Procedure No. 1, except where impractical</p>
<p>in the reasonable opinion of the relevant Generator and the DNO having regard</p>
<p>to the physical and electrical configuration at each Relevant Connection Site.</p>
<p>(c) The extent and nature of the sealing arrangements shall be agreed by the DNO</p>
<p>and the Generator at the design stage of the main connection.</p>
<p>(d) No seal applied pursuant to this Distribution Metering Code shall be broken or</p>
<p>removed except in the presence of or with the prior consent of the DNO or the</p>
<p>User affixing the seal or on whose behalf the seal has been affixed unless it is</p>
<p>necessary to do so in circumstances where both main and check meters are</p>
<p>malfunctioning or there occurs a fire or other similar hazard and such removal</p>
<p>is essential and such consent cannot be obtained (provided that the person which</p>
<p>has affixed the seal and which has not given such consent shall be informed</p>
<p>forthwith thereafter). Where verbal consent is given it must be confirmed in</p>
<p>writing forthwith.</p>
<p>(e) Neither the DNO nor the relevant User shall incur any liability under this</p>
<p>Distribution Metering Code in the event it cannot perform any of its duties</p>
<p>hereunder due to any such consent required by paragraph 9.6(d) being withheld</p>
<p>save that it shall promptly inform the DNO and the relevant Meter Responsible</p>
<p>Person or Generator accordingly.</p>
<p>(f) Each User shall control the issue of its own seals and sealing pliers, and shall</p>
<p>keep an accurate register of all such pliers and the authorised persons to whom</p>
<p>they are issued.</p>
<p>(g) Each seal must be uniquely identified in a format previously agreed with the</p>
<p>DNO. A seal application and removal record must be maintained and signed off</p>
<p>by both parties.</p>
<p>9.7 Inspection and Readings:</p>
<p>(a) The DNO shall ensure that all meters forming part of Metering which is subject</p>
<p>to the terms of this Distribution Metering Code are inspected and read by onsite</p>
<p>interrogation by it or on its behalf not less than once every 5 years and shall</p>
<p>give the Meter Responsible Person or the Generator at least 5 Business Days’</p>
<p>prior notice thereof or such shorter period as the DNO and the relevant User</p>
<p>may agree.</p>
<p>(b) A failure to notify in accordance with paragraph 9.7(a) shall invalidate the</p>
<p>results of any such inspection or reading. Each reading shall be taken at, or as</p>
<p>close as is practicable to, the end of a Settlement Period (as that term is defined</p>
<p>in the Trading and Settlement Code).</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 119</p>
<p>(c) The DNO shall keep written reports of all such inspections and readings and</p>
<p>provide copies to the Meter Responsible Person or the Generator for the</p>
<p>purposes of paragraph 9.5(a). Any resulting discrepancies will be dealt with as</p>
<p>provided in the relevant Agreed Procedure.</p>
<p>(d) The Meter Responsible Person or Generator, as the case may be shall have</p>
<p>the right to attend any such inspection and reading although the failure to attend</p>
<p>shall not prevent such inspection or reading taking place nor invalidate its</p>
<p>results. The representative of the Generator or Meter Responsible Person</p>
<p>shall acknowledge the results of any such inspection or reading in the manner</p>
<p>required by the Agreed Procedure.</p>
<p>10 Access</p>
<p>10.1 Each User hereby agrees to grant to each other User and to the DNO, and the DNO</p>
<p>hereby agrees to grant to each User, its employees, agents and contractors and persons</p>
<p>duly authorised by them (each an “Invitee”) full right to enter upon and through and</p>
<p>remain upon any part of such person’s property to the extent necessary for the purposes</p>
<p>of this Distribution Metering Code subject to the other provisions of paragraph 10.</p>
<p>Each person so granting access must further ensure that any consents or other forms of</p>
<p>approval of third parties required in respect of such access have been correctly obtained</p>
<p>and remain valid at the time of such access including, if appropriate, rights of access</p>
<p>across third party land.</p>
<p>10.2 Each of the DNO and each User shall ensure, so far as it is able, that physical access to</p>
<p>Metering and Generator Metering Circuits is, where practicable, restricted to</p>
<p>personnel who are required to have such access for the proper performance of their</p>
<p>duties and have received permission for such access. A record of any such access shall</p>
<p>be maintained by the DNO or the User, as the case may be, on whose land the</p>
<p>Metering or Generator Metering Circuits are positioned, with copies provided to the</p>
<p>Meter Responsible Person and the DNO pursuant to paragraph 9.5(f). In addition all</p>
<p>Metering and Generator Metering Circuits, where practicable, must be made secure,</p>
<p>if necessary by making the lock and keys subject to similar access restrictions.</p>
<p>10.3 Subject to any other arrangements which may be agreed between the relevant User and</p>
<p>the DNO or another User, as the case may be, the right of access provided for in</p>
<p>paragraph 10.1 includes the right to bring on to such property such vehicles, plant,</p>
<p>machinery and maintenance or other materials as shall be necessary for the purposes of</p>
<p>this Distribution Metering Code.</p>
<p>10.4 Each of the DNO and each User shall ensure that any particular authorisation or</p>
<p>clearance for any Invitee which is required to be given to ensure access by such Invitee</p>
<p>is available on the arrival of such Invitee at the Relevant Connection Site.</p>
<p>10.5 Each of the DNO and each User shall ensure that all reasonable arrangements and</p>
<p>provisions are made and/or revised from time to time as and when necessary or</p>
<p>desirable to facilitate the safe exercise of any right of access granted pursuant to</p>
<p>paragraph 10.1 with the minimum of disruption, disturbance and inconvenience. Such</p>
<p>arrangements and provisions may, to the extent that the same is reasonable, limit or</p>
<p>restrict the exercise of such right of access and/or provide for any of the DNO and each</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 120</p>
<p>User to make directions or regulations from time to time in relation to a specified</p>
<p>matter.</p>
<p>10.6 Matters to be covered by such arrangements and/or provisions include:</p>
<p>(a) the identification of the relevant Metering or Generator Metering Circuits;</p>
<p>(b) the particular access routes applicable to the land in question having particular</p>
<p>regard for the weight and size limits on these routes;</p>
<p>(c) any limitations on times of exercise of the right of access;</p>
<p>(d) any requirements as to prior notification and as to authorisation or security</p>
<p>clearance of individuals exercising such right of access and procedures for</p>
<p>obtaining the same;</p>
<p>(e) the means of communication to the Invitee of any relevant directions or</p>
<p>regulations made by the person granting access; and</p>
<p>(f) the identification of and arrangements applicable to personnel exercising the</p>
<p>right of access granted by paragraph 10.1; and</p>
<p>(g) safety procedures.</p>
<p>Each Invitee shall observe and comply with any such arrangements and all provisions</p>
<p>(or directions or regulations issued pursuant thereto) made from time to time.</p>
<p>10.7 Each Invitee shall ensure that all reasonable steps are taken in the exercise of any right</p>
<p>of access by such Invitee to:</p>
<p>(a) avoid or minimise damage in relation to the property over which it has access;</p>
<p>and</p>
<p>(b) cause as little disturbance and inconvenience as possible to any of the DNO or</p>
<p>any User as the case may be, or other occupier of such property,</p>
<p>and shall make good any damage caused to any such property in the course of exercise</p>
<p>of such rights as soon as may be practicable. Subject to this, all such rights of access</p>
<p>shall be exercisable free of any charge or payment of any kind.</p>
<p>10.8 For the avoidance of doubt, no User or the DNO shall incur any liability under this</p>
<p>Distribution Metering Code in the event it cannot perform any of its duties hereunder</p>
<p>due to access to Metering or Generator Metering Circuits being denied to it save that</p>
<p>such person (where not the DNO) shall promptly inform the DNO, the relevant Meter</p>
<p>Responsible Person and the Generator accordingly.</p>
<p>11 Disputes</p>
<p>11.1 Any dispute in relation to the following matters:</p>
<p>(a) siting of Metering;</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 121</p>
<p>(b) technical specifications for Metering, Generator Metering Circuits or the</p>
<p>DNO Data Collection System;</p>
<p>(c) sealing of Metering;</p>
<p>(d) compliance of Metering or Generator Metering Circuits with technical</p>
<p>specifications of the Distribution Metering Code;</p>
<p>(e) compensation values;</p>
<p>(f) such other matters as the relevant persons in dispute under this Distribution</p>
<p>Metering Code may agree,</p>
<p>shall be referred to an Independent Engineer under paragraph 11.2.</p>
<p>11.2 The parties to a dispute under this paragraph 11 agree and shall procure that the</p>
<p>Independent Engineer shall act as an expert and not as an arbitrator and shall decide</p>
<p>those matters referred or reserved to him under this paragraph 11 by reference to Good</p>
<p>Industry Practice using his skill, experience and knowledge and with regard to such</p>
<p>other matters as the Independent Engineer in his sole discretion considers appropriate.</p>
<p>All references to the Independent Engineer shall be made in writing by either party</p>
<p>with notice to the other being given contemporaneously as soon as reasonably</p>
<p>practicable and in any event, within 14 days of the occurrence of the dispute to be</p>
<p>referred to the Independent Engineer. The parties shall promptly supply the</p>
<p>Independent Engineer with such documents and information as he may request when</p>
<p>considering such question. The Independent Engineer shall use his best endeavours to</p>
<p>give his decision upon the question before him as soon as possible following its referral</p>
<p>to him and in any event within 21 days of such referral. The fees and expenses of the</p>
<p>Independent Engineer shall be shared equally the parties to the dispute. The parties to</p>
<p>the dispute expressly acknowledge that submission of disputes under this paragraph 11</p>
<p>for resolution by the Independent Engineer does not preclude subsequent submission</p>
<p>of disputes for resolution by arbitration as provided for in the Distribution Code.</p>
<p>Pending any such submission the parties shall treat the Independent Engineer’s</p>
<p>decision as final and binding. The Independent Engineer will be a Member of the</p>
<p>Association for Consultancy and Engineering (ACE) and shall be agreed between the</p>
<p>parties within 7 days of a dispute being referred or such other period as may be agreed</p>
<p>between the parties to the dispute. Failing agreement it shall be referred to the</p>
<p>President of the Institution of Electrical Engineers who shall nominate the Independent</p>
<p>Engineer.</p>
<p>11.3 Any other dispute under this Distribution Metering Code shall be dealt with in</p>
<p>accordance with the disputes procedure in the relevant Connection Agreement.</p>
<p>11.4 Any testing of Metering or Generator Metering Circuits required to settle a dispute</p>
<p>will be carried out in accordance with paragraphs 9.3 and 9.4.</p>
<p>11.5 Notwithstanding paragraphs 11.1 to 11.4, any dispute under this Distribution</p>
<p>Metering Code in relation to a matter that is also subject to the dispute resolution</p>
<p>procedures contained within the Trading and Settlement Code and the MRC will be</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 122</p>
<p>dealt with in accordance with the relevant dispute resolution procedure contained within</p>
<p>the MRC.</p>
<p>11.6 If at any time any Metering equipment is destroyed or damaged or otherwise ceases to</p>
<p>function, or is found to be outside the prescribed limits of accuracy referred to in the</p>
<p>Sub-Codes, the DNO will promptly adjust, renew or repair the same. If at any time</p>
<p>any Metering circuit not under the ownership of the DNO is destroyed or damaged or</p>
<p>otherwise ceases to function, or is found to be outside the prescribed limits of accuracy</p>
<p>referred to in the Sub-Codes, the Generator will promptly adjust, renew or repair the</p>
<p>same. In the event that a Generator cannot or does not comply with its obligations to</p>
<p>repair, adjust or replace or renew any defective component, the DNO shall have the</p>
<p>right to carry this out and to recover its own costs and expenses from the Generator.</p>
<p>12 Information</p>
<p>12.1 Where a relevant User has an agreement with the DNO to receive electronic data from</p>
<p>Metering, such User shall install such computer equipment as may be necessary for</p>
<p>such purpose and which shall be compatible with such Metering and shall comply with</p>
<p>any relevant requirement of the Agreed Procedures. Each such User shall be</p>
<p>responsible for its own computer equipment and communication lines.</p>
<p>12.2 Each Generator shall have the right to receive electronic data from Metering in</p>
<p>respect of which it is the Generator. The DNO shall not, without good cause, interrupt</p>
<p>or otherwise disturb such electronic data. The Generator shall be responsible for the</p>
<p>maintenance of any communication lines from the Generator Data Collector to the</p>
<p>relevant Generator.</p>
<p>12.3 Demand Customers shall not have the right to receive electronic data files for</p>
<p>Metering from the DNO in respect of which it is the Demand Customer.</p>
<p>12.4 All Users shall give to the DNO all such information in their possession regarding</p>
<p>Metering as the DNO shall reasonably require for the proper functioning of the Data</p>
<p>Collection System including information regarding the dates and time periods for</p>
<p>installation of new Metering, wiring diagrams, and the dates and periods when</p>
<p>Metering is out of service.</p>
<p>13 Ownership of Metering Data</p>
<p>13.1 The Meter Responsible Person of any Metering shall own the data acquired</p>
<p>therefrom. Any of the DNO and each User to whom such data relates shall at all times</p>
<p>have the right to and is hereby authorised to have access to such data and to use such</p>
<p>data in each case as may be permitted pursuant to this Distribution Metering Code.</p>
<p>13.2 The Meter Responsible Person may make a charge for the provision of such data of an</p>
<p>amount reflecting its reasonable costs of providing such data and, if confidential, may</p>
<p>only release such data to others to the extent required pursuant to this Distribution</p>
<p>Code or as permitted by the Connection Agreement.</p>
<p>13.3 Any person subject to this Distribution Metering Code shall, at all times, comply with</p>
<p>its respective obligations under all applicable Data Protection Legislation in relation to</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 123</p>
<p>all Personal Data that is Processed by it in the course of performing its obligations</p>
<p>under this Distribution Metering Code, including maintaining any required</p>
<p>notification under the Data Protection Legislation. To the extent that any Personal</p>
<p>Data is data that is Processed for a purpose set out in the data protection provisions</p>
<p>contained within the MRC, any person Processing such data will be subject to those</p>
<p>provisions.</p>
<p>14 New Connection Registration and Change of Supplier</p>
<p>14.1 The procedures for registration of a new connection in Northern Ireland and for a</p>
<p>change of Supplier are set out in Retail Market Procedures MP NI 101 and MP NI</p>
<p>102 respectively. Additional guidance relating to these procedures is set out in the</p>
<p>market guide(s) associated with Retail Market Procedures MP NI 101 and MP NI</p>
<p>102.</p>
<p>15 Notices</p>
<p>15.1 Any notice of a new Meter Responsible Person or of a change in Meter Responsible</p>
<p>Person or any other communication required under this Distribution Metering Code</p>
<p>to be given to the DNO shall if required be sent by facsimile to number: 02890 954</p>
<p>329, at NIE Market Services, Fortwilliam House, attention: Metering Systems Manager</p>
<p>(with hard copy to follow by first class post) or such other facsimile number and</p>
<p>address as may from time to time be nominated in writing by the DNO and, if required</p>
<p>to be given to any other User, shall be sent by facsimile to such number at such address</p>
<p>and to such person as such User shall nominate in writing to the DNO (with hard copy</p>
<p>to follow by first class post). In the absence of nomination such communication as is</p>
<p>required shall be sent to the registered office of such other User.</p>
<p>15.2 Any notice or other communication sent by facsimile pursuant to paragraph 15.1 shall</p>
<p>be deemed to have been received when despatched.</p>
<p>15.3 A new Meter Responsible Person must be notified to the DNO at least 20 Business</p>
<p>Days prior to either:</p>
<p>(a) the date of the intended commencement of obligations of the Meter Responsible</p>
<p>Person; or</p>
<p>(b) the date of simultaneous termination of obligations by the existing Meter</p>
<p>Responsible Person and the assumption of those obligations by the new Meter</p>
<p>Responsible Person,</p>
<p>(as the case may be) in connection with the relevant Metering.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 124</p>
<p>SUB-CODES</p>
<p>Summary of Technical Requirements for Distribution Connected Metering Systems</p>
<p>The Metering System technical requirements for Distribution connections are similar to those</p>
<p>at Transmission level. The fundamental Metering attribute which must be specified for</p>
<p>different circuit loads or generator outputs is that of meter accuracy.</p>
<p>A summary of these accuracy requirements is given in the table below and the Sub-Codes that</p>
<p>follow provide more detailed information;</p>
<p>a) Technical Standards Matrix</p>
<p>&gt;100MVA</p>
<p>CTs 0.2S</p>
<p>VTs 0.2</p>
<p>Meters 0.2S</p>
<p>Main/Check Meters Y</p>
<p>Main/Check CTs &amp; VTs Y</p>
<p>3 Phase 4 Wire Required Y</p>
<p>10-100MVA</p>
<p>CTs 0.2</p>
<p>VTs 0.5</p>
<p>Meters 0.5S</p>
<p>Main/Check Meters Y</p>
<p>Main/Check CTs &amp; VTs Y</p>
<p>*3 Phase 4 Wire Required N</p>
<p>1-10MVA</p>
<p>CTs 0.5S</p>
<p>VTs 1.0</p>
<p>Meters 0.5</p>
<p>Main/Check Meters Y</p>
<p>Main/Check CTs &amp; VTs N</p>
<p>*3 Phase 4 Wire Required N</p>
<p>&lt;1MVA</p>
<p>CTs 0.5S</p>
<p>VTs 1</p>
<p>Meters 2</p>
<p>Main/Check Meters N</p>
<p>Main/Check CTs &amp; VTs N</p>
<p>*3 Phase 4 Wire Required N</p>
<p>b) Technical Design Considerations</p>
<p>Specific design details may on occasions require consideration by the DNO and the User on a</p>
<p>case by case basis depending on the nature of the installed electrical connection and its</p>
<p>associated plant.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 125</p>
<p>If any of the above accuracy levels cannot be individually achieved e.g. due to size constraints</p>
<p>within switchgear, it may be possible with the permission of the DNO to increase the accuracy</p>
<p>of other elements such that the overall Metering System accuracy remains within the</p>
<p>prescribed limits.</p>
<p>The burden of Metering CTs and VTs must be determined on a per site basis to ensure that it</p>
<p>is adequate for the purpose. CTs must operate at between 25% and 95% of their rated burden</p>
<p>and VTs must not exceed 95% of their rating.</p>
<p>* Three phase four wire Metering installations are required for generation or loads of greater</p>
<p>than 100MVA. However if it is anticipated that phase energy will be imbalanced, this system</p>
<p>of Metering should be used at other levels. MV metered connections are usually used for</p>
<p>lower than 1 MW capacity, are considered unbalanced and therefore must be measured using</p>
<p>three phase four wire methods of Metering.</p>
<p>The star point of Metering VTs must be earthed irrespective of the Metering System</p>
<p>deployed.</p>
<p>All Metering CTs must be individually wired out to Metering equipment panels i.e. the use of</p>
<p>common return conductors is prohibited.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 126</p>
<p>SUB-CODE D1</p>
<p>Demand Customer Connected Load or Generation &gt; 100MVA</p>
<p>Contents</p>
<p>1 Scope</p>
<p>2 Standards</p>
<p>3 Facilities to be provided at Metering points</p>
<p>3.1 General</p>
<p>3.2 Meters</p>
<p>3.3 Instrument Transformers</p>
<p>3.4 Data Collectors</p>
<p>3.5 Data Collection System</p>
<p>3.6 Facilities</p>
<p>4 Measurement criteria</p>
<p>4.1 Accuracy</p>
<p>4.2 Compensation for Errors</p>
<p>5 Calibration and testing of Metering</p>
<p>5.1 Meters</p>
<p>5.2 Current and Voltage Transformers</p>
<p>5.3 Test Access to Metering Equipment</p>
<p>5.4 Data Collectors</p>
<p>5.5 Records</p>
<p>Appendix</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 127</p>
<p>1 Scope</p>
<p>1.1 This Sub-Code D1 specifies the Metering facilities which must be provided and certain</p>
<p>practices that must be employed for the measurement of electrical energy flows</p>
<p>associated with:</p>
<p>(a) Suppliers in relation to their Demand Customers; and</p>
<p>(b) Generating Units.</p>
<p>1.2 This Sub-Code supplements the Main Code of the Distribution Metering Code to</p>
<p>which reference should be made. In the event of an inconsistency between the</p>
<p>provisions of this Sub-Code and the Main Code, the provisions of the Main Code</p>
<p>shall prevail.</p>
<p>1.3 This Sub-Code should also be read in conjunction with any relevant Agreed</p>
<p>Procedures and Schedule 7 of the Order.</p>
<p>1.4 This Sub-Code applies to circuits with a rated capacity which exceeds 100 MVA.</p>
<p>2 Standards</p>
<p>All references to industry standards given in the text of this Sub-Code are to versions</p>
<p>which are current as at 1 November 2007. However, Metering is required to comply</p>
<p>with the version of any such standard, equivalent or replacement which is in force at</p>
<p>the date of installation.</p>
<p>3 Facilities to be Provided at Metering Points</p>
<p>3.1 General</p>
<p>Although for clarity the specification identifies separate items of equipment, nothing in</p>
<p>this Sub-Code prevents the items being combined to perform the same task provided</p>
<p>the requirements of this Sub-Code are met.</p>
<p>3.2 Meters</p>
<p>3.2.1 For each circuit the following energy measurements are required at or in</p>
<p>relation to the Connection Point:</p>
<p>(a) Active Energy for Import (kWh);</p>
<p>(b) Active Energy for Export (kWh) (applicable to Generators only);</p>
<p>(c) Reactive Energy for Import and Export (kVArh).</p>
<p>3.2.2 The Meter Responsible Person shall ensure that Metering for the above</p>
<p>measurements shall normally be provided on the User’s side of the Connection</p>
<p>Point in order to measure required Settlement Values.</p>
<p>3.2.3 Active Energy Meters (kWh)</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 128</p>
<p>Active Energy meters shall comply with the relevant part of BS EN 62053 (or</p>
<p>the standard current at the date of design of such equipment) for class 0.2S</p>
<p>meters.</p>
<p>3.2.4 Reactive Energy Meters (kVArh)</p>
<p>Reactive Energy meters shall comply with the relevant requirements of IEC</p>
<p>Standard 1268 for class 2 meters.</p>
<p>3.2.5 The measurements will be produced using the outputs from current transformers</p>
<p>and voltage transformers.</p>
<p>3.2.6 Each circuit will be provided with:</p>
<p>(a) main kWh meter;</p>
<p>(b) check kWh meter;</p>
<p>(c) two main kVArh meters or one bi-directional kVArh meter for lagging</p>
<p>and leading power factors; and</p>
<p>(d) two check kVArh meters or one bi-directional kVArh meter for lagging</p>
<p>and leading power factors.</p>
<p>Paragraph 3.2.9 deals with the situation where Import and/or Export of Active</p>
<p>Energy is required at the same point where a single meter can be used.</p>
<p>3.2.7 If direct measurement of the required values cannot be achieved, then the</p>
<p>required values may be calculated using values measured at other points subject</p>
<p>to prior agreement with the DNO and providing the Overall Accuracy meets</p>
<p>the requirements of paragraph 4.1. Where compensation is applied the values</p>
<p>shall be recorded and supporting evidence shall be available to justify the</p>
<p>compensation criteria.</p>
<p>3.2.8 Where the Import and/or Export of Active Energy and Reactive Energy is</p>
<p>required to be measured at the same point, these functions may be combined in</p>
<p>a single meter in which each energy flow is measured separately.</p>
<p>3.2.9 Meters shall be labelled in accordance with the Appendix of this Sub-Code.</p>
<p>3.3 Instrument Transformers</p>
<p>3.3.1 The terms &#8220;current transformer&#8221; (CT) and &#8220;voltage transformer&#8221; (VT) used in</p>
<p>this Sub-Code do not preclude the use of other measuring techniques providing</p>
<p>the accuracy, and also the longer term accuracy in accordance with this Sub-</p>
<p>Code can be verified to the DNO’s satisfaction.</p>
<p>3.3.2 In accordance with the principles in paragraph 3.2.2, all CTs and VTs will be</p>
<p>fitted on the User’s side of the Connection Point except where otherwise</p>
<p>agreed with the DNO.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 129</p>
<p>3.3.3 Where CTs and/or VTs are used, they shall meet the requirements set out in</p>
<p>paragraphs 3.3.5 and 3.3.6 below.</p>
<p>3.3.4 Where CTs and/or VTs are used then a test terminal block or equivalent facility</p>
<p>shall be provided close to the meter(s). This facility will be fitted with the DNO</p>
<p>seals.</p>
<p>3.3.5 Current Transformers</p>
<p>(a) Two sets of CTs to IEC 60044-1 (or the standard current at the date of</p>
<p>design of such equipment) with a minimum standard of accuracy class</p>
<p>0.2S shall be provided per circuit and shall also meet (to the extent</p>
<p>applicable) any meter certification regulations in force at the time.</p>
<p>(b) Each CT secondary winding supplying a main meter shall be dedicated</p>
<p>to Metering purposes only. Each CT secondary winding only supplying</p>
<p>a check meter may be used for other purposes so long as such other uses</p>
<p>do not degrade the accuracy of the check meter outside the limits</p>
<p>required by paragraph 4.1.1 and sub-paragraph (f) below, and the DNO</p>
<p>is notified of such other uses in accordance with sub-paragraph (g)</p>
<p>below.</p>
<p>(c) Where a CT circuit has an additional burden not associated with meters,</p>
<p>this additional burden shall not be modified in any way without obtaining</p>
<p>the approval of the DNO in accordance with sub-paragraph (g) below.</p>
<p>(d) Common return leads for two or more CT secondary circuits are not</p>
<p>permitted.</p>
<p>(e) Main and check meters must be connected to different CTs.</p>
<p>(f) The total burden on CTs shall not exceed their rating at the rated</p>
<p>secondary current.</p>
<p>(g) Where any of the foregoing provisions of this paragraph 3.3.5 permit a</p>
<p>modification to CT secondary circuits, provided that the approval of the</p>
<p>DNO is sought for the modification, any such request must be made in</p>
<p>writing to the DNO a reasonable time in advance of the modification and</p>
<p>evidence of the value of any additional electrical burden must be made</p>
<p>available for inspection to verify compliance with this paragraph 3.3.5</p>
<p>and also to ensure there is no degradation of the accuracy required by</p>
<p>paragraph 4.1.1.</p>
<p>3.3.6 Voltage Transformers</p>
<p>(a) Two VTs, or one VT with two or more secondary winding sets, to IEC</p>
<p>60044-2 (or the standard current at the date of design of such equipment)</p>
<p>with a minimum standard of accuracy class 0.2 shall be provided for the</p>
<p>Metering of each circuit and shall also (to the extent applicable) meet</p>
<p>any meter certification regulations in force at the time.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 130</p>
<p>(b) Capacitor VTs shall have a working burden which provides for</p>
<p>monitoring of the integrity of each fuse and which does not exceed the</p>
<p>maximum rating or fall below the minimum rating stipulated by the</p>
<p>relevant manufacturer.</p>
<p>(c) Each VT secondary winding supplying a main meter shall be dedicated</p>
<p>to Metering purposes only. Each VT secondary winding only supplying</p>
<p>a check meter may be used for other purposes so long as other uses do</p>
<p>not degrade the accuracy of the check meter outside the limits required</p>
<p>by paragraph 4.1.1 and sub-paragraph (g) below and the DNO is notified</p>
<p>of such other uses in accordance with subparagraph (h) below.</p>
<p>(d) Where a VT circuit has an additional burden not associated with meters,</p>
<p>this additional burden shall not be modified in any way unless the</p>
<p>approval of the DNO is obtained in accordance with subparagraph (h)</p>
<p>below.</p>
<p>(e) Each meter circuit shall be fed by a separate, fused supply from the VT.</p>
<p>(f) Main and check meters must be connected to different VTs. If the VT</p>
<p>supplies other equipment, separate fusing must be provided for the</p>
<p>Metering.</p>
<p>(g) The total burden on VTs shall not exceed their rating at the rated</p>
<p>secondary voltages.</p>
<p>(h) Where any of the foregoing provisions of this paragraph 3.3.6 permit a</p>
<p>modification to VT secondary circuits, provided that the approval of the</p>
<p>DNO is sought for the modification, any such request must be made in</p>
<p>writing to the DNO a reasonable time in advance of the modification and</p>
<p>evidence of the value of any additional electrical burden must be made</p>
<p>available for inspection to verify compliance with this paragraph 3.3.6</p>
<p>and also to ensure there is no degradation of accuracy as required by</p>
<p>paragraph 4.1.1.</p>
<p>3.3.7 Existing Installations</p>
<p>For installations connected to the Distribution System prior to 1 January 2010</p>
<p>the installed instrument transformers may be used irrespective of their accuracy</p>
<p>class providing the Overall Accuracy requirements as defined in paragraph 4.1</p>
<p>are met and also the following:</p>
<p>(i) in the event of a significant alteration to the primary plant (e.g. a</p>
<p>switchgear change), new instrument transformers which comply with</p>
<p>paragraphs 3.3.5 and 3.3.6 shall be provided;</p>
<p>(ii) separately fused VT supplies shall be provided for each of the</p>
<p>following:-</p>
<p>(a) the main meters;</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 131</p>
<p>(b) the check meters; and</p>
<p>(c) any additional electrical burden.</p>
<p>3.4 Data Collectors</p>
<p>3.4.1 Data collectors may be either an integral part of individual circuit meters or</p>
<p>stand alone units which collect pulses from one or more individual meters.</p>
<p>Duplicate data collectors may also be an integral part of check meters or stand</p>
<p>alone units. These will be provided by the Meter Responsible Person and used</p>
<p>to collect, store and transmit energy values for each Settlement Period to a</p>
<p>DNO Data Collection System.</p>
<p>3.4.2 The following is required:</p>
<p>(a) the data collectors must have sufficient data channels to store all halfhour</p>
<p>value types necessary for settlement (e.g. kWh and kVArhA</p>
<p>Import and Export per connection) and be capable of storing these</p>
<p>values during failure of the AC power supply;</p>
<p>(b) on demand from the DNO Data Collection System the data collector</p>
<p>will transfer the recorded Settlement Values without loss or error. The</p>
<p>Settlement Values must also be transferable manually using a portable</p>
<p>collection device (personal computer/hand held unit/removable memory</p>
<p>module etc) of a type compatible with the system used by the DNO; and</p>
<p>(c) in the event of failure of communications with the central collection</p>
<p>station the data collector will be capable of storing a minimum of five</p>
<p>channels of data per connection for a minimum period of 20 days with an</p>
<p>integrating period of 30 minutes. This 20 day period may reduce pro rata</p>
<p>dependent on the notified demand period selected as described in</p>
<p>paragraph 3.4.3 below. Access to the manual transfer facility will be</p>
<p>secured from unauthorised interference.</p>
<p>3.4.3 The settlement period shall be selectable over the following range: 30, 15, and 1</p>
<p>minutes and will be notified by the DNO. For any selectable value in this range</p>
<p>one Settlement Period shall commence on the hour and half-hour.</p>
<p>3.4.4 Monitoring facilities shall be provided for data collector fault conditions and to</p>
<p>record any instances of local interrogation which changes data.</p>
<p>3.5 Data Collection System</p>
<p>3.5.1 Communications</p>
<p>The means of communication between the data collector and the central DNO</p>
<p>Data Collection System must be secure at the remote end. Communication can</p>
<p>be via PSTN, PTN, GPRS, GSM networks or by any other technically suitable</p>
<p>means which has previously been agreed with the DNO.</p>
<p>3.5.2 Central Collection Station</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 132</p>
<p>The DNO Data Collection System will interrogate each remote meter or data</p>
<p>collector. All the DNO operations carried out either manually or automatically</p>
<p>shall be protected by password protection. The DNO Data Collection System</p>
<p>will synchronise the outstations during interrogation to a standard reference</p>
<p>time. Following receipt of all data channels from the outstation the meter data</p>
<p>will be transferred to the DNO’s billing and settlement systems.</p>
<p>3.5.3 Supply Voltage</p>
<p>Assured Supplies must be used where ever possible. However, where a</p>
<p>measurement VT source is used and the outstation is storing data for more than</p>
<p>one circuit, a voltage selector relay scheme using each circuit involved shall be</p>
<p>provided. Local and remote phase failure indications shall be provided.</p>
<p>3.6 Facilities</p>
<p>The Metering equipment shall be capable of providing voltage free (clean contacts)</p>
<p>relay outputs which accurately represent the recorded channel values for:</p>
<p>(a) kWh (Import and Export) and kVArh (lagging and leading).</p>
<p>(b) A 30 minute reset pulse.</p>
<p>4 Measurement Criteria</p>
<p>4.1 Accuracy</p>
<p>4.1.1 Overall Accuracy of Equipment</p>
<p>Meters shall be calibrated so as to achieve Overall Accuracy of Metering</p>
<p>within the limits set out below. Calibration of meters shall be adjusted due to</p>
<p>current and voltage transformer errors and/or errors due to lead electrical</p>
<p>burdens but not for primary transformer losses. Paragraph 4.2.2 deals further</p>
<p>with this issue.</p>
<p>(a) Active Energy Measurement</p>
<p><em>Conditions of Test Limits of Error at Power Factor</em></p>
<p>Current expressed as a percentage of rated</p>
<p>measuring current</p>
<p>Power Factor Limits of Error</p>
<p>120% to 10% inclusive</p>
<p>Below 10% to 5% inclusive</p>
<p>Below 5% to 1% inclusive*</p>
<p>120% to 10% inclusive</p>
<p>1.0</p>
<p>1.0</p>
<p>1.0</p>
<p>0.5 lag and 0.8 lead</p>
<p>±0.5%</p>
<p>±0.7%</p>
<p>±1.5%</p>
<p>±1.0%</p>
<p>* This requirement shall only apply where the energy transfers to be measured by the Import</p>
<p>meter and/or the Export meter during normal operating conditions are such that the Rated</p>
<p>Measuring Current will be below 5% (excluding zero) for periods equivalent to 10% or greater</p>
<p>per annum.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 133</p>
<p>(b) Reactive Energy Measurement</p>
<p><em>Conditions of Test Limits of Error at Power Factor</em></p>
<p>Current expressed as a percentage of rated</p>
<p>measuring current</p>
<p>Power Factor Limits of Error</p>
<p>120% &#8211; 10% inclusive</p>
<p>120% &#8211; 20% inclusive</p>
<p>0</p>
<p>0.866 lag and lead</p>
<p>±4.0%</p>
<p>±5.0%</p>
<p>4.1.2 Accuracy of Time Keeping</p>
<p>(a) The time keeping accuracy of Metering equipment shall be maintained</p>
<p>in accordance with Standard Time.</p>
<p>(b) The commencement of each Settlement Period shall be within 10</p>
<p>seconds of Standard Time.</p>
<p>(c) The duration of each Settlement Period shall be within ± 0.1% of the</p>
<p>required duration, except where synchronisation has occurred in a</p>
<p>Settlement Period.</p>
<p>4.2 Compensation for Errors</p>
<p>4.2.1 Compensation for Instrument Transformer Errors</p>
<p>Compensation shall be made for errors of current and voltage transformers</p>
<p>and/or lead electrical burdens, if possible, in the meter calibration.</p>
<p>4.2.2 Compensation for Power Transformer and Line Losses</p>
<p>Where the installed Metering location and the Connection Point do not</p>
<p>coincide then, where necessary, compensation for power transformer and/or line</p>
<p>losses shall be provided to meet the Overall Accuracy at the boundary point</p>
<p>defined in paragraph 3.2.2. Compensation shall be made in the relevant data</p>
<p>collector and the formula for calculation shall be agreed between the DNO and</p>
<p>the relevant User.</p>
<p>4.2.3 Where existing calibration records do not exist, a recalibration test shall be</p>
<p>carried out where practicable. Values of compensation shall be recorded and</p>
<p>evidence to justify the compensation criteria shall be made available for</p>
<p>inspection, including all test certificates.</p>
<p>5 Calibration and Testing of Metering</p>
<p>5.1 Meters</p>
<p>Metering Systems shall be calibrated and tested in accordance with the relevant part of</p>
<p>BS EN 62053 and the manufacturer’s recommendations.</p>
<p>5.2 Current and Voltage Transformers</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 134</p>
<p>Measuring transformers shall be supplied with known characteristics within the</p>
<p>requirements of paragraph 3.3 of this Sub-Code.</p>
<p>5.3 Test Access to Metering Equipment</p>
<p>Metering equipment shall be provided with sealable test terminal blocks both at the</p>
<p>meter and if practicable at the switchgear to facilitate meter testing and current /</p>
<p>voltage transformer checks in situ. Test terminal block design shall be agreed in</p>
<p>advance with the DNO.</p>
<p>5.4 Data Collectors</p>
<p>5.4.1 Maintenance</p>
<p>Data collectors must be maintained in accordance with the manufacturer’s</p>
<p>recommendations or as otherwise necessary to meet the obligations of this Sub-</p>
<p>Code.</p>
<p>5.4.2 Testing</p>
<p>There is no requirement for routine tests of data collectors other than as a part</p>
<p>of an overall Metering System test.</p>
<p>5.5 Records</p>
<p>The results of all tests and periodic checks shall be held as a permanent record by the</p>
<p>DNO and a copy held by the Generator.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 135</p>
<p>APPENDIX</p>
<p>LABELLING OF METERS FOR IMPORT AND EXPORT</p>
<p>1 ACTIVE ENERGY</p>
<p>Active Energy is considered to be Imported when it flows to the User System from</p>
<p>the Distribution System. The meter(s) registering this Active Energy should be</p>
<p>labelled &#8220;Import&#8221;.</p>
<p>Active Energy is considered to be Exported when it flows from the User System to</p>
<p>the Distribution System. The meter(s) registering this Active Energy should be</p>
<p>labelled &#8220;Export&#8221;.</p>
<p>Meters shall be labelled to distinguish between main and check meters.</p>
<p>2 REACTIVE ENERGY</p>
<p>Reactive Energy is considered to be Imported or Exported as follows:</p>
<p><em>Flow of Active Energy Power Factor Flow of Reactive Energy</em></p>
<p>Import Lagging Import*</p>
<p>Import Leading Export*</p>
<p>Import Unity Zero</p>
<p>Export Lagging Export</p>
<p>Export Leading Import</p>
<p>Export Unity Zero</p>
<p>For the purposes of labelling of meters the conditions asterisked above will determine labelling</p>
<p>where Import for Active Energy is defined as in 1 above.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 136</p>
<p>SUB-CODE D2</p>
<p>Demand Customer Connected Load or Generation greater than 10MVA to 100MVA</p>
<p>Contents</p>
<p>1 Scope</p>
<p>2 Standards</p>
<p>3 Facilities to be provided at Metering points</p>
<p>3.1 General</p>
<p>3.2 Meters</p>
<p>3.3 Instrument Transformers</p>
<p>3.4 Data Collectors</p>
<p>3.5 Data Collection System</p>
<p>3.6 Facilities</p>
<p>4 Measurement criteria</p>
<p>4.1 Accuracy</p>
<p>4.2 Compensation for Errors</p>
<p>5 Calibration and testing of Metering</p>
<p>5.1 Meters</p>
<p>5.2 Current and Voltage Transformers</p>
<p>5.3 Test Access to Metering Equipment</p>
<p>5.4 Data Collectors</p>
<p>5.5 Records</p>
<p>Appendix</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 137</p>
<p>1 Scope</p>
<p>1.1 This Sub-Code D2 specifies the Metering facilities which must be provided and certain</p>
<p>practices that must be employed for the measurement of electrical energy flows</p>
<p>associated with:</p>
<p>(a) Suppliers in relation to their Demand Customers; and</p>
<p>(b) Generating Units.</p>
<p>1.2 This Sub-Code supplements the Main Code of the Distribution Metering Code to</p>
<p>which reference should be made. In the event of an inconsistency between the</p>
<p>provisions of this Sub-Code and the Main Code, the provisions of the Main Code</p>
<p>shall prevail.</p>
<p>1.3 This Sub-Code should also be read in conjunction with any relevant Agreed</p>
<p>Procedures and Schedule 7 of the Order.</p>
<p>1.4 This Sub-Code applies to circuits with a rated capacity which exceeds 10 MVA and up</p>
<p>to and including 100 MVA.</p>
<p>1.5 For the purposes of this Sub-Code, the criteria for a Demand Customer supply</p>
<p>(Import Active Energy) to be over 10 MVA is that monthly maximum demand in each</p>
<p>of the three months of the highest maximum demand on the Distribution System in</p>
<p>each period of 12 consecutive months exceeds 10 MVA. For a new supply, a maximum</p>
<p>demand is formally agreed between the Demand Customer and the DNO and this is</p>
<p>periodically reviewed thereafter.</p>
<p>2 Standards</p>
<p>All references to industry standards given in the text of this Sub-Code are to versions</p>
<p>which are current as at 1 November 2007. However, Metering is required to comply</p>
<p>with the version of any such standard, equivalent or replacement which is in force at 1</p>
<p>November 2007.</p>
<p>3 Facilities to be Provided at Metering Points</p>
<p>3.1 General</p>
<p>Although for clarity the specification identifies separate items of equipment, nothing in</p>
<p>this Sub-Code prevents the items being combined to perform the same task provided</p>
<p>the requirements of this Sub-Code are met.</p>
<p>3.2 Meters</p>
<p>3.2.1 For each circuit the following energy measurements are required at or in</p>
<p>relation to the Connection Point:</p>
<p>(a) Active Energy for Import (kWh);</p>
<p>(b) Active Energy for Export (kWh) (applicable to Generators only);</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 138</p>
<p>(c) Reactive Energy for Import and Export (kVArh).</p>
<p>3.2.2 The Meter Responsible Person shall ensure that Metering for the above</p>
<p>measurements shall normally be provided on the User’s side of the Connection</p>
<p>Point in order to measure required Settlement Values.</p>
<p>3.2.3 Active Energy Meters (kWh)</p>
<p>Active Energy meters shall comply with the relevant part of BSEN 62053 (or</p>
<p>the standard current at the date of design of such equipment) for class 0.5S</p>
<p>meters.</p>
<p>3.2.4 Reactive Energy Meters (kVArh)</p>
<p>Reactive Energy meters shall comply with the relevant requirements of IEC</p>
<p>Standard 1268 or BS EN 62053 (or the standard current at the date of design of</p>
<p>such equipment) Part 4 for class 2 meters.</p>
<p>3.2.5 The measurements will be produced using the outputs from current transformers</p>
<p>and voltage transformers.</p>
<p>3.2.6 Each circuit will be provided with:</p>
<p>(a) main kWh meter;</p>
<p>(b) check kWh meter;</p>
<p>(c) two main kVArh meters or one bi-directional kVArh meter for lagging</p>
<p>and leading power factors; and</p>
<p>(d) two check kVArh meters or one bi-directional kVArh meter for lagging</p>
<p>and leading power factors.</p>
<p>Paragraph 3.2.9 deals with the situation where Import and/or Export of Active</p>
<p>Energy is required at the same point where a single meter can be used.</p>
<p>3.2.7 If direct measurement of the required values cannot be achieved, then the</p>
<p>required values may be calculated using values measured at other points subject</p>
<p>to prior agreement with the DNO and providing the Overall Accuracy meets</p>
<p>the requirements of paragraph 4.1. Where compensation is applied the values</p>
<p>shall be recorded and supporting evidence shall be available to justify the</p>
<p>compensation criteria.</p>
<p>3.2.8 Where the Import and/or Export of Active Energy and Reactive Energy is</p>
<p>required to be measured at the same point, these functions may be combined in</p>
<p>a single meter in which each energy flow is measured separately.</p>
<p>3.2.9 Meters shall be labelled in accordance with the Appendix of this Sub-Code.</p>
<p>3.3 Instrument Transformers</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 139</p>
<p>3.3.1 The terms &#8220;current transformer&#8221; (CT) and &#8220;voltage transformer&#8221; (VT) used in</p>
<p>this Sub-Code do not preclude the use of other measuring techniques providing</p>
<p>the accuracy, and also the longer term accuracy, in accordance with this Sub-</p>
<p>Code can be verified to the DNO’s satisfaction.</p>
<p>3.3.2 In accordance with the principles in paragraph 3.2.2, all CTs and VTs will be</p>
<p>fitted on the User’s side of the Connection Point except where otherwise</p>
<p>agreed with the DNO.</p>
<p>3.3.3 Where CTs and/or VTs are used, they shall meet the requirements set out in</p>
<p>paragraphs 3.3.5 and 3.3.6 below.</p>
<p>3.3.4 Where CTs and/or VTs are used then a test terminal block or equivalent facility</p>
<p>shall be provided close to the meter(s). This facility will be fitted with the DNO</p>
<p>seals.</p>
<p>3.3.5 Current Transformers</p>
<p>(a) Two sets of CTs to IEC 60044-1 (or the standard current at the date of</p>
<p>design of such equipment) with a minimum standard of accuracy class</p>
<p>0.2 shall be provided per circuit and shall also meet (to the extent</p>
<p>applicable) any meter certification regulations in force at the time.</p>
<p>(b) Each CT secondary winding supplying a main meter shall be dedicated</p>
<p>to Metering purposes only. Each CT secondary winding only supplying</p>
<p>a check meter may be used for other purposes so long as such other uses</p>
<p>do not degrade the accuracy of the check meter outside the limits</p>
<p>required by paragraph 4.1.1 and sub-paragraph (f) below, and the DNO</p>
<p>is notified of such other uses in accordance with sub-paragraph (g)</p>
<p>below.</p>
<p>(c) Where a CT circuit has an additional burden not associated with meters,</p>
<p>this additional burden shall not be modified in any way without obtaining</p>
<p>the approval of the DNO in accordance with sub-paragraph (g) below.</p>
<p>(d) Common return leads for two or more CT secondary circuits are not</p>
<p>permitted.</p>
<p>(e) Main and check meters must be connected to different CTs.</p>
<p>(f) The total burden on CTs shall not exceed their rating at the rated</p>
<p>secondary current.</p>
<p>(g) Where any of the foregoing provisions of this paragraph 3.3.5 permit a</p>
<p>modification to CT secondary circuits, provided that the approval of the</p>
<p>DNO is sought for the modification, any such request must be made in</p>
<p>writing to the DNO a reasonable time in advance of the modification and</p>
<p>evidence of the value of any additional electrical burden must be made</p>
<p>available for inspection to verify compliance with this paragraph 3.3.5</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 140</p>
<p>and also to ensure there is no degradation of the accuracy required by</p>
<p>paragraph 4.1.1.</p>
<p>3.3.6 Voltage Transformers</p>
<p>(a) Two VTs, or one VT with two or more secondary winding sets, to IEC</p>
<p>60044-2 (or the standard current at the date of design of such equipment)</p>
<p>with a minimum standard of accuracy class 0.5 shall be provided for the</p>
<p>Metering of each circuit and shall also (to the extent applicable) meet</p>
<p>any meter certification regulations in force at the time.</p>
<p>(b) Capacitor VTs shall have a working burden which provides for</p>
<p>monitoring of the integrity of each fuse and which does not exceed the</p>
<p>maximum rating or fall below the minimum rating stipulated by the</p>
<p>relevant manufacturer.</p>
<p>(c) Each VT secondary winding supplying a main meter shall be dedicated</p>
<p>to Metering purposes only. Each VT secondary winding only supplying</p>
<p>a check meter may be used for other purposes so long as other uses do</p>
<p>not degrade the accuracy of the check meter outside the limits required</p>
<p>by paragraph 4.1.1 and sub-paragraph (g) below and the DNO is notified</p>
<p>of such other uses in accordance with subparagraph (h) below.</p>
<p>(d) Where a VT circuit has an additional burden not associated with meters,</p>
<p>this additional burden shall not be modified in any way unless the</p>
<p>approval of the DNO is obtained in accordance with subparagraph (h)</p>
<p>below.</p>
<p>(e) Each meter circuit shall be fed by a separate, fused supply from the VT.</p>
<p>(f) Main and check meters must be connected to different VTs. If the VT</p>
<p>supplies other equipment, separate fusing must be provided for the</p>
<p>Metering.</p>
<p>(g) The total burden on VTs shall not exceed their rating at the rated</p>
<p>secondary voltages.</p>
<p>(h) Where any of the foregoing provisions of this paragraph 3.3.6 permit a</p>
<p>modification to VT secondary circuits, provided that the approval of the</p>
<p>DNO is sought for the modification, any such request must be made in</p>
<p>writing to the DNO a reasonable time in advance of the modification and</p>
<p>evidence of the value of any additional electrical burden must be made</p>
<p>available for inspection to verify compliance with this paragraph 3.3.6</p>
<p>and also to ensure there is no degradation of accuracy as required by</p>
<p>paragraph 4.1.1.</p>
<p>3.3.7 Existing Installations</p>
<p>For installations connected to the Distribution System prior to 1 January 2010,</p>
<p>the installed instrument transformers may be used irrespective of their accuracy</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 141</p>
<p>class providing the Overall Accuracy requirements as defined in paragraph 4.1</p>
<p>are met and also the following:</p>
<p>(i) in the event of a significant alteration to the primary plant (e.g. a</p>
<p>switchgear change), new instrument transformers which comply with</p>
<p>paragraphs 3.3.5 and 3.3.6 shall be provided;</p>
<p>(ii) separately fused VT supplies shall be provided for each of the following:</p>
<p>(a) the main meters;</p>
<p>(b) the check meters; and</p>
<p>(c) any additional electrical burden.</p>
<p>3.4 Data Collectors</p>
<p>3.4.1 Data collectors may be either an integral part of individual circuit meters or</p>
<p>stand alone units which collect pulses from one or more individual meters.</p>
<p>Duplicate data collectors may also be an integral part of check meters or stand</p>
<p>alone units. These will be provided by the Meter Responsible Person and used</p>
<p>to collect, store and transmit energy values for each Settlement Period to a</p>
<p>DNO Data Collection System.</p>
<p>3.4.2 The following is required:</p>
<p>(a) the data collectors must have sufficient data channels to store all halfhour</p>
<p>value types necessary for settlement (e.g. kWh and kVArh Import</p>
<p>and Export per connection) and be capable of storing these values during</p>
<p>failure of the AC power supply;</p>
<p>(b) on demand from the DNO Data Collection System the data collector</p>
<p>will transfer the recorded Settlement Values without loss or error. The</p>
<p>Settlement Values must also be transferable manually using a portable</p>
<p>collection device (personal computer/hand held unit/removable memory</p>
<p>module etc) of a type compatible with the system used by the DNO; and</p>
<p>(c) in the event of failure of communications with the central collection</p>
<p>station the data collector will be capable of storing a minimum of five</p>
<p>channels of data per connection for a minimum period of 20 days with an</p>
<p>integrating period of 30 minutes. This 20 day period may reduce pro rata</p>
<p>dependent on the notified demand period selected as described in</p>
<p>paragraph 3.4.3 below. Access to the manual transfer facility will be</p>
<p>secured from unauthorised interference.</p>
<p>3.4.3 The settlement period shall be selectable over the following range: 30, 15, and 1</p>
<p>minutes and will be notified by the DNO. For any selectable value in this range</p>
<p>one Settlement Period shall commence on the hour and half-hour.</p>
<p>3.4.4 Monitoring facilities shall be provided for data collector fault conditions and to</p>
<p>record any instances of local interrogation which changes data.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 142</p>
<p>3.5 Data Collection System</p>
<p>3.5.1 Communications</p>
<p>The means of communication between the data collector and the central DNO</p>
<p>Data Collection System must be secure at the remote end. Communication can</p>
<p>be via PSTN, PTN, GPRS, GSM networks or by any other technically suitable</p>
<p>means which has previously been agreed with the DNO.</p>
<p>3.5.2 Central Collection Station</p>
<p>The DNO Data Collection System will interrogate each remote meter or data</p>
<p>collector. All the DNO operations carried out either manually or automatically</p>
<p>shall be protected by password protection. The DNO Data Collection System</p>
<p>will synchronise the outstations during interrogation to a standard reference</p>
<p>time. Following receipt of all data channels from the outstation the meter data</p>
<p>will be transferred to the DNO’s billing and settlement systems.</p>
<p>3.5.3 Supply Voltage</p>
<p>Assured Supplies must be used where ever possible. However, where a</p>
<p>measurement VT source is used and the outstation is storing data for more than</p>
<p>one circuit, a voltage selector relay scheme using each circuit involved shall be</p>
<p>provided. Local and remote phase failure indications shall be provided.</p>
<p>3.6 Facilities</p>
<p>The Metering equipment shall be capable of providing voltage free (clean contacts)</p>
<p>relay outputs which accurately represent the recorded channel values for:</p>
<p>(a) kWh (Import and Export) and kVArh (lagging and leading).</p>
<p>(b) A 30 minute reset pulse.</p>
<p>4 Measurement Criteria</p>
<p>4.1 Accuracy</p>
<p>4.1.1 Overall Accuracy of Equipment</p>
<p>Meters shall be calibrated so as to achieve Overall Accuracy of Metering within the</p>
<p>limits set out below. Calibration of meters shall be adjusted due to current and voltage</p>
<p>transformer errors and/or errors due to lead electrical burdens but not for primary</p>
<p>transformer losses. Paragraph 4.2.2 deals further with this issue.</p>
<p>(a) Active Energy Measurement</p>
<p><em>Conditions of Test Limits of Error at Power Factor</em></p>
<p>Current expressed as a percentage of rated</p>
<p>measuring current</p>
<p>Power Factor Limits of Error</p>
<p>120% to 10% inclusive 1.0 ±1.0%</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 143</p>
<p>Below 10% to 5% inclusive</p>
<p>120% to 10% inclusive</p>
<p>1.0</p>
<p>0.5 lag and 0.8 lead</p>
<p>±1.5%</p>
<p>±2.0%</p>
<p>(b) Reactive Energy Measurement</p>
<p>Conditions of Test Limits of Error at Power Factor</p>
<p>Current expressed as a percentage of rated</p>
<p>measuring current</p>
<p>Power Factor Limits of Error</p>
<p>120% &#8211; 10% inclusive</p>
<p>120% &#8211; 20% inclusive</p>
<p>0</p>
<p>0.866 lag and lead</p>
<p>±4.0%</p>
<p>±5.0%</p>
<p>4.1.2 Accuracy of Time Keeping</p>
<p>(a) The time keeping accuracy of Metering equipment shall be maintained</p>
<p>in accordance with Standard Time.</p>
<p>(b) The commencement of each Settlement Period shall be within 10</p>
<p>seconds of Standard Time.</p>
<p>(c) The duration of each Settlement Period shall be within ± 0.1% of the</p>
<p>required duration, except where synchronisation has occurred in a</p>
<p>Settlement Period.</p>
<p>4.2 Compensation for Errors</p>
<p>4.2.1 Compensation for Instrument Transformer Errors</p>
<p>Compensation shall be made for errors of current and voltage transformers</p>
<p>and/or lead electrical burdens, if possible, in the meter calibration.</p>
<p>4.2.2 Compensation for Power Transformer and Line Losses</p>
<p>Where the installed Metering location and the Connection Point do not</p>
<p>coincide then, where necessary, compensation for power transformer and/or line</p>
<p>losses shall be provided to meet the Overall Accuracy at the boundary point</p>
<p>defined in paragraph 3.2.2. Compensation shall be made in the relevant data</p>
<p>collector and the formula for calculation shall be agreed between the DNO and</p>
<p>the relevant User.</p>
<p>4.2.3 Where existing calibration records do not exist, a recalibration test shall be</p>
<p>carried out where practicable. Values of compensation shall be recorded and</p>
<p>evidence to justify the compensation criteria shall be made available for</p>
<p>inspection, including all test certificates.</p>
<p>5 Calibration and Testing of Metering</p>
<p>5.1 Meters</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 144</p>
<p>Metering Systems shall be calibrated and tested in accordance with the relevant part of</p>
<p>BS EN 62053 and the manufacturer’s recommendations.</p>
<p>5.2 Current and Voltage Transformers</p>
<p>Measuring transformers shall be supplied with known characteristics within the</p>
<p>requirements of paragraph 3.3 of this Sub-Code.</p>
<p>5.3 Test Access to Metering Equipment</p>
<p>Metering equipment shall be provided with sealable test terminal blocks both at the</p>
<p>meter and if practicable at the switchgear to facilitate meter testing and current /</p>
<p>voltage transformer checks in situ. Test terminal block design shall be agreed in</p>
<p>advance with the DNO.</p>
<p>5.4 Data Collectors</p>
<p>5.4.1 Maintenance</p>
<p>Data collectors must be maintained in accordance with the manufacturer’s</p>
<p>recommendations or as otherwise necessary to meet the obligations of this Sub-</p>
<p>Code.</p>
<p>5.4.2 Testing</p>
<p>There is no requirement for routine tests of data collectors other than as a part</p>
<p>of an overall Metering System test.</p>
<p>5.5 Records</p>
<p>The results of all tests and periodic checks shall be held as a permanent record by the</p>
<p>DNO and a copy held by the Generator.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 145</p>
<p>APPENDIX</p>
<p>LABELLING OF METERS FOR IMPORT AND EXPORT</p>
<p>1 ACTIVE ENERGY</p>
<p>Active Energy is considered to be Imported when it flows to the User System from</p>
<p>the Distribution System. The meter(s) registering this Active Energy should be</p>
<p>labelled &#8220;Import&#8221;.</p>
<p>Active Energy is considered to be Exported when it flows from the User System to</p>
<p>the Distribution System. The meter(s) registering this Active Energy should be</p>
<p>labelled &#8220;Export&#8221;.</p>
<p>Meters shall be labelled to distinguish between main and check meters.</p>
<p>2 REACTIVE ENERGY</p>
<p>Reactive Energy is considered to be Imported or Exported as follows:</p>
<p><em>Flow of Active Energy Power Factor Flow of Reactive Energy</em></p>
<p>Import Lagging Import*</p>
<p>Import Leading Export*</p>
<p>Import Unity Zero</p>
<p>Export Lagging Export</p>
<p>Export Leading Import</p>
<p>Export Unity Zero</p>
<p>For the purposes of labelling of meters the conditions asterisked above will determine labelling</p>
<p>where Import for Active Energy is defined as in 1 above.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 146</p>
<p>SUB-CODE D3</p>
<p>Demand Customer Connected Load or Generation 1MVA to 10MVA</p>
<p>Contents</p>
<p>1 Scope</p>
<p>2 Standards</p>
<p>3 Facilities to be provided at Metering points</p>
<p>3.1 General</p>
<p>3.2 Meters</p>
<p>3.3 Instrument Transformers</p>
<p>3.4 Data Collectors</p>
<p>3.5 Data Collection System</p>
<p>3.6 Facilities</p>
<p>4 Measurement criteria</p>
<p>4.1 Accuracy</p>
<p>4.2 Compensation for Errors</p>
<p>5 Calibration and testing of Metering</p>
<p>5.1 Meters</p>
<p>5.2 Current and Voltage Transformers</p>
<p>5.3 Test Access to Metering Equipment</p>
<p>5.4 Data Collectors</p>
<p>5.5 Records</p>
<p>Appendix</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 147</p>
<p>1 Scope</p>
<p>1.1 This Sub-Code D3 specifies the Metering facilities which must be provided and certain</p>
<p>practices that must be employed for the measurement of electrical energy flows</p>
<p>associated with:</p>
<p>(a) Suppliers in relation to their Demand Customers; and</p>
<p>(b) Generating Units.</p>
<p>1.2 This Sub-Code supplements the Main Code of the Distribution Metering Code to</p>
<p>which reference should be made. In the event of an inconsistency between the</p>
<p>provisions of this Sub-Code and the Main Code, the provisions of the Main Code</p>
<p>shall prevail.</p>
<p>1.3 This Sub-Code should also be read in conjunction with any relevant Agreed</p>
<p>Procedures and Schedule 7 of the Order.</p>
<p>1.4 This Sub-Code applies to circuits with a rated capacity which exceeds 1 MVA and up</p>
<p>to and including 10 MVA.</p>
<p>1.5 For the purposes of this Sub-Code, the criteria for a Demand Customer supply</p>
<p>(Import Active Energy) to be over 1 MVA is that monthly maximum demand in each</p>
<p>of the three months of the highest maximum demand on the Distribution System in</p>
<p>each period of 12 consecutive months exceeds 1 MVA. For a new supply, a maximum</p>
<p>demand is formally agreed between the Demand Customer and the DNO and this is</p>
<p>periodically reviewed thereafter.</p>
<p>2 Standards</p>
<p>All references to industry standards given in the text of this Sub-Code are to versions</p>
<p>which are current as at 1 November 2007. However, Metering is required to comply</p>
<p>with the version of any such standard, equivalent or replacement which is in force at</p>
<p>the date of installation.</p>
<p>3 Facilities to be Provided at Metering Points</p>
<p>3.1 General</p>
<p>Although for clarity the specification identifies separate items of equipment, nothing in</p>
<p>this Sub-Code prevents the items being combined to perform the same task provided</p>
<p>the requirements of this Sub-Code are met.</p>
<p>3.2 Meters</p>
<p>3.2.1 For each circuit the following energy measurements are required at or in</p>
<p>relation to the Connection Point:-</p>
<p>(a) Active Energy for Import (kWh);</p>
<p>(b) Active Energy for Export (kWh) (applicable to Generators only);</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 148</p>
<p>(c) Reactive Energy for Import and Export (kVArh).</p>
<p>3.2.2 The Meter Responsible Person shall ensure that Metering for the above</p>
<p>measurements shall normally be provided on the User’s side of the Connection</p>
<p>Point in order to measure required Settlement Values.</p>
<p>3.2.3 Active Energy Meters (kWh)</p>
<p>Active Energy meters shall comply with the relevant part of BSEN 60653 (or</p>
<p>the standard current at the date of design of such equipment) for class 0.5</p>
<p>meters.</p>
<p>3.2.4 Reactive Energy Meters (kVArh)</p>
<p>Reactive Energy meters shall comply with the relevant requirements of IEC</p>
<p>Standard 1268 or BS EN 62053 (or the standard current at the date of design of</p>
<p>such equipment) Part 4 for class 2 meters.</p>
<p>3.2.5 The measurements will be produced using the outputs from current transformers</p>
<p>and voltage transformers.</p>
<p>3.2.6 Each circuit will be provided with:-</p>
<p>(a) main kWh meter;</p>
<p>(b) check kWh meter;</p>
<p>(c) two main kVArh meters or one bi-directional kVArh meter for lagging</p>
<p>and leading power factors; and</p>
<p>(d) two check kVArh meters or one bi-directional kVArh meter for lagging</p>
<p>and leading power factors.</p>
<p>Paragraph 3.2.9 deals with the situation where Import and/or Export of Active</p>
<p>Energy is required at the same point where a single meter can be used.</p>
<p>3.2.7 If direct measurement of the required values cannot be achieved, then the</p>
<p>required values may be calculated using values measured at other points subject</p>
<p>to prior agreement with the DNO and providing the Overall Accuracy meets</p>
<p>the requirements of paragraph 4.1. Where compensation is applied the values</p>
<p>shall be recorded and supporting evidence shall be available to justify the</p>
<p>compensation criteria.</p>
<p>3.2.8 Where the Import and/or Export of Active Energy and Reactive Energy is</p>
<p>required to be measured at the same point, these functions may be combined in</p>
<p>a single meter in which each energy flow is measured separately.</p>
<p>3.2.9 Meters shall be labelled in accordance with the Appendix of this Sub-Code.</p>
<p>3.3 Instrument Transformers</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 149</p>
<p>3.3.1 The terms &#8220;current transformer&#8221; (CT) and &#8220;voltage transformer&#8221; (VT) used in</p>
<p>this Sub-Code do not preclude the use of other measuring techniques providing</p>
<p>the accuracy, and also the longer term accuracy, in accordance with this Sub-</p>
<p>Code can be verified to the DNO’s satisfaction.</p>
<p>3.3.2 In accordance with the principles in paragraph 3.2.2, all CTs and VTs will be</p>
<p>fitted on the User’s side of the Connection Point except where otherwise</p>
<p>agreed with the DNO.</p>
<p>3.3.3 Where CTs and/or VTs are used, they shall meet the requirements set out in</p>
<p>paragraphs 3.3.5 and 3.3.6 below.</p>
<p>3.3.4 Where CTs and/or VTs are used then a test terminal block or equivalent facility</p>
<p>shall be provided close to the meter(s). This facility will be fitted with the DNO</p>
<p>seals.</p>
<p>3.3.5 Current Transformers</p>
<p>(a) One set of CTs to IEC 60044-1 (or the standard current at the date of</p>
<p>design of such equipment) with a minimum standard of accuracy class</p>
<p>0.5S5S shall be provided per circuit and shall also meet (to the extent</p>
<p>applicable) any meter certification regulations in force at the time.</p>
<p>(b) Each CT secondary winding circuit supplying the meters shall be</p>
<p>dedicated to Metering purposes only. CT secondary winding may supply</p>
<p>both main and check meters as long as this does not put the overall</p>
<p>Metering system accuracy value outside the limits defined in paragraph</p>
<p>4.1.1 and sub-paragraph (e) below.</p>
<p>(c) Where a CT circuit has an additional burden not associated with meters,</p>
<p>e.g. to improve system accuracy, this additional burden shall not be</p>
<p>modified in any way without obtaining the approval of the DNO in</p>
<p>accordance with sub-paragraph (f) below.</p>
<p>(d) Common return leads for two or more CT secondary circuits are not</p>
<p>permitted.</p>
<p>(e) The total burden on CTs shall not exceed their rating at the rated</p>
<p>secondary current.</p>
<p>(f) Where any of the foregoing provisions of this paragraph 3.3.5 permit a</p>
<p>modification to CT secondary circuits, provided that the approval of the</p>
<p>DNO is sought for the modification, any such request must be made in</p>
<p>writing to the DNO a reasonable time in advance of the modification and</p>
<p>evidence of the value of any additional electrical burden must be made</p>
<p>available for inspection to verify compliance with this paragraph 3.3.5</p>
<p>and also to ensure there is no degradation of the accuracy required by</p>
<p>paragraph 4.1.1.</p>
<p>3.3.6 Voltage Transformers</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 150</p>
<p>(a) One VT to IEC 60044-2 (or the standard current at the date of design of</p>
<p>such equipment) with a minimum standard of accuracy class 1.00 shall</p>
<p>be provided for the Metering of each circuit and shall also (to the extent</p>
<p>applicable) meet any meter certification regulations in force at the time.</p>
<p>(b) Capacitor VTs shall have a working burden which provides for</p>
<p>monitoring of the integrity of each fuse and which does not exceed the</p>
<p>maximum rating or fall below the minimum rating stipulated by the</p>
<p>relevant manufacturer.</p>
<p>(c) Each VT secondary winding supplying the meters shall be dedicated to</p>
<p>Metering purposes only. VT secondary winding may supply both main</p>
<p>and check meters as long as this does not put the overall Metering</p>
<p>System accuracy value outside the limits defined in paragraph 4.1.1 and</p>
<p>subparagraph (f) below.</p>
<p>(d) Where a VT circuit has an additional burden not associated with meters</p>
<p>e.g. to improve system accuracy, this additional burden shall not be</p>
<p>modified in any way unless the approval of the DNO is obtained in</p>
<p>accordance with sub paragraph (g) below.</p>
<p>(e) Each meter circuit shall be fed by a separate, fused supply from the VT.</p>
<p>(f) The total burden on VTs shall not exceed their rating at the rated</p>
<p>secondary voltages.</p>
<p>(g) Where any of the foregoing provisions of this paragraph 3.3.6 permit a</p>
<p>modification to VT secondary circuits, provided that the approval of the</p>
<p>DNO is sought for the modification, any such request must be made in</p>
<p>writing to the DNO a reasonable time in advance of the modification and</p>
<p>evidence of the value of any additional electrical burden must be made</p>
<p>available for inspection to verify compliance with this paragraph 3.3.6</p>
<p>and also to ensure there is no degradation of accuracy as required by</p>
<p>paragraph 4.1.1.</p>
<p>3.3.7 Existing Installations</p>
<p>For installations connected to the Distribution System prior to 1 January 2010,</p>
<p>the installed instrument transformers may be used irrespective of their accuracy</p>
<p>class providing the Overall Accuracy requirements as defined in paragraph 4.1</p>
<p>are met and also the following:</p>
<p>(i) in the event of a significant alteration to the primary plant (e.g. a</p>
<p>switchgear change), new instrument transformers which comply with</p>
<p>paragraphs 3.3.5 and 3.3.6 shall be provided; and</p>
<p>(ii) separately fused VT supplies shall be provided for the main and the</p>
<p>check meters.</p>
<p>3.4 Data Collectors</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 151</p>
<p>3.4.1 Data collectors may be either an integral part of individual circuit meters or</p>
<p>stand alone units which collect pulses from one or more individual meters.</p>
<p>Duplicate data collectors may also be an integral part of check meters or stand</p>
<p>alone units. These will be provided by the Meter Responsible Person and used</p>
<p>to collect, store and transmit energy values for each Settlement Period to a</p>
<p>DNO Data Collection System.</p>
<p>3.4.2 The following is required:</p>
<p>(a) the data collectors must have sufficient data channels to store all halfhour</p>
<p>value types necessary for settlement (e.g. kWh and kVArh Import</p>
<p>and Export per connection) and be capable of storing these values during</p>
<p>failure of the AC power supply;</p>
<p>(b) on demand from the DNO Data Collection System the data collector</p>
<p>will transfer the recorded Settlement Values without loss or error. The</p>
<p>Settlement Values must also be transferable manually using a portable</p>
<p>collection device (personal computer/hand held unit/removable memory</p>
<p>module etc) of a type compatible with the system used by the DNO; and</p>
<p>(c) in the event of failure of communications with the central collection</p>
<p>station the data collector will be capable of storing a minimum of five</p>
<p>channels of data per connection for a minimum period of 20 days with an</p>
<p>integrating period of 30 minutes. This 20 day period may reduce pro rata</p>
<p>dependent on the notified demand period selected as described in</p>
<p>paragraph 3.4.3 below. Access to the manual transfer facility will be</p>
<p>secured from unauthorised interference.</p>
<p>3.4.3 The settlement period shall be selectable over the following range: 30, 15, and 1</p>
<p>minutes and will be notified by the DNO. For any selectable value in this range</p>
<p>one Settlement Period shall commence on the hour and half-hour.</p>
<p>3.4.4 Monitoring facilities shall be provided for data collector fault conditions and to</p>
<p>record any instances of local interrogation which changes data.</p>
<p>3.5 Data Collection System</p>
<p>3.5.1 Communications</p>
<p>The means of communication between the data collector and the central DNO</p>
<p>Data Collection System must be secure at the remote end. Communication can</p>
<p>be via PSTN, PTN, GPRS, GSM networks or by any other technically suitable</p>
<p>means which has previously been agreed with the DNO.</p>
<p>3.5.2 Central Collection Station</p>
<p>The DNO Data Collection System will interrogate each remote meter or data</p>
<p>collector. All the DNO operations carried out either manually or automatically</p>
<p>shall be protected by password protection. The DNO Data Collection System</p>
<p>will synchronise the outstations during interrogation to a standard reference</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 152</p>
<p>time. Following receipt of all data channels from the outstation the meter data</p>
<p>will be transferred to the DNO’s billing and settlement systems.</p>
<p>3.5.3 Supply Voltage</p>
<p>Assured Supplies must be used where ever possible. However, where a</p>
<p>measurement VT source is used and the outstation is storing data for more than</p>
<p>one circuit, a voltage selector relay scheme using each circuit involved shall be</p>
<p>provided. Local and remote phase failure indications shall be provided.</p>
<p>3.6 Facilities</p>
<p>The Metering equipment shall be capable of providing voltage free (clean contacts)</p>
<p>relay outputs which accurately represent the recorded channel values for:</p>
<p>(a) kWh (Import and Export) and kVArh (lagging and leading).</p>
<p>(b) A 30 minute reset pulse.</p>
<p>4 Measurement Criteria</p>
<p>4.1 Accuracy</p>
<p>4.1.1 Overall Accuracy of Equipment</p>
<p>Meters shall be calibrated so as to achieve Overall Accuracy of Metering</p>
<p>within the limits set out below. Calibration of meters shall be adjusted due to</p>
<p>current and voltage transformer errors and/or errors due to lead electrical</p>
<p>burdens but not for primary transformer losses. Paragraph 4.2.2 deals further</p>
<p>with this issue.</p>
<p>(a) Active Energy Measurement</p>
<p><em>Conditions of Test Limits of Error at Power Factor</em></p>
<p>Current expressed as a percentage of rated</p>
<p>measuring current</p>
<p>Power Factor Limits of Error</p>
<p>100% to 20% inclusive</p>
<p>Below 20% to 5% inclusive</p>
<p>100% to 20% inclusive</p>
<p>1.0</p>
<p>1.0</p>
<p>0.5 lag and 0.8 lead</p>
<p>±1.5%</p>
<p>±2.5%</p>
<p>±2.5%</p>
<p>(b) Reactive Energy Measurement</p>
<p><em>Conditions of Test Limits of Error at Power Factor</em></p>
<p>Current expressed as a percentage of rated</p>
<p>measuring current</p>
<p>Power Factor Limits of Error</p>
<p>100% &#8211; 20% inclusive</p>
<p>100% &#8211; 20% inclusive</p>
<p>0</p>
<p>0.866 lag and lead</p>
<p>±4.0%</p>
<p>±5.0%</p>
<p>4.1.2 Accuracy of Time Keeping</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 153</p>
<p>(a) The time keeping accuracy of Metering equipment shall be maintained</p>
<p>in accordance with Standard Time.</p>
<p>(b) The commencement of each Settlement Period shall be within 10</p>
<p>seconds of Standard Time.</p>
<p>(c) The duration of each Settlement Period shall be within ± 0.1% of the</p>
<p>required duration, except where synchronisation has occurred in a</p>
<p>Settlement Period.</p>
<p>4.2 Compensation for Errors</p>
<p>4.2.1 Compensation for Instrument Transformer Errors</p>
<p>Compensation shall be made for errors of current and voltage transformers</p>
<p>and/or lead electrical burdens, if possible, in the meter calibration.</p>
<p>4.2.2 Compensation for Power Transformer and Line Losses</p>
<p>Where the installed Metering location and the Connection Point do not</p>
<p>coincide then, where necessary, compensation for power transformer and/or line</p>
<p>losses shall be provided to meet the Overall Accuracy at the boundary point</p>
<p>defined in paragraph 3.2.2. Compensation shall be made in the relevant data</p>
<p>collector and the formula for calculation shall be agreed between the DNO and</p>
<p>the relevant User.</p>
<p>4.2.3 Where existing calibration records do not exist, a recalibration test shall be</p>
<p>carried out where practicable. Values of compensation shall be recorded and</p>
<p>evidence to justify the compensation criteria shall be made available for</p>
<p>inspection, including all test certificates.</p>
<p>5 Calibration and Testing of Metering</p>
<p>5.1 Meters</p>
<p>Metering Systems shall be calibrated and tested in accordance with the relevant part of</p>
<p>BS EN 62053 and the manufacturer’s recommendations.</p>
<p>5.2 Current and Voltage Transformers</p>
<p>Measuring transformers shall be supplied with known characteristics within the</p>
<p>requirements of paragraph 3.3 of this Sub-Code.</p>
<p>5.3 Test Access to Metering Equipment</p>
<p>Metering equipment shall be provided with sealable test terminal blocks both at the</p>
<p>meter and if practicable at the switchgear to facilitate meter testing and current /</p>
<p>voltage transformer checks in situ. Test terminal block design shall be agreed in</p>
<p>advance with the DNO.</p>
<p>5.4 Data Collectors</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 154</p>
<p>5.4.1 Maintenance</p>
<p>Data collectors must be maintained in accordance with the manufacturer’s</p>
<p>recommendations or as otherwise necessary to meet the obligations of this Sub-</p>
<p>Code.</p>
<p>5.4.2 Testing</p>
<p>There is no requirement for routine tests of data collectors other than as a part</p>
<p>of an overall Metering System test.</p>
<p>5.5 Records</p>
<p>The results of all tests and periodic checks shall be held as a permanent record by the</p>
<p>DNO and a copy held by the Generator.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 155</p>
<p>APPENDIX</p>
<p>LABELLING OF METERS FOR IMPORT AND EXPORT</p>
<p>1 ACTIVE ENERGY</p>
<p>Active Energy is considered to be Imported when it flows to the User System from</p>
<p>the Distribution System. The meter(s) registering this Active Energy should be</p>
<p>labelled &#8220;Import&#8221;.</p>
<p>Active Energy is considered to be Exported when it flows from the User System to</p>
<p>the Distribution System. The meter(s) registering this Active Energy should be</p>
<p>labelled &#8220;Export&#8221;.</p>
<p>Meters shall be labelled to distinguish between main and check meters.</p>
<p>2 REACTIVE ENERGY</p>
<p>Reactive Energy is considered to be Imported or Exported as follows:</p>
<p><em>Flow of active Energy Power Factor Flow of Reactive Energy</em></p>
<p>Import Lagging Import*</p>
<p>Import Leading Export*</p>
<p>Import Unity Zero</p>
<p>Export Lagging Export</p>
<p>Export Leading Import</p>
<p>Export Unity Zero</p>
<p>For the purposes of labelling of meters the conditions asterisked above will determine</p>
<p>labelling where Import for Active Energy is defined as in 1 above.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 156</p>
<p>SUB-CODE D4</p>
<p>Demand Customer Connected Load or Generation 70 kVA to 1MVA</p>
<p>Contents</p>
<p>1 Scope</p>
<p>2 Standards</p>
<p>3 Facilities to be provided at Metering points</p>
<p>3.1 General</p>
<p>3.2 Meters</p>
<p>3.3 Instrument Transformers</p>
<p>3.4 Data Collectors</p>
<p>3.5 Data Collection System</p>
<p>3.6 Facilities</p>
<p>4 Measurement criteria</p>
<p>4.1 Accuracy</p>
<p>4.2 Compensation for Errors</p>
<p>5 Calibration and testing of Metering</p>
<p>5.1 Meters</p>
<p>5.2 Current and Voltage Transformers</p>
<p>5.3 Test Access to Metering Equipment</p>
<p>5.4 Data Collectors</p>
<p>5.5 Records</p>
<p>Appendix</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 157</p>
<p>1 Scope</p>
<p>1.1 This Sub-Code D4 specifies the Metering facilities which must be provided and certain</p>
<p>practices that must be employed for the measurement of electrical energy flows</p>
<p>associated with:</p>
<p>(a) Suppliers in relation to their Demand Customers; and</p>
<p>(b) Generating Units.</p>
<p>1.2 This Sub-Code supplements the Main Code of the Distribution Metering Code to</p>
<p>which reference should be made. In the event of an inconsistency between the</p>
<p>provisions of this Sub-Code and the Main Code, the provisions of the Main Code</p>
<p>shall prevail.</p>
<p>1.3 This Sub-Code should also be read in conjunction with any relevant Agreed</p>
<p>Procedures and Schedule 7 of the Order.</p>
<p>1.4 This Sub-Code applies to circuits with a rated capacity which exceeds 70 kVA and up</p>
<p>to and including 1 MVA.</p>
<p>1.5 For the purposes of this Sub-Code, the criteria for a Demand Customer supply</p>
<p>(Import Active Energy) to be over 70 kVA is that monthly maximum demand in each</p>
<p>of the three months of the highest maximum demand on the Distribution System in</p>
<p>each period of 12 consecutive months exceeds 70 kVA. For a new supply, a maximum</p>
<p>demand is formally agreed between the Demand Customer and the DNO and this is</p>
<p>periodically reviewed thereafter.</p>
<p>2 Standards</p>
<p>All references to industry standards given in the text of this Sub-Code are to versions</p>
<p>which are current as at1 November 2007. However, Metering is required to comply</p>
<p>with the version of any such standard, equivalent or replacement which is in force at</p>
<p>the date of installation.</p>
<p>3 Facilities to be Provided at Metering Points</p>
<p>3.1 General</p>
<p>Although for clarity the specification identifies separate items of equipment, nothing in</p>
<p>this Sub-Code prevents the items being combined to perform the same task provided</p>
<p>the requirements of this Sub-Code are met.</p>
<p>3.2 Meters</p>
<p>3.2.1 For each circuit the following energy measurements are required at or in</p>
<p>relation to the Connection Point:-</p>
<p>(a) Active Energy for Import (kWh);</p>
<p>(b) Active Energy for Export (kWh) (applicable to Generators only);</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 158</p>
<p>(c) Reactive Energy for Import and Export (kVArh).</p>
<p>3.2.2 The Meter Responsible Person shall ensure that Metering for the above</p>
<p>measurements shall normally be provided on the User’s side of the Connection</p>
<p>Point in order to measure required Settlement Values.</p>
<p>3.2.3 Active Energy Meters (kWh)</p>
<p>Active Energy meters shall comply with the relevant part of BS EN 62053 (or</p>
<p>the standard current at the date of design of such equipment) for class 2 meters.</p>
<p>3.2.4 Reactive Energy Meters (kVArh)</p>
<p>Reactive Energy meters shall comply with the relevant requirements of IEC</p>
<p>Standard 1268 or BS EN 62053 (or the standard current at the date of design of</p>
<p>such equipment) Part 4 for class 3 meters.</p>
<p>3.2.5 The measurements will be produced using the outputs from current transformers</p>
<p>and voltage transformers.</p>
<p>3.2.6 Each circuit will be provided with:-</p>
<p>(a) main kWh meter; and</p>
<p>(b) two main kVArh meters or one bi-directional kVArh meter for lagging</p>
<p>and leading power factors;</p>
<p>Paragraph 3.2.9 deals with the situation where Import and/or Export of Active</p>
<p>Energy is required at the same point where a single meter can be used.</p>
<p>3.2.7 If direct measurement of the required values cannot be achieved, then the</p>
<p>required values may be calculated using values measured at other points subject</p>
<p>to prior agreement with the DNO and providing the Overall Accuracy meets</p>
<p>the requirements of paragraph 4.1. Where compensation is applied the values</p>
<p>shall be recorded and supporting evidence shall be available to justify the</p>
<p>compensation criteria.</p>
<p>3.2.8 Where the Import and/or Export of Active Energy and Reactive Energy is</p>
<p>required to be measured at the same point, these functions may be combined in</p>
<p>a single meter in which each energy flow is measured separately.</p>
<p>3.2.9 Meters shall be labelled in accordance with the Appendix of this Sub-Code.</p>
<p>3.3 Instrument Transformers</p>
<p>3.3.1 The terms &#8220;current transformer&#8221; (CT) and &#8220;voltage transformer&#8221; (VT) used in</p>
<p>this Sub-Code do not preclude the use of other measuring techniques providing</p>
<p>the accuracy, and also the longer term accuracy, in accordance with this Sub-</p>
<p>Code can be verified to the DNO’s satisfaction.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 159</p>
<p>3.3.2 In accordance with the principles in paragraph 3.2.2, all CTs and VTs will be</p>
<p>fitted on the User’s side of the Connection Point except where otherwise</p>
<p>agreed with the DNO.</p>
<p>3.3.3 Where CTs and/or VTs are used, they shall meet the requirements set out in</p>
<p>paragraphs 3.3.5 and 3.3.6 below.</p>
<p>3.3.4 Where CTs and/or VTs are used then a test terminal block or equivalent facility</p>
<p>shall be provided close to the meter(s). This facility will be fitted with the DNO</p>
<p>seals.</p>
<p>3.3.5 Current Transformers</p>
<p>(a) One set of CTs to IEC 60044-1 (or the standard current at the date of</p>
<p>design of such equipment) with a minimum standard of accuracy class</p>
<p>0.5S shall be provided per circuit and shall also meet (to the extent</p>
<p>applicable) any meter certification regulations in force at the time.</p>
<p>(b) Each CT secondary winding circuit supplying the meters shall be</p>
<p>dedicated to Metering purposes only. CT secondary winding may supply</p>
<p>both main and check meters as long as this does not put the overall</p>
<p>Metering system accuracy value outside the limits defined in paragraph</p>
<p>4.1.1 and sub-paragraph (e) below.</p>
<p>(c) Where a CT circuit has an additional burden not associated with meters,</p>
<p>e.g. to improve system accuracy, this additional burden shall not be</p>
<p>modified in any way without obtaining the approval of the DNO in</p>
<p>accordance with sub-paragraph (f) below.</p>
<p>(d) Common return leads for two or more CT secondary circuits are not</p>
<p>permitted.</p>
<p>(e) The total burden on CTs shall not exceed their rating at the rated</p>
<p>secondary current.</p>
<p>(f) Where any of the foregoing provisions of this paragraph 3.3.5 permit a</p>
<p>modification to CT secondary circuits, provided that the approval of the</p>
<p>DNO is sought for the modification, any such request must be made in</p>
<p>writing to the DNO a reasonable time in advance of the modification and</p>
<p>evidence of the value of any additional electrical burden must be made</p>
<p>available for inspection to verify compliance with this paragraph 3.3.5</p>
<p>and also to ensure there is no degradation of the accuracy required by</p>
<p>paragraph 4.1.1.</p>
<p>3.3.6 Voltage Transformers</p>
<p>(a) One VT to IEC 60044-2 (or the standard current at the date of design of</p>
<p>such equipment) with a minimum standard of accuracy class 11 shall be</p>
<p>provided for the Metering of each circuit and shall also (to the extent</p>
<p>applicable) meet any meter certification regulations in force at the time.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 160</p>
<p>(b) Capacitor VTs shall have a working burden which provides for</p>
<p>monitoring of the integrity of each fuse and which does not exceed the</p>
<p>maximum rating or fall below the minimum rating stipulated by the</p>
<p>relevant manufacturer.</p>
<p>(c) Each VT secondary winding supplying the meters shall be dedicated to</p>
<p>Metering purposes only. VT secondary winding may supply both main</p>
<p>and check meters as long as this does not put the overall Metering</p>
<p>System accuracy value outside the limits defined in paragraph 4.1.1 and</p>
<p>subparagraph (f) below.</p>
<p>(d) Where a VT circuit has an additional burden not associated with meters</p>
<p>e.g. to improve system accuracy, this additional burden shall not be</p>
<p>modified in any way unless the approval of the DNO is obtained in</p>
<p>accordance with sub paragraph (g) below.</p>
<p>(e) Each meter circuit shall be fed by a separate, fused supply from the VT.</p>
<p>(f) The total burden on VTs shall not exceed their rating at the rated</p>
<p>secondary voltages.</p>
<p>(g) Where any of the foregoing provisions of this paragraph 3.3.6 permit a</p>
<p>modification to VT secondary circuits, provided that the approval of the</p>
<p>DNO is sought for the modification, any such request must be made in</p>
<p>writing to the DNO a reasonable time in advance of the modification and</p>
<p>evidence of the value of any additional electrical burden must be made</p>
<p>available for inspection to verify compliance with this paragraph 3.3.6</p>
<p>and also to ensure there is no degradation of accuracy as required by</p>
<p>paragraph 4.1.1.</p>
<p>3.3.7 Existing Installations</p>
<p>For installations connected to the Distribution System prior to 1 January 2010,</p>
<p>the installed instrument transformers may be used irrespective of their accuracy</p>
<p>class providing the Overall Accuracy requirements as defined in paragraph 4.1</p>
<p>are met and also the following:</p>
<p>(i) in the event of a significant alteration to the primary plant (e.g. a</p>
<p>switchgear change), new instrument transformers which comply with</p>
<p>paragraphs 3.3.5 and 3.3.6 shall be provided; and</p>
<p>(ii) separately fused VT supplies shall be provided for the main and the</p>
<p>check meters.</p>
<p>3.4 Data Collectors</p>
<p>3.4.1 Data collectors may be either an integral part of individual circuit meters or</p>
<p>stand alone units which collect pulses from one or more individual meters.</p>
<p>Duplicate data collectors may also be an integral part of check meters or stand</p>
<p>alone units. These will be provided by the Meter Responsible Person and used</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 161</p>
<p>to collect, store and transmit energy values for each Settlement Period to a</p>
<p>DNO Data Collection System.</p>
<p>3.4.2 The following is required:</p>
<p>(a) the data collectors must have sufficient data channels to store all halfhour</p>
<p>value types necessary for settlement (e.g. kWh and kVArh Import</p>
<p>and Export per connection) and be capable of storing these values during</p>
<p>failure of the AC power supply;</p>
<p>(b) on demand from the DNO Data Collection System the data collector</p>
<p>will transfer the recorded Settlement Values without loss or error. The</p>
<p>Settlement Values must also be transferable manually using a portable</p>
<p>collection device (personal computer/hand held unit/removable memory</p>
<p>module etc) of a type compatible with the system used by the DNO; and</p>
<p>(c) in the event of failure of communications with the central collection</p>
<p>station the data collector will be capable of storing a minimum of five</p>
<p>channels of data per connection for a minimum period of 20 days with an</p>
<p>integrating period of 30 minutes. This 20 day period may reduce pro rata</p>
<p>dependent on the notified demand period selected as described in</p>
<p>paragraph 3.4.3 below. Access to the manual transfer facility will be</p>
<p>secured from unauthorised interference.</p>
<p>3.4.3 The settlement period shall be selectable over the following range: 30, 15, and 1</p>
<p>minutes and will be notified by the DNO. For any selectable value in this range</p>
<p>one Settlement Period shall commence on the hour and half-hour.</p>
<p>3.4.4 Monitoring facilities shall be provided for data collector fault conditions and to</p>
<p>record any instances of local interrogation which changes data.</p>
<p>3.5 Data Collection System</p>
<p>3.5.1 Communications</p>
<p>The means of communication between the data collector and the central DNO</p>
<p>Data Collection System must be secure at the remote end. Communication can</p>
<p>be via PSTN, PTN, GPRS, GSM networks or by any other technically suitable</p>
<p>means which has previously been agreed with the DNO.</p>
<p>3.5.2 Central Collection Station</p>
<p>The DNO Data Collection System will interrogate each remote meter or data</p>
<p>collector. All the DNO operations carried out either manually or automatically</p>
<p>shall be protected by password protection. The DNO Data Collection System</p>
<p>will synchronise the outstations during interrogation to a standard reference</p>
<p>time. Following receipt of all data channels from the outstation the meter data</p>
<p>will be transferred to the DNO’s billing and settlement systems.</p>
<p>3.5.3 Supply Voltage</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 162</p>
<p>Assured Supplies must be used where ever possible. However, where a</p>
<p>measurement VT source is used and the outstation is storing data for more than</p>
<p>one circuit, a voltage selector relay scheme using each circuit involved shall be</p>
<p>provided. Local and remote phase failure indications shall be provided.</p>
<p>3.6 Facilities</p>
<p>The Metering equipment shall be capable of providing voltage free (clean contacts)</p>
<p>relay outputs which accurately represent the recorded channel values for:-</p>
<p>(a) kWh (Import and Export) and kVArh (lagging and leading).</p>
<p>(b) A 30 minute reset pulse</p>
<p>4 Measurement Criteria</p>
<p>4.1 Accuracy</p>
<p>4.1.1 Overall Accuracy of Equipment</p>
<p>Meters shall be calibrated so as to achieve Overall Accuracy of Metering within</p>
<p>the limits set out below. Calibration of meters shall be adjusted due to current</p>
<p>and voltage transformer errors and/or errors due to lead electrical burdens but</p>
<p>not for primary transformer losses. Paragraph 4.2.2 deals further with this</p>
<p>issue.</p>
<p>(a) Active Energy Measurement</p>
<p><em>Conditions of Test Limits of Error at Power Factor</em></p>
<p>Current expressed as a percentage of rated</p>
<p>measuring current</p>
<p>Power Factor Limits of Error</p>
<p>100% to 20% inclusive</p>
<p>Below 20% to 5% inclusive</p>
<p>100% to 20% inclusive</p>
<p>1.0</p>
<p>1.0</p>
<p>0.5 lag and 0.8 lead</p>
<p>±1.5%</p>
<p>±2.5%</p>
<p>±2.5%</p>
<p>(b) Reactive Energy Measurement</p>
<p><em>Conditions of Test Limits of Error at Power Factor</em></p>
<p>Current expressed as a percentage of rated</p>
<p>measuring current</p>
<p>Power Factor Limits of Error</p>
<p>100% &#8211; 20% inclusive</p>
<p>100% &#8211; 20% inclusive</p>
<p>0</p>
<p>0.866 lag and lead</p>
<p>±4.0%</p>
<p>±5.0%</p>
<p>4.1.2 Accuracy of Time Keeping</p>
<p>(a) The time keeping accuracy of Metering equipment shall be maintained</p>
<p>in accordance with Standard Time.</p>
<p>(b) The commencement of each Settlement Period shall be within 10</p>
<p>seconds of Standard Time.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 163</p>
<p>(c) The duration of each Settlement Period shall be within ± 0.1% of the</p>
<p>required duration, except where synchronisation has occurred in a</p>
<p>Settlement Period.</p>
<p>4.2 Compensation for Errors</p>
<p>4.2.1 Compensation for Instrument Transformer Errors</p>
<p>Compensation shall be made for errors of current and voltage transformers</p>
<p>and/or lead electrical burdens, if possible, in the meter calibration.</p>
<p>4.2.2 Compensation for Power Transformer and Line Losses</p>
<p>Where the installed Metering location and the Connection Point do not</p>
<p>coincide then, where necessary, compensation for power transformer and/or line</p>
<p>losses shall be provided to meet the Overall Accuracy at the boundary point</p>
<p>defined in paragraph 3.2.2. Compensation shall be made in the relevant data</p>
<p>collector and the formula for calculation shall be agreed between the DNO and</p>
<p>the relevant User.</p>
<p>4.2.3 Where existing calibration records do not exist, a recalibration test shall be</p>
<p>carried out where practicable. Values of compensation shall be recorded and</p>
<p>evidence to justify the compensation criteria shall be made available for</p>
<p>inspection, including all test certificates.</p>
<p>5 Calibration and Testing of Metering</p>
<p>5.1 Meters</p>
<p>Metering Systems shall be calibrated and tested in accordance with the relevant part of</p>
<p>BS EN 62053 and the manufacturer’s recommendations.</p>
<p>5.2 Current and Voltage Transformers</p>
<p>Measuring transformers shall be supplied with known characteristics within the</p>
<p>requirements of paragraph 3.3 of this Sub-Code.</p>
<p>5.3 Test Access to Metering Equipment</p>
<p>Metering equipment shall be provided with sealable test terminal blocks both at the</p>
<p>meter and if practicable at the switchgear to facilitate meter testing and current /</p>
<p>voltage transformer checks in situ. Test terminal block design shall be agreed in</p>
<p>advance with the DNO.</p>
<p>5.4 Data Collectors</p>
<p>5.4.1 Maintenance</p>
<p>Data collectors must be maintained in accordance with the manufacturer’s</p>
<p>recommendations or as otherwise necessary to meet the obligations of this Sub-</p>
<p>Code.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 164</p>
<p>5.4.2 Testing</p>
<p>There is no requirement for routine tests of data collectors other than as a part</p>
<p>of an overall Metering System test.</p>
<p>5.5 Records</p>
<p>The results of all tests and periodic checks shall be held as a permanent record by the</p>
<p>DNO and a copy held by the Generator.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 165</p>
<p>APPENDIX</p>
<p>LABELLING OF METERS FOR IMPORT AND EXPORT</p>
<p>1 ACTIVE ENERGY</p>
<p>Active Energy is considered to be Imported when it flows to the User System from</p>
<p>the Distribution System. The meter(s) registering this Active Energy should be</p>
<p>labelled &#8220;Import&#8221;.</p>
<p>Active Energy is considered to be Exported when it flows from the User System to</p>
<p>the Distribution System. The meter(s) registering this Active Energy should be</p>
<p>labelled &#8220;Export&#8221;.</p>
<p>Meters shall be labelled to distinguish between main and check meters.</p>
<p>2 REACTIVE ENERGY</p>
<p>Reactive Energy is considered to be Imported or Exported as follows:</p>
<p><em>Flow of active Energy Power Factor Flow of Reactive Energy</em></p>
<p>Import Lagging Import*</p>
<p>Import Leading Export*</p>
<p>Import Unity Zero</p>
<p>Export Lagging Export</p>
<p>Export Leading Import</p>
<p>Export Unity Zero</p>
<p>For the purposes of labelling of meters the conditions asterisked above will determine labelling</p>
<p>where Import for Active Energy is defined as in 1 above.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 166</p>
<p>Agreed Procedure No. 1</p>
<p>MAINTENANCE, TESTING, INSPECTION AND SEALING OF</p>
<p>METERING AND GENERATOR METERING CIRCUITS</p>
<p>for the electricity industry in</p>
<p>Northern Ireland</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 167</p>
<p>AGREED PROCEDURE No. 1</p>
<p>MAINTENANCE, TESTING , INSPECTION AND SEALING OF METERING AND</p>
<p>GENERATOR METERING CIRCUITS</p>
<p>Contents</p>
<p>1 Scope of Procedure</p>
<p>2 Use of the Procedure</p>
<p>3 Amendments to Forms</p>
<p>4 Interface and Timetable Information</p>
<p>Appendix A &#8211; Request to Break Seals Form</p>
<p>Appendix B &#8211; Meter Record Sheet</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 168</p>
<p>1 SCOPE OF PROCEDURE</p>
<p>1.1 This Agreed Procedure (the “Procedure”) outlines the responsibilities of the DNO and</p>
<p>the Generator with regard to notification, authorisation and witnessing of the breaking</p>
<p>and replacement of seals on generation Metering and Generator Metering Circuits and</p>
<p>the carrying out of routine and emergency maintenance, testing and calibration. The</p>
<p>procedure assumes the initial placement of seals by the appropriate Parties in</p>
<p>accordance with the Main Code.</p>
<p>1.2 The Procedure supplements the Main Code and the Sub-Codes of the Distribution</p>
<p>Metering Code to which reference should be made. In the event of an inconsistency</p>
<p>between the provisions of the Procedure and the Main Code or a Sub-Code the</p>
<p>provisions of the Main Code or such Sub-Code shall prevail. The provisions of the</p>
<p>Main Code shall prevail over the provisions of any Sub-Code.</p>
<p>1.3 The Procedure is part of the Distribution Code and terms and expressions defined in the</p>
<p>Distribution Code have the same meaning in the Procedure.</p>
<p>2 USE OF THE PROCEDURE</p>
<p>2.1 The Procedure is to be used by the DNO and Generator staff to ensure that the breaking</p>
<p>and replacement of seals and the carrying out of routine and emergency maintenance,</p>
<p>testing and calibration on generation Metering and Generator Metering Circuits is</p>
<p>correctly authorised and witnessed and that documentary evidence is available to that</p>
<p>effect.</p>
<p>2.2 Where it is not possible to gain prior authorisation for the breaking of a seal</p>
<p>necessitated by malfunctioning of both main and check meters on a circuit, fire or</p>
<p>similar hazard or non-compliance by a party with its obligations under the Main Code</p>
<p>authorisation should be sought as soon as possible after the event.</p>
<p>3 AMENDMENTS TO FORMS</p>
<p>3.1 Forms set out in the Appendices to this Procedure may be amended from time to time</p>
<p>by the DNO upon reasonable notice to all Generators. The DNO shall also take into</p>
<p>account reasonable comments of Generators.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 169</p>
<p>4. INTERFACE AND TIMETABLE INFORMATION</p>
<p>Section: MAINTENANCE, TESTING AND INSPECTION OF METERING AND GENERATOR METERING CIRCUITS</p>
<p>Subject: Interface and Timetable Information – Maintenance, Testing, Inspection, Calibration and Sealing of Metering</p>
<p>REF WHEN ACTION FROM/BY TO METHOD</p>
<p>EITHER:</p>
<p>1a Routine Inspection, Maintenance, Testing &amp; Calibration</p>
<p>At least 5 days</p>
<p>prior to carrying</p>
<p>work out</p>
<p>Notify date, time, work required, estimated duration and request</p>
<p>breaking of seals (as necessary)</p>
<p>DNO or</p>
<p>Generator</p>
<p>Generator</p>
<p>or DNO</p>
<p>Fax on standard</p>
<p>form (Appendix A)</p>
<p>OR:</p>
<p>1b Inspection, Maintenance, Testing and Calibration in an Emergency</p>
<p>At the earliest</p>
<p>opportunity</p>
<p>Notify, date, time, place, work required, estimated duration and</p>
<p>request breaking of seals (as necessary)</p>
<p>DNO or</p>
<p>Generator</p>
<p>Generator</p>
<p>or DNO</p>
<p>Fax on standard</p>
<p>form (Appendix A)</p>
<p>or verbally</p>
<p>2 Prior to work being</p>
<p>carried out (Note 1)</p>
<p>Grant permission to break seals (as appropriate) and notify as to</p>
<p>attendance</p>
<p>Generator</p>
<p>or DNO</p>
<p>DNO or</p>
<p>Generator</p>
<p>Fax on standard</p>
<p>form (Appendix A)</p>
<p>or verbally</p>
<p>3 Day work carried</p>
<p>out</p>
<p>Record meter readings prior to seals being broken and</p>
<p>commencing work</p>
<p>DNO or</p>
<p>Nominated</p>
<p>Party</p>
<p>Manual record</p>
<p>(Appendix B)</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 170</p>
<p>4. INTERFACE AND TIMETABLE INFORMATION</p>
<p>Section: MAINTENANCE, TESTING AND INSPECTION OF METERING AND GENERATOR METERING CIRCUITS</p>
<p>Subject: Interface and Timetable Information – Maintenance, Testing, Inspection, Calibration and Sealing of Metering</p>
<p>REF WHEN ACTION FROM/BY TO METHOD</p>
<p>4a Day work carried</p>
<p>out</p>
<p>Carry out required work. Record details of work done DNO or</p>
<p>Generator</p>
<p>Manual record</p>
<p>(Appendix A)</p>
<p>4b Where possible Witness work being carried out Generator</p>
<p>or DNO</p>
<p>5 After work</p>
<p>completed</p>
<p>Apply own seals and read meters DNO and</p>
<p>Generator</p>
<p>6 After work</p>
<p>completed</p>
<p>Check accuracy of manual record and sign to confirm work</p>
<p>completed and seal applied</p>
<p>DNO and</p>
<p>Generator</p>
<p>Manual record</p>
<p>(Appendix A)</p>
<p>7 After work</p>
<p>completed</p>
<p>Record meter readings DNO or</p>
<p>Generator</p>
<p>Manual record</p>
<p>(Appendix B)</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 171</p>
<p>4. INTERFACE AND TIMETABLE INFORMATION</p>
<p>Section: MAINTENANCE, TESTING AND INSPECTION OF METERING AND GENERATOR METERING CIRCUITS</p>
<p>Subject: Interface and Timetable Information – Maintenance, Testing, Inspection, Calibration and Sealing of Metering</p>
<p>REF WHEN ACTION FROM/BY TO METHOD</p>
<p>8 After work</p>
<p>completed</p>
<p>Copy meter record sheet and work sheet and issue to other</p>
<p>party</p>
<p>DNO or</p>
<p>Generator</p>
<p>Generator</p>
<p>or DNO</p>
<p>By hand</p>
<p>Note 1 In an emergency situation when it is impossible to contact the DNO or the Generator, it may be necessary to break seals prior to the granting</p>
<p>of permission. An emergency situation is defined by the Main Code as when “both main and check meters are malfunctioning or there occurs a fire</p>
<p>or other similar hazard and such removal (of seals) is essential”. In such circumstances fax or other communication of the intent to break seals will</p>
<p>be supplied to the DNO or Generator prior to the commencement of emergency work. The authorisation procedure to break seals must be followed</p>
<p>retrospectively. In an emergency situation when it is impossible to await the required paperwork, verbal consent may be given. In such</p>
<p>circumstances written consent must follow forthwith.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 172</p>
<p>APPENDIX A</p>
<p>TO: [DNO/Generator] Date: [ ]</p>
<p>Tel: [ ]</p>
<p>Fax: [ ]</p>
<p>GENERATOR: SERIAL NO:</p>
<p>DETAILS OF WORK TO BE CARRIED OUT:</p>
<p>We request permission to carry out the work described below and to break such seals as are</p>
<p>necessary. We estimate the duration of the work to be from [ ] to [ ]. The</p>
<p>work is to be carried out at [Site] by [ ].</p>
<p>The description of the work is as follows:</p>
<p>The circuits and meters to be affected are as follows:-</p>
<p>CIRCUIT/METER ID COMMENTS</p>
<p>FROM:</p>
<p>Name Signature____________________________</p>
<p>Position Date________________________________</p>
<p>Continued &#8230;&#8230;&#8230;</p>
<p>REQUEST TO BREAK SEALS</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 173</p>
<p>COMMENTS OF RECIPIENTS:</p>
<p>We acknowledge receipt of your request dated [ ]. We hereby [give/withhold]* consent. Our</p>
<p>reasons for withholding consent are [ ].</p>
<p>Our representative dealing with sealing is [ ]. He will/will not be attending when the</p>
<p>work is carried out.</p>
<p>BY:</p>
<p>Name Signature_________________________</p>
<p>Position Date______________________________</p>
<p>CONFIRM COMPLETION OF WORK AND SEALS APPLIED:</p>
<p>DESCRIPTION OF COMPLETEDWORK:</p>
<p>CONFIRMATION OF SEALING:</p>
<p>(DNO)</p>
<p>Name Signature</p>
<p>Position Date</p>
<p>(GENERATOR)</p>
<p>Name Signature</p>
<p>Position Date</p>
<p>[* Delete as appropriate]</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 174</p>
<p>SHEET: OF</p>
<p>SERIAL NO:</p>
<p>APPENDIX B</p>
<p>METER RECORD SHEET</p>
<p>GENERATOR :</p>
<p>READING DATE :</p>
<p>SITE NAME :</p>
<p>READING TIMES : START :</p>
<p>METER ID : FINISH :</p>
<p>FUNCTION</p>
<p>MAIN METER CHECK METER</p>
<p>BEFORE AFTER BEFORE AFTER</p>
<p>MWh EXPORT</p>
<p>MWh IMPORT</p>
<p>MVAr EXPORT</p>
<p>MVAr IMPORT</p>
<p>RECORDER GENERATORWITNESS</p>
<p>NAME</p>
<p>SIGNATURE</p>
<p>DATE</p>
<p>COMPANY</p>
<p>ACTING FOR</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 175</p>
<p>Agreed Procedure No. 2</p>
<p>MAINTENANCE, TESTING, INSPECTION AND SEALING</p>
<p>OF METERING</p>
<p>(DEMAND CUSTOMER)</p>
<p>for the electricity industry in</p>
<p>Northern Ireland</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 176</p>
<p>AGREED PROCEDURE No. 2</p>
<p>MAINTENANCE, TESTING, INSPECTION AND SEALING OF METERING</p>
<p>(DEMAND CUSTOMER)</p>
<p>Contents</p>
<p>1 Scope of Procedure</p>
<p>2 Use of the Procedure</p>
<p>3 Amendments to Forms</p>
<p>4 Interface and Timetable Information</p>
<p>Appendix A – Guide to Use of AP2 Forms</p>
<p>Form MT1/1</p>
<p>Form MT1/2</p>
<p>Form MT2</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 177</p>
<p>SCOPE OF PROCEDURE</p>
<p>1.1 This Agreed Procedure (the &#8220;Procedure&#8221;) outlines the responsibilities of the DNO and</p>
<p>the Meter Responsible Person with regard to notification, authorisation and witnessing</p>
<p>of the breaking and replacement of seals on Demand Customer Metering and the</p>
<p>carrying out of routine and emergency maintenance, testing and calibration. The</p>
<p>Procedure assumes the initial placement of seals by the appropriate Parties in</p>
<p>accordance with paragraph 9.6 in the Main Code.</p>
<p>1.2 The Procedure supplements the Main Code and the Sub-Codes of the Metering Code to</p>
<p>which reference should be made. In the event of an inconsistency between the</p>
<p>provisions of the Procedure and the Main Code or a Sub-Code the provisions of the</p>
<p>Main Code or such Sub-Code shall prevail. The provisions of the Main Code shall</p>
<p>prevail over the provisions of any Sub-Code.</p>
<p>1.3 The Procedure is part of the Distribution Code and terms and expressions defined in the</p>
<p>Distribution Code have the same meaning in the Procedure.</p>
<p>2 USE OF THE PROCEDURE</p>
<p>2.1 The Procedure is to be used by the DNO and the Meter Responsible Person to ensure</p>
<p>that the breaking and replacement of seals and the carrying out of routine and</p>
<p>emergency maintenance, testing and calibration on Demand Customer Metering is</p>
<p>correctly authorised and witnessed and that documentary evidence is available to that</p>
<p>effect.</p>
<p>2.2 Where it is not possible to gain prior authorisation for the breaking of a seal in the</p>
<p>event of an emergency as described in paragraph 9.6(d)d of the Main Code or noncompliance</p>
<p>by a party with its obligations under the Main Code, authorisation should</p>
<p>be sought as soon as possible after the event.</p>
<p>2.3 A record of work and inspections carried out must be maintained in accordance with</p>
<p>paragraph 9.5 of the Main Code.</p>
<p>2.4 Throughout this Procedure, timetables reflect the number of Business Days (BD) before</p>
<p>or after which (as the case may be) an activity should be completed.</p>
<p>3 AMENDMENTS TO FORMS</p>
<p>3.1 Forms set out in the Appendices to this Procedure may be amended from time to time</p>
<p>by the DNO upon reasonable notice to all relevant Parties. The DNO shall also take</p>
<p>into account reasonable comments of relevant Parties.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 178</p>
<p>4. INTERFACE AND TIMETABLE INFORMATION</p>
<p>Section: MAINTENANCE, TESTING, INSPECTION AND SEALING OF METERING (DEMAND CUSTOMER)</p>
<p>Subject: Interface and Timetable Information – Maintenance, Testing, Inspection, Calibration and Sealing of Metering.</p>
<p>REF WHEN ACTION FROM/BY TO METHOD</p>
<p>EITHER:</p>
<p>1a Routine Inspection, Maintenance, Testing &amp; Calibration</p>
<p>At least 15 BD</p>
<p>prior to carrying</p>
<p>work out</p>
<p>Notify date, time, work required, estimated</p>
<p>duration and request breaking of seals (as</p>
<p>necessary)</p>
<p>DNO or Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>Meter</p>
<p>Responsible</p>
<p>Person or DNO</p>
<p>Fax / Post on standard</p>
<p>form MT1/1</p>
<p>OR:</p>
<p>1b. Inspection, Maintenance, Testing and Calibration in an Emergency</p>
<p>At the earliest</p>
<p>opportunity</p>
<p>Notify, date, time, place, work required,</p>
<p>estimated duration and request breaking of</p>
<p>seals (as necessary)</p>
<p>DNO or Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>Meter</p>
<p>Responsible</p>
<p>Person or DNO</p>
<p>Fax / Post on standard</p>
<p>form MT1/1 or verbally</p>
<p>Prior to work being</p>
<p>carried out</p>
<p>Acknowledge receipt of request to break</p>
<p>seals and confirm attendance of party</p>
<p>representative</p>
<p>Meter</p>
<p>Responsible</p>
<p>Person or DNO</p>
<p>DNO or Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>Fax / Post on standard</p>
<p>form MT1/2</p>
<p>3a. Day work carried</p>
<p>out</p>
<p>Record meter readings prior to seals being</p>
<p>broken and commencing work</p>
<p>DNO or Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>Manual record on</p>
<p>standard form MT2</p>
<p>3b. Where possible Witness recording of meter readings DNO or Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 179</p>
<p>4. INTERFACE AND TIMETABLE INFORMATION</p>
<p>Section: MAINTENANCE, TESTING, INSPECTION AND SEALING OF METERING (DEMAND CUSTOMER)</p>
<p>Subject: Interface and Timetable Information – Maintenance, Testing, Inspection, Calibration and Sealing of Metering.</p>
<p>REF WHEN ACTION FROM/BY TO METHOD</p>
<p>4a. Day work carried</p>
<p>out</p>
<p>Carry out required work. Record details of</p>
<p>work done.</p>
<p>DNO or Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>Manual record on</p>
<p>standard form MT1/2</p>
<p>4b. Where possible Witness work being carried out Meter</p>
<p>Responsible</p>
<p>Person or DNO</p>
<p>5a. After work</p>
<p>completed</p>
<p>Apply seals and then record meter readings. DNO or Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>Manual record on</p>
<p>standard form MT2</p>
<p>5b. Where possible Witness recording of meter readings and</p>
<p>application of seals</p>
<p>DNO or Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>After work</p>
<p>completed</p>
<p>Check accuracy of manual record and sign</p>
<p>to confirm work completed and seal applied</p>
<p>DNO and Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>Standard form MT1/2</p>
<p>After work</p>
<p>completed</p>
<p>Copy meter record sheet and work sheet</p>
<p>and issue to other party</p>
<p>DNO or Meter</p>
<p>Responsible</p>
<p>Person</p>
<p>Meter</p>
<p>Responsible</p>
<p>Person or DNO</p>
<p>By hand</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 180</p>
<p>APPENDIX A</p>
<p>GUIDE TO USE OF AP2 FORMS</p>
<p>AP2 Description Use Form</p>
<p>4.1a/b DNO or Meter Responsible Person give notification of work</p>
<p>to be carried out /completed on Metering.</p>
<p>MT1 / 1</p>
<p>DNO or Meter Responsible Person acknowledge receipt of</p>
<p>form MT1/1 and confirm attendance of representative</p>
<p>during work.</p>
<p>MT1 / 2</p>
<p>4.3a, 4.5a Record of meter readings before and after doing work MT2</p>
<p>4.4a, 4.6 Record of work done in relation to metering MT1 / 2</p>
<p>For forms completed by the Meter Responsible Person, please fax or post to the following address:</p>
<p>NIE plc (Attn: Manager, Customer Service Revenue)</p>
<p>Malone Road</p>
<p>Belfast BT9 5HT</p>
<p>FAX NO: 01232 689280</p>
<p>or such other address and /or recipient as the DNO may notify from time to time.</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 181</p>
<p>Serial No&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;</p>
<p>Page 1 of 2</p>
<p>MT1/1</p>
<p>NOTIFICATION OF WORK TO BE CARRIED OUT/COMPLETED</p>
<p>TO: (DNO/METER</p>
<p>RESPONSIBLE PERSON)*</p>
<p>SITE NAME:</p>
<p>DNO CRN:</p>
<p>METERING ID:</p>
<p>DETAILS OF WORK TO BE CARRIED OUT:</p>
<p>Notification is hereby given to carry out work described below and to break such seals as are</p>
<p>necessary on:-</p>
<p>Date:</p>
<p>We estimate the duration of work to be:- Start Time:</p>
<p>Stop Time:</p>
<p>The work is to be carried out at site by:</p>
<p>The description of the work is as follows:</p>
<p>The circuits and meters to be affected are as follows:-</p>
<p>CIRCUIT/METER SER NO. COMMENTS</p>
<p>FROM: (DNO/METER RESPONSIBLE PERSON)*</p>
<p>Name: Signature:</p>
<p>Position Date:</p>
<p>(* Delete as appropriate)</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 182</p>
<p>Continued&#8230;.</p>
<p>Serial No&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;</p>
<p>Page 2 of 2</p>
<p>MT1/2</p>
<p>COMMENTS OF RECIPIENTS:</p>
<p>We acknowledge receipt of your notification dated:</p>
<p>Our representative is:</p>
<p>and (will/will not)* be attending when the work is carried out.</p>
<p>FROM: (DNO/METER RESPONSIBLE PERSON)*</p>
<p>Name: Signature:</p>
<p>Position Date:</p>
<p>CONFIRM COMPLETION OF WORK AND SEALS APPLIED:</p>
<p>Description of completed work:</p>
<p>Confirmation of sealing:</p>
<p>Date of work:</p>
<p>Time work commenced:</p>
<p>Time work completed:</p>
<p>FOR DNO:</p>
<p>Name: Signature:</p>
<p>Position Date:</p>
<p>FOR METER RESPONSIBLE PERSON:</p>
<p>Name: Signature:</p>
<p>Position Date:</p>
<p>(* Delete as appropriate)</p>
<p>Distribution Code 1 May 2010</p>
<p>The Distribution Metering Code Page 183</p>
<p>Serial No &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;..</p>
<p>Page of</p>
<p>MT2</p>
<p>METER READINGS RECORD SHEET</p>
<p>For multiple feeder sites use additional sheets.</p>
<p>METER</p>
<p>RESPONSIBLE</p>
<p>PERSON:</p>
<p>READING DATE:</p>
<p>SITE NAME: READING TIMES: START:</p>
<p>FINISH:</p>
<p>METERING ID: METER SERIAL</p>
<p>NO(S):</p>
<p>FUNCTION MAIN METER READING CHECK METER READING</p>
<p>BEFORE AFTER BEFORE AFTER</p>
<p>kWh EXPORT</p>
<p>2kWh IMPORT</p>
<p>kVArh EXPORT</p>
<p>kVArh IMPORT</p>
<p>PARTY RECORDING PARTYWITNESSING</p>
<p>NAME</p>
<p>SIGNATURE</p>
<p>DATE</p>
<p>POSITION</p>
<p>COMPANY</p>
<p>Distribution Code 1 May 2010</p>
<p>Agreed Procedure No. 3</p>
<p>METER ADVANCE RECONCILIATION</p>
<p>(HALF HOUR METERED GENERATION)</p>
<p>for the electricity industry in</p>
<p>Northern Ireland</p>
<p>Distribution Code 1 May 2010</p>
<p>AGREED PROCEDURE No. 3</p>
<p>METER ADVANCE RECONCILIATION (GENERATION)</p>
<p>Contents</p>
<p>1 Scope of Procedure</p>
<p>2 Use of the Procedure</p>
<p>3 Amendments to Proformas and Examples</p>
<p>4 Interface and Timetable Information</p>
<p>Appendix A: Proforma of Meter Advance Reconciliation &#8211; Notice of Meter Reading</p>
<p>Appendix B: Proforma of Meter Advance Reconciliation Record</p>
<p>Appendix C: Example of Meter Register Comparison Report</p>
<p>Appendix D: Proforma of Meter Advance Reconciliation Statement</p>
<p>Distribution Code 1 May 2010</p>
<p>1 SCOPE OF THE AGREED PROCEDURE</p>
<p>1.1 This Agreed Procedure (the “Procedure”) covers the collection and processing of tariff</p>
<p>meter readings which are taken quarterly pursuant to paragraph 9.7 of the Main Code</p>
<p>and the reconciliation of such meter readings with Settlement Values collected</p>
<p>electronically and stored on the DNO Data Collection System. This reconciliation is</p>
<p>achieved by comparing the manually read meter register readings with the</p>
<p>accumulations recorded in the DNO Data Collection System. Any discrepancies</p>
<p>discovered will be processed in accordance with the Trading &amp; Settlement Code.</p>
<p>1.2 The Procedure seeks to ensure that any discrepancy between tariff meter register</p>
<p>readings and Settlement Values collected electronically from such meters is identified</p>
<p>on a regular basis such that appropriate adjustments to payments can be made.</p>
<p>1.3 The Procedure supplements the Main Code and the Sub-Codes of the Metering Code to</p>
<p>which reference should be made. In the event of an inconsistency between the</p>
<p>provisions of the Procedure and the Main Code or a Sub-Code the provisions of the</p>
<p>Main Code or such Sub-Code shall prevail. The provisions of the Main Code shall</p>
<p>prevail over the provisions of any Sub-Code.</p>
<p>1.4 The Procedure is part of the Distribution Code and terms and expressions defined in the</p>
<p>Distribution Code have the same meaning in the Procedure.</p>
<p>1.5 This Procedure applies to half hour metered Generators only. The meter advance</p>
<p>reconciliation procedures for Demand Customers are covered by Retail Market</p>
<p>Procedure MP NI 105.</p>
<p>2 USE OF THE PROCEDURE</p>
<p>2.1 The Procedure shall be used by the DNO and staff of those Generators who are metered</p>
<p>on a half-hourly basis who are responsible for meter advance reconciliation readings</p>
<p>and processing.</p>
<p>3 AMENDMENTS TO PROFORMAS AND EXAMPLES</p>
<p>3.1 Proformas and examples set out in the Appendices to this Procedure may be amended</p>
<p>from time to time by the DNO upon reasonable notice to all Generators. The DNO</p>
<p>shall also take into account reasonable comments of Generators.</p>
<p>Distribution Code 1 May 2010</p>
<p>4 INTERFACE AND TIMETABLE INFORMATION</p>
<p>Section: METER ADVANCE RECONCILIATION (GENERATION)</p>
<p>Subject: Interface and Timetable Information – Reconciliation of Meter Readings with Accumulated Settlement Values</p>
<p>REF WHEN ACTION FROM/B</p>
<p>Y</p>
<p>TO METHOD</p>
<p>1 Annually For each calendar month draw up a plan of the meter</p>
<p>readings which are to take place and issue to the</p>
<p>Generator. Such readings to be scheduled at intervals</p>
<p>not exceeding 3 months.</p>
<p>DNO Generator Fax</p>
<p>2 At least 5 days</p>
<p>before reading</p>
<p>date</p>
<p>Advise the Generator of date and time for reading to take</p>
<p>place</p>
<p>DNO Generator Fax on standard</p>
<p>form (Appendix</p>
<p>A)</p>
<p>3 Within 3 months</p>
<p>of last reading</p>
<p>Read meter registers (in the presence of the Generator</p>
<p>representative if attending) as close as is practicable to</p>
<p>the end of a Settlement Period. Record time and date of</p>
<p>reading and meter register values. The DNO and</p>
<p>Generator representative sign record sheet. (Note 1)</p>
<p>DNO and</p>
<p>Generator</p>
<p>Manual record</p>
<p>(Appendix B)</p>
<p>4 Before leaving</p>
<p>site</p>
<p>Sign off and hand copy of actual meter values with time</p>
<p>and date of reading to the Generator.</p>
<p>DNO Generator Manual record</p>
<p>(Appendix B)</p>
<p>Distribution Code 1 May 2010</p>
<p>Section: METER ADVANCE RECONCILIATION (GENERATION)</p>
<p>Subject: Interface and Timetable Information – Reconciliation of Meter Readings with Accumulated Settlement Values</p>
<p>REF WHEN ACTION FROM/B</p>
<p>Y</p>
<p>TO METHOD</p>
<p>5 Within 3</p>
<p>Business Days of</p>
<p>meter reading</p>
<p>(i) Input meter register values, time and date of</p>
<p>reading to the meter register comparison process</p>
<p>of the DNO Data Collection System</p>
<p>(ii) Run meter register comparison process which</p>
<p>compares the difference between the latest</p>
<p>actual and the previous actual reading with the</p>
<p>electronically recorded total delivered energy for</p>
<p>the known time interval</p>
<p>(iii) Print out meter register comparison report</p>
<p>(Appendix C)</p>
<p>DNO Generator On line entry to</p>
<p>the DNO Data</p>
<p>Collection</p>
<p>System</p>
<p>EITHER:</p>
<p>6a Within 5</p>
<p>Business Days of</p>
<p>meter reading</p>
<p>Where the relevant meter register comparison report</p>
<p>shows a difference of less than 0.02%:</p>
<p>- issue copy of report to the Generator (Note 2)</p>
<p>DNO Generator Fax</p>
<p>OR:</p>
<p>6b Within 5</p>
<p>Business Days of</p>
<p>meter reading</p>
<p>Where meter register comparison report shows a</p>
<p>difference of 0.02% or greater:</p>
<p>- prepare a Meter Reconciliation Statement and issue to</p>
<p>the Generator , together with copies of the relevant</p>
<p>meter register comparison reports (Note 2)</p>
<p>Generator DNO</p>
<p>Distribution Code 1 May 2010</p>
<p>Section:METER ADVANCE RECONCILIATION (GENERATION)</p>
<p>Subject: Interface and Timetable Information – Reconciliation of Meter Readings with Accumulated Settlement Values</p>
<p>REF WHEN ACTION FROM/B</p>
<p>Y</p>
<p>TO METHOD</p>
<p>7a Within 14</p>
<p>Business Days of</p>
<p>receipt of Meter</p>
<p>Reconciliation</p>
<p>Statement</p>
<p>Review Meter Reconciliation Statement and either:</p>
<p>(i) advise the DNO that the Meter Reconciliation</p>
<p>Statement is agreed</p>
<p>OR</p>
<p>(ii) discuss areas of concern with the DNO, providing</p>
<p>supporting evidence as necessary</p>
<p>Generator DNO</p>
<p>7b Where revisions to the initial Meter Reconciliation</p>
<p>Statement are agreed, prepare a replacement Meter</p>
<p>Reconciliation Statement and issue to Generator</p>
<p>DNO Generator Fax</p>
<p>8a On or before 15th</p>
<p>Business Day</p>
<p>after receipt of</p>
<p>Meter</p>
<p>Reconciliation</p>
<p>Statement</p>
<p>Where the Meter Reconciliation Statement is agreed,</p>
<p>indicate agreement on form and sign and return to the</p>
<p>DNO</p>
<p>Generator DNO Fax</p>
<p>8b Where the Meter Reconciliation Statement is disputed,</p>
<p>indicate non-agreement on form and sign and return to</p>
<p>the DNO. Immediately thereafter raise a formal dispute</p>
<p>as per the Disputes Procedure of the PPA</p>
<p>Generator DNO Fax</p>
<p>Distribution Code 1 May 2010</p>
<p>Section:METER ADVANCE RECONCILIATION (GENERATION)</p>
<p>Subject: Interface and Timetable Information – Reconciliation of Meter Readings with Accumulated Settlement Values</p>
<p>Ref WHEN ACTION FROM/B</p>
<p>Y</p>
<p>TO METHOD</p>
<p>9 Within 14 days of</p>
<p>receipt of agreed</p>
<p>Meter</p>
<p>Reconciliation</p>
<p>Statement</p>
<p>Issue invoice for agreed payment adjustment Generator DNO As per PPA</p>
<p>10 Within 14 days of</p>
<p>receipt of invoice</p>
<p>Make payment Generator</p>
<p>or DNO</p>
<p>DNO or</p>
<p>Generator</p>
<p>BACS</p>
<p>Note 1: time of reading shall be taken from the radio clock or data collector associated with the meter being read</p>
<p>Note 2: 0.02% is the maximum error due to 1 Settlement Period in 3 months (i.e. this tolerance allows for the fact that meter readings will</p>
<p>not be taken precisely at the end of a Settlement Period).</p>
<p>This tolerance is in itself tighter than the relevant accuracy of the metering system (0.5%)</p>
<p>Distribution Code 1 May 2010</p>
<p>APPENDIX A</p>
<p>To: [Generator] SERIAL NO:</p>
<p>METER ADVANCE RECONCILIATION – NOTICE OF METER READING</p>
<p>Northern Ireland Electricity plc hereby notifies the undermentioned Generator that all Generation tariff meters at the undermentioned site</p>
<p>will be read for the purposes of meter advance reconciliation pursuant to paragraph 8.8 of the Main Code of the Northern Ireland</p>
<p>Distribution Code on the date and at the approximate time stated below. The person(s) attending on behalf of Northern Ireland Electricity</p>
<p>plc is/are indicated below.</p>
<p>Generator:</p>
<p>Site:</p>
<p>DNO Representative(s):</p>
<p>Date/Time</p>
<p>For DNO:</p>
<p>Signature: Name:</p>
<p>(in block capitals)</p>
<p>Position:</p>
<p>Date of Issue:</p>
<p>Distribution Code 1 May 2010</p>
<p>APPENDIX B</p>
<p>METER ADVANCE RECONCILIATION RECORD</p>
<p>SHEET: OF:</p>
<p>GENERATOR : READING DATE : (DD.MM.YY)</p>
<p>SITE NAME : READING TIME : (HH.MM)</p>
<p>METER ID : SERIAL NO :</p>
<p>FUNCTION MAIN METER REGISTER READING CHECK METER REGISTER</p>
<p>READING</p>
<p>MWh EXPORT</p>
<p>MWh IMPORT</p>
<p>MVAr EXPORT</p>
<p>MVAr IMPORT</p>
<p>DNO REPRESENTATIVE GENERATOR WITNESS</p>
<p>PRINT NAME</p>
<p>SIGNATURE</p>
<p>Distribution Code 1 May 2010</p>
<p>Distribution Metering Code Page 193</p>
<p>APPENDIX C</p>
<p>Example printout for Meter Register Comparison</p>
<p>21/04/89 14.20 Page 1</p>
<p>Meter Register Comparison for file EXAMPLE</p>
<p>Meter Name RTU</p>
<p>Name</p>
<p>MV Nr Reading Factor Identification</p>
<p>Meter Reg. Value Energy Difference</p>
<p>Reading</p>
<p>A/B</p>
<p>read acquired Abs %</p>
<p>METER_1 RTU_A 01 1 Meter 1</p>
<p>20/04/89 21/04/89</p>
<p>03:30 0:00</p>
<p>1551.78 2409.45 857.67 858.43 -0.76 0.088</p>
<p>METER_2 RTU_A 04 1 Meter 2</p>
<p>19/04/89 22/04/89</p>
<p>08:30 17:45</p>
<p>554.25 1245.76</p>
<p>3589.65 3809.02</p>
<p>1651.79 2569.45</p>
<p>857.67 857.67 1828.54 1829.01 0.47 0.025</p>
<p>Distribution Code 1 May 2010</p>
<p>Distribution Metering Code Page 194</p>
<p>APPENDIX D</p>
<p>METER ADVANCE RECONCILIATION STATEMENT</p>
<p>SITE NAME: READING DATE:</p>
<p>GENERATOR: SERIAL NO:</p>
<p>SETTLEMENT VALUE AFFECTED:</p>
<p>Difference Recorded</p>
<p>in Meter Register</p>
<p>Comparison Report MWh</p>
<p>Metering Point (as appropriate)</p>
<p>Generator Gross Meter</p>
<p>Generator Transformer Meter</p>
<p>Unit Transformer Meter</p>
<p>Station Transformer Meter</p>
<p>Net Settlement Value Adjustment</p>
<p>MWh</p>
<p>Associated primary transformer losses are ignored in establishing the Net Settlement</p>
<p>Value Adjustment</p>
<p>For DNO:</p>
<p>Signed: Name:</p>
<p>(in block capitals)</p>
<p>Position:</p>
<p>Date:</p>
<p>For Generator:</p>
<p>Signed: Name:</p>
<p>(in block capitals)</p>
<p>Position:</p>
<p>Date: AGREED/DISAGREED</p>
<p>(Delete as appropriate)</p>
<p>Distribution Code 1 May 2010</p>
<p>Distribution Metering Code Page 195</p>
<p>Agreed Procedure No. 4</p>
<p>VALIDATION, ESTIMATION AND SUBSTITUTION RULES</p>
<p>FOR HALF-HOURLY DATA</p>
<p>for the electricity industry in</p>
<p>Northern Ireland</p>
<p>Distribution Code 1 May 2010</p>
<p>Distribution Metering Code Page 196</p>
<p>AGREED PROCEDURE No. 4</p>
<p>VALIDATION, ESTIMATION AND SUBSTITUTION RULES FOR HALF-HOURLY</p>
<p>DATA</p>
<p>Contents</p>
<p>1 Introduction</p>
<p>2 Use of the Procedure</p>
<p>3 Validation of Meter Details</p>
<p>4 Meter ID/Serial Number</p>
<p>5 Meter Register and Pulse Multipliers</p>
<p>6 Meter Data Date and Time</p>
<p>7 Validation of Half hourly Metering Data</p>
<p>8 Meter ID</p>
<p>9 Meter Channel Details</p>
<p>10 Meter Time</p>
<p>11 Pulse Overflow</p>
<p>12 Excluded Intervals</p>
<p>13 Number Of Intervals</p>
<p>14 Cumulative/Total Consumption Comparison</p>
<p>15 Alarms</p>
<p>16 Zero Interval Tolerance</p>
<p>17 Data Estimation and Substitution</p>
<p>18 Check Meter</p>
<p>19 Up to Two Hour Gap in Data</p>
<p>20 Over Two Hour gap in Data</p>
<p>Distribution Code 1 May 2010</p>
<p>Distribution Metering Code Page 197</p>
<p>1 INTRODUCTION</p>
<p>1.1 This Agreed Procedure (the “Procedure”) describes the rules to be followed for both</p>
<p>data validation and data estimation for Generators with remotely read half-hourly</p>
<p>Metering.</p>
<p>1.2 The Procedure supplements the Main Code and the Sub-Codes of the Metering Code to</p>
<p>which reference should be made. In the event of an inconsistency between the</p>
<p>provisions of the Procedure and the Main Code or a Sub-Code the provisions of the</p>
<p>Main Code or such Sub-Code shall prevail. The provisions of the Main Code shall</p>
<p>prevail over the provisions of any Sub-Code.</p>
<p>1.3 The Procedure is part of the Grid Code and terms and expressions defined in the Grid</p>
<p>Code have the same meaning in the Procedure.</p>
<p>1.4 This Procedure applies to half hour metered Generators only. The meter advance</p>
<p>reconciliation procedures for Demand Customers are covered by Retail Market</p>
<p>Procedure MP NI 105.</p>
<p>2 USE OF THE PROCEDURE</p>
<p>2.1 The Procedure shall be used by the DNO and staff of those Generators who are metered</p>
<p>on a half-hourly basis who are responsible for meter advance reconciliation readings</p>
<p>and processing.</p>
<p>3 VALIDATION OF METER DETAILS</p>
<p>3.1 Prior to half-hourly data being accepted and approved for settlement purposes the Meter</p>
<p>details are validated. This occurs for new meter installations, meter changes, meters</p>
<p>that have been re-programmed or for existing meters moving to half-hourly profiling.</p>
<p>4 METER ID/SERIAL NUMBER</p>
<p>4.1 The Meter serial number registered to the Metering installation is verified against the</p>
<p>Meter id retrieved during Polling to ensure the correct meter has been polled.</p>
<p>5 METER REGISTER AND PULSE MULTIPLIERS</p>
<p>5.1 The meter Register Reading multiplier and the Pulse Multiplier are verified to ensure</p>
<p>data accuracy.</p>
<p>6 METER DATA DATE AND TIME</p>
<p>6.1 The date and time held by the meter and stamped on the data collected is checked to</p>
<p>ensure its accuracy.</p>
<p>7 VALIDATION OF HALF HOURLY METERING DATA</p>
<p>7.1 After polling each meter the half-hourly data retrieved from the meter is validated by</p>
<p>the data collection level and the following checks are performed.</p>
<p>Distribution Code 1 May 2010</p>
<p>Distribution Metering Code Page 198</p>
<p>8 METER ID</p>
<p>8.1 Each Time a meter is polled the Electronic Serial Number of that meter is compared to</p>
<p>the Device ID stored within the data collection level. If they do not match then no data</p>
<p>is retrieved and the Failure is reported by the data collection level for investigation.</p>
<p>9 METER CHANNEL DETAILS</p>
<p>9.1 Each time a meter is polled the number of channels of data expected is compared</p>
<p>against the number actually received. If they do not agree then no data is retrieved and</p>
<p>the failure is reported by the DNO Data Collection System for investigation.</p>
<p>10 METER TIME</p>
<p>10.1 Each time a meter is polled it’s time is checked to ensure it falls within two minutes of</p>
<p>the actual time. If the time is out by more than two minutes then the data is retrieved</p>
<p>and the time difference is investigated. The meter will be programmed with the correct</p>
<p>time.</p>
<p>11 PULSE OVERFLOW</p>
<p>11.1 Each channel status for each interval is checked for pulse Overflows. If a Pulse</p>
<p>Overflow is reported the data is marked for estimation and the cause is investigated and</p>
<p>resolved.</p>
<p>12 EXCLUDED INTERVALS</p>
<p>12.1 Each Channel status for each interval is checked for any interval data that may be</p>
<p>excluded. If Excluded intervals are reported then those intervals are marked for</p>
<p>estimation and the cause is investigated.</p>
<p>13 NUMBER OF INTERVALS</p>
<p>13.1 Each time a meter is polled the number of expected half-hour time intervals between</p>
<p>the start and stop times of the Load profile data is calculated and compared with the</p>
<p>actual number of time intervals found in the Load profile data file. Any difference in</p>
<p>the number of time intervals is investigated and resolved.</p>
<p>14 CUMULATIVE/TOTAL CONSUMPTION COMPARISON</p>
<p>14.1 When a meter is polled and it provides an electronic cumulative reading of the prime</p>
<p>register equivalent to the total consumption of the meter, then the difference between</p>
<p>successive cumulative readings is compared to the total of the meter period data for the</p>
<p>same period of time.</p>
<p>14.2 Specifically:</p>
<p>14.2.1 The sum of pulses * pulse multiplier for all the recording intervals collected is</p>
<p>compared to the meter advance * meter multiplier for the time interval.</p>
<p>Distribution Code 1 May 2010</p>
<p>Distribution Metering Code Page 199</p>
<p>14.2.2 If the difference between these values is greater than the meter register</p>
<p>multiplier then a secondary check is performed.</p>
<p>14.2.3 If the difference between actual reading and the calculated reading is more than</p>
<p>2 % then the problem is investigated and resolved.</p>
<p>15 ALARMS</p>
<p>15.1 When a meter is polled and significant meter alarms are flagged in the data file e.g.</p>
<p>long/short intervals etc. Each alarm is investigated.</p>
<p>16 ZERO INTERVAL TOLERANCE</p>
<p>16.1 If a Customer’s half hour data profile does not normally register any zero generation on</p>
<p>the KW Export channel then the total number of zero half hour data intervals retrieved</p>
<p>for the KW channel will be counted. If it exceeds 20 intervals then the data is flagged</p>
<p>for investigation.</p>
<p>17 DATA ESTIMATION AND SUBSTITUTION</p>
<p>17.1 Data estimation is required in situations where meter data is incomplete, has been</p>
<p>irretrievably lost or cannot be obtained within the timeframes required. Data</p>
<p>substitution is required where the data obtained is erroneous. Data will be</p>
<p>estimated/substituted when required using one of the following methods in the order</p>
<p>specified below:</p>
<p>18 CHECK METER</p>
<p>18.1 Where a check meter is installed and functional, data requiring estimation/substitution</p>
<p>will be taken directly from the check meter.</p>
<p>19 UP TO TWO HOUR GAP IN DATA</p>
<p>19.1 If the gap in data is 2 hours or less point –to-point linear interpolation will be used to</p>
<p>estimate/substitute the data. Intervals containing a power Outage are not used as end</p>
<p>points for interpolation:</p>
<p>19.1.1 If the data gap occurs in the middle of the data, the first point is the last valid</p>
<p>interval before the gap and the second point is the first valid interval after the</p>
<p>gap.</p>
<p>19.1.2 If the gap occurs at the beginning of the span the last interval from the historical</p>
<p>data is used as the first point if the historical data is available and valid.</p>
<p>Otherwise the second point (the first valid interval after the section) is used as</p>
<p>the first point – this will cause the Load to be estimated as a flat Load.</p>
<p>19.1.3 If the gap occurs at the end of the span the first point (the last valid interval</p>
<p>before the section) is used as the second point – this will cause the Load to be</p>
<p>estimated as a flat Load.</p>
<p>20 OVER TWO HOUR GAP IN DATA</p>
<p>Distribution Code 1 May 2010</p>
<p>Distribution Metering Code Page 200</p>
<p>20.1 If the gap in data is greater than 2 hours then the interval data is constructed using the</p>
<p>average Load shape based on the three most recent “similar” periods with valid data</p>
<p>(i.e. data that has not been estimated). A “similar” period means the same time period</p>
<p>of week and can be chosen from the previous 90 days. If the period needing estimation</p>
<p>is a holiday, then the “similar days” should be holidays rather than the same day of</p>
<p>week.</p>
<p>20.2 If adequate data is not available to perform this then one of the methods outlined below</p>
<p>will be employed in the order given.</p>
<p>20.2.1 Where actual meter readings are available an adjustment factor shall be</p>
<p>calculated and applied to the data to ensure that the total estimated consumption</p>
<p>is equal to the total actual consumption.</p>
<p>20.2.2 If only two “similar” periods are available within 90 days, the average is</p>
<p>calculated of these two. Similarly, if only one “similar” period is available the</p>
<p>data for this period is used for estimation.</p>
<p>20.2.3 If no “similar” periods are available in the previous 90 days, the three “like”</p>
<p>periods that are closest chronologically prior to the period requiring estimation</p>
<p>are used. A “like” period means a weekday or weekend/holiday.</p>
<p>20.2.4 If no “similar” periods are available and three “like” periods are not available</p>
<p>then the average of the two “like” periods that are closest chronologically prior</p>
<p>to the period requiring estimation is used.</p>
<p>20.2.5 If no “similar” periods are available and two “like” periods are not available</p>
<p>then the data for the “like” period that is closest chronologically prior to the</p>
<p>period requiring estimation is used.</p>
<p>20.2.6 If there is no historical data that can be used, the data should be estimated</p>
<p>manually and all assumptions documented fully.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 201</p>
<p>Glossary and Definitions</p>
<p>In the Distribution Code the following words and expressions shall, unless the subject matter</p>
<p>or the context otherwise requires or is inconsistent therewith, bear the following meanings:</p>
<p>Active Energy the electrical energy produced, flowing or supplied</p>
<p>by an electrical circuit during a time interval, being</p>
<p>the integral with respect to time of Active Power,</p>
<p>measured in units of watt-hours or standard multiples</p>
<p>thereof, that is:</p>
<p>1000 Wh = 1 kWh;</p>
<p>1000 kWh = 1 MWh;</p>
<p>1000 MWh = 1 GWh.</p>
<p>Active Power or MW The product of the components of alternating current</p>
<p>and voltage that equate to true power which is</p>
<p>measured in units of watts and standard multiples</p>
<p>thereof, for example:</p>
<p>1000 Watts = 1kW;</p>
<p>1000kW = 1MW;</p>
<p>1000MW = 1GW.</p>
<p>Aggregated Demand Site A group of Individual Demand Sites represented by</p>
<p>a Dispatchable Demand Customer, which together</p>
<p>are capable of a Demand Reduction Capability</p>
<p>equal to or above 4MW (and which is therefore</p>
<p>subject to Central Dispatch from the TSO). Each</p>
<p>Individual Demand Site comprising an Aggregated</p>
<p>Demand Site shall be in one currency zone. Unless</p>
<p>otherwise specified, information submitted in respect</p>
<p>of an Aggregated Demand Site shall always be at an</p>
<p>aggregated level.</p>
<p>Aggregated Generating Unit A group of Generating Units represented by a</p>
<p>Generator Aggregator, each of which must not have</p>
<p>a Registered Capacity greater than 10MW. An</p>
<p>Aggregated Generating Unit with a total Registered</p>
<p>Capacity of 4MW or more shall be subject to</p>
<p>Central Dispatch, but one with a total Registered</p>
<p>Capacity of less than 4MW may only be subject to</p>
<p>Central Dispatch subject to agreement with the</p>
<p>TSO.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 202</p>
<p>Aggregator Either a Generator Aggregator or a Dispatchable</p>
<p>Demand Customer in respect of an Aggregated</p>
<p>Demand Site.</p>
<p>Agreed Procedure Each of the agreed procedures which are specified in</p>
<p>paragraph 1.10 of the Main Code and set out in the</p>
<p>Distribution Metering Code.</p>
<p>Apparatus All equipment in which electrical conductors are</p>
<p>used, supported or of which they may form a part.</p>
<p>Authority The Northern Ireland Authority for Utility</p>
<p>Regulation.</p>
<p>Automatic Load Shedding A Load shedding scheme utilised by the TSO to</p>
<p>prevent Frequency collapse or other problems and to</p>
<p>restore the balance between generation output and</p>
<p>Demand on the Distribution System.</p>
<p>Automatic Load Shedding</p>
<p>Device</p>
<p>A device for initiating Load shedding automatically,</p>
<p>such as a Low Frequency Relay.</p>
<p>Black Start The procedure necessary for a recovery from a Total</p>
<p>Shutdown or Partial Shutdown.</p>
<p>Business Day Any day (other than a Saturday or a Sunday) on</p>
<p>which banks are open for business in Belfast but</p>
<p>excluding those days which the DNO may from time</p>
<p>to time notify Users as being days on which normal</p>
<p>business will not be conducted at the DNO’s</p>
<p>premises.</p>
<p>Central Dispatch The process of issuing an instruction in relation to</p>
<p>CDGUs, Aggregated Generating Units and/or</p>
<p>Interconnectors by the TSO pursuant to the Grid</p>
<p>Code. In particular:</p>
<p> All Dispatchable WFPSs shall be subject to</p>
<p>Central Dispatch;</p>
<p> All other Power Stations with a Registered</p>
<p>Capacity of above 10MW shall be subject to</p>
<p>Central Dispatch;</p>
<p> All other Power Stations with a Registered</p>
<p>Capacity of 10MW or less can agree with the</p>
<p>TSO to be subject to Central Dispatch.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 203</p>
<p>Centrally Dispatched</p>
<p>Generating Unit (CDGU)</p>
<p>A Generating Unit within a Power Station subject</p>
<p>to Central Dispatch.</p>
<p>Commissioning/Acceptance</p>
<p>Test</p>
<p>Testing of an item of User’s Equipment required</p>
<p>pursuant to the Connection Conditions prior to</p>
<p>connection or re-connection in order to determine</p>
<p>whether or not it is suitable for connection to the</p>
<p>System and the term “Commissioning/Acceptance</p>
<p>Testing” shall be construed accordingly.</p>
<p>Committed Project Planning</p>
<p>Data</p>
<p>Has the meaning set out in paragraph 8.3 of the</p>
<p>Planning Code.</p>
<p>Compensation Factors Loss adjustment factors.</p>
<p>Connected System Test Has the meaning set out in paragraph 1.1(b) of OC9.</p>
<p>Connection Agreement The bilateral agreement between the DNO and the</p>
<p>User, which contains the detail specific to the User’s</p>
<p>connection to the Distribution System.</p>
<p>Connection Conditions or CC The part of the Distribution Code which is identified</p>
<p>as the Connection Conditions.</p>
<p>Connection Point A point at which a User’s Plant and/or Apparatus</p>
<p>connects to the Distribution System.</p>
<p>Connection Site A site containing a Connection Point.</p>
<p>Control Person The term used as an alternative to “Safety Coordinator”</p>
<p>on the Site Responsibility Schedule</p>
<p>only.</p>
<p>Controllable WFPS A WFPS first connected to the Distribution System</p>
<p>on or after 1 April 2005 whose wind turbines</p>
<p>comprise a Registered Capacity of 5MW or more.</p>
<p>Data Protection Legislation The Data Protection Act 1998 implementing</p>
<p>Directive 95/46/EC on the protection of individuals</p>
<p>with regard to the Processing of Personal Data and</p>
<p>including all regulations and codes of practice</p>
<p>applicable to those persons subject to the</p>
<p>Distribution Metering Code in relation to matters</p>
<p>the subject of the Distribution Metering Code.</p>
<p>Demand Customer Voltage</p>
<p>Reduction</p>
<p>A 3 or 6 per cent reduction of voltage supplied to all</p>
<p>or any group of Demand Customers on a particular</p>
<p>part of the Distribution System.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 204</p>
<p>Demand The amount of electrical power consumed</p>
<p>comprising of Active and Reactive Power unless</p>
<p>otherwise stated.</p>
<p>Demand Control As defined in paragraph 1.5 in OC3.</p>
<p>Demand Customer A person to whom electrical Energy is provided by</p>
<p>means of a direct connection to the Distribution</p>
<p>System.</p>
<p>Demand Reduction Capability The reduction capability in MW Demand that can be</p>
<p>achieved by the Demand Side Unit.</p>
<p>Demand Side Unit A Demand Site or Aggregated Demand Site with a</p>
<p>Demand Reduction Capability of at least 4MW.</p>
<p>The Demand Side Unit shall be subject to Central</p>
<p>Dispatch.</p>
<p>Department The Department of Enterprise, Trade and Industry.</p>
<p>Detailed Planning Data Data specified in Part 2 of the Appendix to the</p>
<p>Planning Code.</p>
<p>Development A modification relating to a User’s Plant and/or</p>
<p>Apparatus already connected to the Distribution</p>
<p>System.</p>
<p>Disconnect The act of physically separating Users (and Demand</p>
<p>Customers) equipment from the Distribution</p>
<p>System, and the terms “Disconnection” and</p>
<p>“Disconnecting” shall be construed accordingly.</p>
<p>Dispatchable Demand</p>
<p>Customer</p>
<p>A person who operates a Demand Side Unit, with a</p>
<p>Demand Reduction Capability not less than 4MW.</p>
<p>Dispatchable WFPS A Controllable WFPS which is dispatched via an</p>
<p>Electronic Interface by the TSO.</p>
<p>Distribution Code The document named as such, prepared pursuant to</p>
<p>condition 27 of the Licence held by the DNO.</p>
<p>Distribution Code Review Panel</p>
<p>(Panel)</p>
<p>The panel whose functions are set out in paragraph 6</p>
<p>of the General Conditions.</p>
<p>Distribution Metering Code That part of the Distribution Code identified as the</p>
<p>Distribution Metering Code comprising the Main</p>
<p>Code, each Sub-Code and each Agreed Procedure.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 205</p>
<p>Distribution Service Centre A location used for the control and operation of the</p>
<p>Distribution System.</p>
<p>Distribution System The electric lines within the Authorised Area, as</p>
<p>defined in the Licence held by the DNO, owned by</p>
<p>the Distribution Licensee (but not, for the avoidance</p>
<p>of doubt, any lines forming part of the transmission</p>
<p>system or any Interconnector), and any other</p>
<p>electric lines which the Authority may specify as</p>
<p>forming part of the distribution system, together with</p>
<p>(in each case) any Plant and Apparatus and/or</p>
<p>meters owned or operated by the DNO used in</p>
<p>connection with the distribution of electricity.</p>
<p>DNO or Distribution Network</p>
<p>Owner</p>
<p>Northern Ireland Electricity plc acting in its capacity</p>
<p>as the owner of the Distribution System.</p>
<p>DNO Data Collection System The data collection system (sometimes referred to as</p>
<p>an &#8220;instation&#8221;) operated by the DNO to supply</p>
<p>Settlement Values to the Market Operator (as such</p>
<p>term is defined in the Trading and Settlement</p>
<p>Code) for use in calculating payments due, inter alia,</p>
<p>to Generators and from Suppliers (currently</p>
<p>comprising a central computer together with</p>
<p>datalinks to and from it connecting to System Data</p>
<p>Collectors), or such other data collection system as</p>
<p>the DNO may reasonably specify to be used for such</p>
<p>purpose with the prior agreement of the Authority</p>
<p>and after consultation with all Generators and those</p>
<p>other Users which are, in the reasonable opinion of</p>
<p>the DNO, interested in any such system. For the</p>
<p>avoidance of doubt, the System Data Collectors, the</p>
<p>Generator data collectors and the accounting</p>
<p>software known as the contract management system</p>
<p>are not part of the Data Collection System.</p>
<p>DNO Site A site owned (or occupied pursuant to a lease,</p>
<p>licence or other agreement) by the DNO in which</p>
<p>there is a Connection Point. For the avoidance of</p>
<p>doubt a site owned by a User but occupied by the</p>
<p>DNO as aforesaid, is a DNO Site.</p>
<p>Earthing A way of providing a connection between conductors</p>
<p>and earth by an Earthing Device.</p>
<p>Earthing Device A means of providing a connection between a</p>
<p>conductor and earth being of adequate strength and</p>
<p>capability.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 206</p>
<p>Electronic Interface A system, in accordance with the requirements of the</p>
<p>TSO’s data system providing an electronic interface</p>
<p>between the TSO and a User, for issuing and</p>
<p>receiving instructions, including Dispatch</p>
<p>Instructions, as provided for in the Grid Code and</p>
<p>established pursuant to an agreement between the</p>
<p>TSO and the User.</p>
<p>Emergency Manual</p>
<p>Disconnection</p>
<p>Load shedding carried out at short notice or no notice</p>
<p>when a Regulating Margin cannot otherwise be</p>
<p>achieved.</p>
<p>Energy The electrical energy produced, flowing or supplied</p>
<p>by an electrical circuit during a time interval and</p>
<p>being the integral with respect to time of the</p>
<p>instantaneous power, measured in units of Watthours</p>
<p>or standard multiples thereof, for example:-</p>
<p>1000Wh = 1kWh;</p>
<p>1000kWh = 1MWh;</p>
<p>1000MWh = 1GWh.</p>
<p>Event An unscheduled or unplanned (although it may have</p>
<p>been anticipated) occurrence on a System or on the</p>
<p>Transmission System including, without limiting</p>
<p>that general description, faults, incidents and</p>
<p>breakdowns.</p>
<p>Export In respect of any User, a flow of electricity from the</p>
<p>Apparatus of such User to the Apparatus of</p>
<p>another User and the verb “export” and its respective</p>
<p>tenses shall be construed accordingly.</p>
<p>Final Connection Report Has the meaning set out in paragraph 11.5.1 of the</p>
<p>Connection Conditions.</p>
<p>Final Report Has the meaning set out in paragraph 2.2(d) in OC9.</p>
<p>Finish Date The date on which an Outage is to finish.</p>
<p>Frequency The number of alternating current cycles per second</p>
<p>(expressed in Hertz) at which a System is running.</p>
<p>Fuel Security Code The Northern Ireland Fuel Security Code designated</p>
<p>by the Department as a condition of Licences</p>
<p>granted under Article 10 of the Order.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 207</p>
<p>General Conditions The part of the Distribution Code which is identified</p>
<p>as the General Conditions.</p>
<p>Generating Plant A Power Station subject to Central Dispatch</p>
<p>Generating Unit Other than in the case of Wind Farm Power</p>
<p>Stations, a generator together with all Plant and</p>
<p>Apparatus which relate exclusively to the operation</p>
<p>of that generator. In the case of Wind Farm Power</p>
<p>Stations, a wind turbine generator within a Wind</p>
<p>Farm Power Station, together with all Plant and</p>
<p>Apparatus (including any step-up transformer)</p>
<p>which relates exclusively to the operation of that</p>
<p>wind turbine generator.</p>
<p>Generator A person who generates electricity under a Licence</p>
<p>or exemption under the Order and who is subject to</p>
<p>the Distribution Code either by virtue of a Licence</p>
<p>or exemption or pursuant to any agreement with the</p>
<p>DNO or otherwise.</p>
<p>Generator Aggregator A person who represents several Generating Units,</p>
<p>each of which does not have a Registered Capacity</p>
<p>greater than 10MW and the combined Registered</p>
<p>Capacity of which is equal to or greater than 4MW</p>
<p>in relation to those Generating Units and receiving</p>
<p>Dispatch Instructions in relation to those</p>
<p>Generating Units from the TSO under the Grid</p>
<p>Code. For the avoidance of doubt, a Generator</p>
<p>Aggregator cannot aggregate a Generating Unit</p>
<p>with an output equal to or above 10MW.</p>
<p>Generator data collector A data collector available to transmit data directly to</p>
<p>the relevant Generator.</p>
<p>Generator Metering Circuits Current and voltage transformers in a Power Station</p>
<p>and their associated secondary circuits which feed</p>
<p>Metering and which may be owned by either the</p>
<p>Generator or the DNO.</p>
<p>Generator Terminal The terminals of a Generating Unit.</p>
<p>Generator Transformer The main transformer for a Generating Unit through</p>
<p>which that power passes from the Generator</p>
<p>Terminals to the Distribution System.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 208</p>
<p>Grid Code The Grid Code prepared pursuant to the TSO’s</p>
<p>Licence, as from time to time revised in accordance</p>
<p>with the TSO’s Licence.</p>
<p>Grid Code Metering Code That part of the Grid Code identified as the Grid</p>
<p>Code Metering Code.</p>
<p>High Voltage or HV A voltage exceeding 650 volts.</p>
<p>HV Apparatus High Voltage electrical circuits forming part of a</p>
<p>System.</p>
<p>Implementing Safety Coordinator</p>
<p>Has the meaning set out in paragraph 6.4 in OC6.</p>
<p>Import In respect of any User, a flow of electricity to the</p>
<p>Apparatus of such User from the Apparatus of</p>
<p>another User and the verb “import” and its</p>
<p>respective tenses shall be construed accordingly.</p>
<p>Independent Engineer The person appointed pursuant to paragraph 11.2 of</p>
<p>the Main Code in the Distribution Metering Code.</p>
<p>Independent Generating Plant A Power Station which is not subject to Central</p>
<p>Dispatch and is not a Controllable WFPS.</p>
<p>Induction Generating Unit A Generating Unit in which some or all of the</p>
<p>excitation is derived from the Distribution System</p>
<p>rather than being separately supplied as magnetic or</p>
<p>electrical energy.</p>
<p>Interconnector Electric lines and electric Plant used for conveying</p>
<p>electricity from outside both of Northern Ireland and</p>
<p>the Republic of Ireland directly to or from a</p>
<p>substation or converter station in either Northern</p>
<p>Ireland or the Republic of Ireland.</p>
<p>Interested User As defined in the Metering Code.</p>
<p>Inter-jurisdictional Tie Line The lines, facilities and equipment that connect the</p>
<p>transmission system of the Republic of Ireland to the</p>
<p>transmission system of Northern Ireland.</p>
<p>Intertripping A method of tripping a circuit breaker on receipt of a</p>
<p>signal initiated from protection at another location.</p>
<p>Investigation An investigation carried out by the DNO pursuant to</p>
<p>OC10 in relation to User Sites.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 209</p>
<p>Invitee As defined in paragraph 10.1 of the Main Code.</p>
<p>Isolating Device A device for the purpose of rendering Plant and HV</p>
<p>Apparatus either Isolated or disabled so that</p>
<p>electrical energy cannot pass from the Apparatus</p>
<p>(or, in the case of Plant, from the associated</p>
<p>Apparatus) to the HV Apparatus.</p>
<p>Isolation The disconnection of HV Apparatus from the</p>
<p>remainder of the System in which that HV</p>
<p>Apparatus is situated by means either of an</p>
<p>Isolating Device(s) in the isolating position or</p>
<p>adequate physical separation or sufficient gap or the</p>
<p>disablement (by means of switching or dismantling)</p>
<p>of Plant and/or Apparatus so that electrical energy</p>
<p>cannot pass from the Apparatus (or, in the case of</p>
<p>Plant, from the associated Apparatus) to the HV</p>
<p>Apparatus, other than by an Isolating Device and</p>
<p>“Isolated” shall be construed accordingly.</p>
<p>Licence A licence granted under the Order.</p>
<p>Licence Standards The document designated as such by the Authority</p>
<p>on or before SEM Go-Live, as modified from time to</p>
<p>time in accordance with Condition 19 of the Licence</p>
<p>held by the DNO.</p>
<p>Load The Active Power or Reactive Power, as the context</p>
<p>requires, generated, transmitted or distributed and all</p>
<p>like terms shall be construed accordingly.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 210</p>
<p>Local Safety Instructions Instructions relating to each DNO Site and each User</p>
<p>Site approved by the relevant DNO or User in</p>
<p>accordance with OC6.4.1, setting down the methods</p>
<p>of achieving the objectives of the DNO’s or the</p>
<p>User’s (as the case may be) Safety Rules to ensure</p>
<p>the safety of personnel carrying out work or testing</p>
<p>on Plant and/or Apparatus to which his Safety</p>
<p>Rules apply and in the case of a User, any other</p>
<p>document(s) on a User Site which contains rules with</p>
<p>regard to maintaining or securing the isolating</p>
<p>position of an Isolating Device, or maintaining a</p>
<p>physical separation or sufficient gap, or the</p>
<p>disablement (by means of switching or dismantling)</p>
<p>of Plant and/or Apparatus so that electrical energy</p>
<p>cannot pass from the Apparatus (or, in the case of</p>
<p>Plant, from the associated Apparatus) to the HV</p>
<p>Apparatus, other than by an Isolating Device or</p>
<p>maintaining or securing the position of an Earthing</p>
<p>Device.</p>
<p>Location The electrical location on a System.</p>
<p>Low Frequency Relay An electrical measuring relay intended to operate</p>
<p>when its characteristic quantity (Frequency) reaches</p>
<p>the relay settings by decrease in Frequency.</p>
<p>Low Voltage or LV A voltage not exceeding 250 volts.</p>
<p>Main Code The part of the Distribution Metering Code entitled</p>
<p>the &#8220;Main Code&#8221;.</p>
<p>Market Operator Shall have the meaning set out in the TSC.</p>
<p>Market Registration Code or</p>
<p>MRC</p>
<p>The code of that name drawn up by the DNO as</p>
<p>amended or restated from time to time.</p>
<p>Medium Voltage or MV A voltage exceeding 250 volts but not exceeding 650</p>
<p>volts.</p>
<p>Meter Advance Reconciliation The process for reconciliation of meter readings with</p>
<p>record produced in accordance with Agreed</p>
<p>Procedure 3 of the Distribution Metering Code</p>
<p>and/or the statement produced in accordance with</p>
<p>Agreed Procedure 3.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 211</p>
<p>Meter Advance Reconciliation</p>
<p>Record</p>
<p>The record produced in accordance with Agreed</p>
<p>Procedure 3 of the Distribution Metering Code in</p>
<p>the form set out in Appendix B to Agreed Procedure</p>
<p>3.</p>
<p>Meter Reconciliation Statement A statement prepared by the DNO and submitted to</p>
<p>each Generator.</p>
<p>Meter Responsible Person As defined in paragraph 5 of the Distribution</p>
<p>Metering Code.</p>
<p>Metering Means Tariff Metering.</p>
<p>Metering System Means a meter and any associated voltage</p>
<p>transformers, current transformers and secondary</p>
<p>circuits.</p>
<p>Minimum Generation The minimum MW Output which a Generating</p>
<p>Unit can generate continuously, registered with the</p>
<p>DNO.</p>
<p>Minister The Minister for Enterprise, Trade and Investment.</p>
<p>Monitoring Monitoring carried out by the DNO pursuant to</p>
<p>OC10.</p>
<p>Monitoring Notice A notice issued by the DNO to a User pursuant to</p>
<p>paragraph 4.3 in OC10, informing the User that the</p>
<p>DNO is Monitoring its User Equipment.</p>
<p>NI Demand The Demand on the NI System less the output of</p>
<p>Independent Generating Plant.</p>
<p>NI System Together, the Transmission System and the</p>
<p>Distribution System.</p>
<p>Operating Code or OC That part of the Distribution Code which is</p>
<p>identified as the Operating Code.</p>
<p>Operation A scheduled or planned action relating to the</p>
<p>operation of a System and the Transmission System</p>
<p>but, for the avoidance of doubt, does not include</p>
<p>fault locating operations undertaken by the DNO.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 212</p>
<p>Operational Effect Any effect on the operation of the relevant System or</p>
<p>on the Transmission System which will or may</p>
<p>cause the Systems of the DNO or a User, as the case</p>
<p>may be, to operate differently from the way in which</p>
<p>they would or may have operated in the absence of</p>
<p>that effect.</p>
<p>Operational Procedures Management instructions and procedures, both in</p>
<p>support of the Safety Rules and for the local and</p>
<p>remote operation of Plant and/or Apparatus at or</p>
<p>from a Connection Site.</p>
<p>Order The Electricity (Northern Ireland) Order 1992.</p>
<p>Other Authority The Commission for Energy Regulation in the</p>
<p>Republic of Ireland.</p>
<p>Other Transmission System The transmission system operated by the Other TSO</p>
<p>in the Republic of Ireland.</p>
<p>Other Transmission System</p>
<p>Operator (Other TSO)</p>
<p>The holder of a licence granted pursuant to Section</p>
<p>14 of the Electricity Regulation Act 1999 in the</p>
<p>Republic of Ireland to operate a Transmission</p>
<p>System.</p>
<p>Outage In relation to a Generating Unit, a total or partial</p>
<p>reduction in Output in connection with the repair or</p>
<p>maintenance of the Generating Unit or any</p>
<p>associated Power Station Equipment, or resulting</p>
<p>from a breakdown or failure of the Generating Unit</p>
<p>or any associated Power Station Equipment. In</p>
<p>relation to a Demand Customer’s Connection Site,</p>
<p>a total or partial reduction in Demand in connection</p>
<p>with the repair or maintenance of the Demand</p>
<p>Customer’s Connection Site or any associated</p>
<p>equipment or resulting from a breakdown or failure</p>
<p>of the Demand Customer’s Connection Site or any</p>
<p>associated equipment. In relation to the DNO, the</p>
<p>removal from service for repair, maintenance, safety</p>
<p>or other reason any part of the Distribution System.</p>
<p>Output The actual Active Power output in MW of a</p>
<p>Generating Unit as at the Connection Point derived</p>
<p>from data measured pursuant to the Metering Code.</p>
<p>Overall Accuracy The accuracy of any Metering as affected by its</p>
<p>current and voltage transformers and Generator</p>
<p>Metering Circuits.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 213</p>
<p>Ownership Diagram A diagram created pursuant to paragraph 9.1.4 in the</p>
<p>Connection Conditions and prepared following the</p>
<p>principles set out in Appendix 2 to the Connection</p>
<p>Conditions.</p>
<p>Partial Shutdown The same as a Total Shutdown except that all</p>
<p>generation has ceased in a separate part of the Total</p>
<p>System and there is no electricity supply across any</p>
<p>Interconnector or Inter-jurisdictional Tie Line or</p>
<p>other parts of the Total System to that part of the</p>
<p>Total System and, therefore, that part of the Total</p>
<p>System is shutdown, with the result that it is not</p>
<p>possible for that part of the Total System to begin to</p>
<p>function again without the TSO’s directions relating</p>
<p>to a Black Start.</p>
<p>Personal Data The personal data (as defined in the Data Protection</p>
<p>Act 1998) that is collected or processed under the</p>
<p>Distribution Metering Code.</p>
<p>Planned Manual Disconnection Load shedding carried out when it is known in</p>
<p>advance that a Regulating Margin cannot otherwise</p>
<p>be achieved.</p>
<p>Planning Code or PC That part of the Distribution Code which is</p>
<p>identified as the Planning Code.</p>
<p>Plant Fixed and movable items other than Apparatus.</p>
<p>Power Station An installation comprising one or more Generating</p>
<p>Units (even where sited separately) owned and/or</p>
<p>controlled by the same Generator, which may</p>
<p>reasonably be considered as being managed as one</p>
<p>Power Station or, as the case may be, one Wind</p>
<p>Farm Power Station.</p>
<p>Power Station Equipment Items of Plant in a Power Station which are integral</p>
<p>to the operation of a CDGU, Controllable WFPS</p>
<p>and/or Dispatchable WFPS but which are not used</p>
<p>exclusively in the operation of such CDGU,</p>
<p>Controllable WFPS and/or Dispatchable WFPS,</p>
<p>the Outage of which will, or is likely to (when, for</p>
<p>example, taken together with other Power Station</p>
<p>Equipment Outages), reduce the level of</p>
<p>Availability of a CDGU, Controllable WFPS and/or</p>
<p>Dispatchable WFPS.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 214</p>
<p>Pre-energisation Connection</p>
<p>Report</p>
<p>Has the meanings set out in paragraphs 11.3.2 and</p>
<p>11.6.1 in the Connection Conditions.</p>
<p>Preliminary Notice Has the meaning ascribed to it in paragraph 1.2 in</p>
<p>the Appendix to OC9.</p>
<p>Preliminary Project Planning</p>
<p>Data</p>
<p>Has the meaning set out in paragraph 8.2 in the</p>
<p>Planning Code.</p>
<p>Process/Processing Has the meaning given to &#8220;process&#8221; and &#8220;processing&#8221;</p>
<p>under the Data Protection Act 1998.</p>
<p>Proposal Notice Has the meaning ascribed to it in paragraph 4.1 of</p>
<p>OC9.</p>
<p>Protected Demand Customer A Demand Customer in relation to whom, in</p>
<p>accordance with guidelines issued by the</p>
<p>Department, Planned Manual Disconnection shall,</p>
<p>so far as possible, not be exercised.</p>
<p>Protection Equipment for detecting abnormal conditions on a</p>
<p>System and initiating fault clearance and activating</p>
<p>alarms and indications.</p>
<p>Prudent Operating Practice In relation to a User or the TSO, the standard of</p>
<p>practice attained by exercising that degree of skill,</p>
<p>diligence, prudence and foresight which could</p>
<p>reasonably be expected from a skilled and</p>
<p>experienced operator engaged in the same type of</p>
<p>undertaking under the same or similar circumstances.</p>
<p>Reactive Energy The integral with respect to time of the Reactive</p>
<p>Power measured in units of volt-ampere-hours</p>
<p>reactive or standard multiples thereof, that is:</p>
<p>1000 VArh = 1 kVArh;</p>
<p>1000 kVArh = 1 MVArh.</p>
<p>Reactive Power or MVAr The product of voltage and current and the sine of</p>
<p>the phase angle between them measured in units of</p>
<p>volt-amperes reactive and standard multiples thereof,</p>
<p>i.e.:</p>
<p>1000 VAr = 1 kVAr</p>
<p>1000 kVAr = 1 MVAr</p>
<p>Record of Inter-System Safety</p>
<p>Precautions or RISSP</p>
<p>The procedures set out in paragraph 7 of OC6.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 215</p>
<p>Registered Capacity The normal full Load capacity of a Generating Unit</p>
<p>in MW measured as at the Connection Point and in</p>
<p>relation to a Wind Farm Power Station, the normal</p>
<p>full Load capacity of the collection of one or more</p>
<p>wind turbines, each being a Generating Unit, in</p>
<p>MW measured as at the Connection Point of the</p>
<p>Wind Farm Power Station.</p>
<p>Registered Project Planning</p>
<p>Data</p>
<p>Has the meaning set out in paragraph 8.4 of the</p>
<p>Planning Code.</p>
<p>Regulating Margin The margin of generating capacity that is</p>
<p>Synchronised over Demand which is required in</p>
<p>order to maintain Frequency control.</p>
<p>Relevant Connection Site a site which includes a Connection Point of a Power</p>
<p>Station or Demand Customer to the Distribution</p>
<p>System.</p>
<p>Requesting Safety Co-ordinator Has the meaning set out in paragraph 6.4 of OC6.</p>
<p>Responsible Engineer/Operator A person nominated by a User to be responsible for</p>
<p>control of the User’s System.</p>
<p>Responsible Manager A manager who has been duly authorised by a User</p>
<p>or the TSO to sign Site Responsibility Schedules on</p>
<p>behalf of that User or the TSO, as the case may be.</p>
<p>Re-Synchronisation The act of achieving the state where the Frequencies</p>
<p>and phase relationships of parts of the Total System</p>
<p>are identical.</p>
<p>Retail Market Procedure (MP) Each of the retail market procedures forming part of</p>
<p>the Market Registration Code.</p>
<p>RISSP-A and RISSP-B Have the meanings set out in paragraph 7.2 of OC6.</p>
<p>Rota Load Shedding Planned Disconnection of Demand Customers on a</p>
<p>rota basis during circumstances when there is a</p>
<p>significant shortfall of generation required to meet</p>
<p>the total Demand for a protracted period.</p>
<p>Safety Co-ordinator Has the meaning set out in paragraph 6 of OC6.</p>
<p>Safety From The System That condition which safeguards persons working or</p>
<p>testing HV Apparatus from the dangers which are</p>
<p>inherent in working on items of HV Apparatus.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 216</p>
<p>Safety Precautions Has the meaning set out in paragraph 8.1 of OC6.</p>
<p>Safety Rules The rules and procedures (as amended or restated</p>
<p>from time to time) of the DNO or a User to ensure</p>
<p>Safety From The System.</p>
<p>Schedule Day The period from 0000 hours until 2400 hours on the</p>
<p>same day.</p>
<p>Secretary of State The Secretary of State for the Department of Energy</p>
<p>and Climate Change</p>
<p>Settlement Period Has the meaning given to that term in the TSC.</p>
<p>Settlement Values Values of Active Energy and Reactive Energy</p>
<p>delivered over a Settlement Period as recorded by</p>
<p>Metering required by and operating in accordance</p>
<p>with this Distribution Metering Code or as</p>
<p>estimated or substituted in accordance with this</p>
<p>Distribution Metering Code. Settlement Values are</p>
<p>identified by the time at the end of the relevant</p>
<p>Settlement Period.</p>
<p>Significant Incident Has the meaning set out in paragraph 4.3.3 of OC4.</p>
<p>Single Electricity Market</p>
<p>(SEM)</p>
<p>The wholesale all-island single electricity market</p>
<p>established and governed pursuant to the relevant</p>
<p>legislation and the TSC.</p>
<p>Site A User Site or a DNO Site, as the case may be.</p>
<p>Site Responsibility Schedule A schedule prepared by the DNO and a User and</p>
<p>signed by both parties detailing the division of</p>
<p>responsibilities at Connection Sites towards the</p>
<p>ownership, control, operation and maintenance of</p>
<p>Plant and Apparatus and the safety of personnel at</p>
<p>the Connection Site. The format, principles and</p>
<p>basic procedure to be used in the preparation of Site</p>
<p>Responsibility Schedules are set down in Appendix</p>
<p>1 to the Connection Conditions.</p>
<p>Standard Planning Data Data specified in Appendix A in the Planning Code.</p>
<p>Start Date The date on which an Outage is to begin.</p>
<p>Statement on Distribution</p>
<p>System Capacity</p>
<p>The statement of that name prepared pursuant to</p>
<p>condition 32 of the Licence held by the DNO.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 217</p>
<p>Substation An assemblage of equipment including any necessary</p>
<p>housing for the conversion, transformation or control</p>
<p>of electrical power.</p>
<p>Sub-Code Each of the Sub-Codes referred to in the Main Code</p>
<p>and set out in the Distribution Metering Code.</p>
<p>Supplier The holder of a Licence to supply electricity</p>
<p>pursuant to Article 10(1)(c) of the Order.</p>
<p>Synchronised The condition where an incoming Generating Unit</p>
<p>or System is connected to another System so that the</p>
<p>Frequencies and phase relationships of that</p>
<p>Generating Unit or System, as the case may be, and</p>
<p>the System to which it is connected are identical and</p>
<p>all like terms shall be construed accordingly.</p>
<p>Synchronous Generating Unit A Generating Unit which is connected and</p>
<p>Synchronised to the Distribution System.</p>
<p>System Any User System and/or the Distribution System as</p>
<p>the case may be.</p>
<p>System Data Collector A data collector (sometimes referred to as an</p>
<p>&#8220;outstation&#8221;) owned by the DNO for transmitting</p>
<p>data to the DNO Data Collection System for the</p>
<p>purpose of providing Settlement Values.</p>
<p>System Test Has the meaning set out in paragraph 1.1 of OC9.</p>
<p>Tariff Metering Meters, associated current and voltage transformers,</p>
<p>metering protection equipment including alarms,</p>
<p>electrical circuitry, their associated data collectors</p>
<p>(including Generator data collectors) and wiring and</p>
<p>other devices or any part thereof which are part of</p>
<p>the Active Energy or Reactive Energy measuring</p>
<p>equipment at or relating to a Relevant Connection</p>
<p>Site.</p>
<p>Test Co-ordinator Has the meaning set out in paragraph 1.1 in the</p>
<p>Appendix to OC9.</p>
<p>Test Panel A panel, whose composition is detailed in the</p>
<p>Appendix to OC10, which is responsible for various</p>
<p>matters including considering a proposed System</p>
<p>Test and preparing a Test Programme.</p>
<p>Test Programme Has the meaning set out in paragraph 4.4 of OC9.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 218</p>
<p>Test Proposer Has the meaning set out in paragraph 4.1.4 of OC9.</p>
<p>Testing Testing carried out by the DNO pursuant to OC10 of</p>
<p>Users&#8217; Equipment and the term &#8220;Test&#8221; shall be</p>
<p>construed accordingly.</p>
<p>Thermal Plant A Generating Unit that uses any source of thermal</p>
<p>Energy.</p>
<p>Total Shutdown The situation existing when all generation has ceased</p>
<p>and there is no electricity supply across any</p>
<p>Interconnector and, therefore, the Total System has</p>
<p>shutdown with the result that it is not possible for the</p>
<p>Total System to begin to function again without the</p>
<p>TSO&#8217;s directions relating to a Black Start.</p>
<p>Total System Together, the NI System and all User Systems in</p>
<p>Northern Ireland.</p>
<p>Trading and Settlement Code</p>
<p>or TSC</p>
<p>The Single Electricity Market Trading and</p>
<p>Settlement Code adopted by the Market Operator</p>
<p>and approved by the by the Authority and the Other</p>
<p>Authority.</p>
<p>Transmission Interface</p>
<p>Agreement</p>
<p>The agreement of the same name entered into by the</p>
<p>Transmission Owner and the TSO.</p>
<p>Transmission Owner Northern Ireland Electricity plc in its capacity as the</p>
<p>owner of the Transmission System.</p>
<p>Transmission System The System consisting (wholly or mainly) of high</p>
<p>voltage electric lines and cables operated by the TSO</p>
<p>for the purposes of transmission of electricity from</p>
<p>one Power Station to a Substation or to another</p>
<p>Power Station or between sub-stations or to or from</p>
<p>any Interconnector including any Plant and</p>
<p>Apparatus and meters owned or operated by the</p>
<p>TSO or Transmission Owner in connection with the</p>
<p>transmission of electricity.</p>
<p>TSO (Transmission System</p>
<p>Operator)</p>
<p>The holder of the Licence granted pursuant to Article</p>
<p>10(1)(b) of the Order to operate a Transmission</p>
<p>System.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 219</p>
<p>TSO Data Collection System The data collection system (sometimes referred to as</p>
<p>an &#8220;instation&#8221;) operated by the TSO to supply</p>
<p>Settlement Values to the Market Operator (as such</p>
<p>term is defined in the Trading and Settlement</p>
<p>Code) for use in calculating payments due, inter alia,</p>
<p>to Generators and from Suppliers (currently</p>
<p>comprising a central computer together with</p>
<p>datalinks to and from it connecting to System Data</p>
<p>Collectors), or such other data collection system as</p>
<p>the TSO may reasonably specify to be used for such</p>
<p>purpose with the prior agreement of the Authority</p>
<p>and after consultation with all Generators and those</p>
<p>other Users which are, in the reasonable opinion of</p>
<p>the TSO, interested in any such system. For the</p>
<p>avoidance of doubt, the System Data Collectors, the</p>
<p>Generator data collectors and the accounting</p>
<p>software known as the contract management system</p>
<p>are not part of the Data Collection System.</p>
<p>TSO Licence The licence to carry out electricity transmission</p>
<p>activities granted pursuant to Article 10(1)(b) of the</p>
<p>Order.</p>
<p>User A term utilised in each section of the Distribution</p>
<p>Code specifying the persons (other than the DNO)</p>
<p>bound by that section. In the General Conditions the</p>
<p>term means all Users referred to in the individual</p>
<p>sections of the Distribution Code.</p>
<p>User Site A site owned (or occupied pursuant to a Lease,</p>
<p>licence or other agreement) by a User (which in the</p>
<p>case of an Aggregator, means the combination of the</p>
<p>individual Aggregated Generating Unit or</p>
<p>Aggregated Demand Side Unit sites as the case may</p>
<p>be) in which there is a Connection Point. For the</p>
<p>avoidance of doubt, a site owned by DNO but</p>
<p>occupied by a User as aforesaid, is a User Site.</p>
<p>User System Any system owned or operated by a User comprising</p>
<p>Generating Units together with Plant and/or</p>
<p>Apparatus connecting Generating Units and/or</p>
<p>Large Demand Customers&#8217; equipment to the</p>
<p>Distribution System.</p>
<p>User’s Equipment The Plant and/or Apparatus owned and/or operated</p>
<p>by a User.</p>
<p>VAr A single unit of Reactive Power.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 220</p>
<p>Voltage Control The retention of the voltage on the System within</p>
<p>acceptable limits.</p>
<p>Wind Farm Power Station or</p>
<p>WFPS</p>
<p>A collection of one or more wind turbines owned</p>
<p>and/or operated by the same Generator and joined</p>
<p>together by a System with a single Connection</p>
<p>Point.</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 221</p>
<p>GD2. CONSTRUCTION OF REFERENCES</p>
<p>In the Distribution Code:</p>
<p>(i) the table of contents is inserted for convenience only and shall be ignored in construing</p>
<p>the Distribution Code;</p>
<p>(ii) unless the context otherwise requires, all references to a particular paragraph,</p>
<p>subparagraph, Appendix or Schedule shall be a reference to that paragraph, subparagraph</p>
<p>Appendix or Schedule in or to that part of the Distribution Code in which</p>
<p>the reference is made;</p>
<p>(iii) unless the context otherwise requires, the singular shall include the plural and vice</p>
<p>versa, references to any gender shall include all other genders and references to persons</p>
<p>shall include any individual, body corporate, corporation, joint venture, trust,</p>
<p>unincorporated association, organisation, firm or partnership and any other entity, in</p>
<p>each case whether or not having a separate legal personality;</p>
<p>(iv) references to the words &#8220;include&#8221; or &#8220;including&#8221; are to be construed without limitation</p>
<p>to the generality of the preceding words;</p>
<p>(v) unless there is something in the subject matter or the context which is inconsistent</p>
<p>therewith, any reference to an Order in Council or an Act of Parliament or any section</p>
<p>of or schedule to, or other provision of an Order in Council or an Act of Parliament</p>
<p>shall be construed at the particular time, as including a reference to any modification,</p>
<p>extension or re-enactment thereof then in force and to all instruments, orders and</p>
<p>regulations then in force and made or deriving from the relevant Order in Council or</p>
<p>Act of Parliament;</p>
<p>(vi) references to &#8220;in writing&#8221; or &#8220;written&#8221; include typewriting, printing, lithography and</p>
<p>other modes of reproducing words in a legible and non-transitory form;</p>
<p>(vii) where the Glossary and Definitions refers to any word or term which is more</p>
<p>particularly defined in a part of the Distribution Code, the definition of that part of the</p>
<p>Distribution Code will prevail over the definition in the Glossary &amp; Definitions in the</p>
<p>event of any inconsistency;</p>
<p>(viii) a cross-reference to another document or part of the Distribution Code shall not of</p>
<p>itself impose any additional or further or co-existent obligation or confer any additional</p>
<p>or further or co-existent right in the part of the text where such cross-reference is</p>
<p>contained;</p>
<p>(ix) nothing in the Distribution Code is intended to or shall derogate from the DNO’s</p>
<p>statutory or licence obligations;</p>
<p>(x) a &#8220;holding company&#8221; means, in relation to any person, a holding company of such</p>
<p>person within the meaning of Section 736, 736A and 736B of the Companies Act 1985</p>
<p>as substituted by Section 144 of the Companies Act 1989;</p>
<p>Distribution Code 1 May 2010</p>
<p>Glossary and Definitions Page 222</p>
<p>(xi) a &#8220;subsidiary&#8221; means, in relation to any person, a subsidiary of such person within the</p>
<p>meaning of Section 736, 736A and 736B of the Companies Act 1985 as substituted by</p>
<p>Section 144 of the Companies Act 1989; and</p>
<p>(xii) references to time are to Belfast time.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2012/02/21/grid-code-2010/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Leasing Payment Amount</title>
		<link>http://www.windni.com/2012/01/15/leasing-payment-amount/</link>
		<comments>http://www.windni.com/2012/01/15/leasing-payment-amount/#comments</comments>
		<pubDate>Sun, 15 Jan 2012 10:13:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Developments]]></category>

		<guid isPermaLink="false">http://www.windni.com/?p=1597</guid>
		<description><![CDATA[There are only certain amounts of rent that can be paid for a wind power project and most companies are currently offering approximately the same amount. This figure is usually determined by the size of the project.  The reason the rental amount being offered ...]<br /><a href="http://www.windni.com/2012/01/15/leasing-payment-amount/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<p>There are only certain amounts of rent that can be paid for a wind power project and most companies are currently offering approximately the same amount. This figure is usually determined by the size of the project.  The reason the rental amount being offered by most reputable companies is similar is because they have identified the appropriate rental amount that will allow the project to be financially viable.  If an offer or &#8216;guarantee&#8217; from an individual or company sounds too good to be true then it usually is. After asking a series of questions you will often find that there is no substance behind such offers.</p>
<p>In order to avoid a situation like this it is essential to find out the following before beginning the conversation of what the rental income is likely to be:</p>
<p><strong>1.</strong> How long has the company been going for?  Is it a company or an individual?  Does the company have a healthy trading history?  Are they well known in the Wind Sector?  Are they using advanced wind monitoring? (this ensures project investment and project success!)</p>
<p><strong>2.</strong> What turbines is the developer proposing?  Are they currently available to purchase?  Is there long term historical information on the turbines and their faults?  Are the turbines insurable?</p>
<p><strong>3.</strong> Will the turbine manufacturer/provider guarantee the availability of the turbine?  Will they provide local engineers as well as local spares in Northern Ireland?  How will they be monitored?  What is the response time to a fault?  Who will be providing the operation and maintenance?  How experienced are they in this sector?</p>
<p><strong>4. </strong>Will the developer be able to actually develop the project?  Do they have the experience?  Do they have the finance in place?</p>
<p>All the above may seem more like the developers problem but it is very much in the Landowner&#8217;s interest to know the answers to these questions.</p>
<p>&nbsp;</p>
<p>Since our company was formed in 2007 (long before 4 x ROCs were introduced), Wind NI has been dedicated to helping landowners diversify their income streams by using wind power.</p>
<p>We are locally based, in Larne, Co. Antrim and have a long term vision for our company as opposed to a ‘sell-on’ strategy.  All our packages are not only very generous but also sensible, realistic and most importantly, achievable.</p>
<p>Wind NI&#8217;s O&amp;M division have over 15 years’ experience commissioning, operating and maintaining turbines around the world for clients such as Vestas, Nissan, Airtricty, Scottish Power.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2012/01/15/leasing-payment-amount/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Energy Minister Arlene Foster today welcomed the completion of a significant research project into Northern Ireland’s geological potential for the underground storage of energy.</title>
		<link>http://www.windni.com/2011/12/21/energy-minister-arlene-foster-today-welcomed-the-completion-of-a-significant-research-project-into-northern-irelands-geological-potential-for-the-underground-storage-of-energy/</link>
		<comments>http://www.windni.com/2011/12/21/energy-minister-arlene-foster-today-welcomed-the-completion-of-a-significant-research-project-into-northern-irelands-geological-potential-for-the-underground-storage-of-energy/#comments</comments>
		<pubDate>Wed, 21 Dec 2011 11:01:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[NI News]]></category>

		<guid isPermaLink="false">http://www.windni.com/?p=1698</guid>
		<description><![CDATA[The Energy Storage Study investigated Northern Ireland’s suitability for safe underground energy storage, including compressed air, carbon dioxide capture and natural gas. In particular, it focused on County Antrim and the adjacent off-shore Irish Sea areas, as there are unique ...]<br /><a href="http://www.windni.com/2011/12/21/energy-minister-arlene-foster-today-welcomed-the-completion-of-a-significant-research-project-into-northern-irelands-geological-potential-for-the-underground-storage-of-energy/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<p>The Energy Storage Study investigated Northern Ireland’s suitability for safe underground energy storage, including compressed air, carbon dioxide capture and natural gas. In particular, it focused on County Antrim and the adjacent off-shore Irish Sea areas, as there are unique thick beds of underground salt that could be suitable for the development of storage facilities.</p>
<p>The study will prove an invaluable resource for companies interested in the development of underground energy storage facilities.</p>
<p>Arlene Foster said: “The results of the Energy Storage Study will help planning for the development of safe underground energy storage facilities in Northern Ireland. Potential investors, who are interested in the development of gas storage facilities, compressed air storage, or the storage of carbon dioxide will now be able to use the data to make informed decisions.</p>
<p>The Minister concluded: “The development of energy storage facilities would contribute significantly towards meeting some of the aims of the Department’s Strategic Energy Framework. I therefore hope that the results will encourage private sector development of underground energy storage projects suitable for strategic requirements both now and in the future. The research will also be of interest to the renewables sector for possible offshore renewable energy projects.”</p>
<p>The Energy Storage Study was carried out by the Department of Enterprise, Trade and Investment in co-operation with the Geological Survey of Northern Ireland (GSNI) and the British Geological Survey (BGS).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2011/12/21/energy-minister-arlene-foster-today-welcomed-the-completion-of-a-significant-research-project-into-northern-irelands-geological-potential-for-the-underground-storage-of-energy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Energy Minister Arlene Foster today welcomed the announcement by The Crown Estate of two parallel Leasing Rounds for offshore wind and tidal stream development as new sources of renewable energy for Northern Ireland.</title>
		<link>http://www.windni.com/2011/12/16/energy-minister-arlene-foster-today-welcomed-the-announcement-by-the-crown-estate-of-two-parallel-leasing-rounds-for-offshore-wind-and-tidal-stream-development-as-new-sources-of-renewable-energy-for-n/</link>
		<comments>http://www.windni.com/2011/12/16/energy-minister-arlene-foster-today-welcomed-the-announcement-by-the-crown-estate-of-two-parallel-leasing-rounds-for-offshore-wind-and-tidal-stream-development-as-new-sources-of-renewable-energy-for-n/#comments</comments>
		<pubDate>Fri, 16 Dec 2011 20:01:30 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[NI News]]></category>

		<guid isPermaLink="false">http://www.windni.com/?p=1699</guid>
		<description><![CDATA[The Crown Estate is seeking expressions of interest from private sector developers for offshore wind and tidal stream Leasing Rounds in Northern Ireland waters. An Offshore Wind Area off the east coast to deliver up to 600MW of generating capacity ...]<br /><a href="http://www.windni.com/2011/12/16/energy-minister-arlene-foster-today-welcomed-the-announcement-by-the-crown-estate-of-two-parallel-leasing-rounds-for-offshore-wind-and-tidal-stream-development-as-new-sources-of-renewable-energy-for-n/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<p>The Crown Estate is seeking expressions of interest from private sector developers for offshore wind and tidal stream Leasing Rounds in Northern Ireland waters. An Offshore Wind Area off the east coast to deliver up to 600MW of generating capacity and a Tidal stream area off the north east coast around Rathlin of up to 200MW.</p>
<p>Arlene Foster said<strong>: </strong>“Today’s announcement by The Crown Estate opens up new Leasing Rounds in Northern Ireland waters. This marks a major step forward in the growth of our offshore renewable energy industry. This follows on from discussions with the sector to identify the best way to release our offshore resources to optimise market interest and secure sustainable renewable and economic benefits for Northern Ireland.</p>
<p>“Over the last six months there has been a high level of activity to address a number of key issues identified in our offshore plans to facilitate the Leasing Rounds. In this regard, I welcome the recent signing of a Memorandum of Understanding between the United Kingdom and Irish Government which provides clarity in relation to offshore renewable energy marine jurisdictional issues. The seas around the coast of Northern Ireland and the Republic of Ireland offer not just a significant renewable resource but also significant economic benefits which we are both keen to capture.”</p>
<p>Rob Hastings, The Crown Estate’s Marine Director said: “Our discussions with industry have highlighted demand for the leasing rounds, which represent another major step forward for the UK’s already world-leading offshore renewables industry. The energy infrastructure projects to be delivered will not only reap significant economic benefits for Northern Ireland, but will also further diversify the energy supply away from industrial sources to low carbon renewable energy .”</p>
<p>This next stage involves the issue of a pre-qualification questionnaire leading to invitations to tender. Tenders would then be assessed in early 2012 with development rights being granted to successful companies from as early as summer 2012.</p>
<p>The Minister concluded:<strong> </strong>“I see offshore renewables making a key contribution to our future energy mix to meet the Executive’s challenging 40% renewable electricity target by 2020.</p>
<p>“The interest to date in Northern Ireland waters is very encouraging and this announcement today presents the offshore wind and tidal stream sectors with an excellent opportunity. Northern Ireland offers a strong but accessible offshore resource, world class research facilities at our Universities, a strong engineering tradition and an excellent port infrastructure.</p>
<p>&#8220;The development of offshore renewable energy provides not only greater energy security and diversity but significant economic and employment benefits. The recent announcement by DONG Energy at Belfast Harbour confirms that Northern Ireland has what it takes for offshore renewable energy development.”</p>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2011/12/16/energy-minister-arlene-foster-today-welcomed-the-announcement-by-the-crown-estate-of-two-parallel-leasing-rounds-for-offshore-wind-and-tidal-stream-development-as-new-sources-of-renewable-energy-for-n/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wind Speed Measurement: Anemometers</title>
		<link>http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/</link>
		<comments>http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/#comments</comments>
		<pubDate>Sat, 03 Dec 2011 22:20:40 +0000</pubDate>
		<dc:creator>jonny</dc:creator>
				<category><![CDATA[Wind Monitoring]]></category>

		<guid isPermaLink="false">http://pilot.windni.com/?p=648</guid>
		<description><![CDATA[The measurement of wind speeds is usually done using a cup anemometer, such as the one in the picture to the left. The cup anemometer has a vertical axis and three cups which capture the wind. The number of revolutions ...]<br /><a href="http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<div>
<p>The measurement of wind speeds is usually done using a cup anemometer, such as the one in the picture to the left. The cup anemometer has a vertical axis and three cups which capture the wind. The number of revolutions per minute is registered electronically. Normally, the anemometer is fitted with a wind vane to detect the wind direction.</p>
<p>Other anemometer types include ultrasonic or laser anemometers which detect the phase shifting of sound or coherent light reflected from the air molecules. Hot wire anemometers detect the wind speed through minute temperature differences between wires placed in the wind and in the wind shade (the lee side).</p>
<p>The advantage of non-mechanical anemometers may be that they are less sensitive to icing. In practice, however, cup anemometers tend to be used everywhere, and special models with electrically heated shafts and cups may be used in arctic areas.  Quality Anemometers are a Necessity for Wind Energy Measurement  You often get what you pay for, when you buy something. That also applies to anemometers. You can buy surprisingly cheap anemometers from some of the major vendors in the business. They may be OK for meteorology, and they are OK to mount on a wind turbine, where a large accuracy is not really important. *) But cheap anemometers are not usable for wind speed measurement in the wind energy industry, since they may be very inaccurate and calibrated poorly, with measurement errors of maybe 5 per cent or even 10 per cent.</p>
<p>If you are planning to build a wind farm it may be an economic disaster if you have an anemometer which measures wind speeds with a 10% error. In that case, you may risk counting on an energy content of the wind which is 1.1 3 &#8211; 1 = 33% higher than than it is in reality. If you have to recalculate your measurements to a different wind turbine hub height (say, from 10 to 50 m height), you may even multiply that error with a factor of 1.3, thus you end up with a 75% error on your energy calculation.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wind Speed Measurement: Anemometers</title>
		<link>http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/</link>
		<comments>http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/#comments</comments>
		<pubDate>Sat, 03 Dec 2011 22:20:40 +0000</pubDate>
		<dc:creator>jonny</dc:creator>
				<category><![CDATA[Wind Monitoring]]></category>

		<guid isPermaLink="false">http://pilot.windni.com/?p=648</guid>
		<description><![CDATA[The measurement of wind speeds is usually done using a cup anemometer, such as the one in the picture to the left. The cup anemometer has a vertical axis and three cups which capture the wind. The number of revolutions ...]<br /><a href="http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<div>
<p>The measurement of wind speeds is usually done using a cup anemometer, such as the one in the picture to the left. The cup anemometer has a vertical axis and three cups which capture the wind. The number of revolutions per minute is registered electronically. Normally, the anemometer is fitted with a wind vane to detect the wind direction.</p>
<p>Other anemometer types include ultrasonic or laser anemometers which detect the phase shifting of sound or coherent light reflected from the air molecules. Hot wire anemometers detect the wind speed through minute temperature differences between wires placed in the wind and in the wind shade (the lee side).</p>
<p>The advantage of non-mechanical anemometers may be that they are less sensitive to icing. In practice, however, cup anemometers tend to be used everywhere, and special models with electrically heated shafts and cups may be used in arctic areas.  Quality Anemometers are a Necessity for Wind Energy Measurement  You often get what you pay for, when you buy something. That also applies to anemometers. You can buy surprisingly cheap anemometers from some of the major vendors in the business. They may be OK for meteorology, and they are OK to mount on a wind turbine, where a large accuracy is not really important. *) But cheap anemometers are not usable for wind speed measurement in the wind energy industry, since they may be very inaccurate and calibrated poorly, with measurement errors of maybe 5 per cent or even 10 per cent.</p>
<p>If you are planning to build a wind farm it may be an economic disaster if you have an anemometer which measures wind speeds with a 10% error. In that case, you may risk counting on an energy content of the wind which is 1.1 3 &#8211; 1 = 33% higher than than it is in reality. If you have to recalculate your measurements to a different wind turbine hub height (say, from 10 to 50 m height), you may even multiply that error with a factor of 1.3, thus you end up with a 75% error on your energy calculation.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wind Speed Measurement: Anemometers</title>
		<link>http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/</link>
		<comments>http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/#comments</comments>
		<pubDate>Sat, 03 Dec 2011 22:20:40 +0000</pubDate>
		<dc:creator>jonny</dc:creator>
				<category><![CDATA[Wind Monitoring]]></category>

		<guid isPermaLink="false">http://pilot.windni.com/?p=648</guid>
		<description><![CDATA[The measurement of wind speeds is usually done using a cup anemometer, such as the one in the picture to the left. The cup anemometer has a vertical axis and three cups which capture the wind. The number of revolutions ...]<br /><a href="http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<div>
<p>The measurement of wind speeds is usually done using a cup anemometer, such as the one in the picture to the left. The cup anemometer has a vertical axis and three cups which capture the wind. The number of revolutions per minute is registered electronically. Normally, the anemometer is fitted with a wind vane to detect the wind direction.</p>
<p>Other anemometer types include ultrasonic or laser anemometers which detect the phase shifting of sound or coherent light reflected from the air molecules. Hot wire anemometers detect the wind speed through minute temperature differences between wires placed in the wind and in the wind shade (the lee side).</p>
<p>The advantage of non-mechanical anemometers may be that they are less sensitive to icing. In practice, however, cup anemometers tend to be used everywhere, and special models with electrically heated shafts and cups may be used in arctic areas.  Quality Anemometers are a Necessity for Wind Energy Measurement  You often get what you pay for, when you buy something. That also applies to anemometers. You can buy surprisingly cheap anemometers from some of the major vendors in the business. They may be OK for meteorology, and they are OK to mount on a wind turbine, where a large accuracy is not really important. *) But cheap anemometers are not usable for wind speed measurement in the wind energy industry, since they may be very inaccurate and calibrated poorly, with measurement errors of maybe 5 per cent or even 10 per cent.</p>
<p>If you are planning to build a wind farm it may be an economic disaster if you have an anemometer which measures wind speeds with a 10% error. In that case, you may risk counting on an energy content of the wind which is 1.1 3 &#8211; 1 = 33% higher than than it is in reality. If you have to recalculate your measurements to a different wind turbine hub height (say, from 10 to 50 m height), you may even multiply that error with a factor of 1.3, thus you end up with a 75% error on your energy calculation.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2011/12/03/wind-speed-measurement-anemometers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Instrumentation</title>
		<link>http://www.windni.com/2011/12/03/instrumentation/</link>
		<comments>http://www.windni.com/2011/12/03/instrumentation/#comments</comments>
		<pubDate>Sat, 03 Dec 2011 21:55:28 +0000</pubDate>
		<dc:creator>jonny</dc:creator>
				<category><![CDATA[Wind Monitoring]]></category>

		<guid isPermaLink="false">http://pilot.windni.com/?p=643</guid>
		<description><![CDATA[Sensors: A crucial factor for precise measuring is the correct choice of sensors. For wind measurement, only anemometers according to IEC 61400 – recommended: category - should be used. The anemometers must be calibrated by a specialised institute in accordance with ...]<br /><a href="http://www.windni.com/2011/12/03/instrumentation/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<p><strong>Sensors:</strong></p>
<p>A crucial factor for precise measuring is the correct choice of sensors. For wind measurement, only anemometers according to IEC 61400 – recommended: category - should be used. The anemometers must be calibrated by a specialised institute in accordance with national and international standards and regulations (MEASNET)</p>
<p>If the client is relying upon data generated by an insufficient or incorrectly-installed wind measurement system, this could lead to big miscalculations and builds up the risk of economically non-viable operation of the planned investment. Small deviations could be caused simply by the use of non-calibrated anemometers</p>
<p>Anemometer producers guarantee a certain accuracy for their products, for example ± 0.3 to 0.5 m/s (or 3 to 5 % for speeds above 15 m/s). The measurements usually remain well within this tolerance range and this is sufficient for all needs in weather forecast and in industrial processes. For a reliable prognosis in wind energy, this tolerance is not acceptable. When using a non-calibrated anemometer, it is necessary to reckon with a reduced accuracy for the predictions. This is a risk and we recommend using only anemometers which are individually calibrated.</p>
<p>The anemometer should be calibrated by a specialised institute in accordance with national and international standards and regulations, which should also provide an official certificate of compliance (ISO 3966 1977, IEA-guidelines, uniform measuring process of the MEASNET-Group). The members of the MEASNET Group (<a href="http://www.measnet.com/" target="_blank">www.measnet.com</a>) are independent, international institutes which have specialised on applications in the field of wind energy. The development of standard measuring processes and the continuous flow of experience and information makes sure that the calibration of anemometers will be handled according to the strictest guidelines.</p>
<p>The results of each anemometer calibration are presented in a calibration report, which describes precisely which aspects of the performance of the anemometer have been measured. In addition, the measurement equipment should be described in each report, including the reference tools and their last check-up.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2011/12/03/instrumentation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Instrumentation</title>
		<link>http://www.windni.com/2011/12/03/instrumentation/</link>
		<comments>http://www.windni.com/2011/12/03/instrumentation/#comments</comments>
		<pubDate>Sat, 03 Dec 2011 21:55:28 +0000</pubDate>
		<dc:creator>jonny</dc:creator>
				<category><![CDATA[Wind Monitoring]]></category>

		<guid isPermaLink="false">http://pilot.windni.com/?p=643</guid>
		<description><![CDATA[Sensors: A crucial factor for precise measuring is the correct choice of sensors. For wind measurement, only anemometers according to IEC 61400 – recommended: category - should be used. The anemometers must be calibrated by a specialised institute in accordance with ...]<br /><a href="http://www.windni.com/2011/12/03/instrumentation/">Read Full Story &#187;</a>]]></description>
			<content:encoded><![CDATA[<p><strong>Sensors:</strong></p>
<p>A crucial factor for precise measuring is the correct choice of sensors. For wind measurement, only anemometers according to IEC 61400 – recommended: category - should be used. The anemometers must be calibrated by a specialised institute in accordance with national and international standards and regulations (MEASNET)</p>
<p>If the client is relying upon data generated by an insufficient or incorrectly-installed wind measurement system, this could lead to big miscalculations and builds up the risk of economically non-viable operation of the planned investment. Small deviations could be caused simply by the use of non-calibrated anemometers</p>
<p>Anemometer producers guarantee a certain accuracy for their products, for example ± 0.3 to 0.5 m/s (or 3 to 5 % for speeds above 15 m/s). The measurements usually remain well within this tolerance range and this is sufficient for all needs in weather forecast and in industrial processes. For a reliable prognosis in wind energy, this tolerance is not acceptable. When using a non-calibrated anemometer, it is necessary to reckon with a reduced accuracy for the predictions. This is a risk and we recommend using only anemometers which are individually calibrated.</p>
<p>The anemometer should be calibrated by a specialised institute in accordance with national and international standards and regulations, which should also provide an official certificate of compliance (ISO 3966 1977, IEA-guidelines, uniform measuring process of the MEASNET-Group). The members of the MEASNET Group (<a href="http://www.measnet.com/" target="_blank">www.measnet.com</a>) are independent, international institutes which have specialised on applications in the field of wind energy. The development of standard measuring processes and the continuous flow of experience and information makes sure that the calibration of anemometers will be handled according to the strictest guidelines.</p>
<p>The results of each anemometer calibration are presented in a calibration report, which describes precisely which aspects of the performance of the anemometer have been measured. In addition, the measurement equipment should be described in each report, including the reference tools and their last check-up.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.windni.com/2011/12/03/instrumentation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

