Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -

Mumbai(shivangp000@gmail.com) 163.116.213.74.

(Reaffirmed 2016)

(Reaffirmed 2015)

(Reaffirmed 2014)

(Reaffirmed 2013)

(Reaffirmed 2012)

(Reaffirmed 2011)

(Reaffirmed 2010)

(Reaffirmed 2009)

(Reaffirmed 2008)

(Reaffirmed 2007)

(Reaffirmed 2006)

(Reaffirmed 2005)
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.

Equipment for Electrical Energy Measurement, Tariff and Load Control Sectional Committee, ETD 13

FOREWORD
This Indian Standard was adopted by the Bureau of Indian Standards, after the draft finalized by the Equipment
for Electrical Energy Measurement, Tariff and Load Control Sectional Committee had been approved by the
Electrotechnical Division Council.
With development of electronic meters having possibilities of metering data being integrated into business processes
of service providers and in turn with generating agencies, thus opening up multiple opportunities in power system
management at both micro and macro levels and being guided by the National Electricity Policy of the Central
Government after enactment of the Electricity Act, 2003, the Committee initiated the work of formulating standards
on Data Exchange for Electricity Metering Equipment in 2006.
Two options were taken up for interoperable use of meters in a data network. In 2007, the Committee decided to
adopt the International Standard IEC 62056 already available in various parts. However it was felt that only
adoption was not sufficient for proper implementation as the selective features of the standard available at that
time were not adequate for use by different utilities collectively. In view of urgent power reforms programme of
the Central Government and the metering data integration involved, the Electrotechnical Division Council in
April 2008, while appreciating the other option of Common Framework based solution being developed by Indian
Electrical and Electronics Manufacturers Association (IEEMA), advised the committee and divergent stakeholders
for rapid implementation of the IEC Standard available. The Committee inducted experts and held a series of
meetings for evolving this Indian Standard for proper implementation of the IEC Standard based on open protocol
and wide ranging selective features thereof, for application in Indian networks.
The Central Electricity Authority (CEA), a body under the Electricity Act, 2003, to prepare regulations on installation
and operation of meters and to record data regarding electricity from generation to utilization and the Central
Power Research Institute, a Society under the Central Government, with established conformance test facilities
for meters conforming to IEC 62056 at its Bangalore Laboratory, both members of the Committee, were involved
in preparation of category-wise comprehensive list of metering parameters for use in national networks. The
Report titled “Standardization of Metering Parameters” finalized with object identifier codes as requested was
submitted to BIS in April 2009 for facilitating preparation of Indian Standards/Guides on Metering data exchange.
Some assistance has also been derived from CBIP Publication 304 Manual on Standardization of AC Static
Electrical Energy Meters (for electrical energy and tariff related parameter terminologies).
Device Language Message Specification (DLMS) with functionalities of Companion Specification for Energy
Metering (COSEM) based on open protocols and maintained by Device Language Message Specification User
Association, DLMS UA, Geneva, in the form of four technical Reports, namely “Blue”, “Green”, “Yellow” and
“White” Books, have been adopted by IEC on regular basis in the International Standards mentioned above for
interoperable use of electricity meters in a data network. The continuous development of DLMS/COSEM open
communications protocols for data retrieval, updation, and reconfiguration of metering devices, has enabled
diverse operators to access safely and quickly data from metering equipment provided by diverse manufacturers.
This standard, a Companion Specification in the form of a Guide, is intended to provide a field level basis for
efficient and secure transfer of electricity metering data in an open manner with judicious application of features
and protocols of the International Standards.
This specification refers to latest updates of Interface classes and OBIS codes available in 9th edition (2009) of
the Blue Book of DLMS UA. This also refers to updates of procedures and services available in 7th edition
(2009) of the DLMS UA Green Book. These revised Technical Reports of DLMS UA, considered as pre-standards
for several parts of IEC 62056, will be adopted by IEC in due course and subsequently by BIS in adopted Indian
Standards being published. Till such time these books, accessible by members of DLMS User Association in

(Continued on third cover)

 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Indian Standard
DATA EXCHANGE FOR ELECTRICITY METER
READING, TARIFF AND LOAD CONTROL —
COMPANION SPECIFICATION
1 SCOPE c) Values and distribution methods of secret
keys.
1.1 This standard is intended for use as companion to
IS/IEC 62056 (Parts 21, 42, 46, 47, 53, 61 and 62) 1.5 Metering functions are outside the scope of this
series of standards on ‘Electricity metering: Data standard and are covered by prevailing Indian Standards
exchange for meter reading, tariff and load control’ for as applicable.
proper application/implementation of the provisions
thereof. 2 REFERENCES

1.2 These generic metering data exchange standards The standards listed in Annex H contain provisions
based on DLMS/COSEM open protocols and features, which, through reference in this text, constitutes
provide a coverage for structured modelling of metering provisions of this standard. At the time of publication
the editions indicated were valid. All standards are
functionalities as available at communication
subject to revision and parties to agreements based on
interface(s), with procedures for identification of these
this standard are encouraged to investigate the
data objects by mapping into respective codes, and
possibility of applying the most recent edition of the
finally for direct local exchange or remote exchange
standard indicated at Annex H.
of these data messages by transporting over various
layers of communication channels with specified 3 TERMINOLOGY
procedures and services, as applicable.
For the purpose of this standard, the definitions given
1.3 This Companion Specification provides guidelines, in IS/IEC/TR 62051-1 and the following shall apply.
specifies optional DLMS/COSEM elements and
outlines boundary requirements for design of such 3.1 Network — A data communications system that
DLMS/COSEM compliant electricity meters for allows a number of devices to communicate with each
possible applications in Indian electricity networks (see other. It indicates interconnection of these devices in a
also Annex A). Such selections may involve: way concordant with the communications profile
selected. It does not necessarily mean a diverse or wide-
a) COSEM interface classes, their instances, ranging set of connections, nor any routing capability
attributes and methods to be supported, event (see also 13.23 of IEC 62051).
and status tables, identified objects, DLMS
3.2 Architecture — Overall requirement and
services, communication media and protocol
application of the communication network, indicating
stacks.
structure and hierarchy (see also 4.3 of IEC 62051).
b) Requirements for Direct Local Data Exchange
involving HHU (MRI) and Remote Data 3.3 Object — A collection of characteristic attributes
Exchange with HOST Computer. and specified methods (see also DLMS UA, Blue Book).
c) The necessary country/project specific codes, 3.4 Object Modelling — A technology independent
not documented by DLMS UA, are included model of a meter can be represented by a list of objects
in Annex A for specified usage of electricity as seen through an interface and provides controlled
meters. access to their attributes and methods. The data objects
related to metering functionalities and parameters can
1.4 The following are outside the scope of this standard
be mapped into identifier codes forming a message for
and will be decided by user/manufacturer/system
transportation according to an open protocol (see also
integrator:
DLMS UA, Blue Book).
a) HOST computer — Metering equipment
3.5 Access Point — A physical interface point used to
connectivity;
transfer data from/to the meter network. It may be a
b) Compatible modem (Data Communication gateway from a LAN to a higher order network or an
Equipment) and its requirements for chosen interface to temporary reading equipment such as a HHU
communication medium; and (MRI), a portable PC, etc (see also 4.2 of IEC 62051).

1
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

3.6 Held Unit (HHU) — A portable device for reading nauthorized messages may be detected. It ensures data
and programming equipment or meters at the access security (see also 13.29 of IEC 62051).
point (see also 4.19 of IEC 62051 and Annex J).
3.17 Key — Transforms a particular message using an
3.7 Meter Reading Instrument — These are algorithm to make it unreadable to anyone except the
synonymous with HHU (see also G-1.7 and G-1.8 of recipient, to preserve integrity, authenticity and
IS 14697). confidentiality of the message or vice versa, through a
standardized procedure (see also DLMS UA, Green
3.8 Configuration — Setting of measurement and
communication parameters to operate the meter Book).
correctly (see also 4.7 of IEC 62051). 3.18 Confidentiality — Preserving authorized
3.9 Protocol — The rules for communications system restrictions on information access and disclosure,
operation that must be followed if communication is to including means for protecting personal privacy and
be effected (for example for meter reading and proprietary information. A loss of confidentiality is the
programming) ( see also 13.72 of IEC 62051). unauthorized disclosure of information (see also NIST
FIPS PUB 199 : 2004).
3.10 Open Protocol — The rules for communications
system operation suitable for meter reading and limited 3.19 Integrity — Guarding against improper
programming of meters and data collection equipment information modification or destruction, and includes
of different types and from different manufacturers ensuring information non-repudiation and authenticity.
through open standardized documents, for example A loss of integrity is the unauthorized modification or
DLMS/COSEM (see also 3.1.65 of IS/IEC 62051-1). destruction of information (see also NIST FIPS PUB
199 : 2004).
3.11 Interface — A point or means of interaction
between two systems (for example between a meter 3.20 Open Systems Interconnections (OSI) — A
and a data collection equipment) (see also 13.50 of framework for communication processes in which the
IEC 62051). process is divided into seven functional layers, arranged
one above the other with each having a separate
3.12 Parameter — A single identifiable metering or
responsibility. Each layer communicates with the layer
other quantity which may be read or altered within
immediately above and below it (see also 12.1 and 12.4
meter readings, tariffication, or control and may have
of IEC 62051).
multiple aspects such as its value, scaling, timestamp,
etc. 3.21 Collapsed Architecture — A subset of the OSI
3.13 Parameterization — Setting of those parameters reference model which consists of only three layers:
that define the configuration of the metering device, Physical layer, Data link layer and Application layer.
which implies writing values of COSEM object 3.22 Layer — One of seven functional entities within
attributes. The parameterization tool can be seen as a the OSI model (normal and collapsed architecture) as
special client. given in Table 1 (see also 12.2 of IEC 62051).
3.14 Data Concentrator — A device used to hold the
data from a number of meters, in a way that identifies Table 1 OSI Model — Functional Layers
the data from each meter, and allows it to be accessed
Sl No. Layer Normal Collapsed
in real time by a higher-level data collector. Typically (1) (2) (3) (4)
a concentrator is accessed in a manner similar to the
meters, but supports faster or cheaper communication, i) 7 Application Application
ii) 6 Presentation —
and has greater storage capacity than available with
iii) 5 Session —
the meters themselves (An example of use is to iv) 4 Transport —
concentrate data from a number of electrical distribution v) 3 Network —
substations). vi) 2 Data link Data link
vii) 1 Physical Physical
3.15 HOST Computer — A computer system to which
data collected by HHUs is returned for processing, and/
or which can collect data remotely from a meter or data 3.22.1 Physical Layer (OSI Layer 1) — That layer of
concentrator. the OSI reference model which provides bit
transmission between one node and the next, physical
3.16 Data Encryption — The changing of the form of interfacing with media, data signal encoding and defines
a data stream in such a way that only the intended electrical parameters, connector size, shape and
recipient can read or alter the information and pinouts.

2
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

3.22.2 Data Link Layer (OSI Layer 2) — That layer of declared features of this standard and generic standards
the OSI reference model which performs and controls IEC 62056 in that particular type, by a laboratory
specified transmission service functions by means of a authorized for the purpose (see also DLMS UA, Yellow
link protocol. Book and Annex K ).
3.22.3 Network Layer (OSI Layer 3) — That layer of 4 ARCHITECTURE
the OSI reference model which establishes the source
to destination path across the network, switches, routes 4.1 The typical connectivity scheme between a meter
and controls congestion of information packets. (server) and the client, considered for this standard, is
shown in Fig. 1.
3.22.4 Transport Layer (OSI Layer 4) — That layer of
the OSI reference model which provides reliable 4.2 Physical Requirements
transmission of layer 7 messages end-to-end across the
The meter (server) shall support a minimum of two ports
communication network.
for data communication, as given below:
3.22.5 Session Layer (OSI Layer 5) — That layer of
a) P1 — An Electrical port compatible with
the OSI reference model which establishes and
RS 232 or RS 485 specifications. This shall
terminates end-to-end sessions, provides process
be used for remote access from the HOST
synchronization, and determines if half-duplex or full-
(Client) or DC (Client).
duplex is to be used.
b) P2 — An optical port complying with hardware
3.22.6 Presentation Layer (OSI Layer 6) — That layer specifications detailed in IS/IEC-62056-21.
of the OSI reference model which establishes the syntax This shall be used for local access from a HHU
(form) in which data is exchanged. (MRI).
3.22.7 Application Layer (OSI Layer 7) — That layer c) The P1 and P2 both shall support the 3-layer
of the OSI reference model which provides end-user Connection Oriented COSEM/HDLC profile,
services such as file transfers, electronic messages and with a minimum and default baud rate of 9600.
remote data base access. d) Both P1 and P2 shall support 4 byte and one
byte addressing both. HHU can read from
3.23 Conformance Testing — Planned and regulated
either port.
process of evaluation of a type of metering equipment
in order to gain confidence about implementation of The optical port is not required to support any mode of

1-1 HDLC PORT.

DCE

P1
Meter
Category DC
A/B/C HOST
1-1 HDLC PORT. (Client)
(Server)
BCS
P2 1-1, HDLC PORT. HHU

Legend Link to base

DCE — Data communication equipment computer
PSTN Modem, GSM/GPRS Modem
HHU — Hand held unit system
DC — Data concentrator
P1 — RS 232/RS 485 Port — For remote access
P2 — Optical port — For local access

FIG. 1 MESSAGE FLOW CONNECTIVITY S CHEME BETWEEN METER/SERVER AND C LIENT

3
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

