FUNCTIONAL REQUIREMENTS AND TECHNICAL SPECIFICATIONS OF AMI/MDM SYSTEM

(1)

Updated by Deepview

FUNCTIONAL REQUIREMENTS AND

TECHNICAL SPECIFICATIONS OF

AMI/MDM SYSTEM

Version 3.0 April 2014

(2)

TABLE OF CONTENTS

ABBREVIATIONS ... 9

APPLIED STANDARDS ... 10

FUNCTIONAL REQUIREMENTS AND TECHNICAL SPECIFICATIONS OF SYSTEM ARCHITECTURE12 1. HIGH LEVEL ARCHITECTURE ... 13

FUNCTIONAL REQUIREMENTS AND TECHNICAL SPECIFICATIONS OF AMI SYSTEM ... 17

1. FUNCTIONAL REQUIREMENTS FOR AMM CENTRE ... 18

1.1. DESCRIPTION AND GENERAL REQUIREMENTS FOR AMM CENTRE IN AMI CONTEXT .. 18

2. AMM CENTRE FUNCTIONS ... 19

2.1 ADMINISTRATION FUNCTIONS ... 19

2.2 AMM CENTRE DATA COLLECTION/READING AND MEMORISING FUNCTIONS ... 23

2.3 REPORTING FUNCTIONS OF AMM CENTRE ... 24

2.4 DATA AND INFORMATION EXCHANGE FUNCTIONS WITH MDM SYSTEM AND OTHER ISS OF ELECTRIC UTILITY ... 26

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR LOW VOLTAGE CONCENTRATOR ... 28

1. TECHNICAL CHARACTERISTICS OF LOW VOLTAGE CONCENTRATOR ... 29

1.1. SUPPLY: ... 29

1.2. MOUNTING:... 29

1.3. OPERATION TEMPERATURE RANGE: ... 29

1.4. MAXIMUM OPERATION HUMIDITY: ... 29

1.5. ANTICIPATED OPERATION LIFE: ... 29

1.6. MAXIMUM HOUSING DIMENSIONS (WХLХH): ... 29

1.7. NUMBER OF SUPPORTED METERS (CAPACITY): ... 29

1.8. STORAGE CAPACITY: ... 29

1.9. COMMUNICATION PORTS (MINIMUM): ... 29

1.10. OTHER PORTS (OPTIONAL): ... 29

1.11. HARDWARE MONITORING: ... 30

1.12. REAL TIME CLOCK ... 30

1.13. PROTECTION AGAINST DUST AND WATER: ... 30

1.14. OPERATING SYSTEM: ... 30

2. CONCENTRATOR ROLE AND FUNCTIONS ... 30

2.1. CONCENTRATOR ROLE ... 30

(3)

Page 3 of 192

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR AMM

GATEWAY/ROUTER ... 39

1. TECHNICAL CHARACTERISTICS AMM GATEWAY/ROUTER ... 40

1.1. SUPPLY: ... 40

1.2. MOUNTING:... 40

1.3. OPERATION TEMPERATURE RANGE: ... 40

1.4. MAXIMUM OPERATION HUMIDITY: ... 40

1.5. ANTICIPATED OPERATION LIFE: ... 40

1.6. MAXIMUM HOUSING DIMENSIONS (WХLХH): ... 40

1.7. NUMBER OF SUPPORTED METERS (CAPACITY): ... 40

1.8. COMMUNICATION PORTS (MINIMUM): ... 40

1.9. OTHER PORTS (OPTIONAL): ... 40

1.10. HARDWARE MONITORING: ... 40

1.11. REAL TIME CLOCK ... 41

1.12. PROTECTION AGAINST DUST AND WATER: ... 41

2. AMM GATEWAY/ROUTER ROLE AND FUNCTIONS ... 41

2.1. GATEWAY/ROUTER ROLE ... 41

2.2. GATEWAY/ROUTER FUNCTIONS ... 42

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR CELLULAR MODEM . 44 1 BASIC CHARACTERISTICS OF CELLULAR MODEM ... 45

1.1. GPRS MOBILE STATION CLASS: ... 45

1.2. GPRS MULTI-SLOT CLASS: ... 45

1.3. DUAL BAND GSM/GPRS:... 45

1.4. OPERATING TEMPERATURE RANGE: ... 45

1.5. EXTERNAL ANTENNA CONNECTION: ... 45

2 REQUIREMENTS FOR CELLULAR MODEM ... 45

2.1 GENERAL REQUIREMENTS FOR CELLULAR MODEM ... 45

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR PLC MODEM ... 47

1. GENERAL REQUIREMENTS FOR PLC MODEM ... 48

1.1 SPECIAL REQUIREMENTS OF PLC MODEM FOR THE CONCENTRATOR/ROUTER ... 48

1.2 SPECIAL REQUIREMENTS OF PLC MODEM FOR METERS ... 48

2. BASIC TECHNICAL CHARACTERISTICS OF OFDM PLC MODEM ... 50

2.1 GENERAL REQUIREMENTS FOR OFDM PLC COMMUNICATION ... 50

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR RADIO MODEM ... 51

(4)

1.1 SPECIAL REQUIREMENTS OF RADIO MODEM FOR THE CONCENTRATOR/ROUTER ... 52

1.2 SPECIAL REQUIREMENTS OF A RADIO MODEM FOR METERS ... 52

2. BASIC TECHNICAL CHARACTERISTICS OF A RADIO MODEM ... 54

FUNCTIONAL REQUIREMENTS FOR SWITCHING MODULE (BISTABLE SWITCH) ... 55

1. SWITCHING MODULE (BISTABLE SWITCH) ... 56

1.1. INTEGRATED SWITCHING MODULE (BISTABLE SWITCH) ... 56

1.2. EXTERNAL SWITCHING MODULE (BISTABLE SWITCH) ... 56

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR SINGLE-PHASE AND THREE-PHASE METERS OF ACTIVE ELECTRICAL ENERGY ... 57

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR SINGLE-PHASE METERS OF ACTIVE ELECTRICAL ENERGY ... 58

SINGLE-PHASE METER WITH CONSUMPTION MANAGEMENT FUNCTION ... 59

1. TECHNICAL CHARACTERISTICS OF SINGLE-PHASE ACTIVE ELECTRICITY METER FOR DIRECT CONNECTION (SINGLE-PHASE METER WITH CONSUMPTION MANAGEMENT FUNCTION) ... 60

1.1. GENERAL TECHNICAL CHARACTERISTICS ... 60

1.2 OTHER TECHNICAL CHARACTERISTICS ... 63

2. METER FUNCTIONS ... 65

2.1. METERING, REGISTRATION AND DISPLAY FUNCTIONS ... 65

2.2. ADDITIONAL FUNCTIONS ... 68

2.3. CONSUMPTION AND ELECTRICAL DEVICES MANAGEMENT ... 70

2.4. ELECTRICITY METERING QUALITY ... 72

2.5. METER FIRMWARE UPGRADE ... 73

2.6. SELF-CHECK ... 73

