CIM – MultiSpeak Harmonization Update
•Télécharger en tant que PPTX, PDF•
1 j'aime•1,065 vues
A review of
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (9)
Similaire à CIM – MultiSpeak Harmonization Update
Similaire à CIM – MultiSpeak Harmonization Update (20)
CIM – MultiSpeak Harmonization Update
- 1. CIM – MultiSpeak Harmonization Update Dr. Gerald R. Gray Sr. Project Manager Enterprise Architecture and Integration EPRI
- 2. Agenda • Why harmonize? • Where we left off… • Current status • Lab integration © 2012 Electric Power Research Institute, Inc. All rights reserved. 2
- 3. Why harmonize? • While the standards evolved by supporting different constituencies, they cover the same domain • Learn how the standards are similar – Leverage best practices of each going forward • Develop integration guidance for systems integrators, utilities, vendors • Open vendors to additional markets “+” “o” © 2012 Electric Power Research Institute, Inc. All rights reserved. 3
- 4. Where we left off…2011 • EPRI report 1024443 – Focus: IEC 61968-9 Meter Reading and Control – 10 of 23 profiles • On Demand Meter Read service mapping • Developed MultiSpeak profile methodology CIM Profiles CustomerAccountConfig EndDeviceFirmware CustomerAgreementConfig MeterAssetConfig EndDeviceControls MeterReadSchedule EndDeviceEvents ServiceCategoryConfig ServiceLocationConfig SupplierConfig © 2012 Electric Power Research Institute, Inc. All rights reserved. 4
- 5. Day in the life… • Creating a harmonization profile – CIM and MultiSpeak are maintained in Enterprise Architect; UML • CIMEA – extension to Enterprise Architect – Select classes, attributes, associations – Maintains traceability – Generate the XSD • Validate/edit • Map to corresponding CIM profile © 2012 Electric Power Research Institute, Inc. All rights reserved. 5
- 6. Example: mspSupplierConfig • Added association from resource to contact © 2012 Electric Power Research Institute, Inc. All rights reserved. 6
- 7. Current Status • EPRI Report, 1026585, CIM-MultiSpeak Harmonization, 2nd Edition – Documented • Correlations • Suggested transformations • Gaps • All 23 IEC 61968-9 Meter Reading & Control 1st Profiles mapped – Feedback to IEC, MultiSpeak communities • IEC 61968-14 Technical Report, NWIP status – This will include IEC 61968-9 2nd Edition Profiles © 2012 Electric Power Research Institute, Inc. All rights reserved. 7
- 8. Lab Integration • EndDeviceEvent profile – Power Out/Ping • Meter to OMS • CIM/MultiSpeak translation at the ESB • Endpoints blissfully unaware of the transformation © 2012 Electric Power Research Institute, Inc. All rights reserved. 8
- 9. Acknowledgements • NRECA – Bob Saint • Gary McNaughton – Cornice Engineering • David Haynes – Aclara • Don Taylor – Itron • Michael Johnson, Elster • Dr. John Simmins - EPRI • TriState G&T • Synaptitude Consulting © 2012 Electric Power Research Institute, Inc. All rights reserved. 9
- 10. Together…Shaping the Future of Electricity © 2012 Electric Power Research Institute, Inc. All rights reserved. 10
Notes de l'éditeur
- Open vendors to new markets, e.g. MilSoft has a MultiSpeak interfaceIf a utility requires CIM, e.g. at the ESB, if MilSoft can pass an interop test with their MultiSpeak interface and a standard adapter…This report (and technical specification) will facilitate technology transfer and contribute to system being integrated in a consistent fashion.
- Q: What is a profile?A: A snapshot of the model. Usually used to define a useful “chunk” of work. Often used for messaging
- Equivalents are named msp…For example: EndDeviceEvents => mspEndDeviceEventsIn some cases abstract class will be added to the model as “placeholders” to construct the XSDMay add suggested associations for where classes, attributes exist in MultiSpeak, the association just doesn’t happen to match the CIMGuiding principle: Model driven development