DLMSUA TPAK1_Intro

1
IEC 62056 DLMS/COSEMworkshopPart 5 COSEM data
model
Metering, Billing/CRM Asia 13-14th May 2009,
Bangkok Gyozo Kmethy, DLMS UA, President
2
Breaking news Blue Book 9 issued

• Release date 9th February 2009
• Contains all recent additions for smart metering
  and advanced gas metering
• New elements derived from and used in Dutch and
  French projects, as well as Italian Gas project
• Flexibility, expandibility and future proofness
  of COSEM proven

3
Contents

• Object modelling
• COSEM interface classes
• OBIS Object identification system
• Recent extensions for smart metering

4
IEC 62056 DLMS/COSEM
Object modelling
5
Object modelling
The NAME attributeidentifies the data
NAME
Any real-world things can be described by some
attributes
Attribute 1
Attribute 2
Each attribute has a meaning, a data type and a
value range
...
Using the object means
Attribute n
...to read or write the attributes
Method 1
Methods allow performing operations on attributes
...
Method n
...to invoke the methods
Attributes and methods constitute an object
6
Modelling, from reality to abstraction
Template

• All data in the meter are mapped to objects
• The model provides the meters functional view
• Similar objects make up an interface class (IC)
• Each IC has a specific set of attributes and
  methods
• All ICs are accessed with the same xDLMS services

7
Object model common for all energy types
IC template
Interface class
Instances
Three phase import active energy 1.0.1.8.0.255 401
53 kWh
S Li A total
Value
scaler_unit
Register 1
Forward undisturbed meter volume 7.0.1.0.0.255,
7086 m3

• Abstract objects e.g. service parameters,
  clock, schedules, scripts, communication channel
  setup
• Energy type specific objects

8
COSEM interface classes

• Data storage
• measurement data
• statuses, events
• parameters

• Time / event bound control
• Clock
• Schedule
• Scripts

• Access control
• Association
• SAP
• Logical dev. name
• Security setup

• Comm. setup
• Local port
• Modem
• Internet
• PLC

9
COSEM interface class tree
10
Objects for data storage
.need a value
need a scaler, a unit and need to Reset the
value
...need to know when the data was measured and
its status
......

• Object names are
• standardised
• unique
• have a defined meaning

11
Objects for control applications
A Clock object to keep the time
Schedule objects to define tasks
Script objects to perform tasks
Register activation objects define tariff masks
Script
Name
Id
Command
Execute
12
Profiles Efficient data organisation
Logical device 2
Any attributes can be captured in profiles
Read-out lists, Load profiles, Historical values,
Events
Logical device 1
Selective access

• Uniform attributes can be captured in Register
  table objects simple profile
• Examples Voltage dips, Harmonics

13
Specific objects

• Specific instances of standard classes
• Specific classes
• No need and no possibility for conformance testing

• Manufacturer specific
• configuration ( e.g. HW dependent)
• specific grouping of data
• novel features

• Country specific
• country specific elements, e.g. VDEW /
  Germany

• Consortia specific
• example SELMA

• Utility specific
• utility specific features

14
Device modelling

• A meter is modelled as a physical device
• A physical device contains one or more logical
  devices (LD)
• One and only one Management Logical Device is
  mandatory
• Each LD has the objects required for the
  application organization tool
• Mandatory objects one Logical Device Name and
  one Current Association

15
Modelling, from abstraction to reality
Instantiation of objects
Allocation to logical devices
16
OBIS data identification system
EDIS 'Wertegruppe'
M -
KK
GG .
AA
. T
VV
OBIS 'value group'
A
B
C
D
E
F

• Six value groups in a hierarchical structure
• Meaningful combinations standardised
• Reduced codes for display and standard readout

