Utility Integration Bus Approach To System Migration

1. Utility Integration Bus Approach To System Migration Duquesne Light Co.

2. EMS Migration • Never Done • Choices at every step • Employ standards whenever possible

3. Duquesne’s EMS Migration • First Cut • MMS as the Integration Bus • SQL Server for Data Persistence

4. Duquesne’s EMS Migration • Established access to all real-time data using MMS and the GOMSFE Basic RTU Model • Separated EMS Functions into Collaborating Components on a Local Area Network • Using the LAN, MMS, and DCOM and SQL Tables as the Integration Bus

5. Utility Integration Bus Approach • Need for the standard Bus • Tried DCOM • Tried SQL Update Queue

6. Utility Integration Bus Approach • Single Interface for All components • 1 to 1 interfaces don’t work • Redundant Data Providers and consumers • Single queue for maintenance, persistence and security

7. Utility Integration Bus Approach • Publish and Subscribe • Provide single interface for vendor and in-house development • Thin Specification approach • Reduced Documentation

8. Operator Event Notification • First Step in Migration • Minimize impact on Operators • Single point for Operator notification

9. Operator Event Notification • New Events Published to the “Event Forwarder” • Operator Screens Subscribe to a category of events • Historian Function Subscribes to all events • Acknowledgment and clearing published to “Event Forwarder”

10. DCOM Event Publishers Operator Event Screens DCOM Event Historian Event Diagram MTS DCOM Event Forwarder DCOM DCOM

11. SCADA Function • Field Data Changes Published to SQL Database and SQL “Queue Table” • Operator One Lines Subscribe to Database for changes • Change detection and Limit Detection subscribe to “Queue Table” • On Change Detection Message Published to Event Notification System

12. Operator SCADA Screens SCADA Diagram SQL Database Real-Time Data Base Change Queue UCA Publishers Status Change Publisher DCOM UCA Devices ( MMS Servers) Event System

13. Need a Common Publish and Subscribe Bus(UIB) • Event Actions and SCADA Data Published to the Same Bus • Onelines and Operator Event Screens Subscribe to the Same Bus • Messages differentiated for quick routing • Security Redundancy and a Persistent Queue needed

14. Event Publishers UCA Publishers Operator Event Screens Operator SCADA Screens UIB Diagram Real-Time Data Base Event Historian UIB

15. Utility Involvement • Get involved in EPRI’s CCAPI • CIM is the Data Model • Bus is needed to integrate different Applications. • Standard Message Types, Security Roles and Redundancy Schemes

16. UIB Immediate Benefits • Plug and Play applications • Integration of NERC-Tagging, Oasis, ISN, IIDC • Pennsylvania Customer Choice applications.

17. UIB Can • Make integration of different Applications a reality • Define a scheme that can be replicated into the future • Build an extensible framework for the changing environment