Blue Book - Excerpt BB4.PDF

Reference number: EXCERPT FROM DLMS UA 1000-1:2001, Fourth Edition © Copyright 1997-2001 DLMS User Association

EXCERPT FROM

Companion Specificationfor Energy Metering

COSEM

Identification Systemand Interface Objects

DLMS User Association

device languagemessagespecification

DLMS UA, EXCERPT FROM COSEM Identification System and Interface Objects, Fourth Edition

DLMS User Association EXCERPT DLMS UA 1000-1 ed.4 2/43 © Copyright 1997-2001 DLMS User Association



Table of Contents1. Foreword.............................................................................................................................. 5

2. Scope ................................................................................................................................... 6

3. Introduction ......................................................................................................................... 73.1 Referenced Documents....................................................................................................... 73.2 Terms, Definitions and Abbreviations .................................................................................. 8

4. COSEM Interface Classes................................................................................................... 94.1 Basic Principles................................................................................................................... 94.1.1 Introduction ....................................................................................................................... 94.1.2 Class Description Notation.............................................................................................. 104.1.3 Common Data Types ...................................................................................................... 114.1.4 Data formats for date and time notation.......................................................................... 124.1.5 The COSEM server model .............................................................................................. 144.1.6 COSEM Logical Device................................................................................................... 154.1.7 Authentication Procedures .............................................................................................. 164.2 The interface classes ........................................................................................................ 174.2.1 Data (class_id: 1) ............................................................................................................ 184.2.2 Register (class_id: 3) ...................................................................................................... 184.2.3 Extended Register (class_id: 4) ...................................................................................... 204.2.4 Demand Register (class_id: 5)........................................................................................ 204.2.5 Register Activation (class_id: 6) ...................................................................................... 214.2.6 Profile Generic (class_id: 7) ............................................................................................ 214.2.7 Clock (class_id: 8)........................................................................................................... 214.2.8 Script Table (class_id: 9) ................................................................................................ 244.2.9 Schedule (class_id: 10)................................................................................................... 244.2.10 Special Days Table (class_id: 11) ................................................................................... 244.2.11 Activity Calendar (class_id: 20) ....................................................................................... 244.2.12 Association LN (class_id: 15).......................................................................................... 254.2.13 Association SN (class_id: 12) ......................................................................................... 254.2.14 SAP Assignment (class_id: 17)....................................................................................... 254.2.15 Register Monitor (class_id: 21) ....................................................................................... 254.2.16 Utility Tables (class_id: 26) ............................................................................................. 264.2.17 Single Action Schedule (class_id: 22) ............................................................................. 264.3 Maintenance of the Interface Classes ............................................................................... 264.4 Protocol related Interface Classes..................................................................................... 264.5 Using Short Names for accessing attributes and methods ............................................... 264.5.1 Guidelines for Assigning Short Names............................................................................ 274.5.2 Reserved base_names for Special COSEM Objects ...................................................... 274.6 Relation to OBIS ............................................................................................................... 274.6.1 Mapping of Data Items to COSEM Objects and Attributes .............................................. 284.6.2 Coding of OBIS Identifications ........................................................................................ 284.7 Previous Versions of Interface Classes ............................................................................. 28

5. COSEM Object Identification System (OBIS) .................................................................. 295.1 Introduction ....................................................................................................................... 295.2 Scope................................................................................................................................ 295.3 OBIS Object identification system structure ...................................................................... 29



5.3.1 Value group A ................................................................................................................. 305.3.2 Value group B ................................................................................................................. 305.3.3 Value group C................................................................................................................. 305.3.4 Value group D................................................................................................................. 305.3.5 Value group E ................................................................................................................. 305.3.6 Value group F ................................................................................................................. 305.3.7 Manufacturer specific codes ........................................................................................... 305.4 Value group definitions...................................................................................................... 315.4.1 Value group A ................................................................................................................. 315.4.2 Value group B ................................................................................................................. 315.4.3 Value group C................................................................................................................. 315.4.4 Value group D................................................................................................................. 335.4.5 Value group E ................................................................................................................. 365.4.6 Value group F ................................................................................................................. 385.4.7 Abstract objects .............................................................................................................. 385.4.8 Electricity-related General purpose objects..................................................................... 395.4.9 List objects...................................................................................................................... 415.4.10 Electricity data profile objects.......................................................................................... 415.5 Code presentation ............................................................................................................. 415.5.1 Reduced ID codes (e.g. for IEC 62056-21) ..................................................................... 425.5.2 Display ............................................................................................................................ 425.5.3 Special handling of value group F ................................................................................... 425.5.4 COSEM........................................................................................................................... 43



1. Foreword

Copyright

© Copyright 1997-2001 DLMS User Association.

This document is confidential. It may not be copied, nor handed over to persons outside the stan-dardisation environment.

The copyright is enforced by national and international law. The "Berne Convention for the Protec-tion of Literary and Artistic Works", which is signed by 121 countries world-wide, and other trea-ties apply.

Acknowledgement

The actual document has been established by a team of experts working for the meter manufac-turers DZG, Enermet, Schlumberger and Siemens, with input from other members of the DLMSUser Association and from working group members of standardisation bodies, e.g. IEC TC13WG14 and CEN TC294 WG2.

Status of standardisation

The actual edition 4 of this document combines the contents of draft IEC 62056-62 (Interface Ob-jects) and draft IEC 62056-61 (OBIS Object Identification System) submitted to IEC for FDIS cir-culation.


DLMS User Association EXCE © Copyright 199

2. Scope

This document specifies the functionalityof the meter which is available at its in-terface (internal issues concerning theimplementation are not covered by thespecification) and how the functions andthe data can be accessed from the out-side. The complex functionality of themeter is divided into generic buildingblocks. The COSEM specifications followa three step approach as illustrated inFigure 1:

Step 1:The meter model and data identi-fication (data model);

Step 2:The mapping of the model intoprotocol data units (pdu);

Step 3:The transportation of the bits andbytes through the communication chan-nel.

The data model uses generic buildingblocks to define the complex functionalityof the metering equipment. It provides aview of this functionality of the meter, asit is available at its interface(s). Themodel does not cover internal, imple-mentation specific issues. The communi-cation protocol defines how the data canbe accessed and exchanged.

• The COSEM specification specifies functionality of the meter is defined COSEM objects. This is defined in thcodes), identifying the COSEM object

• The attributes and methods of these messaging services of the Application

• The lower layers of the protocol trans

RPT DLMS UA 1000-1 ed.4 6/437-2001 DLMS User Association

Figure 1 –The three steps approach of COSEM:Modelling - Messaging - Transporting