IS/IEC-62056-21, that is, mode of usage shall be direct a) Public client association (PC);
HDLC (see also Fig. 1). b) Meter reader association (MR); and
c) Utility settings association (US).
4.3 Requirements for Simultaneous Operation
The meter (server) is not required to allow more than 5.1 Mandatory Objects
one association to be open at any one time. Optical The following objects as given in Table 2 are mandated
port shall have priority when both ports are accessed by IS/IEC 62056-62.
simultaneously. This means that if the electrical port is
connected and being accessed for data, any attempt to 5.2 Association Properties
connect on optical port shall cause the connection on
5.2.1 The PC association shall contain the following in
electrical port to be interrupted and the optical
addition to mandatory objects:
connection processed after sending ‘DM’
(Disconnected Mode) message to HOST. Any further a) Meter’s real-time clock; and
attempts to communicate on electrical port while the b) Meter serial number.
optical port is being used shall be returned with a ‘DM’
code. This is an indication to the HOST that the meter 5.2.2 The MR association shall contain the following
is temporarily busy. in addition to mandatory objects:
a) Profile objects allowing bulk collection of data
5 LOGICAL STRUCTURE OF METERS
defined by the parameter lists in Annex C, D,
The meter represents one physical device as mentioned E, F and G; and
in 4.5 of IS/IEC 62056-62. b) Simple objects allowing ad-hoc access to
The physical device (meter) hosts one logical device items in the instantaneous parameters list. Ad-
as mentioned in 4.5 of IS/IEC 62056-62, which is the hoc access to the profile objects shall also be
management logical device. This has SAP (Service possible.
Access Point) address 1, as mandated in IS/IEC 62056- 5.2.3 The US association shall contain in addition to
53. The physical device address (lower HDLC address) mandatory objects:
shall also be set to a default value of ‘256’ on supply
and the actual communication address shall be a) All the objects accessible via the MR
programmed on installation. association; and
b) Simple and compound objects allowing
The meter shall support the Logical Name (LN) tariffication and configuration of the meter
referencing mechanism as defined in Annex C.1 of (see also 9).
IS/IEC 62056-62. Short name referencing as defined in
Annex C.2 of IS/IEC 62056-62 is not required to be 5.2.4 The object list of each association is detailed in
supported. Annex C, D, E, F and G. Mandatory objects do not
necessarily appear in these tables. Access rights for each
The meter shall support three associations in the data item are also shown in Annex C, D, E, F and G.
management logical device The association properties, object list, and access rights

Table 2 Mandatory Objects

(Clause 5.1)
Sl No. Object OBIS Code Interface Class Requirements
(1) (2) (3) (4) (5)
i) Logical device name 0.0.42.0.0.255 IC = 1 (Data) Value data type will be octet-string with maximum
length 16.
ii) Current association 0.0.40.0.0.255 IC = 15 (Association LN) This object will refer to the currently connected
association object. The meter shall have three
association objects, of which the currently
connected one shall be accessible via the OBIS
0.0.40.0.0.255

NOTES
1 The logical device name shall have a maximum length of 16 characters, and shall have as its first three characters the manufacturer’s
3-letter code as specified in 4.6.2 of IS/IEC-62056-62.
2 The three letters manufacturer ID’s are administered by the FLAG Association, in co-operation with the DLMS UA.

4
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

are identical on ports P1 and P2. 5.4.3 Methods may have the following access rights:
5.2.5 The required associations shall have the properties a) No access; and
as given in Table 3. b) Execute access.
5.3 Descriptive Notes for Logical Structuring 5.4.4 Access rights are specific to each association.
Different associations may have different object lists,
5.3.1 Associations
or award different access rights to the same set of data
Each logical device can organize the data objects into objects. Thus the grouping of data into associations
different associations, each having different access gives different views of the same real data.
rights to the list of objects. Each association defines
the SAP address pair of the client and server logical 6 USAGE OF DLMS/COSEM PROVISIONS
device addresses that participate in the data transaction.
6.1 Usage of Interface Classes
5.3.2 Objects
6.1.1 This standard defines the set of interface classes
All meter data is represented by COSEM interface to be used for various types of data. The interface class
objects. COSEM interface objects are instances of the for the identified parameters is specified in Annex C to
COSEM interface classes. Annex G.
5.3.3 Attributes and Methods
6.1.2 Either requiring support or offering support for a
The actual placeholders of the different data elements class shall not imply support for all its attributes.
of the meter are the attributes of the objects, whereas Required attributes are listed under respective Annex
the methods exposed by the objects allow manipulating as notes. Not supporting an attribute can be
the attributes in defined manners. implemented as given below:

5.4 Referencing Methods a) Attribute does not appear in the object list;
and
5.4.1 DLMS/COSEM provides two referencing
b) Attribute appears in the object list but with
methods to access the meter data, Logical name
no access rights.
referencing and Short name referencing. Under LN
referencing, data is accessed by specifying the Logical 6.1.3 Attribute_0 referencing (indicating access to all
name (OBIS code) of the object, the Class ID and the attributes in one request, as specified by Bit 10 of the
attribute (or method) index. Under SN referencing each conformance block) is not required to be supported in
attribute and method of each object has its own any case.
individual address.
6.1.4 References to classes may be made in the form
5.4.2 Access rights are specified for each attribute and of capture-IDs or register-table entries even if the
each method of every data object in the meter. Attributes corresponding classes are not supported for direct data
may have the following access rights: access.
a) No access; 6.1.5 References to OBIS codes may be made in the form
b) Read access; of capture-IDs, masks, or scripts even if the corresponding
c) Write access; and objects are not individually accessible. In this case those
d) Read-write access. items will not appear in the Association object.

Table 3 Association Properties

(Clause 5.2.5)
Sl No. Feature Public Client Meter Reader Utility Settings
(1) (2) (3) (4) (5)

i) SAP address pair in format (client, server) (16,1) (32,1) (48,1)

ii) Application context — Basic security LN without ciphering LN without ciphering LN without ciphering
iii) Application context — Advanced security Not applicable LN-Ciphered LN-Ciphered
iv) Sign on authentication mechanism (see also 7.3.7.2 Lowest Level Low Level (LLS) High Level (HLS)
of IS/IEC-62056-53)
v) Services required in conformance block Get, Get
with block transfer Get, Get with block transfer,
Selective access Get, Set, Action, Get and set with
block transfer, Selective access
vi) OBIS codes 0.0.40.0.1.255 0.0.40.0.2.255 0.0.40.0.3.255

5
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

6.2 Requirements for Interoperability control mechanisms shall be used in the association
establishment phase and encryption/authentication
6.2.1 A client device supporting the parameters,
mechanism shall be used in the data communication
functions, and classes of the minimum specification,
phase.
along with suitable configuration of system-dependent
features (such as physical addresses, timeout thresholds, 7.1 Security Profiles
and secret keys), shall be able to retrieve all of the
specified data items and perform any of the specified Two security schemes are defined in this standard.
updates without particular knowledge about the server. 7.1.1 Basic Security
6.2.2 Given the knowledge that a certain client or a The basic security profile does not provide for
certain server implements particular additional features encryption or authentication during data
defined as in this standard, a server can be built to return communication stage. The only security provided for
data and receive updates from that client, or a client is the sign-on authentication security provided by low
can be built to retrieve data and perform updates upon level and high level security as applicable for the
that server, respectively, without further special respective associations.
knowledge other than system-dependent features.
7.1.2 Advanced Security
6.2.3 Interpretation of the data shall be possible by any Encryption, authentication, or both can be performed
user with adequate knowledge of electricity metering by the application programme and transferred using
provided that a complete set of data has been retrieved. ciphered PDUs. All systems must implement basic
security. Implementation of advanced security is
6.3 Country-Specific OBIS Codes
discretionary. When implemented it shall be as provided
Within this Companion Specification, country-specific in NIST SP 800-38-D.
variations or additions to quantities such as energy types
are managed by the allocation of new codes in the full 7.2 Security Setup (Class id: 64, Version: 0)
OBIS format. The country-specific OBIS codes The following interface class is defined in addition to
introduced in this document are in the format — those published in the National/International Standard
a.b.94.91.e.f, along with interface class and attributes, (see also IS/IEC 62056-62).
where C = 94 indicates a country-specific code and
Instances of this IC contain the necessary information
D = 91 is allocated for India.
on the security policy applicable and the security suite
7 ASSOCIATION AND DATA SECURITY in use within a particular AA, between two systems
identified by their client system title and server system
As per the provisions of the DLMS/COSEM protocol, title respectively. They also contain methods to increase
data access control mechanism and encryption/ the level of security and to transfer the global keys as
authentication mechanism shall be supported. Access given in Table 4.

Table 4 Security Setup

Sl Security Setup 0….n Class_id = 64, Version = 0
No. Data Type
Min Max Def. Short Name
(1) (2) (3) (4) (5) (6) (7)
i) Attributes:
a) logical_ name (static) octet-string — — — x
b) security-policy (static) enum — — — x + 0×08
c) security-suite (static) enum — — — x + 0×10
d) client-system-title (dynamic) octet-string — — — x + 0×18
e) server-system-title (static) octet-string — — — x + 0×20
ii) Specific methods: m/o
a) security_activate o x + 0×28
b) global_key_transfer o x + 0×30

NOTE — Use of this interface class is only required for Advanced Security profile implementations. Implementations of Basic
Security profiles shall not contain this Class.

6
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

7.3 Security Setup Objects LN Interface Class (IC = 15). The version 1 of IC = 15
adds an extra attribute ‘security_ setup_reference’
7.3.1 The following object identifiers as given in Table 5 (attribute 9) which will be used to contain the reference
are defined in addition to those given in to an instance of a Security Setup class, namely one of
IS/IEC 62056-62. the two instances defined in Table 6.
Table 5 Object for Security Setup 7.4.2 The implementation of version 1 of Association
LN Interface class is not required for Basic Security
Security Setup IC OBIS Code
Objects
profile.
A B C D E F 7.4.3 The following Interface Class definition is defined
(1) (2) (3) (4) (5) (6) (7) (8) in Table 7 in addition to those published in
Security setup 64 — Security setup 0 b 43 0 e 255 IS/IEC 62056-62.
7.4.4 COSEM logical devices able to establish AAs
7.3.2 Instances of the IC Security setup are used to set within a COSEM context using LN referencing model
up the message security features. For each Association the AAs through instances of the ‘Association LN’ IC.
object, there is one Security setup object managing A COSEM logical device has one instance of this IC
security within that AA. Value group E numbers the for each AA the device is able to support.
instances. This specification defines 2 values for E
corresponding to the 2 associations as given in Table 6. 7.5 Descriptive Notes for Data Security
7.5.1 Access Control for Association
Table 6 Security Setup Object OBIS Code for
The DLMS/COSEM standard provides three different
Association Levels
sign-on authentication mechanisms for each
(Clauses 7.3.2 and 7.4.1)
association’s access to meter data applied at the time
Sl Security Setup Object Association Description of performing COSEM OPEN operation.
No. OBIS Code
(1) (2) (3) 7.5.1.1 Lowest level security
i) 0.b.43.0.1.255 Meter Reader Association Open access without any authentication at sign-on. This
ii) 0.b.43.0.2.255 Utility Settings Association
shall be used by the public client.
NOTE — These instances of the Security Setup interface
Class are only required for Advanced Security profile
7.5.1.2 Low level security (LLS)
implementations. Implementations of Basic Security profile Password based sign-on where the client authenticates
shall not contain these instances.
itself to the meter using a password. The Utility Settings
association shall provide access to write the password
7.4 LN Association Interface Class for all associations that utilize this authentication
scheme (Currently only the Meter Reader association
7.4.1 This standard utilizes version 1 of the Association object). This is accomplished by providing write access

Table 7 LN Association Interface Class

(Clause 7.4.3)
Sl Association LN 0 MaxNbofAss. Class_id = 15, Version = 1
No. Data Type
Min Max Def. Short Name
(1) (2) (3) (4) (5) (6) (7)
i) Attributes:
a) logical_name (static) octet-string — — — x
b) object_list (static) object_list_type — — — x + 0×08
c) associated_partners_id associated_partners_type — — — x + 0×10
d) application_context_name application-context-name — — — x + 0×18
e) xDLMS_context_info xDLMS_context_type — — — x + 0×20
f) authentication_mechanism_name mechanism-name — — — x + 0×28
g) LLS_secret octet-string — — — x + 0×30
h) association_status enum — — — x + 0×38
j) security_setup_reference (static) octet-string — — — x + 0×40
ii) Specific Methods: m/o
a) reply_to_HLS_authentication (data) o x + 0×60
b) change_HLS_secret(data) o x + 0×68
c) add_object(data) o x + 0×70
d) remove_object(data) o x + 0×78

7
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

to the ‘LLS_secret’ attribute (attribute number 7) of 10 values (0...9) for value group E, enabling user to
the Meter Reader association LN object. This write define up to 10 event categories.
access is provided only through the Utility Settings
association. Table 8 Event Code
(Clause 8.1.1)
The MR association object has an OBIS code
0.0.40.0.2.255. The LLS_secret of this object shall be Event IC OBIS Code
changed only through US association. Code
A B C D E F
7.5.1.3 High level security (HLS) (1) (2) (3) (4) (5) (6) (7) (8)

Event code 1 — Data 0 b 96 11 e 255

HLS mechanism defines a 4-pass sign-on scheme where
the client and server exchange challenges (a random
number or code) and then reply to the challenges with 8.1.3 This standard defines 7 categories for
a processed response. The processing performed on the classification of events and correspondingly 7 event
challenges is an encryption using a secret ‘key’. The code objects as given in Table 9.
Utility Settings association shall provide write access
to the ‘secret’ attribute of the Utility Settings Table 9 Event Code OBIS Codes
association. The US association object has an OBIS
Sl Event Code Object Event Category Description
code 0.0.40.0.3.255. The HLS secret of this object can
No. OBIS Code
be changed using method 2 of this object. The (1) (2) (3)
encryption mechanism used for processing the
i) 0.b.96.11.0.255 Voltage related events
challenges shall be AES-128 algorithm as provided in ii) 0.b.96.11.1.255 Current related events
NIST FIPS PUB 197 : 2001. iii) 0.b.96.11.2.255 Power failure related events
iv) 0.b.96.11.3.255 Transaction related events
7.5.2 Encryption for Data Communication v) 0.b.96.11.4.255 Other events
vi) 0.b.96.11.5.255 Non-rollover events
The confidentiality of data communicated between the vii) 0.b.96.11.6.255 Control events for connect/
meter and the client is handled by the encryption disconnect
mechanism chosen in the application context.
Associations utilizing the ‘Logical name with ciphering’ NOTES
application context provide encryption/decryption 1 The 7th Event code object is required only where remote
load control by means of connect/disconnect are specified by
services for data messages. Ciphering may be:
agreement between the utility and the manufacturer.
a) Authentication, providing message integrity; 2 Reference to Annex G and the relevant tables may be made
for the valid Event Identifier values defined for the above 7
b) Encryption, providing confidentiality; and categories by this standard.
c) both.

