STCP 04-1 Issue 005 Real Time Data Change Management

Similar documents
STCP 04-3 Issue 005 Real Time Data Provision

STCP14-3 Issue 003 Customer Charging Enquiries

STCP Amendment Proposal Form

STCP 18-3 Issue 006 TEC Changes

STCP22-1 Issue 003 Production of Models for GB System Planning

STCP19-3 Issue 006 Operational Notification & Compliance Testing

GC0102 Mod Title: EU Connection Codes GB Implementation Mod 3

Balancing and Settlement Code BSC PROCEDURE

Offshore BMU Configuration

SOUTH TEXAS ELECTRIC COOPERATIVE, INC.

IMS INTERFACE MARKET PROCEDURE NETWORK OPERATORS AND AEMO

MONITORING AND CONTROL REQUIREMENTS FOR DISTRIBUTED GENERATION FACILITIES

IMS INTERFACE MARKET PROCEDURE NETWORK OPERATORS AND AEMO

CAISO RIG Acceptance Test Procedure

Distributed Generation Requirements Update

Description of the Application Process for Small Embedded Generators

An Introduction to the Operational Notification and Compliance Process Including Timescales for New Generation Connections

MESP TECHNICAL SPECIFICATION FOR A RECTIFIER UNIT CONTROL & PROTECTION SYSTEM FOR USE IN THE 1500V DC TRACTION SYSTEM

POWER SYSTEM OPERATION PROCEDURE: NETWORK MODELLING DATA

ANCILLARY SERVICES BUSINESS MONITORING

UK LINK MANUAL CODE COMMUNICATIONS REFERENCE DOCUMENT. June Version 1 For Approval

CONFIRMATION OF VERIFICATION EVIDENCE REPORT (COVER) [Distribution Connected Generation (DCG)]

Company Directive STANDARD TECHNIQUE: TP14J. Management of Metering CT & VT Test Certificates

FREQUENCY RESPONSE MONITORING (ANCILLARY SERVICES BUSINESS MONITORING)

Guidance: Operational Conditions Precedent (OCPs) September 2016 Version 1

Chapter 5A Embedded Generation Information Pack United Energy s guide to the Embedded Generation connection process for of Chapter 5A

Specification Voltage Limiting Device

POWER SYSTEM DATA COMMUNICATION STANDARD

Joint Office of Gas Transporters xxxx: <Introduction of a Discretionary Release Mechanism for Non-Obligated Annual NTS Exit (Flat) Capacity>

GC0106: Mod Title: Data exchange requirements in accordance with Regulation (EU) 2017/1485 (SOGL)

A Guide to EDT, EDL and CT with National Grid. A Guide to EDT, EDL and CT with National Grid

Recording and Reporting of High Voltage and Low Voltage Switching

European Aviation Safety Agency

0522: Governance of the use of as a valid UNC communication

TRANSMISSION ENGINEERING STANDARDS SUBSTATIONS

THE CONNECTION AND USE OF SYSTEM CODE TEMPORARY TEC EXCHANGE RATE REQUEST FORM

Relevant Electrical Standards (RES) Grid Code Review Panel January 2014

SIN 462 Issue 1.4 August 2016

SHORT TERM OPERATING RESERVE E-TENDER GUIDANCE DOCUMENT

California Independent System Operator Corporation Fifth Replacement Electronic Tariff

Revision 6.0. Transmission Interconnection Guide

APPROVAL PROCESS TO BE FOLLOWED FOR PROVISIONAL ACCREDITATION OF CBs UNDER FM CERTIFICATION SCHEME

EDS SCADA NUMBERING SYSTEM

0522: Governance of the use of as a valid UNC communication

Memorandum. This memorandum requires Board action. EXECUTIVE SUMMARY

Appendix I: LOAD OPERATING AGREEMENT

ECP SECONDARY SUBSTATION COMMISSIONING PROCEDURE

Smart Meters Programme Schedule 6.3. (Development Process) (CSP North version)

DOCUMENTATION AND QUALITY ASSURANCE

Code Administration Code of Practice

Generation, Transmission, and End User Facilities

