Energy Management System (EMS) 3.0 Implementation Overview for BRP Consultation. July 2015

Transcription

1 Energy Management System (EMS) 3.0 Implementation Overview for BRP Consultation July 2015

2 Background Energy Management System EMS - Used by System Controllers to monitor, control and optimize the performance of the power system (used in grid operations) - The last EMS upgrade project ran from 2006 to 2009 and included both the EMS application (Alstom suite) and the underpinning infrastructure. Much of the infrastructure was purchased in 2007 and is now over six years old. - To ensure the continued reliability of grid operations, it has now become critical to refresh the EMS system in its entirety 2

3 EMS System - EMS is a system, multi-faceted and distributed across multiple servers inclusive of: o SCADA Data Acquisition (and outbound controls), Calculations, Tagging, Notes, LSSI o Generation Balancing (Automatic Generation Control), Reserves Calculation, Dynamic Scheduling, Wind Power Ramp Management (WPRM) o Network Applications State Estimation, Contingency Analysis, Voltage Stability Analysis, Power System studies o Core Services User Interface, Alarm, Inter-system connectivity, Security 3

4 EMS System - Key Statistics: o AESO power system model contains approximately data points, including information collected from over 1200 substations through 85 different data providers. o Data collected every 2s to 30s (depending on criticality); AESO is adopting high-speed data acquisition (30/s) through phasor measurement technology - Incorporates environments to support modeling, development, testing, and training (including scenario simulation) - EMS facilitates the market to operate in the least constrained manner possible 4

5 Problem Statement - The EMS application and associated infrastructure are end of life. Vendor support ceases Growing risk of security breaches and operational impacts - Current system is not CIP compliant 5

6 EMS Program Approach Current Status: Definition Phase (85% complete) Decision to proceed with Implementation Go-Live June 2017 Validation Definition Implementation Sustainment Technical Assessment Evaluation of environment Opportunity identification Decision to move to Definition Phase Requirements Detailed design Cost Schedule Planning and Management Application Infrastructure Testing Training Deployment Decommission Evergreen Lifecycle management to optimize operational costs 6

7 Options 1. Do Nothing (not viable) No vendor support Increase risks: security, reliability Non-compliance penalties 2. Hardware enhancement and patching of EMS 2.5 (defer upgrade) Compliance may be achieved (short-term), residual security risk and no vendor support More analysis required for patching and virtualization 3. Implement EMS 3.0 (preferred option) Higher initial cost, vendor support Regulatory compliance 7

8 Implementation Phase Objectives - Optimize system reliability, security and performance - Reduce risk to grid management - Maximum period of vendor support coverage - Implement EMS Lifecycle Management Plan to manage operations, enhancements and upgrades - Ensure EMS system is fully CIP compliant 8

9 Proposed Solution - Upgrade current system: Alstom EMS 2.5 to New on New new software version on new infrastructure - Ensure Like for Like functionality with the existing system, but with room for growth - Implement EMS Lifecycle Management Plan 9

10 Implementation Deliverables 10

11 Scope - Application upgrade to EMS Infrastructure replacement: servers, storage, network, security and monitoring - Testing: 10 months duration hours of parallel testing - Training: End users and operational support team - EMS 2.5 decommissioning - Life-cycle Management Plan Target Complete: Q Estimated budget: $31.7M (Excludes capitalized borrowing costs) 11

12 Implementation Budget ($31.7M) $20 $17.2 $15 $10 $5 $8.2 $6.3 $ Total program cost: $39M (Definition Phase: $7.3M) Costs will be allocated between energy market and transmission and will be recovered post program completion. 12

13 EMS Implementation Timelines Pre-FAT: Pre-Factory Acceptance testing FAT: Factory Acceptance testing SAT: Site Acceptance testing 13

14 Program Risks and Mitigations Key Risks Mitigations Schedule and implementation delays possible Detailed, fit-for-purpose program management and governance structure implemented Solution delivery: large and complex project Extensive Definition Phase conducted Vendor ability to deliver Overall schedule and CIP compliance Hybrid staff augmentation Adapted program governance Comprehensive test strategy New on New parallel approach Rigorous vendor management practices Advance the Alstom development work and associated infrastructure required 14

15 External Stakeholders Impact - No stakeholder impact expected - No impact to the market and SCADA/controls 15

16 Proposed Next Steps - Present the business case and the results of the stakeholder consultation to AESO Audit Committee and Board of Directors for approval - Commence the Implementation Phase Oct 1 st

17 Comments/questions?