8 EVENT HANDLING 8.2 Event Log

This clause adds the definitions for the event code 8.2.1 An event log is a profile generic object provided
object and event log object. to store historical values of the event code object for a
given category of event as given in Table 10. The capture
8.1 Event Code object includes object attribute definitions of associated
data. Associated data includes event code and other
8.1.1 An event code object is used to hold the identifier relevant information such as timestamp, instantaneous
corresponding to most recent event. Data, register or electricity related information (such as current/voltage/
extended register classes can be used to model this object. energy register, contents etc at the time of the event).
DLMS allows defining country specific reference table
that lists all possible events with corresponding 8.2.2 For the purpose of this standard, the capture
identifiers (see Annex G). For the purposes of this objects will include the entries specified in Annex G.
specification the Interface Class used for this object is
restricted to IC = 1 (Data) as given in Table 8. The value Table 10 Event Log Profile
attribute of the object will have a DLMS data type ‘long (Clause 8.2.1)
unsigned’ (16 bit integer) which will contain the event Event IC OBIS Code
identifier for the last recorded event (identifier taken from Log
the reference tables (see Annex G). A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8)
8.1.2 Value group E allows to classify events into
Event log 7 — Profile Generic 0 b 99 98 e 255
different categories as needed. Currently DLMS allows

8
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

8.2.3 Value of group E allows to classify event logs into to each time-switch in the schedule as given in Table 13.
different categories as needed. Currently DLMS allows
10 values (0...9) for value of group E allowing to define Table 12 Activity Calendar OBIS Code
up to 10 event log categories as given in Table 11. (Clause 9.3)
8.2.4 This standard defines 7 categories for Activity IC OBIS Code
classification of event log objects with a one-to-one Calendar
A B C D E F
correspondence with the 7 event code categories (1) (2) (3) (4) (5) (6) (7) (8)
defined in 8.1.
Activity 20 — Activity 0 b 13 0 0 255
8.2.5 Event Log Storage Recommendations Calendar Calendar

This standard recommends a total storage of 200 events

in the event logs. The division of the specified storage Table 13 Tariff Script Table OBIS Code
space across the 7 compartments specified above shall (Clause 9.4)
be by the agreement between the utility and the Script Table IC OBIS Code
manufacturer.
A B C D E F
The event code and event log parameters are accessible (1) (2) (3) (4) (5) (6) (7) (8)
through the MR and US associations with read-only Tariffication 9 — Script Table 0 b 10 0 100 255
access (see Annex J). Script Table

Table 11 Event Log OBIS Codes 9.5 This standard utilizes a simple mechanism for
(Clause 8.2.3) associating TOU/TOD scripts with tariffs, as described
Sl Event Log Object Event Category Description below. Use of the Register Activation object is not
No. OBIS Code required.
(1) (2) (3)
9.6 Under this mechanism, script identifiers in the
i) 0.b.99.98.0.255 Voltage related events
tariffication script table are inherently associated with
ii) 0.b.99.98.1.255 Current related events
iii) 0.b.99.98.2.255 Power failure related events tariffs, as defined below.
iv) 0.b.99.98.3.255 Transaction related events
v) 0.b.99.98.4.255 Other events
9.7 Script identifiers from 1 to 16 are associated with
vi) 0.b.99.98.5.255 Non-rollover events the Activation of Tariff Rate Registers 1 to 16.
vii) 0.b.99.98.6.255 Control events for connect/ Implementations that do not require 16 different tariff
disconnect rates shall use identifiers from 1 to the required number.
For example if 8 tariffs are defined, script identifiers 1
NOTE — The 7th Event log category is required only where
remote load control by means of connect/disconnect are to 8 shall be used, where scripts 9 to 16 are reserved
specified by agreement between the utility and the manufacturer. for future use. Scripts identifiers 17 to 32 are associated
with Maximum Demand tariffs 1 to 16.
9 TOU METERING Implementations that do not require 16 different tariff
rates shall use identifiers from 1 to the required number.
9.1 DLMS/COSEM provide a number of interface
classes to deal with TOU metering. These include 9.8 The activity calendar shall be used to associate
activity calendars (objects that specify the time- activation times to different Tariff rates simply by using
switches for tariffs based on a season/week/day profile the appropriate script identifiers. All scripts shall point
tree) and schedules (a simple tabular listing of time- to a dummy OBIS code and attribute index which has
switch scripts associated with a date-time). no associated meaning.
9.9 To ensure coordination of the updates to various
9.2 These objects associate a script (stored in a script
attributes, activity calendar shall be updated by writing
table object, IC = 9) with each time-switch. The script
to the passive-calendar attributes. The end of the update
usually defines the list of registers that get enabled for
process is indicated by update of the activation date
that time-switch using a register activation object (IC
attribute with an appropriate value, causing all changes
= 6) that stores masks of registers that can be selectively
to become effective simultaneously.
enabled/disabled.
9.10 Use of the special days table is not considered
9.3 For the purpose of this standard, the activity
presently in this standard.
calendar (IC = 20) shall be used as given in Table 12.
10 BILLING PERIODS
9.4 An instance of a script table class, the tariffication
script table object will be used to store the scripts related 10.1 Billing period resets are driven by an instance of

9
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

the single action schedule class in conjunction with a actions internal to the meter may also be triggered by
script table. The data of the billing period is stored in a the end of each billing period, but are not required to
profile generic object as given in Table 14. Each entry be expressed as scripts here.
in the profile buffer captures the billing period values
for a specific billing period. 11 HISTORIC DATA
11.1 Historic data can be accessed by two mechanisms
Table 14 Billing Period OBIS Code in DLMS-COSEM. One mechanism provides access to
Profile IC OBIS Code past values of specific quantities by using a VZ (billing
Generic period number) related value for F in the OBIS code of
A B C D E F the original quantity. The other mechanism is profile
(1) (2) (3) (4) (5) (6) (7) (8)
generic objects, where individual billing data set is one
Data of 7 — Profile Generic 1 b 98 1 0 255 entry. Profile generic object method is supported in this
Billing specification for accessing historical data.
Period
Profile
11.2 Billing Period Counter

10.2 This standard specifies the single action schedule 11.2.1 The meter will contain an instance of a billing
object to drive the end of billing period resets as given period counter object as given in Table 17.
in Table 15. The object will contain the time-date entries
at which billing period resets are scheduled. Table 17 Billing Period Counter OBIS Code
Billing IC OBIS Code
Table 15 Single Action Schedule OBIS Code Period
Counter
Single IC OBIS Code A B C D E F
Action (1) (2) (3) (4) (5) (6) (7) (8)
Schedule
A B C D E F Billing 1 — Data 0 b 0 1 0 255
(1) (2) (3) (4) (5) (6) (7) (8) Period
Counter
MDI Reset/ 22 — Single Action 0 b 15 0 0 255
End of Schedule
Billing 11.2.2 The value attribute of the object will have a
Period DLMS data type unsigned 32 bit and cumulative value
since installation The meter will contain an instance of
10.3 Each time-date entry in the execution time array a Data object that provides the number of available
will be associated with a link to a single script in the billing periods in the meter as given in Table 18.
MDI reset/end of billing period script table. The script
table object as given in Table 16 will be programmed Table 18 Available Billing Periods OBIS Code
with scripts to handle the billing period resets. Number of IC OBIS Code
Billing Periods
Table 16 Billing Script Table OBIS Code A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8)
Script Table IC OBIS Code
Available Billing 1 — Data 0 b 0 1 1 255
A B C D E F Period
(1) (2) (3) (4) (5) (6) (7) (8)
MDI Reset/End 9 — Script Table 0 b 10 0 1 255 11.2.3 The above can be read by the client to identify
of Billing how many previous billing period’s data is available in
Period Script
Table the meter. The value attribute of the above object will
have a DLMS data type unsigned (8-bit character).
10.4 The script table will contain a single script that 11.3 Profiles
specifies the capture method invocation for the
corresponding data of billing period profile 11.3.1 Historic data like load profiles etc are supported
(1.0.98.1.0.255). Therefore a single action schedule in IEC 62056 by the Profile Generic Interface Class
entry will trigger a call to the script table to execute the (IC = 7). This object supports capture of other meter
capture method at a specific time (namely the end of object attributes at specific intervals or on demand. The
the billing period) which will cause a billing period captured data is stored in the buffer attribute
entry to be made in the profile for the current period (Attribute 2) of the Profile generic class. This class also
and trigger the start of a new billing period. Other supports selective access to filter the buffer data in

10
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

response to GET requests. There are two mechanisms described in IS/IEC 62056-42 is required only where
for selective access viz. selective access by entry and modem is fitted internal to the meter.
selective access by range.
13 COMMUNICATION SETUP OBJECTS
11.3.2 This standard requires that the selective access
by range shall be supported for block load profile and This stantard requires the communication setup objects
daily load profile. This standard requires support for as given in Table 19 to be supported in the meter
selective access by entry for billing data profile and implementation. This document also recommends that
event log profiles. a specific baud rate may be fixed between the utility
and the manufacturer for each project. The suggested
11.3.3 In case of selective access by range, this standard default baud rate is given in 4.2.
imposes that the restricting object is to be an instance
of the clock interface class (IC = 8) and the date-time Table 19 Communication Setup Object
attribute of the object is captured in the buffer.
Communication IC OBIS Code
11.3.4 Selective access by entry and range supports Setup and
filtering the profile buffer by rows as well as by Related Objects
for Serial
columns. However this standard doesn’t require support Communication
for filtering by columns ( see also Annex L). A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8)
11.3.5 Any configuration change in profile capture object
will be treated as given in 5.6 of IS/IEC 62056-62. IEC HDLC Setup 23 — IEC HDLC 0 b 22 0 0 255
Setup
12 COMMUNICATION PROFILES
IEC 62056 adopts the collapsed architecture subset of 14 CONNECT/DISCONNECT CONTROL
the open systems interconnect reference model. In implementations that require remote Connect/
Figure 2 illustrates the system used. This standard Disconnect control, effected by operation of an output
requires that the three-layer serial Connection- pulse from the meter, this specification requires support
Orientated (CO) profile shall at least be supported. for the disconnect control object as given in Table 20.
The 3-layer serial CO profile consists of COSEM,
logical link control (LLC), and high-level distribution Table 20 Disconnect Control Object
line control (HDLC) on a serial physical channel. This Disconnector IC OBIS Code
profile may be extended by using modems to handle
different carriers such as PSTN, GSM, or GPRS, A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8)
Radio, Zigbee, etc, by tunneling HDLC frames over
these media. Disconnect 70 — Disconnect 0 b 96 3 10 255
Control Control
The addition of dial-up modem connections as

11
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

FIG. 2 COMMUNICATION PROFILE OPTIONS

12
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

ANNEX A
(Clause 1.3)
INTRODUCTION TO METERING PARAMETERS WITH DATA IDENTIFIERS

A-1 Three categories of electricity meters have been parameters listed for this category is for consumers who
selected for compiling comprehensive lists of metering draw energy from the grid. For consumers who also
parameters with their data identifiers as required for data supply energy to grid, the category B Meter is
networks in India for COSEM procedures and services. recommended (see also Annex E).
The relevant reference documents are listed in Annex H.
A-2 The meters complying with this standard shall be
A-1.1 Category A Meter considered as servers in a data network. The data
collecting devices at the head end or HHU shall function
This meter is identified for use at sub-station feeders as client and seek required services from these servers.
and Distribution Transformer Centers. The parameters Table 21 lists the server categories with metering
listed for this category is for ‘Energy Accounting and nomenclatures and annex references.
Audit’ purposes (see also Annex C).
Table 21 Categories of Meters
A-1.2 Category B Meter
Sl Server Metering Nomenclature/Purpose Ref to
This meter is identified for use at meter banks and No. Category Annex
network boundaries. The parameters listed for this (1) (2) (3) (4)
category is for import/export of energy. This meter is i) A Energy accounting and audit B, C, F, G
also suitable for availability based tariff (ABT) regime metering
(see also Annex D). ii) B Boundary/Bank/Ring/ABT metering B, D, F, G
iii) C HV (VT/CT) and LV (CT) consumer B, E, F, G
A-1.3 Category C Meter metering
NOTE — The Annex B to Annex G are in continuation to this
This meter is identified for use at HV (PT and CT Annex.
operated) and LV (CT operated) consumers. The

ANNEX B
( Table 21)
INTRODUCTION TO STANDARDIZED METER PARAMETERS LIST

B-1 CLASSIFICATION OF PARAMETERS For each of the identified parameter, the OBIS code,
The metering parameters have been identified and interface class and the attributes are given in the various
classified as follows: tables in Annexures. The OBIS codes listed are
applicable for LN referencing and is mandatory to
a) Instantaneous parameters; adhere to by the servers and clients.
b) Block profile/load survey parameters;
c) Daily profile parameters; B-2 INSTANTANEOUS PARAMETERS
d) Parameters for accounting/billing; The instantaneous parameters shall be continuously
e) General purpose quantities; updated by the meter hardware/software as per internal
1) Name plate details; sampling and computation time. The energy values in
2) Programmable parameters; and the table shall be cumulative readings from the date of
manufacturing or installation of meter as the case may
f) Event conditions.
be. These shall be continuously updated and last
The measurement and computation of each of these updated value shall be available for downloading as
parameters and events shall be based on standard and when required. Each of the parameters shall be
methods or based on utilities prudent practices or as readable at any instant by the HOST from remote or by
directed by respective regulatory commission. HHU at site. The snap shot of all the instantaneous