2.7. MULTI-UTILITY METERING ... 73

2.8. DATA SECURITY ... 74

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR THREE-PHASE ELECTRICITY METERS OF ACTIVE ELECTRICAL ENERGY ... 75

THREE-PHASE METER WITH CONSUMPTION MANAGEMENT FUNCTION ... 76

1. TECHNICAL CHARACTERISTICS OF THREE-PHASE ACTIVE ELECTRICITY METER FOR DIRECT CONNECTION (THREE-PHASE METER WITH CONSUMPTION MANAGEMENT FUNCTION) ... 77

1.2 OTHER TECHNICAL CHARACTERISTICS ... 80

(5)

Page 5 of 192

2.3. CONSUMPTION AND ELECTRICAL DEVICES MANAGEMENT ... 88

2.4. ELECTRICITY METERING QUALITY ... 90

2.5. METER FIRMWARE UPGRADE ... 90

2.6. SELF-CHECK ... 91

2.7. MULTI-UTILITY METERING ... 91

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR THREE-PHASE ELECTRICITY METERS OF ACTIVE AND REACTIVE ELECTRICAL ENERGY ... 93

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR THREE-PHASE ELECTRICITY METERS OF ACTIVE AND REACTIVE ELECTRICAL ENERGY FOR DIRECT CONNECTION ... 94

DIRECT C/I METER WITHOUT THE POSSIBILITY OF DEMAND MANAGEMENT ... 94

1. TECHNICAL CHARACTERISTICS OF METERS OF ACTIVE AND REACTIVE ELECTRICITY FOR DIRECT CONNECTION (THREE-PHASE DIRECT C/I METER WITHOUT CONSUMPTION MANAGEMENT) ... 95

1.2. OTHER TECHNICAL CHARACTERISTICS ... 99

2.3. CONTROL OUTPUT ... 106

2.4. ELECTRICITY QUALITY METERING ... 106

2.5. SELF-CHECK ... 106

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR THREE-PHASE METERS OF ACTIVE AND REACTIVE ELECTRICITY FOR DIRECT CONNECTION ... 108

DIRECT C/I METER WITH CONSUMPTION MANAGEMENT ... 108

1. TECHNICAL CHARACTERISTICS OF THREE-PHASE METER OF ACTIVE AND REACTIVE ELECTRICITY FOR DIRECT CONNECTION (THREE-PHASE DIRECT C/I METER WITH CONSUMPTION MANAGEMENT) ... 109

(6)

2.5. SELF-CHECK ... 122

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR THREE-PHASE METERS OF ACTIVE AND REACTIVE ELECTRICITY ... 124

CT CONNECTED C/I METER ... 124

1. TECHNICAL CHARACTERISTICS FOR THREE-PHASE METERS OF ACTIVE AND REACTIVE ELECTRICITY FOR SEMI-INDIRECT CONNECTION (THREE-PHASE CT CONNECTED C/I METER) ... 125

2.3. CONTROL OUTPUT ... 135

2.5. SELF-CHECK ... 136

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR THREE-PHASE METERS OF ACTIVE AND REACTIVE ELECTRICITY ... 138

1. TECHNICAL CHARACTERISTICS FOR THREE-PHASE METERS OF ACTIVE AND REACTIVE ELECTRICITY FOR INDIRECT CONNECTION (THREE-PHASE CT VT CONNECTED C/I METER) ... 139

2.4. SELF-CHECK ... 151

ADDITIONAL METER FUNCTIONS FOR CONNECTION OF ELECTRICITY GENERATION FACILITIES ... 153

1. ADDITIONAL METER FUNCTIONS FOR CONNECTION OF ELECTRICITY GENERATION FACILITIES ... 154

1.1. MANDATORY SCOPE OF EXTENDED FUNCTIONS FOR METERS WITH DIRECT CONNECTION ... 154

(7)

Page 7 of 192

1.2. MANDATORY SCOPE OF EXTENDED FUNCTIONS FOR CT METERS ... 155

1.3. MANDATORY SCOPE OF EXTENDED FUNCTIONS FOR CT VT METERS ... 155

2. OPTIONAL SCOPE OF ADDITIONAL FUNCTIONS ... 155

2.1. SEALING ... 155

2.2. PROFILES OF METERED AND REGISTERED VALUES ... 155

2.3. MAXIMUM APPARENT POWER ... 156

2.4. MINIMUM POWER FACTOR ... 156

2.5. DATA STORAGE PERIOD ... 156

3. OPTIONAL SCOPE OF ADDITIONAL FUNCTIONS FOR CT METERS ... 156

3.1. RATED ACCURACY CLASS ... 156

FUNCTIONAL REQUIREMENTS OF METER DATA MANAGEMENT AND REPOSITORY SYSTEM (MDM/R) ... 157

1. METER DATA MANAGEMENT AND REPOSITORY SYSTEM ... 158

1.1. ABBREVIATIONS ... 158

1.2. APPLIED STANDARDS ... 161

1.3. PURPOSE ... 162

1.4. SCOPE ... 162

1.5. MDM/R SYSTEM OVERVIEW ... 162

1.6. GENERAL FUNCTIONAL REQUIREMENTS ... 163

2. DETAILED FUNCTIONAL REQUIREMENTS ... 164

2.1. OVERVIEW OF FUNCTIONALITIES ... 165

2.2. REGULATORY AGENCY REQUIREMENTS ... 165

2.3. UNIQUE POINT OF DELIVERY (POD) ID NUMBER ... 166

2.4. DATA ENTRY INTO MDM/R SYSTEM ... 166

2.5. TIME FLOW OF DATA EXCHANGE ... 170

2.6. DATA SUBMISSION BY MDM/R SYSTEM ... 172

2.7. DATA MANAGEMENT ... 175

2.8. FUNCTIONAL REQUIREMENTS IN TERMS OF DATA STORAGE ... 178

FUNCTIONAL REQUIREMENTS - PRINCIPLES OF END-TO-END SECURITY ... 183

FUNCTIONAL REQUIREMENTS - PRINCIPLES OF INTEGRATION ... 188

FUNCTIONAL REQUIREMENTS - GENERAL ... 190

(8)

(9)

Page 9 of 192

ABBREVIATIONS

Table 1 – Overview of used abbreviations

AMCD Advanced Metering Communication Device

AMR Automated Meter Reading

AMRC Advanced Metering Regional Collector

AMI Advanced Metering Infrastructure

AMM Automated/Advanced Metering Management

AMCC Advanced Metering Control Computer

CET Central European Time

CIM Common Information Model

CIS Customer Information System

COSEM Companion Specification for Energy Metering

DLMS Device Language Message Specification

IEC International Electrotechnical Commission

MDM/R Meter Data Management and Repository

OMS Outage Management System

RF Radio Frequency

CT Current transformer

VT Voltage transformer

(10)

APPLIED STANDARDS

The following standards were used in the course of development of this document:

IEC 60529 Degrees of protection provided by enclosures (IP Code)

IEC 60050-300

