The iEMS Refresh Project · · 2017-11-23PR2 (a) PR2 (b) Data and updates . System Security 7 ....

Place your chosen

image here. The four

corners must just

cover the arrow tips.

For covers, the three

pictures should be the

same size and in a

straight line.

The iEMS Refresh Project

Ronan Jamieson & Graham Newton

System Operator, Wokingham

Agenda

National Grid’s iEMS

iEMS Refresh Project

System cut-over and go-live

2

Introduction to National Grid’s iEMS

What is the iEMS?

Integrated Energy Management System

SCADA system to manage NG’s transmission assets

Receive real-time data from the network (i.e. Voltage, Power, Equipment status)

Send controls to network equipment

4

“Meet licence obligations of continuously operating a safe,

secure and economic electricity network for the whole of Great Britain”

5

Key iEMS capabilities

High Availability

Dual redundant systems located in two locations, three locations capable of access

Real-time Data

Real-time data is collected from all NG electricity substations and from Scottish TOs and, some DNOs

Selected data is transferred out to other key systems

Tele command switching

The ability for engineers to re-configure the network to meet operation needs

PNA Analysis

Security, contingency and voltage analysis of the power network in real time (< 2mins) and offline studies.

Safety Management

Safety application allowing work to be safely processed and carried out on the electricity grid with extensive reporting and tracking of safety document, with clear visual indications on graphical displays

Design Philosophy

The design of the production IEMS systems uses the following principles:

Two production systems located at different sites.

Each production system is made of two independent halves, located in independent rooms.

The two production systems collect and process data independently

Database updates are performed independently on all iEMS systems

All servers are physical

This distributed nature of the architecture greatly minimises

service loss due to a single site / system failure

6

Production

system 1

Site 1

Production

system 2

Site 2

PR1 (a) PR1 (b)

PR2 (a) PR2 (b)

Data and

updates

System Security

7

IEMS Interfaces

8

IEMS

Substations

Data Archive

Scottish TOs and DNOs

ENTSO-E User

Interfaces

Balancing System

Other Key NG

Systems

System Monitoring

All elements of the IEMS refresh system will be monitored 24-hours a day 365 days a year by the following four teams:

CNI Health Team (CHT)

This team is based in DC1, monitors the IEMS hardware

Vodafone Network Monitoring Team

This team is based in DC2, monitors the IEMS network and highlights any issues to the CHT.

Security Team

This team will be investigating alerts from the IDS system

Property Team

This team will provide monitoring of power and air conditioning at the three sites (DC1, DC2, and DC3)

9

The iEMS Refresh project

Project Scope

Upgrade the existing IEMS system Software Application

Replace all existing Application hardware

Deliver a new IEMS production network in the UK at

Wokingham, Warwick and Reading, replacing all

existing IEMS network equipment.

Provide an enduring replica production system,

including network, for ongoing Testing (GE1)

11

iEMS Refresh Customer Benefits

12

Ongoing Network management

Secures our ability to manage power transmission systems 24x7 to

mid-2020s

Secure, robust and stable

Provides enhanced cyber security

Ensures required resilience and stability

Enhanced Capabilities

IEMS v17 is providing enhanced capabilities now and allowing for further future opportunities

System Quality and Testing

The Project has used a extensive test regime to ensure the delivery of a high quality product:

Multiple test phases, using a high number of experienced users

More than 2000 tests to validate the solution

Successful Failure-over testing

iEMS Synchrocheck Test – 100% Success

Real-time operational switching at Minety 400kV was performed via the R17 iEMS system

13

iEMS Timeline

14

• Site Acceptance Testing Complete

September 2017

• System Go-Live 4 November

2017

• Post Implementation support complete

December 2017

• Decommissioning complete / Project Closed

January 2017

Cut over process

Senior Management Involvement

Independent Transition forum (Recommends)

3 month/1 month /1 week/1day Go / No Go Meetings

Dress Rehearsal Sessions

Halt Periods during cut over (Roll-back plans identified)

On the day Cut Over Team (Defined roles & responsibilities over the

period)

15

MAIN = Active