0...255Quantity
0..126Historical values
0...64Channel
0...255Classification e.g. tarification
0...15Medium
0...255Processing e.g. integration
Example
1 Electricity
1 Channel
1 S Li A
8Time int. 1
2 Rate 2
255 Not used
17
Identification of measurement values
18
Identification of abstract data
19
Example 1 Tarification and billing
Quantity
Channels
Month
Tariff
Processing
Source
Active
Channel 0
Current
Total
Energy
Data
Electricity
Reactive
Channel 1
Last
T1
Average
Heat cost
Apparent
...
2nd last
T2
Mini
Cooling
Voltage
...
...
Maxi
Heat
Current
Cum. Maxi
nth last
...
...
Gas
Frequency
Threshold
...and many more
Cold water
Power fact.
Instant.
...
Hot water
Angles
Channel n
T n
20
Example 2 Power quality data
Quantity
Channels
Month
Harmonics
Processing
Source
Active
Channel 0
Current
Total
Energy
Data
Electricity
Reactive
Channel 1
Last
H1
Average
Heat cost
Apparent
...
2nd last
H2
Mini
Cooling
Voltage
Hn
Maxi
Heat
Current
nth last
f U,I
Cum. Maxi
Gas
Frequency
Dips
Threshold
...and many more
Cold water
Power fact.
...
Instant.
Hot water
Angles
Channel n
I2-I3
21
Profile generic objects and their use
Load profiles
Billing profiles
Harmonics
Event log
...and many more
22
Tariff- and load control, register monitor
Clock
Schedule
Script
Register list
Time Tasks
Date/Time
Action list
Tariff schemes
Output control
Calendar
Season/Week/Day Tasks
Alarms e.g. SMS
...and many more
Monitor
Register
Thresholds Tasks
Value
23
IEC 62056 DLMS/COSEM
Recent extensions for smart metering
24
Smart residential metering requirements

• Multi-energy
• Messages for the customer
• Load limitation
• Connect / disconnect for load contract
  management
• Association objects authenticated access rights
• Data security
• Firmware upgrade
• Status / Fraud monitoring

25
Multi-energy key requirements
E-meter shall read the gas meter registers and
load profiles
E-meter acts as M-Bus master, controls up to 4
M-Bus slaves
Install / de-install M-Bus devices
Commands to the gas meter clock setting, alarm
reset, valve control
26
Multi energy COSEM solution (1)

• New interface classes and objects
• M-Bus client objects configure E-meters as M-Bus
  masters, to exchange data with M-Bus devices
• M-Bus master port setup object sets up DLMS/COSEM
  device as M-Bus master
• M-Bus master value objects and profile generic
  objects hold values captured from M-Bus slave
  devices
• M-Bus master disconnect control objects control
  disconnector devices of M-Bus slave devices (e.g.
  gas valves)
• M-Bus master control log objects log status
  changes of the disconnect device

27
Multi-energy COSEM solution (2)

• M-Bus protocol parameters mapped to attributes
• M-Bus functions are mapped to methods

28
Messages for the customer

• Requirement display messages on meter display
  and customer display
• reason for disconnect
• threshold limitation
• impending credit shortage etc.
• also messages related to gas, water

• COSEM solution
• use instances of existing Data / Register /
  Extended register classes
• new OBIS codes (with Data class)
• 0.0.96.13.0.255 customer port
• 0.0.96.13.1.255 display and customer port

29
Load limitation - key requirements
Triggers set contract level, anticipate shortage
(code red), credit low
Remote setting of thresholds (can be Imax), with
plausibility check
Setting the thresholds shall be logged
If threshold exceeded, disconnect (local)
Manual reconnect by customer
30
Load limitation COSEM solution

• Allows specifying the value to be monitored
• Allows defining normal/emergency threshold, with
  min. over/under threshold duration
• With threshold 0, timed OFF / ON
• Allows allocating the meter to emergency groups
• Allows specifying the actions (scripts) to be
  executed)

31
Connect / disconnect key requirements
Disconnect above threshold, low credit,
emergency, contract close
Connect contract open, below threshold, credit
ok, emergency over
The breaker / valve is not a safety device !
Appropriate security (authentication)
All events must be logged
32
Connect / disconnect - COSEM solution (1)
33
Connect / Disconnect COSEM solution (2)