International Electrotechnical Vocabulary – Electrical and electronic measurements and measuring instruments

Part 311: General terms relating to measurements

Part 312: General terms relating to electrical measurements Part 313: Types of electrical measuring instruments

Part 314: Specific terms according to the type of instrument

IEC 61334-5-1 Distribution automation using distribution line carrier systems - Part 5-1: Lower

layer profiles - The spread frequency shift keying (S-FSK) profile IEC 61968-1

Application integration at electric utilities – System interfaces for distribution management

Part 1: Interface architecture and general requirements IEC 61968-2

Part 2: Glossary IEC 61968-3

Part 3: Interface for network operations IEC 61968-9

Part 9: Interface for meter reading and control IEC 61968-11

Part 11:Common Information Model (CIM) Extensions for Distribution

IEC 61970-301 Energy management system application program interface (EMS-API)

Part 301: Common information model (CIM) base

IEC 62051:1999 Electricity metering – Glossary of terms

IEC 62051-1

Electricity metering – Data exchange for meter reading, tariff and load control Part 1: Terms related to data exchange with metering equipment using DLMS/COSEM

IEC 62052-11 Electricity metering equipment (AC) - General requirements, tests and test

conditions - Part 11: Metering equipment.

IEC 62053-31 Electricity metering equipment (a.c.) - Particular requirements - Part 31: Pulse _{output devices for electromechanical and electronic meters (two wires only).}

IEC 62053-21 Electricity metering equipment (a.c.) - Particular requirements -Static meters for

active energy (classes 1 and 2)

IEC 62053-22 Electricity metering equipment (a.c.) - Particular requirements -Static meters for

active energy (classes 0.2S and 0.5S)

IEC 62053-52 Electricity metering equipment (AC) - Particular requirements - Part 52: Symbols.

IEC 62054-11 Electricity metering (a.c.) - Tariff and load control - Part 11: Particular requirements

(11)

Page 11 of 192

IEC 62054-21 Electricity metering (a.c.) - Tariff and load control - Part 21: Particular requirements

for time switches. IEC 62055-31

Electricity metering – Payment systems

Part 31: Particular requirements – Static payment meters for active energy (classes 1 and 2)

IEC 62056-21 Electricity metering - Data exchange for meter reading, tariff and load control -

Part 21: Direct local data exchange. IEC 62056-42

Electricity metering - Data exchange for meter reading, tariff and load control - Part 42: Physical layer services and procedures for connection-oriented asynchronous data exchange.

Part 46: Data link layer using HDLC protocol.

Part 47: COSEM transport layers for IPv4 networks.

Part 53: COSEM application layer.

Part 61: Object identification system (OBIS).

Part 62: Interface classes.

EN 13757-2 EN 13757-2 Communication systems for remote reading of meters. Physical and

link layer.

DIN 43857 Watthour meters in moulded insulation case without instrument transformers, up

to 60 A rated maximum current; principal dimensions for three-phase meters EN 50065-1

CENELEC EN 50065-1 Signalling on Low-Voltage Electrical Installations in the Frequency Range 3 kHz to 148,5 kHz Part 1: General Requirements, Frequency Bands and Electromagnetic Disturbances

EN 50470-1 EN 50470-1 Electricity metering equipment (a.c) - General requirements, tests and

test conditions – Metering equipment (class indexes A, B, C)

EN 50470-3 EN 50470-3 Electricity metering equipment (a.c) - Particular requirements, Static

meters for active energy (class indexes A, B, C)

VDN Recommendation of German Electric Industry Association

MID 2004/22/EC Directive 2004/22/EC of the European Parliament and of the Council of 31 March

(12)

FUNCTIONAL REQUIREMENTS AND TECHNICAL SPECIFICATIONS OF

SYSTEM ARCHITECTURE

(13)

Page 13 of 192

1. HIGH LEVEL ARCHITECTURE

This chapter describes high level architecture of the Smart Metering system in a wider context of Smart Grid activities, home automation etc.

In general MDM and AMM systems have to be integrated in the context of EPS application infrastructure (EPS legacy systems, DSOs legacy systems and).

Regular data exchange regarding metered consumption and related information will be provided to relevant third parties (e.g. suppliers, market operator, market regulator).

The smart metering infrastructure will enable EPS to measure consumption of:

 - MV/LV substations;

 - MV commercial and industrial customers;

 - LV households and commercial and industrial customers.

Smart metering context

Smart metering provides two-way information flows between the smart meters and the designated market participants. Smart metering systems may exist in the context of larger smart grid infrastructures and may co-exist with home automation systems.

In the context of this document we will focus mainly on the elements of Smart metering systems – technologies and architectures which enable modern data acquisition and processing.

Figure 1 - Intersection of Smart Metering, Smart Grid and Home Automation systems

As it is shown above, smart metering applications may overlap with applications of smart grid systems and building / home automation systems.

Indeed, the functional scope of smart metering can vary from just automating the meter value collection process, to full automation and surveillance of the low voltage network.

Particularly in relation to electricity metering, there is the important additional objective of facilitating smart grid applications, notably through the incorporation of distributed generation.

(14)

Smart metering architecture

AMI is a system of smart meters, data concentrators, two-way communications networks, and data management systems implemented to enable metering and other information exchange between utilities and their customers.

High level architecture of Smart Metering system and its connections with ICT environment of EPS, grid operator and third parties is shown below.

Figure 2 – High level architecture

(15)

Page 15 of 192

The smart metering infrastructure will enable EPS to measure consumption of:

 MV/LV substations;

 MV commercial and industrial customers;

 LV households and commercial and industrial customers.

Different types of communications have to be assumed for these groups:

Smart Meter segment PLC RF GPRS/LTE Ethernet

Substation balancing meters

MV industrial and commercial customers

LV households and industrial and commercial customers

Table 1 - Smart meter segments and types of communications to be used

Smart meters communicate using Power Line Communications (PLC) and Radio Frequency (RF) with Field Area Concentrators /Routers in Neighbour Area Network (NAN). This network is specific because it is limited to certain geographic area (usually on the level of sub-station). Field Area Concentrators / Routers are through WAN connected with AMI (Advanced Meter Infrastructure) application center(s) which consists of:

 Advanced metering infrastructure Head-End (AMI Head End),

 This systems controls collection of metring data, manage two-way communication with meters, and monitors and manage communication network (Network Management System – NMS),

 Meter Data Management/ (MDM) and Data Center,

 Meter Data Management process data collected from the meters and is also repository of data. Amount of these data is potentially extremely big, so Data Centre is build for purpose of keeping this data.

Main connections of AMI are:

 to other technical subsystems – SCADA, Outage management systems (OMS), Distribution management systems (DMS),

 to business support systems: billing, CRM, asset management,

 to third party systems: market operators, market regulator, suppliers, etc.

Security aspects (authorization and authentication of all elements of the system, keys, certificates, cryptography, access control, etc) can be handled by separate security sub-system or security system for complete ICT infrastructure.

