Utility Integration Bus Approach To System Migration Duquesne Light Co.
-
Upload
harold-hill -
Category
Documents
-
view
218 -
download
0
Transcript of Utility Integration Bus Approach To System Migration Duquesne Light Co.
Utility Integration Bus Utility Integration Bus Approach To System Approach To System MigrationMigrationDuquesne Light Co.Duquesne Light Co.Duquesne Light Co.Duquesne Light Co.
EMS MigrationEMS Migration
• Never DoneNever Done
• Choices at every stepChoices at every step
• Employ standards whenever Employ standards whenever possiblepossible
Duquesne’s EMS MigrationDuquesne’s EMS Migration
• First CutFirst Cut
• MMS as the Integration BusMMS as the Integration Bus
• SQL Server for Data PersistenceSQL Server for Data Persistence
Duquesne’s EMS MigrationDuquesne’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
Utility Integration Bus Approach
• Need for the standard Bus
• Tried DCOM
• Tried SQL Update Queue
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
Utility Integration Bus Approach
• Publish and Subscribe
• Provide single interface for vendor and in-house development
• Thin Specification approach
• Reduced Documentation
Operator Event Operator Event NotificationNotification
• First Step in Migration
• Minimize impact on Operators
• Single point for Operator notification
Operator Event Operator Event NotificationNotification
• New Events Published to the “Event New Events Published to the “Event Forwarder”Forwarder”
• Operator Screens Subscribe to a category Operator Screens Subscribe to a category of eventsof events
• Historian Function Subscribes to all eventsHistorian Function Subscribes to all events
• Acknowledgment and clearing published Acknowledgment and clearing published to “Event Forwarder”to “Event Forwarder”
Event DiagramEvent DiagramEvent HistorianEvent Historian
Event Forwarder
Event Forwarder DCOMDCOM
MTSMTS
Operator Event Screens
Operator Event Screens
DCOMDCOM
Event PublishersEvent Publishers
DCOMDCOM
DCOMDCOM
DCOMDCOM
SCADA FunctionSCADA Function
• Field Data Changes Published to SQL Field Data Changes Published to SQL Database and SQL “Queue Table” Database and SQL “Queue Table”
• Operator One Lines Subscribe to Database for Operator One Lines Subscribe to Database for changeschanges
• Change detection and Limit Detection Change detection and Limit Detection subscribe to “Queue Table”subscribe to “Queue Table”
• On Change Detection Message Published to On Change Detection Message Published to Event Notification SystemEvent Notification System
SCADA DiagramSCADA Diagram
UCA Publishers
UCA Publishers
SQL DatabaseSQL Database
StatusChange
Publisher
StatusChange
PublisherOperator SCADA
Screens
Operator SCADA Screens
Real-Time Data Base
Real-Time Data Base
Change QueueChange Queue
UCA Devices( MMS Servers)
UCA Devices( MMS Servers)
Event SystemEvent System
DCOMDCOM
Need a Common Publish Need a Common Publish and Subscribe Bus(UIB)and Subscribe Bus(UIB)
• Event Actions and SCADA Data Published Event Actions and SCADA Data Published to the Same Busto the Same Bus
• Onelines and Operator Event Screens Onelines and Operator Event Screens Subscribe to the Same BusSubscribe to the Same Bus
• Messages differentiated for quick routingMessages differentiated for quick routing
• Security Redundancy and a Persistent Security Redundancy and a Persistent Queue neededQueue needed
UIB DiagramUIB Diagram
Event PublishersEvent Publishers
Event HistorianEvent Historian
Operator Event Screens
Operator Event Screens
UIB
Operator SCADA Screens
Operator SCADA Screens
UCA Publishers
UCA Publishers
Real-TimeData Base
Real-TimeData Base
Utility InvolvementUtility Involvement
• Get involved in EPRI’s CCAPIGet involved in EPRI’s CCAPI
• CIM is the Data ModelCIM is the Data Model
• Bus is needed to integrate different Bus is needed to integrate different Applications.Applications.
• Standard Message Types, Security Standard Message Types, Security Roles and Redundancy SchemesRoles and Redundancy Schemes
UIB Immediate BenefitsUIB Immediate Benefits
• Plug and Play applicationsPlug and Play applications
• Integration of NERC-Tagging, Oasis, Integration of NERC-Tagging, Oasis, ISN, IIDCISN, IIDC
• Pennsylvania Customer Choice Pennsylvania Customer Choice applications.applications.
UIB CanUIB Can
• Make integration of different Make integration of different Applications a realityApplications a reality
• Define a scheme that can be Define a scheme that can be replicated into the futurereplicated into the future
• Build an extensible framework for Build an extensible framework for the changing environmentthe changing environment