13
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

values of all parameters shall be readable by the HOST quantities and are static in nature, grouped as ‘Name
computer. Plate Details’, containing pertinent information about
the supplied meter. The parameters identified and
B-3 PROFILE GENERIC OR LOAD SURVEY grouped as ‘Name Plate Details’ under this
PARAMETERS (CAPTURE TIME BLOCK 15 OR classification are applicable for all categories of meters
30 MIN) ( see Annex F).
This is an array of parameters identified for capturing
and storing at specified time intervals or capture times. B-5.2 Programmable Parameters
The capture times shall be either 15 or 30 min. The These parameters are non electrical quantities. The
capture times shall be programmable by the utilities. parameters identified and grouped as ‘Programmable
The tables lists the parameters whose profile (survey) Parameters’ shall be programmable by the utility
is to be captured and stored in the meter as per set engineers. For the purpose of setting/altering the values
capture time period. The profiles shall be readable at of these parameters, the security and access rights in
any time by the HOST from remote or by HHU (MRI) line with the methodology described in protocol, shall
at site for any specified range and time. be mutually agreed between utility and manufacturer.
In the case of Category B meters the capture time shall The parameters shall be programmable by HOST from
be of 15 min duration. remote and HHU at site. These are applicable for all
categories of meters ( see Annex F).
The data stored in the array shall be the average value
for the captured time block and stored at the end of B-6 EVENT CONDITIONS
that block, except for energy values. The energy entries
are the consumption during respective capture time B-6.1 Any abnormal or a tamper condition is defined
block and posted at the end of that block. The array of as an event. The meters shall identify and log both
data shall be retained inside the meter memory for the occurrence and restoration of such events. The meters
last 22 days for a capture period of 15 min or for the shall also capture some of the parameters at the instance
last 45 days for a capture period of 30 min. It is assumed of above said log. This standard has identified the
that the number of load survey parameters is 5 which events to be logged and the parameters to be captured
can be selected from the respective tables by the for each of those events (see Annex G).
utilities. The storage days can be expanded by choosing B-6.2 This standard has further classified those events
less number of parameters. in sub groups for easy handling. The sub groups are:
The block load profiles shall not store or return values a) Voltage related events;
(typically zero values) for conditions where the meter
b) Current related events;
is powered down for a full day, where a full day is
defined as the 24 h period from midnight 00 h to the c) Power failure related events;
next midnight 00 h. Under such conditions the block d) Transactional events;
load profile for the entire 24 h period shall not be stored e) Other events;
nor padded with zero entries. However if the meter is f) Non-rollover events; and
powered up even for a small amount of time (sufficient
for it to boot up and record the power up event) during g) Control events.
the 24 h period, it shall store and return the block load B-6.3 The number of events stored in each compartment
profile for the entire 24 h duration. shall be decided by agreement between the utility and
manufacturers. However the total number of events
B-4 PARAMETERS FOR ACCOUNTING/ shall be 200.
BILLING PURPOSE
B-6.4 The event conditions identified are listed in
These are parameters identified for accounting/billing Table 32 to Table 38 covering all the sub groups. For
purposes. These shall be generated by the meter for each each type of event condition the parameters to be
billing cycle and stored in the memory. The set of data captured are listed in Table 39. The required capture
for last 6 (six) cycles shall be stored in the memory. At parameters for selected event condition shall be chosen
the end of each cycle corresponding set of data shall be by the utility as per its practices and directives.
readable by the HOST from remote or by HHU at site.
B-6.5 The types of events to be recorded may be
B-5 GENERAL PURPOSE QUANTITIES selected by the utility out of the list provided in tables.
Table 32 to Table 38 as per utility need and practice.
B-5.1 Name Plate Details The parameters for which snapshot is to be recorded at
These parameters are electrical and non-electrical time of tamper/event can also be selected out of list of

14
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

parameters provided in ‘Capture Parameters’ in and directives may choose required parameters from
Table 39. the full list. Sequence of parameters in buffer shall
B-6.6 The servers shall be capable of providing the be derived from capture object. The OBIS code for
entire list of parameters listed in the respective such selected parameters however shall remain as
Annexure. However the utility as per its practices assigned.

ANNEX C
(Clauses 6.1.1 and A-1.1; and Table 21)
PARAMETER LIST FOR CATEGORY A METERS
C-1 The parameters listed here are for energy unit attributes of the Instantaneous parameters listed
accounting and audit purposes. These meters are in Table 22. Instantaneous parameters that do not have
identified for feeder metering and DTC metering where a scaler-unit (like IC = 1) shall not be included in the
the power flow is unidirectional. In circumstances capture objects list. The profile buffer shall have only
where bidirectional power flow is to be measured then one entry. This profile is not required to be updated
Category B meters shall be deployed. periodically.
C-2 The parameters identified are grouped under C-5 BLOCK LOAD PROFILE PARAMETERS
instantaneous (see Table 22) and block load profile (see
Table 23). The tables include the name of the parameter, C-5.1 This is an array of load survey data captured as a
the OBIS code and interface class. profile generic. The OBIS code is 1.0.99.1.0.255, with
Interface class as 7. The capture objects of this block
C-3 Association access rights are as follows: load profile are as per Table 23 and the captured attribute
a) Public client — Read only for clock and no shall be attribute 2 of each interface class. The capture
access for other objects. object values will be copied into buffer of this array
automatically as per capture period which shall be set
b) Meter reader — Read only for all objects.
through OBIS code 1.0.0.8.4.255 of recording interval 1.
c) Utility setting — Read and write for clock and
read only for others. C-5.2 Association access rights are as follows:

C-4 INSTANTANEOUS PARAMETERS a) Public client — No access for all objects.

b) Meter reader — Read only for all objects.
Each of the parameters is a separate entity. The OBIS
c) Utility setting — Read only for all objects.
code for each parameter is identified as per DLMS/
COSEM protocol. C-5.3 Scaler Profile

C-4.1 Snapshot of Instantaneous Parameters This profile is meant for capturing the scaler-unit of
each of the parameter listed in Table 23. This is
The parameters of Table 22 shall be captured as a profile modelled as profile generic (IC = 7) and is assigned
generic using the country specific OBIS code the country specific OBIS code 1.0.94.91.4.255. The
1.0.94.91.0.255; the attribute 2 of each of the capture capture objects for this profile shall include the scaler-
objects shall be copied into the profile at the instant of unit attributes of the parameters listed in Table 23. The
a request from the HOST. profile buffer shall have only one entry. This profile is
not required to be updated periodically.
C-4.2 Scaler Profile
This profile is meant for capturing the scaler-unit of C-6 PARAMETERS FOR ACCOUNTING/
each of the parameter listed in Table 22. This is BILLING
modelled as profile generic (IC = 7) and is assigned The list of parameters in Table 22 and Table 23 shall
the country specific OBIS code 1.0.94.91.3.255. The be used for computing the daily accounting data at the
capture objects for this profile shall include the scaler- HOST.

15
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 22 Instantaneous Parameters for Class A Meters

(Clauses C-2, C-4.1, C-4.2 and C-6)
Sl Parameter OBIS Code Interface
No. Class No.
A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Real time clock, date and time 0 0 1 0 0 255 8
ii) Current, IR 1 0 31 7 0 255 3
iii) Current, IY 1 0 51 7 0 255 3
iv) Current, IB 1 0 71 7 0 255 3
v) Voltage, VRN 1 0 32 7 0 255 3
vi) Voltage, VYN 1 0 52 7 0 255 3
vii) Voltage, VBN 1 0 72 7 0 255 3
viii) Voltage, VRY 1 0 32 7 0 255 3
ix) Voltage, VBY 1 0 52 7 0 255 3
x) Signed power factor, R-phase 1 0 33 7 0 255 3
xi) Signed power factor, Y-phase 1 0 53 7 0 255 3
xii) Signed power factor, B-phase 1 0 73 7 0 255 3
xiii) Three phase power factor, PF 1 0 13 7 0 255 3
xiv) Frequency 1 0 14 7 0 255 3
xv) Apparent power, kVA 1 0 9 7 0 255 3
xvi) Signed active power, kW
(+ Forward; – Reverse) 1 0 1 7 0 255 3
xvii) Signed reactive power, kvar
(+ Lag; – Lead) 1 0 3 7 0 255 3
xviii) Cumulative energy, kWh 1 0 1 8 0 255 3
xix) Cumulative energy, kvarh (Lag) 1 0 5 8 0 255 3
xx) Cumulative energy, kvarh (Lead) 1 0 8 8 0 255 3
xxi) Cumulative energy, kVAh 1 0 9 8 0 255 3
xxii) Number of power-failures. 0 0 96 7 0 255 1
xxiii) Cumulative power-failure duration 0 0 94 91 8 255 3
xxiv) Cumulative tamper count 0 0 94 91 0 255 1
xxv) Cumulative billing count 0 0 0 1 0 255 1
xxvi) Cumulative programming count 0 0 96 2 0 255 1
xxvii) Billing date 0 0 0 1 2 255 3
xxviii) Maximum demand, kW 1 0 1 6 0 255 4
xxix) Maximum demand, kVA 1 0 9 6 0 255 4

NOTES
1 The items at Sl No. (v), (vi), and (vii) are for 3Φ/4W system of measurement with neutral as reference point.
2 The items at Sl No. (viii) and (ix) are for 3 Φ/3W system of measurement with Y-phase as reference point.
3 Signed power factor: (+) indicates lag and (–) indicates lead.
4 The parameters at Sl No. (xviii) to (xxvi) hold cumulative values at that instant from the date of manufacturing or installation of
meter as the case may be.
5 The above list is identified for the purpose of communication to HOST or HHU.
6 The utilities may choose, based on needs, additional parameters for display purpose only.
7 Item number at Sl No. (xxv) refers to the billing period counter.

16
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 23 Block Load Survey Parameters for Category A Meters

(Clauses C-2, C-5.1, C-5.3 and C-6)
Sl Parameter OBIS Code Interface
No. Class No./
A B C D E F Attribute
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Real time clock — date and time 0 0 1 0 0 255 8/2
ii) Current, IR 1 0 31 87 0 255 3/2
iii) Current, IY 1 0 51 27 0 255 3/2
iv) Current, IB 1 0 71 27 0 255 3/2
v) Voltage, VRN 1 0 32 27 0 255 3/2
vi) Voltage, VYN 1 0 52 27 0 255 3/2
vii) Voltage, VBN 1 0 72 27 0 255 3/2
viii) Voltage, VRY 1 0 32 27 0 255 3/2
ix) Voltage, VBY 1 0 52 27 0 255 3/2
x) Block energy, in kWh 1 0 1 29 0 255 3/2
xi) Block energy, kvarh (lag) 1 0 5 29 0 255 3/2
xii) Block energy, in kvarh (lead) 1 0 8 29 0 255 3/2
xiii) Block energy, in kVAh 1 0 9 29 0 255 3/2

NOTES
1 The items at Sl No. (v), (vi), and (vii) are for 3Φ/4W system of measurement with neutral as reference point.
2 The items at Sl No. (viii) and (ix) are for 3 Φ/3W system of measurement with Y-phase as reference point.
3 The parameters at Sl No. (ii) to (ix) are the average values during the block period time and stored at the end of that time block.
4 The parameters at Sl No. (x) to (xiii) are the actual energy consumption during that time block.
5 Capture objects for 3 Φ/4W are items Sl No. (i) to (vii) and (x) to (xiii).
6 Capture objects for 3 Φ/3W are items Sl No. (i) to (iv) and (viii) to (xiii).
7 Support for selective access shall be as defined in 11.3.

ANNEX D
(Clauses 6.1.1 and A-1.2; and Table 21)
PARAMETER LIST FOR CATEGORY B METERS

D-1 The parameters listed here are for Boundary/Bank/ generic using the country specific OBIS code
Ring Fencing/ABT Metering. The meter records 1.0.94.91.0.255. The attribute 2 of each of the capture
parameters under import and or export conditions. objects shall be copied into the profile at the instant of
D-2 The parameters identified for this are grouped a request from the HOST.
under instantaneous (see Table 24), block load profile D-3.4 Scaler Profile
(see Table 25) and daily load profile (see Table 26).
The tables include the name of the parameter, the OBIS This profile is meant for capturing the scaler-unit of each
code and interface class. of the parameter listed in Table 24. This is modeled as
profile generic (IC = 7) and is assigned the country
D-3 INSTANTANEOUS PARAMETERS specific OBIS code 1.0.94.91.3.255. The capture objects
D-3.1 Each of the parameters is a separate entity. The for this profile shall include the scaler-unit attributes of
OBIS code for each parameter is identified as per DLMS/ the Instantaneous parameters listed in Table 24.
COSEM protocol. Instantaneous parameters that do not have a scaler-unit
(like IC = 1) shall not be included in the capture objects
D-3.2 Association access rights are as follows: list. The profile buffer shall have only one entry. This
a) Public client — Read only for clock and no profile is not required to be updated periodically.
access for other objects.
D-4 BLOCK LOAD PROFILE PARAMETERS
b) Meter reader — Read only for all objects.
c) Utility setting — Read and write for clock and D-4.1 This is an array of load survey data captured as
read only for others. a profile generic. The OBIS code is 1.0.99.1.0.255,
with interface class as 7. The capture objects of this
D-3.3 Snapshot of Instantaneous Parameters
block load profile are as per Table 25 and the captured
The parameters of Table 24 shall be captured as a profile object shall be attribute 2 of each interface class. The

17
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 24 Instantaneous Parameters for Category B Meters