ESB (Enterprise Service Bus) is preferable way to connect all applications of grid operator. In general every new system which is to be built shall be integrated on related EPS legacy systems via ESB layer. ESB doesn’t handle processes within AMM but exposes connectors on and among all related. New processes realized in the new AMM system are integrated through ESB.

(16)

AMI should be monitored as a whole. It means that also status of communication technology or for example service level of telecommunication networks are also gathered and evaluated. Two main components of Smart Metetering system are decriebed in this document:

 Meter Data Management (MDM);

 Advanced Metering Infrastructure System (AMI/AMM).

Requirements concerning the following closely related topics are furder described in grater detail in separate sections:

 Integration,

(17)

Page 17 of 192

FUNCTIONAL REQUIREMENTS AND TECHNICAL SPECIFICATIONS OF

AMI SYSTEM

(18)

1. FUNCTIONAL REQUIREMENTS FOR AMM CENTRE

1.1. DESCRIPTION AND GENERAL REQUIREMENTS FOR AMM CENTRE IN AMI CONTEXT

AMM centre is based on AMM (Automated Meter Management) concept implying remote reading and simultaneous efficient supervision and management of other AMI components (Advanced Metering Infrastructure) (hereinafter referred to as: ’the System’), high data processing speed in multiuser environment (Client/Server architecture), connection with other information systems (Billing system, Customer Information System, etc.) and data transfer into MDM/R (Meter Data Management & Repository) (hereinafter referred to as: ’MDM’).

Depending on the size of demand area of individual subsidiaries, the scope of AMM system will be in the range from 30.000 to 1.000.000 units (meters). The system is sufficiently flexible to allow easy upgrade and thereby cover the changes within PE EPS, whether due to the change of the number of customers, or due to the changes in the organization of subsidiaries, i.e. PE EPS.

Data are stored into the data base of standard and licensed system for relation data bases management. Applied data model has to enable simple integration with other information systems and subsystems implemented in subsidiaries for electricity distribution of PE EPS (electric utility). AMM Centre data model needs to be realised and delivered in a standard format of modelling programmes with descriptive names and/or clear description of all data base objects (entities, attributes, views, relations, procedures, etc.).

AMM Centre is based on a corresponding computer and telecommunication infrastructure enabling its continual and efficient operation - (existing „fail safe“ systems provide required redundancy, disturbance-free operation in case of power supply outage and like). Servers (AMCC - Advance Metering Control Computer) and clients of AMM Centre have a corresponding system and application software installed enabling execution of all specific functions. AMM Centre needs to function under the conditions of existing computer and telecommunication organisation of electric utility. It is desirable that administrator and client GUI (Graphical User Interface) is realised on the latest computer platform not requiring special software installation.

Functional requirements to be specified in this document imply that AMM Centre will be realised to enable functionality indicated in technical specification of other System components related to AMM Centre.

Communication between AMM Centres and other System components is executed via WAN. Every electric utility will according to its current state of telecommunication and computer infrastructure define redundant communication routes with System components.

Security in AMM Centre is part of overall security system, e.g. access to data is strictly protected by role based security, devices (meters, data concentrator/ routers) are check for validity and encryption is mandatory for storing data and any type of communication.

Data export into files option is mandatory (min. ASCII, EXCEL and XML type files). More detailed file formats would be additionally determined based on the needs of electric utility. Also, standardized interfaces (see functional request for integration in this document) will be used for advanced information exchange.

AMM system should support data concentrators and/or meter routers/gateways (see respective chapters in the rest of this document). In this chapter we will make alternatives of

(19)

Page 19 of 192

requested functionalities for both ways. Alternatives will be marked with DC and RG marks. Alternative text will be in italic.

Functions of AMM Centre in terms of data reading and configuration should be executed on laptops connected directly to the concentrator and/or router/gateway and the meter.

In addition to this, functions related to meter data reading and configuration should also be executed on handhelds.

2. AMM CENTRE FUNCTIONS

AMM Centre functions may be divided into the following:

 Administration functions.

 Data reading/collection and archiving functions.

 Reporting functions.

 Data and information exchange functions with MDM system and other information systems and subsystems of electric utility.

2.1 ADMINISTRATION FUNCTIONS

System administration is executed via multiuser application for the purpose of:

 System components administration

 AMM Centre administration

2.1.1 SYSTEM COMPONENTS ADMINISTRATION

Administration of System components is realised via remote management/parameterisation in two ways. First operation mode is when desired parameters are changed with corresponding administrative rights in direct communication with the meter or DC: concentrator.

The second operation mode is when automated management/parameterisation is performed over a group of system elements. In AMM Centre, commands/parameters are set for management/parameterisation of System components, while afterwards superordinate System component individually realises the task.

DC: For example, in case when all meters within one substation region are in question, AMM

Centre sets necessary parameters for the authorised concentrator, while the task is performed by the concentrator without direct connection with AMM Centre.

RG: In the case of router/gateway, automation scheduling of tasks are done by centralised

scheduler.

According to the number of managed i.e. parameterised System elements we have:

 Management/parameterisation of an individual element.

(20)

According to the manner of execution, management/parameterisation may be:

 Automated management/parameterisation according to sequence.

 Manual management/parameterisation on request.

Administration of System components is realised to make possible any combination of the above-indicated divisions according to the number of elements or the manner of management/parameterisation execution.

Administration of System components will after its every action generate a corresponding report available to the system administrator, containing the success percentage of the set action and the list of elements from which there was no confirmation of management/parameterisation execution.

Administration of System components enables:

 Meter administration.

 Administration of communication devices.

 DC: Concentrator administration.

 Monitoring of System components replacement history.

 Monitoring of command and parameter history of System components.

 Monitoring of the communication network

2.1.2 METER ADMINISTRATION

Meter administration enables the following:

 Meter data entry and update.

 Customer data entry and update.

 Meter parameters entry and update.

 Entry, update and monitoring of data on installation and replacement of meters.

 Introducing previously automatically detected meters into the system.

 Real time clock synchronisation.

 Daylight saving time changes.

 Tariff programme change.

 Change of value display period on meter display.

 Change of sequence and selection of registers for display on meter display.

 Activation of function keys on the meter (e.g. conditional reconnection).

 Change of electric power integration period.

 Change of phase presence detection threshold.

 Change of approved mean power limit.

(21)

Page 21 of 192

 Remote customer disconnection/connection.

 Controllable output management.

 Change of reconnection regime (automatic or conditional).

 Update of ‘penalty time’ parameters.

 Change of registers within profile framework.

 Change of profile periods.

 Change of voltage thresholds related to electricity quality.

 Meter software change (single-phase and three-phase meters).

 Credit change for Pre-Paid meters.

 Enabling of message sending to the customer (HAN)

AMM Centre will execute automatic generation of a unique point of delivery identifier (contains identification attribute of the meter) – POD (Point of Delivery).

Meter administration should enable simple concurrent POD connection with identification attributes of entities (customer data, network resources data, etc) from other information systems and subsystems of ELECTRIC UTILITY via ‘drag-and-drop’ procedure.

