April 3, 2001 Washington, DC

39
April 3, 2001 Washington, DC 2001 EMS Users Group

description

2001 EMS Users Group. April 3, 2001 Washington, DC. PEPCO EMS Migration. Manley Higgins PEPCO Project Manager Mark Bruen KEMA Consulting Principal Consultant. EMS Migration. Migration Philosophy Overview of EMS Migration Phases Related Enhancement Efforts Future Phases - PowerPoint PPT Presentation

Transcript of April 3, 2001 Washington, DC

Page 1: April 3, 2001  Washington, DC

April 3, 2001 Washington, DC

2001 EMS Users Group

Page 2: April 3, 2001  Washington, DC

Manley Higgins PEPCO

Project Manager

Mark BruenKEMA Consulting

Principal Consultant

PEPCO EMS Migration

Page 3: April 3, 2001  Washington, DC

EMS Migration

• Migration Philosophy

• Overview of EMS

• Migration Phases

• Related Enhancement Efforts

• Future Phases

• Long Range Plan & Update Process

• Challenges for the Future

Page 4: April 3, 2001  Washington, DC

EMS Migration

Migration Philosophy

Page 5: April 3, 2001  Washington, DC

Migration Philosophy

• In 1995, PEPCO Adopted a Long-Term EMS Migration Philosophy to Keep the EMS “Ever-green”.

Page 6: April 3, 2001  Washington, DC

Migration Philosophy

• Migration Rationale:

• Keep the system technologically current to meet the terms of the financial lease

• To protect the investment in the operational procedures, EMS software, system design, & database.

• To avoid obsolescence of hardware

Page 7: April 3, 2001  Washington, DC

Migration Philosophy

• Migration Rationale (cont.):

• To support increased performance and capacity requirements

• To allow for the addition and enhancement of system functions as business requirements change

• Enhance the EMS to accommodate the implementation of large-scale Distribution Automation and Substation Automation projects

Page 8: April 3, 2001  Washington, DC

Migration Philosophy

• Migration Rationale (cont.)

• And, to avoid the extreme and expensive effort of another EMS “forklift” replacement, including:• Procurement costs• System Testing• Cutover• Software Quality Control• Staff time commitment

Page 9: April 3, 2001  Washington, DC

EMS Migration

Overview of the PEPCO EMS

Page 10: April 3, 2001  Washington, DC

Overview of the Original PEPCO EMS

• EMS is “Consolidated Control System”• Designed to support Transmission,

Distribution, and Generation Operations • (Generation sold December

2000)

Page 11: April 3, 2001  Washington, DC

Overview of the Original PEPCO EMS

• Interfaces with other critical PEPCO and external systems including:• New Outage Management

System• Corporate Systems• PJM

Page 12: April 3, 2001  Washington, DC

Overview of the Original PEPCO EMS

• Procured from ABB Network Management (formerly NMTI)

• Delivered in 1993

• Initially commissioned in 1994

Page 13: April 3, 2001  Washington, DC

Overview of the Original PEPCO EMS

• Full featured EMS including:

• SCADA• Graphical User Interface (not

workstation based Full Graphics)• Distributed System w/ Proprietary

Hardware Front-ends• Full Advanced Applications Suite

• Real-time and Study• PEPCO Specific Applications

Page 14: April 3, 2001  Washington, DC

Overview of the Original PEPCO EMS

• Dispatcher Consoles• Transmission Dispatchers• Load Dispatchers• Transmission Shift Supervisors• Distribution Shift Supervisors

• System Support Consoles

• Development and Testing Facility• Dispatcher Training Simulator

Page 15: April 3, 2001  Washington, DC

EMS Migration

PEPCO Migration Phases

Page 16: April 3, 2001  Washington, DC

Migration Phases

• PEPCO established a multi-year migration program:• To fully migrate the EMS every

seven years.

• PEPCO’s management committed to to fund the effort to avoid the high costs of another procurement.

Page 17: April 3, 2001  Washington, DC

Migration Phases

• Migration Phase I – 1995 – 1996

• Open Systems Platform Enhancements including:

• Introduction of Dec Alpha Hardware Platform

• Operating System Upgrades• VAX VMX to UNIX• Intel RMX to UNIX

Page 18: April 3, 2001  Washington, DC

Migration Phases

• Migration Phase I (cont.)

• Conversion of Code to C• (from less common/difficult

languages – PLM, Assembly)• FORTRAN not converted

Page 19: April 3, 2001  Washington, DC

Migration Phases• Migration Phase II – 1997-1998