metering domain specific interface classes. Theby the instances of these interface classes, callede first part of this document. Logical names (OBISs are defined in the second part of this document.

COSEM objects can be accessed and used via the layer.

port the information.

3. Transporting

C0 01 00 03 01 01 01 08 00 FF 02

2. Messaging

Protocol Services to access attributes and methods

ISO, IEC,...

Communication Protocol

Messages :Service_Id( Class_Id, Instance_Id, Attribute_Id/Method_Id )

Encoding: ( APDU )

1. Modelling COSEM Interface Objects

Register 0..n Class_id=3, Version=0Attribute(s) Data Type Min Max Def1. logical_name (static) octet-string2. value (dyn.) instance specific3. scaler-unit (static) scal_unit_typeMethod(s) m/o1. reset o

DLMS User Associatio

n



3. Introduction

Driven by the need of the utilities to optimise their business processes, the meter becomes moreand more part of an integrated metering and billing system. Whereas in the past the commercialvalue of a meter was mainly generated by its data acquisition and processing capabilities, nowa-days the critical issues are system integration and interoperability.

The Companion Specification for Energy Metering (COSEM) addresses these challenges by look-ing at the meter as an integrated part of a commercial process which starts with the measurementof the delivered product (energy) and ends with the revenue collection.

The meter is specified by its “behaviour” as seen from the utility's business processes. The formalspecification of the behaviour is based on object modelling techniques (interface classes and ob-jects). The specification of these objects forms a major part of COSEM.

The COSEM server model (comp. chapter 4.1.5) represents only the externally visible elements ofthe meter. The client applications that support the business processes of the utilities, of the cus-tomers and of the meter manufacturers make use of this server model. The meter offers means toretrieve its structural model (the list of objects visible through the interface), and provides accessto the attributes and specific methods of these objects.

The set of different interface classes (see chapter 4) form a standardised library from which themanufacturer can assemble (model) its individual products. The elements are designed such thatwith them the entire range of products (from residential to commercial and industrial applications )can be covered. The choice of the subset of interface classes used to build a meter, their instan-tiation and their implementation are part of the product design and therefore left to the manufac-turer. The concept of the standardised metering interface class library provides the different usersand manufacturers with a maximum of diversity without having to sacrifice interoperability.

The competitive energy markets require an ever-increasing amount of timely information concern-ing the usage of electrical energy. Recent technology developments enable to build intelligentstatic metering equipment, which are capable to capture, process and communicate this informa-tion to all parties involved.

For further analysis of this information, for the purposes of billing, load-, customer- and contractmanagement, it is necessary to uniquely identify all data in a manufacturer independent way col-lected manually or automatically, via local or remote data exchange.

The OBIS definition of Identification codes (see chapter 5) was based on:

draft DIN 43863-3 (December 1997), Electricity meters - Part 3: Tariff metering device as additional equip-ment for electricity meters - EDIS - Energy Data Identification System

3.1 Referenced DocumentsRef. TitleDLMS UA 1000-2 COSEM Three Layer Connection Oriented Architecture, Second Edition (2001)IEC 61268:1995 Alternating current static var-hour meters for reactive energy (classes 2 and 3)IEC 61334-4-41:1996 Distribution automation using distribution line carrier systems - Part 4: Data com-

munication protocols - Section 41: Application protocols - Distribution line messagespecification



Ref. TitleIEC 62056-21 Data exchange for meter reading, tariff and load control – Part 21: Direct local data

exchangeIEC 62056-31:1999 Electricity metering – Data exchange for meter reading, tariff and load control – Part

31- Using local area networks on twisted pair with carrier signallingIEC 62056-46 Electricity metering – Data exchange for meter reading, tariff and load control – Part

46 – Data link layer using HDLC-protocolIEC 62056-53 Electricity metering – Data exchange for meter reading, tariff and load control – Part

53- COSEM Application layerIEC 62056-61 Electricity metering – Data exchange for meter reading, tariff and load control – Part

61- OBIS Object Identification SystemIEC 62056-62 Data exchange for meter reading, tariff and load control – Part 62: Interface

ClassesANSI C12.19:1997 IEEE 1377:1998, Utility industry end device data tables

3.2 Terms, Definitions and AbbreviationsAbbreviation ExplanationAARE Application Association ResponseAARQ Application Association RequestACSE Application Control Service ElementAPDU Application protocol data unitASE Application Service ElementA-XDR Adapted Extended Data Representationbase_name The short_name corresponding to the first attribute (“logical_name”)of a COSEM object..Class_id Class identification codeCOSEM Companion Specification for Energy MeteringCOSEM object An instance of an interface classDLMS Distribution Line Message SpecificationGMT Greenwich Mean TimeHLS High Level SecurityIC Interface ClassIEC International Electrotechnical CommissionLLS Low Level SecurityLSB Least significant bitm mandatory, used in conjunction with attribute and method definitionsMSB Most significant bito optional, used in conjunction with attribute and method definitionsOBIS Object Identification SystemPDU Protocol data unitUTC Universal Time Co-ordinated



4. COSEM Interface Classes

4.1 Basic Principles

4.1.1 IntroductionThis section describes the basic principles on which the COSEM interface classes are built. It alsogives a short overview on how interface objects (instantiations of the interface classes) are usedfor communication purposes. Meters, support tools and other system components that followthese specifications can communicate with each other in an interoperable way.

Object modelling: for specification purposes this document uses the technique of object modelling.An object is a collection of attributes and methods.

The information of an object is organised in attributes. They represent the characteristics of anobject by means of attribute values. The value of an attribute may affect the behaviour of an ob-ject. The first attribute in any object is the "logical_name". It is one part of the identification of theobject.

An object offers a number of methods to either examine or modify the values of the attributes.Objects that share common characteristics are generalised as an interface class with a class_id.Within a specific class the common characteristics (attributes and methods) are described oncefor all objects. Instantiations of an interface class are called COSEM objects.

Manufacturers may add proprietary methods or attributes to any object, using negative numbers.

Figure 2 illustrates these terms by means of an example:

Figure 2 – An interface class and its instances

Register class_id=3logical_name: octet-stringvalue: instance specific...

logical_name = [1 1 3 8 0]value = 57…

Total PositiveReactive Energy: Register

logical_name = [1 1 1 8 0]value= 1483…

Total PositiveActive Energy: Register

Class Methods Object Attribute Values class identifier Attributes Instantiation

reset



The interface class "Register" is formed by combining the features necessary to model the be-haviour of a generic register (containing measured or static information) as seen from the client(central unit, hand held terminal). The contents of the register are identified by the attribute "logi-cal_name". The logical_name contains an OBIS identifier (see Clause 5 or IEC 62056-61). Theactual (dynamic) content of the register is carried by its "value" attribute.

Defining a specific meter means defining several specific registers. In the example of Figure 2 themeter contains 2 registers; i.e. two specific COSEM objects of the class "Register" are instanti-ated. This means that specific values are assigned to the different attributes. Through the instan-tiation one COSEM object becomes a "total, positive, active energy register" whereas the otherbecomes a "total, positive, reactive energy register".

REMARK The COSEM objects (instances of interface classes) represent the behaviour of the meter as seen from the"outside". Therefore modifying the value of an attribute must always be initiated from the outside (e.g. resetting the valueof a register). Internally initiated changes of the attributes are not described in this model (e.g. updating the value of aregister).

4.1.2 Class Description NotationThis section describes the notation used to define the interface classes.

A short text describes the functionality and application of the class. A table gives an overview ofthe class including the class name, the attributes and the methods.

Table 1 – Class description template

Class name Cardinality class_id, VersionAttribute(s) Data Type Min. Max. Def1. logical_name (static) octet-string2. ….. (..) …..3. …… (..) …..Specific Method(s) (if required) m/o1. ….. …..2. ….. …..

Each attribute and method must be described in detail.

Class name Describes the class (e.g. Register, Clock, Profile, ...)Cardinality Specifies the number of instances of the class within a logical device (see 4.1.5).

value The class shall be instantiated exactly “value” times.min...max. The class shall be instantiated at least “min.” times and

at most “max.” times. If min. is zero (0) then the class isoptional, otherwise (min. > 0) "min." instantiations of theclass are mandatory.

class_id Identification code of the class (range 0 to 65 535). The class_id can be obtainedfrom an “Association” object. The class_id's from 0 to 8 191 are reserved to bespecified by the DLMS UA. Class_id's from 8 192 to 32 767 are reserved formanufacturer specific interface classes. Class_id's from 32 768 to 65 535 arereserved for user group specific interface classes. DLMS UA reserves the right toassign ranges to individual manufacturers or user groups.

Version Identification code of the version of the class. The version can be obtained froman “Association” object.Within one logical device all instances of a certain class must be of thesame version.

Attribute(s) Specifies the attribute(s) that belong to the class.



(dyn.) Classifies an attribute that carries a process value, which isupdated by the meter itself.

(static) Classifies an attribute which is not updated by the meteritself (e.g. configuration data).

logical_name octet-string The logical name is always the first attribute of a class. Itidentifies the instantiation (COSEM object) of this class. Thevalue of the logical_name conforms to OBIS (see Clause 5or IEC 62056-61).

Data Type Defines the data type of an attribute (see 4.1.3).Min. Specifies if the attribute has a minimum value.

x The attribute has a minimum value.

<empty> The attribute has no minimal value.Max. Defines if the attribute has a maximum value.

x The attribute has a maximum value.

<empty> The attribute has no maximum value.Def Specifies if the attribute has a default value. This is the value of the attribute after

reset.

x The attribute has a default value.

<empty> The default value is not defined by the class definition. .SpecificMethod(s)

Provides a list of the specific methods that belong to the object.

Method Name () The method has to be described in the subsection "MethodDescription".

m / o Defines if the method is mandatory or optional.

m (mandatory) The method is mandatory.

o (optional) The method is optional.

Attribute Description

Describes each attribute with its data type (if the data type is not simple), its data formats and itsproperties (Minimum value, Maximum value and Default value).

Method Description

Describes each method and the invoked behaviour of the instantiated COSEM object(s).

NOTE Services for accessing attributes or methods by the protocol are described in DLMS UA 1000-2 or IEC 62056-53.

Selective Access

The common methods READ/WRITE and GET/SET typically reference the entire attribute ad-dressed. However, for certain attributes selective access to just part of the attribute may be pro-vided. The part of the attribute is identified by specific selective access parameters. These selec-tive access parameters are defined as part of the attribute specification.

4.1.3 Common Data TypesThe following list contains some data types common to all interface classes.



Simple data types Data types carrying one data item onlyinteger, long, double-long,unsigned, long-unsigned,double-long-unsigned,boolean

Simple data types as defined in IEC 61334-4-41:1996 (A.12, Data).Examples:integer Integer8 1 bytelong Integer16 2 bytesdouble-long Integer32 4 bytes

enum The elements of the enumeration type need to be defined in the sub-section “Attribute Description”.Any not listed value for an enumeration is reserved by default.

real32, real64 Real data types according to the REAL specification of IEC 61334-4-41:1996.

visible-string, octet-string An ordered sequence of ASCII-characters respectively octets (8-bitbytes).

bit-string An ordered sequence of boolean values.

Complex data types More than one data item is included, or the data item itselfis not simple

array The array elements need to be defined in the sub-section “AttributeDescription”.

compact array The array elements need to be defined in the sub-section “AttributeDescription”.

structure The structure type needs to be defined in the sub-section “AttributeDescription”.

instance specific The data type of the attribute needs to be specified in the instantiationof the object for a particular meter (instance model).

4.1.4 Data formats for date and time notationDate and time notations are normally using octet-string as data type, but the formatting of the data is definedprecisely.

date octet-string year highbyte, year lowbyte, month, day of month, day ofweek

year: interpreted as unsigned16range 0..big

0xFFFF = not specifiedyear highbyte and year lowbyte reference the 2 bytes of the unsigned16

month: interpreted as unsigned8range 1..12, 0xFD,0xFE,0xFF

1 is January0xFD= daylight_savings_end0xFE= daylight_savings_begin0xFF = not specified

dayOfMonth: interpreted as unsigned8range 1..31, 0xFD, 0xFE, 0xFF

0xFD = 2nd last day of month0xFE = last day of month0xE0 to 0xFC = reserved0xFF = not specified



dayOfWeek: interpreted as unsigned8range 1..7, 0xFF

1 is Monday0xFF = not specified

For repetitive dates the unused parts must be set to “not specified”.

time octet-string hour, minute, second, hundredthshour: interpreted as unsigned8

range 0..23, 0xFF0xFF = not specified

minute: interpreted as unsigned8range 0..59, 0xFF

0xFF = not specifiedsecond: interpreted as unsigned8

range 0..59, 0xFF0xFF = not specified

hundredths: interpreted as unsigned8range 0..99, 0xFF

0xFF = not specified

For repetitive times the unused parts must be set to “not specified”.

deviation Integer16 -720..720:in minutes of local time to GMT0x8000 = not specified

clock_status Unsigned8 interpreted as 8 bit string

The status bits are defined as follows:bit 0 (LSB): invalid a valuebit 1: doubtful b valuebit 2: different clock base cbit 3: invalid clock status dbit 4: reservedbit 5: reservedbit 6: reservedbit 7 (MSB): daylight saving active e

date_time octet-stringyear highbyteyear lowbytemonthday of monthday of weekhourminutesecondhundredths of seconddeviation highbytedeviation lowbyteclock statusIndividual fields of date_time are encoded as defined above. Somemay be set to „not specified“ as described above in date and time.

a Time could not be recovered after an incident. Detailed conditions are manufacturer specific(e.g. after the power to the clock has been interrupted).

b Time could be recovered after an incident but the value cannot be guaranteed. Detailed condi-



tions are manufacturer specific.c Bit is set if the basic timing information for the clock is presently taken from a timing source

different from the source specified in clock_based This bit indicates that at least one bit of the clock status is invalid. Some bit may be correct. The

exact meaning shall be explained in the manufacturer’s documentation.e Flag set to true: the transmitted time contains the daylight saving deviation (summer time), Flag

set to false: the transmitted time does not contain daylight saving deviation (normal time)

4.1.5 The COSEM server modelThe COSEM server is structured into 3 hierarchical levels as shown in Figure 3:

Level 1: Physical DeviceLevel 2: Logical DeviceLevel 3: Accessible COSEM objects

COSEM physical device A

COSEMLogical device 2

COSEM Objects

COSEMManagement logical

device

COSEM Objects

Figure 3 – The COSEM server model

The following example (see Figure 4) shows how a combined metering device can be structuredusing the COSEM server model.

Combined metering device

Management logicaldevice

Register“Total Energy”

Register “Tariff 1”

Logical device 2

Register“Total Volume”

Logical device 3

Register“Total Volume”

LDN

A

Physical device

Logical device

Objects

A: Association object

LDN LDN

AA

LDN: COSEM logicaldevice name object

Figure 4 – Combined metering device



4.1.6 COSEM Logical Device

4.1.6.1 GeneralThe COSEM Logical Device is a set of COSEM objects. Each physical device must contain a"Management logical device".

The addressing of COSEM Logical Devices must be provided by the addressing scheme of thelower layers of the protocol used.

4.1.6.2 COSEM Logical Device NameThe COSEM Logical Device can be identified by its unique COSEM Logical Device Name. Thisname can be retrieved from an instance of IC "SAP Assignment" (see 4.2.14), or of a COSEMobject "COSEM Logical Device Name".

This name is defined as an octet-string of up to 16 octets. The first three octets uniquely identifythe manufacturer of the device. The manufacturer is responsible for guaranteeing the uniquenessof the octets that follow (up to 13 octets).

4.1.6.3 The "Association View" of the Logical DeviceIn order to access COSEM objects in the server, an application association must be first estab-lished. This characterises the context within which the associated applications will communicate.The major parts of this context are• information on the application context;• information on the COSEM context;• information on the authentication mechanism used;• etc.

This information is contained in a special COSEM object, the "Association" object. There are twotypes of this Association object defined. One for associations using Short Name referencing (As-sociation SN) and one for using Logical Name referencing (Association LN).

Depending on the association established between the client and the server different access rightsmay be granted by the server. Access rights concern a set of COSEM objects - the Visible objects- which can be accessed ('seen') within the given association. In addition, access to attributes andmethods of these COSEM objects may also be restricted within the association (e.g. a certain typeof clients can only read a particular attribute of a COSEM object).

The list of the visible COSEM objects - the "Association View" - can be obtained by the client byreading the "object_list" attribute of the appropriate Association object.

Additional information about the access rights (read only, write only, read and write) to the attrib-utes and the availability of the methods (within the established association) can be found via spe-cific methods provided by the Association objects (see 4.2.12, 4.2.13).

4.1.6.4 Mandatory Contents of a COSEM Logical DeviceThe following objects must be part of each COSEM logical device. They must be accessible forGET/READ in all application associations with this logical device:

• COSEM logical device name object• Current Association (LN or SN) object



4.1.7 Authentication Procedures

4.1.7.1 Low Level Security (LLS) Authenticationmore details, see complete Blue Book DLMS UA 1000-1 ...

4.1.7.2 High Level Security (HLS) Authenticationmore details, see complete Blue Book DLMS UA 1000-1 ...



4.2 The interface classesThe currently defined interface classes for meters and the rela-tions between them are illustrated in Figure 5.

NOTES

The interface class "Base" itself is not specified explicitly. It contains only oneattribute "logical_name".

In the description of the "Demand Register", "Clock" and "Profile Generic" inter-face classes, the 2nd attributes are labelled differently than the 2nd attribute ofthe "Data" interface class, namely "current_average_value", "time" and "buffer"vs. "value". This is to emphasise the specific nature of the "value".

Figure 5 – Overview of the interface classes

Base

Data

Register

Extended Register

Demand Register

Association LN

Clock

Profile Generic

Register Activation

Script Table

Schedule

SAP Assignment

Activity Calendar

Register Monitor

Special Days Table

Association SN

IEC optical port Setup

Single Action Schedule

PSTN modem config.

PSTN auto answer

PSTN auto dial

IEC HDLC Setup

IEC Twisted Pair (1) Setup

Utility Tables



4.2.1 Data (class_id: 1)A Data object stores data related to internal meter object(s). The meaning of the value is identifiedby the logical_name. The data type of the value is instance specific. Data is typically used to storemanufacturer specific configuration data and parameters having manufacturer specific logicalnames.

Data 0..n class_id = 1, Version = 0Attribute(s) Data Type Min. Max. Def1. logical_name (static) octet-string2. value instance specificSpecific Method(s) m/o


logical_name Identifies the data contained in value. Identifiers are specified in 4.6.1.

value Contains the data.instance specific The data type of the value depends on

the instantiation defined by “logi-cal_name”.

4.2.2 Register (class_id: 3)A Register object stores a process value or a status value with its associated unit. The Registerobject knows the nature of the process value or of the status value. The nature of the value is de-scribed by the attribute "logical name" using the OBIS identification system (see 4.6.1).

Register 0..n class_id = 3, Version = 0Attribute(s) Data Type Min. Max. Def1. logical_name (static) octet-string2. value (dyn.) instance specific3. scaler_unit (static) scal_unit_typeSpecific Method(s) m/o1. reset o


value Contains the current process or status value.

instance specific The data type of the value depends on theinstantiation defined by “logical_name”and possibly from the manufacturer.Therefore, this attribute must provide thevalue and the data type when it is ac-cessed by a client.The type has to be chosen such that, to-gether with the logical_name, an unambi-guous interpretation of the value is possi-ble.

scaler_unit Provides information on the unit and the scaler of the value.If the value uses a complex data type, the scaler and unit apply to all ele-ments.

scal_unit_type:structure scaler, unit



scaler: integer

unit: enum

This is the exponent (to the base of 10) ofthe multiplication factorREMARK If the value is not numerical then thescaler shall be set to 0.

Enumeration defining the physical unit;details see below

Method Description

reset (data) This method forces a reset of the object. By invoking this method thevalue is set to the default value. The default value is an instance specificconstant.data ::= integer(0)

unit ::= enumCode // Unit Quantity Unit SI definition(1) a // time year(2) mo // time month(3) wk // time week 7*24*60*60 s(4) d // time day 24*60*60 s(5) h // time hour 60*60 s(6) min. // time minute 60 s(7) s // time (t) second s(8) ° // (phase) angle degree rad*180/π(9) °C // temperature (T) degree centi-

gradeK-273.15

(10) currency // (local) currency(11) m // length (l) meter m(12) m/s // speed (v) m/s(13) m3 // volume (V) m3

(14) m3 // corrected volume m3

(15) m3/h // volume flux m3/(60*60s)(16) m3/h // corrected volume flux m3/(60*60s)(17) m3/d // volume flux m3/(24*60*60s)(18) m3/d // corrected volume flux m3/(24*60*60s)(19) l // volume 10-3 m3

(20) kg // mass (m) kilogram kg(21) N // force (F) newton N(22) Nm // energy newtonmeter J = Nm = Ws(23) Pa // pressure (p) pascal N/m2

(24) bar // pressure (p) bar 10-5 N/m2

(25) J // energy joule J = Nm = Ws(26) J/h // thermal power J/(60*60s)(27) W // active power (P) watt W = J/s(28) VA // apparent power (S)(29) var // reactive power (Q)(30) Wh // active energy W*(60*60s)(31) VAh // apparent energy VA*(60*60s)(32) varh // reactive energy var*(60*60s)(33) A // current (I) ampere A(34) C // electrical charge (Q) coulomb C = As(35) V // voltage (V) Volt V(36) V/m // electrical field strength (E) V/m(37) F // capacity (C) farad C/V = As/V(38) Ω // resistance (R) ohm Ω = V/A(39) Ωm2/m // resistivity (ρ) Ωm(40) Wb // magnetic flux (Φ) weber Wb = Vs(41) T // induction (T) tesla Wb/m2



Code // Unit Quantity Unit SI definition(42) A/m // magnetic field strength (H) A/m(43) H // inductivity (L) henry H = Wb/A(44) Hz // frequency (f, ω) hertz 1/s(45) Rac // active energy meter con-

stant1/(Wh)

(46) Rre // reactive energy meter con-stant

(47) Rap // apparent energy meter con-stant

(48) V2h // V2(60*60s)(49) A2h // A2(60*60s)(50) kg/s // mass flux kg/s(51) S mho // conductance siemens 1/Ω

(52)...(253)

//////

reserved...reserved

(254) other // other unit(255) count // no unit, unitless, count 1

Table 2 – Example of values and unitsValue Scaler Unit Data263788 -3 m3 263,788 m3

593 3 Wh 593 kWh3467 0 V 3467 V

4.2.3 Extended Register (class_id: 4)Instances of an Extended Register class store a process value with its associated status, unit, andtime information. The Extended Register object knows the nature of the process value. The natureof the value is described by the attribute "logical name" using the OBIS identification system.

more details, see complete Blue Book DLMS UA 1000-1 ...

4.2.4 Demand Register (class_id: 5)Instances of a Demand Register class store a demand value with its associated status, unit, andtime information. The demand register measures and computes its current_average_value peri-odically. The time interval T over which the demand is measured or computed is defined by speci-fying "number_of_periods" and "period".

12N

period

T = number_of_periods * period

nowcapture_timestart_time_currentt

T is the time intervalused for calculationof the current_valueof a sliding demandregister

Figure 6 – The attributes when measuring sliding demand

The demand register delivers two types of demand: the current_average_value and thelast_average_value (see Figure 7).



The demand register knows its type of process value which is described in "logical name" usingthe OBIS identification system.

period

now start_time+periodstart_time_currentt

current_average_value

energy/period

0

last_average_value

Figure 7 – The attributes when measuring current_average_value if number of periods is 1


4.2.5 Register Activation (class_id: 6)An instance of the Register Activation class is used to handle different tariffication structures. Itspecifies which Register, Extended Register and Demand Register objects are enabled if a spe-cific Activation Mask is active (active_mask). All other register objects defined in regis-ter_assignment not being part of the active_mask are disabled. All register objects not defined inany register_assignment are enabled by default.


4.2.6 Profile Generic (class_id: 7)The Profile Generic class defines a generalised concept to store dynamic process values of cap-ture objects. A capture object is either a register, a clock or a profile. The capture objects are col-lected periodically or occasionally. A profile has a buffer to store the captured data. To retrieve apart of the buffer, either a value range or an entry range may be specified, asking to retrieve allentries whose values or entry numbers fall within the given range.

Assigning the corresponding objects to the profile specifies the capture objects the values of whichhave to be retained (with method capture). The buffer has homogenous entries (all have the samesize and structure), and the assignment is defined statically. The modification of the capture objectassignment clears the buffer of the profile completely. All profiles capturing this modified profile willbe cleared as well to guarantee the homogeneity of their entries.

The buffer may be defined as sorted by one of the registers or by a clock, or the entries arestacked in a "last in first out" order. So for example, it is very easy to build a "maximum demandregister" with a one entry deep sorted profile capturing and sorted by a demand register. It is justas simple to define a profile retaining the three largest values of some period.


4.2.7 Clock (class_id: 8)An instance of the clock interface class handles all information that is related to date and time, in-cluding leap years and the deviation of the local time to a generalised time reference (Greenwich



Mean Time GMT). The deviation from the local time to the generalised time reference can changedepending on the season (e.g. summer time vs. wintertime). The interface to an external client isbased on date information specified in day, month and year, time information given in hundredthsof seconds, seconds, minutes and hours and the deviation from the local time to the generalisedtime reference.

It also handles the daylight savings function in that way; i.e. it modifies the deviation of local timeto GMT depending on the attributes. The start and end point of that function is normally set once.An internal algorithm calculates the real switch point depending on these settings.

GMT

LocalTime

Deviation

daylight_savings_begin daylight_savings_end

Figure 8 – The generalised time concept

Clock 0..1 class_id = 8, Version = 0Attribute(s) Data Type Min. Max. Def1. logical_name (static) octet-string2. time (dyn.) octet-string3. time_zone (static) long4. status (dyn.) unsigned85. daylight_savings_begin (static) octet-string6. daylight_savings_end (static) octet-string7. daylight_savings_deviation (static) integer8. daylight_savings_enabled (static) boolean9. clock_base (static) enumSpecific Method(s) m/o1. adjust_time o2. adjust_to_measuring_period o3. adjust_to_minute o4. adjust_to_preset_time o5. preset_adjusting_time o6. shift_time o

Attribute Descriptiontime Contains the meter’s local date and time, its deviation to GMT

and the status. See also the description in 4.1.4.

When this value is set, only specified fields of the date_time arechanged. For example for setting the date without changing thetime, all time relevant octets of the date_time must be set to“not specified”. The clock_status must always be set whenwriting the time.



octet-string, formatted as set in 4.1.4 for date_time.time_zone The deviation of local, normal time to GMT in minutes.

longstatus The status is equal to the status read in time. See also the de-

scription in 4.1.4.

unsigned8, formatted as set in 4.1.4 for clock_statusdaylight_savings_begin Defines the local switch date and time when the local time has

to be deviated from the normal time.

For generic definitions wildcards are allowed.

octet-string, formatted as set in 4.1.4 for date_time.daylight_savings_end See above.

octet-string, formatted as set in 4.1.4 for date_time.daylight_savings_deviation Contains the number of minutes by which the deviation in gen-

eralised time must be corrected at daylight savings begin.

integer Deviation range of up to ± 120 mindaylight_savings_enabled TRUE enables daylight savings function.

boolean

clock_base Defines where the basic timing information comes from.

enum (0) not defined(1) internal crystal(2) mains frequency 50 Hz(3) mains frequency 60 Hz(4) GPS (global positioning system)(5) Radio Controlled

Method Descriptionadjust_time (data) Sets the meter’s time to the nearest (+/-) quarter of an hour

value (*:00, *:15, *:30, *:45).

data ::= integer (0).adjust_to_measuring_period(data)

Sets the meter’s time to the nearest (+/-) starting point of ameasuring period.

data ::= integer (0).adjust_to_minute (data) Sets the meter’s time to the nearest minute.

If second_counter < 30 s, so second_counter is set to 0.If second_counter ≥ 30 s, so second_counter is set to 0 andminute_counter and all depending clock values are incre-mented if necessary.

data ::= integer(0)adjust_to_preset_time (data) This method is used in conjunction with the pre-

set_adjusting_time method. If the meter’s time lies betweenvalidity_interval_start and validity_interval_end, then time is setto preset_time.

data ::= integer(0)preset_adjusting_time (data) Presets the time to a new value (preset_time) and defines a



validity_interval within which the new time can be activated.

data ::= structure

preset_time: octet-string;validity_interval_start: octet-string;validity_interval_end: octet-string

all octet-strings formatted as set in 4.1.4 for date_time.

shift_time (data) Shifts the time by n (-900 <= n <= 900) s.

data ::= long

4.2.8 Script Table (class_id: 9)The IC Script table provides the possibility to trigger a series of actions by activating an executemethod. For that purpose Script table contains a table of script entries. Each table entry (script)consists of a script_identifier and a series of action_specifications. An action_specification acti-vates a method of a COSEM object or modifies attributes of a COSEM object within the logical de-vice.

A specific script may be activated by other COSEM objects within the same logical device or fromthe outside.


4.2.9 Schedule (class_id: 10)The IC Schedule together with an object of the IC Special Days Table handles time and datedriven activities within a device.


4.2.10 Special Days Table (class_id: 11)The interface class allows defining dates, which will override normal switching behaviour for spe-cial days. The interface class works in conjunction with the class "Schedule" or "Activity Calendar"and the linking data item is day_id.


4.2.11 Activity Calendar (class_id: 20)An instance of the Activity Calendar class is typically used to handle different tariffication struc-tures. It is a definition of scheduled actions inside the meter, which follow the classical way of cal-endar based schedules by defining seasons, weeks... It can coexist with the more general objectSchedule and can even overlap with it. If actions are scheduled for the same activation time in anobject Schedule and in the object Activity Calendar, the actions triggered by Schedule are exe-cuted first.

After a power failure only the "last action" missed from the object Activity Calendar is executed(delayed). This is to ensure proper tariffication after power up. If a Schedule object is present, thenthe missed "last action" of the Activity Calendar must be executed at the correct time within thesequence of actions requested by the Schedule.



The Activity Calendar defines the activation of certain scripts, which can perform different activitiesinside the logical device. The interface to the object Script is the same as for the object Schedule.(see 4.2.9)

If an instance of the interface class "Special Days Table" (see 4.2.10) is available, relevant entriesthere take precedence over the Activity Calendar object driven selection of a day profile. The dayprofile referenced in the "Special Days Table" activates the day_schedule of the day_profile_tablein the "Activity Calendar" object by referencing through the day_id.


4.2.12 Association LN (class_id: 15)COSEM Logical Devices able to establish application associations within a COSEM context usingLogical Name references, model the associations through instances of the Association LN class. ACOSEM Logical Device has one instance of this IC for each association the device is able to sup-port.


4.2.13 Association SN (class_id: 12)COSEM Logical Devices able to establish application associations within a COSEM context usingShort Name references, model the associations through instances of the Association SN class. ACOSEM Logical Device has one instance of this IC for each association the device is able to sup-port.

The short_name of the Association SN object itself is fixed within the COSEM context. It is given in4.5.2 as 0xFA00


4.2.14 SAP Assignment (class_id: 17)The interface class SAP Assignment contains the information on the assignment of the logical de-vices to their Service Access Points (SAP) (see DLMS UA 1000-2 or IEC 62056-46)..


4.2.15 Register Monitor (class_id: 21)This interface class allows to define a set of scripts (see 4.2.8) that are executed when the valueof an attribute of a monitored register type object (Data, Register, Extended Register, DemandRegister, etc.) crosses a set of threshold values.

The IC Register Monitor requires an instantiation of the IC Script Table in the same logical device.




4.2.16 Utility Tables (class_id: 26)An instance of the Utility Tables class encapsulates ANSI C12.19:1997 table data.

With this interface class definition, each "Table" is represented as an instance. The specific in-stance is identified by its logical_name.


4.2.17 Single Action Schedule (class_id: 22)Many applications request periodic actions within a meter. These actions are not necessarily linkedto tariffication (activity calendar or schedule).


4.3 Maintenance of the Interface Classesmore details, see complete Blue Book DLMS UA 1000-1 ...

4.4 Protocol related Interface ClassesEach communication device and / or protocol needs some setup parameters to be defined forproper operation.


4.5 Using Short Names foraccessing attributes and methods

Attributes and methods of COSEM objects can be referenced in two different ways:

Using COSEM Logical Names: In this case the attributes and methods of a COSEM object arereferenced via the identifier of the COSEM object instance to which they belong.

The reference for an attribute is:class_id, value of the 'logical_name' attribute, attribute_index;

The reference for a method is:class_id, value of the 'logical_name' attribute, method_index;

attribute_index is used as the identifier of the required attribute.method_index is used as the identifier of the required method.

Using Short Names: This kind of referencing is intended for use in simple devices. In this caseeach attribute and method of a COSEM object is identified with a 13 bit integer. The syntax for theShort Name is the same as the syntax of the name of a DLMS Named Variable.



4.5.1 Guidelines for Assigning Short NamesThis clause gives guidelines for assigning short names for public attributes and methods.

Dataclass_id = 1, Version = 0

Short name Remarks

Attribute(s)logical_name x x is the base_name of the object.value x+8Specific Method(s)

Registerclass_id = 3, Version = 0

Short name Remarks

Attribute(s)logical_name x x is the base name of the object.value x+8scaler_unit x+16Specific Method(s)reset x+40


4.5.2 Reserved base_names for Special COSEM ObjectsIn order to grant access for devices offering accessing by short_names some short_names arereserved as base_names for special COSEM objects. The reserved range of names is from0xFA00 to 0xFFF8.

Table 3 – Reserved base_names for Special COSEM Objects

base_name (objectName) COSEM object0x FA00 Association SN0x FB00 Script Table (instantiation: “broad-

cast_receiver script”)0x FC00 SAP Assignment0x FD00 Register object containing the “COSEM

Logical Device Name” in the attribute"value"

4.6 Relation to OBISThe OBIS identification system serves as a basis for the COSEM logical names. The system ofnaming COSEM objects is defined in the basic principles (see 4.1) the identification of real dataitems is specified in Clause 5 or IEC 62056-61.

The following clauses define the usage of those definitions in the COSEM environment.

All codes, which are not explicitly listed, but below the manufacturer specific range (128 ..255) are reserved for future use.



4.6.1 Mapping of Data Items to COSEM Objects and AttributesThis clause defines the usage of OBIS identifications and their mapping to COSEM objects ofcertain interface classes and their attributes.


4.6.2 Coding of OBIS IdentificationsTo identify different instances of the same interface class they have to differ in their logical_name.In COSEM the logical_name is taken from the OBIS definition (see Clause 5 or IEC 62056-61).

OBIS codes are used within the COSEM environment as an octet-string[6]. Each octet containsthe unsigned value of the corresponding OBIS value group, coded without tags.

If a data item is identified by less than 6 value groups, all unused value groups must be filled with0xFF.


4.7 Previous Versions of Interface Classes

This chapter lists those interface class definitions which where included in previous editions of thisdocument. The previous interface class versions differ form the current versions by at least oneattribute and/or method and by the version number.

For new implementations in metering devices only the current versions shall be used.

Communication drivers at the client side must also support previous versions.




5. COSEM Object Identification System (OBIS)

5.1 IntroductionThe competitive electricity market requires an ever-increasing amount of timely information con-cerning the usage of electrical energy. Recent technology developments enable to build intelligentstatic metering equipment, which are capable to capture, process and communicate this informa-tion to all parties involved. For further analysis of this information, for the purposes of billing, load-,customer- and contract management, it is necessary to uniquely identify all data in a manufacturerindependent way collected manually or automatically, via local or remote data exchange.

The definition of identification codes was based on DIN 43863-3 December:1997, Electricity me-ters – Part 3: Tariff metering device as additional equipment for electricity meters – EDIS – EnergyData Identification System

5.2 ScopeThe Object Identification System (OBIS) defines the identification codes (ID-codes) for commonlyused data items in electricity metering equipment. This standard specifies the overall structure ofthe identification system and the mapping of all data items to their identification codes.

The Object Identification System (OBIS) provides a unique identifier for all and every data withinthe metering equipment, including not only measurement values, but also abstract values used forconfiguration or obtaining information about the behaviour of the metering equipment. The IDcodes defined in this standard are used for identification of• logical names of the various instances of the Interface Classes, or objects, as defined in

Clause 4 or IEC 62056-62;• data transmitted through communication lines (see 5.5.1);• data displayed on the metering equipment (see 5.5.2).

This standard applies to all types of electricity metering equipment, like fully integrated meters,modular meters, tariff attachments, data concentrators etc.

To cover metering equipment measuring other energy types than electricity, combined meteringequipment measuring more than one type of energy or metering equipment with several physicalmeasurement channels, the concept of channels and medium are introduced. This allows meterdata originating from different sources to be identified. While this standard fully defines the struc-ture of the identification system for other media, the mapping of non-electrical energy related dataitems to ID codes needs to be completed separately. In co-operation with CEN TC294, WG2 somenon-electrical codes are already implemented.

5.3 OBIS Object identification system structureOBIS codes are a combination of six value groups, which describe – in a hierarchical way – theexact meaning of each data item (see Figure 9).



A B C D E F

Figure 9 – OBIS code structure

5.3.1 Value group AThe value group A defines the characteristic of the data item to be identified (abstract data, elec-tricity-, gas-, heat-, water-related data).

5.3.2 Value group BThe value group B defines the channel number, i.e. the number of the input of a metering equip-ment having several inputs for the measurement of energy of the same or different types (e.g. indata concentrators, registration units). Data from different sources can thus be identified. Thedefinitions for this value group are independent from the value group A.

5.3.3 Value group CThe value group C defines the abstract or physical data items related to the information sourceconcerned, e.g. current, voltage, power, volume, temperature. The definitions depend on the valueof the Value group A. Measurement, tariff processing and data storage methods of these quanti-ties are defined by value groups D, E and F.

For abstract data the hierarchical structure of the 6 code fields is not applicable.

5.3.4 Value group DThe value group D defines types, or the result of the processing of physical quantities identifiedwith the value groups A and C, according to various specific algorithms. The algorithms can deliverenergy and demand quantities as well as other physical quantities.

5.3.5 Value group EThe value group E defines the further processing of measurement results identified with valuegroups A to D to tariff registers, according to the tariff(s) in use. For abstract data or for measure-ment results for which tariffs are not relevant, this value group can be used for further classifica-tion.

5.3.6 Value group FThe value group F defines the storage of data, identified by value groups A to E, according to dif-ferent billing periods. Where this is not relevant, this value group can be used for further classifi-cation.

5.3.7 Manufacturer specific codesIf any value group C to F contains a value between 128 and 254 the whole code is considered asmanufacturer specific.



5.4 Value group definitions

5.4.1 Value group AThe range for value group A is 0 to 15.

Table 4 – Value group A codes

Value group A0 Abstract objects1 Electricity-related objects

4 Heat cost allocator related objects5 Cooling related objects6 Heat-related objects7 Gas-related objects8 Cold water-related objects9 Hot water related objects

All other possible values are reserved1.

5.4.2 Value group BThe range for value group B is 1 to 255.

Table 5 – Value group B codes

Value group B0 No channel specified1 Channel 1…64 Channel 6465…127 Reserved128 .. 254 Manufacturer specific codes255 Reserved

With implementations that contain one channel only, even not channel-specific data can be as-signed to channel 1.

5.4.3 Value group CThe range for value group C is 0 to 255.

5.4.3.1 Abstract objectsAbstract objects are data items, which are not related to a certain type of physical quantity.

Table 6 – Value group C codes (abstract objects)

Value group CAbstract objects (A = 0)

0…89 Context specific identifiers a

1 Administered by the DLMS User Association



94 Country specific identifiers

96 General service entries, see 5.4.797 General error messages, see 5.4.798 General list objects, see 5.4.9

127 Inactive objects b

128…254 Manufacturer specific codesAll other Reserved

a Context specific identifiers identify objects specific to a certain proto-col and/or application. For the COSEM context the identifiers are de-fined in Clause 4 or IEC 62056-62.b An inactive object is an object, which is defined and present in ameter, but which has no assigned functionality.

5.4.3.2 Quantities for electrical energy related objects

Table 7 – Value group C codes (electricity objects)

Value group CElectricity related objects (A = 1)

0 General purpose objects (see 5.4.8)1 ΣLi Active power+2 ΣLi Active power-3 ΣLi Reactive power+4 ΣLi Reactive power-5 ΣLi Reactive power QI6 ΣLi Reactive power QII7 ΣLi Reactive power QIII8 ΣLi Reactive power QIV9 ΣLi Apparent power+10 ΣLi Apparent power-11 Current: any phase12 Voltage: any phase13 Average power factor14 Supply frequency15 ΣLI Active power QI+QIV+QII+QIII16 ΣLI Active power QI+QIV-QII-QIII17 ΣLi Active power QI18 ΣLi Active power QII19 ΣLi Active power QIII20 ΣLi Active power QIV

21 L1 Active power+22 L1 Active power-23 L1 Reactive power+24-30 L1 etc. (see 4-10)31 L1 Current a

32 L1 Voltage33 L1 Power factor34 L1 Frequency35-40 L1 Active power ... etc. (see 15-20)

41 L2 Active power+42 L2 Active power-



43 L2 Reactive power+44-60 L2 etc. (see 24-40)

61 L3 Active power+62 L3 Active power-63 L3 Reactive power+64-80 L3 etc. (see 24-40)

81 Angles b

82 Unitless quantity (pulses or pieces)

91 L0 current (neutral)92 L0 voltage(neutral)

96 Electricity-related service entries, see 5.4.797 Electricity-related error messages98 Electricity list99 Electricity data profile see 5.4.10…127 Reserved

128 .. 254 Manufacturer specific code255 Reserved

NOTES

• Li Quantity is the value (to be measured) of a measurement sys-tem connected between the phase i and a reference point. In 3phase 4-wire systems the reference point is the neutral. In 3phase 3-wire systems the reference point is the phase L2.

• ΣLi quantity is the total measurement value across all systems.a For details of extended codes, see 5.4.5.1b For details of extended codes, see 5.4.5.2

The quadrant definitions are according to IEC 61268:1995 - Annex E, Figure E.1.

Figure 10 – Quadrants for power measurement

5.4.4 Value group DThe range for value group D is 0 to 255.

5.4.4.1 Electricity related objects

Table 8 –Value group D codes (electricity)

Value group DElectricity related objects A = 1, C <> 0, 96,97,98,99

0 Billing period average (since last reset)1 Cumulative minimum 12 Cumulative maximum 13 Minimum 14 Current average 15 Last average 16 Maximum 17 Instantaneous value8 Time integral 19 Time integral 2



10 Time integral 311 Cumulative minimum 212 Cumulative maximum 213 Minimum 214 Current average 215 Last average 216 Maximum 2

21 Cumulative minimum 322 Cumulative maximum 323 Minimum 324 Current average 325 Last average 326 Maximum 3

27 Current average 528 Current average 629 Time integral 530 Time integral 6

31 Under limit threshold32 Under limit occurrence counter33 Under limit duration34 Under limit magnitude35 Over limit threshold36 Over limit occurrence counter37 Over limit duration38 Over limit magnitude39 Missing threshold40 Missing occurrence counter41 Missing duration42 Missing magnitude

55 Test average

58 Time integral 4

128 .. 254 Manufacturer specific codes all other Reserved

NOTESAveraging Scheme 1Controlled by measurement period 1 (see 5.4.8) a set of registers is calculated by a meter-ing device. (codes 1..6). The typical usage is for billing purposes.

Averaging Scheme 2Controlled by measurement period 2 (see 5.4.8) a set of registers is calculated by a meter-ing device. (codes 11..16). The typical usage is for billing purposes.

Averaging Scheme 3Controlled by measurement period 3 (see 5.4.8) a set of registers is calculated by a meter-ing device. (codes 21..26). The typical usage is for instantaneous values.

Averaging Scheme 4Controlled by measurement period 4 (see 5.4.8) a test average value. (code 55) is calculatedby the metering device.

Last average



The value of the demand register at the end of the last measurement period.

Current average 5The value of a current demand register using recording interval 1 as time base.

Current average 6The value of a current demand register using recording interval 2 as time base.

Time integral 1Without the inclusion of a billing period code (F <> 255): time integral of the quantity calcu-lated from the origin (first start of measurement) to the instantaneous time point.

With a billing period code included (0<=F<100): time integral of the quantity calculated fromthe origin to the end of the billing period given by the billing period code.

Time integral 2Without the inclusion of a billing period code(F <> 255): Time integral of the quantity calcu-lated from the beginning of the current billing period to the instantaneous time point.

With a billing period code included (0<=F<100): Time integral of the quantity calculated overthe billing period given by the billing period code.

Time integral 3Time integral of the positive difference between the quantity and a prescribed thresholdvalue.

Time integral 4 ("Test time integral”)Time integral of the quantity calculated over a time specific to the device or determined bytest equipment.

Time integral 5used as a base for load profile recording: Time integral of the quantity calculated from thebeginning of the current recording interval to the instantaneous time point for recording pe-riod 1.

Time integral 6used as a base for load profile recording: Time integral of the quantity calculated from thebeginning of the current recording interval to the instantaneous time point for recording pe-riod 2.

Under limit valuesValues under a certain threshold (e.g. dips).

Over limit valuesValues above a certain threshold (e.g. swells).

Missing valuesValues considered as missing (e.g. interruptions).

For identifiers of abstract objects see 5.4.7.

For identifiers of electricity related General purpose objects see 5.4.8.

5.4.4.2 Value group D for country specific identifiersThis table specifies the identifiers for country specific applications. Wherever possible the phonecodes are used. In this table there are no reserved ranges for manufacturer specific codes. Theusage of value group E and F are defined in country specific documents.

Table 9 – Value group D codes (country specific)

Value group DCountry specific identifiers a (A = 0, C = 94)

00 Finnish identifiers01 USA identifiers02 Canadian identifiers07 Russian identifiers10 Czech identifiers11 Bulgarian identifiers12 Croatian identifiers13 Irish identifiers



14 Israeli identifiers15 Ukraine identifiers16 Yugoslavian identifiers27 South African identifiers30 Greece identifiers31 Dutch identifiers32 Belgian identifiers33 French identifiers34 Spanish identifiers35 Portuguese identifiers36 Hungarian identifiers38 Slovenian identifiers39 Italian identifiers40 Romanian identifiers41 Swiss identifiers42 Slovakian identifiers43 Austrian identifiers44 United Kingdom identifiers45 Danish identifiers46 Swedish identifiers47 Norwegian identifiers48 Polish identifiers49 German identifiers55 Brazilian identifiers61 Australian identifiers62 Indonesian identifiers64 New Zealand identifiers65 Singapore identifiers81 Japanese identifiers86 Chinese identifiers90 Turkish identifiers91 Indian identifiers

a Must be limited to two charactersNOTE 1 All other codes reserved

NOTE 2 Objects that are already identified in this document but notincluded in 5.4.4.2 must not be re-identified by a country specific iden-tifier.

5.4.5 Value group EThe range for value group E is 0 to 255.

Table 10 – Value group E codes (electricity)

Value group EElectrical energy related objects (A=1)

0 Total



1 Rate 12 Rate 23 Rate 3.. ...9 Rate 9.. …63 Rate 63

128…254 Manufacturer specific codeall other Reserved

This table is not valid if one of the following separate specifications for value group E apply.

5.4.5.1 Usage of value group E for current and voltage measurementsThe following table show the meaning of the group E value while measuring current or voltage.

Table 11 – Extended current/voltage measurement

Value group EElectrical energy related objects (A = 1); current/voltage

measurement (C = 31, 51, 71, 32, 52 or 72; D = 7)0 Total1 1st harmonic (fundamental)2 2nd harmonic… nth harmonic127 127th harmonic

128…254 manufacturer specific255 Reserved

5.4.5.2 Usage of value group E for measuring anglesThe following table shows the meaning of the group E value while measuring angles.

Table 12 – Extended angle measurement

Value group EElectrical energy related objects (A = 1); angle measurement (C = 81; D = 7)

Angle U(L1) U(L2) U(L3) I(L1) I(L2) I(L3) I(L0) <=From

U(L1) (00) 01 02 04 05 06 07U(L2) 10 (11) 12 14 15 16 17U(L3) 20 21 (22) 24 25 26 27I(L1) 40 41 42 (44) 45 46 47I(L2) 50 51 52 54 (55) 56 57I(L3) 60 61 62 64 65 (66) 67I(L0) 70 71 72 74 75 76 (77)

^ To (Reference)

For identifiers of abstract objects see 5.4.7.For identifiers of electricity related General purpose objects see 5.4.8.



5.4.6 Value group FThe range for value group F is 0 to 255.In all cases, if value group F is not used, it is set to 255.

5.4.6.1 Usage of value group F for billing periodsValue group F specifies the allocation to different billing periods (sets of historical values) for theobjects with following codes:• Value Group A: 1• Value Group C: 1 to 99• Value Group D: 0 to 3; 6; 8 to 13; 16; 21 to 23; 26.

This allocation is valid for 0<=F<100.

5.4.7 Abstract objects

Table 13 – Abstract object codes

Abstract objects, general service entries OBIS codeA B C D E F

Device ID numbers (non energy/channel related)Complete device ID (manufacturing number) 0 0 96 1Device ID 1............Device ID 10

0

0

0

0

96…96

1…1

0…9

Parameter changes, calibration and accessNumber of configuration program changesDate of last configuration program changeDate of last time switch program changeDate of last ripple control receiver program change

0000

xxxx

96969696

2222

0123

Status of security switches 0 x 96 2 4Date of last calibration 0 x 96 2 5Date of next configuration program change 0 x 96 2 6Number of protected configuration program changes aDate of last protected configuration program change a

00

xx

9696

22

1011

Input/output control signalsState of the input control signals 0 x 96 3 1State of the output control signals 0 x 96 3 2State of the internal control signals 0 x 96 4 0Internal operating status 0 x 96 5 0Battery entriesBattery use time counterBattery charge displayDate of next change

000

xxx

969696

666

012

Battery voltage 0 x 96 6 3Number of power failuresTotal failure of all three phases longer than internal autonomy 0 0 96 7 0Phase L1Phase L2Phase L3

000

000

969696

777

123

Operating timeTime of operation 0 x 96 8 0Time of registration rate 1Time of registration rate 2…Time of registration rate 63

00…0

xx…x

9696…96

88…8

12…63

Environmental related parameters



Abstract objects, general service entries OBIS codeA B C D E F

Ambient temperature 0 x 96 9 0Manufacturer specific.....................Manufacturer specific

0

0

x

x

96

96

50

96

x

x

x

xa Protected configuration is characterized by the need to open the main meter cover to modify it, or to break ametrological seal.

REMARK If a value field is shaded, then this value group is not used. “x” is equal to any value within the range.

Table 14 – General error messages

Abstract objects, general error messages OBIS codeA B C D E F

Error object 0 x 97 97 x a

REMARK If a value field is shaded, then this value group is not used. “x” is equal to any value within the range.

a If only one object is instantiated, the value shall be 0

In the manufacturer specific objects only those values shall be placed, which are not representedby another defined code, but need representation on the display as well. If this is not required, thecode shall use the possibilities of a value group above 127.

5.4.8 Electricity-related General purpose objects

Table 15 – General purpose codes (electricity)

Electricity related General purpose objects OBIS-codeA B C D E F

Free ID-numbers for utilitiesComplete combined electricity ID 1 x 0 0Electricity ID 1...Electricity ID 10

1

1

x

x

0

0

0

0

0

9Billing period values/reset counter entriesBilling period counterNumber of available billing periods

11

xx

00

11

01

Time stamp of the billing period VZ (last reset)Time stamp of the billing period VZ-1.........................................................Time stamp of the billing period VZ-n

11

1

xx

x

00.....0

11......1

22......2

VZVZ-1.......VZ-n

Program entriesConfiguration program version numberParameter record numberTime switch program numberRCR program number

1111

xxxx

0000

2222

0123

Meter connection diagram ID 1 x 0 2 4Output pulse constantsRLW (Active energy, metrological LED )RLB (Reactive energy, metrological LED)RLS (Apparent energy, metrological LED)RAW (Active energy, output pulse)RAB (Reactive energy, output pulse)RAS (Apparent energy, output pulse)

111111

xxxxxx

000000

333333

012345

Ratios




Reading factor for powerReading factor for energy

11

xx

00

44

01

Transformer ratio – current (numerator) bTransformer ratio – voltage (numerator) bOverall transformer ratio (numerator) bTransformer ratio – current (denominator) b

Transformer ratio – voltage (denominator) bOverall transformer ratio voltage (denominator) b

111111

xxxxxx

000000

444444

234567

V-ya

V-ya

V-ya

V-ya

V-ya

V-ya

Nominal valuesVoltage [V]Basic/nominal current [A]Frequency [Hz)Maximum current [A]

1111

xxxx

0000

6666

0123

Reference voltage for power quality measurement 1 x 0 6 4 V-ya

Input pulse constantsREW [Imp/kWh] (active energy)REB [Imp/kvarh] (reactive energy)RES [Imp/kVAh] (apparent energy)

111

xxx

000

777

012

Measurement-/registration-period durationMeasurement period 1, for average value 1Measurement period 2, for average value 2Measurement period 3, for instantaneous valueMeasurement period 4, for test valueRecording interval 1, for load profileRecording interval 2, for load profileBilling period

1111111

xxxxxxx

0000000

8888888

0123456

V-ya

V-ya

V-ya

V-ya

V-ya

V-ya

Time entriesTime expired since last end of billing period 1 x 0 9 0Local time 1 x 0 9 1Local date 1 x 0 9 2Reserved 1 x 0 9 3Reserved 1 x 0 9 4Week day (0..7) 1 x 0 9 5Time of last reset 1 x 0 9 6Date of last reset 1 x 0 9 7Output pulse duration 1 x 0 9 8Clock synchronization window 1 x 0 9 9Clock synchronization method 1 x 0 9 10CoefficientsTransformer magnetic lossesTransformer thermal lossesLine resistance lossesLine reactance losses

1111

xxxx

0000

10101010

0123

V-ya

V-ya

V-ya

V-ya

Measurement methodsAlgorithm for active power measurementAlgorithm for active energy measurementAlgorithm for reactive power measurementAlgorithm for reactive energy measurementAlgorithm for apparent power measurementAlgorithm for apparent energy measurementAlgorithm for power factor calculation

1111111

xxxxxxx

0000000

11111111111111

1234567




a y can be set at any value between –1 and n ; for current values group F is not used.b If a transformer ratio is expressed as a fraction the ratio is numerator, divided by denominator. If the transformer ratio isexpressed by an integer or real figure, only the numerator is used.

REMARK If the value field F is shaded, then value group F is not used.

It has to be observed, that some of the codes above are normally not used, as the related dataitems are covered by attributes of already defined objects (application dependent). See Clause 4or IEC 62056-62.

5.4.9 List objectsLists – identified with one single OBIS code – are defined as a series of any kind of data (e.g.measurement value, constants, status, events).

Table 16 – General list objects

General list objects OBIS codeA B C D E F

Data of billing period 0 x 98 1 x VZ a

a see 5.5.3

5.4.10 Electricity data profile objectsData profiles – identified with one single OBIS code – are defined as a series of measurement val-ues of the same type or of groups of the same kind consisting of a number of different measure-ment values.

Table 17 – Profile codes (electricity)

Electricity data profile objects OBIS-codeA B C D E F

Load profile with recording period 1 1 X 99 1 x aLoad profile with recording period 2 1 X 99 2 x aLoad profile during test 1 X 99 3 0Dips voltage profile 1 X 99 10 1 0Swells voltage profile 1 X 99 10 2 0Cuts voltage profile 1 X 99 10 3 0Voltage harmonic profile 1 X 99 11 nth 0Current harmonic profile 1 X 99 12 nth 0Voltage unbalance profile 1 X 99 13 0 0

Event log 1 x 99 98 x aCertification data log 1 x 99 99 x a

a If only one object of each kind is instantiated, the value shall be 0

5.5 Code presentationDepending on the environment used the presentation of codes can be slightly different.



5.5.1 Reduced ID codes (e.g. for IEC 62056-21)To comply with the syntax defined for protocol modes A to D of IEC 62056-21, the range of IDcodes is reduced to fulfil the limitations which are usually applied to the number of digits and theASCII representation of them. All value groups are limited to a range of 0 .. 99 and within that tothe limits given in the relevant chapters.

Some value groups may be suppressed, if they are not relevant to an application:

Optional value groups: A,B,E,F

Mandatory value groups: C,D

To allow the interpretation of shortened codes delimiters are inserted between all value groups:

A - B : C . D . E * FFigure 11 – Reduced ID code presentation

The delimiter between value groups E and F can be modified to carry some information about thesource of a reset (& instead of * if the reset was performed manually).

For compatibility with existing implementations, in value group A an identifier for an energy typemay be used even for abstract objects.

5.5.2 DisplayThe usage of OBIS codes to display values is normally limited in a similar way as for data transfer,e.g. according to IEC 62056-21.

Some codes may be replaced by letters to indicate clearly the differences from other data items:

Table 18 – Example of display code replacement

Value group COBIS code Display code

96 C97 F98 L99 P

5.5.3 Special handling of value group FIdentifying values from previous billing periods uses the group F field to indicate the actual timeperiods/point.

Table 19 – Values of billing periods

Value group FVZ+1 Future periodVZ Period 1VZ-1 Period 2VZ-2 Period 3VZ-3 Period 4



Value group FVZ-4 ...etc.

101 Most recent value102 Two most recent values….125 25 most recent values126 unspecified number of most recent

values

The value of the most recent (youngest) billing period is identified using the ID-code VZ (state ofthe billing period counter), and the second youngest is identified by the code VZ-1 etc. The oper-ating mode of the billing period counter can differ, e.g. modulo-12 or modulo-100. The value that isrepresented after reaching the limit of the billing period counter, contains the billing period valuecode 0 for modulo-100, and 1 for other (e.g. modulo-12).

Values above 100 allow to identify profiles which contain values of more than one billing period.The maximum allowed value for this is 125.

The value 126 identifies a profile with values of an unspecified number of billing periods.For thresholds the value group F contains a reference into several threshold levels for the samequantity (if applicable).

5.5.4 COSEMThe usage of OBIS codes in the COSEM environment is defined in Clause 4 or IEC 62056-62.

Blue Book - Excerpt BB4.PDF

Documents

Transcript of Blue Book - Excerpt BB4.PDF