ENERGY

Ivo Kuijlaars

SCADA Lifecycle Management The 13th International Workshop on Electric Power Control Centers Bled, Slovenia, May 17-20, 2015

1

DNV GL ©

1

SAFER, SMARTER, GREENER

2

DNV GL ©

Agenda  SCADA Lifecycle Management values  Reasons for choosing a new SCADA system  Trends  Process towards a new SCADA system  System handover: Hurray! or Wmah?

 What to do after system handover?  Solution in 3 gap analyses  Conclusion

3

DNV GL ©

SCADA Lifecycle Management: Values DNV GL VALUES  We build trust and confidence  We never compromise on quality or integrity  We are committed to teamwork and innovation  We care for our customers and each other

 We embrace change and deliver results SCADA Lifecycle Management values  We embrace change as a chance to help the business improve

 We believe in standardisation and best practices  We care for system and data quality  We promote fit for purpose systems  We want customers to maximise benefits from their SCADA system

4

DNV GL ©

Reasons for choosing a new SCADA system  System replacement/upgrade: – Outdated hardware: – servers, wall display etc. – Hardware limitations: – e.g. on historical data storage

– Lagging system / database maintenance – Outdated database versions, limited vendor support – Outdated cyber security measures – Cumbersome MMI (inefficient, slow, user unfriendly)

5

DNV GL ©

Reasons for choosing a new SCADA system  Need for more advanced features: – External demands for data – Interfaces to GIS, CIS etc. – Smart meter integration – Use of standards (CIM, IEC 61850)

– Redundancy – Asset optimisation (affordable) – Grid optimisation (reliable)

6

DNV GL ©

Reasons for choosing a new SCADA system  Cost reduction: – Compensation/fine reduction – Efficiency – Process harmonisation and a more proactive way of working – Loss reduction – Risk reduction  Other reasons: – Data quality improvement – Aging workforce – Safety

SCADA maturity 7

DNV GL ©

Trends  System trends: – Systems become more open, more modular, more standardised – IT ages faster, virtualization of hardware – More frequent updates – Shorter vendor support (OS, SCADA, database)

– Maintenance contracts more questionable  Data trends: – More measurements, more controlled devices – Higher frequency of data (e.g. for load forecast renewables)

– More exchange of data, more interfaces, CIM – Big data, data analytics, data quality  Business trends: – Requirements change with business (process) changes

– From reactive to proactive system operation 8

DNV GL ©

Standardised data exchange

Benefits • •

One interfaces per application: less development/maintenance One asset definition: improved knowledge on assets, fewer errors

Common situation

Standardised situation

 Point-to-point interfaces.

 Interfaces based on one protocol.

DNV GL © 9

Process towards a new SCADA system Business planning

Hand over

Feasibility study

Commissioning

System design (Requirements)

SAT

SCADA system specification

Installation

Tendering and vendor selection

FAT

Vendor contract and system set up

Problem space

DNV GL ©

Specs System

Solution space

After system handover: Hurray! or Mwah?  Benefits of a new system are not always, not directly, not fully gained  Some causes: – Acceptance of system deviations – Altered business requirements – Reluctance to alter business processes

– Inadequate user training – Failure to keep documentation up-to-date  Trends show systems need frequent updates and system replacement can be expected within less than 10 years.

11

DNV GL ©

What to do after system handover?  What can be done after SCADA system handover? – to benefit more from the new system? – to improve efficiency in system usage – with training? – with process optimisation? – to improve system features with (tailored) changes? – to prepare for the next SCADA project? SYSTEM USE

DNV GL ©

The SCADA lifecycle scan

13

DNV GL ©

The SCADA lifecycle scan Gap 1: Operational use - Requirements  Experience shows that system functionalities are not fully used as was intended.  Therefore the operational system usage is reviewed against system specifications. – Is all offered functionality used in practice? – Is system usage according to training? Are there workarounds? – Are data quality and interfaces blocking the way for optimal use?

– Is system communication flawless? – Are processes described and followed?  To benefit operationally from the system, recommendations are given on:

– Extended training – Process optimisation – Data quality, system interfaces, communication settings

14

DNV GL ©

The SCADA lifecycle scan Gap 2: Business case - KPIs  In many cases the business cases of the projects were based on quantitative costs and more qualitative benefits. Performance control needs to be implemented.  The business case is reviewed and measured against Key Performance Indicators. – Gather KPIs before and after system implementation

– Interviews on improvements based on KPI measurements  To benefit financially from the system, recommendations are given on: – Process efficiency – Harmonisation of work – System improvements – Use of standards

15

DNV GL ©

The SCADA lifecycle scan Gap 3: Documentation - Functionality  In the final testing phase changes and settings are sometimes poorly documented. This is detrimental to system maintenance and obstructs an efficient future upgrade path.  System and user documentation is reviewed against the actual functionality of the system. – Is the documentation complete and up to date? – Were there any specials implemented during or after commissioning?  To prepare for maintenance, updates and replacement: – Document all implemented system changes and settings – Document changed requirements and new wishes

16

DNV GL ©

Examples of best practices 1. Dispatchers are guided by a user friendly interface. 2. KPIs are automatically generated by the system. 3. Documentation is continuously updated and verified at changes. 4. Standard IT solutions are the guide to process optimisation. 5. Business users (not IT) are responsible for the data and the processes.

6. The principle of ONE truth is applied: data has only one source system in the organisation. Data can exist in more systems, but will be updated in only one system. 7. All assets shall have a unique identification within the enterprise and naming conventions are established. 8. Data updating and data analysis environments are separated. 9. There is consensus on data definition and a corporate sematic information model is used (e.g. CIM). 10.Sets of test cases to automate testing are created.

17

DNV GL ©

The SCADA lifecycle scan

The SCADA lifecycle scan provides valuable recommendations for improvement of the overall system effectiveness.

18

DNV GL ©

Scan iteration moments

Example of SCADA lifecycle scan moments New system

Scan

Warranty period

Usage Patch 1 Scan

Usage Patch 2 Usage New requirements

Scan Scan

19

DNV GL ©

Reasons to choose for the SCADA lifecycle scan  Effectiveness: to operationally benefit from the system  Efficiency: to financially benefit from the system  Change readiness: to be better prepared for maintenance, updates and future system replacement

20

DNV GL ©

Thank you for your attention Ivo Kuijlaars MSc MMC www.dnvgl.com

SAFER, SMARTER, GREENER

21

DNV GL ©

Principal Consultant Intelligent Networks & Communication [email protected] Direct: +31 26 3562668 www.dnvgl.com/energy