40 SDMS 02B REV.08 WC - OBIS - Code - Specs PDF

Saudi Electricity Company ‫الشركة السعودية للكهرباء‬
SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

SPECIFICATION DATE: March 2017
SUPPLEMENTARY
(SEC DLMS/COSEM OBIS CODE SPECIFICATION)
FOR
ELECTRONIC REVENUE WC METER
(40-SDMS-02B REV.08)
[March 2017]
This specification is property of SEC and currently optimized.

The optimization is not finalized and this specification
is subject to change or optimized without any notice.

CONTENTS
1. General ............................................................................................................................... 1
1.1. Scope of Application .............................................................................................. 1
1.2. Communication Specifications ............................................................................. 1
1.2.1. Configuration of communication specifications for meters ............................. 1
1.2.2. Referenced Documents ..................................................................................... 1
1.3. Terminology ........................................................................................................... 2
1.3.1. Client ................................................................................................................ 2
1.3.2. Server ................................................................................................................ 2
1.3.3. Master ............................................................................................................... 2
1.3.4. Slave ................................................................................................................. 2
1.3.5. OSI 7 Layer ...................................................................................................... 2
1.4. List of Abbreviation .............................................................................................. 2
2. Physical Layer.................................................................................................................... 3
2.1. Application of IEC 62056-21 ................................................................................ 3
2.3. RS-485 Serial Communication Interface ............................................................ 6
3. Data Link Layer ................................................................................................................ 6
3.2. COSEM Server (Meter) Addressing Scheme ...................................................... 6
4. Application Layer .............................................................................................................. 8
4.1. Application of IEC 62056-5-3 ............................................................................... 9
4.2. The COSEM Server Model .................................................................................. 9
5. Application Process ......................................................................................................... 10
5.1. Application of IEC 62056-6-1 (Object identification system) ......................... 10
5.2. Application of IEC 62056-6-2 ............................................................................. 10
5.3. COSEM Logical Device ...................................................................................... 11
5.4. Classification of Application Association (AA) ................................................. 11
6. Definition of COSEM objects and OBIS codes............................................................. 13
6.1. Energy .................................................................................................................. 13
6.1.1. Total Energy Registers .................................................................................... 14
6.1.2. TOU Energy Registers .................................................................................... 15
6.1.3. Energy Register (Current value from last Demand-reset) .............................. 17
6.1.4. Energy Profile (Daily snapshot) ..................................................................... 18
2

6.1.5. EOB data Profile (Monthly snapshot for billing purpose) ............................. 21
6.2. Demand / Maximum Demand / Cumulative Maximum Demand ................... 23
6.2.1. Demand Registers (current/last average demand) .......................................... 24
6.2.2. Maximum Demand Registers ......................................................................... 26
6.2.3. Maximum demand profile .............................................................................. 28
6.2.4. Cumulative maximum demand registers ........................................................ 31
6.2.5. Cumulative maximum demand profile ........................................................... 33
6.3. Power Factor ........................................................................................................ 36
6.4. Load Profile ......................................................................................................... 37
6.4.1. Load Profile Data ........................................................................................... 37
6.4.2. Load Profile Interval....................................................................................... 38
6.5. Status Information .............................................................................................. 39
6.6. Instantaneous Quality Registers and Internal Maximum Registers .............. 40
6.7. TOU/EOB-control Objects ................................................................................. 45
6.7.1. Activity Calendar / Tariffication Script Table / Tariff Register Activation .... 46
6.7.2. Special Days Table ......................................................................................... 52
6.7.3. End of Billing (EOB) Single Action Schedule / EOB Script Table ................ 53
6.7.4. Current Date/Time (Clock) ............................................................................. 57
6.7.5. Date/Time for Display .................................................................................... 60
6.8. Meter Information............................................................................................... 61
6.8.1. Basic Information ........................................................................................... 61
6.8.2. Metrological parameters ................................................................................. 63
6.8.3. Measurement algorithm .................................................................................. 66
6.8.4. Threshold registers ......................................................................................... 68
6.8.5. Storage Device Information ........................................................................... 70
6.8.6. Meter reading parameter ................................................................................. 70
6.8.7. Billing Period Value........................................................................................ 71
6.8.8. Time Stamp of the Billing Period ................................................................... 72
6.9. Objects regarding Meter Operation .................................................................. 73
6.9.1. Display List .................................................................................................... 73
6.9.2. Meter display control ...................................................................................... 83
6.9.3. Remote output relay control ........................................................................... 85
6.9.4. Commands for meter operation ...................................................................... 90
6.9.5. Number/time of meter program change ......................................................... 95
6.9.6. Current active tariff ........................................................................................ 97
6.9.7. Error Registers ................................................................................................ 97
6.9.8. Number of Events ......................................................................................... 100
6.9.9. Data Transport Security Mode...................................................................... 102
6.9.10. Information security related objects ............................................................. 103
6.9.11. Temperature over limit threshold ................................................................. 105
6.9.12. Average Voltages and Currents ..................................................................... 106
3

6.9.13. Average Voltages and Currents Profile Interval ........................................... 108

6.9.14. Sag Setting Value .......................................................................................... 108
6.9.15. Sag Setting Time........................................................................................... 109
6.9.16. Swell Setting Value ....................................................................................... 109
6.9.17. Swell Setting Time ....................................................................................... 110
6.9.18. Magnetic Interference Detection Time ......................................................... 110
6.9.19. Instantaneous Values Profile ......................................................................... 111
6.9.20. Security Association Event ........................................................................... 113
6.10. Event Log ........................................................................................................... 114
6.11. Push objects ....................................................................................................... 119
6.12. Access Control and Management Objects ...................................................... 123
6.12.1. Association LN ............................................................................................. 123
6.12.2. SAP Assignment ........................................................................................... 128
6.12.3. COSEM logical device name ....................................................................... 129
6.13. Communications ................................................................................................ 130
6.13.1. Optical Port Setup......................................................................................... 130
6.13.2. HDLC Setup ................................................................................................. 130
6.13.3. Communication Port Log ............................................................................. 132
7. Conformance Test .......................................................................................................... 133
8. Tariff (TOU) Programs ................................................................................................. 133

8.1. Tariff Program ID (14AC0001) 01 as per 40-SDMS-02A Rev.07 (2014) ...... 134
8.2. Tariff Program ID (13AC0001) as per 40-SDMS-02A Rev.06 (2013) ........... 134
8.3. Tariff Program ID (11AC0001) as per 40-SDMS-02A Rev.06 (2011) ........... 134
4

1. General
1.1. Scope of Application
This specification shall apply to all Electronic Revenue Meters (hereafter referred to as meters)
currently being supplied to COMPANY, and also meters to be supplied in the future. It includes the
COSEM objects, their data format and OBIS codes, and any other necessary requirements regarding
the meter communications and operational functions.
1.2. Communication Specifications
1.2.1. Configuration of communication specifications for meters
These specifications shall be in compliance with IEC regulations known as International

Communication Specifications for communication with meters and also applied by the IEC standard
for communication with meters revised and established in 2014.
1.2.2. Referenced Documents

Table 1 – Referenced Documents
Reference Year Title
Electricity metering data exchange – The DLMS/COSEM suite –
IEC 62056-1-0 2014
Part 1-0: Smart metering standardization framework
IEC 62056-21 2002 Direct Local Data Exchange (3rd edition of IEC 61107)
Physical layer services and procedures for connection oriented
IEC 62056-42 2002
asynchronous data exchange
IEC 62056-46 2007 Data Link Layer using HDLC-Protocol
IEC 62056-5-3 2013 COSEM Application layer
IEC 62056-6-1 2013 OBject Identification System (OBIS)
IEC 62056-6-2 2013 COSEM Interface Classes
Information technology - open Systems Interconnection -
IEC 9646-1 1994 Conformance testing methodology and framework - Part 1 : General
concept
Information technology - Open Systems interconnection -
IEC 9646-2 1994 conformance testing methodology and framework - Part 2 : Abstract
test suite specification
DLMS UA
2014 COSEM – Identification System and Interface Classes (Blue Book)
1000-1 Ed.12
Page 1 / 139

DLMS UA
2014 DLMS/COSEM – Architecture and Protocols (Green Book)
1000-2 Ed.8
DLMS UA
2010 DLMS/COSEM Conformance Testing Process (Yellow Book)
1001-1 Ed.4
1.3. Terminology
Terminology not commonly included in the technical specifications registered in COMPANY or the
standard specifications specified in the clause 1.4 are defined below.
1.3.1. Client
It indicates a device that requests data or service. A master station is generally referred to as
client.
1.3.2. Server
It indicates a device that provides data or service. (e.g. an electricity meter that transfers the data
requested from Client or performs a required function).
1.3.3. Master
It indicates a device that initializes and controls data flow.
1.3.4. Slave
It indicates a device responds to a request from a master; commonly referring to electricity

meters.
1.3.5. OSI 7 Layer
An abstract description that provides data transmission method between computers linked in a
communication network. It divides network architecture into seven layers and defines
communication functions appropriately.
1.4. List of Abbreviation
- ACSE Application Control Service Element

- APDUs Application Protocol Data Units
- COSEM COmpanion Specification for Energy Metering
- CTT Conformance Test Tool
Page 2 / 135

- DCE Data Communication Equipment (Communication Interface or Modem)

- DLMS Device Language Message Specification
- DLMS UA Device Language Message Specification - User Association
- DTE Data Terminal Equipment (Computer, Terminal or Printer)
- HDLC High-level Data Link Control
- HHU Hand Held Unit
- HLS High Level Security
- IC Interface Class
- ID Identifier
- IEC International Electro-technical Commission
- ISO International Organization for Standardization
- LLC Logical Link Control
- LLS Low Level Security
- LN Logical Name
- MAC Medium Access Control
- OBIS Object Identification System
- OSI Open System Interconnection
- PDU Protocol Data Unit
- PH PHysical layout
- PSTN Public Switched Telephone Network
- SN Short Name
- Xdlms eXtended DLMS
- xDLMS_ASE eXtended DLMS Application Service Element0
2. Physical Layer
For direct local connection in the physical layer of this specification, the optical or electrical
interface defined in the IEC 62056-21 is applied. For remote connection, use the standard interface
between DTE and DCE defined in IEC 62056-42 with HDLC protocol. In addition only mode E of
the protocol defined in IEC 62056-21 shall be available. Therefore the same DLMS protocol can be
applied to both direct local and remote connections.
2.1. Application of IEC 62056-21
IEC 62056-21 describes hardware and protocol specifications for local meter data exchange. In such
systems, a hand-held unit (HHU) or a unit with equivalent functions is connected to a meter or a
group of meters.
This is using an optical or electrical coupling. An electrical interface is proposed for use with a
permanent connection, or when more than one meter needs to be read at one site. The optical coupler
Page 3 / 135

should be able to be easily disconnected to enable data collection via an HHU. The HHU or
equivalent unit acts as a master while the meter acts as a slave in protocol modes A to D. In protocol
E, the HHU acts as a client and the meter acts as a server.
The identical data link protocol is applied to both remote and local direct connections. The applied
standard is IEC 62056-46. The Figure 1 shows the process in which the data link protocol specified
in IEC 62056-46 is used when local direction connection is made with optical or electrical interface
according the standard IEC 62056-21 (Mode E).
Figure 1 – Data link connection from IEC 62056-21 mode E
IEC 62056-42 specifies the physical layer service and protocols within the COSEM 3-layer,
connection-oriented profile for asynchronous data communication. The document does not specify
physical layer signals and mechanical aspects. From an external point of view, the physical layer
provides the interface between the DTE and the DCE. A typical configuration of data exchange
being implemented via wide area network (an example: PSTN) is illustrated in Figure 2 and Figure
3.
Page 4 / 135

From the physical connection point of view, all communications involve two sets of equipment
represented by the terms ‘caller system’ and ‘called system’. From the data link point of view, the
central station normally acts as a master, taking the initiative and controlling the data flow. The
meter is the slave, responding to the master station. The central station normally acts as a client
asking for services, and the meter acts as a server delivering the requested services.
Figure 2 – Typical PSTN Configuration
The situation involving a caller client and a called server is undoubtedly the most frequent case,
but a communication based on a caller server and a called client is also possible, in particular to
report the occurrence of an urgent alarm.
For the purpose of local data exchange, two DTEs can be directly connected using appropriate
connections.
To allow using a wide variety of media, this standard does not specify the physical layer signals
and their characteristics. However, the following assumptions are made:
- The communication is point to point or point to multipoint;

- Both half-duplex and duplex connections are possible;
- Asynchronous transmission with 1 start bit, 8 data bits, no parity and 1 stop bit (8N1).
Page 5 / 135

Figure 3 – The location of the physical layer
IEC 62056-42 defines the services of the physical layer towards its peer layer(s) and the upper
layers, and the protocol of the physical layer.
2.3. RS-485 Serial Communication Interface
In this specification, RS-485 serial communication interface is used for physical layer
communication interface standard. To secure scalability of RS-485 communications, RS-485
drivers of Gateways, PLC modems, and electronic revenue meters shall communicate with up to
32 drivers in a single serial line.
After a RS-485 driver of a device finishes receiving data packets from other device (Receive
Mode), it shall delay at least 5ms before it is converted into Transmit Mode. After the RS-485
driver transmits data packets, it shall be converted into Receive Mode within 1ms.
3. Data Link Layer
IEC 62056-46 specifies the data link layer for connection-oriented, HDLC-based, asynchronous
communication profile.
In order to ensure a coherent data layer service specification for both connection-oriented and
connectionless operation modes, the data link layer is divided into two sub-layers: the Logical Link
Control (LLC) sub layer and the Medium Access Control (MAC) sub layer.
3.2. COSEM Server (Meter) Addressing Scheme
In the 3-layer, connection-oriented, HDLC-based communications profile for Automatic Meter

Reading (AMR) defined in the COSEM standard (IEC 62056), each server (meter) is identified by
Page 6 / 135

server HDLC addresses in Data link Layer. In this specification, the server HDLC address field has
four bytes. The server HDLC address field is divided into Upper HDLC address and Lower HDLC
address, each field has two bytes respectively. According to the COSEM standard, the upper HDLC
address is used as Logical Device Address and the lower HDLC address is used as the Physical
Device address of the meter.
According to the COSEM standard, available values to be used for the upper HDLC address and the
lower HDLC address are specified in table below.
Upper HDLC address (HEX) [2 bytes]

Management Logical Device (default) 0x0001
Reserved for future use 0x0002~0x000F
All-station (Broadcast) [Optional] 0x3FFF
Lower HDLC address (HEX) [2 bytes]
Reserved for future use 0x0001~0x000F
Available values
0x0010 ~ 0x3FFE
(Physical Device Address)
All-station (Broadcast) [Optional] 0x3FFF
For unique identification of each physical device, the last four (4) digits of the meter serial number
are converted to the server lower HDLC address. The converting method between the meter serial
number and the server HDLC address is described below.
Figure 4 – COSEM Server HDLC addressing method
[Note]
1) The default value of server lower HDLC address has to be set to a hexadecimal number
which is derived from the meter serial number. And, the lower HDLC addresses (It is not
Serial Number) shall be rewritable during installation, commissioning and test period.
Page 7 / 135

2) The value “0x3FFF” in lower HDLC address of a COSEM server means the broadcasting
address. All COSEM servers which are connected to the COSEM client will accept the
message, if the COSEM client sends a message with the value “0x3FFF” in the lower HDLC
address field of the destination address.
3) If one or more overlapped addresses of any lower HDLC addresses (physical device
addresses) is occurred under the local area network with a Gateway or a DCU, one of the
lower HDLC addresses which overlapped shall be reassigned with a reserved address from
0x2720 to 0x3FFD.
4) In DLMS/COSEM, data exchange takes place based on the Client/Server model. Physical
devices are modeled as a set of logical devices, acting as servers, providing responses to
requests.
5) The client may send requests, after its power-on and on a regular basis (the same as a gateway
default reading interval) for Push objects (EventNotification), at the same time to multiple
servers, if no response is expected (multi-cast or broadcast). If the client expects a response,
it must send the request to a single server, giving also the right to talk. It has to wait then for
the response before it may send a request to another server and with this, giving the right to
talk (continuously sending broadcast or a single server, if there are other meters which are
not registered or not sent Push objects maximum up to 31 times).
6) Messages from the client to the servers must contain addressing information. In this profile,
it is ensured by using HDLC addresses. If a multi-drop arrangement is used, the HDLC
address is split to two parts: the lower HDLC address to address physical devices and the
upper HDLC address to address logical devices within the physical device. Both the lower
and the upper address may contain a broadcast address (the meter passwords for each
association shall be managed by clients).
7) To be able reporting events, a server may initiate a connection to the client, using the non-
client/server type EventNotification / InformationReport services. As events in several or all
meters connected to a multidrop may occur simultaneously – for example in the case of a
power failure – they may initiate a call to the client simultaneously. For such cases, the
problem has to be handled by above mentioned Master-Slave model and DLMS Client-
Server model. (refer to Green Book 7th edition 218 page clause 10.2.6.4)
4. Application Layer
The applied standard for the application layer is IEC 62056-5-3.
Page 8 / 135

4.1. Application of IEC 62056-5-3
IEC 62056-5-3 specifies the COSEM application layer in terms of structure, services and protocols
for COSEM clients and servers, and defines how to use the COSEM application layer in various
communication profiles.
4.2. The COSEM Server Model
The COSEM server is structured into three hierarchical levels as shown in Figure 5:
Level 1: Physical device
Level 2: Logical device
Level 3: Accessible COSEM objects
The COSEM Server Model is as below:
1) A meter is regarded as a physical device.
2) Physical device consists of at least one logical device.
3) The COSEM logical device contains a set of COSEM objects. Each physical device shall
contain a “management logical device”. In the 3-layer, connection-oriented, HDLC-based
communications profile, the upper HDLC address is used for the logical device address.
The management logical device address is reserved as 0x0001.
4) All the objects defined in this specification are regarded as existing in the management
logical device.
Figure 5 – The COSEM server model
Page 9 / 135

5. Application Process
This specification complies with IEC 62056-6-1 and IEC 62056-6-2 standards which define
informational structures on meters and their processes. All metering data transferred shall be
encrypted or non-encrypted as per clause "9.9 Data Transport Security" of 40-SDMS-02B latest
version
5.1. Application of IEC 62056-6-1 (Object identification system)
Object Identification System (OBIS) defines the identification codes (ID-codes) for commonly used
COSEM object in electricity meter. IEC 62056-6-1 specifies the overall structure of the
identification system and the mapping of all COSEM object to their identification codes.
Each OBIS code provides a unique identifier for all data within the meter, including not only
measurement values, but also abstract values used for configuration or obtaining information about
the behavior of the meter. The ID codes defined in this standard are used for the identification of:
- Logical names of objects defined in IEC 62056-6-2;