DBU = Standby (no RTUs)

PR1 = n/a available

PR2 = Active

This is the preferred system

configuration determined to be

lowest risk to operations, in

anticipation of cut-over activities at

SGL-0

Required Control Systems

Configuration

16

IEMS – DBU Control Enabled

IEMS – MAIN In Control

RTDT Enabled to

DBU

SUB

IEMS – PR1 Control Disabled


RTDT Enabled to

PR1

Release 10 Release 17

Hands-off period to be agreed with

ENCC/TNCC for approximately 0-

30, whilst the Manual Entered Data

(MED) is exported from IEMS-DBU.

Co-ordination to be via PSM (and

CHT).

Failure to adhere to restriction

could result in database mismatch

or data corruption, causing delay or

abortion of system migration

activities.

On completion of MED Import PR2

is available for control

- MED dip-check

- PNA running

- Manual data catch-up and dual

dressing

Duration Est. 3 hours before hand-

over

SGL – 1day

17



RTDT Enabled to

DBU

SUB



RTDT Enabled to

PR1

Export all Manually Entered

Data [MED]: tags, hand

dressing, memo notes, etc.

Import all MED:

Gain status of dip-check

Gain status of PNA runs

Hands-off period on Rel:17 only

Manually Synchronise PR2 to PR1.

On completion establish System to

System synchronisation (SISO)

Co-ordination to be via PSM (and

CHT).

On completion of ManualSynch,

CHT confirms status of data

between PR1 /PR2

Dual dressing continues on Rel:10

and Rel:17

Duration Est. 2 hours

SGL – 0

18



SUB



Manually synchronise

database and all data

MAIN system demoted from Active

to Standby working.

PR2 taken down, configuration

changes made. To complete a

‘warm’ start is initiated.

Visibility of power system still

possible through IEMS MAIN as

Standby and possible option to

promote back to ACTIVE working

Duration Est. 30 minutes

SGL – 0

19


IEMS – MAIN Control Enabled

SUB


IEMS – PR2 Control Enabled

Interfaces transfers outstanding

PR2 returns taking control of all

RTU connections. Control room

initiates dummy breaker checks.

PR2 = Active

MAIN = Standby

Dual dressing continues on Rel:10

and Rel:17

HOLD POINT x

PR1 taken down, configuration

changes made in anticipation of

system being established as

STANDBY.

Duration Est. 45 minutes

SGL – 0 (PR2 now in Control[Active])

20



SUB



SGL – 0 Interface Transfers 1 of 3

21



ICCP: BM1

ICCP: EBS1

ICCP: BM2

ICCP: EBS2

Risks

All ICCP connections dual feed Rel:10 and Rel:17

Activities are to establish redundant connections to Rel:17


22



EBS sftp

OLTA sftp

RMS sftp

EFS sftp

OSA sftp

DH esb

FATE rs232

Risks

EFS - terminating end has opted for making changes on the

day without testing to their production

DH – code change needed to be implemented on the day to

establish Rel:17 communications


23



ICCP: SP

ICCP: SSE

ICCP: Coreso

ICCP: UKPN

ICCP: ENW

ICCP: EAS(RTE)

Risks

All ICCP connections dual feed Rel:10 and Rel:17

Activities are to establish redundant connections to Rel:17

Interface transfers complete

Status

PR2 = Active

MAIN = Standby

PR1 = Available

PR1 Control Enabled in preparation

of promotion to Standby

Duration Est. 15-20 minutes

SGL – 0 Establish PR1 as Standby

IEMS

24



SUB



Interfaces transfers complete

PR1 Promoted to Standby

Final Status

PR2 = Active

PR1 = Standby

MAIN = Available

DBU = Available

System check conducted by CHT

Duration Est. 15-20 minutes

SGL – 0 Establish PR1 as Standby

IEMS

25



SUB



Questions

The iEMS Refresh Project · · 2017-11-23PR2 (a) PR2 (b) Data and updates . System Security 7 ....

Documents

Transcript of The iEMS Refresh Project · · 2017-11-23PR2 (a) PR2 (b) Data and updates . System Security 7 ....