• ICCP for standards-based communications with:• PJM• PEPCO to BGE (planned

merger)• Ranger Data Acquisition Server

• Compaq Alpha hardware and Unix operating system

• Bow Software Protocol Emulations

Page 20: April 3, 2001  Washington, DC

Migration Phases• Migration Phase II – (cont.)

• Addition of PI Historian Data Repositories

• Upgraded DTS• Increased Database Sizing

• Via System Master Parameters

Page 21: April 3, 2001  Washington, DC

Migration Phases• Migration Phase III – 1999 – 2000

• Workstation Based Graphical User Interface

• ODBC Interface Into EMS• NT Based Historian• Study Mode State Estimator –

Uses Historian Data for Studies• DNP Protocol

Page 22: April 3, 2001  Washington, DC

Migration Phases• Migration Phase III (cont.)

• Event Storage and Retrieval

• Updated Software Tools to Improve Maintenance and Support Environment

Page 23: April 3, 2001  Washington, DC

Migration Phases

• Migration Phase IV – 2001-2002

(currently in progress)

• Increase DB Sizing (1.5 x current)• Naming size increases• DNP Protocol Converter (Rockwell

5020 to DNP)• Transfer Existing RTU to RDAS• Graphical Data Engineering Tool

• CIM Based

Page 24: April 3, 2001  Washington, DC

Migration Phases

• Migration Phase IV – (cont.)

• Facilities and Support Systems• Console Voice Equipment

(integrates PEPCO’s radio and telephone requirements)

• Upgrade/Life Extension for Critical Power (UPS) and HVAC

Page 25: April 3, 2001  Washington, DC

Migration Phases• More to Come?

• Phase V – Commercial Display Generation Software

• Phase VI – Upgrade EMS Application Processors, storage devices, printers, Bow-Tie Equipment, LAN I/F

• Phase VII – SCADA System• Phase VIII – Advanced Apps.

• These phases are currently under review

Page 26: April 3, 2001  Washington, DC

EMS Migration

Related EMS Enhancement Efforts

Page 27: April 3, 2001  Washington, DC

Related EMS Enhancement Efforts

• RTU Protocol Conversion for existing RTUs

• Outage Management System/EMS Interface – using ICCP

• Source Data Management System – to improve data management process

• System Security Enhancements

Page 28: April 3, 2001  Washington, DC

Related EMS Enhancement Efforts

• PEPCO Substation Automation Initiatives:

• Increased data from smart relays and Substation Automation systems (4 kV, 13 kV, 69 kV, 230 kV substations)

• VAR Dispatch – using feeder capacitors.

Page 29: April 3, 2001  Washington, DC

Related EMS Enhancement Efforts

• PEPCO Distribution Automation Initiatives:

• Feeder sectionalization using fault detectors and Motor Operated Disconnects

• 69 kV MODs• 13 kV MODs• Utilinet Spread Spectrum Radios

Page 30: April 3, 2001  Washington, DC

EMS Migration

Future Migration Phases

Page 31: April 3, 2001  Washington, DC

Future Migration Phases

• Migration of Advanced Applications to support:

• New Business Needs• New ISO Support Requirements• New Corporate Information Needs• Corporate Reorganizations and

Industry Restructuring

Page 32: April 3, 2001  Washington, DC

EMS Migration

Long-Range Plan & Update Process

Page 33: April 3, 2001  Washington, DC

Long-Range Plan and Update Process

• PEPCO is currently reviewing the Long-Range Migration Plan• Looking at current operational and

business needs• Investigating current technology• Assessing impacts of restructuring

• To properly align the next migration phases with the overall long-term direction

Page 34: April 3, 2001  Washington, DC

Long-Range Plan and Update Process

• Goal is to provide an updated 10 Year Forecast for planning purposes.

• Also to more clearly define the near-term needs and associated migration projects.

Page 35: April 3, 2001  Washington, DC

EMS Migration

Challenges for the Future

Page 36: April 3, 2001  Washington, DC

Challenges for the Future

• Distribution Operations Optimization• Fault detection and automated

feeder reconfiguration• Other distribution functions

• Additional Expansion of Distribution Functional and Data Requirements• Smart Relays, MODs, etc.

Page 37: April 3, 2001  Washington, DC

Challenges for the Future

• Integration with Corporate Systems

• Corporate-wide Data Availability• For Maintenance Monitoring

System• Enterprise Application Integration

(EAI) Environment

Page 38: April 3, 2001  Washington, DC

EMS Migration

Questions and Comments?

Page 39: April 3, 2001  Washington, DC

EMS Migration

Thank You!