- Data transmitted via communication line. (refer to 62056-6-1 A.1);
- Data displayed on meter (refer to 62056-6-1 A.2).
IEC 62056-6-1 applies it to all types of electricity meters, such as fully integrated meter, modular
meter, and data concentrators (or DLMS clients).
5.2. Application of IEC 62056-6-2
IEC 62056-6-2 specifies a model of a meter as it is seen through its communication interfaces.
Generic building blocks are defined using object-oriented methods, in the form of interface classes
to model meters from simple up to very complex functionality.
Data collection systems (or DLMS clients) and meters from different vendors, following this
standard shall exchange data in an interoperable way.
Object modeling: for specification purposes this standard uses the technique of object modeling. An
object is a collection of attributes and methods. The information of an object is organized in
attributes. They represent the characteristics of an object by means of attribute values. The value of
an attribute may affect the behavior of identification of the object. An object may offer a number of
methods to either examine or modify the values of the attributes.
Page 10 / 135

Figure 6 illustrates these terms by means of an example.
Figure 6 – An interface class and its instances
The user can know the register characteristics through the "logical_name" as OBIS identifier (refer
to IEC 62056-6-1), and the “value” contains the actual contents of the register.
Defining a specific meter means defining several specific registers. In Figure 7, the meter has two
registers, and it generates two COSEM objects (“Register” interface class) in this case. One of the
COSEM object is “total, positive, active energy register” and the other is “total, positive, reactive
energy register”.
5.3. COSEM Logical Device
The COSEM logical device is a set of COSEM objects. Each physical device shall contain a
“Management logical device”. The addressing of COSEM logical devices shall be provided by the
addressing scheme of the lower layers of the protocol stack used.
In order to access COSEM objects in the server, an Application Association (AA) shall be first
established with the client. This identifies the partners and characterizes the context within which
the associated applications will communicate. The major parts of this context are application context,
authentication context and xDLMS context. This information is contained in the “Association LN”
object.
5.4. Classification of Application Association (AA)
Depending on the AA established between the client and the server, different access rights may be
Page 11 / 135

granted by the server. Access rights concern a set of COSEM objects – the visible objects – that can
be accessed within the given AA. In addition, access to attributes and methods of these COSEM
objects may also be restricted within the AA.
The structure and purpose of the associations to be supported in the meters are described below:
- The server (meter) classifies each association by identifying the client address.
- The server (meter) has to define at least four (4) associations with different IDs and
passwords;
- The access right (GET/SET/ACTION) for each COSEM object shall be addressed differently
by each association;
- The meter can allow only one client access per each association at the same time (the multiple
accesses are not allowed).
Association Client
User Security Level
Index Address
Client Management Process (default) - 0x01 No Security
0x02 Low Level Security
Manual Meter Reader
Association 2
0x09 High Level Security
AMR/AMM System and On-Site 0x03 Low Level Security

Association 3
Engineer for maintenance 0x0A High Level Security
Low Level Security
Testing, Critical configuration, 0x04
Association 4 (Separate passwords)
Recycle used meter
0x0B High Level Security
0x05 Low Level Security

Security Server Association 5
0x0C High Level Security
[Note] xDLMS services of COSEM Application Layer are accomplished through the conformance
parameters at the agreement time of Application Layer association.
※ Default Passwords for Association 2 and Association 3 should be different for the meter
(Default passwords of Association 2 and Association 3 shall be provided by the meter
manufacturers). The password management method for Association 4 to protect meter data
manipulation shall be provided by the meter manufacturers.
※ The Association 4 password for each meter shall be differently set by manufacturer and
Page 12 / 135

those passwords shall be provided to COMPANY (including all passwords management

program).
※ The password of Meter’s Association 2, 3, and 4 should be changed remotely by AMR and
locally.
※ Low Level Security shall be optionally associated by the clients, only if High Level Security
is not accessible (In Data Transport Security's "disabled" mode).
※ The associations of Low Level Security shall be disabled / enabled with the access right of
each High Level Security.
※ The policy and methods, including detail technical specifications of High Level Security
Policy shall be proposed and implemented by the Vendor. The proposed detail technical
specifications shall be approved by COMPANY.
Association Index Supported Services

Association 2 GET, selective-access, block-transfer-with-get
GET, SET, selective-access,

Association 3
event-notification, ACTION, block-transfer-with-get
GET, SET, selective-access, event-notification, ACTION, block-
Association 4
transfer-with-get, block-transfer-with-set
GET, SET, selective-access, event-notification, ACTION, block-
transfer-with-get, block-transfer-with-set.
Association 5
(Use the same access right with Association 4 for the Meter data
reading)
6. Definition of COSEM objects and OBIS codes
In this section, the common COSEM objects and their standard interface classes, formats are
defined. For detailed information about specific meaning of the standard Interface Classes, refer to
‘IEC 62056-6-2’ and ‘DLMS UA 1000-1:2014, Ed. 12.0’ or latest version.
The Meter shall have required OBIS codes, not specified in this "Supplementary_OBIS_Code" for
Meter operation and maintenance purposes including firmware upgrade functions.
[Note] Access right notations [R: Read-only, W: Write-only, R/W: Read/Write, A: Action]
6.1. Energy
Classification OBIS code Interface Class
Page 13 / 135

A B C D E F
255 Register
Total Energy Register 1 0 c 8 0
VZ (Class id=3, version: 0)
TOU Energy Register 255 Register
1 0 c 8 e
(e = 1 ~ 8) VZ (Class id=3, version: 0)
Energy Register 255 Register
1 0 c 9 0
(Current value from last reset) VZ (Class id=3, version: 0)
255 Profile Generic
Energy profile 1 0 98 1 1
255 Profile Generic
EOB Data Profile 1 0 98 1 2
※ Refer to VZ of OBIS CODE “F” group in IEC 62056-6-1 A3.

※ All VZ tables shall support up to VZ-3 (at least previous three (3) months EOB data).
※ VZ shall use Modulo-100: after VZ=99, VZ shall be zero (0) (VZ=0).
※ VZ means billing period counter (form Vorwertzahler in German)
6.1.1. Total Energy Registers
The total energy registers store the all energy quantities consumed during entire meter operation
period. The total energy registers consist of the aggregate (three phases summation) registers and
the per-phase registers.
1) OBIS codes of the total energy register objects
* ‘Li’ in each energy type notation indicates the phase of the input source. ‘L1’ means ‘Phase
1’, ‘L2’ means ‘Phase 2’, ‘L3’ means ‘Phase 3’, ‘∑Li’ means ‘Aggregate (L1+L2+L3)’.
No. Total Energy Registers OBIS Code

1 ∑Li Import active energy (QI+QIV) 1.0.1.8.0.255
2 ∑Li Export active energy (QII+QIII) 1.0.2.8.0.255
3 ∑Li Import reactive energy (QI+QII) 1.0.3.8.0.255
4 ∑Li Export reactive energy (QIII+QIV) 1.0.4.8.0.255
3 ∑Li Reactive energy (QI) 1.0.5.8.0.255
4 ∑Li Reactive energy (QII) 1.0.6.8.0.255
5 ∑Li Reactive energy (QIII) 1.0.7.8.0.255
Page 14 / 135

No. Total Energy Registers OBIS Code

6 ∑Li Reactive energy (QIV) 1.0.8.8.0.255
7 ∑Li Import apparent energy (QI+QIV) 1.0.9.8.0.255
8 ∑Li Export apparent energy (QII+QIII) 1.0.10.8.0.255
9 ∑Li Active energy (abs(QI+QIV)+(abs(QII+QIII)) 1.0.15.8.0.255
2) Attributes description of the object “Register”
Register Class_id = 3, version = 0

Access right
Attributes Data type & Description
- A.2 A.3 A.4
1. logical_name octet-string - R R R
2. value long64-unsigned - R R R
Scaler: 0 or -1 (integer)
Unit: Active energy = 30 [Wh],
3. scaler_unit - R R R
Reactive energy = 32 [varh],
Apparent energy =31 [VAh]
[Note] When the scaler of the register values (123) is 3 and its unit is [Wh], it indicates the metering
value is measured and stored in unit of kWh with zero (0) decimal point number. E.g. 123 [kWh] or
123,000 [Wh].
6.1.2. TOU Energy Registers
The TOU (Time of Use) energy registers store all energy quantities consumed during each tariff
period. The number of TOU rates supported shall be at least 8 rates.
The number of TOU channels supported shall be at least 8 channels. The energy types defined in
this specification shall be used as a default setting.
[Note] The memory capacity for TOU energy registers shall be at least 64 (Refer to Clause 9.1.3. 3
of 40-SDMS-02B).
E.g. When the 8 energy quantities (see below table) are selected as TOU energy registers, the
available TOU periods are 8 (tariff #1 ~ #8). And when the 8 energy quantities are selected, the
available TOU periods are 8 (tariff #1 ~ #8).
Page 15 / 135

1) Default set of the TOU energy register objects
Registers from 33 to 40
No. TOU Energy Registers OBIS Code

1 ∑Li Import active energy (QI+QIV) [Tariff 1] 1.0.1.8.1.255
2 ∑Li Export active energy (QII+QIII) [Tariff 1] 1.0.2.8.1.255
3 ∑Li Import reactive energy (QI+QII) [Tariff 1] 1.0.3.8.1.255
4 ∑Li Export reactive energy (QIII+QIV) [Tariff 1] 1.0.4.8.1.255
5 ∑Li Reactive energy (QI) [Tariff 1] 1.0.5.8.1.255
6 ∑Li Reactive energy (QIV) [Tariff 1] 1.0.8.8.1.255
7 ∑Li Import apparent energy (QI+QIV) [Tariff 1] 1.0.9.8.1.255
8 ∑Li Export apparent energy (QII+QIII) [Tariff 1] 1.0.10.8.1.255
Page 16 / 135

No. TOU Energy Registers OBIS Code

Sufficient memory space for configuring registers #25 ~ 64 (at least) shall be available (Tariff
4 ~ 8 shall be available to be added).

Access right
- A.2 A.3 A.4
Unit:
3. scaler_unit Active energy = 30 [Wh], - R R R
6.1.3. Energy Register (Current value from last Demand-reset)
The energy registers are used to store all energy quantities (all items defined in the Clause 6.1.1)
calculated from the beginning of the current billing period to the instantaneous time point. The
values of these registers are set to zero whenever reset is occurred.
1) OBIS codes of the energy objects (Current value from last Demand-reset)
OBIS code
Classification Interface Class
A B C D E F
Energy Register
255 Register
(Current value from last 1 0 c 9 0
Demand-reset)
Page 17 / 135

Energy Registers (Current value from last Demand-reset) OBIS Code

∑Li Import active energy (QI+QIV) 1.0.1.9.0.255
∑Li Import reactive energy (QI+QII) 1.0.3.9.0.255
∑Li Import apparent energy (QI+QIV) 1.0.9.9.0.255
∑Li Export active energy (QII+QIII) 1.0.2.9.0.255
∑Li Export reactive energy (QIII+QIV) 1.0.4.9.0.255
∑Li Export apparent energy (QII+QIII) 1.0.10.9.0.255

Access right
- A.2 A.3 A.4
Unit:
3. scaler_unit Active energy = 30 [Wh], - R R R
6.1.4. Energy Profile (Daily snapshot)
This object holds total energy values and each TOU values. All registers defined in the attribute
“capture_object” are captured on a daily basis and when Daily Auto Reset is occurred.
The daily capture process is called “Auto Reset” and triggered by the “Daily Single Action Schedule”
object (OBIS: 0.0.15.1.0.255).
1) OBIS codes of the “energy profile” object
* For reading a part of elements stored in buffer, use method “entry_descriptor” of selective access.
Page 18 / 135

OBIS code
A B C D E F
255 Profile Generic
Energy Profile 1 0 98 1 1
2) Attributes description of the object “Profile Generic”
Profile generic Class_id = 7, version = 1

Access right
- A. 2 A. 3 A. 4
2. buffer array - R R R
3. capture_objects array (See below table) - R R R/W
double-long-unsigned
4. capture_period - - R R
(0: No automatic capture)
5. sort_method Enum: FIFO (first in first out) - - R R
6. sort_object No object to sort by (default) - - R R
7. entries_in_use double-long-unsigned - R R R
8. profile_entries - - R R
(default: 3)
3) Capture_objects description of the object “Profile Generic”
* When the attribute_index is zero (0), it means all public attributes of the object are captured.
Attribute Data
No. Capture_objects Logical_name
_index _index
1 Current date/time 0.0.1.0.0.255 2 0
2 Status information 0.0.96.5.0.255 2 0
3 ∑Li Import active energy (QI+QIV) 1.0.1.8.0.255 0 0
4 ∑Li Export active energy (QII+QIII) 1.0.2.8.0.255 0 0
5 ∑Li Import reactive energy (QI+QII) 1.0.3.8.0.255 0 0
6 ∑Li Export reactive energy (QIII+QIV) 1.0.4.8.0.255 0 0
Page 19 / 135

Attribute Data
_index _index
7 ∑Li Reactive energy (QI) 1.0.5.8.0.255 0 0
8 ∑Li Reactive energy (QII) 1.0.6.8.0.255 0 0
9 ∑Li Reactive energy (QIII) 1.0.7.8.0.255 0 0
10 ∑Li Reactive energy (QIV) 1.0.8.8.0.255 0 0
11 ∑Li Import apparent energy (QI+QIV) 1.0.9.8.0.255 0 0
12 ∑Li Export apparent energy (QII+QIII) 1.0.10.8.0.255 0 0
13 ∑Li Active energy (abs(QI+QIV)+(abs(QII+QIII)) 1.0.15.8.0.255 0 0
14 ∑Li Average import power factor 1.0.13.0.0.255 0 0
15 ∑Li Import active energy (QI+QIV) [Tariff 1] 1.0.1.8.1.255 0 0
16 ∑Li Export active energy (QII+QIII) [Tariff 1] 1.0.2.8.1.255 0 0
17 ∑Li Import reactive energy (QI+QII) [Tariff 1] 1.0.3.8.1.255 0 0
18 ∑Li Export reactive energy (QIII+QIV) [Tariff 1] 1.0.4.8.1.255 0 0
19 ∑Li Reactive energy (QI) [Tariff 1] 1.0.5.8.1.255 0 0
20 ∑Li Reactive energy (QIV) [Tariff 1] 1.0.8.8.1.255 0 0
21 ∑Li Import apparent energy (QI+QIV) [Tariff 1] 1.0.9.8.1.255 0 0
22 ∑Li Export apparent energy (QII+QIII) [Tariff 1] 1.0.10.8.1.255 0 0
23 ∑Li Average import power factor [Tariff 1] 1.0.13.0.1.255 0 0
Page 20 / 135

Attribute Data
_index _index
The sufficient memory space for adding registers #42 ~ 96 (at least) shall be available (Tariff 4 ~ 8 shall be
available to be added).
4) “buffer”: Contains a sequence of entries. Each entry contains values of the captured objects
5) “capture_period”: Period to record (0: No automatic capture)
6) “sort_method”: Storage method (FIFO: first input first output)
7) “sort_object”: Default (FIFO: first input first output)
8) “entries_in_use”: Number of entries that are stored into “buffer”(double long unsigned: 6)
9) “profile_entries”: Maximum number of entries that can be stored into “buffer” (double long
unsigned:
10) The Energy Profile data capture and store at least three historical data.
6.1.5. EOB data Profile (Monthly snapshot for billing purpose)
This profile object records all values necessary for monthly EOB Reset process. This monthly
capture process belongs to “EOB reset” (refer to Clause 6.5 for further explanation about the term)
and is triggered by the “Monthly EOB Action Schedule” object (OBIS: 0.0.15.0.0.255).
1) OBIS codes of the EOB data profile objects
* For reading a part of elements stored in buffer, use method “entry_descriptor” of selective
access.
OBIS code
A B C D E F
255 Profile Generic
EOB Data Profile 1 0 98 1 2
Page 21 / 135


Access right
- A. 2 A. 3 A. 4
(default: 3)
Attribute Data
_index _index
2 Status information 0.0.96.5.0.255 2 0
3 Maximum demand profile 1.0.98.1.3.255 2 Last entry
4 Cumulative maximum demand profile 1.0.98.1.4.255 2 Last entry
5 Energy Profile 1.0.98.1.1.255 2 Last entry
∑Li Import active energy (QI+QIV)
6 1.0.1.9.0.255 0 0
[current billing period]
∑Li Import reactive energy (QI+QII)
7 1.0.3.9.0.255 0 0
8 ∑Li Import apparent energy (QI+QIV) 1.0.9.9.0.255 0 0

∑Li Export active energy (QII+QIII)
9 1.0.2.9.0.255 0 0
Page 22 / 135

Attribute Data
_index _index
∑Li Export reactive energy (QIII+QIV)
10 1.0.4.9.0.255 0 0
11 ∑Li Export apparent energy (QII+QIII) 1.0.10.9.0.255 0 0

∑Li Average import power factor
12 1.0.13.0.e.255 0 0
(Current billing period average)
∑Li Average export power factor
13 1.0.84.0.e.255 0 0
(Current billing period average)
* The ‘E’ code value in the OBIS code indicates tariff period as described below.
e 0 1 2 3 4 5 6 7 8
Tariff
Total Tariff 1 Tariff 2 Tariff 3 Tariff 4 Tariff 5 Tariff 6 Tariff 7 Tariff 8
Period
7) “sort_object”: Default (first input first output)
unsigned:
10) The EOB Data Profile data shall capture and store at least three historical data (entry).
6.2. Demand / Maximum Demand / Cumulative Maximum Demand
The demand register objects are modeled by the “Demand Register” IC (Class id=5, version: 0).
The maximum demand register objects are modeled by the “Extended Register” IC (Class id=4,
version: 0) and “Profile Generic” IC (Class id=7, version: 1).
The cumulative maximum demand register objects are modeled by the “Register” IC (Class id=3,
version: 0) and “Profile Generic” IC (Class id=7, version: 1).
OBIS code
A B C D E F
Demand Register
Demand register 1 0 c 4 0 255
(Class id=5, version: 0)
Page 23 / 135

OBIS code
A B C D E F
255 Extended Register
Maximum demand register 1 0 c 6 e
Cumulative maximum demand 255 Register
1 0 c 2 e
register VZ (Class id=3, version: 0)
255 Profile Generic
Maximum demand profile 1 0 98 1 3
255 Profile Generic
Cumulative maximum demand profile 1 0 98 1 4

※ VZ means billing period counter (form Vorwertzahler in German).
6.2.1. Demand Registers (current/last average demand)
The demand is calculated by the ‘Sliding Window’ method with the period is 300 seconds and the
number of period is 6. Thus the current_average_value is updated every 300 seconds and the
denominator of the current_average_value is 1,800 seconds (=30min).
OBIS code
A B C D E F
Demand Register
Demand registers 1 0 c 4 0 255
1) Default set of the demand register objects
1’, ‘L2’ means ‘Phase 2’, ‘L3’ means ‘Phase 3’, ‘∑Li’ means ‘Aggregate’.
No. Demand Type OBIS Code

1 ∑Li Import active power (QI+QIV) [Total] 1.0.1.4.0.255
2 ∑Li Export active power (QII+QIII) [Total] 1.0.2.4.0.255
3 ∑Li Import reactive power (QI+QII) [Total] 1.0.3.4.0.255
4 ∑Li Export reactive power (QIII+QIV) [Total] 1.0.4.4.0.255
Page 24 / 135