In addition to this, meter administration enables meter location into hierarchically organised logical wholes (customer categories, substation regions, geographical – administrative areas, etc), with possibility of simultaneous location into the higher number of hierarchically equal logical wholes. It is necessary to provide simple relocation of one meter/groups of meters from one logical whole to another (drag-and-drop).

2.1.3 CONCENTRATOR ADMINISTRATION

Concentrator administration enables the following:

 Concentrator data entry and update.

 Concentrator parameters entry and update.

 Entry, update and monitoring of data on installation and replacement of concentrators.

 Review, organisation and change of ancillary meters.

 Review and synchronisation of reading programmes/sequence.

 Review and synchronisation of programmes/sequence of management/parameterisation.

 Review and synchronisation of programme/sequence execution priorities.

 Review of communication PLC route (if not set automatically).

 Review and change of concentrator reporting time and frequency parameters.

 Review and change of event parameters for emergency concentrator reporting.

 Review and change of communication parameters of concentrator.

(22)

 Change of concentrator management software.

 Review of corresponding concentrator records on the change of parameters and concentrator adjustment.

 Setting of security parameters (keys,etc…) of concentrator.

2.1.4 ADMINISTRATION OF COMMUNICATION CELLLULAR MODEMS

 Entry, update and monitoring of data on installation and replacement of router/gateway.

 Real time clock synchronisation

 Review and change of communication parameters of gateway/router.

 Change of gateway/router management software.

 Setting of security parameters (keys, etc…) of gateway/router.

2.1.5 ADMINISTRATION OF COMMUNICATION CELULAR MODEMS

Administration of communication celular modems enables the change of communication parameters.

2.1.6 ADMINISTRATION OF AMM CENTRE  Defining of roles and users/user groups.

 Access control to System components and AMM Centre.

 Administration of reporting functions of AMM Centre.

 Regular automatic backup of all data at the desired time.

Defining of user/user group rights needs to be defined in relation to:

 Entry and update of data and parameters.

 Defining of possibilities for command execution.

 Hierarchically organised logical wholes.

Optionally, AMM Centre administration also ensures the following:

 Administration of software components (versions of application software and firmware) and all the settings of AMI system, i.e. its components.

 Automatic monitoring of parameters and performances of AMM Centre operation, analysis and generation of the reports on the system operation, as well as informing the system operator on the observed problems.

 Management (generating, taking over, archiving, monitoring and controlling the access) of the documents required for proper system operation.

(23)

Page 23 of 192

2.2 AMM CENTRE DATA COLLECTION/READING AND MEMORISING FUNCTIONS

Data collection/reading and memorising function collects data automatically in an efficient and reliable manner from the DC: concentrator/meter and memorises (archive) them in a corresponding data base or performs instant reading of the concentrator/meter upon user request.

Reading function is realized through corresponding reading programmes/sequences. According to the amount of concentrator/meters being read we differentiate:

 Reading of individual DC: concentrator/meter.

 Reading of the group of DC: concentrator /meters According to the reading frequency we differentiate:

 Automated reading according to the sequence

 Reading on request

 Periodical reading on request

 Special reading on request

Data collected automatically according to the sequence set in advance (no difference is made whether these data are collected from the concentrator or via direct communication with the meter) include:

 Daily register values*.

 Meter states*.

 Electricity quality log.

 Event log.

 Load profile.

 Hourly register values *.

 State of monthly accounting registers.

 Time and date.

Data collected from the meter on request (via DC: concentrators or direct communication with the meter) include the following, in addition to data collected automatically:

 Effective voltage values per phases at the moment of reading.

 Effective current values per phases at the moment of reading.

 Current power – (load power at the moment of reading)*.

 Tariff programme.

 Integration period for 15-minute maximum power.

 Consumption management parameters.

 Parameters for voltage thresholds within electricity quality log.

(24)

 Parameters for registers within profiles.

 Parameters related to the presentation on meter display.

 Archive states of accounting registers.

 Current state of bi-stabile switch.

 Meter software version.

 Factory number and type of meter.

* The data is transmitted together with the time stamp of data creation

Data read according to the sequence from the DC: concentrator RG: router/gateway (in addition to data obtained by meter reading) include:

 Statistics of communication.

 Emergency and regular reports.

DC: Data read from the concentrator upon the request include:

 Concentrator data archive.  Reading programmes/sequences.

 Management/parameterisation programmes/sequences.  Programme/sequence execution priorities.

 Communication PLC routes.

 Concentrator response time and frequency parameters.  Communication parameters of the concentrator.

 Current date and time.

 Other concentrator parameters.  Concentrator software version.

 Records on concentrator parameter changes and adjustments.

Data collection/reading function offers reading control with the display of percentage of successfully read meters/DC: concentrators in every reading.

2.3 REPORTING FUNCTIONS OF AMM CENTRE

Reporting functions are divided in:

 Reports with analysis of statuses and alarms.

 Reports on electricity quality.

(25)

Page 25 of 192

 Communication reports.

 Control reports.

 Reports generated by the concentrator.

Reports with analysis of statuses and alarms

This type of reporting functions processes alarms and statuses of meters/concentrators, event logs, with the making of corresponding reports after finding corresponding alarms, statuses and events.

These functions would minimally process events and alarms related to the disruption of meter integrity (e.g. opening of termination cover), as well as attempt or disruption of data integrity in meters or concentrators themselves (e.g. meter reprogramming attempt).

Result of such reports should be the daily, i.e. periodical report on the state clearly showing all alarms, statuses and events and on which meters, representing the basis for further action on these meters.

Reports on electricity quality

This reporting function would execute analysis of voltage circumstances on meters themselves since there are corresponding records in the electricity quality log recording voltage drop/overvoltage below/above defined voltage thresholds and supply interruptions. In this way the function would indicate poor voltage circumstances with one or a group of customers and it would represent the reason for the crews to go out into the field.

Reports related to parameterisation and management

In addition to the reports which were the consequence of parameterisation/management over System elements, it is also necessary to anticipate a number of reports.

Due to great significance, there also needs to be a report on disconnected customers, i.e. the report on the management of bistable switch which needs to contain the date when the action was set and when action execution confirmation arrived.

Communication reports

Successfulness statistics of communication between system elements represents a special whole within the reporting functions.

Control reports

These reports would indicate real time detuning or disagreement in tariff programme. Results of these reports represent the basis for the setting of automatic parameterisation over elements where detuning has been noticed.

(26)

DC: Reports generated by the concentrator

Reporting functions also support the presentation of reports the concentrator sends upon emergency reporting request to AMM Centre.

General requirements

It goes without saying that reports may be sorted according to all parameters. Moreover, search function needs to have the possibility of search according to all System element attributes.

Form of registered energy and power report is dynamically/automatically adapted to the current tariff programme without the need for additional software intervention.

Print/Print Preview option is mandatory with every report automatically generated in the form of PDF file.

This list of reports is not final since it is not possible at this moment to anticipate all necessary types of reports. This is a minimum set which surely needs to exist and which will in time evolve into a final and detailed list of reporting functions based on electric utility needs. Generator of ad hoc reports should be realised within AMM Centre.