• Remote disconnect / reconnect
• Manual disconnect / reconnect
• Local disconnect (limiter, prepayment) /
  reconnect
• Control modes determine possible transitions
• Controls electricity breaker or gas valve
• Works with Register, Clock, Limiter and Script
  objects

34
New version of Association SN class

• New acess_rights_list attribute provides access
  rights
• Link between object_list and access_right_list
  is short_name
• New security_setup_reference attribute points to
  Security setup object managing security for the
  particular Association object instance
• Selective access by base_name

35
Access rights (fragment)
access_rights_type array access_rights_elemen
t access_rights_element structure base_name
long, attribute_access attribute_access_descr
iptor, method_access method_access_descriptor
attribute_access_descriptor array
attribute_access_item attribute_access_item
structure attribute_id integer, access_mode
enum, (0) no_access, (1) read_only, (2) w
rite_only, (3) read_and_write, (4) authenticat
ed_read_only, (5) authenticated_write_only (6)
authenticated_read_and_write
Authenticated access can be specified selectively
for each attribute and method
36
New version of Association LN class

• New security_setup_reference attribute points to
  Security setup object managing security for the
  particular Association object instance

37
Access rights (fragment)
access_right structure attribute_access a
ttribute_access_descriptor, method_access metho
d_access_descriptor attribute_access_descriptor
array attribute_access_item attribute_access_i
tem structure attribute_id integer, acces
s_mode enum     (0) no_access, (1) read_on
ly, (2) write_only, (3) read_and_write, (4)
authenticated_read_only, (5) authenticated_write
_only (6) authenticated_read_and_write
Authenticated access can be specified selectively
for each attribute and method
38
Security setup class

• security policy determines if authentication,
  encryption or both apply globally
• security suite defines algorithm Galois /
  Counter mode based on AES 128
• security activate method turns up security A
  E AE
• global_key_transfer transfers global keys using
  AES key wrapping
• dedicated key is transferred at application
  association establishment

39
Firmware upgrade key requirements
Triggers new functionality, optimization, bug
correction
Meter data, configuration, metrology must remain
unaffected
Download only to selected meters (enable /
disable)
Download by broadcast, complete individually
Validation success, or discard
Activation on request or automatically at
pre-set time
All events must be logged
40
COSEM solution Image transfer class

• New interface class Image transfer manages
  image transfer process
• New script allows auto activation
• Events logged in Disconnector event log

41
Status / fraud monitoring key requirements
Classify events by their kind HW, SW, power,
fraud
Capture events in event logs, with snapshot if
needed
Maintain status words
Maintain error registers
Allow raising alarms (filtered)
42
Status / fraud monitoring COSEM solution
Project specific status table 1 .. 2 3. 255
Fixed or flexible mapping
Capture selected events in a bit-string

• Capture code of last event by kind
• hardware
• firmware
• power
• tamper
• access.

Event logs Date_time Event code Status Snapshot
Capture selected and filtered events in a
bit-string, to raise an alarm
43
DLMS/COSEM for gas metering

• Participants major industrial associations,
  utilities and manufacturers Germany, France,
  Italy, Netherlands, UK
• Result new OBIS codes to support smart gas
  meters (going far beyond EN 13757-1)
• volume conversion, mass metering
• gas composition, energy calculation
• tariffs (TOU)
• flow rate
• process values
• profiles, minima / maxima
• Elaboration for companion standard for Italy
  started Feb. 2009

44
Summary COSEM model properties

• Application / Data model provides external view
  of the device
• Metering domain specific objects Register,
  Demand register, Profile, Clock, Schedule,
  Register activation...
• OBIS identification system
• Gives a name to each application data
• Rich set of standard objects
• Extensible
• new versions of interface classes
• new interface classes
• manufacturer specific classes, attributes and
  methods allowed
• for standard features, manufacturer specific
  hacks are not allowed
• changing the model does not affect the protocol

Flexible, supports innovation and competition,
future proof