5 ∑Li Reactive power (QI) [Total] 1.0.5.4.0.255
6 ∑Li Reactive power (QIV) [Total] 1.0.8.4.0.255
7 ∑Li Import apparent power (QI+QIV) [Total] 1.0.9.4.0.255
8 ∑Li Export apparent power (QII+QIII) [Total] 1.0.10.4.0.255
9 ∑Li Import active power (QI+QIV) [Tariff 1] 1.0.1.4.1.255
10 ∑Li Export active power (QII+QIII) [Tariff 1] 1.0.2.4.1.255
11 ∑Li Import reactive power (QI+QII) [Tariff 1] 1.0.3.4.1.255
12 ∑Li Export reactive power (QIII+QIV) [Tariff 1] 1.0.4.4.1.255
13 ∑Li Reactive power (QI) [Tariff 1] 1.0.5.4.1.255
14 ∑Li Reactive power (QIV) [Tariff 1] 1.0.8.4.1.255
15 ∑Li Import apparent power (QI+QIV) [Tariff 1] 1.0.9.4.1.255
16 ∑Li Export apparent power (QII+QIII) [Tariff 1] 1.0.10.4.1.255
Page 25 / 135


Sufficient memory space for adding registers #32 ~ 40 (at least) shall be available available
(Tariff 4 ~ 8 shall be available to be added).
2) Attributes / Methods description of the object “Demand Register”
Demand Register Class_id = 5, version = 0

Access right
- A. 2 A. 3 A. 4
2. current_average_value double-long-unsigned - R R R
3. last_average_value double-long-unsigned - R R R
Scaler: 0 (integer)
Unit: Active power = 27 [W],
Reactive power = 29 [var],
Apparent power =28 [VA]
5. status Bit-string (default = 0) - R R R
date_time (octet-string
6. capture_time - R R R
(size(12))
date_time (octet-string
7. start_time_current - R R R
(size(12))
8. period - R R/W R/W
(default: 300 seconds)
long-unsigned
9. number_of_periods - R R/W R/W
(default: 6)
6.2.2. Maximum Demand Registers
At the end of the current/average demand integration period, the current demand is compared with
the previous maximum demand recorded by the meter, and if the new value is greater, the new value
replaces the previous maximum and the current time is used to time stamp of this new maximum.
The maximum demand registers hold the maximum values and its event date/times of each current/
average demand automatically by the meter during the current billing period.
When Demand reset or EOB reset or Manual reset are occurred, these registers are captured into the
object “Maximum demand profile”, and then set to zero. The demand-reset is triggered by the
Page 26 / 135

“Monthly EOB Action Schedule” object (OBIS: 0.0.15.0.0.255).
1) Default set of the maximum demand register objects
No. Maximum Demand Type OBIS Code

Page 27 / 135

No. Maximum Demand Type OBIS Code

Sufficient memory space for adding registers #33 ~ 90 (at least) shall be available (Tariff 4 ~ 8
shall be available to be added).
2) Attributes description of the object “Extended Register”
Extended Register Class_id = 4, version = 0

Access right
- A. 2 A. 3 A. 4
2. value double-long-unsigned - R R R
Scaler: 0 (integer)
Unit:
3. scaler_unit Active power = 27 [W], - R R R
4. status bit-string - R R R
date_time[25]
(OCTET STRING (SIZE(12))
* Bit mapping table of the attribute “status”: Refer to Clause 6.5.
6.2.3. Maximum demand profile
The maximum demand registers are captured into the object “Maximum demand profile” on a
Page 28 / 135

monthly basis or manual reset. The monthly capture process is triggered by the “Monthly EOB
Action Schedule” object (OBIS: 0.0.15.0.0.255).
1) OBIS code of maximum demand profile
OBIS code
A B C D E F
255 Profile Generic
Maximum demand profile 1 0 98 1 3

Access right
- A. 2 A. 3 A. 4
5. sort_method enum: FIFO (first in first out) - - R R
(default: 3)
Attribute Data
_index _index
Page 29 / 135

Attribute Data
_index _index
2 ∑Li Import active power (QI+QIV) [Total] 1.0.1.6.0.255 0 0
3 ∑Li Export active power (QII+QIII) [Total] 1.0.2.6.0.255 0 0
4 ∑Li Import reactive power (QI+QII) [Total] 1.0.3.6.0.255 0 0
5 ∑Li Export reactive power (QIII+QIV) [Total] 1.0.4.6.0.255 0 0
6 ∑Li Reactive power (QI) [Total] 1.0.5.6.0.255 0 0
7 ∑Li Reactive power (QIV) [Total] 1.0.8.6.0.255 0 0
8 ∑Li Import apparent power (QI+QIV) [Total] 1.0.9.6.0.255 0 0
9 ∑Li Export apparent power (QII+QIII) [Total] 1.0.10.6.0.255 0 0
10 ∑Li Import active power (QI+QIV) [Tariff 1] 1.0.1.6.1.255 0 0
11 ∑Li Export active power (QII+QIII) [Tariff 1] 1.0.2.6.1.255 0 0
12 ∑Li Import reactive power (QI+QII) [Tariff 1] 1.0.3.6.1.255 0 0
13 ∑Li Export reactive power (QIII+QIV) [Tariff 1] 1.0.4.6.1.255 0 0
14 ∑Li Reactive power (QI) [Tariff 1] 1.0.5.6.1.255 0 0
15 ∑Li Reactive power (QIV) [Tariff 1] 1.0.8.6.1.255 0 0
16 ∑Li Import apparent power (QI+QIV) [Tariff 1] 1.0.9.6.1.255 0 0
17 ∑Li Export apparent power (QII+QIII) [Tariff 1] 1.0.10.6.1.255 0 0
Page 30 / 135

Attribute Data
_index _index
unsigned:
10) The Maximum demand profile data capture and store at least three historical data.
6.2.4. Cumulative maximum demand registers
Before being Demand reset or EOB reset or Manual reset, the maximum demand value is added to
the sum of all the previous maximum demand, and this data is the cumulative maximum demand.
The cumulative maximum demand registers hold the cumulative sum of the maximum demand
values. These registers are captured into the object “Cumulative maximum demand profile” on a
monthly basis or manual demand-reset. The monthly capture process is triggered by the “Monthly
EOB Action Schedule” object (OBIS: 0.0.15.0.0.255).
When demand-reset is occurred, these registers are captured into the object “Cumulative maximum
demand profile”, but these registers are NOT set to zero.
1) OBIS codes of the cumulative maximum demand register objects
1’, ‘L2’ means ‘Phase 2’, ‘L3’ means ‘Phase 3’, 31∑Li’ means ‘Aggregate’.
Page 31 / 135

No. Cumulative Maximum Demand Type OBIS Code

Page 32 / 135

No. Cumulative Maximum Demand Type OBIS Code

2) Attributes description of the object “Register"

Access right
- A. 2 A. 3 A. 4
Scaler: 0 (integer)
Unit: Active power = 27 [W],
6.2.5. Cumulative maximum demand profile
The maximum demand registers are captured into the object “Cumulative maximum demand profile”
on a monthly basis. The monthly capture process is triggered by the “Monthly EOB Action Schedule”
object (OBIS: 0.0.15.0.0.255).
1) OBIS code of cumulative maximum demand profile
OBIS code
A B C D E F
255 Profile Generic
Cumulative maximum demand profile 1 0 98 1 4
Page 33 / 135


Access right
A.1 A. 2 A. 3 A. 4
1. logical_name octet-string R R R R
2. buffer array R R R R
3. capture_objects array (See below table) R R R R/W
4. capture_period double-long-unsigned - - R R
6. sort_object No object to sort by (Default) - - R R
7. entries_in_use - R R R
8. profile_entries double-long-unsigned - - R R
(default: 3)
Attribute Data
_index _index
2 ∑Li Import active power (QI+QIV) [Total] 1.0.1.2.0.255 0 0
3 ∑Li Export active power (QII+QIII) [Total] 1.0.2.2.0.255 0 0
4 ∑Li Import reactive power (QI+QII) [Total] 1.0.3.2.0.255 0 0
5 ∑Li Export reactive power (QIII+QIV) [Total] 1.0.4.2.0.255 0 0
6 ∑Li Reactive power (QI) [Total] 1.0.5.2.0.255 0 0
7 ∑Li Reactive power (QIV) [Total] 1.0.8.2.0.255 0 0
8 ∑Li Import apparent power (QI+QIV) [Total] 1.0.9.2.0.255 0 0
Page 34 / 135

Attribute Data
_index _index
9 ∑Li Export apparent power (QII+QIII) [Total] 1.0.10.2.0.255 0 0
Sufficient memory space for adding registers #34 ~ 91 (at least) shall be available (Tariff 4 ~ 8 shall
be available to be added).
Page 35 / 135


8) “entries_in_use”: Number of entries that are stored into “buffer” “profile_entries”: Maximum
number of entries that can be stored into “buffer”
9) The Cumulative maximum demand profile data capture and store at least three historical data.
6.3. Power Factor
1) OBIS codes of the power factor objects
OBIS code
A B C D E F
∑Li Average import power factor 255 Register
1 0 13 0 e
(Current billing period average) VZ (Class id=3, version: 0)
∑Li Current average import power Register
1 0 13 4 0 255
factor (demand period) (Class id=3, version: 0)
∑Li Last average import power Register
1 0 13 5 0 255
∑Li Average export power factor 255 Register
1 0 84 0 e
(Current billing period average) VZ (Class id=3, version: 0)
∑Li Current average export power Register
1 0 84 4 0 255
∑Li Last average export power Register
1 0 84 5 0 255

※ VZ means billing period counter (form Vorwertzahler in German).
The ‘E’ code value in the OBIS code indicates tariff period as described below.
E 0 1 2 3 4 5 6 7 8
Tariff
Total Tariff 1 Tariff 2 Tariff 3 Tariff 4 Tariff 5 Tariff 6 Tariff 7 Tariff 8
Period
Page 36 / 135


Access right
A. 1 A. 2 A. 3 A. 4
1. logical_name octet-string R R R R
2. value double-long R R R R
Scaler: -3 (integer)
3. scaler_unit R R R R
Unit: 255 (unitless)
6.4. Load Profile
6.4.1. Load Profile Data
The load profile data are modeled by the “Profile Generic” IC (Class id=7, version: 1).
OBIS code
A B C D E F
Profile Generic
Load Profile 1 0 99 1 0 255

Access right
- A. 2 A. 3 A. 4
double-long-unsigned [unit: sec]
4. capture_period - R R R
Programmable (default: 1,800)
enum
5. sort_method - - R R
(Default: (1) FIFO (first in first out))
Page 37 / 135


Access right
- A. 2 A. 3 A. 4
(shall be equal to or larger than 4320)
Capture_objects Logical_name Attribute_index Data_index

Current date/time 0.0.1.0.0.255 2 0
Status Information 0.0.96.5.0.255 2 0
∑Li Import active power (QI+QIV) 1.0.1.4.0.255 2 0
∑Li Import reactive power (QI+QII) 1.0.3.4.0.255 2 0
∑Li Import apparent power (QI+QIV) 1.0.9.4.0.255 2 0
∑Li Reactive power (import) [Total] 1.0.5.4.0.255 2 0
∑Li Export active power (QII+QIII) [Total] 1.0.2.4.0.255 2 0
∑Li Export reactive power (QIII+QIV) [Total] 1.0.4.4.0.255 2 0
∑Li Export apparent power (QII+QIII) [Total] 1.0.10.4.0.255 2 0
∑Li Reactive power (Export) [Total] 1.0.8.4.0.255 2 0
At least two more channels from Demand Register shall be available.
[Note]
1. The Load Profile object captures the attribute 2 “current_average_value” of the demand
registers (1.0.c.4.0.255) in above table capture. It means that in every scheduled capture time the
Load Profile object captures the current average value of each demand register first, after that, the
demand registers store the current average values into last average value (attribute 3).
2. Likewise the Load Profile object captures the current average power factor value before the
meter stores it into the last average power factor register.
6.4.2. Load Profile Interval
This object holds the interval recording duration for the load profile.
Page 38 / 135

OBIS code
A B C D E F
Load Profile Interval 1 0 0 8 4 255 Register
1) Attributes description of the object “Load Profile Interval”

Access right
- A. 2 A. 3 A. 4
unsigned
Programmable among 1, 5, 15,
2. value - R R/W R/W
30, 60 minutes and default value
is 30 minutes.
scaler: 0 (integer)
unit: 28 [minute]
6.5. Status Information
This object is used to show the status information and be captured by the profile object.
1) OBIS code of the status information object
OBIS code
A B C D E F
Status Information 0 0 96 5 0 255 Data
2) Attributes description of the object “Data”
Data Class_id = 1, version = 0

Access right
- A. 2 A. 3 A. 4
bit-string (3 bytes)
2. value - R R R
(shows the conditions during the
Page 39 / 135


Access right
- A. 2 A. 3 A. 4
load profile recording period, if
any status shown in table below is
triggered, a bit for the condition
will be set to 1)
* Bit mapping table of the attribute “value” of the object.
Byte MSB bit6 bit5 bit4 bit3 bit2 bit1 LSB

No
Configuration
Auto Power Manual EOB Energy Voltage
Byte 0 Time change program
Reset failure Reset Reset Storage cut
change
Device
Wrong
Sag / Magnetic Current
Byte 1 cable Temperature DST
Well tamp tariff
connection
Over Top Terminal
Byte 2
current cover cover
[Note]
1. Auto Reset, Manual Reset, EOB Reset (Refer to Clause 9.2 “Reset Function and Historical
Data Recording” of 40-SDMS-02A Rev.07 for more detailed information about Reset)
2. This object is used to show the meter’s status (during the last LP period) caused by those events
in above table and be captured into the profile object. The Bit mapping table shall be cleared
automatically at the end of every load profile interval.
3. Current Tariff Bit Setting: 1 – tariff1, 2 – tariff2, 3 – tariff3, 4 – tariff4.
4. DST (Daylight Saving Time) Bit Setting: when DST time is changed (start/end).
6.6. Instantaneous Quality Registers and Internal Maximum Registers
The instantaneous quality registers and internal maximum registers are modeled by the “Register”
IC (Class id=3, version: 0) and “Extended Register” IC (Class id=4, version: 0) each.
OBIS code
A B C D E F
Page 40 / 135

Register
Instantaneous quality register 1 0 c 7 0 255
Extended Register
Internal maximum register 1 0 c 6 0 255
1) OBIS codes of the instantaneous quality register and internal maximum register objects.
Energy Type OBIS Code

∑Li Instantaneous import active power (QI+QIV) 1.0.1.7.0.255
∑Li Instantaneous export active power (QII+QIII) 1.0.2.7.0.255
∑Li Instantaneous import reactive power (QI+QII) 1.0.3.7.0.255
∑Li Instantaneous export reactive power (QIII+QIV) 1.0.4.7.0.255
∑Li Instantaneous reactive power (QI) 1.0.5.7.0.255
∑Li Instantaneous reactive power (QIV) 1.0.8.7.0.255
∑Li Instantaneous import apparent power (QI+QIV) 1.0.9.7.0.255
∑Li Instantaneous export apparent power (QII+QIII) 1.0.10.7.0.255
∑Li Instantaneous import power factor 1.0.13.7.0.255
∑Li Instantaneous export power factor 1.0.84.7.0.255
Instantaneous supply frequency 1.0.14.7.0.255
L1 Instantaneous current 1.0.31.7.0.255
L1 Instantaneous voltage 1.0.32.7.0.255
L1 Instantaneous import power factor 1.0.33.7.0.255
Internal L1 Voltage Maximum 1.0.32.6.0.255
Page 41 / 135

Energy Type OBIS Code

Internal L1 Current Maximum 1.0.31.6.0.255
L1-L2 Instantaneous voltage 1.0.130.7.0.255
* Internal Li Voltage/Current Maximum Register shall be reset at every EOB.
a) Active power

Access right
- A. 2 A. 3 A. 4
Scaler: 0 (integer)
Unit: 27 [W]
b) Reactive power

Access right
- A. 2 A. 3 A. 4
Scaler: 0 (integer)
Unit: 29 [var]
Page 42 / 135

c) Apparent power

Access right
- A. 2 A. 3 A. 4
Scaler: 0 (integer)
Unit: 28 [VA]
d) Power factor

Access right
- A. 2 A. 3 A. 4
2. value double-long - R R R
e) Supply frequency

Access right
- A. 2 A. 3 A. 4
2. value unsigned16 - R R R
Unit: 44 [Hz]
f) Current
Page 43 / 135

Access right
- A. 2 A. 3 A. 4
Unit: 33 [Ampere]
g) Voltage

Access right
- A. 2 A. 3 A. 4
Unit: 35 [Voltage]
3) Attributes description of the object “Extended Register”
a) Voltage Maximum

Access right
- A. 2 A. 3 A. 4
Unit: 35 [Voltage]
4. status bit-string (def. = 0) - R R R
date_time[25]
b) Current Maximum
Page 44 / 135


Access right
- A. 2 A. 3 A. 4
Unit: 33 [Ampere]
4. status bit-string (def. = 0) - R R R
date_time[25]
6.7. TOU/EOB-control Objects
TOU/EOB control objects are used for handling of various tariff structures in the meter. They
consist of “Activity Calendar”, “Tariffication Script Table”, “Tariff Register Activation”, “Special
Days Table”, “End of Billing (EOB) Single Action Schedule”, “EOB Script Table” and “Clock”
objects.
The “Activity Calendar” object provides a list of scheduled actions, following the classical way of
calendar based schedules by defining season, month, week, day profile. The “Activity Calendar”
object activates certain scripts defined in the “Tariffication Script Table” object. The activated
script in the “Tariffication Script Table” object writes a “mask_list” attribute which is used to bind
groups of registers to various tariff schemes. “The “Special Days Table” objects are used for
defining special dates such as regular or irregular holidays. On such special days, the day script
specified in the “Special Days Table” overrides the normal day script specified in the “Activity
Calendar”. The diagram below shows the relational behavior of these objects.
The “Single Action Schedule” object is used for executing periodic actions within the meter
(regular/irregular meter reading). This object specifies the time of day on which the EOB script is
executed. The actions of the EOB script are specified in the “EOB Script Table”. The diagram
below shows the relational behavior of these objects.
Page 45 / 135

Figure 7 - Relational diagram of TOU/EOB-control objects
6.7.1. Activity Calendar / Tariffication Script Table / Tariff Register Activation
The “Activity Calendar” object is modeled by the “Activity Calendar” IC (Class id: 20, version: 0).
The “Tariffication Script Table” object is modeled by the “Script Table” IC (Class id: 9, version: 0).
The “Tariffication Register Activation” object is modeled by the “Register Activation” IC (Class id:
6, version: 0).
OBIS code
A B C D E F
Activity Calendar
Activity Calendar 0 0 13 0 0 255
(Class id: 20, version: 0)
Script Table
Tariffication Script Table 0 0 10 0 100 255
Register Activation
Tariff Register Activation 0 0 14 0 0 255
1) Attributes description of the object “Activity Calendar”
Activity calendar Class_id = 20, version = 0
Page 46 / 135