OPENREACH WHOLESALE EXTENSION SERVICE 622 (WES622) AND WHOLESALE END TO END EXTENSION SERVICE 622 (WEES622) Service & Interface Description

Revised Generation Interconnection Impact Study Report. For. Queue Position 31 ( Interconnection Customer )

REAL-TIME MONITORING DATA SPECIFICATION

Test Agreement Test Description: Satellite Multicast For Education Technical Trial

Annual Industry Consultation

G8 - Contracts for Difference Metering

Supervisory Control and Data Acquisition (SCADA) Performance Criteria Transmission Maintenance Procedure No. 6

CASE STUDY. Wind Farm in Mexico Completes First Successful IEC Application With Multivendor Interoperability

CALIFORNIA INDEPENDENT SYSTEM OPERATOR CORPORATION FERC ELECTRIC TARIFF FIRST REPLACEMENT VOLUME NO. II Original Sheet No. 727 METERING PROTOCOL

CHARTER TOWNSHIP OF ALLENDALE, OTTAWA COUNTY, MICHIGAN WIRELESS COMMUNICATION FACILITIES APPLICATION

SPI PowerNet requirements for the non-contestable Interface Works at Deer Park Terminal Station

Dumfries and Galloway Developer Forum. Welcome and Introduction. Gareth Hislop

Use of Synthetic Data in Live Environments

SMUD Model Data Requirements & Reporting Procedures MOD VERSION 1.2

CALIFORNIA INDEPENDENT SYSTEM OPERATOR CORPORATION FERC ELECTRIC TARIFF ORIGINAL VOLUME NO. III Original Sheet No. 977 METERING PROTOCOL

SIN 459 Issue 1.6 August 2016

Robin Hood Energy Feed-In Tariff Application Form

Reliability Coordinator Procedure

A regulatory framework for Number Portability in Gibraltar. A Statement by the Gibraltar Regulatory Authority

Severn Trent Water. Telecommunications Policy and Access Procedure

Disturbance Monitoring and

Business Requirements Specification for the. Nomination and Matching Procedures. In Gas Transmission Systems (NOM BRS)

April 2010 Power Systems division A brief introduction. ABB Group August 25, 2011 Slide 1

Smart Metering Implementation Programme. Consultation on transitional arrangements in the Smart Energy Code

Chapter 2 State Estimation and Visualization

BSCP128 Production, Submission, Audit and Approval of Line Loss Factors Version 3.0. Balancing and Settlement Code. BSC Procedure DRAFT

INTERNATIONAL STANDARD

METERING COMPETITION EMBEDDED NETWORKS METER REPLACEMENT PROCESSES PROCEDURE CONSULTATION PARTICIPANT RESPONSE PACK

Data Subject Access Request

European Network Codes: RfG GB Grid Code Application Options

Network Services BT MPLS (Marketed as IP Connect Global)

BSCP128 Production, Submission, Audit and Approval of Line Loss Factors Version 3.0. Balancing and Settlement Code. BSC Procedure DRAFT

Updating MACS documentation

Flexible Connections for DG Customers

Robin Hood Energy Feed-in Tariff Application Form

Workgroup Terms of Reference and Membership

Established Leaders in Actuation Technology. In-Vision PC based supervisory control. Publication S210E issue 04/03

New Zealand Telecommunications Forum. Code for Vulnerable End Users of Telecommunication Services. ( Vulnerable End User Code )

ATTACHMENT I: Generator Interconnection Procedures (GIP)

Open Access Transmission Tariff of Southern Companies

Governance of the use of as a valid UNC communication

Guidance Document. UNC Modification Proposals Guidance for Proposers

AUTHORITY FOR ELECTRICITY REGULATION

"PPS" is Private Practice Software as developed and produced by Rushcliff Ltd.

Document C0. Use for:

CALIFORNIA INDEPENDENT SYSTEM OPERATOR CORPORATION FERC ELECTRIC TARIFF FIRST REPLACEMENT VOLUME NO. II Original Sheet No. 727 METERING PROTOCOL

Castle View Primary School Data Protection Policy