2.4 DATA AND INFORMATION EXCHANGE FUNCTIONS WITH MDM SYSTEM AND OTHER ISS OF ELECTRIC UTILITY

This function is realized to enable most efficiently the connection and exchange of data from MDM system. This function will also provide the connection towards other information subsystems.

By the use of existing computer and telecommunications infrastructure within subsidiaries, required safety of communication route/routes between AMM Centre and MDM System is ensured.

2.4.1 DATA TRANSFER INTO MDM SYSTEM

AMM Centre should support push and pull procedure of data submission on metered consumption and other data to MDM system. Data on metered consumption to be transferred to MDM system are as follows:

 Data on metered consumption for households, where there are no requirements in terms of requested load on hourly level; data on consumption need to be transferred in the end of the daily accounting interval.

 Data on metered consumption for industrial customers, where there are requirements in terms of requested load; data on consumption need to be transferred either as 15 or 60-minute data in the end of the daily accounting interval.

(27)

Page 27 of 192

All data transferred via this data transfer method need to be related to the same calendar day. Finally, transferred parameters should minimally have identified information in their heading reporting to MDM system the priority during data upload for more subordinated devices simultaneous data transfer is requested.

Data transfer priorities

MDM system will preserve all versions of meter data received from the control AMM Centre. For the purpose adaptation to enable MDM system to execute urgent data processing in accordance with critical situations, when several requests need to be processed at the same moment, it needs to have data processing procedure according to priority. MDM system should support processing priority determination procedure in relation to data to be submitted by AMM Centre. Priority should be based on time and date of meter data occurrence.

AMM Centre should be able to enable the sending of all data on metered consumption every day for the previous daily reading period. In order to perform data transfer successfully, all process clocks on all computers within the subject subsystems should be synchronised.

Confirmation

After all data sent by AMM Centre are received and processed for the purpose of verification by MDM system, MDM system will send a message to AMM Centre for confirmation of successful message receipt or possible problem in the course of transfer.

2.4.2 REPORT SUBMISSION TO MDM SYSTEM BY AMM CENTRE

AMM Centre should submit reports to MDM system defined by this document. MDM system should archive submitted reports.

(28)

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR

LOW VOLTAGE CONCENTRATOR

(29)

Page 29 of 192

1. TECHNICAL CHARACTERISTICS OF LOW VOLTAGE CONCENTRATOR

CONSTRUCTION: Fanless Embedded PC – Concentrator is executed without moving parts, in accordance with standards for industrial computers (resistant to temperature, humidity, dust, vibrations, electromagnetic radiation and other) adapted to operation conditions in substations (SS).

1.1. SUPPLY:

AC: 1х230V or 3х230V, 50Hz, Optional, DC: 24V.

1.2. MOUNTING:

vertical (wall mounted).

1.3. OPERATION TEMPERATURE RANGE:

from -20 c to +55 c.

1.4. MAXIMUM OPERATION HUMIDITY:

90%.

1.5. ANTICIPATED OPERATION LIFE:

10 years.

1.6. MAXIMUM HOUSING DIMENSIONS (WХLХH):

400х400х200 (mm).

1.7. NUMBER OF SUPPORTED METERS (CAPACITY):

1000 meters.

1.8. STORAGE CAPACITY:

Capacity: minimum 4 GB.

1.9. COMMUNICATION PORTS (MINIMUM):

1хLAN 10/100, RJ45.

COMMUNICATION PORTS FOR COMMUNICATION WITH CELLULAR or PLC modem – depending on cellular or PLC modem performance):

 If cellular modem is executed as external device, corresponding communication port for communication with cellular modem;

 If PLC modem is executed as external device, corresponding communication port for communication with PLC modem.

COMMUNICATION PORTS (Optional) - depending on communication module):

 1хUSB (minimum 2.0)

 1хRS-232 (Isolated)

1.10. OTHER PORTS (OPTIONAL):

(30)

1.11. HARDWARE MONITORING:

watchdog timer, optional CPU and housing temperature monitoring.

1.12. REAL TIME CLOCK

1.13. PROTECTION AGAINST DUST AND WATER:

IP 51 or better

1.14. OPERATING SYSTEM:

Embedded OS (ex: Windows XP embedded, Windows CE, Windows Mobile, Linux...)

2. CONCENTRATOR ROLE AND FUNCTIONS

2.1. CONCENTRATOR ROLE

Concentrator is a device executing automatically or on request the functions of meter reading and parameterization and data transfer functions to AMM Centre.

Concentrator has to execute operations defined in programmes/sequences submitted to it remotely (from AMM Centre) or locally (via laptop) independently from AMM Centre and to memorise read data obtained through execution of defined programmes/sequences for a specified time period. The concentrator follows priorities of programmes/sequences during execution of such programmes/sequences. At the request of AMM Centre or under reporting programme/sequence, the concentrator needs to submit memorised data to AMM Centre or deliver the data to laptop on request.

Concentrator also needs to enable immediate communication with individual meters, remotely (from AMM Centre) or locally (via laptop).

Concentrator has communication ports for communication with meters and AMM Centre, as well as communication port for local communication.

CONCENTRATOR

PLC modem GPRS modem

Meters with PLC modem

Management Centre

Handheld terminal for reading and parameterisation (Handheld, Lap-top...)

(31)

Page 31 of 192

Concentrator needs to support operation with DLMS/COSEM protocol along PLC communication with meters.

In parallel with the above-indicated tasks, the concentrator executes initial data processing collected until such moment, not affecting data reading, parameterisation and delivery.

Local access is used during the installation procedure or for the performance of other maintenance activities, for local reading and configuration of the concentrator, as well as when there are communication problems with AMM Centre. Local access between other accesses has to support Remote Desktop approach.

Communication via local access has hierarchical precedence over the remote one.

External devices optionally connected to the concentrator may be used for future smart network functionalities, e.g. control and supervision of substations, where concentrators are usually located.

In addition to the connection of several networks, the concentrator may provide optimization of communication. Optimisation methods include:

 Data compression

 Communication channels engagement time reduction

 Response time optimisation

It is expected that new communication technologies, as well as additional requirements in terms of expansion concentrator functions will emerge during the operation life of the concentrator and the system in general. Concentrator software needs to have upgrade option for future functionalities.

2.2. GENERAL DESCRIPTION OF CONCENTRATOR FUNCTIONS

Concentrator software package has to realise at least the following functions:

 Reading and memorising functions

 Management/parameterisation functions

 Communication functions

 Data processing functions

 Data and access protection functions

 Administration functions

2.2.1. READING AND MEMORISING (ARCHIVING) FUNCTIONS

One of the basic functions of the concentrator is reading of meters located in its

communication network. Reading function is realised through the reading

programme/sequence. We differentiate: 1. According to the purpose of read meters:

 Meters for total metering at the substation

 Public lighting meters