Data type & Access right

Attributes
Description - A. 2 A. 3 A. 4
2. calendar_name_active octet-string (see below) - R R R
3. season_profile_active array (see below) - R R R
4. week_profile_active array (see below) - R R R
5. day_profile_active array (see below) - R R R
6. calendar_name_passive octet-string (see below) - R R/W R/W
7. season_profile_passive array (see below) - R R/W R/W
8. week_profile_passive array (see below) - R R/W R/W
9. day_profile_passive array (see below) - R R/W R/W
10. activate_passive_calendar_time octet-string (see below) - R R/W R/W
Methods
1. activate_passive_calendar integer (0) - - A A
a) Attribute “calendar_name_active”
- Contains an identifier, which is descriptive to the set of scripts, which are activated by
the object.
- “calendar_name”: The identifier of a set of activity schedules (octet-string [9] (Size: 1
byte)). “calendar_name” uses BCD coded data (available range: 00 ~ 99).
b) Attribute “season_profile_active”
- Contains an array of seasons defined by their starting date and a specific week_profile
to be executed. The list is sorted according to “season_start”.
- “season_profile_name”: The identifier of a list of seasons (octet-string [9] (Size: 1
byte)). “season_profile_name” uses BCD coded data (available range: 00 ~ 99).
- “season_start” defines the starting time of the season. (date_time [25] (Size: 12 bytes))
- “week_name” defines the “week_profile” active in this season.
c) Attribute “week_profile_table_active”
Page 47 / 135

- Contains an array of week_profiles to be used in the different seasons. For each

week_profile, the day_profile for every day of a week is identified.
- “week_profile_name” is: The identifier of a list of seasons (octet-string [9] (Size: 1
byte)). “week_profile_name” uses BCD coded data (available range: 00 ~ 99).
- “Monday” defines the day profile valid on Monday (day_id, unsigned [17]).
- “Tuesday” defines the day profile valid on Tuesday (day_id, unsigned [17])..
- “Wednesday” defines the day profile valid on Wednesday (day_id, unsigned [17]).
- “Thursday” defines the day profile valid on Thursday (day_id, unsigned [17]).
- “Friday” defines the day profile valid on Friday (day_id, unsigned [17]).
- “Saturday” defines the day profile valid on Saturday (day_id, unsigned [17]).
- “Sunday” defines the day profile valid on Sunday (day_id, unsigned [17]).
d) Attribute “day_profile_table_active”
- Contains an array of day_profile, identified by their day_id. For each day_profile, a list
of scheduled actions is defined by a script to be executed and the corresponding
activation time (start_time). The list is sorted according to start_time.
- “day_id” is a used defined identifier, identifying the current day_profile. It uses BCD
coded data (unsigned [8], available range: 00 ~ 99).
- “start_time” defines the time when the script is to be executed (time [27] (Size: 4 bytes)))
- “script_logical_name” defines the logical name of the “Tariffication Script Table”
object (OBIS code: 0.0.10.0.100.255).
- “script_selector” defines the script_identifier of the script to be executed.
e) Attribute “calendar_name_passive”: This attribute is a reserved calendar set to be

replaced with “calendar_name_active”. This attribute will be activated by the method
“activate_passive_calendar”.
f) Attribute “season_profile_passive”: This attribute is a reserved calendar set to be

replaced with “season_profile_active”. This attribute will be activated by the method
g) Attribute “week_profile_table_passive”: This attribute is a reserved calendar set to be

replaced with “week_profile_table_active”. This attribute will be activated by the
method “activate_passive_calendar”.
h) Attribute “day_profile_table_passive”: This attribute is a reserved calendar set to be
Page 48 / 135

replaced with “day_profile_table_active”. This attribute will be activated by the method

i) Attribute “activate_passive_calendar_time”
- Defines the time when the object itself calls the method “activate_passive_calendar”
(date_time [25] (Size: 12 bytes)).
j) Method description: “activate_passive_calendar”
- This method copies all attributes called …_passive to the corresponding attributes
called …_active (integer: 0).
k) Number of profile_table
- Number of “season” in a “season_profile”: 8 ("season_profile_name": 0~7)

- Number of “week_profile” in a “week_profile_table”: 8 ("week_profile_name": 0~7)
- Number of “day_profile” in a “day_profile_table": 8 ("day_id": 0~7), where
“day_schedule” in a "day_profile" has 10.
2) Attributes description of the object “Tariffication Script Table”
Script table Class_id = 9, version = 0

Access right
- A. 2 A. 3 A. 4
2. scripts array (see below) - R R R
Methods
1. execute long-unsigned - - - -
a) Attribute “scripts”
- The attribute “scripts” consists of the “script_identifier” (long-unsigned [18]) and the
“actions” (array). When a certain “script_identifier” is referenced by the
“script_selector” element of the attribute “day_profile_table_active” of the “Activity
Calendar” object, the corresponding “actions” (array) is executed. The script_selectors
Page 49 / 135

and their designated purposes are specified in the table below.
Script_selector (two bytes) Meaning

0x0001 Tariff 1 activation
- Each script which is identified by the script selectors triggers each tariff register to be
activated using the object “Tariff Register Activation (Register Activation)”, which is
specified in the following clause.
3) Attributes description of the object “Tariff Register Activation”
Register activation Class_id =6, version = 0

Access right
- A. 2 A. 3 A. 4
2. register_assignment array (see below) - R R R
3. mask_list array (see below) - R R R
4. active_mask octet-string - R R R
a) Attribute “register_assignment”
- Specifies an ordered list of COSEM objects assigned to the “Register Activation” object.
[array: (class_id: long-unsigned), (logical_name: octet-string)]
- This attribute holds all the TOU-related objects such as energy, maximum demand, and
power factor. These objects are identified by an array of indices (e.g. the first object is
referenced by index 1, the second object by index 2, …).
Page 50 / 135

b) Attribute “mask_list”
- Specifies a list of register activation masks. Each entry (mask) is identified by its
mask_name.
- “mask_name”: identifies “index_list” which refers to the registers assigned to the mask
(octet-string [9], size(2 bytes))
Mask_name (two bytes) Activated registers
0x0001 Total & Tariff 1

c) Attribute “active_mask”
- Specifies the currently active mask, which is identified by the “mask_name” (octet-
string [9] , size(2 bytes))
d) Method “add_register”
- Adds one more registers to the attribute “register_assignment”. The new register is
added at the end of the array.
e) Method “add_mask”
- Adds another mask to the attribute “mask_list”. If there exists already a mask with the
same name, the existing mask will be overwritten by the new mark.
f) Method “delete_mask”
Page 51 / 135

- Deletes a mask from the attribute “mask_list”. The mask is defined by its mask_name.
6.7.2. Special Days Table
The “Special Days Table” object is modeled by the “Special Days Table” IC (Class id: 11, version:
0).
OBIS code
A B C D E F
Special Days Table
Special Days Table 0 0 11 0 0 255
1) Attributes description of the object “Special Days Table”

Access right
- A. 2 A. 3 A. 4
2. entries array (see below) - R R R
Methods
structure
{index: long-unsigned,
1. insert - - A A
specialday_date: octet-string,
day_id: unsigned}
2. delete long-unsigned - - A A
a) “entries”
- Specifies a special day identifier for a given date.

- “index” is a sequence number of the entries.
- “specialday_date” designates the year / month / date of the special day (date, octet-
string [26], size (5 bytes)).
- “day_id” indicates the day_profile to be applied with reference to the attribute
“day_profile_active” of the object “Activity Calendar”.
- A part of the “date” elements in the “specialday_date” may have wildcards (e.g. 0xFF
or 0xFFFF) for repeating special days like New Year’s Day.
Page 52 / 135

- The regular holidays (e.g. ‘New Year’s Day’) are expressed by using wildcards in the
“specialday_date” as mentioned above. The irregular holidays (e.g. ‘Ramadan’) are
registered by specifying ‘year’, ‘month’, ‘day of month’, ‘day of week’ of the
“specialday_date”.
b) The number of “spec_day_entry”
- Regular holiday “spec_day_entry”: 20 ("index": 0~19, first ~ 20th)

- Irregular holiday “spec_day_entry”: 400 ("index": 20~419, 20years*20 /year, 21th ~
420th)
c) “insert” method
- Inserts a new entry in the table.
d) “delete” method
- Deletes an entry in the table.
6.7.3. End of Billing (EOB) Single Action Schedule / EOB Script Table
The “Monthly End of Billing (EOB) Single Action Schedule” and “Daily Single Action Schedule”
objects are modeled by the “Single Action Schedule” IC (Class id: 22, version: 0). This object is
used for the execution of periodic actions within a meter, such as regular or irregular date/time.
The “EOB Script Table” object is modeled by the “Script Table” IC (Class id: 9, version: 0).
OBIS code
A B C D E F
Single Action Schedule
Monthly EOB Action Schedule 0 0 15 0 0 255
Single Action Schedule
Daily Single Action Schedule 0 0 15 1 0 255
Script Table
EOB Script Table 0 0 10 0 1 255
1) Attributes description of the object “Monthly EOB Action Schedule”
Single action schedule Class_id = 22, version = 0
Page 53 / 135

Access right
- A. 2 A. 3 A. 4
2. executed_script script (see below) - R R/W R/W
3. type enum (see below) - R R R/W
4. execution_time array (see below) - R R R/W
a) Attribute “executed_script”
- Contains the logical name of the “Script Table” and the script selector of the script to
be executed.
- “script_logical_name”: The OBIS code of the object “EOB Script Table”
(0.0.10.0.1.255)
(Default value for “script_selector”: 0x0001 [Auto Reset, Demand Reset])
b) Attribute “type”
- Type=1: size of execution_time=1, wildcard in date allowed.

- Type=2: size of execution_time=n, all time values are the same, wildcards in date are
not allowed.
allowed.
- Type=4: size of execution_time=n, all time values may be different, wildcards in date
are not allowed.
are allowed.
- Default: Type=1
c) Attribute “execution_time”
- Specifies the time of day the script is executed (quantity of execution_time: 1).
- The attribute has an array of “execution_time_date” elements. The
“execution_time_date” elements consist of “time” and “date”.
- “time”: time [27], octet-string (size: 4 bytes)
Page 54 / 135

- “date”: date [26], octet-string (size: 5 bytes)

- As a default setting (regular billing date), an “execution_time_date” element shall be
configured as below.
[“time” is set to “00,00,00,00” (00h:00m:00s) and “date” is set to “FF,FF,FF,01,FF”
(1st day of every month).]
2) Attributes description of the object “Daily Single Action Schedule”
Single action schedule Class_id = 22, version = 0

Access right
- A. 2 A. 3 A. 4
2. executed_script script (see below) - R R/W R/W
3. type enum (see below) - R R R/W
4. execution_time array (see below) - R R R/W
a) Attribute “executed_script”
- Contains the logical name of the “Script Table” and the script selector of the script to
be executed.
- “script_logical_name”: The OBIS code of the object “EOB Script Table”
(0.0.10.0.1.255)
(Default value for “script_selector”: 0x0002 [Auto Reset])
b) Attribute “type”
- Type=1: size of execution_time=1, wildcard in date allowed.

not allowed.
allowed.
are not allowed.
Page 55 / 135

are allowed.
- Default: Type=1
c) Attribute “execution_time”
- Specifies the time of day the script is executed (quantity of execution_time: 1).
- The attribute has an array of “execution_time_date” elements. The
“execution_time_date” elements consist of “time” and “date”.
- “time”: time [27], octet-string (size: 4 bytes)
- “date”: date [26], octet-string (size: 5 bytes)
- As a default setting, an “execution_time_date” element shall be configured as below.
[“time” is set to “17,00,00,00” (23h:00m:00s) and “date” is set to “FF,FF,FF,FF,FF”
(every day).]
3) Attributes description of the object “EOB Script Table”

Access right
- A. 2 A. 3 A. 4
Methods
1. execute long-unsigned - A A A
a) Attribute “scripts”
- The attribute “scripts” consists of the “script_identifier” (long-unsigned [18]) and the
“actions” (array). When a certain “script_identifier” is referenced by the
“script_selector” element of the attribute “executed_script” of the “EOB Single Action
Schedule” object, the corresponding “actions” (array) is executed. The script_selectors
and their designated purposes are specified in the table below.
0x0000 Do Nothing
Page 56 / 135


Meter reading
0x0001
(EOB Reset: Auto + Demand)
Meter reading
0x0002
(Auto Reset)
Meter reading
0x0003
(Demand Reset)
[Note] These script_selectors above are commonly used by both “Monthly EOB Action
Schedule” and “Daily Single Action Schedule” objects. These script_selectors are also
used for switching the meter reset mode between Internal Clock (Automatic) Reset and
Manual Reset. The following table shows the different cases when those two action
schedule objects use each combination of script_selectors.
Script_selector
Monthly EOB Daily Single Meter Mode
Action Schedule Action Schedule
Manual Reset enabled
(Internal Clock (Automatic) Reset disabled)
0x0000 0x0000
※ Note: In this mode when the manual reset
button is pressed, the EOB Reset (Auto +
Demand) shall be performed.
0x0001 0x0002
Internal Clock (Automatic) Reset and On-
[Default] [Default]
command Reset enabled
Other combinations (Manual Reset disabled)
6.7.4. Current Date/Time (Clock)
The “Current Date/Time” object is modeled by the “Clock” IC (Class id: 8, version: 0).
OBIS code
A B C D E F
Clock
Current Date/Time (Clock) 0 0 1 0 0 255
1) Attributes description of the object “Clock”
Page 57 / 135

Clock Class_id = 8, version = 0

Data type & Access right
Attributes
Description - A. 2 A. 3 A. 4
date_time [9] (OCTET
2. time - R R/W R/W
STRING SIZE(12))
3. time_zone long (unit: minute) - R R/W R/W
4. status unsigned - R R R
5. daylight_savings_begin - R R/W R/W
STRING SIZE(12)
6. daylight_savings_end - R R/W R/W
STRING SIZE(12)
7. daylight_savings_deviation integer (unit: minute) - R R/W R/W
boolean
8. daylight_savings_enabled (TRUE: DST enabled, - R R/W R/W
FALSE: DST disabled)
9. clock_base enum - R R R
a) Attribute “time” is represented by the form “date_time” (octet-string [25], size(12 bytes))
as described below.
Attribute Type Meaning
Year long unsigned [18] Year

Month unsigned [17] Month
Day of month unsigned [17] Day
a day of week
1: Monday, 2: Tuesday, 3: Wednesday
Day of week unsigned [17]
4: Thursday, 5: Friday, 6: Saturday
7: Sunday
Hour unsigned [17] Hour
Minute unsigned [17] Minute
Second unsigned [17] Second
Page 58 / 135

Hundreds of second unsigned [17] 1/100 second

Time Deviation of Time deviation to be applied when daylight
integer [15]
daylight savings savings begin [unit: minute]
Clock status unsigned [17] Clock status [refer to 4.4 of IEC62056-6-2]
b) The “time_zone”: Deviation of local time to GMT in minutes (long: 16). [default = 180]
* GMT: Greenwich Mean Time
c) Attribute “status”: Clock status (integer [15]). The status bits are defined as follows.
Bit 0 Invalid value

Bit 1 Doubtful value
Bit 2 Different clock base
Bit 3 Invalid clock status
Bit 4 Reserved
Bit 5 Reserved
Bit 6 Reserved
Bit 7 Daylight saving active
d) Attribute “daylight_savings_begin”: defines the local switch date and time when the
local time has to be deviated from the normal time (date_time, octet-string (size(12)) ).
e) Attribute “daylight_savings_end”: defines the local switch date and time when the local
time has to return to the normal time (date_time, octet-string (size(12)) ).
f) Attribute “daylight_savings_deviation”: contains the number of minutes by which the

daylight_savings_deviation in generalized time must be corrected at daylight savings
begin. (integer [15]).
g) Attribute “daylight_savings_enabled”: contains the status of DST activation. (boolean

[3], TRUE = DST enabled, FALSE = DST disabled).
Page 59 / 135

6.7.5. Date/Time for Display
The “Date/Time for display” objects are modeled by the “Data” IC (Class id: 1, version: 0). These
objects are used only for LCD display of the meter.
OBIS code
A B C D E F
Data
Time for display 1 0 0 9 1 255
Data
Date for display 1 0 0 9 2 255
1) Attributes description of the object “Data”
Clock Class_id = 1, version = 0

Access right
- A. 2 A. 3 A. 4
2. value octet-string (see below) - R R R
a) Attribute “value” of the object “Time for display” is represented by the form “time”
(OCTET STRING SIZE(4)) as described below.
Hour unsigned [17] Hour

Minute unsigned [17] Minute
Second unsigned [17] Second
Hundreds of second unsigned [17] 1/100 second
b) Attribute “value” of the object “Date for display” is represented by the form “date”
(OCTET STRING SIZE(5)) as described below.
Page 60 / 135

Year long unsigned [18] Year

Month unsigned [17] Month
Day of month unsigned [17] Day
a day of week
1: Monday, 2: Tuesday, 3: Wednesday
Day of week unsigned [17]
4: Thursday, 5: Friday, 6: Saturday
7: Sunday
6.8. Meter Information
6.8.1. Basic Information
The objects defined in this clause are used to hold basic information of the meter.
OBIS code
A B C D E F
Data
Meter serial number 0 0 96 1 0 255
Data
Meter model 0 0 96 1 1 255
Data
SEC item number 0 0 96 1 2 255
Data
Firmware version 1 0 0 2 0 255
1) Attributes description of the object “Meter serial number”

Access right
- A. 2 A. 3 A. 4
visible-string (size: 8 bytes)
Manufacturer shall assign a series
2. value - R R R
of ASCII-coded characters which
represent the meter serial number.
Page 61 / 135

2) Attributes description of the object “Meter model”

Access right
- A. 2 A. 3 A. 4
2. value - R R R
represent the meter model.
3) Attributes description of the object “SEC item number”

Access right
- A. 2 A. 3 A. 4
2. value - R R R
represent the SEC item number.
- The value of “SEC item number” and its description is below:
SEC Item
Short Description
No.
908402201 EMETER,WC,133/230/400VAC,3PH,60HZ,10(100)A,CL1ACT/2REACT,DIGITAL,4W,BOT
908402202 EMETER,WC,133/230/400VAC,3PH,60HZ,20(160)A,CL1ACT/2REACT,DIGITAL,4W,BOT
4) Attributes description of the object “Firmware version”

Attributes Data type & Description Access right
Page 62 / 135

- A. 2 A. 3 A. 4
2. value - R R R
Firmware version (see below)
- The “value” is formatted as below.
Byte 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Char P X X X X Y Y Y Y - M M - D D
- XXX.X: Version number

