Utility Integration Bus Standard Middleware Utility Specific Integration
Utility Integration Bus Standard Middleware + Utility Specific Integration (not secret) Sauce Copyright 1998, 1999 Systems Integration Specialists Company, Inc. All Rights Reserved 1
Objectives of UIB • Provide utility specific integration features missing from DCOM and CORBA. • Facilitate integration without requiring reprogramming. • Create an environment where skrinkwrapped products can be integrated. 2
The UIB Specification is • A set of middleware requirements • A set of middleware use specifications • A set of utility specific services 3
UIB Architecture APPLICATION UTILITY COMMON SERVICES OFF THE SHELF MIDDLEWARE Utility Applications Utility Specific Services and Specifications CORBA or DCOM 4
UIB features • Can be run over different middleware implementations • Allows for direct access to middleware • Provides an environment for integration of utility applications 5
UIB Requirements of Middleware • • • Persistent Message Queuing Remote Procedure Calls Life cycle Services Transaction Services Security Services Other standard distributed objects services 6
Why not just use Middleware? Answer: Utilities need more! 7
Utility Business Objects • Many different types • Are long lived (ie monitored continually instead of short live transactions) • Attributes are distributed in existing legacy applications 8
An Object Instance (e. g. SISCOMeter) Owner Billing Address Rate Structure Last Calibration Meter. ID Usage 9
Typical Middleware Solution Aggregate or Proxy Object Instance From Independent Sources CORBA or DCOM 10
Utilities really need: Decomposed Objects Attributes directly available from multiple sources. CORBA or DCOM This requirement has several design impacts! 11
Example: Information in Legacy Applications DB CIS AMR SISCOMeter Maintenance 12
UIB is designed for: • Coarse Objects and Distributed Attributes – IDLs to UIB services – Business Objects (e. g. breaker, capbank controller, meter, cis) are not expressed at the application interface. • Sending and receiving messages – UIB defines a set of standard messages – Allows for future message expansion 13
Utility Specific Services • ID Management – Create/Delete – Alias – Information Exchange Model support • Error Recovery 14
Specific Examples • How to subscribe for object class events as opposed to object instance events. • How to detect loss of information and information sources. • How to dynamically create a “directory” of information consumers and publishers. • How to recover and resync components 15 that have been off the bus.
Solution: OID/XID Hierarchy Type Standard Private Authority Type. Of. Class ORGID SUBORG Class. ID Instance. ID Class. Value Inst. Value 16
Why Alias? Less Filling Tastes Great Its Object B Its Object A UIB 2 UIB 1 Need One View, Not Two ! 17
UIB Concept of Context Test Online Need Standard Context: - Online - Test - Simulation - Others. . . Deployment Runtime Need Non-Standard Contexts 18
Models on the BUS • • Deployment Models Run time Models Information Exchange Model Reference Model 19
What is an IEM? • Defines information flow – Message Dictionary – Message Routing Model – Information Filtering IEM allows components to be written without knowing before hand who will supply or consume pieces (allows third party subscription) 20
Meta. Schema Overview Messaging Class Instance 21
Terminology 22
Class Object Class Component Class Name ID 1 N Attribute Class Attribute Name ID 1 1 Name ID Units 23
Examples of Business Objects • Class – Switch • • Fuse Breaker Manual Disconnector • Instance – Breaker • B 1 in sub 1 • B 2 on T 1 • etc. . Business Objects have Attributes! 24
Attribute Instance = Object Instance Name ID Object. Inst. ID + Attribute. ID Object Class Name ID 1 N Attribute Class Attribute Name ID 1 1 Name ID Units 25
Breaker Attribute Example: • • • Status (OPEN/CLOSED) Vendor Cost Number of Operations etc. . 26
Run. Time and Deployment • Deployment = Expected • Runtime = Actual – Used to determine which attributes are actually being supported • Is tracked on Context/Attribute Instance Basis 27
Messages • UIB Standard Messages • Other Standard Messages • User Defined Messages - Most Interesting! 28
Messages (cont. ) Message Definitions/ Templates (Class) Header Filterable Binary Topics ID/Value Attribute Inst. Message Based Sets OF 29
MIID is. . • MCID • Source CIID of component issuing message • Sequence number generated from issuing component. All found in header of messages. . . 30
UIB is Reference Model Independent (used by components but not managed by the bus) CIM Reference Model EMS ERP Reference Model Work Management ERP Connector 31
Conclusion Documents and Presentations available from: ftp: //ftp. sisconet. com/outgoing/uib 32
- Slides: 32