(Clauses D-2, D-3.3 and D-3.4 )
Sl Parameter OBIS Code Interface
No. Class No.
A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i)Real time clock, date and time 0 0 1 0 0 255 8
ii)Current, IR 1 0 31 7 0 255 3
iii) Current, IY 1 0 51 7 0 255 3
iv) Current, IB 1 0 71 7 0 255 3
v) Voltage, VRN 1 0 32 7 0 255 3
vi) Voltage, VYN 1 0 52 7 0 255 3
vii) Voltage, VBN 1 0 72 7 0 255 3
viii) Voltage, VRY 1 0 32 7 0 255 3
ix) Voltage, VBY 1 0 52 7 0 255 3
x) Signed power factor, R-phase 1 0 33 7 0 255 3
xi) Signed power factor, Y-phase 1 0 53 7 0 255 3
xii) Signed power factor, B-phase 1 0 73 7 0 255 3
xiii) Three phase power factor, PF 1 0 13 7 0 255 3
xiv) Frequency 1 0 14 7 0 255 3
xv) Apparent power, kVA 1 0 9 7 0 255 3
xvi) Signed active power, kW
(+ import: – export) 1 0 1 7 0 255 3
xvii) Signed reactive power, kvar
(+ Lag; – Lead) 1 0 3 7 0 255 3
xviii) Cumulative energy, kWh (Import) 1 0 1 8 0 255 3
xix) Cumulative energy, kWh (Export) 1 0 2 8 0 255 3
xx) Cumulative energy, kVAh (Import) 1 0 9 8 0 255 3
xxi) Cumulative energy, kVAh (Export) 1 0 10 8 0 255 3
xxii) Number of power, failures. 0 0 96 7 0 255 1
xxiii) Cumulative power, failure duration 0 0 94 91 8 255 3
xxiv) Cumulative tamper count 0 0 94 91 0 255 1
xxv) Cumulative billing count 0 0 0 1 0 255 1
xxvi) Cumulative programming count 0 0 96 2 0 255 1
xxvii) Billing date 0 0 0 1 2 255 3

NOTES
1 The items at Sl No. (v), (vi) and (vii) are for 3Φ/4W system of measurement with neutral as reference point.
2 The items at Sl No. (viii), (ix) are for 3 Φ/3W system of measurement with Y-phase as reference point.
3 Signed Power factor: (+) indicates lag and (–) indicates lead.
4 The parameters at Sl No. (xviii) to (xxvi) hold cumulative values at that instant from the date of manufacturing or installation of
meter as the case may be.
5 The above list is identified for the purpose of communication to HOST or HHU.
6 The utilities may choose, based on needs, additional parameters for display purpose only.
7 Item number at Sl No. (xxv) refers to the billing period counter.

capture object values will be copied into a buffer of unit attributes of the parameters listed in Table 25. The
this array automatically as per capture period which profile buffer shall have only one entry. This profile is
shall be set through OBIS code 1.0.0.8.4.255 of not required to be updated periodically.
recording interval 1. D-5 DAILY LOAD PROFILE PARAMETERS
D-4.2 Association access rights are as follows: D-5.1 This is an array of load survey data captured as
a) Public client — No access for all objects. a profile generic at the end of 24 h. The OBIS code is
b) Meter reader — Read only for all objects. 1.0.99.2.0.255, with Interface class as 7. The capture
objects of this daily load profile are as per Table 26
c) Utility setting — Read only for all objects.
and the captured attribute shall be attributing 2 of each
D-4.3 Scaler Profile interface class. The capture object values will be copied
into a buffer of this array automatically as per capture
This profile is meant for capturing the scaler-unit of
period which shall be set through OBIS code
each of the parameter listed in Table 25. This is
1.0.0.8.5.255 of recording interval 2. The capture
modelled as profile generic (IC = 7) and is assigned
period attribute shall be statically fixed as 24 h.
the country specific OBIS code 1.0.94.91.4.255. The
capture objects for this profile shall include the scaler- D-5.2 Association access rights are as follows:
18
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

a) Public client — No access for all objects. each of the parameter listed in Table 26. This is
b) Meter reader — Read only for all objects. modelled as profile generic (IC=7) and is assigned the
country specific OBIS code 1.0.94.91.5.255. The
c) Utility setting — Read only for all objects.
capture objects for this profile shall include the scaler-
unit attributes of the parameters listed in Table 26. The
D-5.3 Scaler Profile
profile buffer shall have only one entry. This profile is
This profile is meant for capturing the scaler-unit of not required to be updated periodically.

Table 25 Block Load Survey Parameters for Category B Meters

(Clauses D-2 and D-4.3)
Sl Parameter OBIS Code Interface
No. Class No./
A B C D E F Attribute
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Real time clock, date and time 0 0 1 0 0 255 8/2
ii) Frequency 1 0 14 27 0 255 3/2
iii) Voltage, VRN 1 0 32 27 0 255 3/2
iv) Voltage, VYN 1 0 52 27 0 255 3/2
v) Voltage, VBN 1 0 72 27 0 255 3/2
vi) Energy — active import 1 0 1 29 0 255 3/2
vii) Energy — net active energy 1 0 16 29 0 255 3/2
viii) Energy — active export 1 0 2 29 0 255 3/2
ix) Energy, kvarh, Quadrant I 1 0 5 29 0 255 3/2
x) Energy, kvarh, Quadrant II 1 0 6 29 0 255 3/2
xi) Energy, kvarh, Quadrant III 1 0 7 29 0 255 3/2
xii) Energy, kvarh, Quadrant IV 1 0 8 29 0 255 3/2

NOTES
1 The parameters listed in this table are for load survey purpose and are logged as per the block period time.
2 The block period time for interface meters is fixed at 15 min for which the data storage will be for 22 days.
3 The parameters at Sl No. (iii) to (vi) are the average values of 15 min block and stored at the end of that time block.
4 The parameters at Sl No. (vii) to (xii) are the actual energy consumption during the 15 min time block.
5 Item at Sl No. (ii) is an ABT parameter for absolute average value.
6 Item at Sl No. (vii) is an ABT parameter for net energy in the current 15 min block.
7 Support for selective access shall be as defined in 11.3.

Table 26 Daily Load Profile Parameters for Category B Meters

(Clauses D-2 and D-5.1)
Sl Parameter OBIS Code Interface
No. Class No./
A B C D E F Attribute
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Real time clock, date and time 0 0 1 0 0 255 8/2
ii) Cumulative energy, kWh (Import) 1 0 1 8 0 255 3/2
iii) Cumulative energy, kWh (Export) 1 0 2 8 0 255 3/2
iv) Cumulative energy, kVAh while kW Import 1 0 9 8 0 255 3/2
v) Cumulative energy, kVAh while kW Export 1 0 10 8 0 255 3/2
vi) Reactive energy high (V > 103 per cent) 1 0 94 91 1 255 3/2
vii) Reactive energy low (V < 97 per cent) 1 0 94 91 2 255 3/2
viii) Cumulative energy, kvarh, Quadrant I 1 0 5 8 0 255 3/2
ix) Cumulative energy, kvarh, Quadrant II 1 0 6 8 0 255 3/2
x) Cumulative energy, kvarh, Quadrant III 1 0 7 8 0 255 3/2
xi) Cumulative energy, kvarh, Quadrant IV 1 0 8 8 0 255 3/2

NOTES
1 The parameters listed in this table are meant for billing purpose and shall be logged at midnight (00 h).
2 The storage time for these parameters is 22 days.
3 The parameters at Sl No. (ii) to (xi) are cumulative values at that instant from the date of manufacturing or installation of meter as the
case may be.
4 Item at Sl No. (vi) is an ABT parameter.
5 Item at Sl No. (vii) is an ABT parameter.
6 Support for selective access shall be as defined in 11.3.

19
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

ANNEX E
(Clauses 6.11 and A-1.3; and Table 21)
PARAMETER LIST FOR CATEGORY C METERS

E-1 The parameters listed here are for HV (VT/CT) E-4 BLOCK LOAD PROFILE PARAMETERS
and LV (CT) consumer metering. This meter records
E-4.1 This is an array of load survey data captured as a
energy in import mode. These meters shall be capable
profile generic. The OBIS code is 1.0.99.1.0.255, with
of recording import of energy. For customers who
Interface class as 7. The capture objects of this block
import energy and also export energy, use of category
load profile are as per Table 28 and the captured
B meters is recommended.
attribute shall be 2 of each interface class. The capture
E-2 The parameters identified for this are grouped object values will be copied into a buffer of this array
under instantaneous (see Table 27), block load profile automatically as per capture period which shall be set
(see Table 28), and billing (see Table 29). The tables through OBIS code 1.0.0.8.4.255 of recording
include the name of the parameter, the OBIS code and interval 1.
interface class.
E-4.2 Association access rights are as follows:
E-3 INSTANTANEOUS PARAMETERS a) Public client — No access for all objects.
E-3.1 Each of the parameters is a separate entity. The b) Public client — Read only for all objects.
OBIS code for each parameter is identified as per c) Public client — Read only for all objects.
DLMS/COSEM protocol.
E-4.3 Scaler Profile
Association access rights are as follows:
This profile is meant for capturing the scaler-unit of
a) Public client — Read only for clock and no each of the parameter listed in Table 28. This is
access for other objects. modelled as profile generic (IC = 7) and is assigned
b) Meter reader — Read only for all objects. the country specific OBIS code 1.0.94.91.4.255. The
c) Utility setting — Read and write for clock and capture objects for this profile shall include the scaler-
read only for others. unit attributes of the parameters listed in Table 28. The
profile buffer shall have only one entry. This profile is
E-3.2 Snapshot of Instantaneous Parameters not required to be updated periodically.
The parameters of Table 27 shall be captured as a profile E-5 BILLING PROFILE PARAMETERS
generic using the country specific OBIS code
1.0.94.91.0.255. The attribute 2 of each of the capture E-5.1 The contents of Table 29 are for billing purpose.
objects shall be copied into the profile at the instant of E-5.2 Association access rights are as follows:
a request from the HOST.
a) Public client — No access for all objects.
E-3.3 Scaler Profile b) Meter reader — Read only for all objects.
This profile is meant for capturing the scaler-unit of c) Utility setting — Read only for all objects.
each of the parameter listed in Table 27. This is
E-5.3 Scaler Profile
modelled as profile generic (IC = 7) and is assigned
the country specific OBIS code 1.0.94.91.3.255. The This profile is meant for capturing the scaler-unit of
capture objects for this profile shall include the scaler- each of the parameter listed in Table 29. This is
unit attributes of the instantaneous parameters listed in modelled as profile generic (IC = 7) and is assigned
Table 27 instantaneous parameters that do not have a the country specific OBIS code 1.0.94.91.6.255. The
scaler-unit (like IC = 1) shall not be included in the capture objects for this profile shall include the scaler-
capture objects list. The profile buffer shall have only unit attributes of the parameters listed in Table 29
one entry. This profile is not required to be updated above. The profile buffer shall have only one entry.
periodically. This profile is not required to be updated periodically.

20
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 27 Instantaneous Parameters for Category C Meters

(Clauses E-2, E-3.2 and E-3.3)
Sl Parameter OBIS Code Interface
No. Class No.
A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Real time clock, date and time 0 0 1 0 0 255 8
ii) Current, IR 1 0 31 7 0 255 3
iii) Current, IY 1 0 51 7 0 255 3
iv) Current, IB 1 0 71 7 0 255 3
v) Voltage, VRN 1 0 32 7 0 255 3
vi) Voltage, VYN 1 0 52 7 0 255 3
vii) Voltage, VBN 1 0 72 7 0 255 3
viii) Voltage, VRY 1 0 32 7 0 255 3
ix) Voltage, VBY 1 0 52 7 0 255 3
x) Signed power factor, R-phase 1 0 33 7 0 255 3
xi) Signed power factor, Y-phase 1 0 53 7 0 255 3
xii) Signed power factor, B-phase 1 0 73 7 0 255 3
xiii) Three phase power facto, PF 1 0 13 7 0 255 3
xiv) Frequency 1 0 14 7 0 255 3
xv) Apparent power, kVA 1 0 9 7 0 255 3
xvi) Signed active power, kW (+ Forward; – Reverse) 1 0 1 7 0 255 3
xvii) Signed reactive power, kvar (+ Lag; – Lead) 1 0 37 7 0 255 3
xviii) Number of power — failures 0 0 96 7 0 255 1
xix) Cumulative power — failure duration 0 0 94 91 8 255 3
xx) Cumulative tamper count 0 0 94 91 0 255 1
xxi) Cumulative billing count 0 0 0 1 0 255 1
xxii) Cumulative programming count 0 0 96 2 0 255 1
xxiii) Billing date 0 0 0 1 2 255 3
xxiv) Cumulative energy, kWh 1 0 1 8 0 255 3/2
xxv) Cumulative energy, kvarh (Lag) 1 0 5 8 0 255 3/2
xxvi) Cumulative energy, kvarh (Lead) 1 0 8 8 0 255 3/2
xxvii) Cumulative energy, kVAh 1 0 9 8 0 255 3/2

NOTES
1 The items at Sl No. (v), (vi) and (vii) are for 3 Φ/4W system of measurement with NEUTRAL as reference point.
2 The items at Sl No. (viii) and (ix) are for 3 Φ/3W system of measurement with Y-Phase as reference point.
3 Signed Power factor : (+) indicates lag and (–) indicates lead.
4 The parameters at Sl No. (xviii) to (xxii) hold cumulative values at that instant from the date of manufacturing or installation of meter
as the case may be.
5 The above list is identified for the purpose of communication to HOST or HHU.
6 The utilities may choose, based on needs, additional parameters for display purpose only.
7 Item at Sl No. (xxi) refers to the Billing Period Counter.
8 Item at Sl No. (xxiii) — Data type to be same as for attribute 2 of IC = 8, Clock.

Table 28 Block Load Survey Parameters for Category C Meters