(32)

 Customer meters – Households

 Customer meters – Contractual customers 2. According to the type of read meters:

 Single-phase

 Three-phase

 Direct metering groups.

 Semi-indirect metering groups.

3. According to the amount of read meters:

 Reading of individual meter

 Reading of the group of meters 4. According to reading frequency:

 Automated reading according to sequence

 Reading on request

 Periodical reading on request

 Special reading on request. Data read according to sequence:

 Daily states of registers

 Meter statuses

 Electricity supply quality register

 Event log

 Load profile

 Hourly states of registers

 States of monthly accounting registers

 Time and date.

Data read on request include the following, in addition to all data indicated as read according to sequence:

 Effective voltage values per phases at the moment of reading

 Effective current values per phases at the moment of reading

(33)

Page 33 of 192

 Tariff programme

 Integration period for 15-minute maximum power

 Consumption management parameters

 Parameters for voltage thresholds within electricity quality log

 Parameters for time intervals of profiles

 Parameters for registers within profiles

 Parameters related to presentation of meter display

 Archive states of accounting registers

 Current state of bistable switch

 Meter software version

 Factory number and type of meter

Reading function in the concentrator is realised to enable all reading combinations (through corresponding reading programmes/sequences) indicated above and the ones making sense. Concentrator should have sufficient storage space (storage – point 1.1.9), therefore data storage (archiving) function reliably should store all read data for at least 6 months, except accounting data which need to be stored for 12 months.

2.2.1.1. PROPOSAL FOR AUTOMATED READING ACCORDING TO SEQUENCE

Programmes/sequences related to this type of reading are divided into:

 Daily

 Weekly

 Monthly

Initial daily reading programme/sequence of three-phase meters (households) reads the following:

1. Daily value of meter register (value from 00:00) and meter statuses are read first.

2. When reading from point 1 is finalised, reading of electricity quality logs starts on all meters.

3. When reading from point 2 is finalised, reading of event logs starts on all meters. 4. Hourly data from the meter are read after finalisation of Event Log reading. 5. Load profiles from the meter are read.

Under the current technical solution for PLC communication it can hardly be expected that daily programmes will fully be executed on all meters within one substation region. That is way reading algorithms should be provided enabling 98% realisation of daily reading programme/sequence of points 1, 2 and 3 in accordance with the remaining time for execution of this programme/sequence and priorities for other programmes/sequences.

Initial weekly reading programme/sequence of three-phase meters (households) reads the following:

(34)

1. Real time clock reading from all meters.

Initial monthly reading programme/sequence of three-phase meters (households) reads the following:

2. Reading of monthly accounting data from all meters. Programme/sequence reading priority should be as follows:

If the date on the real time clock is within between the 1st and 3rd day of the month, monthly programme/sequence of reading has absolute priority and it is executed until all monthly accounting data are completed for all meters or other conditions are created for programme interruption. Otherwise, daily reading programme/sequence is executed.

Readings on request have priority over automated programmes/sequences of reading.

2.2.2. MANAGEMENT/PARAMETERISATION FUNCTION

Concentrator should have management/parameterisation function in charge for the change of meter parameters, bistable switch control as well as meter software change (applied only for single-phase and three-phase meters). This Function is realised through the programme/sequence of management/parameterisation. We differentiate:

1. According to the purpose of read meters:

 Meters for total metering at the substation

 Public lighting meters

 Control meters

 Customer meters – Households

 Customer meters – Contractual customers

2. According to the type of managed/parameterised meters:

 Single-phase

 Three-phase

 Direct metering groups.

 Semi-indirect metering groups.

3. According to the amount of managed/parameterised meters:

 Management/parameterisation of individual meter

 Management/parameterisation of the group of meters According to frequency, function may be divided in:

 Management/parameterisation according to sequence

 Management/parameterisation on request The list of parameters:

(35)

Page 35 of 192

 Daylight saving time changes.

 Tariff programme change.

 Change of value presentation period on meter display.

 Change of sequence and selection of registers for presentation on meter display.

 Key roles - conditional reconnection.

 Change of integration period in case of 15-minute power.

 Voltage threshold for phase presence decision.

 Change of maximum power limit.

 Change of bistable switch position. Remote disconnection/connection of the customer.

 Controllable output management.

 Automatic or conditional repeated disconnection

 Penalty time.

 Change of registers within profile framework.

 Change of profile periods.

 Voltage thresholds related to electricity quality.

 Meter software change (only for single-phase and three-phase meters).

 Credit change for Pre-Paid meters.

 Message sending to the customer (HAN)

Management/parameterisation function will generate a corresponding report to be sent to AMM Centre after it’s every action, containing assigned action success percentage and the list of meters from which there is no management/parameterisation execution confirmation. Management/parameterisation function initially has execution priority over automated regular reading function. Setting of priorities is fully configurable.

2.2.3. COMMUNICATION FUNCTION

Concentrator is in communication terms realised as the device communicating with at least two sides: on one side there are electricity meters located in the substation region where the concentrator is also installed, while on the other side it communicates with AMM Centre. The connection via both communication paths shall be bidirectional.

Communication with meters goes on via PLC (Power Line Carrier) communication. Communication with AMM Centre goes on via cellular communication.

2.2.3.1. COMMUNICATION WITH METERS

Concentrator is equipped with corresponding PLC modem enabling communication between the concentrator and the meter.

(36)

PLC modem on the concentrator should meet general requirements from point 1 and 2 of the Technical Requirements for PLC Modem, as well as special requirements from point 2.1.

Communication with meters is realised to make automatic meter detection of newly-installed meters mandatory. It goes without saying that no information should be sent to the concentrator, so that it could be able to execute meter detection procedure.

Communication function with meters needs to support a fully automated repetition procedure and finding of optimal communication path, except in case that this functionality is provided by the protocol itself in the PLC modem.

If the concentrator realizes the repetition function itself, it memorizes communication route (topology) towards every meter in its network and submits this information locally or remotely. It goes without saying that PLC technology has to support operation with repeaters. Every communication module on meters also has to operate as repeater, without any additional device.

Communication function has to offer information on line quality such as signal/noise ratio, attenuation and data loss statistics.

2.2.3.2. COMMUNICATION WITH AMM CENTRE

Concentrator is equipped with the corresponding cellular modem (it also has GSM functionality, due to possible implementation of the system with dynamic addressing of cellular modem) enabling bidirectional communication of the concentrator and AMM Centre.

Cellular modem meets technical characteristics from Technical Requirements for cellular

modem.

Communication with AMM Centre is initiated in several ways:

 According to automatic concentrator response sequence.

 According to emergency request of the concentrator.

 Upon the request from AMM Centre

Sequence of automatic concentrator reporting to AMM Centre is fully configurable, in terms of the number of reports during the day and defining of reporting time.

2.2.4. DATA PROCESSING FUNCTION

Concentrator software, in addition to reading and data sending towards AMM Centre as primary functions, also performs partial processing of collected data. Distributed data processing would be introduced in this manner, as well as partial reduction of pressure on transmission communication path to AMM Centre, and on AMM Centre servers.