- YYYY: Year
- MM: Month
- DD: Day
- P: Provider
- Byte 11 means ‘space’.
[Note] The format of “Firmware version” value may be different from different manufacturers. The
format shown above is recommended by COMPANY, but the different format of the
firmware version may be acceptable.
6.8.2. Metrological parameters
The objects defined in this clause are used to hold metrological parameters of the meter.
OBIS code
A B C D E F
Register
Metrological LED (active energy) 1 0 0 3 0 255
Register
Metrological LED (reactive energy) 1 0 0 3 1 255
Register
Nominal voltage 1 0 0 6 0 255
Register
Nominal current 1 0 0 6 1 255
Register
Nominal frequency 1 0 0 6 2 255
Page 63 / 135

Register
Maximum current 1 0 0 6 3 255
Register
Metrological LED (apparent energy) 1 0 0 3 2 255
Data
Tariff Program ID 0 0 96 1 3 255
1) Attributes description of the object “Metrological LED (active energy)”

Access right
- A. 2 A. 3 A. 4
2. value - R R R
Meter constant for active energy
scaler: -3 (integer)
unit: 45 [1/Wh]
2) Attributes description of the object “Metrological LED (reactive energy)”

Access right
- A. 2 A. 3 A. 4
2. value - R R R
Meter constant for reactive energy
unit: 46 [1/varh]
3) Attributes description of the objects “Nominal current” and “Maximum current”

Access right
- A. 2 A. 3 A. 4
Page 64 / 135

2. value long_unsigned - R R R
unit: 33 (ampere)
4) Attributes description of the object “Nominal frequency”

Access right
- A. 2 A. 3 A. 4
2. value long_unsigned - R R R
unit: 44 (hertz)
5) Attributes description of the object “Tariff Program ID”

Access right
- A. 2 A. 3 A. 4
2. value octet-string (8 bytes) - R R/W R/W
6) Attributes description of the object “Nominal Voltage”

Access right
- A. 2 A. 3 A. 4
2. value long_unsigned R R/W R/W
scalar: 0(integer)
3. scalar unit - R R R
unit: 35(voltage)
7) Attributes description of the object “Metrological LED (apparent energy)”
Page 65 / 135


Access right
- A. 2 A. 3 A. 4
Double-long-unsigned
2. value R R R
Meter constant for apparent energy
scalar: -3(integer)
3. scalar unit - R R R
unit: 47[1/Vah]
[Note]
1. Tariff (TOU) Program ID: e.g.) 14AC0001 [14 (Year 2014), A type (B, C, …), Commercial
(Industrial, Residential, Governmental, …), 0001 (0002, 0003, …)].
2. Tariff Program ID shall be updated automatically as the Tariff Program is reprogrammed (or
uploaded as a file) by DLMS clients (HHU, DCU or HES system, etc.). Also, manual update
of Tariff Program and Tariff Program ID shall be configurable.
3. Default Tariff Program ID shall be 14AC0001.
6.8.3. Measurement algorithm
The measurement algorithm objects are modeled by the “Data” IC (class id: 1, version: 0).
OBIS code
A B C D E F
Data
Measurement algorithm for active power 1 0 0 11 1 255
(class id: 1, version: 0)
Data
Measurement algorithm for active energy 1 0 0 11 2 255
Data
Measurement algorithm for reactive power 1 0 0 11 3 255
Data
Measurement algorithm for reactive energy 1 0 0 11 4 255
Data
Measurement algorithm for power factor 1 0 0 11 7 255
1) Attributes description of the objects “measurement algorithm for active power / energy”

Page 66 / 135

- A. 2 A. 3 A. 4
2. value enum (see below) [default: 2] - R R R
enum Measurement algorithm

2 All harmonics of voltage and current are used
2) Attributes description of the objects “measurement algorithm for reactive power / energy”

Access right
- A. 2 A. 3 A. 4

(sum of) reactive power/energy of each phase, calculated from the fundamental of the
1
per phase voltage and the per phase current
3) Attributes description of the objects “measurement algorithm for power factor”

Access right
- A. 2 A. 3 A. 4

True power factor, the power factor produced by the voltage and current including
2 their harmonics. It may be calculated from apparent power and active power,
including the harmonics
Page 67 / 135

6.8.4. Threshold registers
The threshold registers are modeled by the “Register” IC (class id: 3, version: 0).
OBIS code
A B C D E F
Register
Current over limit threshold 1 0 11 35 0 255
Register
Current over limit duration 1 0 11 44 0 255
Register
Voltage under limit threshold 1 0 12 31 0 255
Register
Voltage under limit duration 1 0 12 43 0 255
Register
∑Li PF under limit threshold 1 0 13 31 0 255
1) Attributes description of the objects “Current over limit threshold”

Access right
- A. 2 A. 3 A. 4
2. value long-unsigned [default: 1200] - R R/W R/W
3. scaler_unit unit: 56 (Percentage) - R R R
※ 100% = Maximum current
2) Attributes description of the objects “Current over limit duration”

Access right
- A. 2 A. 3 A. 4
2. value unsigned [default: 1] - R R/W R/W
Page 68 / 135

scaler: 0 (integer)
unit: 6 (minute)
3) Attributes description of the objects “Voltage under limit threshold”

Access right
- A. 2 A. 3 A. 4
3. scaler_unit unit: 56 (Percentage) - R R R
※ 100% = Reference Voltage
4) Attributes description of the objects “Voltage under limit duration”

Access right
- A. 2 A. 3 A. 4
2. value unsigned [default: 1] - R R/W R/W
scaler: 0 (integer)
unit: 6 (minute)
5) Attributes description of the objects “∑Li PF under limit threshold”

Access right
- A. 2 A. 3 A. 4
2. value long [default: 0] - R R/W R/W
3. scaler_unit Scaler: -4 (integer) - R R R
Page 69 / 135

6.8.5. Storage Device Information
The Storage Device information objects (Storage Device installation date/time, Storage Device
failure date/time) are modeled by the “Data” IC (class id: 1, version: 0).
OBIS code
A B C D E F
Storage Device Installation Data
0 0 96 6 5 255
Date/Time (class id: 1, version: 0)
Storage Device Failure Data
0 1 94 96 2 255
Date/Time (class id: 1, version: 0
1) Attributes description of the objects “Data”

Access right
- A. 2 A. 3 A. 4
Date_time[25] (OCTET STRING
2. value - R R R
SIZE(12))
6.8.6. Meter reading parameter
The meter reading parameter object is modeled by the “Data” IC (class id: 1, version: 0).
OBIS code
A B C D E F
Data
Meter reading parameter 0 96 15 128 0 255 (class id: 1, version:
0)

Page 70 / 135

- A. 2 A. 3 A. 4
2. value octet-string (size (6 bytes)) - R R/W R/W
a) Parameter mapping table for the attribute “value”
Data Type
Meanings Size
Order Type
[byte]
bit 6: reserved
bit 5: pass a date (or a month)
bit 4: by internal clock schedule
Cause for last Auto Reset 1 1 bit 3: on command via the communication interfaces
bit 2: by date/time change
bit 1: program change
bit 0: reserved
bit 6: reserved
bit 5: pass a month
bit 4: by internal clock schedule
Cause for last Demand
1 2 bit 3: on command via the communication interfaces
Reset
bit 2: by date/time change
bit 1: program change
bit 0: by manual push-button
Duration of prohibiting
“Manual reset” after 4 3 Unit: second (default: 300)
previous demand reset
[Note]
1. Program (configuration) change: change of TOU, DST, EOB, LP, etc.
2. The reset conditions for last Auto (Demand) Reset shall be configurable as below:
- Initial allowed condition settings: Auto Reset (0011 1011), Demand Reset (0011 1011).
6.8.7. Billing Period Value
The billing period value objects are modeled by the “Data” IC (class id: 1, version: 0).
OBIS code
A B C D E F
Page 71 / 135

Data
Billing period counter (VZ) 1 0 0 1 0 255
(class id: 1, version: 0
Data
Number of available billing periods 1 0 0 1 1 255
(class id: 1, version: 0

Access right
- A. 2 A. 3 A. 4
2. value unsigned - R R R
[Note] The meter shall retain at least three (3) historically registered EOB data (With F = 0…99,
F = 255 identifies the current billing period).
6.8.8. Time Stamp of the Billing Period
The time stamp of the billing period objects are modeled by the “Data” IC (class id: 1, version: 0).
OBIS code
A B C D E F
Time stamp of the current billing Data
1 0 0 1 2 255
period (class id: 1, version: 0)
Time stamp of the last billing period Data
1 0 0 1 2 VZ
(last reset) (class id: 1, version: 0)
Time of the most recent billing Data
1 0 0 9 6 255
(for display) (class id: 1, version: 0)
Date of the most recent billing Data
1 0 0 9 7 255
(for display) (class id: 1, version: 0)
1) Attributes description of the objects “Time stamp of the most recent billing period” and “Time
stamp of the billing period (last reset)”

Access right
- A. 2 A. 3 A. 4
Page 72 / 135

2. value Time [27] (OCTET STRING SIZE(4)) - R R R
2) Attributes description of the objects “Time of the most recent billing (for display)”

Access right
- A. 2 A. 3 A. 4
2. value Date [26] (OCTET STRING SIZE(5)) - R R R
3) Attributes description of the objects “Date of the most recent billing (for display)”

Access right
- A. 2 A. 3 A. 4
Date_time [26] (OCTET STRING
2. value - R R R
SIZE(5))
6.9. Objects regarding Meter Operation
6.9.1. Display List
The display list objects are used to hold the lists of displayed items on each display mode (normal
display mode, test display mode). The display list objects are modeled by the “Data” IC (class id: 1,
version: 0).
OBIS code
A B C D E F
Data
Normal Display List 0 0 21 0 1 255
Data
Test Display List 0 0 21 0 2 255
Page 73 / 135

[Note] These Display List objects are necessary in order for engineers to edit the items to be
displayed on the meter’s LCD. However different implementation of the attribute description and
value type of these objects presented here can be proposed by manufacturers and submitted for
COMPANY’s review and approval.
1) Attributes description of the objects “Display List”

Access right
- A. 2 A. 3 A. 4
2. value array (see below) - R R/W R/W
b) Attribute “value” of the object “Display List”
- The attribute “value” is an array of structures: The array is composed of following

elements.
Attribute “value” Data type
Display item 1 Structure

: :
Display item n Structure
- The structure of the display items is:
array display_item_element
display_item_element ::= structure

{
class_id: long-unsigned,
logical_name: octet-string of 6 bytes in hex,
attribute_number: unsigned,
display_date_time: octet-string of 6 bytes in hex
}
Page 74 / 135

c) Number of display items
- The number of display items shall be programmable. At least one item shall be
displayed in the meter display. Therefore, the minimum number of display item shall
be one. If there are no display items, the number of display item equals to zero. Default
display values are as below lists: Normal Display List and Test Display List.
d) Normal Display List
- The default display items of the normal display mode consist of the minimum items as
specified in the table below.
Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

Attribute Index
OBIS code (6 byte)
number number
* Notation Description in below table

- “B1 ~ B8”: Byte 1 ~ Byte 8
* Byte8 (B8) is Index number and the Description is below;

- “1” means DD/MM/YYYY
- “6” means HH:MM:SS
Normal Display List

Item to display (8 Bytes)
No Contents to display
B1 B2 B3 B4 B5 B6 B7 B8
1 ∑Li Import active energy (QI+QIV) [Total] 1 0 1 8 0 255 2 0
2 ∑Li Import active energy (QI+QIV) [Rate1] 1 0 1 8 1 255 2 0
Page 75 / 135

Normal Display List

B1 B2 B3 B4 B5 B6 B7 B8
6 Time 1 0 0 9 1 255 2 0
7 Date 1 0 0 9 2 255 2 0

8 1 0 1 9 0 255 2 0
(for a current billing period)
9 1 0 3 9 0 255 2 0
10 L1 Instantaneous voltage 1 0 32 7 0 255 2 0
13 L1 Instantaneous current 1 0 31 7 0 255 2 0
16 L1 Instantaneous power factor 1 0 33 7 0 255 2 0
Page 76 / 135

Normal Display List

B1 B2 B3 B4 B5 B6 B7 B8
19 ∑Li Instantaneous power factor 1 0 13 7 0 255 2 0
∑Li Average Power Factor [Total]

20 1 0 13 0 0 255 2 0
∑Li Average Power Factor [Rate 1]
21 1 0 13 0 1 255 2 0
22 1 0 13 0 2 255 2 0
23 1 0 13 0 3 255 2 0
24 1 0 13 0 5 255 2 0
25 Instantaneous supply frequency 1 0 14 7 0 255 2 0
26 Meter serial number 0 0 96 1 0 255 2 0
27 Firmware version 1 0 0 2 0 255 2 0
28 ∑Li Instantaneous import active power (QI+QIV) 1 0 1 7 0 255 2 0
29 ∑Li Instantaneous import reactive power (QI+QII) 1 0 3 7 0 255 2 0
30 ∑Li Import active average demand (QI+QIV) 1 0 1 4 0 255 2 0
31 ∑Li Import reactive average demand (QI+QII) 1 0 3 4 0 255 2 0
32 ∑Li Import active maximum demand (QI+QIV) 1 0 1 6 0 255 2 0
Page 77 / 135

Normal Display List

B1 B2 B3 B4 B5 B6 B7 B8
Date of ∑Li import active maximum demand

33 1 0 1 6 0 255 5 1
(QI+QIV)
Time of ∑Li import active maximum demand
34 1 0 1 6 0 255 5 6
(QI+QIV)
35 ∑Li Import reactive maximum demand (QI+QII) 1 0 3 6 0 255 2 0
Date of ∑Li import reactive maximum demand

36 1 0 3 6 0 255 5 1
(QI+QII)
Time of ∑Li import reactive maximum demand
37 1 0 3 6 0 255 5 6
(QI+QII)
38 ∑Li Import reactive energy (QI+QII) [Total] 1 0 3 8 0 255 2 0
39 ∑Li Import reactive energy (QI+QII) [Rate1] 1 0 3 8 1 255 2 0
43 Billing period counter (VZ) 1 0 0 1 0 255 2 0
44 Load profile interval 1 0 99 1 0 255 4 0
45 Time stamp of the most recent billing 1 0 0 9 6 255 2 0
46 Date stamp of the most recent billing 1 0 0 9 7 255 2 0
Page 78 / 135

Normal Display List

B1 B2 B3 B4 B5 B6 B7 B8
47 Energy Storage Device installation date 0 0 96 6 5 255 2 1
e) Test Display List
- The default display items of the test display mode consist of the minimum items as
specified in the table below.
* Notation Description in below table

- “B1 ~ B8”: Byte 1 ~ Byte 8
* Byte8 (B8) is Index number and the Description is below;

- “1” means DD/MM/YYYY
- “6” means HH:MM:SS
Test Display List

B1 B2 B3 B4 B5 B6 B7 B8
1 ∑Li Import active energy (QI+QIV) [Total] 1 0 1 8 0 255 2 0
Page 79 / 135

Test Display List

B1 B2 B3 B4 B5 B6 B7 B8
6 Time 1 0 0 9 1 255 2 0
7 Date 1 0 0 9 2 255 2 0

8 1 0 1 9 0 255 2 0
9 1 0 3 9 0 255 2 0
∑Li Export active energy (QII+QIII)
10 1 0 2 9 0 255 2 0
∑Li Export reactive energy (QIII+QIV)
11 1 0 4 9 0 255 2 0
Page 80 / 135

Test Display List

B1 B2 B3 B4 B5 B6 B7 B8
21 ∑Li Instantaneous power factor 1 0 13 7 0 255 2 0
∑Li Average Power Factor [Total]

22 1 0 13 0 0 255 2 0
23 1 0 13 0 1 255 2 0
24 1 0 13 0 2 255 2 0
25 1 0 13 0 3 255 2 0
26 1 0 13 0 5 255 2 0
27 Instantaneous supply frequency 1 0 14 7 0 255 2 0
28 Meter serial number 0 0 96 1 0 255 2 0
29 Firmware version 1 0 0 2 0 255 2 0
30 ∑Li Instantaneous import active power (QI+QIV) 1 0 1 7 0 255 2 0
31 ∑Li Instantaneous import reactive power (QI+QII) 1 0 3 7 0 255 2 0
32 ∑Li Import active average demand (QI+QIV) 1 0 1 4 0 255 2 0
33 ∑Li Import reactive average demand (QI+QII) 1 0 3 4 0 255 2 0
Page 81 / 135

Test Display List

B1 B2 B3 B4 B5 B6 B7 B8
34 ∑Li Import active maximum demand (QI+QIV) 1 0 1 6 0 255 2 0
Date of ∑Li import active maximum demand

35 1 0 1 6 0 255 5 1
(QI+QIV)
Time of ∑Li import active maximum demand
36 1 0 1 6 0 255 5 6
(QI+QIV)
37 ∑Li Import reactive maximum demand (QI+QIV) 1 0 3 6 0 255 2 0
Date of ∑Li import reactive maximum demand

38 1 0 3 6 0 255 5 1
(QII+QIII)
Time of ∑Li import reactive maximum demand
39 1 0 3 6 0 255 5 6
(QII+QIII)
40 ∑Li Import reactive energy (QI+QII) [Total] 1 0 3 8 0 255 2 0
45 ∑Li Export active energy (QI+QIV) [Total] 1 0 2 8 0 255 2 0
46 ∑Li Export active energy (QI+QIV) [Rate1] 1 0 2 8 1 255 2 0
Page 82 / 135

Test Display List

B1 B2 B3 B4 B5 B6 B7 B8
50 ∑Li Export reactive energy (QIII+QIV) [Total] 1 0 4 8 0 255 2 0
51 ∑Li Export reactive energy (QIII+QIV) [Rate1] 1 0 4 8 1 255 2 0
55 Billing period counter (VZ) 1 0 0 1 0 255 2 0
56 Load profile interval 1 0 99 1 0 255 4 0
57 Time stamp of the most recent billing 1 0 0 9 6 255 2 0
58 Date stamp of the most recent billing 1 0 0 9 7 255 2 0
59 Storage Device installation date 0 0 96 6 5 255 2 1
6.9.2. Meter display control
The meter display control objects are used to setting and reading the meter’s display (LCD)
operation mode.
Page 83 / 135

OBIS code
A B C D E F
LCD time-to-return to default Data
0 1 94 96 22 255
screen (class id: 1, version: 0)
Data
LCD auto scroll time 0 1 94 96 23 255
Data
LCD night off option 0 1 94 96 24 255
Start-stop time setting of LCD Data
0 96 94 96 25 255
night off (class id: 1, version: 0)
1) Attributes description of the objects “LCD time-to-return to default screen”

Access right
- A. 2 A. 3 A. 4
Unsigned (value in seconds)
2. value [default: 10, programmable range: 1- - R R/W R/W
255]
2) Attributes description of the objects “LCD auto scroll time”

Access right
- A. 2 A. 3 A. 4
Unsigned (value in seconds)
2. value [default: 2, programmable range: 1 - - R R/W R/W
255]
3) Attributes description of the objects “LCD night off option”

Page 84 / 135

