1. Utility Integration Bus Architecture (and Implementation) the KCPL CIM / UIB Project EMS Users Group June, 1999 Pat Brown, KCPL John Kishpaugh, KCPL

2. n 1997 EMS Users Group presentation – the KCPL integration problem – the progress of electric utility standards – the promise of distributed object technology “A fascinating intersection of industry readiness and technology readiness” KCPL CIM / UIB Project

3. high quality becoming commonly used? our standards are... allows software and data to be spread across platforms that 5-letter “C” word... CORBA (Common Object Request Broker Architecture) that 5-letter “C” word... CORBA (Common Object Request Broker Architecture) Electric Utility Software Standards Electric Utility Software Standards a fascinating intersection...

4. n 1998 EMS Users Group presentation – the KCPL integration problem – designing solutions with electric utility standards – and distributed object technology “Why we’re using an integration bus” KCPL CIM / UIB Project

5. the KCPL Business Solution: the KCPL Technical Problem CIM Database Desktop Access DFMS Distribution Facilities Management System EMS Energy Management System Power Pool ICCP Maintenance Management System Real-Time Data Historian Substation Automation

6. the KCPL Technical Solution CIM Database Desktop Access DFMS Distribution Facilities Management System EMS Energy Management System Power Pool ICCP Maintenance Management System Real-Time Data Historian Substation Automation Utility Integration Bus

7. n 1999 EMS Users Group presentation – the KCPL integration problem – the key architectural concepts of the Utility Integration Bus, an electric utility standard integration framework using distributed object technology “What is the Utility Integration Bus?” KCPL CIM / UIB Project

8. n An integration of 4 control center applications, that supports: – data sharing real-time electrical system model one-line display data – remote requests supervisory control KCPL CIM / UIB Project Overview

9. EMS Energy Management System Trans & Power Operators real-time “point” data electrical system model info supy control requests RTUs CIM / UIB Project Applications Integrated

10. EMS Energy Management System DFMS Distribution Facilities Management System Distribution Operators CADS real-time “point” data display info electrical system model info supy control requests Trans & Power Operators RTUs CIM / UIB Project Applications Integrated

11. EMS Energy Management System KCPL-wide Desktop Access TOM Transmission Operations Model database DFMS Distribution Facilities Management System Distribution Operators CADS real-time “point” data display info electrical system model info supy control requests Trans & Power Operators RTUs CIM / UIB Project Applications Integrated

12. EMS Energy Management System KCPL-wide Desktop Access Power Pool ICCP Inter-Control Center Communications Protocol package TOM Transmission Operations Model database DFMS Distribution Facilities Management System Distribution Operators CADS real-time “point” data display info electrical system model info supy control requests Trans & Power Operators RTUs CIM / UIB Project Applications Integrated

13. EMS Energy Management System Utility Integration Bus (UIB) KCPL-wide Desktop Access Power Pool KCPL CIM/UIB Project Overview DFMS/UIB Interface ICCP Inter-Control Center Communications Protocol package TOM Transmission Operations Model database DFMS Distribution Facilities Management System Distribution Operators CADS TOM/UIB Interface ICCP/UIB Interface EMS/UIB Interface Trans & Power Operators RTUs

14. n 1996 - selling the project n 1997 - designing the bus KCPL CIM/UIB Project Timeline n 1998 - implementing the simple bus n 1999 - deploying the first simple bus n 2000 - sending out the SISCO fleet?? Observations: n EVERYTHING takes longer than you expect n being standards-based is worth the pain

15. n Review of integration strategies n Key UIB design concepts CIM/UIB Project UIB Philosophies

16. Possible Integration Strategies Point-to-point interfaces 1 interface per source/destination pair Central Database 1 interface between each application and the database  cleaner, but leads to the database “kitchen sink” problem  no support of application- to-application interaction  solves short term problem, but each subsequent application addition becomes more difficult

17. The Integration Framework Strategy Integration Bus 1 interface between each application and the integration framework Observation: n integration frameworks make integration easier, not easy  applications are autonomous  interface to bus is standard  shared data is modeled and is extensible