Concentrator shall execute initial data processing collected up to that moment, in the manner not affecting data reading, parameterisation and delivery.

Data processing function processes alarms and statuses of meters, electricity supply quality logs, event logs, with the making of corresponding reports after finding corresponding alarms, statuses and events to be sent to AMM Centre upon emergency request of the concentrator. This function should minimally process events and alarms related to the disruption of meter integrity (e.g. opening of termination cover), as well as attempt or disruption of data integrity in the meters themselves (e.g. meter reprogramming attempt, etc).

(37)

Page 37 of 192

This function should also perform analysis of voltage circumstances on meters themselves, since there are corresponding records in electricity delivery quality register recording voltage drops below agreed voltage thresholds and supply interruptions. In this manner, this function would indicate poor voltage circumstances of one or a group of customers and it would serve as the reason to send crews into the field.

The concentrator also automatically informs AMM Centre on the detection of new meters in the subordinate substation region.

2.2.5. DATA AND ACCESS PROTECTION FUNCTION

Access to data and functions of the concentrator has to be protected by authentication and authorisation procedure.

Concentrator should have the possibility of creating access logs, both for local or remote access through communication channels.

Concentrator has to support communication encryption with meters and with AMM Centre. Communication security

The concentrator when communicating with meter must fully support DLMS Security as described in the DLMS/COSEM Green Book, 7th ed., section 9.2 ( layer 7 of OSI model)

In addition, concentrator must encrypt data using Advanced Encryption Standard (AES) at least at one of:

● Layer 2 (IEEE 802.15.4g or IEEE P1901.2) ● Layer 3 (IP Security [IPsec])

In this context, the concentrator must store and manage the keys in a secure way

The concentrator must raise an alarm if a meter's key is changed for more than x time per hour. (x to be defined as changeable parameter)

2.2.6. ADMINISTRATION FUNCTION

Administration function may be done locally or remotely. It minimally has to provide:

 Review and synchronisation of reading programmes/sequences with AMM Centre or a laptop.

 Review and synchronisation of management/parameterisation programmes/sequences with AMM Centre or local laptop.

 Review and change of programmes/sequences execution priorities.

 Review of communication PLC route, if not implemented through PLC protocol itself in PLC modems.

(38)

 Review and change of communication parameters of concentrator.

 Review and change of all other concentrator parameters.

 Change of concentrator management software.

Concentrator needs to have data stored in its memory (in the form of logs) on changes of all of its parameters and settings at least for the last 6 months.

(39)

Page 39 of 192

TECHNICAL CHARACTERISTICS AND FUNCTIONAL REQUIREMENTS FOR

AMM GATEWAY/ROUTER

(40)

1. TECHNICAL CHARACTERISTICS AMM GATEWAY/ROUTER

CONSTRUCTION: AMM gateway/router is implemented without moving parts, in accordance with standards for industrial computers (resistant to temperature, humidity, dust, vibrations, electromagnetic radiation and other) adapted to operation conditions in substations (SS).

1.1. SUPPLY:

AC: 1х230V or 3х230V, 50Hz, Optional, DC: 24V.

1.2. MOUNTING:

vertical (wall mounted).

1.3. OPERATION TEMPERATURE RANGE:

from -20 c to +55 c.

1.4. MAXIMUM OPERATION HUMIDITY:

90%.

1.5. ANTICIPATED OPERATION LIFE:

10 years.

1.6. MAXIMUM HOUSING DIMENSIONS (WХLХH):

400х400х200 (mm).

1.7. NUMBER OF SUPPORTED METERS (CAPACITY):

Min. 1000 meters.

1.8. COMMUNICATION PORTS (MINIMUM):

1хLAN 10/100, RJ45.

COMMUNICATION PORTS/SLOTS FOR COMMUNICATION WITH GPRS or PLC/RF modem – depending on GPRS or PLC modem implementation):

 If GPRS, PLC or RF modem is executed as external device, corresponding communication port for communication with respective modem;

 GPRS, PLC and RF modems can also be implemented as slots in device COMMUNICATION PORTS (Optional) - depending on communication module):

 1хUSB (minimum 2.0)

1.9. OTHER PORTS (OPTIONAL):

1xD-Sub (DB15) VGA

1.10.

HARDWARE MONITORING:

(41)

Page 41 of 192

1.11. REAL TIME CLOCK

1.12.

PROTECTION AGAINST DUST AND WATER:

IP 51 or better

2. AMM GATEWAY/ROUTER ROLE AND FUNCTIONS

2.1. GATEWAY/ROUTER ROLE

Gateway/router is device in AMM and Smart grid networks network that enables end-to-end IP communications in such system. In the case of AMM, this means that each meter is IP addressable and AMM applications directly communicate with meters, without additional functionality in the middle (concentrator) level.

Picture below show this architecture.

Figure 4 - General architecture of IPv6 based SG network

One of the main functions of the gateway/router is to adapt IP packets to PLC and RF environment, which is not ideal for communications. This is done by segmenting/desegmenting IP packets. Set of the protocols is developed to enable standardization of such communication techniques. Picture below shows protocols stack in Smart Grid/AMM environment.

(42)

Figure 5 - Implementation of current IP, SG and SM protocols

Gateway/router covers 6LoWPAN parts of the protocols and implement RPL: IPv6 Routing Protocol for Low power and Lossy Networks. Since gateway/router is intended to be used in Smart Grid networks, IPv6 is preferred protocol, although tunnelling of IPv6 trough IPv4 (for example for GPRS implementations) is also possible.

2.2. GATEWAY/ROUTER FUNCTIONS

There are two main functional areas of functions:

- Routing between RF and PLC devices (meters) and IP network - Security

2.2.1. ROUTING

As previously stated, IPv6 and RPL protocol is used to communicate with PLC or RF based meters.

At least one of requested protocols should be supported by router /gateway: - G3 (PLC OFDM)

- PRIME (PLC OFDM)

- 1902.1 (RF and PLC OFDM)

2.2.2. SECURITY

Security is of crucial importance of router/gateway functionality. The main areas are: Security - Access control,

Router/should have possibility to identify itself using certificates (e.g. X.509) and also pass certificates of meters connected to it to AAA server to enable their identifications - Data integrity, confidentiality and privacy,

(43)

Page 43 of 192

Data confidentiality uses encryption mechanisms available at various layers of the communication stack. Router/gateway should encrypt data using Advanced Encryption Standard (AES) at least:

- Layer 2 (IEEE 802.15.4g or IEEE P1901.2) - Layer 3 (IP Security [IPsec])

- Layer 4 (Datagram Transport Layer Settings [DTLS]) Threat detection and mitigation

- Router should logically separate different functional elements that should never be communicating with each other. For example, traffic originating from field technicians should be logically separated from AMI and DA. Router should enable VPN technology and firewalls for that purpose.

- Also, event logs from firewalls, routers, network management systems (NMS) and head-end systems, meters, and other head-endpoints need to be collected and passed on to a security incident and event manager (SIEM) tool.

Device and platform integrity

(44)