(Clauses E-2, E-4.1 and E-4.3)
Sl Parameter OBIS Code Interface
No. Class No./
A B C D E F Attribute
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Real time clock, date and time 0 0 1 0 0 255 8/2
ii) Current, IR 1 0 31 27 0 255 3/2
iii) Current, IY 1 0 51 27 0 255 3/2
iv) Current, IB 1 0 71 27 0 255 3/2
v) Voltage, VRN 1 0 32 27 0 255 3/2
vi) Voltage, VYN 1 0 52 27 0 255 3/2
vii) Voltage, VBN 1 0 72 27 0 255 3/2
viii) Voltage, VRY 1 0 32 27 0 255 3/2
ix) Voltage, VBY 1 0 52 27 0 255 3/2
x) Block energy, kWh 1 0 1 29 0 255 3/2
xi) Block energy, kvarh (lag) 1 0 5 29 0 255 3/2

21
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 28 (Concluded)
Sl Parameter OBIS Code Interface
No. Class No./
A B C D E F Attribute
(1) (2) (3) (4) (5) (6) (7) (8) (9)
xii) Block energy, kvarh (lead) 1 0 8 29 0 255 3/2
xiii) Block energy, kVAh 1 0 9 29 0 255 3/2

NOTES
1 The parameters listed in this table are for load survey purpose and are logged as per the block period time.
2 The parameters at Sl No. (ii) to (ix) are the average values during the block period time and stored at the end of that time block.
3 The parameters at Sl No. (x) to (xiii) are the actual energy consumption during that time block.
4 Capture objects for 3 Φ/4W are items at Sl No. (i) to (vii) and (x) to (xiii).
5 Capture objects for 3 Φ/3W are items at Sl No. (i) to (iv) and (viii) to (xiii).
6 Support for selective access shall be as defined in 11.3.

Table 29 Billing Profile Parameters for Category C Meters

(Clauses E-5.1 and E-5.3)
Sl Parameter OBIS Code Interface
No. Class No./
A B C D E F Attribute
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Billing date 0 0 0 1 2 255 3/2
ii) System power factor for billing period 1 0 13 0 0 255 3/2
iii) Cumulative energy, kWh 1 0 1 8 0 255 3/2
iv) Cumulative energy, kWh for TZ1 1 0 1 8 1 255 3/2
v) Cumulative energy, kWh for TZ2 1 0 1 8 2 255 3/2
vi) Cumulative energy, kWh for TZ3 1 0 1 8 3 255 3/2
vii) Cumulative energy, kWh for TZ4 1 0 1 8 4 255 3/2
viii) Cumulative energy, kWh for TZ5 1 0 1 8 5 255 3/2
ix) Cumulative energy, kWh for TZ6 1 0 1 8 6 255 3/2
x) Cumulative energy, kWh for TZ7 1 0 1 8 7 255 3/2
xi) Cumulative energy, kWh for TZ8 1 0 1 8 8 255 3/2
xii) Cumulative energy, kvarh (Lag) 1 0 5 8 0 255 3/2
xiii) Cumulative energy, kvarh (Lead) 1 0 8 8 0 255 3/2
xiv) Cumulative energy, kVAh 1 0 9 8 0 255 3/2
xv) Cumulative energy, kVAh for TZ1 1 0 9 8 1 255 3/2
xvi) Cumulative energy, kVAh for TZ2 1 0 9 8 2 255 3/2
xvii) Cumulative energy, kVAh for TZ3 1 0 9 8 3 255 3/2
xviii) Cumulative energy, kVAh for TZ4 1 0 9 8 4 255 3/2
xix) Cumulative energy, kVAh for TZ5 1 0 9 8 5 255 3/2
xx) Cumulative energy, kVAh for TZ6 1 0 9 8 6 255 3/2
xxi) Cumulative energy, kVAh for TZ7 1 0 9 8 7 255 3/2
xxii) Cumulative energy, kVAh for TZ8 1 0 9 8 8 255 3/2
xxiii) MD, kW 1 0 1 6 0 255 4/2 ,5
xxiv) MD, kW for TZ1 1 0 1 6 1 255 4/2 ,5
xxv) MD, kW for TZ2 1 0 1 6 2 255 4/2 ,5
xxvi) MD, kW for TZ3 1 0 1 6 3 255 4/2 ,5
xxvii) MD, kW for TZ4 1 0 1 6 4 255 4/2 ,5
xxviii) MD, kW for TZ5 1 0 1 6 5 255 4/2 ,5
xxix) MD, kW for TZ6 1 0 1 6 6 255 4/2 ,5
xxx) MD, kW for TZ7 1 0 1 6 7 255 4/2 ,5
xxxi) MD, kW for TZ8 1 0 1 6 8 255 4/2 ,5
xxxii) MD, kVA 1 0 9 6 0 255 4/2 ,5
xxxiii) MD, kVA for TZ1 1 0 9 6 1 255 4/2 ,5
xxxiv) MD, kVA for TZ2 1 0 9 6 2 255 4/2 ,5
xxxv) MD, kVA for TZ3 1 0 9 6 3 255 4/2 ,5
xxxvi) MD, kVA for TZ4 1 0 9 6 4 255 4/2 ,5
xxxvii) MD, kVA for TZ5 1 0 9 6 5 255 4/2 ,5
xxxviii) MD, kVA for TZ6 1 0 9 6 6 255 4/2 ,5
xxxix) MD, kVA for TZ7 1 0 9 6 7 255 4/2 ,5

22
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 29 (Concluded)
Sl Parameter OBIS Code Interface
No. Class No./
A B C D E F Attribute
(1) (2) (3) (4) (5) (6) (7) (8) (9)

xl) MD, kVA for TZ8 1 0 9 6 8 255 4/2 ,5

NOTES
1 The data are stored up to 6 billing cycles. The billing profile is modeled as Profile generic (IC = 7) object with OBIS Code 1.0.98.1.0.255.
The capture objects of this load profile are as per Table 29. The capture object values will be copied into buffer of this object either
automatically or asynchronously. The capture period is set to zero, billing action is controlled by billing dates as provided in 10 and
Table 31.
2 Support for selective access shall be as defined in 11.3.
3 The current cycle billing parameters shall be readable as the values of the latest billing period, on demand. This shall be in addition
to the last 6 billing period data which shall be available in the profile buffer as the last 6 entries in the buffer.
4 The captured attributes in case of Interface Class 4 (Extended register) used for MD values will be attributes 2 and 5 (Value and
Timestamp).

ANNEX F
(Clauses 6.1.1, B-5.1 and B-5.2)
GENERAL PURPOSE PARAMETERS
F-1 NAME PLATE DETAILS c) Utility setting — Read only for all objects.
The contents of Table 30 are common to all meters. F-2 PROGRAMMABLE PARAMETERS
The data are meter specific information.
Association access rights for programmable parameters
F-1.1 Association access rights for name plate details as given in Table 31 are as follows:
are as follows:
a) Public client — No access for all objects
a) Public client — No access for all objects except real time clock.
except meter serial number. b) Meter reader — Read only for all objects.
b) Meter reader — Read only for all objects. c) Utility setting — Read, write for all objects.

Table 30 Name Plate Details Parameters

(Clause F-1)
Sl Parameter OBIS Code Interface
No. Class
A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Meter serial number 0 0 96 1 0 255 1 (Data)
ii) Manufacturer name 0 0 96 1 1 255 1
iii) Firmware version for meter 1 0 0 2 0 255 1
iv) Meter type (3P-3W/3P-4W) 0 0 94 91 9 255 1
v) Internal CT ratio 1 0 0 4 2 255 1
vi) Internal VT ratio 1 0 0 4 3 255 1
vii) Meter year of manufacture 0 0 96 1 4 255 1

NOTE — For item Sl No. (iv), a value of ‘0’ indicates 3P-3W; a value of ‘1’ indicates 3P-4W.

23
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 31 Programmable Parameters

(Clause F-2)
Sl Parameter OBIS Code Interface
No. Class
A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Real time clock, date and time 0 0 1 0 0 255 8 (Clock)
ii) Demand integration period 1 0 0 8 0 255 1 (Data)
iii) Profile capture period 1 0 0 8 4 255 1
iv) Single-action schedule for billing dates 0 0 15 0 0 255 22
v) Activity calendar for time zones etc 0 0 13 0 0 255 20

NOTES
1 The parameters are programmable by the utility engineers with required access rights.
2 Unit for demand integration period and profile capture period is in ‘second’.
3 Programming of any of the parameters shall increment the ‘Cumulative programming count’ value.

ANNEX G
(Clauses 6.1.1 and B-1)
EVENT REFERENCE TABLE

G-1 EVENTS profile object will store (asynchronously) a new entry

for every event (occurrence and restoration are
Any exceptional/fraud/tamper condition is considered
considered as separate events). The capture objects for
as an Event and stored in an Event code object (OBIS
the event log object is define in Table 39.
= 0.0.96.11.e.255 IC = 1, values of e range from 0 to
6). The value attribute (attr-2) of this object stores G-1.1 Indian Event Reference Tables
identifier corresponding to most recent event occurred The contents of Tables 32 to 38 are common to all
in the meter. Unique identifier is assigned to occurrence categories of meter.
and restoration of all possible events (identified so far)
in the event reference tables (see Tables 32 to 38). Thus G-1.2 Capture Parameters for Event as Applicable
event code object will tell only about the most recent (Event Log Profile)
event and to get a picture of all events and associated
Association access rights are as follows:
information (at the time of event) an event log object
is used. An event log object is modelled as Profile a) Public client — No access;
generic (OBIS = 0.0.99.98.e.255 IC = 7, values of e b) Meter reading — Read only; and
range from 0 to 6). The buffer attribute (attr-2) of this c) Utility settings — Read only.

Table 32 Indian Event Reference Table — Voltage Related

(Clauses B-6.4, B-6.5, G-1 and G-1.1)
Sl No. Event ID Descriptions
(1) (2) (3)
i) 1 R-Phase — VT link missing (Missing potential) — Occurrence
ii) 2 R-Phase — VT link missing (Missing potential) — Restoration
iii) 3 Y-Phase — VT link missing (Missing potential) — Occurrence
iv) 4 Y-Phase — VT link missing (Missing potential) — Restoration
v) 5 B-Phase — VT link missing (Missing potential) — Occurrence
vi) 6 B-Phase — VT link missing (Missing potential) — Restoration
vii) 7 Over voltage in any phase — Occurrence
viii) 8 Over voltage in any phase — Restoration
ix) 9 Low Voltage in any Phase — Occurrence
x) 10 Low voltage in any phase — Restoration
xi) 11 Voltage unbalance — Occurrence

24
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 32 (Concluded)
Sl No. Event ID Descriptions
(1) (2) (3)

xii) 12 Voltage unbalance — Restoration

NOTES
1 These are the event conditions generally recorded in consumer meters, utilities may select any the above event conditions based on
their practice. The need and applicability of these events for other type of meters shall be considered by utility.
2 Either occurrence or restoration is considered an event.
3 For each of the events a certain list of parameters will be captured.
4 The list capture parameters are given in Table 39. The utility shall select the required parameters from Table 39 as per their practice.
5 For each of the event captured ‘Cumulative tamper count’ value will be incremented.
6 Capture parameters mentioned in Table 39 are captured when event occurrence and restoration is logged.
7 The attributes of each of the IC (Interface class) is to be identified while finalizing the Specification.
8 For 3 Φ/4W the reference point is NEUTRAL.
9 For 3 Φ/3W the reference point is Y-Phase.
10 Support for selective access shall be as defined in 11.3.

Table 33 Indian Event Reference Table — Current Related

(Clauses B-6.4, B-6.5, G-1 and G-1.1)
Sl No. Event ID Descriptions
(1) (2) (3)
i) 51 Phase — R CT reverse — Occurrence
ii) 52 Phase — R CT reverse — Restoration
iii) 53 Phase — Y CT reverse — Occurrence
iv) 54 Phase — Y CT reverse — Restoration
v) 55 Phase — B CT reverse — Occurrence
vi) 56 Phase — B CT reverse — Restoration
vii) 57 Phase — R CT open — Occurrence
viii) 58 Phase — R CT open — Restoration
ix) 59 Phase — Y CT open — Occurrence
x) 60 Phase — Y CT open — Restoration
xi) 61 Phase — B CT open — Occurrence
xii) 62 Phase — B CT open — Restoration
xiii) 63 Current unbalance — Occurrence
xiv) 64 Current unbalance — Restoration
xv) 65 CT bypass — Occurrence
xvi) 66 CT bypass — Restoration
xvii) 67 Over current in any phase — Occurrence
xviii) 68 Over current in any phase — Restoration

NOTES
1 These are the event conditions generally recorded in consumer meters, utilities may select any the above event conditions based on
their practice. The need and applicability of these events for other type of meters shall be considered by utility.
2 Either occurrence or restoration is considered an event.
3 For each of the events a certain list of parameters will be captured.
4 The list capture parameters are given in Table 39. The utility shall select the required parameters from Table 39 as per their practice.
5 For each of the event captured ‘Cumulative tamper count’ value will be incremented.
6 Capture parameters mentioned in Table 39 are captured when event occurrence and restoration is logged.
7 The attributes of each of the IC (Interface class) is to be identified while finalizing the Companion Specification.
8 For 3 Φ/4W the reference point is NEUTRAL.
9 For 3 Φ/3W the reference point is Y-Phase.
10 Support for selective access shall be as defined in 11.3.

