{"id":420725,"date":"2024-10-20T06:32:34","date_gmt":"2024-10-20T06:32:34","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-iec-ts-62056-6-92016-2\/"},"modified":"2024-10-26T12:14:35","modified_gmt":"2024-10-26T12:14:35","slug":"bsi-pd-iec-ts-62056-6-92016-2","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-iec-ts-62056-6-92016-2\/","title":{"rendered":"BSI PD IEC\/TS 62056-6-9:2016"},"content":{"rendered":"
This part of IEC 62056, which is a Technical Specification, describes how in the utility environment an ERP system or a third party system can exchange information with a metering system. In particular, this Technical Specification covers the mapping between information interchange messages of a CIM-based ERP or third party system and a DLMS\/COSEM-based metering system.<\/p>\n
A typical metering system would comprise a HES and end devices such as meters as well as tariff and load control devices. There may be intermediate devices in the metering system such as NNAPs and LNAPs, as described in the smart metering architecture of IEC 62056-1-0. These intermediate devices are outside of the scope of this Technical Specification.<\/p>\n
CIM ReadingType, EndDeviceControlType and EndDeviceEventType codes as specified in IEC 61968-9 are mapped to OBIS codes as specified in IEC 62056-6-1.<\/p>\n
In some cases the CIM models and COSEM models are differently structured, in which case it is not possible to provide a one-to-one mapping between the OBIS codes and the CIM data type codes. In these cases the mapping is thus performed between the CIM UML object attributes and the COSEM object attributes (see 4.3.4 UC3).<\/p>\n
CIM EndDeviceControlType codes as specified in IEC 61968-9 are mapped to COSEM IC attributes and methods as specified in IEC 62056-6-2.<\/p>\n
CIM verbs and nouns as specified in IEC 61968-9 are mapped to DLMS service requests and responses as specified in IEC 62056-5-3.<\/p>\n
Only the most commonly used UCs are given in order to illustrate possible applications. Extensions may be considered in future editions.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
6<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
8<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 3 Terms, definitions and abbreviations 3.1 Terms and definitions 3.2 Abbreviations 3.3 Notation and terminology <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 4 Reference environment 4.1 General reference architecture Figures Figure 1 \u2013 General reference architecture <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 4.2 Reference use cases \u2013 Generalized use case Figure 2 \u2013 Generic use case <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 4.3 Use case examples 4.3.1 General 4.3.2 UC1: ReadMeterOnSchedule Figure 3 \u2013 UC1: ReadMeterOnSchedule <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 4.3.3 UC2: ReadMeterOnDemand Figure 4 \u2013 UC2: ReadMeterOnDemand <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 4.3.4 UC3: ConfigureTariffRemotely Figure 5 \u2013 UC3: ConfigureTariffRemotely <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 4.3.5 UC4: DisconnectReconnectRemotely Figure 6 \u2013 UC4: DisconnectReconnectRemotely <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 4.3.6 UC5: ManageLoadByRelayControl Figure 7 \u2013 UC5: ManageLoadByRelayControl <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4.3.7 UC6: ReportOnQualityOfSupply Figure 8 \u2013 UC6: ReportOnQualityOfSupply <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4.3.8 UC7: ManageLoadByDemandLimits Figure 9 \u2013 UC7: ManageLoadByDemandLimits <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 4.3.9 UC8: SynchronizeClock Figure 10 \u2013 UC8: SynchronizeClock <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 4.3.10 UC9: ChangeFirmware Figure 11 \u2013 UC9: ChangeFirmware <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 4.3.11 UC10: RegisterMeter Figure 12 \u2013 UC10: RegisterMeter Tables Table 1 \u2013 UC10 RegisterMeter <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 4.3.12 UC11: SuperviseMeter 5 CIM \u2013 DLMS\/COSEM translation 5.1 CIM message construct 5.2 CIM verb mapping Figure 13 \u2013 UC11: SuperviseMeter <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 5.3 CIM noun mapping Table 2 \u2013 CIM verb mapping to DLMS\/COSEM service Table 3 \u2013 CIM noun mapping to DLMS\/COSEM service parameters <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.4 CIM data type mapping 5.5 OBIS code mapping to CIM ReadingType enumerated code Table 4 \u2013 CIM data type mapping to DLMS\/COSEM service parameters <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | Table 5 \u2013 OBIS value group C code mapped to CIM ReadingType enumerated attribute values <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Table 6 \u2013 OBIS values mapped to CIM ReadingType enumerated codes <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 5.6 OBIS code mapping to CIM EndDeviceControlType enumerated code <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Table 7 \u2013 OBIS code mapped to CIM EndDeviceControlType enumerated code <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 5.7 OBIS code mapping to CIM EndDeviceEventType enumerated code for UC8, UC9 and UC11 5.8 CIM attributes mapping to DLMS\/COSEM attributes for UC3 Table 8 \u2013 OBIS code mapped to CIM EndDeviceEventType enumerated code for UC8, UC9 and UC11 <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Table 9 \u2013 PricingStructureConfig mapped to DLMS\/COSEM attributes for UC3 <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Annex A (informative) Example of a 2-rate TOU tariff A.1 DLMS\/COSEM model of a 2-rate TOU tariff example <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Figure A.1 \u2013 DLMS\/COSEM model of a 2-rate TOU tariff example <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | A.2 DLMS\/COSEM model example of load management by demand limits Figure A.2 \u2013 DLMS\/COSEM model example of load management by demand limits <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Electricity metering data exchange. The DLMS\/COSEM suite – Mapping between the Common Information Model message profiles (IEC 61968-9) and DLMS\/COSEM (IEC 62056) data models and protocols<\/b><\/p>\n |