- A. 2 A. 3 A. 4
Boolean
2. value [default: True = Enabled, False = - R R/W R/W
Disabled (default)
[Note] By using this option the LCD will be OFF from 08:00 PM to 04:00 AM, during this
OFF time if any Push Button pressed, it shall be ON for a period of 5 minutes.
4) Attributes description of the objects “start-stop time setting of LCD night off”

Access right
- A. 2 A. 3 A. 4
2. value visual-string (size (4 byte)) - R R/W R/W
[Note] The start/stop time of LCD OFF shall be configurable. The default value of start
time and stop time (08:00 PM to 04:00 AM) shall be set as “2004”.
6.9.3. Remote output relay control
The remote output relay control object is modeled by the “Disconnect control” IC (class id: 70,
version: 0). This object manages operation methods of the output relay to which the magnetic switch
is connected. The relay disconnection control object is modeled by the “script table” IC (class id: 9,
version: 0) and the object controls the action of the meter output relay. The other objects are modeled
by the “Data” IC (class id: 1, version: 0).
OBIS code
A B C D E F
Disconnect control Disconnect control
0 0 96 3 10 255
(Output relay control) (class id: 70, version: 0)
Script table
Disconnect control Script table 0 0 10 0 106 255
State of output relay control Data
0 0 96 3 2 255
signals (ON/OFF) (class id: 1, version: 0)
Page 85 / 135

Selection of the input control Data

0 96 94 96 8 255
signals (class id: 1, version: 0)
Auto recovery operation times of Data
0 96 94 96 9 255
current over limit (class id: 1, version: 0)
Auto recovery times setting of Data
0 96 94 96 10 255
Release times of current over Data
0 96 94 96 11 255
limit setting (class id: 1, version: 0)
* Disconnect and reconnect can be requested:

- Remotely, via a communication channel: remote_disconnect, remote_reconnect;
- Manually, using e.g. a push button: manual_disconnect, manual_reconnect;
- Locally, by a function of the meter using over current limiter: local_disconnect, local_reconnect.
Figure 8 – State Diagram of the Disconnect Control Object
1) Attributes description of the object “Disconnect control”
Disconnect control Class_id = 70, version = 0

Access right
- A. 2 A. 3 A. 4
Page 86 / 135

a) Boolean
2. output_state - R R R
b) [TRUE = Closed, FALSE = Open]
Enum
(0) Disconnected,
3. control_state - R R R
(1) Connected,
(2) Ready_for_reconnection
Enum (5)
Disconnection: Remote (b, c),
4. control_mode local (g) - - R/W R/W
Reconnection: Remote (a),
manual (e),
Methods
1. remote_disconnect() - - A A
2. remote_reconnect() - - A A
2) Attributes description of the object “Script table"

Access right
- A. 2 A. 3 A. 4
2. scripts array (see below) - - - R
Methods
1. execute long-unsigned - - - -
a) The method (execute) of the object “Disconnect control script table” is triggered by
script_identifier (long-unsigned: 18). The script_identifier is designated as the following
table.
Script_identifier (two bytes) Execution

0x0001 Relay trigger (Disconnect)
0x0010 Relay trigger (Reconnect)
3) Attributes description of the object “State of output relay control signals (ON/OFF)”
Page 87 / 135


Access right
- A. 2 A. 3 A. 4
c) boolean
[TRUE = Closed, FALSE = Open]
[Note] Output relay state transition table, before and after the remote commands as below:
Before command After command

Disconnect Command Disconnect Relay Remark
Relay
Relay Relay Output
Output State
Control Control State
Disconnecte
Connected Close Remote disconnect Open -
d
Error
Connected Close Remote reconnect Connected Close
msg
Connected Open Abnormal status (Meter should not be in this state)
Disconnecte Error
Disconnected Open Remote disconnect Open
d msg
Ready for
Disconnected Open Remote reconnect Reconnectio Open -
n
Disconnected Close Abnormal status (Meter should not be in this state)
Ready for Disconnecte
Open Remote disconnect Open -
Reconnection d
Ready for
Ready for Error
Open Remote reconnect Reconnectio Open
Reconnection msg
n
Ready for
Close Abnormal status (Meter should not be in this state)
Reconnection
4) Attributes description of the object “Selection of the input control signals”

Page 88 / 135

- A. 2 A. 3 A. 4
2. value d) unsigned (default: 3) - R R/W R/W
* “value” “ value = 0: No selection, value = 1: Current over limit threshold, value = 2: Remote
disconnection control, value = 3: Current over limit threshold or remote disconnection control,
value = 4: reserved.
5) Attributes description of the object “Auto Recovery Operation Times of current over limit”

Access right
- A. 2 A. 3 A. 4
2. value unsigned - R R R
* “Value” is the number of times counted when the current value goes beyond the current over
limit threshold. "Auto Recovery Operation Times of current over limit" is the number of events
of the real operation.
6) Attributes description of the object “Auto Recovery Times Setting of current over limit”

Access right
- A. 2 A. 3 A. 4
2. value unsigned - R R/W R/W
* “Value” is the auto recovery times setting which will limit the auto recovery operation up to
the setting value [default: 0 (no limitation of the auto recovery times), value setting range: 1 ~
100]. If the auto recovery operations go beyond the setting value, the output relay shall be
disconnected (not operated any more before resetting).
7) Attributes description of the object “Release Times of Current Over Limit Setting”
Page 89 / 135


Access right
- A. 2 A. 3 A. 4
* “Value” is “the Number of Release Times of Current Over Limit Setting” counted, whenever
“Auto recovery times setting of current over limit” is released. In this case, the current over
limit function shall be released.
6.9.4. Commands for meter operation
The commands for meter operation objects hold the lists of executed scripts for meter operational
commands. The objects are modeled by the “Script Table” IC (class id: 9, version: 0).
The “Global Meter Reset” object is used for resetting the meter in one command. The ‘reset’ in this
context means ‘to set all values of registers and internal memories to their default values. The default
values for attributes of all objects are zero values in most cases unless the default values are set to
specific values in this specification.
The “Meter Program Configuration” objects is used for configuring (reading, deleting, reserving
and deleting) the meter program. The ‘program’ in this context indicates the sets of meter parameters,
schedules, etc. In this clause, the list of items in the ‘program’ is specified.
OBIS code
A B C D E F
Script Table
Global Meter Reset 0 0 10 0 0 255
Script Table
Meter Program Configuration 0 1 94 96 10 255
Meter Program Configuration Data
0 1 94 96 11 255
Status (class id: 1, version: 0)
1) Attributes description of the objects “Global Meter Reset”
Page 90 / 135

Access right
- A. 2 A. 3 A. 4
Methods
1. execute long-unsigned - - - A
a) “script_identifier” for Global Meter Reset
- Holds a list of meter operational commands, where “script_identifier” of the “scripts”

identifies the commands to be executed. Each script identifier and the corresponding
command are specified in the tables below.
- It works as a command to reset the meter, initializing metering data and meter
configuration such as the regular date for reading or TOU.
- In order to allow the selection and editing of the Parameters which have to be included
in the Global Meter Reset command, it is mandatory to include the “delete” method (as
defined in the DLMS UA Blue Book) in all these parameters. Parameters to be included
can be checked in as depicted in the WC Meter Specification Last Version
Script_identifier for Global Meter Reset

Script _identifier
Meaning
(2 bytes)
0x0001 Global meter reset
2) Attributes description of the objects “Meter Program Configuration”

Access right
- A. 2 A. 3 A. 4
Methods
Page 91 / 135

1. execute long-unsigned - - A A
a) “script_identifier” for Meter Program Configuration
Script_identifier for Meter Program Configuration

Script _identifier
Meaning
(2 bytes)
0x0001 Meter program download mode
0x0002 Activating Passive meter program
0x0003 Reading Active meter program
0x0004 Reserving activation of Passive meter program
0x0005 Reading Passive meter program
0x0006 Deleting Passive meter program
0x0007 Normal operation mode
0x0008 Reserved
0x0009 Reserved
0x0010 Reserved
A. Meter program download mode

- It is a command to inform the meter of the beginning of download mode of the meter
program such as the regular date for reading or TOU, and the meter program will be
input to meter after giving this command. After this command the clients (HHU,
DCU or HES Server) can send the "set command (or download program)" to the
meters, and accordingly the meters accept and apply the register's setting values into
the registers.
B. Activating Passive meter program

- It is a command to activate a meter program which has been downloaded to the meter.
If this command is given after downloading a meter program, the meter will run by
the meter program recently downloaded. After this command, the meters will run by
the newly applied setting values (or the downloaded program).
C. Reading Active meter program
Page 92 / 135

- It is a command to direct the meter to begin the reading mode of the currently running
meter program (e.g. TOU or the regular date for reading). After issuing this command,
a client can read out the currently running meter program from meter.
D. Reserving activation of Passive meter program

- It is a command to reserve the activation of new meter program (currently
downloaded but not activated yet). If this command is issued after downloading a
new meter program, the downloaded meter program will be activated at the
designated date.
E. Reading Passive meter program

- It is a command to direct the meter to begin the reading mode of the Passive (reserved)
meter program (e.g. TOU, the regular date for reading), the Passive meter program is
readable from meter after issuing this command.
F. Deleting Passive meter program

- It is a command to delete the Passive (reserved) meter program.
G. Normal operation mode

- It is a command to turn the meter back into the normal operation mode.
b) Procedure for Meter Configuration programming

① The user sends a script to make the meter in download mode.
② The user starts sending the setting in the above table where each one is independent
from each other.
③ If any loose of current HDLC session, the user should send the Meter Download
Mode script again after the new HDLC connection established and he can continue
or start from beginning.
④ The Order of the Messages is not required but Setting ALL MSG is required except
special days object which is optional.
⑤ Confirm the setting done by putting the Mode to Reading Passive Meter Program and
start reading the same OBIS.
⑥ The meter will check the accuracy of the settings at:
i. When he user send Immediate activation Method MSG
ii. When he user send next Program time/Date
⑦ And if any problem in the data the meter will do the below action:
i. The Meter will reject the WHOLE Passive setting and will keep the active as it
is.
ii. The Meter keeps the Passive Setting in the EEPROM Memory for user checking.
⑧ The Activation with Reserving activation of Passive Meter Program will be used with
Page 93 / 135

DATE/TIME of NEXT METER PROGRAM CHANGE Object (0.0.96.2.6.255).
c) List of meter configuration sets
[Note] The file format of a meter program related meter configuration sets shall be specified
during the development phase of the field management software for meters by the
Contractor and provided to COMPANY for Approval.
No Description Related Object OBIS Code
Current over limit threshold 1.0.11.35.0.255
Current over limit duration 1.0.11.44.0.255

1 Threshold Value
Voltage under limit threshold 1.0.12.31.0.255
Voltage under limit duration 1.0.12.43.0.255
2 Remote output relay control Disconnect control 0.0.96.3.10.255

Regular/irregular date for
3 EOB single action schedule 0.0.15.0.0.255
meter reading
4 Meter reading parameter Meter reading parameter 0.0.15.128.0.255
5 Load profile interval Load profile interval 1.0.0.8.4.255
6 Passive calendar name

7 Passive season profile name
Activity Calendar 0.0.13.0.0.255
8 Passive week profile name
9 Passive day profile name
Regular and Irregular
10 Special Days Table 0.0.11.0.0.255
Holidays
Normal display list 0.0.21.0.0.255
11 Display List
Test display list 0.0.21.0.1.255
Selection of the input control
12 Remote output relay control 0.96.94.96.8.255
signals
Auto recovery times setting
13 Remote output relay control 0.96.94.96.10.255
of current over limit
Page 94 / 135

[Note] After setting the meter to be in Download Mode, the meter will accept only the list of
thirteen (13) OBISs (parameters) described in the above table. Once the meter is back to
normal operation mode it can be communicated normally and all OBIS’s will be available.
Also, individual setting of the thirteen (13) OBISs’ shall be possible.
d) Attribute description of the object “Meter Program Configuration Status”

Access right
- A. 2 A. 3 A. 4
2. value Enum (see below) - R R R
Enum Description
1 Meter program download mode
2 Activating Passive meter program
3 Reading Active meter program
Reserving activation of Passive meter
4
program
5 Reading Passive meter program
6 Deleting Passive meter program
7 Normal operation mode
8 Reserved
9 Reserved
10 Reserved
6.9.5. Number/time of meter program change
The number/time of meter program change objects are modeled by the “Data” IC (class id: 1, version:
0).
Page 95 / 135

OBIS code
A B C D E F
Data
Number of meter program changes 0 0 96 2 0 255
Date/Time of last meter program Data
0 0 96 2 1 255
change (class id: 1, version: 0)
Date/Time of next meter program Data
0 0 96 2 6 255
change (class id: 1, version: 0)
a) Attribute description of the objects “Number of meter program change”

Access right
- A. 2 A. 3 A. 4
2. value long-unsigned - R R R
b) Attribute description of the objects “Date/Time of last meter program change”

Access right
- A. 2 A. 3 A. 4
2. value - R R R
SIZE(12))
c) Attribute description of the objects “Date/Time of next meter program change”

- The object “Date/Time of next meter program change” holds the next date and time for
activating the reserved meter program mentioned in Clause 6.9.3.

Access right
- A. 2 A. 3 A. 4
Page 96 / 135


SIZE(12))
6.9.6. Current active tariff
The current active tariff object is modeled by the “Data” IC (class id: 1, version: 0). This object
holds the current active tariff period number (TOU number).
OBIS code
A B C D E F
Data
Current tariff 0 0 96 14 0 255
1) Attribute description of the objects “Current active tariff”

Access right
- A. 2 A. 3 A. 4
unsigned [8]
value = 1: Tariff 1, value = 2: Tariff 2
2. value value = 3: Tariff 3, value = 4: Tariff 4 - R R R
6.9.7. Error Registers
The error registers are modeled by the “Data” IC (class id: 1, version: 0). These objects are used
for self-diagnosis purposes and being recorded into the event logs. The error registers have to be
defined together with the vendor
OBIS code
A B C D E F
Data
Error Register 1 0 0 97 97 0 255
Page 97 / 135

Data
Data
Data
Data
Data
[Note] The EventNotification function shall be activated by error registers above. Thus, when
the errors defined in those error registers occur, the meter shall trigger the ‘Push script table’
(refer to Section 6.11 Push objects) to send the events to client without receiving request.
1) Attribute description of the objects “Error registers”

Access right
- A. 2 A. 3 A. 4
2. value bit-string - R R R
2) Bit-wise status mapping of the attribute “value” of each object
[Note]
1. In event of relevant status, the corresponding bit will be set to 1 in binary system. When the
error event is resolved, the corresponding bit is returned to zero.
2. These error registers are captured into the “Event Log” objects (Interface Class: Profile generic)
whenever their status is changed (set to ‘1’ and return to zero).
3. Each bit of Error Registers shall detect each error state separately (sharing the same sensor is
not acceptable).
a) Error Register 1
MSB bit6 bit5 bit4 bit3 bit2 bit1 LSB
Page 98 / 135

Low/Failur
Password Meter Memory Clock
- - - e Storage
changed initialization error initialization
Device
b) Error Register 2

Current Current Current Missing
Voltage cut Voltage cut Voltage cut
Missing Missing Missing neutral line
(L3) (L2) (L1)
(L3) (L2) (L1) connection
[Note]
1. If the meter has three normal voltage values with all "0" current phase values (a certain
threshold value, e.g. under 0.001A), then the meter shall not make any Current Missing event
(no energy consumption). In case, any one or two current phases have some current values
(e.g. over 0.001A) and the other current phase (s) have "0" current phase values (e.g. under
0.001A) with normal voltage values, then the meter shall make Current Missing event (s) to
the "0" current phase (s) using its internal program.
2. The range of Voltage Cut is 0V ~ below 30V.
c) Error Register 3

Phase and Phase and Phase and
Top Terminal Reverse Reverse Reverse
neutral wire neutral wire neutral wire
cover cover current current current
swapped swapped swapped
open open (L3) (L2) (L1)
(L3) (L2) (L1)
d) Error Register 4

Low Low Low Over Over Over
∑Li PF under
- voltage voltage voltage current current current
limit threshold
(L3) (L2) (L1) (L3) (L2) (L1)
[Note] 1. The duration of ∑Li PF under limit threshold (bit 6) is same as LP/Demand period.
2. The range of Low Voltage is 30V ~ Threshold value.
e) Error Register 5
Page 99 / 135


Wrong Phase- Phase- Phase- Phase Phase Phase
Magnetic
password neutral neutral neutral sequence sequence sequence
interference
tried bypassing bypassing bypassing reversal reversal reversal
detected
(3 times) (L3-N) (L2-N) (L1-N) (L1-L2) (L1-L3) (L2-L3)
f) Error Register 6

Swell Sag Harmonics Maximum Output relay Temperature
limit limit limit current state over limit
6.9.8. Number of Events
These objects are defined to represent number information of meter events. These objects are not
access directly, but recorded into the event logs.
OBIS code
A B C D E F
Number of power failures Data
0 0 96 7 0 255
(in all three phases) (class id: 1, version: 0)
0 0 96 7 1 255
(Phase L1) (class id: 1, version: 0)
0 0 96 7 2 255
0 0 96 7 3 255
Number of power restore Data
0 1 94 96 3 255
(in all three phases) (class id: 1, version: 0)
0 1 94 96 4 255
0 1 94 96 5 255
0 1 94 96 6 255
Data
Number of clock change 0 0 96 11 1 255
Page 100 / 135


OBIS code
A B C D E F
Data
Number of EOB reset 0 0 96 11 2 255
Data
Number of manual reset 0 0 96 11 3 255
Data
Number of auto-reset 0 0 96 11 4 255
Data
Number of Current Missing 0 0 96 11 5 255
Data
Number of top cover open 0 0 96 11 6 255
Data
Number of terminal cover open 0 0 96 11 7 255
Data
Number of phase-neutral swap 0 0 96 11 8 255
Data
Number of reverse current 0 0 96 11 9 255
Number of magnetic interference Data
0 0 96 11 10 255
tampering (class id: 1, version: 0)
Data
Number of phase-neutral bypassing 0 0 96 15 0 255
Data
Number of phase sequence reversal 0 0 96 15 1 255
Data
Number of neutral line missing 1 0 91 40 0 255
Data
Number of voltage cut 1 0 12 40 0 255
Data
Number of password changes 0 0 96 15 2 255
Number of state change of output relay Data
0 96 96 4 1 255
control signals (class id: 1, version: 0)
Number of selection of the input Data
0 96 96 4 2 255
control signals (class id: 1, version: 0)
Number of auto recovery operation Data
0 96 96 4 3 255
times of current over limit (class id: 1, version: 0)
Number of auto recovery times setting Data
0 96 96 4 4 255
of current over limit (class id: 1, version: 0)
Data
Number of current over limit release 0 96 96 4 5 255
Page 101 / 135