25
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 34 Indian Event Reference Table 36 Indian Event Reference Table — Others
Table — Power Related (Clauses B-6.4, B-6.5, G-1 and G-1.1)
(Clauses B-6.4, B-6.5, G-1 and G-1.1)
Sl No. Event ID Descriptions
(1) (2) (3)
Sl No. Event ID Descriptions
(1) (2) (3) i) 201 Influence of permanent magnet or ac/
dc electromagnet — Occurrence
i) 101 Power failure (3 phase) — Occurrence ii) 202 Influence of permanent magnet or ac/dc
electromagnet — Restoration
ii) 102 Power failure (3 phase) — Restoration
iii) 203 Neutral disturbance — HF and dc —
Occurrence
NOTES iv) 204 Neutral disturbance — HF and dc —
1 These are the event conditions generally recorded in consumer Restoration
meters, utilities may select any the above event conditions based v) 205 Very low PF — Occurrence
on their practice. The need and applicability of these events for vi) 206 Very low PF — Restoration
other type of meters shall be considered by utility.
NOTES
2 Either occurrence or restoration is considered an event. 1 These are the event conditions generally recorded in consumer
3 For events in Table 34, no parameters shall be captured along meters, utilities may select any the above event conditions based
with the event. on their practice. The need and applicability of these events for
other type of meters shall be considered by utility.
4 The attributes of each of the IC (Interface class) is to be
identified while finalizing the Companion Specification. 2 Either occurrence or restoration is considered an event.
3 For each of the events a certain list of parameters will be captured.
5 For 3 Φ/4W the reference point is NEUTRAL.
4 The list capture parameters are given in Table 39. The utility
6 For 3 Φ/3W the reference point is Y-Phase. shall select the required parameters from Table 39 as per their
7 Support for selective access shall be as defined in 11.3. practice.
5 For each of the event captured ‘Cumulative tamper count’
value will be incremented.
Table 35 Indian Event Reference Table — 6 Capture parameters mentioned in Table 39 are captured when
Transaction Related event occurrence and restoration is logged.
7 The attributes of each of the IC (Interface class) is to be
(Clauses B-6.4, B-6.5, G-1 and G-1.1) identified while finalizing the Companion Specification.
8 For 3 Φ/4W the reference point is NEUTRAL.
Sl No. Event ID Descriptions 9 For 3 Φ/3W the reference point is Y-Phase.
(1) (2) (3) 10 Support for selective access shall be as defined in 11.3.

i) 151 Real time clock, date and time

ii) 152 Demand integration period
Table 37 Indian Event Reference
iii) 153 Profile capture period Table — Non-rollover Events
iv) 154 Single-action schedule for billing dates (Clauses B-6.4, B-6.5, G-1 and G-1.1)
v) 155 Activity calendar for time zones, etc
Sl No. Event ID Descriptions
(1) (2) (3)
NOTES
1 These are the event conditions generally recorded in consumer i) 251 Meter cover opening — Occurrence
meters, utilities may select any the above event conditions based
NOTES
on their practice. The need and applicability of these events for
1 This event condition is generally recorded in consumer meters,
other type of meters shall be considered by utility.
utilities may select the above event condition based on their
2 Either occurrence or restoration is considered an event. practice. The need and applicability of the event for other type
3 For each of the events a certain list of parameters will be of meters shall be considered by utility.
captured. 2 Either occurrence or restoration is considered an event.
4 The list capture parameters are given in Table 39. The utility 3 For the event a certain list of parameters will be captured.
shall select the required parameters from Table 39 as per their 4 The list capture parameters are given in Table 39. The utility
practice. shall select the required parameters from Table 39 as per their
5 Capture parameters mentioned in Table 39 are captured when practice.
event occurrence and restoration is logged. 5 Capture parameters mentioned in Table 39 are captured when
event occurrence and restoration is logged.
6 The attributes of each of the IC (Interface class) is to be
6 The attributes of each of the IC (Interface class) is to be
identified while finalizing the Companion Specification.
identified while finalizing the Companion Specification.
7 For 3 Φ/4W the reference point is NEUTRAL. 7 For 3 Φ/4W the reference point is NEUTRAL.
8 For 3 Φ/3W the reference point is Y-Phase. 8 For 3 Φ/3W the reference point is Y-Phase.
9 Support for selective access shall be as defined in 11.3. 9 Support for selective access shall be as defined in 11.3.

26
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Table 38 Indian Event Reference Table — Control Events

(Clauses B-6.4, B-6.5, G-1 and G-1.1)
Sl No. Event ID Descriptions
(1) (2) (3)
i) 301 Meter load disconnected
ii) 302 Meter load connected

NOTES
1 These are the event conditions generally recorded in consumer meters, utilities may select any the above event conditions based on
their practice. The need and applicability of these events for other type of meters shall be considered by utility.
2 Either occurrence or restoration is considered an event.
3 For events in Table 38 no parameters shall be captured along with the event.
4 The attributes of each of the IC (Interface class) is to be identified while finalizing the Companion Specification.
5 For 3 Φ/4W the reference point is NEUTRAL.
6 For 3 Φ/3W the reference point is Y-Phase.
7 Support for selective access shall be as defined in 11.3.

Table 39 Capture Parameters for Events

(Clauses B-6.4, B-6.5 and G-1)
Sl No. Parameter OBIS Code Interface
Class
A B C D E F
(1) (2) (3) (4) (5) (6) (7) (8) (9)
i) Date and time of event 0 0 1 0 0 255 8 (Clock)
ii) Event code 0 0 96 11 0 255 1 (Data)
iii) Current, IR 1 0 31 7 0 255 3 (Register)
iv) Current, IY 1 0 51 7 0 255 3 (Register)
v) Current, IB 1 0 71 7 0 255 3 (Register)
vi) Voltage, VRN
(3 Φ/4W) 1 0 32 7 0 255 3 (Register)
vii) Voltage, VYN
(3 Φ/4W) 1 0 52 7 0 255 3 (Register)
viii) Voltage, VBN
(3 Φ/4W) 1 0 72 7 0 255 3 (Register)
ix) Voltage, VRY
(3 Φ/3W) 1 0 32 7 0 255 3 (Register)
x) Voltage, VYB
(3 Φ/3W) 1 0 52 7 0 255 3 (Register)
xi) Power factor, R-Phase 1 0 33 7 0 255 3 (Register)
xii) Power factor, Y-Phase 1 0 53 7 0 255 3 (Register)
xiii) Power factor, B-Phase 1 0 73 7 0 255 3 (Register)
xiv) Cumulative energy, kWh 1 0 1 8 0 255 3 (Register)

NOTES
1 These are the event conditions generally recorded in consumer meters, utilities may select any of the above event conditions based on
their practice. The need and applicability of these events for other type of meters shall be considered by utility.
2 Either Occurrence or Restoration is considered an event.
3 For each of the events a certain list of parameters will be captured.
4 The list of capture parameters are given. The utility shall select the required parameters from the table as per their practice.
5 Capture parameters mentioned in the table are to be captured when event occurrence and restoration is logged.
6 For 3 Φ/4W the reference point is NEUTRAL.
7 For 3 Φ/3W the reference point is Y-Phase.
8 Support for Selective access shall be as defined in 11.3.

G-2 SCALER PROFILE unit attributes of the parameters listed above.

This profile is meant for capturing the scaler-unit of Parameters listed above that do no have a scaler-unit
each of the parameter listed in Table 39. This is attribute shall not be included in the capture objects
modelled as profile generic (IC = 7) and is assigned of this profile. The profile buffer shall have only one
the country specific OBIS code 1.0.94.91.7.255. The entry. This profile is not required to be updated
capture objects for this profile shall include the scaler- periodically.

27
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

ANNEX H
(Clause 2 )
LIST OF REFERRED INDIAN/INTERNATIONAL STANDARDS

Indian/Interna- Title Indian/Interna- Title

tional Standard tional Standard
ISS 14697 : 1999 ac static transformer operated watt- IS/IEC 62056- Electricity metering: Part 61 Data
hour and var-hour meters, class 0.2 S, 61 : 2006 exchange for meter reading, tariff and
0.5 S and 1.0 S — Specification load control Object identification
DLMS UA 1000 Blue book, COSEM identification system (OBIS)
-1 ed.9, 2009 system and interface classes IS/IEC 62056- Electricity metering : Data exchange
DLMS UA 1000 Green book, DLMS/COSEM 62 : 2006 for meter reading, tariff and load
-2 ed.7, 2007 architecture and protocols control: Part 62 Interface classes
DLMS UA 1002: White book, COSEM Glossary of IEC/TR 62051: Electricity metering — Glossary of
ed.1, 2003 terms 1999 terms
DLMS UA 1001 Yellow book, companion testing IS/IEC/TR Electricity metering : Data exchange
-1:2007 ed-3 process 62051-1: 2004 for meter reading, tariff and load control
IS/IEC 62056- Electricity metering : Data exchange — Glossary of terms: Part 1 Terms
21 : 2002 for meter reading, tariff and load related to data exchange with metering
control: Part 21 Direct local data equipment using DLMS/COSEM
exchange NIST Special Recommendation for block cipher
IS/IEC 62056- Electricity metering : Data exchange Publication 800 modes of operation: Galois/Counter
42 : 2002 for meter reading, tariff and load -38D, Nov 2007 mode (GCM) and GMAC
control: Part 42 Physical layer NIST Federal Advanced encryption standard
services and procedures for Information (AES)
connection-oriented asynchronous Processing
data exchange Standards
IS/IEC 62056- Electricity metering : Data exchange Publication 197 :
46 : 2007 for meter reading, tariff and load Nov 2001
control: Part 46 Data link layer using NIST Federal Standards for security categorization
HDLC protocol Information of federal information and
IS/IEC 62056- Electricity metering Data exchange Processing information systems
47 : 2006 for meter reading tariff and load Standards
control: Part 47 COSEM transport Publication 199 :
layer for IPv4 network 2004
IS/IEC 62056- Electricity metering : Data exchange IETF Request Advanced encryption standard (AES)
53 : 2006 for meter reading, tariff and load For Circulation key wrap algorithm (Informative )
control: Part 53 COSEM application (RFC) - 3394 :
layer Sept, 2002

ANNEX J
(Clause 3.6)
HHU (MRI) CONSIDERATION

J-1 HHU (MRI) CONSIDERATION a suitable approach to the implementation of the IEC-
62056 standards and this Indian Companion
Communication standards in the Indian metering
Specification in such devices.
scenario require supporting considerations for the
utilization of those standards in HHUs (Hand held units J-1.1 The terms of this suggested implementation are
synonymous with MRI or CMRI ). This Annex provides as below:

28
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

a) HHUs may retrieve data from DLMS/COSEM server shall support one association with
Meters conforming to this standard using the properties, objects, and access rights adequate
communication ports. for transferring the stored data of the
b) HHUs shall exclusively use the Meter Reading corresponding meter to the BCS in an efficient
(MR) association and shall support all the manner. The server within the HHU is not
features and specifications listed in this required to support ad-hoc access or selective
specification for the MR association. access to the data that differs from the requests
c) HHUs shall have the same data access rights which were earlier used to read the data from
that are available to the MR association, as the meter.
that available for remote meter reading. h) The BCS shall maintain a mapping table that
d) HHU when acting as a server shall support maps the individual meter identifications (the
the client addresses and security methods of same IDs that are used to identify the meter
the Meter Reading (MR) association. during remote meter reading) to Logical
Device addresses. During upload of data from
e) HHUs shall provide a DLMS/COSEM server
HHU to BCS, the BCS shall query each
interface to the BCS (Base Computer System
Logical device to download the data of each
— the Data collection software) over a
meter over the local serial port.
suitable communication medium (local serial
port implementing the DLMS/COSEM CO 3- j) The mapping table described in Item I-1.6
layer stack is suggested). above shall require that the Logical device
addresses allocated to each meter are at least
f) HHUs shall internally map the individual
unique across all meters that are to be retrieved
meter data to Logical Devices (one Logical
using one HHU. Other HHUs may re-use the
Device for each meter). Inside each Logical
same addressing from their own range of
Device the structure and naming of the data
allocated meters. The BCS shall take care to
shall be the same as that retrieved from the
ensure that the re-use of addresses does not
meter.
create conflicts in Meter identification.
g) For each logical device the DLMS/COSEM

ANNEX K
(Clause 3.23 )
CONFORMANCE TESTING

K-1 Meters claiming conformance to this specification as specified in this standard with all specified
will be required to services supported;
a) conform to the DLMS/COSEM base standards d) association object lists conform to this
(IEC 62056) as certified by the conformance document with access rights and OBIS codes
test tool (CTT). as specified here; and
b) conform to the specific requirements and e) event related DLMS objects are implemented
constraints of this standard as certified by with Event identifiers as specified in the Event
CPRI or any other laboratory having facilities reference tables in this standard.
for the purpose. K-2.1 The test report from an accredited laboratory
K-2 This certification shall ensure: and having membership with DLMS UA shall be
considered as a proof of conformance of protocol
a) all mandatory parameters applicable to the
implementation.
category of the meter under test are
implemented; K-2.2 Systems once created in accordance with this
b) all data types where specified are conforming specification and contemporary standards, shall be
to this document; deemed acceptable, provided such systems are tested
c) all application associations are implemented and certified through standard evaluation process.

29
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

ANNEX L
(Clause 11.3.4)
DESCRIPTIVE NOTES ON PROFILE GENERIC INTERFACE CLASS

L-1 Profile generic objects are available to capture accessed in its entirety or selectively, using appropriate
values of attributes from other objects periodically or selection criteria.
occasionally. They can be used:
L-1.3 Profile generic objects provide attributes and
a) for load profiles; methods for controlling and managing how data are
b) for historical data; and captured and accessed as illustrated in Fig. 3.
c) for event logs, etc.
L-2 SELECTIVE ACCESS
L-1.1 The list of attributes to capture are held by the
There are two types of selective access which allows
capture object attribute. The values captured are held
reading the buffer selectively.
in the buffer attribute.
L-2.1 Selective Access by Entry
L-1.2 The buffer can be seen as a table, with the capture
objects as column headers and a new line of values Selective Access by Entry provides a set of 4 integers
added with each capture. The data in the buffer can be to filter the contents of the “buffer” attribute in response

Logical Name
1.0.99.1.0.255

X1 Y1 01-01-07 06:00:00
X2 Y2 01-01-07 06:15:00
Buffer . . .
. . .

X16 Y16 01-01-07 10:00:00

