0
Integrating Utility Operations and Business Management (ERP)  Copyright 2000, Systems Integration Specialists Company, In...
How to Exchange Information with
Topics to be Covered <ul><li>Why Integrate? </li></ul><ul><li>Why ERP? </li></ul><ul><li>The Integration Issues </li></ul>...
Why Integrate (Use Case) The Customer
Utilities Provide: Power Tertiary Services Restoration and  Repair Services Contracted Services Requires
Contracted Service Failure Planning Financial Materials ERP Customer Service (CIS) Upset Customer Call Request Work Order ...
Other Reasons
Utilities Have: <ul><li>Normal Business Concerns (e.g. Accounting, warehousing, ERP, etc...). </li></ul><ul><li>Government...
Utilities Have (cont.) <ul><li>Wide Geographic delivery areas </li></ul><ul><ul><li>Infrastructure is distributed </li></u...
Different Information Schemas MFG Serial Number Test Results Certification Date of Production Rating DIST Utility Order fo...
Different Information Even in Utility WH SE MFG DIST Serial Number Price Date of Delivery Test Results Certification Date ...
Different Information Even in Utility WH SE MFG DIST Serial Number Price Date of Delivery Test Results Certification Date ...
Where did ERP come From?
First there was paper! Human Resources Production Order Entry
Then Came: MRP Human Resources Order Entry Production  Planning
Then came ERP Human Resources Workflow Financial Accounting Materials Management Sales and Distribution Fixed Asset Manage...
Internally? Database * MetaData * Instance * Data Similar to EMS’s MetaData Rules Interfaces
Information Exchange by: <ul><li>Manual Entry </li></ul><ul><li>Proprietary Interfaces </li></ul><ul><ul><li>No two vendor...
Wrappering of Proprietary Interface <ul><li>Oracle </li></ul><ul><li>TSI Software </li></ul><ul><li>IBM </li></ul><ul><li>...
Enter Open Access Group (OAG) <ul><li>Consortium of ERP Vendors </li></ul><ul><li>Charter to define information Exchange b...
<ul><li>American Software, Inc. </li></ul><ul><li>AT&T Wireless </li></ul><ul><li>Bluestone </li></ul><ul><li>CANDLE Corp....
OAG Information <ul><li>http://www.openapplications.org/ </li></ul><ul><ul><li>OAMAS - Interface Specification/Architectur...
Sample Messages <ul><li>Sync Customer </li></ul><ul><li>Sync Supplier </li></ul><ul><li>Process PO </li></ul><ul><li>Updat...
Example DTD
XML Support being Announced <ul><li>SAP </li></ul><ul><li>Peoplesoft </li></ul><ul><li>IBM </li></ul><ul><li>Oracle </li><...
OAG Does Not Specify How to Exchange XML!
Parallel Activities Yield Similar Results <ul><li>EPRI CCAPI Project </li></ul><ul><ul><li>Message based information excha...
No Nirvana Yet! CIM/ERP MetaData Mismatch Public/Private Data Issues Political Issues Standardized Interface Needed
Adapters/Wrappers still Needed! Service Transformation * Publish/Subscribe *Request/Response MetaData/ Data Transformation
Message Bus must support: <ul><li>Publish/Subscribe </li></ul><ul><li>Request/Response </li></ul><ul><li>Publish Request/D...
Why Publish/Subscribe? <ul><li>Decouples applications from the data sources. </li></ul><ul><ul><ul><li>Sources of data do ...
Publish/Subscribe Model Publishing App Publishing App Publishing App Message Bus A B C D D E Subscribing App A B Subscribi...
How to Construct a Message Bus?
A Message Bus is: <ul><li>A set of middleware requirements </li></ul><ul><li>A set of middleware use specifications </li><...
Possible Architecture CORBA or DCOM Utility Applications Utility Specific Services and Specifications APPLICATION UTILITY ...
Architectural  features <ul><li>Can be run over different middleware implementations  </li></ul><ul><li>Allows for direct ...
Requirements of Middleware  <ul><li>Persistent Message Queuing </li></ul><ul><li>Life cycle Services </li></ul><ul><li>Tra...
Why not just use Middleware? Answer: Utilities need more!
Utility Objects are: <ul><li>Many different types </li></ul><ul><li>Are long lived (ie monitored continually instead of sh...
Owner Billing Address Rate Structure Usage MeterID Last Calibration An Object Instance (e.g. SISCOMeter)
Typical Middleware Solution From Independent Sources Aggregate or Proxy Object Instance CORBA or DCOM
Utilities really need: Decomposed Objects CORBA or DCOM Attributes directly available from multiple sources. This requirem...
Example: Information in Legacy Applications AMR/ERP DB CIS Maintenance SISCOMeter
XML Messaging Allows Messaging Technology Integration of Various Technologies without Object Gateways IIOP Notif. CORBA JM...
Messages need to be exchanged Through Standard Interface!
The Generic Interface Definition (GID) <ul><li>A standardized API to used to wrap applications and middleware. </li></ul><...
Open messaging and adapter architecture Supplied by SISCO  or others Supplied by Neon, Tibco, TSI, Oberon, Oracle, etc. GI...
The GID - An open approach <ul><li>SISCO,  partners, CCAPI, and IEC are  actively working on defining the GID </li></ul><u...
GID based on OAG Concepts <ul><li>OAG work is technology neutral </li></ul><ul><ul><li>allows mappings to CORBA, JMS, and ...
GID and Messaging Allows Messaging Technology DCOM SQL Legacy CORBA EJB GID JMS COM C, C++ Wrap IIOP Notif.
Metadata and Data BOD’s and Beyond
EPRI Common  Information Model (CIM) Standardizes the Data Models
Common Model <ul><li>Provides a base for application integration and higher level applications </li></ul><ul><li>Future st...
Measurement Units? <ul><li>IEC indicates a preference for SI units. </li></ul><ul><ul><li>One Conversion per application <...
Data Definition Standardization <ul><li>Status and Control: </li></ul><ul><ul><li>IEC is Harmonizing between UCA, ICCP/TAS...
Now Possible to Integrate! <ul><li>Adoption of OAG Architecture </li></ul><ul><li>Adoption of B2B and OAG XML Messages </l...
Messages and Data are the key! <ul><li>Scaleable beyond current Distributed Object technologies. </li></ul><ul><li>Technol...
For Further Information Herbert Falk Systems Integration Specialists Company 6605 19½ Mile Road Sterling Heights, MI  4831...
Upcoming SlideShare
Loading in...5
×

Integrating Utility Operations and Business Management (ERP)

307

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
307
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Integrating Utility Operations and Business Management (ERP)"

  1. 1. Integrating Utility Operations and Business Management (ERP)  Copyright 2000, Systems Integration Specialists Company, Inc. All Rights Reserved
  2. 2. How to Exchange Information with
  3. 3. Topics to be Covered <ul><li>Why Integrate? </li></ul><ul><li>Why ERP? </li></ul><ul><li>The Integration Issues </li></ul><ul><li>Resolution </li></ul><ul><ul><li>OAG </li></ul></ul><ul><ul><li>XML Messages </li></ul></ul><ul><ul><li>CCAPI </li></ul></ul>
  4. 4. Why Integrate (Use Case) The Customer
  5. 5. Utilities Provide: Power Tertiary Services Restoration and Repair Services Contracted Services Requires
  6. 6. Contracted Service Failure Planning Financial Materials ERP Customer Service (CIS) Upset Customer Call Request Work Order Service Restoration Happier Customer Work Completion
  7. 7. Other Reasons
  8. 8. Utilities Have: <ul><li>Normal Business Concerns (e.g. Accounting, warehousing, ERP, etc...). </li></ul><ul><li>Government, public, and business ramifications for failure to deliver. </li></ul><ul><li>Government Regulations for audibility beyond pharmaceuticals. </li></ul><ul><ul><li>Environment, service delivery, power quality, etc... </li></ul></ul>
  9. 9. Utilities Have (cont.) <ul><li>Wide Geographic delivery areas </li></ul><ul><ul><li>Infrastructure is distributed </li></ul></ul><ul><ul><li>Equipment installed and maintained for 30 years or more. </li></ul></ul><ul><li>Uncertain business models </li></ul><ul><ul><li>Deregulation </li></ul></ul><ul><ul><li>High Merger Rate </li></ul></ul><ul><li>High throughput requirements greater than financial applications. </li></ul>
  10. 10. Different Information Schemas MFG Serial Number Test Results Certification Date of Production Rating DIST Utility Order for Restocking Causes Relay to Ship Price Charged Date of MFG Ship MFG Serial Number Date Rxd’d Cost Order to DIST Date of DIST Ship Price Charged MFG DIST Serial Number Price Date of Delivery Inherited
  11. 11. Different Information Even in Utility WH SE MFG DIST Serial Number Price Date of Delivery Test Results Certification Date of Production Rating Configuration MFG Serial Number Rating Init. Test Results Date in Service Location Reference CC Telemetry Date in Service Location Reference Rating CC Reference Warehouse Substation Engineering Control Center
  12. 12. Different Information Even in Utility WH SE MFG DIST Serial Number Price Date of Delivery Test Results Certification Date of Production Rating Configuration MFG Serial Number Rating Init. Test Results Date in Service Location Reference Maint. MFG Serial Number Rating Problem { Location Problem Desc. Date of Maint. Resolution }[ ] Current Location Test Results [ ] Config[ ]
  13. 13. Where did ERP come From?
  14. 14. First there was paper! Human Resources Production Order Entry
  15. 15. Then Came: MRP Human Resources Order Entry Production Planning
  16. 16. Then came ERP Human Resources Workflow Financial Accounting Materials Management Sales and Distribution Fixed Asset Management Others..... Industry Solutions
  17. 17. Internally? Database * MetaData * Instance * Data Similar to EMS’s MetaData Rules Interfaces
  18. 18. Information Exchange by: <ul><li>Manual Entry </li></ul><ul><li>Proprietary Interfaces </li></ul><ul><ul><li>No two vendor’s interfaces the same </li></ul></ul><ul><li>EDI </li></ul><ul><ul><li>Batch mode typically </li></ul></ul><ul><li>Others </li></ul>
  19. 19. Wrappering of Proprietary Interface <ul><li>Oracle </li></ul><ul><li>TSI Software </li></ul><ul><li>IBM </li></ul><ul><li>Etc... </li></ul>No Common Messages or Interfaces - $$$
  20. 20. Enter Open Access Group (OAG) <ul><li>Consortium of ERP Vendors </li></ul><ul><li>Charter to define information Exchange between business applications </li></ul><ul><li>Architecture has been defined </li></ul><ul><li>XML messages defined for exchange </li></ul>
  21. 21. <ul><li>American Software, Inc. </li></ul><ul><li>AT&T Wireless </li></ul><ul><li>Bluestone </li></ul><ul><li>CANDLE Corp. </li></ul><ul><li>Compaq </li></ul><ul><li>Component Software </li></ul><ul><li>Computer Associates </li></ul><ul><li>CrossWorlds Software </li></ul><ul><li>DATEV eG </li></ul><ul><li>Extricity Software </li></ul><ul><li>Ford Motor </li></ul><ul><li>Fortress Technologies </li></ul><ul><li>GloTech Solutions </li></ul><ul><li>Great Plains </li></ul><ul><li>HK Systems </li></ul><ul><li>I2 </li></ul><ul><li>IBM Adv. Mfg. Solutions Unit </li></ul><ul><li>Indus International </li></ul><ul><li>Integrated Systems & Services </li></ul><ul><li>J.D. Edwards </li></ul><ul><li>Lockheed Martin </li></ul><ul><li>Lucent Technologies </li></ul><ul><li>Microsoft </li></ul><ul><li>NEC Corporation </li></ul><ul><li>Netfish </li></ul><ul><li>ObTech </li></ul><ul><li>OnDisplay </li></ul><ul><li>Oracle Corporation </li></ul><ul><li>PCS </li></ul><ul><li>PeopleSoft, Inc. </li></ul><ul><li>PricewaterhouseCoopers </li></ul><ul><li>PSDI, Inc. </li></ul><ul><li>QAD, Inc. </li></ul><ul><li>Requisite </li></ul><ul><li>Robocom Systems Intl. </li></ul><ul><li>SAGA Software </li></ul><ul><li>SAP AG </li></ul><ul><li>Teklogix </li></ul><ul><li>Trilogy </li></ul><ul><li>TSI </li></ul><ul><li>USData </li></ul><ul><li>Vitria </li></ul><ul><li>Wonderware </li></ul><ul><li>webMethods </li></ul><ul><li>XML Solutions </li></ul>OAG Membership
  22. 22. OAG Information <ul><li>http://www.openapplications.org/ </li></ul><ul><ul><li>OAMAS - Interface Specification/Architecture </li></ul></ul><ul><ul><li>XML - Schema and Messages </li></ul></ul><ul><ul><ul><li>122 Messages currently defined (BODs) </li></ul></ul></ul><ul><ul><ul><li>26 Other Messages under Consideration </li></ul></ul></ul>
  23. 23. Sample Messages <ul><li>Sync Customer </li></ul><ul><li>Sync Supplier </li></ul><ul><li>Process PO </li></ul><ul><li>Update Delivery </li></ul><ul><li>Load invoice </li></ul><ul><li>Post Journal </li></ul><ul><li>Sync Salesorder </li></ul><ul><li>Sync Item </li></ul><ul><li>Sync Inventory </li></ul><ul><li>Add Requisition </li></ul><ul><li>Load Payable </li></ul>
  24. 24. Example DTD
  25. 25. XML Support being Announced <ul><li>SAP </li></ul><ul><li>Peoplesoft </li></ul><ul><li>IBM </li></ul><ul><li>Oracle </li></ul>
  26. 26. OAG Does Not Specify How to Exchange XML!
  27. 27. Parallel Activities Yield Similar Results <ul><li>EPRI CCAPI Project </li></ul><ul><ul><li>Message based information exchange supported </li></ul></ul><ul><ul><li>XML Messages being defined </li></ul></ul><ul><ul><li>Power System Metadata Defined </li></ul></ul><ul><ul><ul><li>EPRI/IEC Common Information Model </li></ul></ul></ul><ul><ul><li>OAG Architecture being supported </li></ul></ul>
  28. 28. No Nirvana Yet! CIM/ERP MetaData Mismatch Public/Private Data Issues Political Issues Standardized Interface Needed
  29. 29. Adapters/Wrappers still Needed! Service Transformation * Publish/Subscribe *Request/Response MetaData/ Data Transformation
  30. 30. Message Bus must support: <ul><li>Publish/Subscribe </li></ul><ul><li>Request/Response </li></ul><ul><li>Publish Request/Directed Response </li></ul><ul><li>Alarming/Transactions/Events </li></ul><ul><li>Standardized API </li></ul>
  31. 31. Why Publish/Subscribe? <ul><li>Decouples applications from the data sources. </li></ul><ul><ul><ul><li>Sources of data do not need to be configured with the destination of data. </li></ul></ul></ul><ul><li>Allows for the creation of redundancy and fault tolerance. </li></ul><ul><li>Reduces overhead of communications. </li></ul>
  32. 32. Publish/Subscribe Model Publishing App Publishing App Publishing App Message Bus A B C D D E Subscribing App A B Subscribing App A C Subscribing App A D Subscribing App A B C E
  33. 33. How to Construct a Message Bus?
  34. 34. A Message Bus is: <ul><li>A set of middleware requirements </li></ul><ul><li>A set of middleware use specifications </li></ul><ul><li>A set of utility specific services </li></ul>
  35. 35. Possible Architecture CORBA or DCOM Utility Applications Utility Specific Services and Specifications APPLICATION UTILITY COMMON SERVICES OFF THE SHELF MIDDLEWARE
  36. 36. Architectural features <ul><li>Can be run over different middleware implementations </li></ul><ul><li>Allows for direct access to middleware </li></ul><ul><li>Provides an environment for integration of utility applications </li></ul>
  37. 37. Requirements of Middleware <ul><li>Persistent Message Queuing </li></ul><ul><li>Life cycle Services </li></ul><ul><li>Transaction Services </li></ul><ul><li>Security Services </li></ul><ul><li>Other standard distributed objects services </li></ul>
  38. 38. Why not just use Middleware? Answer: Utilities need more!
  39. 39. Utility Objects are: <ul><li>Many different types </li></ul><ul><li>Are long lived (ie monitored continually instead of short live transactions) </li></ul><ul><li>Attributes are distributed in existing legacy applications </li></ul>
  40. 40. Owner Billing Address Rate Structure Usage MeterID Last Calibration An Object Instance (e.g. SISCOMeter)
  41. 41. Typical Middleware Solution From Independent Sources Aggregate or Proxy Object Instance CORBA or DCOM
  42. 42. Utilities really need: Decomposed Objects CORBA or DCOM Attributes directly available from multiple sources. This requirement has several design impacts!
  43. 43. Example: Information in Legacy Applications AMR/ERP DB CIS Maintenance SISCOMeter
  44. 44. XML Messaging Allows Messaging Technology Integration of Various Technologies without Object Gateways IIOP Notif. CORBA JMS EJB DCOM COM Legacy C, C++
  45. 45. Messages need to be exchanged Through Standard Interface!
  46. 46. The Generic Interface Definition (GID) <ul><li>A standardized API to used to wrap applications and middleware. </li></ul><ul><li>GID gives customers and application developers a greater independence from proprietary or specific broker/messaging implementations. </li></ul><ul><li>Lowers cost of wrapper deployment. </li></ul>
  47. 47. Open messaging and adapter architecture Supplied by SISCO or others Supplied by Neon, Tibco, TSI, Oberon, Oracle, etc. GID GID XML Messages Transport Supplied by SAP, Peoplesoft, Siemens, Telegyr, Alstom, Oracle, etc…. Application Proprietary OTS Connector EMS/DMS Connector
  48. 48. The GID - An open approach <ul><li>SISCO, partners, CCAPI, and IEC are actively working on defining the GID </li></ul><ul><li>Goal is to make the GID an IEC standard </li></ul><ul><li>GID complements the work being done in the Open Applications Group </li></ul>
  49. 49. GID based on OAG Concepts <ul><li>OAG work is technology neutral </li></ul><ul><ul><li>allows mappings to CORBA, JMS, and COM </li></ul></ul><ul><li>Architecture separates content from interface: </li></ul><ul><ul><li>Business Object Documents </li></ul></ul><ul><ul><ul><li>Nouns, Verbs, Business Data Area </li></ul></ul></ul><ul><ul><li>Interface is content neutral CCAPI and IEC leadership have agreed. </li></ul></ul>
  50. 50. GID and Messaging Allows Messaging Technology DCOM SQL Legacy CORBA EJB GID JMS COM C, C++ Wrap IIOP Notif.
  51. 51. Metadata and Data BOD’s and Beyond
  52. 52. EPRI Common Information Model (CIM) Standardizes the Data Models
  53. 53. Common Model <ul><li>Provides a base for application integration and higher level applications </li></ul><ul><li>Future standards work will leverage the CIM </li></ul><ul><li>Tools available to centrally manage the meaning and location of data </li></ul>
  54. 54. Measurement Units? <ul><li>IEC indicates a preference for SI units. </li></ul><ul><ul><li>One Conversion per application </li></ul></ul><ul><ul><li>HMI units display a local issue. </li></ul></ul>$185M of Problems if not addressed!
  55. 55. Data Definition Standardization <ul><li>Status and Control: </li></ul><ul><ul><li>IEC is Harmonizing between UCA, ICCP/TASE.2, and CIM </li></ul></ul><ul><li>Quality Codes </li></ul><ul><ul><li>Recommend IEC 61850-7-3 definitions. </li></ul></ul><ul><li>Time Base: GMT </li></ul>
  56. 56. Now Possible to Integrate! <ul><li>Adoption of OAG Architecture </li></ul><ul><li>Adoption of B2B and OAG XML Messages </li></ul><ul><li>Development and Standardization of Utility specific XML messages. </li></ul><ul><li>Standardization at IEC </li></ul>
  57. 57. Messages and Data are the key! <ul><li>Scaleable beyond current Distributed Object technologies. </li></ul><ul><li>Technology Neutrality </li></ul><ul><li>Minimizes API requirements. </li></ul>
  58. 58. For Further Information Herbert Falk Systems Integration Specialists Company 6605 19½ Mile Road Sterling Heights, MI 48314 Ph: 586-254-0020, Fx: 586-254-0053 URL: http://www.sisconet.com Email: herb@sisconet.com Electronic Copy of Presentation: http://www.sisconet.com/uib.htm
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×