OBIS code
A B C D E F
Data
Number of abnormal temperature 0 96 96 4 6 255
Data
Number of maximum current 0 96 96 4 7 255
Data
Number of harmonics (THD) limit 0 96 96 4 8 255
Data
Number of Sag limit 0 96 12 32 0 255
Data
Number of Swell limit 0 96 12 36 0 255
Data
Number of Global Meter Reset 0 96 94 96 15 255
Data
Number of wrong cable connection 0 96 94 96 16 255
1) Attribute description of the objects “Number of …”

Access right
- A. 2 A. 3 A. 4
1. logical_name octet-string - - R R
2. value long-unsigned [18] - - R R
[Note]
All values of “Number of …” shall be reset after the last EOB reset on 1st day January of each year.
6.9.9. Data Transport Security Mode
The Data Transport Security function Enable/Disable Mode object is modeled by the “Data” IC
(class id: 1, version: 0). This object is setting and reading the meter’s status whether the Data
Transport Security function is enabled or disabled.
OBIS code
A B C D E F
Data
Data Transport Security Mode 0 1 94 96 12 255
Page 102 / 135


1) Attribute description of the objects “Data Transport Security Mode”

Access right
- A. 2 A. 3 A. 4
Boolean
2. value [TRUE = Enabled, - R R/W R/W
FALSE = Disabled (default)]
6.9.10. Information security related objects
Instances of the IC “Security setup” – see 4.4.7 of DLMS Bluebook – are used to set up the
message security features. For each Association object, there is one Security setup object
managing security within that AA. See 5.4.4 and 5.4.5. Value group E numbers the instances.
Invocation counter objects hold the invocation counter element of the initialization vector. They
are instances of the IC “Data”. The value in value group B identifies the communication channel.
Instances of the IC “Data protection” – see 4.4.9 of DLMS Bluebook – are used to apply / remove
protection on COSEM data, i.e. sets of attributes values, method invocation and return parameters.
Value group E numbers the instances.
OBIS code
A B C D E F
Push setup
Security Setup 0 0 43 0 e 255
Data
Invocation Counter 0 b 43 1 e 255
Data Protection
Data Protection 0 0 43 2 e 255
1) Attributes description of the objects “Security Setup”
Security Setup Class_id = 64, version = 0

Page 103 / 135


- A. 2 A. 3 A. 4
2. security_policy enum (default: 0) - R/W R/W R/W
3. security_suite Enum (default: 0) - R/W R/W R/W
4. client_system_title octet_string - R/W R/W R/W
5. server_system_title octet_string - - R R
Methods
1. security_activate m - - - -
2.global_key_transfer m - - - -
2) Attribute description of the objects “Invocation Counter”

Access right
- A. 2 A. 3 A. 4
2. value long-unsigned - R R/W R/W
3) Attributes description of the objects “Data Protection”
Security Setup Class_id = 30, version = 0

Access right
- A. 2 A. 3 A. 4
2.protection_buffer octet_string - - R R/W
3. protection_object_list array - - R R/W
4. protection_paramenter_get array - - R R/W
5. protection_paramenter_set array - - R R/W
6. required_protection enum - - R R/W
Methods
Page 104 / 135


1. get_protected_attribute (data) m - - - -
2. set_protected_attribute (data) m - - - -
3. invoke protected_method
m - - - -
(data)
[Note] The detail attributes and methods data of Security-related OBIS codes, including detail
technical specifications and Security Events shall be proposed and implemented by the Vendor.
The proposed detail technical specifications shall be approved by COMPANY.
6.9.11. Temperature over limit threshold
The Residue Price object is modeled by the “Register” IC (class id: 3, version: 0).
OBIS code
A B C D E F
Register
Temperature over limit threshold 0 96 128 35 0 255
Register
Temperature over limit duration 0 96 128 35 1 255
1) Attributes description of the object “Temperature over limit threshold”

Access right
- A. 2 A. 3 A. 4
scaler: 0 (integer)
Unit: 9 [temperature, ◦C]
2) Attributes description of the object “Temperature over limit duration”

Access right
- A. 2 A. 3 A. 4
Page 105 / 135


scaler: 0 (integer)
Unit: 7 [second, time]
6.9.12. Average Voltages and Currents
The average voltages and currents profile data are modeled by the “Profile Generic” IC (Class id=7,
version: 1).
OBIS code
A B C D E F
Average Voltages and Profile Generic
1 96 99 13 0 255
Currents Profile (Class id=7, version: 1)
1) Attributes description of the object “Average Voltages and Currents Profile”

Access right
- A. 2 A. 3 A. 4
double-long-unsigned [unit: minute]
Programmable (default: 15)
enum
8. profile_entries [larger than 288: 15 minutes, three (3) - - R R
days, (record 96 per one (1) day)]
2) Capture_objects description of the object “Average Voltages and Currents Profile”
Page 106 / 135



R-Y Phase average voltage 1.0.32.128.0.255 2 0
R Phase instantaneous voltage THD 1.0.32.7.124.255 2 0
R Phase average current 1.0.31.5.0.255 2 0
Y-B Phase average voltage 1.0.52.128.0.255 2 0
Y Phase instantaneous voltage THD 1.0.52.7.124.255 2 0
Y Phase average current 1.0.51.5.0.255 2 0
B-R Phase average voltage 1.0.72.128.0.255 2 0
B Phase instantaneous voltage THD 1.0.72.7.124.255 2 0
B Phase average current 1.0.71.5.0.255 2 0
[Note]
1. The Average Voltages and Currents Profile object captures “the attribute 2” of each
register in above table (capture objects).
2. Capture_period shall be as per the “Average Voltages and Currents Profile Interval”
3) Attributes description of the objects average voltages, instantaneous voltage THDs and
average currents.

Access right
- A. 2 A. 3 A. 4
2. value double-long-unsigned - R R/W R/W
[Ampere]
Scaler: -3 (integer), Unit: 33 [A]
[Voltage]
3. scaler_unit Scaler: -3 (integer), Unit: 35 [V] - R R R
[Voltage THD]
Scaler: 0 (integer), Unit: 56 [%,
percentage]
Page 107 / 135


6.9.13. Average Voltages and Currents Profile Interval
This object holds the interval recording duration for the average voltages and currents profile.
OBIS code
A B C D E F
Average Voltages and Currents
1 96 128 0 12 255 Register
Profile Interval
1) Attributes description of the object “Average Voltages and Currents Profile Interval”

Access right
- A. 2 A. 3 A. 4
unsigned
default value: 15 minutes
(configurable among 5, 15, 30, 60
minutes)
scaler: 0 (integer)
unit: 6 [minute, time]
6.9.14. Sag Setting Value
The sag setting value data is modeled by the “Register” IC (Class id=3, version: 0).
OBIS code
A B C D E F
Register
Sag setting value 1 96 12 31 0 255
1) Attributes description of the object “Sag setting value”

Access right
- A. 2 A. 3 A. 4
Page 108 / 135


scaler: 0 (integer)
unit: 56 [%, percentage]
6.9.15. Sag Setting Time
The sag setting time data is modeled by the “Register” IC (Class id=3, version: 0).
OBIS code
A B C D E F
Register
1) Attributes description of the object “Sag setting time”

Access right
- A. 2 A. 3 A. 4
Unsigned (default: 5 seconds)
2. value (configurable among 1, 5, 15, 30, - R R/W R/W
60 seconds)
scaler: 0 (integer)
unit: 7 [second, time]
6.9.16. Swell Setting Value
The swell setting value data is modeled by the “Register” IC (Class id=3, version: 0).
OBIS code
A B C D E F
Register
1) Attributes description of the object “Swell setting value”
Page 109 / 135



Access right
- A. 2 A. 3 A. 4
scaler: 0 (integer)
unit: 56 [%, percentage]
6.9.17. Swell Setting Time
The swell setting time data is modeled by the “Register” IC (Class id=3, version: 0).
OBIS code
A B C D E F
Register
1) Attributes description of the object “Swell setting time”

Access right
- A. 2 A. 3 A. 4
Unsigned (default: 5 seconds)
2. value (configurable among 1, 5, 15, 30, - R R/W R/W
60 seconds)
scaler: 0 (integer)
6.9.18. Magnetic Interference Detection Time
The swell setting time data is modeled by the “Register” IC (Class id=3, version: 0).
Page 110 / 135


OBIS code
A B C D E F
Magnetic Interference Register
1 96 128 0 3 255
Detection Time (Class id=3, version: 0)
1) Attributes description of the object “Magnetic Interference Detection Time”

Access right
- A. 2 A. 3 A. 4
scaler: 0 (integer)
6.9.19. Instantaneous Values Profile
The instantaneous values profile data are modeled by the “Profile Generic” IC (Class id=7, version:
1).
OBIS code
A B C D E F
Average Voltages and Profile Generic
1 96 98 128 0 255
Currents Profile (Class id=7, version: 1)
1) Attributes description of the object “Instantaneous values profile”
Page 111 / 135



Access right
- A. 2 A. 3 A. 4
Double-long-unsigned
Enum
[maximum entry: 1]
2) Capture_objects description of the object “Instantaneous values Profile”

R Phase instantaneous current 1.0.31.7.0.255 2 0
R Phase instantaneous voltage 1.0.32.7.0.255 2 0
R Phase instantaneous voltage THD 1.0.32.7.124.255 2 0
R Phase instantaneous power factor 1.0.33.7.0.255 2 0
R Phase voltage-current phase angle 1.0.81.7.40.255 2 0
Y Phase instantaneous current 1.0.51.7.0.255 2 0
Y Phase instantaneous voltage 1.0.52.7.0.255 2 0
Y Phase instantaneous voltage THD 1.0.52.7.124.255 2 0
Y Phase instantaneous power factor 1.0.53.7.0.255 2 0
Y Phase voltage-current phase angle 1.0.81.7.51.255 2 0
B Phase instantaneous current 1.0.71.7.0.255 2 0
B Phase instantaneous voltage 1.0.72.7.0.255 2 0
B Phase instantaneous voltage THD 1.0.72.7.124.255 2 0
Page 112 / 135



B Phase instantaneous power factor 1.0.73.7.0.255 2 0
B Phase voltage-current phase angle 1.0.81.7.62.255 2 0
Phase angle of voltage R phase and voltage Y
1.0.81.7.10.255 2 0
phase
Phase angle of voltage Y phase and voltage B
1.0.81.7.20.255 2 0
phase
Current temperature 0.0.96.9.0.255 2 0
[Note] The Instantaneous Values Profile object captures “the attribute 2” of each register in above
table (capture objects).
3) Attributes description of the objects of instantaneous currents, voltages, voltage THDs,

power factor, phase angles and temperature.

Access right
- A. 2 A. 3 A. 4
[Ampere]
Scaler: -3 (integer), Unit: 33 (A)
[Voltage]
Scaler: -3 (integer), Unit: 35 (V)
[Voltage THD]
Scaler: 0 (integer), Unit: 56 (%,
percentage)
3. scaler_unit [Power Factor] - R R R
Scaler: -3 (integer), Unit: 255 (unitless)
[Phase Angle]
Scaler: 0 (integer), Unit: 8 (◦, degree)
[Temperature]
Scaler: 0 (integer), Unit: 9 (◦C, degree-
celsius)
6.9.20. Security Association Event
Page 113 / 135


The Security Association Event Code data is modeled by the “Data” IC (Class id=1, version: 0).
OBIS code
A B C D E F
Data
Security Association Event 0 96 99 98 19 255
1) Attributes description of the object “Security Association Event”.

Access right
- A. 2 A. 3 A. 4
2. value visual-string (size (4 byte)) - R R/W R/W
[Note]
1. The value shall be separated higher 2 bytes (security event code) and low 2 bytes (security
error code). The value of Security Association Event shall be configured as “high two
bytes (01) + low two bytes (81)”, i.e.) “0181”.
2. The detail data of Security Association Event shall be implemented by the Vendor, when
COMPANY provides the specific information.
6.10. Event Log
The event log profiles are modeled by the “Profile Genetic” IC (class id: 7, version: 1).
These profile generic objects for event logging capture their capture_objects whenever any event
defined in this clause occurs. The specific methods for capturing those capture_objects on an event
basis shall be implemented by manufacturers.
OBIS code
A B C D E F
Event log Profile Generic
1 0 99 97 0 255
(Power failure) (class id: 7, version: 1)
1 0 99 98 2 255
(Power restore) (class id: 7, version: 1)
1 0 99 98 3 255
(Time change: from time) (class id: 7, version: 1)
Page 114 / 135


OBIS code
A B C D E F
1 0 99 98 4 255
(Time change: to time) (class id: 7, version: 1)
1 0 99 98 5 255
(EOB reset) (class id: 7, version: 1)
1 0 99 98 6 255
(Manual reset) (class id: 7, version: 1)
1 0 99 98 7 255
(Auto-reset) (class id: 7, version: 1)
1 0 99 98 8 255
(Meter configuration change) (class id: 7, version: 1)
Event Log Profile Generic
1 0 99 98 9 255
(Communication port log) (class id: 7, version: 1)
1 0 99 98 10 255
(Storage Device /Memory) (class id: 7, version: 1)
1 0 99 98 11 255
(Power line cut) (class id: 7, version: 1)
1 0 99 98 12 255
(Tamper 1) (class id: 7, version: 1)
1 0 99 98 13 255
(Tamper 2) (class id: 7, version: 1)
Event log
Profile Generic
(Current/voltage limit 1 0 99 98 14 255
violation)
1 0 99 98 15 255
(Output relay control) (class id: 7, version: 1)
1 0 99 98 16 255
(Password changes) (class id: 7, version: 1)
State of output relay control Profile Generic
1 96 99 98 12 255
signals (ON/OFF) (class id: 7, version: 1)
Selection of the input control Profile Generic
1 96 99 98 2 255
signals (class id: 7, version: 1)
Auto recovery operation times Profile Generic
1 96 99 98 3 255
of current over limit (class id: 7, version: 1)
Auto recovery times setting of Profile Generic
1 96 99 98 4 255
Profile Generic
Current over limit release 1 96 99 98 13 255
Temperature over limit 1 96 99 98 6 255 Profile Generic
Page 115 / 135


OBIS code
A B C D E F
Profile Generic
Maximum current 1 96 99 98 7 255
Profile Generic
Harmonics (THD) limit 1 96 99 98 8 255
Profile Generic
Sag limit 1 96 99 10 1 255
Profile Generic
Swell limit 1 96 99 10 2 255
Profile Generic
Security association Event 1 96 99 98 19 255
Display Roll-Over to Zero 1 96 99 98 20 255 Profile Generic (class
Event id: 7, version: 1)
1) Attributes description of the objects “Profile Generic”

Access right
- A. 2 A. 3 A. 4
3. capture_objects array (See below table) - R R R
5. sort_method enum: FIFO (first in first out) - - R R
8. profile_entries double-long-unsigned - - R R
a) “capture_object” of each event log profiles
Page 116 / 135


Interface Attribute
Classification Capture_objects OBIS code
class index
Current date/time 0.0.1.0.0.255 Clock 2
Number of power failure
0.0.96.7.0.255 Data 2
(in all three phases)
Event Log Number of power failure
0.0.96.7.1.255 Data 2
(Power failure) (phases L1)
0.0.96.7.2.255 Data 2
(phases L2)
0.0.96.7.3.255 Data 2
(phases L3)
Number of power restore
0.1.94.96.3.255 Data 2
(in all three phases)
Event Log Number of power restore
0.1.94.96.4.255 Data 2
(Power restore) (phases L1)
0.1.94.96.5.255 Data 2
(phases L2)
0.1.94.96.6.255 Data 2
(phases L3)
Event Log Current date/time 0.0.1.0.0.255 Clock 2
(Time before change) Number of clock change 0.0.96.11.1.255 Data 2
(Time after change) Number of clock change 0.0.96.11.1.255 Data 2
(EOB reset) Number of EOB reset 0.0.96.11.2.255 Data 2
(Manual reset) Number of manual reset 0.0.96.11.3.255 Data 2
(Auto Reset) Number of Auto Reset 0.0.96.11.4.255 Data 2
(Meter configuration Number of meter program
change) 0.0.96.2.0.255 Data 2
change
(Communication port Number of optical port
log) 0.0.96.12.1.255 Data 2
connection/disconnection
Page 117 / 135


Interface Attribute
class index
Communication port status
0.0.96.12.4.255 Data 2
change
(Storage Device
/Memory) Error register 1 0.0.97.97.0.255 Data 2
Error register 2 0.0.97.97.1.255 Data 2
Event Log
(Power line cut) Number of neutral line
1.0.91.40.0.255 Data 2
missing
Number of voltage cut 1.0.12.40.0.255 Data 2
Number of top cover open 0.0.96.11.6.255 Data 2
Event Log Number of terminal cover
(Tamper 1) 0.0.96.11.7.255 Data 2
open
Number of phase-neutral
0.0.96.11.8.255 Data 2
swap
Number of reverse current 0.0.96.11.9.255 Data 2
Number of phase-neutral
Event Log 0.0.96.15.0.255 Data 2
bypassing
(Tamper 2) Number of phase sequence
0.0.96.15.1.255 Data 2
reversal
Number of magnetic
0.0.96.11.10.255 Data 2
interference tampering
Event log Current date/time 0.0.1.0.0.255 Clock 2
(Current/voltage/
Power Factor limit Error register 4 0.0.97.97.3.255 Data 2
violation)
Event Log Disconnect
Disconnect control 0.0.96.3.10.255 2
(Output relay control) control
State of output relay
0.0.96.3.2.255 Data 2
control signals (ON/OFF)
Page 118 / 135


Interface Attribute
class index
Selection of the input
0.96.94.96.8.255 Data 2
control signals
Auto recovery operation
0.96.94.96.9.255 Data 2
times of current over limit
Auto recovery times
setting of current over 0.96.94.96.10.255 Data 2
limit
Release times of current
0.96.94.96.11.255 Data 2
over limit setting
Event Log Number of password
0.0.96.15.2.255 Data 2
(Password changes) changes
Association
Current Association 0.0.40.0.0.255 3
LN
(Error register 6) Error register 6 0.0.97.97.5.255 Data 2
(Security association) Security association Event 0.96.99.98.19.255 Data 2
(Display Roll-Over to Number of Roll-Over to 0.0.96.11.11.255 Data 2
Zero) Zero
[Note] In case of Security Association Event, the event shall be logged up to maximum 255 events
(FIFO).
6.11. Push objects
The push objects are used when some DLMS messages can be ‘pushed’ to a destination without
being explicitly requested.
The core element of modelling the push operation is the “Push setup” IC. The push_object_list
attribute contains a list of references to COSEM object attributes to be pushed.
The local trigger (e.g. upon power on) and event trigger (e.g. error registers in Section 6.9.7) call a
script entry in a Push “Script table” object which invokes then the push method of the related
“Push setup” object.
e.g.) The push operation explained above is depicted in diagram below:
Page 119 / 135


