IEC 62746-10-3:2018 defines and describes methods and example XML artefacts that can be used to build a conformant adapter to enable interoperation between a utility distributed automation or demand response (DR) system based on the IEC common information model (CIM) and a utility smart grid user interface (SGUI) bridge standard (e.g., IEC 62746-10-1) to a customer facility. The scope is restricted to a method to define payload mappings between any specific CIM profile that contains DR\/DER information models and the SGUI bridge standards including IEC 62746-10-1. <\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 5<\/td>\n | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 4 Abbreviated terms 5 Connecting facility management and grid operations 5.1 Business and functional requirements for the adapter 5.2 Adapter benefits <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 5.3 Interoperation overview 5.3.1 General 5.3.2 Grid operations standards 5.3.3 Customer facility standards 5.3.4 Smart grid user interface (SGUI) <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 5.3.5 Role of the bridge and adapter Figures Figure 1 \u2013 The smart grid user interface (SGUI) as a blue bar betweengrid operations and customer facility management and control <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 5.4 Interaction model for interoperability Figure 2 \u2013 Adapter and IEC 62746-10-1 as an example SGUI bridge Tables Table 1 \u2013 Actors and key standards <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 5.5 Adapter deployments Figure 3 \u2013 Actors in grid, adapter, and facility domains, usingIEC 62746-10-1 as the SGUI bridge standard <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6 Constructing the adapter 6.1 General considerations Figure 4 \u2013 Grouping adapters with grid actor (left hand side) orwith a facility actor (right hand side) <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | Figure 5 \u2013 Two transformation paths from CIM DR profile (upper left)to SGUI bridge standard (lower right) <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 6.2 Adapter protocol and message type 6.3 Namespace and version management 6.4 Subjects of the adapter Figure 6 \u2013 Transforming CIM DR model profiles into XML schema <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 6.5 Implementing the adapter 6.5.1 General 6.5.2 Step one: Determine information model for SGUI end 6.5.3 Step two: Determine information model for grid operations end 6.5.4 Step three: Build XML schema for CIM DR profile 6.5.5 Step four: Build XML transformation between grid operations and SGUI <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 6.5.6 Step five: Develop, test and deploy the adapter 6.5.7 Changing the adapter implementation to use the UML-to-UML-first path 7 Example transformation (informative) 7.1 General <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 7.2 Notes on transformation 7.2.1 General Figure 7 \u2013 Graphical XSLT mapping between CIM ResourceDeployment sample messagebased on IEC 62325-301:2018 and IEC 62746-10-1 EiEvent <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 7.2.2 Transformation functions that do not draw on the CIM DR schema 7.2.3 Transformation functions that draw on business and implementation context <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.2.4 Transformation functions for detailed signal name, type, and ID 7.2.5 Transformation function that converts CIM date time intervals to the equivalent SGUI bridge standard intervals 7.2.6 Other information mapping issues <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | Annex A (informative)XML artefacts for standard adapters A.1 General A.2 Adapter example CIM XML artefacts A.3 Adapter example OpenADR XML artefacts A.4 XSLT transform xml artefact <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | Annex B (informative)Details for mapping and adaptation B.1 Time interval mapping function B.2 Mapping functions related to mRIDs B.3 Business context mapping functions B.4 Other mapping functions <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | Annex C (informative)Considerations for adapter implementers C.1 Overview C.2 Notes on information model for CIM endpoint C.3 Notes on information model for SGUI-facing endpoint C.4 Interfaces and protocols C.5 Service requests and verbs in IEC 61968-100 and SGUI standards <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | Table C.1 \u2013 Verbs comparison (source: OASIS Energy Interoperation 1.0) Table C.2 \u2013 Message type comparison <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Systems interface between customer energy management system and the power management system – Open automated demand response. Adapting smart grid user interfaces to the IEC common information model<\/b><\/p>\n |