Scott Neumann November 1, 2009

Slides:



Advertisements
Similar presentations
Chapter 2: Basic Elements of C++
Advertisements

SG Systems - Service Definition Team Chair: Gerald Gray, CIMple Integrations Co-Chair: Shawn Hu, Xtensible Solutions
May 3, 2010OpenSG – SG Systems – Service Definitions1 Chair: Gerald Gray, CIMple Integrations Co-Chair: Shawn Hu, Xtensible Solutions.
IEC TC57 WG14 Scott Neumann December 8, IEC TC57 WG14 Developing IEC Focus is to describe the information exchanges between systems (i.e.
© 2010 EnerNex Corporation. All Rights Reserved. CIM Test Development Process EPRI Project January 2011.
Systems Integration Specialists Company, Inc. The Standards Based Integration Company © Copyright 2009 SISCO, Inc. IOP Status Report CIMug Meeting Margaret.
October 19, 2009OpenSG - AMI-ENTERPRISE1 The Framework, Standards, and Plans AMI-Enterprise Service Definition Team.
Systems Analysis I Data Flow Diagrams
OneM2M-MP Data_Model_Repository Establishing Data Model Repository for oneM2M Group Name: Method and Procedure Sub-commitee Source: WG3 chair.
Interoperability Tests for IEC Scott Neumann November 12, 2009.
Systems Integration Specialists Company, Inc. The Standards Based Integration Company © Copyright 2010 SISCO, Inc – 9 Meter Reading and Control.
Project CIM Test Development Process John Simmins Weekly Status and Planning Meeting 2/1/2011.
J-L Sanson, A. Maizener Cimug © Zamiren CimConteXtor A. Maizener : J.L. Sanson : Credit to Sebastien.
© 2010 EnerNex Corporation. All Rights Reserved. CIM Test Development Process EPRI Project January 2011.
CIM Test Methodology Overview John Simmins 5/24/2011.
SG Systems - Service Definition Team Chair: Gerald Gray, Guiding Principle Consulting Co-Chair: Shawn Hu, Xtensible Solutions.
CIM Test Methodology Overview John Simmins 5/3/2011.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
AMI -ENT Service Definition Team Step-by-Step Modeling and Artifacts Generation Process.
TOSCA V1.1: Variants of Collections of Specs. Spec Structure – Variant A The XML Simple Profile is a subsetting of the V1.1 spec but compliant with the.
1 © 2003, Cisco Systems, Inc. All rights reserved. DMTF and Cisco Profile overview/comparison August 17, 2005.
Images were sourced from the following web sites: Slide 2:commons.wikimedia.org/wiki/File:BorromeanRing...commons.wikimedia.org/wiki/File:BorromeanRing...
1 January 31, Documenting Software William Cohen NCSU CSC 591W January 31, 2008.
Stephen Banghart Dave Waltermire
General Cost Center Planning
Stakeholders Meeting High-Level Update on the Forthcoming Consultations Incorporating ComFrame Text with Revised Insurance Core Principles (ICPs) La.
9101 Forms July 20-21, Revision Team Paul Dionne
Systems Analysis and Design
INCOSE Usability Working Group
XML Schema for WIRED XML Detector Description Workshop
CIM Test Development Process
Introduction to HTML5.
ISO
Introduction to Unified Modeling Language (UML)
“SG-Systems” (Smart Grid – Operational Applications Integration) “Boot Camp” Overview Brent Hodges, Chair, SG-Systems Greg Robinson, Co-Chair, SG-Systems.
Markle Site Map + Wireframes.
NITS Review Scoping Document.
IEC TC57 Smart Grid Activities
Draft Recommendation Overview
Organizing Semantics For Effective Enterprise Application Integration
Introduction to ISO 9000 ISO
WG Technical Editor’s Report
S-127 – Marine Traffic Management Release Candidate NIPWG 6 30 January 2019 Raphael Malyankar Eivind Mong Sponsored by IHO.
UMIGs IM and BR-EI Documentation Structure Review
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Main changes in 2018 revision of ISO/IEC Directives, Part 2
Epic Referral Processing
UMIGs IM and BR-EI Documentation Structure Review
UMIGs IM and BR-EI Documentation Structure Review
Project Management Body of Knowledge
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
WG Technical Editor’s Report
PN UNC AMR Topic Workgroup Meeting 14 – Meter Reading
Web-based Imaging Management System Working Group - WIMS
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Interoperability Test Enumerations for IEC
Introduce myself & around table
Fiscal policy program Presented by Cindy Draper, Fiscal Policy Officer – Training Days 2018 Introduce myself This session is to provide an overview of.
InterOp Technical Notes
Interoperability Test Message Patterns for IEC
Error Handling for IEC Scott Neumann September 29, 2009.
Interoperability Test Message Patterns for IEC
ISO and TR Update for FDA Regulated Industries
InterOp Events Scott Neumann October 25, 2009.
Interoperability Test Message Patterns for IEC
Scott Neumann December 8, 2005
Presentation transcript:

Scott Neumann November 1, 2009 IEC 61968-9 Errata Scott Neumann November 1, 2009

Introduction The purpose of this presentation is to document errors discovered in the FDIS for IEC 61968-9 This should provide key input to the second edition IEC 61968-9

Use of ‘Get’ for MeterReadings Some sequence diagrams incorrectly use ‘create’ instead of ‘get’ for requesting meter readings Specific figures in error include: Section 5.4.2.3, figure 25 Section 5.4.2.5, figure 27 Section 5.5.2.4, figure 34 Section 5.5.2.4, figure 35 Section 5.6.2.2, figure 39 Section 5.8.1, figure 47 The following 6 slides provide the revised sequence diagrams correcting verb usage It is still important to note that these diagrams are examples and are not normative

Figure 25

Figure 27

Figure 34

Figure 35

Figure 39

Figure 47

EndDeviceAssets Profile The following elements are needed, but are not consistent with stricter profile definition rules: MeterAsset.formNumber MeterAsset.kH MeterAsset.kR The profile will need to be revised to allow for a MeterAsset instead of a more generic EndDeviceAsset Seal.kind needs to be defined as an enumeration, not a reference This will impact future versions of the corresponding XSD in appendix H

CustomerMeterDataSet Profile The following elements are needed, but are not consistent with stricter profile definition rules: MeterAsset.ServiceCategories The profile will need to be revised to allow for a MeterAsset instead of a more generic EndDeviceAsset This will impact future versions of the corresponding XSD in appendix H

MeterReadings Profile Need to make Status a concrete type Need to note that ReadingTypes are optional, as in practice they do not need to be communicated Might potentially need to expand enumerations for units on ReadingTypes or remove them altogether

Notes on Profile Namespaces These are notes, not errata … IEC 61968-9 uses the http://iec.ch/TC57/2009 namespace Some legacy XSDs use a namespace that reflects 2007 The second edition of 61968-9 will use a 2010 or 2011 namespace as appropriate

CIM Issues Need to correct cardinality to make a DemandResponseProgram optional (i.e. 0:1|0:*)

Outside of 61968-9 In Message.xsd, Request.StartTime and EndTime are typed as a string, when they should be xsd:dateTime

More Information UISOL web site: http://uisol.com E-mail: sneumann@uisol.com EPRI Technical Report: ESB Implementation Profile Using IEC 61968