The "Push setup” IC contains a list of references to COSEM object attributes to be pushed. It also
contains the push destination and method as well as the communication time windows and the
handling of retries. And the “Push script table” object is used for activating the push setup objects
by various triggers.
OBIS code
A B C D E F
Push setup
Push setup 1 0 1 25 9 0 255
Push setup
Push setup 2 0 2 25 9 0 255
Push setup
Push setup 3 0 3 25 9 0 255
Push setup
Push setup 4 0 4 25 9 0 255
Push setup
Push setup 5 0 5 25 9 0 255
Push setup
Push setup 6 0 6 25 9 0 255
Push setup
Push setup 7 0 7 25 9 0 255
Push script table 0 0 10 0 108 255 Script table
Page 120 / 135


1) Attributes description of the objects “Push setup”
Push setup Class_id = 40, version = 0

Access right
- A. 2 A. 3 A. 4
2. push_object_list array (see below) - - R R/W
3. send_destination_and_method structure - - R R/W
array
4. communication_window - - R R/W
(default: array [0])
long-unsigned
5. randomization_start_interval - - R/W R/W
(default: 10 [sec])
unsigned
6. number_of_retries - - R/W R/W
(default: 3)
long_unsigned
7. repetition_delay - - R R/W
(default: 5 [sec])
Methods
1. push (data) m - - - -
[Note] If the values of both randomization_start_interval and number_of_retry are set (written)
to zero (0), it means that the Push Setup shall be disabled automatically by the meter.
a) Attribute “push_object_list”
The objects which are pushed to COSEM clients are defined in this attribute.
array object_definition
object_definition ::= structure
{
class_id: long-unsigned,
logical_name: octet-string,
attribute_index: integer,
data_index: long-unsigned
}
The objects to be pushed by each “push setup” object shall be configurable. However the default
set is shown below:
Page 121 / 135


Member of array (structure)

‘Push setup’ object attribute data
Object name class_id logical_name
_index _index
COSEM logical device
Push setup 1 1 0.0.42.0.0.255 2 0
name
Push setup 2 Error Register 1 1 0.0.97.97.0.255 2 0
b) Attribute “send_destination_and_method”
Contains the destination address where the data specified by the push_object_list has to be
sent, as well as the sending method.
send_destination_and_method ::= structure
{
transport_service: transport_service_type,
destination: octet-string,
message: message_type
}
Element Default value
transport_service (5) HDLC

destination 0x03
message (0) A-XDR encoded xDLMS APDU
2) Attributes description of the objects “Push script table”
Page 122 / 135


Access right
- A. 2 A. 3 A. 4
2. scripts array (see below) - R R R/W
Methods
1. execute long-unsigned - - A A
a) Description of ‘scripts’ attribute for Push script table

actions
Script_identifier
service_id class_id logical_name index parameter
0x0001 (2) 40 0.1.25.9.0.255 1 0
0x0002 (2) 40 0.2.25.9.0.255 1 0
0x0003 (2) 40 0.3.25.9.0.255 1 0
0x0004 (2) 40 0.4.25.9.0.255 1 0
0x0005 (2) 40 0.5.25.9.0.255 1 0
0x0006 (2) 40 0.6.25.9.0.255 1 0
0x0007 (2) 40 0.7.25.9.0.255 1 0
6.12. Access Control and Management Objects
6.12.1. Association LN
COSEM logical devices are able to establish Application Associations (AAs) within a COSEM
context using LN (Logical Name) referencing, model the AAs through instances of the “Association
LN” object. Refer to 5.3.2. of IEC 62056-6-2 for details. A COSEM logical device has one
“Association LN” object for each AA the device is able to support. In this specification, since the
four associations are defined,
The Association LN objects are modeled by the “Association LN” IC (class id: 15, version: 1).
OBIS code
A B C D E F
Association LN
Current Association 0 0 40 0 0 255
Association LN
Association LN #2 0 0 40 0 2 255
Association LN #3 0 0 40 0 3 255 Association LN
Page 123 / 135



Association LN
Association LN #4 0 0 40 0 4 255
* The “Association LN #n” objects are corresponding with the four associations which the
management logical devices of the meter support (Association 2~4).
1) Attributes description of the object “Current Association”
Association LN Class_id = 15, version = 1

Access right
A. 2 A. 3 A. 4
1. logical_name octet-string R R R
2. object_list object_list_type (see below) R R R
3. associated_partners_id associated_partners_type R R R
4. application_context_name application_context_name R R R
5. xDLMS_context_info xDLMS_context_type R R R
6. authentication_mechanism
mechanism_name R R R
_name
7. secret octet-string R/W R/W R/W
8. association_status enum (see below) R R R
9. security_setup_reference octet-string - R R R
Specific methods m/o
1. reply_to_HLS_authentication
m
(data)
2. change_HLS_secret (data) m
3. add_object (data) m
4. remove_object (data) m
2) Attributes description of the object “Association LN #2” and “Association LN #3”
Page 124 / 135



Access right
- A. 2 A. 3 A. 4
2. object_list object_list_type (see below) - R R R
3. associated_partners_id associated_partners_type - R R R
4. application_context_name application_context_name - R R R
5. xDLMS_context_info xDLMS_context_type - R R R
6. authentication_mechanism -
_name
m
(data)
3) Attributes description of the object “Association LN #4” and “Association LN #5”

Access right
- A. 2 A. 3 A. 4
2. object_list object_list_type (see below) - R R R
3. associated_partners_id associated_partners_type - R R R
4. application_context_name application_context_name - R R R
5. xDLMS_context_info xDLMS_context_type - R R R
6. authentication_mechanism -
_name
Page 125 / 135



Access right
- A. 2 A. 3 A. 4
m
(data)
a) Attribute “object_list”
- Contains the list of visible COSEM objects with their class_id, version, logical name
and the access rights to their attributes and methods within the given application
association.
- In case of HLS authentication s (Assoc. 2, 3, 4 and 5), the Access Rights of each LLS
association shall be the same of each HLS association with "authenticated" access mode
respectively.
b) Attribute “associated_partners_id”
- Contains the identifiers of the COSEM client and the COSEM server (logical device)
application processes within the physical devices hosting these processes, which belong
to the application association modeled by the “Association LN” object.
- The value of the client_SAP for each user group is described below.
Client_SAP
User Association Index (=Client HDLC Address)
LLS HLS
AMR Readers Association 2 0x02 0x09
Utility Engineers /
Association 3 0x03 0x0A
Management
Page 126 / 135


Management/SEC Lab Association 4 0x04 0x0B

Security Server Association 5 0x05 0x0C
c) Attribute “application_context_name”
- In the COSEM environment, it is intended that an application context pre-exist and is

referenced by its name during the establishment of an AA. This attribute contains the
name of the application context for that association.
d) Attribute “xDLMS_context_info”
- Contains all the necessary information on the xDLMS context for the given association.
e) Attribute “authentication_mechanism_name”
- Contains the name of the authentication mechanism for the association.
CHOICE
{
structure [2],
//Data type: UNSIGNED8
//Authorized value: 0 to 255
//Default value: 0
octet-string [9]
}
The authentication mechanism name is specified as an OBJECT IDENTIFIER in
clause No.9.4.2.3.3 of the Green Book(7th Edition).
The authentication_mechanism_name attribute includes the arc labels of the OBJECT
IDENTIFIER.
No mechanism-name is required when no authentication is used..
f) Attribute “secret”
- Contains the secret for LLS authentication process (octet-string (size: 4~10 bytes)). Each
secret for association 2, 3, 4 and 5 is to be provided by Contractor to COMPANY.
- LLS Association 3 (Access Right) can read/write the secret passwords for Assoc.2 and
Assoc.3 (except for Assoc.4).
- LLS Association 4 (Access Right) can read/write the secret passwords for Assoc.2,
Page 127 / 135


Assoc.3 and Assoc.4 (Access Right of Association 5 will be the same Assoc.4).
- Contains the secret for HLS authentication process (octet-string (size: 4~10 bytes)).
Each secret for association 2, 3, 4 and 5 is to be provided by Contractor to COMPANY.
- HLS Association 3 (Access Right) can read/write the secret passwords for Assoc.2 and
Assoc.3 (except for Assoc.4).
- HLS Association 4 (Access Right) can read/write the secret passwords for Assoc.2,
Assoc.3 and Assoc.4 (Access Right of Association 5 will be the same Assoc.4).
- Each HLS shall have the read / write Access Right for each LLS and lower level LLSs
than its LLS.
g) “association_status”
- Indicates the current status of the association, which is modeled by the object.
- Enum: (0) non-associated, (1) association-pending, (2) associated
6.12.2. SAP Assignment
The SAP Assignment object is modeled by the “SAP Assignment” IC (class id: 17, version: 0).
OBIS code
A B C D E F
SAP Assignment
SAP Assignment 0 0 41 0 0 255
1) Attributes description of the object “SAP Assignment”
SAP Assignment Class_id = 17, version = 0

Access right
- A. 2 A. 3 A. 4
2. SAP_assignment_list asslist_type (see below) - R R R
a) Attribute “SAP_assignment_list”
- Contains the logical device name and its SAP address (server upper HDLC address)
- “SAP”: server logical device address (upper HDLC address) (long-unsigned [18])
Page 128 / 135


- “logical_device_name”: octet-string (size(16 bytes))
6.12.3. COSEM logical device name
The COSEM logical device name object is modeled by the “Data” IC (class id: 1, version: 0). Each
logical device of the meter has one instance of this object. However, since this specification does
not specify the number of additional logical devices to be included in the meter, creating the
“COSEM logical device name” objects are left to manufacturer.
OBIS code
A B C D E F
Data
COSEM logical device name 0 0 42 0 0 255
1) Attributes description of the object “COSEM logical device name”

Access right
- A. 2 A. 3 A. 4
2. value - R R R
The byte configuration is below
a) The byte configuration of the “value” is described below.
byte byte byte byte byte byte byte byte byte byte byte byte byte byte byte byte
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Manufacturer
Year Type
identifier (issued Meter serial number (Octet-string : 8 bytes)
(xx) (xxx)
by DLMS UA)
※ Manufactured Year uses the last two digit of the manufactured year of the meter. If the
meter manufactured year is 2010, then 10 shall be used instead of xx.
※ Meter Type uses the last three (3) digit of SEC Item No. If SEC Item No. is 908402101,
then 101 shall be used instead of x.
e.g.) Meter ID: AEC1410100000001
Page 129 / 135


6.13. Communications
6.13.1. Optical Port Setup
The Optical port setup object is modeled by the “IEC local port setup” IC (class id: 19, version: 1).
OBIS code
A B C D E F
IEC Local Port Setup
Optical port setup 0 0 20 0 0 255
1) Attributes description of the objects “IEC Local Port Setup”
IEC Local Port Setup Class_id = 19, version = 1

Access right
- A. 2 A. 3 A. 4
2. default_mode enum, default: (0) - R R R
3. default_baud enum, default: (0) 300 baud - R R R
4. prop_baud enum, default: (5) 9600 baud - R R/W R/W
5. response_time enum, (0): 20 ms, (1): 200ms - R R/W R/W
6. device_addr octet-string - R R R
7. pass_p1 octet-string - - - -
8. pass_p2 octet-string - - - -
9. pass_w5 octet-string - - - -
6.13.2. HDLC Setup
The Optical/RS485 HDLC Setup objects are modeled by the “IEC HDLC setup” IC (class id: 23,
version: 1).
OBIS code
A B C D E F
Page 130 / 135


IEC HDLC Setup

Optical HDLC setup 0 1 22 0 0 255
IEC HDLC Setup
RS485 HDLC setup 0 2 22 0 0 255
1) Attributes description of the objects “Optical HDLC setup”

Access right
- A. 2 A. 3 A. 4
2. comm._speed enum, default: (5) 9600 baud - R R/W R/W
3. window_size_transmit unsigned (default: 1) - R R/W R/W
4. window_size_receive unsigned (default: 1) - R R/W R/W
5. max_info_field_length
long-unsigned (default: 128) - R R/W R/W
_transmit
_receive
7. inter_octet_time_out long-unsigned (default: 25 ms) - R R/W R/W
8. inactivity_time_out long-unsigned (default: 120 sec) - R R/W R/W
9. device_address long-unsigned (default: 0x0010) - R R/W R/W
2) Attributes description of the objects “RS485 HDLC setup”

Access right
- A. 2 A. 3 A. 4
2. comm._speed enum, default: (5) 9600 baud - R R/W R/W
3. window_size_transmit unsigned (default: 1) - R R/W R/W
4. window_size_receive unsigned (default: 1) - R R/W R/W
_transmit
Page 131 / 135



Access right
- A. 2 A. 3 A. 4
_receive
7. inter_octet_time_out long-unsigned ( default: 25 ms) - R R/W R/W
8. inactivity_time_out long-unsigned (default: 120 sec) - R R/W R/W
long-unsigned (default: Physical
9. device_address address, refer to clause 3.2 for - R R/W R/W
addressing scheme)
6.13.3. Communication Port Log
The communication port log objects are modeled by the “Data” IC (class id: 1, version: 0). These
objects are used to record the number of communication port connection/disconnection and the
time/date of communication port parameters change. And these objects are captured by the event
log objects (profile generic objects).
OBIS code
A B C D E F
Number of optical port Data
0 0 96 12 1 255
connection/disconnection (class id: 1, version: 0)
Communication port Data
0 0 96 12 4 255
status change (class id: 1, version: 0)
1) Attribute description of the objects “Number of optical port connection”

Access right
- A. 2 A. 3 A. 4
1. logical_name octet-string - - R R
2. value long-unsigned - - R R
2) Attribute description of the objects “Communication port status change”
Page 132 / 135



Access right
- A. 2 A. 3 A. 4
2. value octet-string (1 byte) - R R R
* This object is captured into the “Event Log” objects (Interface Class: Profile generic) whenever
their status is changed (set to ‘1’ and return to zero).

Serial port Optical port
- - - - - -
connected/disconnected connected/disconnected
* When the events of serial port and optical port connected, the corresponding bits (bit1, LSB)
will be set to 1 in binary system. Then when the ports are disconnected, the corresponding bits
will be reset to 0.
7. Conformance Test
To comply with the DLMS/COSEM specifications between static electronic meter for low voltage
measurement and communication modem, the certificate of “SEC-DLMS” must be acquired, and
the conformance test shall be substituted by evaluation test record executed by an organization
accredited by COMPANY. (That is to say, the accredited organization carries out the test on behalf
of COMPANY.)
The procedure to get SEC-DLMS certificate and delivery:
1) The CTT certificate including detail adjoining reports.

2) The SEC-DLMS test certificate (or Type Test certificate) and detail adjoining reports.
3) The Vendor has to submit all Type Test Reports including DLMS CTT Certificate and SEC-
DLMS test certificate.
4) The Company's Approval for Mass Production and Release of Shipment Certificate.
5) Then, Routine Test shall be performed for each delivery batch.
8. Tariff (TOU) Programs
The meter manufacturer shall provide the following TOU programs (Default is 8.1). Due to
Page 133 / 135


COMPANY’s TOU policy change, if SEC requests new TOU program, then the manufacturer shall
provide the requested one without additional charge to COMPANY. The followings are current
COMPANY TOU programs:
8.1. Tariff Program ID (14AC0001) 01 as per 40-SDMS-02A Rev.07 (2014)

TOU Start time Start date Remark
T1 12:00 1 Jan. to 31 Dec. Sat to Thursday Peak Hours
8:00 1 Jan. to 31 Dec. Sat to Thursday
T2 17:00 1 Jan. to 31 Dec. Sat to Thursday Other Hours
9:00 1 Jan. to 31 Dec. Friday
0:00 1 Jan. to 31 Dec. All week days
T3 Off-Peak Hours
8.2. Tariff Program ID (13AC0001) as per 40-SDMS-02A Rev.06 (2013)

T1 12:00 1 Jan. to 31 Dec. Sat to Thursday Peak Hours
8:00 1 Jan. to 31 Dec. Sat to Thursday
T2 17:00 1 Jan. to 31 Dec. Sat to Thursday Other Hours
0:00 1 Jan. to 31 Dec. All week days
T3 Off-Peak Hours
8.3. Tariff Program ID (11AC0001) as per 40-SDMS-02A Rev.06 (2011)

0:00 1-January to 30-April, All week days
T1 Outside peak period
0:00 1-October to 31-December, All week days
0:00 1 –May to 30-September. Sat to Thursday
T2 0:00 1 –May to 30-September. Friday Off-Peak Hours
21:00 1 –May to 30-September. Friday
Page 134 / 135


8:00 1 –May to 30-September. Sat to Thursday

T3 17:00 1 –May to 30-September. Sat to Thursday Other Hours
9:00 1 –May to 30-September. Friday
T4 12:00 1 –May to 30-September. Sat to Thursday Peak Hours
❖❖❖ END ❖❖❖
Page 135 / 135

40 SDMS 02B REV.08 WC - OBIS - Code - Specs PDF

Uploaded by

Copyright:

Available Formats

40 SDMS 02B REV.08 WC - OBIS - Code - Specs PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

40 SDMS 02B REV.08 WC - OBIS - Code - Specs PDF

Uploaded by

Copyright:

Available Formats

Saudi Electricity Company ‫الشركة السعودية للكهرباء‬

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

(SEC DLMS/COSEM OBIS CODE SPECIFICATION)

ELECTRONIC REVENUE WC METER

This specification is property of SEC and currently optimized.

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

6.9.13. Average Voltages and Currents Profile Interval ........................................... 108

8. Tariff (TOU) Programs ................................................................................................. 133

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

1.1. Scope of Application

1.2. Communication Specifications

1.2.1. Configuration of communication specifications for meters

These specifications shall be in compliance with IEC regulations known as International

1.2.2. Referenced Documents

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

It indicates a device that initializes and controls data flow.

It indicates a device responds to a request from a master; commonly referring to electricity

1.3.5. OSI 7 Layer

1.4. List of Abbreviation

- ACSE Application Control Service Element

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

- DCE Data Communication Equipment (Communication Interface or Modem)

2.1. Application of IEC 62056-21

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

Figure 1 – Data link connection from IEC 62056-21 mode E

2.2. Application of IEC 62056-42

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

Figure 2 – Typical PSTN Configuration

- The communication is point to point or point to multipoint;

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

Figure 3 – The location of the physical layer

2.3. RS-485 Serial Communication Interface

3. Data Link Layer

3.1. Application of IEC 62056-46

3.2. COSEM Server (Meter) Addressing Scheme

In the 3-layer, connection-oriented, HDLC-based communications profile for Automatic Meter

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

Upper HDLC address (HEX) [2 bytes]

Figure 4 – COSEM Server HDLC addressing method

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

The applied standard for the application layer is IEC 62056-5-3.

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

4.1. Application of IEC 62056-5-3

4.2. The COSEM Server Model

Level 1: Physical device

Level 2: Logical device

Level 3: Accessible COSEM objects

The COSEM Server Model is as below:

1) A meter is regarded as a physical device.

2) Physical device consists of at least one logical device.

Figure 5 – The COSEM server model

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

5.1. Application of IEC 62056-6-1 (Object identification system)

- Logical names of objects defined in IEC 62056-6-2;

5.2. Application of IEC 62056-6-2

SEC DISTRIBUTION MATERIALS SUPP. A. 40-SDMS-02B REV.08

Figure 6 illustrates these terms by means of an example.