18. n The integration problem – stand-alone applications – sharing info about / making requests related to business objects CIM/UIB Project UIB Key Concept #1 Application AApplication BApplication C business objects

19. CIM/UIB Project UIB Key Concept #2 n Data sharing – is done by announcements of changes related to business objects called events – which are passed over the bus from a supplier application to one or more consumer applications Application A (supplier) Application B (consumer) Application C (consumer) x X xx

20. CIM/UIB Project UIB Key Concept #3 Application A (server) Application B (client) Application C x X x n Inter-application communication – is accomplished via business object-related request / replies – requests are passed over the bus from one client application to one server application ?

21. CIM/UIB Project UIB Key Concept #3 Application A (server) Application B (client) Application C x X x n Inter-application communication – replies return information or acknowledgement to the client ?

22. CIM/UIB Project UIB Key Concept #4 Application A (supplier) Application BApplication C x X n Applications are blissfully unaware of the identity of other applications – suppliers issue events to the bus

23. Application AApplication B Application C (consumer) x n Applications are blissfully unaware of the identity of other applications – consumers receive events from the bus CIM/UIB Project UIB Key Concept #4

24. Application AApplication B (client) Application C x X ? n Applications are blissfully unaware of the identity of other applications – clients make requests of the bus CIM/UIB Project UIB Key Concept #4

25. Application A (server) Application B (client) Application C x X x ? n Applications are blissfully unaware of the identity of other applications – except, perhaps, when servers reply CIM/UIB Project UIB Key Concept #4

26. n Applications are blissfully unaware of the identity of other applications – therefore, adding an application requires no change to any existing application Application AApplication BApplication C Application D x x CIM/UIB Project UIB Key Concept #4

27. Application A SUPPORT Application BApplication C n Applications have roles – they can be event announcers and request servers in their support role x x X CIM/UIB Project UIB Key Concept #5

28. Application A SUPPORT Application B INTEREST Application C INTEREST n Applications have roles – they can be event consumers and/or request clients in their interest role x xxx x X X ? CIM/UIB Project UIB Key Concept #5

29. Application A SUPPORT Application B SUPPORT/ INTEREST Application C INTEREST n Applications have roles – they can be both! x xxx x X X ? Y Y ? Y Y Y CIM/UIB Project UIB Key Concept #5

30. Application AApplication BApplication C n Most applications have an internal model – and the job of the interface is to translate business object information from the application’s internal model to the bus model (or vice versa) interface CIM/UIB Project UIB Key Concept #6

31. n When applications interact in any UIB deployment – the message package and the interaction mechanics are the same – only the contents of the event or request package change CIM/UIB Project UIB Key Concept #7

32. UIB Deployment 1 Application CApplication BApplication A UIB Deployment 2 Application ZApplication YApplication X CIM/UIB Project UIB Key Concept #7

33. Information Exchange Model n Business objects – are modeled in an OO way – are described in classes that have attributes, events and methods and relationships – have a model, the Information Exchange Model, that is “understood” by the participating applications – whose reference can be a standard…like the CIM! Class Foo attribute1 method1 event1 event2 Class FooToo attribute1 event1 event2 event3 CIM/UIB Project UIB Key Concept #8

34. n Adding to the interaction – requires modifications only to the business object model and to involved / interested application interfaces – does not affect existing applications that have no interest Application A interface Application B interface Application C interface Information Exchange Model Class Foo Class FooToo interface CIM/UIB Project UIB Key Concept #9

35. EMS Energy Management System Utility Integration Bus (UIB) Trans Ops Model KCPL-wide Desktop Access Power Pool KCPL CIM / UIB Project DFMS/UIB Interface ICCP Inter-Control Center Communications Protocol package TOM Transmission Operations Model database DFMS Distribution Facilities Management System Distribution Operators CADS TOM/UIB Interface ICCP/UIB Interface EMS/UIB Interface Trans & Power Operators RTUs