Switching Process and Rules Systems Operations Framework. Document Number:

SERVICE SCHEDULE & ADDITIONAL TERMS AND CONDITIONS FOR DIRECT WHOLESALE INTERCONNECT VOICE SERVICE

Transcription:

STCP 04-1 Issue 005 Real Time Data Change Management STC Procedure Document Authorisation Party Name of Party Representative Signature Date National Grid Electricity Transmission plc SP Transmission plc Scottish Hydro Electric Transmission plc Offshore Transmission Owners STC Procedure Change Control History Issue 001 21/12/2004 BETTA Go-Live Version Issue 002 20/04/2005 Issue 002 incorporating STCPAP004 Issue 003 25/10/2005 Issue 003 incorporating PA034 & PA037 Issue 004 14/01/2011 Issue 004 incorporating changes for Offshore Transmission Issue 005 26/02/2014 Issue 005 incorporating PM075 Page 1 of 10

1 Introduction 1.1 Scope 1.1.1 It is essential that all changes to real time data that involve modification to SCADA databases or displays are reported to, and co-ordinated with any affected Party. Affected Parties must be notified of changes in sufficient time to permit discussions to manage change effectively. 1.1.2 This document applies to NGET and the TO for real time data changes brought about by events such as: new Plant and/or Apparatus connected to the National Electricity Transmission System; Plant and/or Apparatus reconnected to the National Electricity Transmission System; Plant and/or Apparatus disconnected from the National Electricity Transmission System; changes to Protection Apparatus or control equipment; changes to numbering or nomenclature of existing Plant and/or Apparatus; temporary changes made to the National Electricity Transmission System; emergency changes to the National Electricity Transmission System; User s System changes; and any other changes that require modification to the NGET and TO SCADA database displays. 1.1.3 This procedure applies to NGET and each TO. 1.1.4 For the purposes of this document, TOs are: SPT; SHE-T and All Offshore Transmission Licence holders as appointed by OFGEM In the event that specific conditions or exceptions are made in the document relating to an Onshore TO or Offshore TO these will be prefixed appropriately 1.1.5 At NGET sites that connect with TO sites, certain real time data is provided to the TO via local Data Transmission equipment that is owned and maintained by the TO. Any changes that may affect this data are subject to the provisions of this document. 1.1.6 TO - TO data change management is outside the scope of this document. It is anticipated that a similar procedure shall be followed. 1.1.7 The procedure for the management of NGET TO Datalinks is detailed in STCP 4-2 (Real Time Datalink Management) and is outside the scope of this document. 1.2 Objectives 1.2.1 This document specifies the requirements and responsibilities placed on NGET and TOs for ensuring that changes to real time data and displays are captured and made available to the other affected Parties in good time. Page 2 of 10

1.3 General Provisions 1.3.1 The change management process for SCADA data shall apply during the Commissioning and De-commissioning process (see STCP 19-4 Commissioning / Decommissioning) and shall also apply to changes to equipment outside the scope of the Commissioning and De-commissioning process. 1.3.2 Each TO and NGET shall each nominate a contact point for data co-ordination, including a dedicated email account, to facilitate data co-ordination between NGET and that TO. 1.3.3 Communication of TO SCADA database changes shall be supplied electronically in a format to be agreed with NGET and is to include a description of the change. The format and content of the pro-forma for use in documenting the change as agreed from time to time is included in Appendix B. 1.3.4 Parties will acknowledge receipt of data via the agreed contact points. 1.3.5 On application NGET can provide guidance to SCS suppliers on the process required for SCS changes Page 3 of 10