IC OBIS Attr ID Data index
Capture 0003 01 00 00 06 00 FF 02 00
Objects 0003 01 00 00 06 01 FF 02 00
0008 00 00 01 00 00 FF 02 00
Capture period 15 mnts

Sort method FIFO

Sort object Default

Entries in use 16

Profile entries 1000

FIG. 3 I LLUSTRATION OF A PROFILE GENERIC OBJECT CONTAINING 16 CAPTURES OF 3 ATTRIBUTES

30
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

to get requests as illustrated in Fig. 4. The 4 integers Typically the capture object selected for this purpose
are as below: is the Clock’s date-time attribute which is usually one
of the capture objects in most profiles as illustrated in
a) From-Entry — The index of the first entry to
Fig. 6. The selective access parameters in this case are
return from the buffer.
as below:
b) To-Entry — The index of the last entry to
return from the buffer. L-2.2.1 Restricting Object
c) From-Value — The index of the first column This parameter identifies the capture object whose
to return. value will be used to filter the buffer. The object is
d) To-Value — The index of the last column to defined by the OBIS Code and attribute index of the
return. selected object.
Thus the selective access parameters as above can be L-2.2.2 From-Value
used to select a subset of the rows from the buffer table.
The start-range value for the subset. All selected rows
Also the selective access parameters as above can be in the buffer will have a value for the restricted object
used to select not only a subset of the rows from the that is higher than or equal to this limit.
buffer table but also a subset of the columns from among
the selected rows. Refer to the illustration in Fig. 5. L-2.2.3 To-Value
However this mechanism does not permit retrieving The stop-range value for the subset. All selected rows
discontinuous ranges of columns from the buffer. in the buffer will have a value for the restricting object
that is lower than or equal to this limit.
L-2.2 Selective Access by Range
L-2.2.4 Selected-Values
Selective access by range permits a client to retrieve a
subset of the rows and columns in the Profile buffer An array of column indices specifying the columns that
based on the value of one of the capture objects. should be returned from the selected rows.

ENTRY_DESCRIPTOR {
00000002
00000004
0000
0000
Entry 2
}

Value 1 Value 2

Entry 4

Y2 01-01-07 06:15:00
Y3 01-01-07 06:30:00
Y4 01-01-07 06:45:00

NOTE — This illustration requests from 2nd row to the 4th row.

F IG. 4 I LLUSTRATION OF S ELECTIVE ACCESS OF PROFILE BUFFER BY ENTRY

31
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

NOTE — This illustration requests only the 2nd and 3rd columns of data from the 2nd row to the 4th row.

F IG. 5 I LLUSTRATION OF S ELECTIVE ACCESS OF PROFILE BUFFER BY ENTRY

RANGE—DESCRIPTOR
{0008, 0000010000FF, 02, 0000}
1-1-7 06:00:00
1-1-7 08:00:00
00 }
All columns
are returned

X1 Y1 01-01-07 06:00:00
X2 Y2 01-01-07 06:15:00
. . .
. . .

X8 Y8 01-01-07 08:00:00

FIG. 6 ILLUSTRATION OF SELECTIVE ACCESS OF PROFILE BUFFER BY R ANGE

32
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

ANNEX M
(Foreword)
ACRONYMS AND ABBREVIATIONS

Acronyms and Description

Abbreviations
IEC International Electro-technical Commission
NIST National Institute for Standards and Technology
IETF Internet Engineering Task Force
DLMS Device Language Message Specification
DLMS UA Device Language Message Specification User Association
COSEM Companion Specification for Energy Metering
HHU Hand Held Unit
MRI Meter Reading Instrument
DCE Data Communication Equipment
DC Data Concentrator
PSTN Public Switched Telephone Network
GSM Global System for Mobile Communications
GPRS General Packet Radio Service
802.2 LLC ISO/IEC 8802-2 defined Logical Link Control
IEEE Institute of Electrical and Electronics Engineers
ASE Adaptive Server Enterprise for database security
ZigBee Low power wireless connectivity based on IEEE standard 802.15.4 protocol
VZ Vorwarts Zaehler (previous value counter)
IP Internet Protocol
PC Public Client
MR Meter Reader
US Utility Settings
TCP Transmission Control Protocol (for connection oriented service)
UDP User Datagram Protocol ( for connectionless service)
RS232/RS485 Recommended industrial Standards for communication between driver and receiver equipment
TOU Time of Use
ABT Availability Based Tariff
CTT Conformance Test Tool
TZ Time Zone

33
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

ANNEX N
(Foreword)
COMMITTEE COMPOSTION
Equipment for Electrical Energy Measurement, Tariff and Load Control Sectional Committee, ETD 13

Organization Representative(s)
In personal capacity (Triparna 28/10/1C, Nakuleshwar Bhattachrya, SHRI SUBRATA BISWAS (Chairman)
Kalighat, Kolkata)
Areva T&D India Ltd (ALSTOM), Kolkata SHRI H. RAY
Bharat Heavy Electricals Ltd, Bangalore SHRI THARAK RAJ
SHRI BALASUBRAMANIAN M. (Alternate)
Brihan Mumbai Electric Supply & Transport Undertaking, Mumbai SHRI N. V. B HANDAR
SHRI S. M. SAKPAL (Alternate)
BSES Rajdhani Power Ltd, New Delhi SHRI BANSAL RAJESH
SHRI GITAY RAJ (Alternate)
Bureau of Energy Efficiency, New Delhi SHRI G. PANDIAN
CG Actaris Electricity Management Ltd, New Delhi SHRI ASHOK DASH
SHRI ASHISH TANDON (Alternate I)
SHRI NEELABHRA PAUL (Alternate II)
Central Board of Irrigation & Power, New Delhi SHRI K. P. SINGH
SHRI S. K. BATRA (Alternate)
Central Electricity Authority, New Delhi SHRIMATI ANJALI CHANDRA
SHRIMATI A. K. RAJPUT (Alternate)
Central Power Research Institute, Bangalore SHRI R. K. HEGDE
SHRI B. A. SAWALE (Alternate)
CESC Limited, Kolkata SHRI UDAYAN G ANGULI
SHRI SIDDHARTHA MUKHERJEE (Alternate)
Development Commissioner Micro, Small & Enterprises, SHRI A. K. VERMA
New Delhi
ECE Industries Ltd, Hyderabad SHRI K. K. SHARMA
Electrical Research & Development Association, Vadodara SHRI U. C. TRIVEDI
SHRI H. K. MISHRA (Alternate)
Elster Metering Private Ltd, Mumbai SHRIMATI MANJUSHRI
Genus Overseas Electronics Ltd, Jaipur SHRI UMESH SONI
Genus Power Infrastructures Ltd, Jaipur SHRI ARVIND KAUL
HPL-Socomec Pvt Ltd, Gurgaon SHRI C. P. JAIN
SHRI SUNDEEP TANDON (Alternate)
IEEMA, New Delhi SHRI SUNIL SINGHVI
SHRIMATI ANITA GUPTA (Alternate)
Jaipur Vidyut Vitaran Nigam Ltd, Jaipur SHRI ARJUN S INGH
Larsen & Toubro Ltd, Mysore SHRI R. M. BHAKTA
SHRI AHUJA SANJAY (Alternate)
Landis & Gyr Ltd, Kolkata SHRI PRADIP RANJAN DUTT
SHRI S. PAL (Alternate I)
SHRI ANAND SRIVASTAVA (Alternate II)
SHRI R. DUBEY (Alternate III)
Maharashtra State Transco Ltd, Mumbai SHRI SANTOSH N. KATAKWAR
National Physical Laboratory, New Delhi SHRI M. K. MITTAL
SHRI BISWAS (Alternate)
North Delhi Power Ltd, New Delhi SHRI R. K. SINGH
SHRI DESHMUKH (Alternate)
NTPC, Noida SHRIMATI M. S. RADHA
SHRI HIMANSHU SHEKHAR (Alternate)

34
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.
IS 15959 : 2011

Organization Representative(s)
Power Grid Corporation of India Ltd, New Delhi SHRI V. MITTAL
MS PUNAM (Alternate)
PRAYAS, Secundrabad SHRI SREEKUMAR N.
SHRI GIRISH SANT (Alternate)
Rural Electification Corporation Ltd, New Delhi SHRI DINESH K UMAR
SHRI P. S. HARIHARAN (Alternate)
Secure Meters Ltd, Gurgaon SHRI KAUSHIK GHOSH
SHRI JHALORA SURENDRA (Alternate I)
SHRI SINGHVI S. K. (SML) (Alternate II)
The Tata Power Co Ltd, Mumbai SHRI S. C. DHAPRE
SHRI S. G. JOSHI (Alternate)
Voluntary Organisation in Interest of Consumer Education, SHRI T. C. KAPOOR
New Delhi SHRI H. WADHWA (Alternate)
Yadav Measurements Pvt Ltd, Udaipur SHRI B. M. VYAS
SHRI N. K. BHATI N.K (Alternate)
BIS Directorate General SHIR R. K. TREHAN, Scientist ‘E’ and Head (ETD)
[Representing Director General (Ex-officio)]

Member Secretary
SHRIMATI MANJU GUPTA
Scientist ‘E’ (ETD), BIS

Panel on Metering Protocols and Interoperability, ETD 13/P1

Central Power Research Institute, Bangalore SHRI V. ARUNACHALAM (Convener)
Brihan Mumbai Electric Supply & Transport Undertaking, SHRI S. M. SAKPAL
Mumbai
Central Electricity Authority, New Delhi SHRI ALOK G UPTA
CESC Limited, Kolkata SHRI UDAYAN G ANGULI
Elster Metering Private Ltd, Mumbai SHRI P. C. KARNIK
HPL-Socomec Pvt Ltd, Gurgaon SHRI C. P. JAIN
Larsen & Toubro Ltd, Mysore SHRI SANJAY A HUJA
Landis & Gyr. Ltd, Kolkata SHRI RAMESHWAR D UBEY
IEEMA, New Delhi SHRI J. PANDE
Kalki Communication Technologies Ltd, Bangalore SHRI VINOO S. WARRIOR
North Delhi Power Ltd, New Delhi SHRI R. K. SINGH
Secure Meters Ltd, Gurgaon SHRI JHALORA S URENDRA
In personal capacity (Triparna 28/10/1C, Nakuleshwar Bhattachrya, SHRI SUBRATA BISWAS
Kalighat, Kolkata)

35
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.

(Continued from second cover)

India, may be referenced as IEC pre-standards. Contact details of these members can be found at -http://
www.dlms.com/organization/listofmembers/index.html.
While writing this Specification it has been endeavoured not to contradict on principle IEC 62056 and the DLMS/
COSEM updates on which it is based. However, in case of any divergence/disparity, not amounting to conflict of
interpretations that may be revealed later, provisions of this specification will prevail.
The acronyms and abbreviations used in this standard are given in Annex M (see also IS/IEC/TR 62051-1).
The composition of the Committee responsible for the formulation of this standard is given at Annex N.
For the purpose of deciding whether a particular requirement of this standard is complied with, the final value,
observed or calculated, expressing the result of a test or analysis, shall be rounded off in accordance with IS 2 : 1960
‘Rules for rounding off numerical values (revised)’. The number of significant places retained in the rounded off
value should be the same as that of the specified value in this standard.
 Free Standard provided by BIS via BSB Edge Private Limited to Required for Self Learning -
Mumbai(shivangp000@gmail.com) 163.116.213.74.

Bureau of Indian Standards

BIS is a statutory institution established under the Bureau of Indian Standards Act, 1986 to promote
harmonious development of the activities of standardization, marking and quality certification of goods
and attending to connected matters in the country.

Copyright

BIS has the copyright of all its publications. No part of these publications may be reproduced in any form
without the prior permission in writing of BIS. This does not preclude the free use, in the course of
implementing the standard, of necessary details, such as symbols and sizes, type or grade designations.
Enquiries relating to copyright be addressed to the Director (Publications), BIS.

Review of Indian Standards

Amendments are issued to standards as the need arises on the basis of comments. Standards are also reviewed
periodically; a standard along with amendments is reaffirmed when such review indicates that no changes are
needed; if the review indicates that changes are needed, it is taken up for revision. Users of Indian Standards
should ascertain that they are in possession of the latest amendments or edition by referring to the latest issue of
‘BIS Catalogue’ and ‘Standards : Monthly Additions’.

This Indian Standard has been developed from Doc No.: ETD 13 (6211).

Amendments Issued Since Publication

Amend No. Date of Issue Text Affected

BUREAU OF INDIAN STANDARDS

Headquarters:
Manak Bhavan, 9 Bahadur Shah Zafar Marg, New Delhi 110002
Telephones : 2323 0131, 2323 3375, 2323 9402 Website: www.bis.org.in

Regional Offices: Telephones

Central : Manak Bhavan, 9 Bahadur Shah Zafar Marg
NEW DELHI 110002 { 2323 7617
2323 3841
Eastern : 1/14 C.I.T. Scheme VII M, V. I. P. Road, Kankurgachi
KOLKATA 700054 { 2337 8499, 2337 8561
2337 8626, 2337 9120
Northern : SCO 335-336, Sector 34-A, CHANDIGARH 160022
{ 60 3843
60 9285
Southern : C.I.T. Campus, IV Cross Road, CHENNAI 600113
{ 2254 1216, 2254 1442
2254 2519, 2254 2315
Western : Manakalaya, E9 MIDC, Marol, Andheri (East)
MUMBAI 400093 { 2832 9295, 2832 7858
2832 7891, 2832 7892
Branches: AHMEDABAD. BANGALORE. BHOPAL. BHUBANESHWAR. COIMBATORE. DEHRADUN.
FARIDABAD. GHAZIABAD. GUWAHATI. HYDERABAD. JAIPUR. KANPUR. LUCKNOW.
NAGPUR. PARWANOO. PATNA. PUNE. RAJKOT. THIRUVANANTHAPURAM.
VISAKHAPATNAM.
P P Published by BIS, New Delhi.