2 Key Definitions and Interpretation 2.1 For the purposes of STCP04-1: 2.1.1 Data Transmission Equipment means equipment that collects indications and data from an NGET site and relays it to the relevant TO through a communications route. 3 Procedure 3.1 Changes not associated with Plant and/or Apparatus 3.1.1 Following changes to real time data that are not directly associated with Plant and/or Apparatus for example alarms, modifications to an outstation or a database legend change, the TO shall prepare a pro-forma (Appendix B) identify the change and provide a supporting real time electronic data submission. The format must align with NGET s GI74 or IEC60870-5-101 configuration file, as agreed with NGET, detailed in the data spreadsheet (Appendix C) listing the changes made to the database including all the relevant attributes and date of change. Where relevant an operational or EMS display diagram shall also be included. 3.1.2 The information detailed in 3.1.1 shall be sent by the nominated TO contact point to the nominated NGET contact point as soon as reasonably practicable, which shall normally be not less than 6 weeks in advance of the implementation date. NGET shall provide acknowledgement of receipt of the relevant information to the TO via the agreed contact point. NGET shall ensure that its database is updated in line with the supplied information. 3.1.3 Where NGET requires changes to real time data at NGET sites where the TO has Data Transmission Equipment installed NGET shall identify the changes and provide the information to the TO using the pro forma Appendix B via the respective contact point, to enable changes to be made to the TO SCADA database. Where relevant an operational or EMS display diagram shall also be included. 3.1.4 NGET shall notify the relevant TO(s) of any User initiated changes of which NGET has been made aware and which will require modification to that TO database or displays. Notification shall take place as soon as reasonably practicable which shall normally be not less than 6 weeks prior to implementation in order to allow sufficient time for the TO to satisfy its obligations under 3.1.1 and 3.1.2. NGET shall co-ordinate the change process between all parties. 3.1.5 Appropriate and timely testing shall be arranged at the request of either party, to validate the transmission of real time data from the TO to NGET following changes made to either or both the TO and NGET database. 3.2 Commissioning / De-Commissioning 3.2.1 STCP 19-4 Commissioning / De-Commissioning specifies the process for initiating and completing changes to the National Electricity Transmission System. Changes to real time data are an essential part of that process. 3.2.2 The key dates in the Plant and/or Apparatus change process are: the planned date on which equipment becomes subject to or is removed from the TO safety rules the planned date of commissioning or de-commissioning of equipment Page 4 of 10

3.2.3 The TO and NGET shall plan the change process to allow sufficient time for all parties to evaluate and co-ordinate the changes. This shall normally be not less than 6 weeks prior to the planned database change implementation date that aligns with the key dates in 3.2.2 3.2.4 The TO shall supply the relevant real time data (specified in STCP 4-3: Provision of Real Time Data) via the respective contact point. This shall be in the format agreed between the TO and NGET showing the proposed / amended /deleted data, and associated attributes and proposed date of change. Where applicable operational or EMS display diagrams shall be supplied. 3.2.5 NGET shall supply the TO, via the agreed contact point, details of any changes to the real time information (specified in STCP 4-3) for NGET sites that contain TO Data Transmission Equipment using Appendix B. Where applicable, operational and or display diagrams shall be supplied. 3.2.6 Where changes to the National Electricity Transmission System are to take place in a staged manner, the TO shall provide the data relevant to each stage of the change together with the proposed implementation dates. 3.2.7 As soon as reasonably practicable, NGET shall notify the relevant TO(s) of any User initiated Commissioning / De-commissioning of which they have been made aware that may require amendment to the TO SCADA database and/or operational or EMS display diagrams. 3.2.8 All real time data changes associated with Commissioning/ Decommissioning on the TO Transmission System or User System shall be the subject of close liaison between NGET and the TO in order to ensure that changes are co-ordinated. All Parties shall agree the time and date of implementation. 3.2.9 As part of commissioning the communication links between site and NGET should be proven prior to any formal testing. 3.2.10 The TO shall ensure transmission of real time data to the Datalink in accordance with STCP 4-2 (Real Time Datalink Management). 3.2.11 In order to validate the transmission of alarms and indications from the TO appropriate and timely testing shall be undertaken using agreed points of contact, at the request of either party, following changes made to either or both the TO and NGET database 3.3 Emergency Changes 3.3.1 Emergency changes are those required at very short notice to accommodate modifications initiated by events such as: emergency re-configuration of the National Electricity Transmission System urgent changes in control time scales. 3.3.2 When NGET or the TO is made aware of emergency changes in real time data that must be implemented in a shorter timescale than that specified as normal, the process detailed in 3.2 and 3.3 shall still be followed wherever reasonably practicable. Page 5 of 10

Appendix A: Flow Diagram Note that the Process Diagrams shown in this Appendix A are for information only. In the event of any contradiction between the process represented in this Appendix and the process described elsewhere in this STCP, then the text elsewhere in this STCP shall prevail. STCP 4-1 Real Time Data Change Management - Changes not associated with Plant and/or Apparatus External NGET TO User initiates changes to real time data Receive notice of User initiated change and notifies TO as soon as practicable and normally not less than 6 weeks prior to implementation date. If emergency change then as much time as possible Receive notification of User initiated change Change required to real time data not associated with Plant / Apparatus Co-ordinate change process between all parties Identify changes to real time data at NGET sites where the TO has Data Transmission Equipment installed and notify TO of changes using Appendix B providing any relevant operational or display diagram Update database. End Yes Was change to Database a result of changes at NGET site? No Receive notification of changes and acknowledges receipt Following changes made to SCADA real time data not associated with Plant and/or Apparatus prepare and send to NGET Appendix B and Appendix C and any relevant operational display or EMS diagram normally not less than 6 weeks prior to implementation date. If emergency change then as much time as possible Receive acknowledgement Implements changes and updates its database Liaison between points of contact at request of either party to validate the transmission of real time data from TO to NGET Page 6 of 10

STCP 4-1 Real Time Data Change Management - Commissioning and De-commissioning External NGET TO STCP19-4 specifies the process for initiating and completing changes to the National Electricity Transmission System NGET and TO liaison to agree relevant dates allowing all parties to evaluate and coordinate changes. Normally not less than 6 weeks. If emergency change then as much time as possible User Initiated Commissioning / Decommissioning that may change TO database Notify relevant TO of any User initiated Commissioning / De-commissioning that require amendment to the TO SCADA database and/or operational/display diagrams Receive notification of User initiated Commissioning / De-commissioning Supply details of any changes to real time data for NGET sites that contain TO Data Transmission Equipment using Appendix B. Where applicable also provide operational and/or display diagrams Supply the relevant real time data using Appendix B and Appendix C. Where applicable also provide operational and/or display diagrams. Provide details of each stage where this is appropriate Receive notifcation of changes and acknowledge receipt of the data within 3 business days of receipt Receive notifcation of changes Receive acknowledgement NGET and TO co-ordinate the change process through close liaison between all parties. Parties shall agree the time and date of implementation. Liaison between points of contact at request of either party to validate the transmission of real time data from TO to NGET Page 7 of 10

Appendix B: Modification of Facilities Certificate Initiated by (Print Name) Contact Tel. No. Initiators Change Request Number Company / Party Date issued Date of Implementation Target Date for Testing... Description of Required Change Diagram / Description of required change Y/N Display Change Display / Circuit Name / Number Page 8 of 10

substation including voltage description pointid point type normal state abnormal state substaion including voltage Display digits engunits exdesc pointid point type span step typical value zero STCP 04-1 Real Time Data Change Management Appendix C: Sample Real Time Data Spreadsheet Analogue xxxxxx 2 AMPS xxxxxx 22106 float32 1400 1 1400 0 xxxxxx 0 AMPS xxxxxx 136791 float32 500 1 500 0 xxxxxx 2 MVAR xxxxxx 22566 float32 300 1 300-150 xxxxxx 2 MW xxxxxx 22567 float32 89 1 89 1 xxxxxx 0 AMPS xxxxxx 22591 float32 1400 1 1400 0 Digital xxxxx xxxxxx 12345 digital in out Page 9 of 10

Appendix D: Abbreviations & Definitions Abbreviations SPT SHE-T SCADA TO SP Transmission plc Scottish Hydro Electric Transmission plc Supervisory Control and Data Acquisition Transmission Owner Definitions STC definitions used: Apparatus NGET Plant User Grid Code definitions Used: Protection Apparatus Definition used from other STCPs: Datalink STCP04-2: Real Time Datalink Management Page 10 of 10