Appendix 3 to the Agreement for Delivery of Metering Infrastructure List and Description of Deliverables

pogonotomyeyrarΔίκτυα και Επικοινωνίες

26 Οκτ 2013 (πριν από 3 χρόνια και 9 μήνες)

85 εμφανίσεις

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





1
/
27


Appendix 3 to the

Agreement for Delivery of
Metering
Infrastructure

List and Description of Deliverables


TABLE OF CONTENTS

DELIVERABLES

................................
................................
................................
................................
................................
.

3

DETAILED DESCRIPTION OF DELIVERABLES

................................
................................
................................
.............

4

D
ELIVERABLE
P.1

-

M
ETERING
I
NFRASTRUCTURE
M
OCK
-
U
P WITH
M
OCK
-
U
P DOCUMENTATION
,

T
ESTING AND
D
IAGNOSTIC
S
OFTWARE FOR THE
M
OCK
-
U
P AND
T
EST
S
CENARIOS

................................
................................
................................
........

4

M
ETERING
I
NFRASTRUCTURE
M
OCK
-
U
P WITH DOCUMENTATION

OF THE
M
OCK
-
U
P

................................
.......................

4

T
ESTING AND
D
IAGNOSTIC
S
OFTWARE FOR
THE
M
OCK
-
U
P

................................
................................
.............................

5

T
EST
S
CENARIOS

................................
................................
................................
................................
...........................

5

D
ELIVERABLE
P.2

-

W
ORKSHOP MATERIALS AN
D INSTALLATION INSTR
UCTION

................................
................................
...

6

D
ELIVERABLE
P.3

W
ORKSHOPS

................................
................................
................................
................................
........

7

D
ELIVERABLE
P.4

C
ERTIFICATES

................................
................................
................................
................................
.......

8

D
ELIVERABLE
P.5

D
OCUMENTATION OF
D
EVICES
................................
................................
................................
...............

9

D
ELIVERABLE
P.6

T
ESTING AND
D
IAGNOSTIC
S
OFTWARE FOR THE
D
EVICES

................................
................................
.....

10

PRIME SPECIFICATION

................................
................................
................................
................................
.................

11

COMMUNICATION STANDARD BETWEEN AMI APPLICATION AND METERING INFRASTRUCTURE

..............

11

DESCRIPTION OF
FUNCTIONAL REQUIREMENTS


SINGLE
-
PHASE AND THREE
-
PHASE METERS

..................

11

Measurement of physical values

................................
................................
................................
............................

11

Control

................................
................................
................................
................................
................................
.........

11

Meter configuration

................................
................................
................................
................................
..................

12

Event detection and registration
................................
................................
................................
............................

12

Data presentation on the display

................................
................................
................................
...........................

13

Communication

................................
................................
................................
................................
.........................

14

USB port

................................
................................
................................
................................
................................
......

14

General Requirements

................................
................................
................................
................................
.............

15

Technical and quality parameters

................................
................................
................................
.........................

16

Meter operation

................................
................................
................................
................................
.........................

17

Software

................................
................................
................................
................................
................................
......

17

DESCRIPTION OF REQUIREMENTS FOR THE CONCENTRATOR AND BALANCING METER SET APPLICABLE
TO THE BALANCING METER.

................................
................................
................................
................................
.......

18

Measurement and recording of physical values

................................
................................
................................
..

18

Meter configuration

................................
................................
................................
................................
..................

18

Event de
tection and registration
................................
................................
................................
............................

19

Communication

................................
................................
................................
................................
.........................

19

General Requirements

................................
................................
................................
................................
.............

20

Technical and quality parameters

................................
................................
................................
.........................

20

Software

................................
................................
................................
................................
................................
......

21

DESCRIPTION OF REQUI
REMENTS FOR THE CONCENTRATOR AND BALANCING METER SET APPLICABLE
TO THE CONCENTRATOR

................................
................................
................................
................................
.............

21

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





2
/
27

Operation of the meters

................................
................................
................................
................................
...........

21

Communication

................................
................................
................................
................................
.........................

22

General Requirements

................................
................................
................................
................................
.............

22

Technica
l and quality parameters

................................
................................
................................
.........................

23

Software

................................
................................
................................
................................
................................
......

23

OBIS CODES

................................
................................
................................
................................
................................
.....

23

Data read for recipients

................................
................................
................................
................................
...........

23

Load profile data

................................
................................
................................
................................
...................

24

Billing data

................................
................................
................................
................................
...............................

24

Data read for ma
nufacturers

................................
................................
................................
................................
.....

25

Load profile data

................................
................................
................................
................................
.....................

25

Billing data

................................
................................
................................
................................
...............................

25




Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





3
/
27


I.

DELIVERABLES.

The Contractor will provide the Contracting Authority with the following Deliverables:

in Stage I:

1)

Deliverable P.1
-

Metering Infrastructure Mock
-
Up with Mock
-
Up documentation, Testing and D
i-
agnostic Software for the Mock
-
Up and Test Scena
rios;

In Stage II:

2)

Deliverable P.2
-

Workshop materials and installation instructions

3)

Deliverable P.3
-

Workshops

In Stage III:

4)

Deliverable P.4
-

Certificates

5)

Deliverable P.5
-

Documentation of Devices

6)

Deliverable P.6
-

Testing and Diagnostic Software

7)

Deliverable P.7
-

Devices, including:

a)


Concentrator
-
Balancing Sets

______ units

b)


Single
-
phase residential meters

______ units

c)


Three
-
phase residential meters, direct

______ units



Deliverable
Code

Deliverable Name

Description

P.1.

Metering
Infrastru
c-
ture Mock
-
Up





Metering Infrastructure Mock
-
Up allowing the Contracting
Authority, to verify the functionality, quality and technical
parameters of the Devices which are to be delivered under
the Agreement and their consistency with the sample
pr
o-
vided with the Offer along with documentation describing
how the functionality is delivered by respective elements of
the Mock
-
Up.


Testing and Diagno
s-
tic Software for the
Mock
-
Up

Computer software with a user manual, used for testing, d
i-
agnosis and parameterization of the Mock
-
Up delivered by
the Contractor.


Test scenarios

Scenarios based on which the Metering Infrastructure will
be tested


P.2

Workshop materials
and installation i
n-
structions

Instruction for installation, assembly,
start
-
up and oper
a-
tion of the Devices, manuals for support services, training
materials, form of the Workshop Completion Certificate.

P.3

Workshops

Training courses aimed at equipping the attendees with
knowledge and competence needed to:

1)

install the
Devices individually


䥮s瑡汬慴i潮oWo牫s桯ps;
慮a



s瑡牴t 異Ⱐc潮晩g畲攠慮搠潰敲慴攠t桥 D敶eces


S瑡牴
-
Up
坯牫s桯ps;

慳 灡牴r潦 瑨t 䵥M敲eng 䥮晲慳瑲畣t畲攬 敮e敤ewi瑨 數慭s; if
瑨攠慴瑥a摥ds 灡ss 瑨攠數慭sⰠ瑨敹t睩w氠b攠慷慲摥搠坯r

s桯瀠䍯m灬整i潮o
C敲瑩晩c慴敳 ⡉(s瑡汬慴a潮o潲o S瑡tt
-
U瀬pr

s灥ptiv敬礩.


倮P

Certificates

Documents issued by institutions external to the Contra
c-
tor, within the scope:

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





4
/
27



1) Specified in

the

Measuring Instruments Directive
2004/22/EC of the European Parliament and of the Council
issued on 31 March 2004 (EU OJ 2004.135.1, the "MID D
i-
rective") and in the Economy Minister's regulation of 18
December 2006 on basic requirements for measuring i
n-
str
uments (Journal of Laws of 2007 No. 3 Item 27, as
amended) (in the form of a photocopy of the original certi
f-
icate with translation to Polish,



2) of aging tests



3) of a PRIME ALLIANCE certificate

P.5

Documentation of
Devices

Includes DTR (technical and maintenance documentation),
software other than testing and diagnostic software, doc
u-
mentation of interfaces.

P.6

Testing and Diagno
s-
tic Software for the
Devices

Computer software for testing, diagnosis and parameteriz
a-
tion of

the Devices delivered by the Contractor, plus user
manual for the software.


II.

DETAILED DESCRIPTION OF DELIVERABLES



D
ELIVERABLE
P.1

-

M
ETERING
I
NFRASTRUCTURE
M
OCK
-
U
P WITH
M
OCK
-
U
P DOCUMENTATION
,

T
ESTING AND
D
IAGNOSTIC
S
OFTWARE FOR THE
M
OCK
-
U
P AND
T
EST
S
CENARIOS


M
ETERING
I
NFRASTRUCTURE

M
OCK
-
U
P WITH DOCUMENTATION

OF THE
M
OCK
-
U
P

Purpose:

Delivery of the Mock
-
Up presenting the full functionality of Metering Infrastructure
devices to the Contracting
Authority

Descri
p-
tion:

1)

The following should be delivered in particular as part of the Deliverable:

a)

One Concentrator and Balancing Set,

b)

Two single
-
phase residential electricity meters,

c)

Two three
-
phase residential electricity meters,

d)

Removable communication module ensuring communication between the
residential meter and meters used for other utilities,

e)

Two meters used for other utilities (e.g. gas, water),

f)

One electricity receiver per each residential meter,

g)

3 current
transformers 50/5 for the balancing set.

2)

The mock
-
up should enable connection to a single
-
phase 230V socket, which will
allow the devices to be powered with a unipolar phase in a three
-
phase system.

3)

The meters should be connected with the Mock
-
Up's
power supply installation
using "S" type protection measures and control and metering rails and switches
for reversing the flow direction.

4)

The removable communication module mentioned in item 1) d) which ensures
communication between the residential mete
r and other
residential

meters
should be connected to one of the residential meters using a USB port.

5)

The communication module described in item 1) d) should integrate HAN ne
t-
works with the following functionalities:

a)

Communication between the HAN
communication module and the concentr
a-
Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





5
/
27

tor should be carried out using the meter and the PLC/nN technology,

b)

The reading of other
residential
meters should be possible from the level of
concentrator and balancing sets,

c)

Two
-
way
communication with the modu
le with a display should be possible
from the level of concentrator and balancing sets,

d)

The USB interface should also be used as an interface for connecting comm
u-
nication modules in technologies other than PLC directly into the central sy
s-
tem,

6)

The
communication module mentioned in item 1) d) should be provided in tec
h-
nologies other than PLC.

7)

The Mock
-
Up should support connection of the communication module me
n-
tioned in clause 1) d) to any residential meter.

8)

Relevant documentation should be
attached to the Mock
-
Up.

Type:

Devices.

Document
a-
tion format

MS Office or other equivalent, as agreed.


T
ESTING AND
D
IAGNOSTIC
S
OFTWARE FOR THE
M
OCK
-
U
P


Purpose:

to

configure and test the Mock
-
Up.

Descri
p-
tion:

1)

Under this Deliverable, the Testing and Diagnostic Software with documentation
should be developed and delivered to the Contracting Authority.

2)

The software should enable:

a)

parameterization and
configuration of the Devices, in particular with respect
to:

i)

values measured and stored by the Devices,

ii)

values displayed on the display,

iii)

configuration files,

iv)

maintenance of the execution element in response to commands,

v)

value of current
limiter,

b)

firmware upgrade, excluding firmware subject to MID certification,

c)

reading of the Devices,

d)

control of the execution element,

in

the full functional scope of the Devices described in the Agreement and in the
scope required for the Client’s appropriate use of the Devices.

Type:

Software, Document.

Document
a-
tion format:

MS Office or other equivalent, as agreed.


T
EST
S
CENARIOS

Purpose:

Prepare scenarios for testing of the Metering Infrastructure.

Descri
p-
Test scenarios should take into account all of the technical requirements set out in
Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





6
/
27

tion:

the Terms of Reference and in the Agreement and also include a description of how
to test each of these requirements. The plan test scenarios and the corresponding
clauses in the ToR and in the Agreement (as ordered in the Terms of Reference and
the Agreem
ent) should be prepared in the form of a table.

Type:

Document.

Format

MS Office or other equivalent, as agreed.



Delivery
Date

........ days after the date of the Agreement.

Description
of actions:

According to the following list.

Action

Contractor

Contracting
Authority

1.

Transfer Models for Infrastructure counters and document
a-
tion Models, Software test and Diagnostic Models and Scena
r-
ios test


Deliverable submitted for acceptance

O

NW

2.

Verification of the Deliverable

W

O

3.

Consideration of

any objections to the Deliverable

O

NW

4.

Acceptance of the Deliverable

W

O

*) O


person responsible for execution, W


person supporting the execution, NW


co
-
operation in accordance with the
Agreement


D
ELIVERABLE
P.2

-

W
ORKSHOP MATERIALS AN
D
INSTALLATION INSTRUC
TIONS

Purpose:

Transfer of knowledge and technical information about the Devices.

Delivery
Date

No later than one week after signing the acceptance
report for Deliverable P.1.

Description:

1)

The following should be delivered in particular as part of the Deliverable:

a)

plan and scope of the Workshops containing detailed information on the ge
n-
eral requirements set forth in the Agreement, including presentation of
workshop methodology and competence of trainers,

b)

technology card for installation and start
-
up of individual Device types, i
n-
cluding detailed installation instructions;

c)

description of the manner of fulfilling the functional requirements for the e
l-
ements of the Metering Infrastructure;

d)

manual for the operation and parameterization of the measuring systems,
concentrator and balancing sets, along with a functional
description of the
testing and diagnostic application;

e)

form of the workshop completion certificate.

Type:

Document.

Format

MS Office or other equivalent, as agreed.

Description
According to the following list.

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





7
/
27

of actions:

Action

Contractor

Contracting
Authority

1.

Delivery of a complete set of workshop materials and install
a-
tion instructions


Deliverable submitted for acceptance

O

NW

2.

Verification of the Deliverable

W

O

3.

Consideration of any objections to the Deliverable

O

NW

4.

Acceptance of the Deliverable

W

O

*) O


person responsible for execution, W


person supporting the execution, NW


co
-
operation in accordance with the
Agreement


D
ELIVERABLE
P.3

W
ORKSHOPS

Purpose:

to

equip the participants with knowledge and competencies necessary for their una
s-
sisted installation, configuration and operation of the Devices within the Metering I
n-
frastructure.

Delivery
Date

Beginning ......... days after acceptance of the Workshop doc
umentation, end


no later
than 4 years after the date of the Agreement.

The Deliverable will be accepted after each Workshop cycle is completed

Preparation of the Deliverable for acceptance involves, among others, delivery of a
t-
tendance records in
the form of lists with individual names and a complete set of
Workshop Completion Certificates arranged in the order consistent with such lists.

Descri
p-
tion:

1)

The Workshops will be held in Poland in a location specified by the Contracting
Authority and will be divided into:

a)

Installation Workshops during which the participants will be trained on:

i)

installation and configuration of the Devices,

ii)

operation of
the offered Devices,

iii)

operation of the Testing and Diagnostic Software in the basic scope (i
n-
cluding but not limited to installation and data reading from the Device).

b)

Start
-
Up Workshops during which the participants will be trained on:

i)

start
-
up of
the Devices, in particular communication between them,

ii)

diagnosis (remotely and locally) of faults and disturbances in the fun
c-
tioning of the Metering Infrastructure,

c)

preparing of parameterization files,

d)

operation

of the Testing and Diagnostic Software in the extended scope (i
n-
cluding but not limited to parameterization and configuration of the Devices,
reporting from the Metering Infrastructure level).

2)

The Start
-
Up Workshop may only be attended by persons who
have completed
the Installation Workshop and received Completion Certificates for that wor
k-
shop.

3)

The Contractor is obliged to ensure at his expense:

a)

conducting of the Workshops by appropriately qualified trainers;

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





8
/
27

b)

workshop materials and tests to
check the participants’ knowledge;

c)

Personal Completion Certificates for the Installation Workshop and the Start
-
Up Workshop, respectively, bearing participant names and unique ID nu
m-
bers, confirming a positive completion of respective Workshops by indivi
dual
participants;

d)

equipment necessary to conduct training (notebook computer, projector)

4)

The Contractor undertakes to:

a)

develop a Workshop program in such a way that it would be possible to co
n-
duct a Workshop in 1 day;


b)

ensure

at least one coach per group of Workshop participants consisting up
to 10 people.


5)

Each Workshop should end with an exam (a test prepared by the Contractor).
Each participant is awarded a Workshop Completion Certificate after he/she
passes the exam. The
condition for participation in a Start
-
Up Workshop is for
the participant to hold an Installation Workshop Completion Certificate.

Type:

Workshops.

Format

n/a

Description
of actions:

According to the following list.

Action

Contractor

Contracting
Authority

1.

Presentation of a workshop concept that would allow impl
e-
mentation of workshops in a single day. Provision and
presentation of Contractor's proposed personnel and its
qual
i
fications.

O

NW

2.

Acceptance of the workshop program and personnel

pr
o-
posed by the Contractor

W

O

3.

Implementation of the changes proposed by the Contracting
Authority

O

NW

4.

Delivery of workshop materials to the Contracting Authority

O

NW

5.

Execution of Workshops with staff specified by the Contrac
t-
ing Authority

O

NW

6.

Delivery of Workshop Completion Certificates confirming the
skills to install and operate the Metering Infrastructure to pa
r-
ticipants

O

NW

7.

Deliverable submitted for Acceptance

O

NW

9.

Acceptance of the Deliverable

W

O

*) O


person
responsible for execution, W


person supporting the execution, NW


co
-
operation in accordance with the
Agreement


D
ELIVERABLE
P.4

C
ERTIFICATES

Purpose:

to

confirm compliance with legal and technical requirements of the Devices that have
Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





9
/
27

passed the tests on the Mock
-
Up.

Delivery
Date

........ days after the date of the Agreement.

Descri
p-
tion:

The following should be delivered in particular as part of the D
eliverable:



certificate of compliance with the MID Directive no. 2004/22/EC of the Europ
e-
an Parliament of 31 March 2004 on measuring instruments



PRIME certificate confirming interoperability of the devices, in accordance with
the technical specification developed by the PRIME ALLIANCE technical group




aging tests.

Type:

Document.

Size:

MS Office or other equivalent formats, as agreed

Description
of actions:

According to the following list.

Action

Contractor

Contracting
Authority

1.

Delivery of the complete documentation (Certificates)


D
e-
liverable submitted for acceptance

O

NW

2.

Verification of the Deliverable

W

O

3.

Consideration of any objections to the Deliverable

O

NW

4.

Acceptance of the Deliverable

W

O

*) O


person responsible for execution, W


person supporting the execution, NW


co
-
operation in accordance with the
Agreement


D
ELIVERABLE
P.5

D
OCUMENTATION
OF
D
EVICES

Purpose:

for the Contracting Authority to obtain the full Documentation of the Devices.

Delivery
Date

........ days after the date of the Agreement.

Descri
p-
tion:

The following should

be delivered in particular as part of the Deliverable:



technical and maintenance documentation for individual Devices, where the do
c-
umentation of the Metering Devices must be compliant with the MID Directive
no. 2004/22/EC of the European Parliament of
31 March 2004 on measuring i
n-
struments (EU OJ L.2004.135.1, the "MID Directive") and with the Economy Mi
n-
ister's regulation of 18 December 2006 on basic requirements for measuring i
n-
struments (Journal of Laws 2007, No. 3, Item 27, as amended);



detailed d
ocumentation of the application protocol implemented in the conce
n-
trator and balancing sets used for communication with the AMI application, ta
k-
ing into account detailed descriptions of the interface functioning in accordance
with the requirements contain
ed in section III of this appendix “PRIME Specific
a-
tion” and in section IV of this appendix “Standard of Communication between the
AMI application and the Metering Infrastructure”, and communication protocols
with detailed technical specifications enablin
g development of an interface;



detailed documentation of the application protocol and description of the opera
t-
Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





10
/
27

ing concept behind the meter's USB port;




technical documentation, installation, maintenance and user manuals for all the
Devices (including
technology cards of installation and start
-
up for respective
Device types, in both hard
-
copy format and as electronic files saved in common
file formats allowing them to be read on personal computers).

Type:

Hard
-
copy and electronic document.

Format

MS
Office or other equivalent, as agreed.

Description
of actions:

According to the following list.

Action

Contractor

Contracting
Authority

1.

Delivery of the complete documentation of the Devices along
with the acceptance document


Deliverable submitted
for a
c-
ceptance

O

NW

2.

Verification of the Deliverable

W

O

3.

Consideration of any objections to the Deliverable

O

NW

4.

Acceptance of the Deliverable

W

O

*) O


person responsible for execution, W


person supporting the execution, NW


co
-
operation

in accordance with the
Agreement

D
ELIVERABLE
P.6

T
ESTING AND
D
IAGNOSTIC
S
OFTWARE FOR THE
D
EVICES


Purpose:

to configure and test the Devices.

Delivery
Date

…….. days

慦a敲⁴桥⁤慴攠潦⁳ gning⁴桥⁍ ck
-
U瀠acce灴慮c攠牥灯牴r

Description:

1)

Under this Deliverable, the Testing and Diagnostic Software with documentation
should be developed and delivered to the Contracting Authority.

2)

The software should enable:

a)

parameterization and configuration of the Devices, in particular with respect
to:

i)

values measured and stored by the Devices,

ii)

values displayed on the display,

iii)

configuration files,

iv)

maintenance of the execution element in response to commands,

v)

value of current limiter,

b)

firmware upgrade, excluding firmware subject to MID certification,

c)

reading of the Devices,

d)

control of the execution element,

in

the full functional scope of the Devices described in the Agreement and in the
scope required for the Client’s appropriate use of the Devices.

Type:

Software, Document.

Document
a-
MS Office or other equivalent, as agreed.

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





11
/
27

tion format:

Description
of
actions:

According to the following list.

Action

Contractor

Contracting
Authority

1.

Delivery of the Testing and Diagnostic Software for the Devi
c-
es along with documentation


Deliverable submitted for a
c-
ceptance

O

NW

2.

Verification of the Deliverable

W

O

3.

Consideration of any objections to the Deliverable

O

NW

4.

Acceptance of the Deliverable

W

O

*) O


person responsible for execution, W


person supporting the execution, NW


co
-
operation in accordance with the
Agreement



III.

PRIME SPECIFICATION

The PRIME specification is included in separate documents, which constitute an integral part of this
Appendix, i.e. files (documents) named „Appendix 3 to the Agreement


PRIME, English version” and
„Appendix 3 to t
he Agreement


PRIME, translation, Polish version”.

The English version of the document is the main (leading) version.


IV.

COMMUNICATION STANDARD BETWEEN AMI APPLICATION AND METE
R-
ING INFRASTRUCTURE

The standard of communication between the AMI Application and the Metering Infrastructure is d
e-
scribed in a separate document, constituting an integral part of this Appendix, i.e. the file (document)
named “Appendix 3 to
the Agreement


Communication Standard”.


V.

DESCRIPTION OF FUNCTIONAL REQUIREMENTS


SINGLE
-
PHASE AND
THREE
-
PHASE METERS

1)

Measurement of physical values

a)

The meter should measure and register active and reactive energy in both directions (input
and output).

b)

Measured values of active energy should be registered in kWh to a precision of at least three
significant

digits.

c)

Measured values of reactive energy should be registered in kvarh to a precision of at least
three significant digits.

d)

Load profile should be registered by default as indications of the counter.

e)

The meter should measure effective voltage and phase

currents.

f)

The meter should measure instantaneous power.


2)

Control

a)

The meter should support power limitation by remote and local settings:

i)

threshold value of input 15
-
minute power, with accuracy not worse than 0.1 kW;

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





1
2
/
27

ii)

time of au
tomatic connection of the meter (understood as meter readiness to connect
voltage at the recipient’s installation) after occurrence of a limitation. The time should
be configurable in the range from 1 to 60 minutes.

b)

The meter should support remote and loca
l disconnection / connection of the recipient by
changing the state of an execution element (e.g. contactor). The meter is configured by d
e-
fault to execute remote connection.

c)

Execution element in no
-
voltage state of the meter should be in the off position
.

d)

The meter should support local and remote checking of the execution element state.

e)

After a downtime in power supply due to a disturbance in network work, the execution el
e-
ment should be in the same state as before the event.

f)

The meter should support volt
age connection to recipient’s installation locally by the recip
i-
ent after previous connection.


3)

Meter configuration

a)

The meter should support remote and local setting of averaging periods for the following
values: 15,

30, 60 minutes, for registration of active and reactive energy consumption pr
o-
files (four energy profiles).

b)

In the event of an interruption of the parameterization process (locally or remotely) the m
e-
ter should continue work in accordance with the to
-
date

parameterization. Until the moment
of confirmation of parameterization correctness in a local or remote connection session the
meter should remain in the settings from before the change.

c)

The meter should enable defining of at least 1 threshold of exceedin
g and at least 3 thres
h-
olds of reducing voltage as a percentage value of deviation from rated voltage. The meter
should have the following pre
-
defined thresholds:

i)

-

reduced voltage: 10,20%

ii)

-

loss of voltage: 50%,

iii)

-

excess voltage: 10%.

d)

The meter should sta
rt measurement of the duration of excess/reduced voltage, in a period
programmed by the operator (not shorter than 1s), if its extent exceeds the set threshold.

e)

The meter should end measurement of the duration of the event if the voltage value is:

i)

for red
uction


1% higher than the declared threshold;

ii)

for excess


1% lower.

f)

The meter should support remote and local change of the list of parameters displayed on the
display with regard to any meter parameters.



4)

Event detection and registration

a)

The meter should record the state of the counter of active cumulated energy at the moment
of occurrence of any set event registered by the meter (e.g. voltage decay, removal of the
cover of terminal strip, etc.).

b)

The meter should enable configuration of the communication transmission mode for the
events registered by the meter. For each type of event one of the following modes may be d
e-
termined:

i)

automatic transmission mode (immediately);

ii)

session read
-
out mode (on

schedule);

c)

the meter should register at least the following events:

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





13
/
27

i)

disconnection / connection of the recipient's meter;

ii)

activation / deactivation of the function of limiting the recipient’s active input power;

iii)

reduction / excess of rated voltage;

iv)

energy

theft
-
related events: exposure to magnetic field (insensitivity level up to 400
mT), by
-
pass detection, detection of phase change and zero, removal of the cover of the
terminal strip, removal of the cover;

v)

internal errors of the meter (bit flag vector).

d)

T
he meter should register and send in session read
-
out mode the events related to config
u-
ration change (parameterization of the meter).

e)

Each event registered by the meters should be described with the following attributes:

i)

date and time of the event;

ii)

event
code.


5)

Data presentation on the display

a)

The meter should have a display (in compliance with the relevant valid laws and regul
a-
tions) enabling the display of at least:

i)

Eight characters for registers,
enabling parameterization of the measurement display,
i.e. any setting of the decimal place with respect to meter measurement accuracy. The
default value of presentation in 7+1 format;

ii)

tariff group marker;

iii)

current zone market;

iv)

state of the execution elemen
t;

v)

date and time of built
-
in clock.

b)

Values shown on the display should be described with OBIS codes.

c)

Explanations of major register codes, fixed durably on the meter case or rate table, or on the
terminal strip cover must be compliant with the OBIS code a
nd in the following positions:




OBIS code

OVERVIEW

C.1.0

Meter identification number

1.8.0

E:Input
-
active.Energy.Total

1.8.1

E: Input
-
active.Energy.1
-
strefa

1.8.2

E: Input
-
active.Energy.2
-
strefa

1.8.3

E: Input
-
active.Energy.3
-
strefa

1.6.0

E: Input
-
active.Pmax.round
-
the
-
clock

2.8.0

Active energy output to the network (total)

5.8.0

Reactive induction energy (total)

8.8.0

Reactive capacity energy (total)

0.9.1

Current time

0.9.2

Current date

0.2.2.

Tariff


Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





14
/
27

d)

The meter should enable automatic and
manual scrolling of communications on the display.
60 seconds after the end of manual scrolling of the communications the meter should return
to displaying in the automatic mode. The interval of automatic scrolling of the communic
a-
tions should be configura
ble. There should be at least two display lists:

i)

sequence list;

ii)

manual scrolling list;

The lists should be freely configurable.

e)

Highlighting of the display is admissible only in the mode of manual scrolling of the comm
u-
nications. It should be possible to
read out from the display for at least 4 months:

i)

counter states;

ii)

tariff group marker;

iii)

date and time.


6)

Communication


a)

The meter should have at least the following communication interfaces:

i)

Optical link for local
communication compliant with IEC 62056
-
21;

ii)

USB port type A for connection of the module intermediating in the communication
with the meters of other utilities or HAN infrastructure; USB port is defined in section
7.

b)

The meter should be equipped with built
-
in module for communication with wide area ne
t-
work in PLC in accordance with PRIME specification in version 1.3.6 or newer (the specific
a-
tion is contained in section III of this Appendix) and the communication standard described
in section IV of this Appe
ndix. The communication module to the wide area network should
additionally meet the following characteristics:

i)

It should support automatic detection and identification of the meter by the Central
System and concentrator in its area of operation. The mete
r should start communic
a-
tion with the superior device or with the Central System directly after power supply
connection. The status of setting up and establishing of communication should be si
g-
naled;

ii)

It should support dynamic creation of transmission conne
ction networks (dynamic
creation of alternative routing paths) independently of electrical energy network div
i-
sions;

iii)

Power supply to the module is provided via an internal feeder cable of the meter;

iv)

Communication should be encrypted with the algorithm AES
-
128.

c)

Electrical interfaces of the meter should not be available for the user without breaking of the
fitter’s seal.


7)

USB port

a)

The meter should be equipped with USB Host Controller compliant at least with the standard
USB 1.1 (F
ull Speed).

b)

USB Host Controller in the meter should be integrated with Root Hub equipped with at least
one USB port compliant with the standard USB 1.1.

c)

Mechanically the USB port should have the form of A type socket resistant to exposure to e
x-
ternal facto
rs.

d)

USB port in the meter should enable current input up to 500 mA.

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





15
/
27

e)

USB port in the meter should be used to connect to the meter a device for communication
with the HAN network (“HAN module”). Communication model should be based on Virtual
Serial Port type

connection:

i)

Meter software should support Host Controller and Root Hub as well as devices co
n-
nected to the USB port for communication with HAN;

ii)

devices connected to the USB port for communication with HAN should be CDC


Co
m-
munication Device Class (02h) a
nd implement Abstract Control Model for the device
with Serial Emulation mode.

f)

Device connected to the USB port for communication with HAN should implement at least
two interfaces:

i)

control (02h


for communication control);

ii)

data (0Ah


for data transmissio
n).

g)

Communication from / to WAN incoming to / from HAN should be from the WAN perspe
c-
tive transported via DLMS protocol addressing special registers with producer
-
specific OBIS
codes.

h)

HAN module should support communication with HAN autonomously, in accord
ance with
the specification of a given HAN solution. HAN module translates the application protocol b
e-
tween the meter and HAN module into HAN protocol (having the function of a gateway b
e-
tween the meter and HAN).

i)

Meter communication with the HAN module sho
uld be fully two
-
way, encrypted with the
AES
-
128 algorithm with an encryption key length of at least 128, offering “push” and “pull”
modes. In the “push” mode the meter should enable service of the USB port in two options:

i)

“autonomous”


the meter autonomo
usly with a set interval (by default every 10s)
sends communications to the USB port for propagation in HAN (the scope of the tran
s-
mitted data might be based on the scope analogous to the one defined in mode D of IEC
62056
-
21 protocol and should contain at

least energy consumption registers and meter
statuses). This option of sending communications should be disabled in the meter in
the factory. Enabling of the option should be possible by software, both remotely and
locally;

ii)

“system”


the meter should sup
port transfer of communication (with the size of up to
4096B) from the Central System via the WAN module to the HAN module, where tran
s-
fer of the communication from the WAN module to the HAN module should last no
longer than 1s.

j)

The meter supplier should m
ake available full documentation of:

i)

Host Controller and Root Hub of the USB interface implemented in the meter;

ii)

expected implementations of USB interfaces in the HAN module;

iii)

application protocol between the meter and the HAN module;

iv)

communication protocol

with the HAN network;

v)

expected extensions of OBIS codes for communication with the HAN network via WAN
network.


8)

General Requirements

a)

The meter should store Gregorian calendar with fixed and movable holidays, leap
years and
time zone change dates for at least 16 years with automatic summer / winter switch.

b)

The meter should enable a remote update of the calendar.

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





16
/
27

c)

The meter should store in non
-
volatile memory measurement data (profile and billing) and
non
-
measurement
data (events and alerts).

d)

Memory size should enable storing of profile data for a period of at least 63 last days with
the averaging period of 15 minutes (for active and reactive energy register in both dire
c-
tions).

e)

The meter should store the register ev
ents in cyclical event buffers:

i)

network (voltage decay, voltage increase)


at least 120 items;

ii)

other


at least 120 items.

f)

All devices should be new out of factory (not operated in production).

g)

The meter should be produced in the year of delivery.

h)

Signin
g of the meter type and identification number must be durable, unique and must en
a-
ble unequivocal identification of each meter in no
-
voltage status. Factory number of the m
e-
ter should be displayed on the meter display. Identification parameters should be r
eadable
electronically remotely and locally.

i)

Indication of the software version of the devices and communication modules should be u
n-
equivocal and readable electronically remotely and locally.

j)

The meter should have additional signing with a bar code along
with attached three stickers
containing the signing of the meter (it should be possible to remove the stickers from the
meter case and reuse them by sticking them on a paper document) and its bar code in the
standard compliant with Interleaved 2 of 5 or eq
uivalent:

i)

meter type


5 characters;

ii)

factory number


8 characters;

iii)

production date


2 characters;

iv)

control sum


1 character (or 0 if the sum is not calculated);

k)

The meter should receive tariff file with the activation date.

l)

The meter should support
setting of at least 4 time zones.

m)

The meter should support automatic daily fixing of energy counter states. The daily states
should be stored for a period of at least 1 month.

n)

The total of measurements resulting from daily increments must be the same as
the diffe
r-
ence in counter states in the same period.


9)

Technical and quality parameters

a)

The meter should have active energy measuring of at least class B (in accordance with MID).

b)

The meter should have re
active energy measurement class of at least 3, according to the tes
t-
ing methodology defined in standards: IEC 62053
-
21 and 23.

c)

The range of temperatures of the meter work should be at least:
-
40
o
C / +70
o
C.

d)

The case should ensure protection degree of at lea
st IP 51.

e)

The meter should be resistant to exposure to a magnetic field of up to 400 mT.

f)

Nominal frequency of the meter is 50 Hz.

g)

Nominal voltage of single
-
phase meter is 230V and for tripe
-
phase meter it is 3x230V /
400V.

h)

Base current for the meter is 5A
, according to the testing methodology specified in IEC
62053 standards.

i)

The maximum current for single
-
phase meters: Imax

60A, for three
-
phase meters:
Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





17
/
27

Imax

80A, according to the testing system defined in the IEC 62053 standards.

j)

The meter should meet the
requirements of protection against atmospheric and network
overvoltage of at least 4 kV.

k)

Metering unit own power consumption for a single
-
phase meter should not exceed 2W and
for a triple
-
phase meter 4W.

l)

The meter should have an internal real time clock
maintained for at least 8 years.

m)

Accuracy of the built
-
in clock of the meter should not be worse than 1 second per 24 hours.

n)

The time source for the meter is the concentrator.

o)

The meter should mark time
-
marked data with a flag informing about time
synchronization
status. The fag (certified time / non
-
certified time) informing about time synchronization
status will be set in case of:

i)

turning on (initiation) of the meter / resuming of power supply to the meter;

ii)

loss of the possibility to synchronize t
ime for 7 subsequent calendar days. The meter
will provide the data marked with a flag at each transmission of time
-
marked data.

p)

The meter should enable local and remote change of firmware (within limits ensuring
maintenance of compliance with the MID).

q)

Th
e case and terminals of the meter should comply with the DIN 43857 standard with r
e-
spect to spacing of hangers / installation holes and dimensions of terminals of the terminal
box.



10)

Meter operation

a)

Data shown on the dis
play and meter identification data should be visible after installation
of the meter.

b)

The meter should enable change of the configuration locally via an optical link and remotely
via the module for communication with large area network.


11)

Software

a)

The Contractor will deliver software for local operation, diagnosis and reporting of the meter
work, enabling full configuration, parameterization, diagnosis and reading of the measur
e-
ment data and events from the meter .

b)

The software
for local operation (configuration and reading) of the meters should ensure
three access levels:

i)

only reading of the measurement data and parameters from the meter (collector
mode);

ii)

reading and parameterization of the meter with ready parameterization file
s, clock se
t-
ting (fitter mode);

iii)

reading and parameterization of the meter in full scope (administration mode).

c)

Access to the collector mode should be secured at least with software security. Access to the
fitter and administration modes should be limited
by hardware key securing the testing and
diagnostic application.

d)

The software for local operation of the meters should enable preparation of configuration
files (for purposes of fitter mode). Configuration files from an older version of the software
should

be possible to service in newer releases.

e)

The software for local operation of the meters should enable export of measurement data,
events and configurations from the meters to text files (TXT, CSV, XML) with a documented
Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





18
/
27

structure ensuring data collection

in the Central System.

f)

The Contractor will ensure at least for the duration of the guarantee, within the compens
a-
tion for the scope of the order, access to current versions of software for local operation of
the meters, communication modules and local rea
d
-
out systems if new software versions are
released. The new software versions should support the devices previously bought by the
client from the supplier.

g)

The software for local operation of the meters should support interworking with the Wi
n-
dows 7 opera
ting system.

h)

Technical documentation of the configuration and communication protocols will be provided
under the contract in order to implement support of those protocols in the IT systems of the
Client.



VI.

DESCRIPTION OF REQUIREMENTS FOR THE CONCENTRATOR

AND BALANCING
METER SET APPLICABLE TO THE BALANCING METER.

1)

Measurement and recording of physical values


a)

The meter should work in a semi
-
direct system in complete star configuration.

b)

The meter should measure active energy in both directions (input and output).

c)

Measured values of active energy should be registered
in kWh to a precision of three signif
i-
cant digits.

d)

The meter should register 2 profiles for active energy and 4 profiles for reactive energy (four
quadrants) as well as voltages and phase currents.

e)

Measured values of reactive energy values should be regist
ered in kVARh to a precision of
three significant digits.

f)

The meter should measure apparent energy in both directions (input and output).

g)

The measured apparent energy values should be registered in kVAh to a precision of three si
g-
nificant digits.

h)

Load
profile should be registered by default as indications of the counter.

i)

The meter should measure instantaneous values of:

i)

voltages and phase currents and the current in the neutral wire;

ii)

voltage and current angles (φ referring to phase 1 voltage);

iii)

active, r
eactive and apparent power as a total and for each phase;

iv)

the THD ratio in current and voltage.

j)

The meter should support automatic daily fixing of energy counter states. The daily states
should be stored for a period of at least 1 month.

k)

The total sum of e
nergy resulting from increases in 24
-
hour periods should be identical to the
difference of the statuses of energy counters in the same periods.


2)

Meter configuration

a)

The meter should make it possible to have remote an
d local access to all the measured quant
i-
ties and functions offered by the meter.

b)

The meter should support remote and local setting of averaging periods in the minimum range
from 15 minutes to 60 minutes for the following values:

15, 30, 60 minutes, for re
gistration
of active and reactive energy consumption profiles.

c)

In the event of an interruption of the parameterization process (locally or remotely) the meter
Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





19
/
27

should continue work in accordance with the to
-
date parameterization. Until the moment of
confirm
ation of parameterization correctness in a local or remote connection session the m
e-
ter should remain in the settings from before the change.

d)

The meter should enable defining of at least 1 threshold of exceeding and at least 3 thresholds
of reducing
voltage as a percentage value of deviation from rated voltage. The meter should
have the following pre
-
defined thresholds:

i)

-

reduced voltage: 10.20%,

ii)

-

loss of voltage: 50%,

iii)

-

excess voltage: 10%.

e)

The meter should start measurement of the duration of excess/reduced voltage, in a period
programmed by the operator (not shorter than 1s), if its extent exceeds the set threshold.

f)

The meter should end measurement of the duration of the event if the volta
ge value is:

i)

for reduction


1% higher than the declared threshold;

ii)

for excess


1% lower.


3)

Event detection and registration

a)

The meter should enable configuration of the communication transmission mode f
or the
events registered by the meter. For each type of event one of the following modes may be d
e-
termined:

i)

automatic transmission mode (immediately);

ii)

session read
-
out mode (on schedule);

b)

Each event recorded by a meter should be described by the followin
g attributes:

i)

date and time of the event;

ii)

event code.


4)

Communication


a)

A balancing meter may be a free
-
standing device or one integrated with a data concentrator.

b)

Local communication with a free
-
standing meter should be possible via an optical link or
Ethernet/RJ45 or USB, with the use of IEC 62056
-
21 or DLMS.

c)

Local communication with a metering module included in a device combining the function of
meter and data c
oncentrator should be possible in at least one of the following ways:

i)

via an optical link or Ethernet/RJ45 or USB, with the use of IEC 62056
-
21 or DLMS;

ii)

via

Ethernet/RJ45 with the use of an interface possible to be reached locally through a web
browser to which an access requires authorization.

d)

Interfaces of a meter (or a device combining the function of meter and data concentrator)
should make it possible to

connect a 3GPP communication module.

e)

In the case of a free
-
standing meter, it should make communication with a concentrator poss
i-
ble at least through the following solutions:

i)

a WAN communication module using powerline communications (PLC) based on PRIME
s
pecification, version 1.3.6 or newer (the specification can be found in section III of this
Appendix) and the communication standard described in section IV of this Appendix;

ii)

an RS485 interface.

f)

Communication with a concentrator should additionally have th
e following features:

i)

a device combining the function of a meter and a concentrator should support automatic
Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





20
/
27

detection and identification of the metering module by the Central System and the data
concentrator module within its operating range. The meterin
g module should start co
m-
municating with a master device or the Central System directly after connecting power
supply. The status of such communication being established and having been established
should be signaled;

ii)

the communication module is powered vi
a the meter’s internal power supply.

g)

Communication must be ensured between the metering module and the data concentrator
module


5)

General Requirements

a)

The meter should store in non
-
volatile memory measurement data (profile and billing) and
non
-
measurement data (events and alerts).

b)

Values of active energy registers should be expressed in kWh with possible parameterization
of measurement precision to thre
e significant digits.

c)

The meter should store the register events in cyclical event buffers:

i)

network events (blackouts, voltage increases)


at least 120 items;

ii)

other events


at least 120 items.

d)

The memory size should make it possible to store data for a p
eriod of at least 63 most recent
days with the averaging period of 15 minutes for the active energy register in both directions.

e)

All devices should be new out of factory (not operated in production).

f)

Signing of the meter type and identification number must

be durable, unique and must enable
unequivocal identification of each meter in no
-
voltage status. If a meter is equipped with a di
s-
play, the meter’s number must be shown on it. If there is no display, a meter should report its
number under OBIS code


C.1
.0. Identification parameters should be readable electronically
remotely and locally.

g)

Indication of the software version of the devices and communication modules should be un
e-
quivocal and readable electronically remotely and locally.

h)

The meter should have

additional signing with a bar code along with attached three stickers
containing the signing of the meter (it should be possible to remove the stickers from the m
e-
ter case and reuse them by sticking them on a paper document) and its bar code in the Inte
r-
l
eaved 2 of 5 standard or equivalent:

i)

meter type


5 characters;

ii)

factory number


8 characters;

iii)

production date


2 characters;

iv)

control sum


1 character (or 0 if the sum is not calculated);

v)

The meter’s identification data should be visible after its instal
lation.

i)

The device should be ready for placement of fitter’s seals to prevent access to the device’s i
n-
ternal elements.


6)

Technical and quality parameters

a)

The meter should have active energy measurement
class at least C (according to MID) or class
0.5.

b)

The meter should have reactive energy measurement class of at least 1.

c)

The range of temperatures of the meter work should be at least:
-
40
o
C / +70
o
C.

d)

The meter’s case should fulfill requirements at least
for protection class IP 51.

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





21
/
27

e)

Nominal frequency for the meter is 50 Hz.

f)

Nominal voltage for the meter is 3x230V / 400V.

g)

Maximum current is I
max

6A.

h)

The meter should satisfy requirements of protection against lightning surges and network
overvoltages at the l
evel of 4 kV, for a voltage impulse of 1,2/50 microseconds according to IEC
62052
-
11

i)

The meter should have an internal real time clock maintained for at least 8 years.

j)

Accuracy of the built
-
in clock of the meter should not be worse than 1 second per 24 hou
rs.

k)

The source of time for the meter is the concentrator and, if communication bypasses a conce
n-
trator, then an indicated external IT system.

l)

The meter should stamp measurement data with an unverified time status in the event of:

i)

turning the meter on (unt
il the clock is synchronized);

ii)

loss of the possibility to synchronize time for 7 subsequent calendar days.

m)

The meter should make it possible to change firmware locally and remotely.


7)

Software

a)

The Contractor will deliver software for local operation, diagnosis and reporting of the meter
work, enabling full configuration, parameterization, diagnosis and reading of the measurement
data and events from the meter .

b)

The software for local operation
of the meters should make it possible to prepare configuration
files. Configuration files from an older version of the software should be possible to service in
newer releases.

c)

The software for local operation of the meters should enable export of measurem
ent data,
events and configurations from the meters to text files (TXT, CSV, XML) with a documented
structure ensuring data collection in the Central System.

d)

The Contractor will ensure at least for the duration of the guarantee, within the compensation
for

the scope of the order, access to current versions of software for local operation of the m
e-
ters, communication modules and local read
-
out systems if new software versions are r
e-
leased. The new software versions should support the devices previously bough
t by the client
from the supplier.

e)

The software for local operation of the meters should support interworking with the Windows
7 operating system.

f)

Technical documentation of the configuration and communication protocols will be provided
under the contract

in order to implement support of those protocols in the IT systems of the
Client.


VII.

DESCRIPTION OF REQUIREMENTS FOR THE CONCENTRATOR AND BALANCING
METER SET APPLICABLE TO THE CONCENTRATOR


1)

Operation of the meters

a)

The concentrator should automatically detect and address meters turned on within its opera
t-
ing range during less than 12 hours fr
om the moment of installation of a new meter.

b)

The concentrator should record at least the events of connecting and disconnecting a meter.
Each event should include at least:

i)

date and time of the operation;

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





22
/
27

ii)

operation type;

iii)

the meter’s serial number.

c)

The
concentrator should ensure two
-
way communication between the Central System and d
e-
vices connected to the concentrator, at least within the following scope:

i)

demands for reading data and events from meters;

ii)

changes to the meters’ configuration;

iii)

changes to
the meters’ software, including their communication modules (firmware);

iv)

messages connected with controlling a meter (e.g. switch on / off, power limitations);

v)

messages sent to / from the HAN network (communication with the driver of the HAN
network).

d)

The
concentrator should make it possible to read, on demand, measurement data and info
r-
mation about events from the supported devices:

i)

locally via the concentrator’s interface;

ii)

remotely via the Central System.

e)

The concentrator should start transmitting all the

events sent by meters in the automatic (i
n-
stantaneous) mode to the Central System in the period not longer than 1 minute.

f)

The concentrator should ensure synchronization of real time clocks in the meters.

g)

The concentrator should make available statistics
about communication quality independently
for each supported device.


2)

Communication

a)

The concentrator may be a free
-
standing device or one integrated with a balancing meter.

b)

Local communication with the data concentrator,
for local data readouts from the supported
devices, their configuration and diagnostic testing, should be possible via an optical link or
Ethernet/RJ45 or USB.

c)

The concentrator should support automatic detection and identification of a device by the Ce
n-
tr
al System. The concentrator should start communicating directly after connecting power
supply. The status of such communication being established and having been established
should be signaled.

d)

The concentrator should be equipped with a network card at least of the FastEthernet stan
d-
ard (RJ
-
45) and it should use it to communicate with the Central System, via TCP/IP protocol
(through a data transmission network).

e)

The concentrator should be equippe
d with RS485 interface, which may be used, e.g., to co
m-
municate with an external balancing meter.

f)

The concentrator should communicate with low voltage devices using PLC based on PRIME
specification, version 1.3.6 or newer (the specification can be found i
n section III of this A
p-
pendix).

g)

The concentrator should communicate with the Central System using the communication
standard described in section IV of this Appendix, and in particular the DCSML protocol.


3)

General Requirements

a)

All devices should be new out of factory (not operated in production).

b)

The concentrator should make it possible to store in non
-
volatile memory all the data and
events obtained from at least 500 devices read, for a 15
-
minute profile, at least
for the period
of most recent 63 days.

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





23
/
27

c)

The marking of type and identification number of a concentrator must be permanent, unique
and unambiguously identifiable for each device. It should be possible to read the identification
parameters via electronic tra
nsmission, both remote and local.

d)

The concentrator should be unambiguously marked with its software version and it should be
possible to read this information via electronic transmission, both remote and local.

e)

The concentrator should be additionally marke
d with a bar code and with three stickers sho
w-
ing the concentrator’s identification (it should be possible to unstick the stickers from the co
n-
centrator’s case and reuse them by sticking them onto a paper document) and its bar code in
the following format:

i)

concentrator type (5 digits);

ii)

serial number, unique for the given concentrator type (8 digits);

iii)

date of manufacturing the concentrator (2 digits);

iv)

checksum (1 digit)


calculated according to any algorithm or “0” instead of the checksum.


4)

Technical and
quality parameters

a)

The concentrator should operate at least within the following range of temperatures:
-
40
o
C /
+70
o
C.

b)

The concentrator should not contain any active cooling elements.

c)

The concentrator’s
case should fulfill requirements at least for protection class IP 51.

d)

The source of time for the concentrator is the Central System managing the measurement i
n-
frastructure.

e)

The concentrator should have an internal real time clock. The accuracy of the embed
ded clock
should be at least to 1 second per 24 hours.

f)

The concentrator should make it possible to change configuration and software locally and
remotely.

g)

It should be possible to restart the concentrator locally and remotely.


5)

Software

a)

The Contractor will provide software for local use and diagnostic testing of the concentrator a
l-
lowing for full configuration, diagnostic testing and reading measurement data and events
from the device.

b)

The software for local use of the concentra
tor should make it possible to export data from the
concentrator’s memory to files of a pre
-
defined format documented by the Contractor.

c)

The software should make it possible to create and restore back
-
up copies from the concentr
a-
tor‘s current configuration
.

d)

The use of software for local use of concentrators should require authorization.

e)

The Contractor will ensure, at least within the guarantee validity period and within the rem
u-
neration for the subject matter of the order, access to up
-
to
-
date versions of t
he software for
local use of the concentrator if newer versions of the software appear. The new software ve
r-
sions should support the devices previously bought by the client from the supplier.

f)

The software for local use of the meters should be adjusted to c
ooperate with Windows 7.


VIII.

OBIS CODES

OBIS codes should be identical to those used by ENERGA
-
OPERATOR S.A., i.e.:

1)

Data read for recipients
:

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





24
/
27

a)

Load profile data:

A+

Load profile

1.8.0

Energy profile

Ri+

Load profile

5.8.0

Energy profile

Rc
-

Load profile

8.8.0

Energy profile

U1

Load profile

32.7.0

Voltage profile

U2

Load profile

52.7.0

Voltage profile

U3

Load profile

72.7.0

Voltage profile

I1

Load profile

31.7.0

Current profile

I2

Load profile

51.7.0

Current profile

I3

Load profile

71.7.0

Current profile


b)

Billing data
:

Date and time

Billing

1.0.0

Historical data

Reset counter

Billing

0.1.0

Historical
data

A+ HIST T1

Billing

1.8.1*

Historical data

A+ HIST T2

Billing

1.8.2*

Historical data

A+ HIST T3

Billing

1.8.3*

Historical data

A+ HIST

Billing

1.8.0*

Summary

Pmax HIST

Billing

1.6.0*

Historical data

Pmax HIST CZAS

Billing

1.6.0*VV

Historical data

Ri+ HIST T1

Billing

5.8.1*

Historical data

Ri+ HIST T2

Billing

5.8.2*

Historical data

Ri+ HIST T3

Billing

5.8.3*

Historical data

Ri+ HIST

Billing

5.8.0*

Historical data

Rc
-

HIST T1

Billing

8.8.1*

Historical data

Rc
-

HIST T2

Billing

8.8.2*

Historical

data

Rc
-

HIST T3

Billing

8.8.3*

Historical data

Rc
-

HIST

Billing

8.8.0*

Historical data

U2h

Billing

83.8.6

Historical data

I2h

Billing

83.8.3

Historical data


KOD BLEDU [‘Error code’]

䉩B汩ng

䘮F

䥮獴慮瑡s敯us⁤慴

NR RESETU [‘Reset no.’]

䉩B汩ng

0⸱⸰

䥮獴慮瑡s敯us⁤慴

N删R䕓䕔N⁈ 協⁛S楳io物捡r
Reset no.’]

䉩B汩ng

0⸱⸰⁖


AKTUALNY CZAS [‘Current
time’]


0⸹⸱

䥮獴慮瑡s敯us⁤慴

AKTUALNA DATA [‘Current
date’]


0⸹⸲

䥮獴慮瑡s敯us⁤慴

䍚C匠婁M⸠MO

䉩B汩ng

0⸱⸲

䥮獴慮瑡s敯us⁤慴

N啍䕒N
LICZNIKA (“Meter
no.’]

䉩B汩ng

䌮ㄮC

䥮獴慮瑡s敯us⁤慴

TARYFA [‘Tariff’]

䉩B汩ng

0⸲⸲

䥮獴慮瑡s敯us⁤慴

䤱I䍈W

䉩B汩ng

31⸷.0

䥮獴慮瑡s敯us⁤慴

䤲I䍈W

䉩B汩ng

51⸷.0

䥮獴慮瑡s敯us⁤慴

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





25
/
27

I3 CHW

Billing

71.7.0

Instantaneous data

U1 CHW

Billing

32.7.0

Instantaneous data

U2 CHW

Billing

52.7.0

Instantaneous data

U3 CHW

Billing

72.7.0

Instantaneous data

A+ T1

Billing

1.8.1

Instantaneous data

A+ T2

Billing

1.8.2

Instantaneous data

A+ T3

Billing

1.8.3

Instantaneous data

A+

Billing

1.8.0

Instantaneous
data

Ri+ T1

Billing

5.8.1

Instantaneous data

Ri+ T2

Billing

5.8.2

Instantaneous data

Ri+ T3

Billing

5.8.3

Instantaneous data

Ri+

Billing

5.8.0

Instantaneous data

Rc
-

T1

Billing

8.8.1

Instantaneous data

Rc
-

T2

Billing

8.8.2

Instantaneous data

Rc
-

T3

Billing

8.8.3

Instantaneous data

Rc
-

Billing

8.8.0

Instantaneous data

Pmax+

Billing

1.6.0

Instantaneous data


2)

Data read for manufacturers

a)

Load profile data
:

A+

Load
profile

1.8.0

Energy profile

A
-

Load profile

2.8.0

Energy profile

Ri+

Load profile

5.8.0

Energy profile

Rc+

Load profile

6.8.0

Energy profile

Ri
-

Load profile

7.8.0

Energy profile

Rc
-

Load profile

8.8.0

Energy profile

U1

Load profile

32.7.0

Voltage
profile

U2

Load profile

52.7.0

Voltage profile

U3

Load profile

72.7.0

Voltage profile

I1

Load profile

31.7.0

Current profile

I2

Load profile

51.7.0

Current profile

I3

Load profile

71.7.0

Current profile


b)

Billing data
:

Date and time

Billing

1.0.0

Historical data

Reset counter

Billing

0.1.0

Historical data

A+ HIST T1

Billing

1.8.1*

Historical data

A+ HIST T2

Billing

1.8.2*

Historical data

A+ HIST T3

Billing

1.8.3*

Historical data

A+ HIST

Billing

1.8.0*

Summary

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





26
/
27

Pmax

HIST

Billing

1.6.0*

Historical data

Pmax HIST CZAS

Billing

1.6.0*VV

Historical data

A
-

HIST T1

Billing

2.8.1*

Historical data

A
-

HIST

Billing

2.8.0*

Summary

Ri+ HIST T1

Billing

5.8.1*

Historical data

Ri+ HIST T2

Billing

5.8.2*

Historical data

Ri+
HIST T3

Billing

5.8.3*

Historical data

Ri+ HIST

Billing

5.8.0*

Historical data

Rc
-

HIST T1

Billing

8.8.1*

Historical data

Rc
-

HIST T2

Billing

8.8.2*

Historical data

Rc
-

HIST T3

Billing

8.8.3*

Historical data

Rc
-

HIST

Billing

8.8.0*

Historical data

Ri
-

HIST

Billing

7.8.0*

Historical data

Rc+ HIST

Billing

6.8.0*

Historical data

U2h

Billing

1
-
1:83.8.6

Historical data

I2h

Billing

1
-
1:83.8.3

Historical data


KOD BLEDU [‘Error code’]

䉩B汩ng

䘮F

䥮獴慮瑡s敯us⁤慴

NR RESETU [‘Reset no.’]

䉩B汩ng

0⸱⸰

䥮獴慮瑡s敯us⁤慴

N删R䕓䕔N⁈ 協⁛S楳io物捡r
Reset no.’]

䉩B汩ng

0⸱⸰⁖


AKTUALNY CZAS [‘Current
time’]


0⸹⸱

䥮獴慮瑡s敯us⁤慴

AKTUALNA DATA [‘Current
date’]


0⸹⸲

䥮獴慮瑡s敯us⁤慴

䍚C匠婁M⸠.R

䉩B汩ng

0⸱⸲

䥮獴慮瑡s敯us⁤慴

N啍䕒N
LICZNIKA (“Meter
no.’]

䉩B汩ng

䌮ㄮC

䥮獴慮瑡s敯us⁤慴

TARYFA [‘Tariff’]

䉩B汩ng

0⸲⸲

䥮獴慮瑡s敯us⁤慴

䤱I䍈W

䉩B汩ng

31⸷.0

䥮獴慮瑡s敯us⁤慴

䤲I䍈W

䉩B汩ng

51⸷.0

䥮獴慮瑡s敯us⁤慴

䤳I䍈W

䉩B汩ng

71⸷.0

䥮獴慮瑡s敯us⁤慴

唱⁃䡗

䉩B汩ng

32⸷.0

䥮獴慮瑡s敯us⁤慴

唲⁃䡗

䉩B汩ng

52⸷.0

䥮獴慮瑡s敯us⁤慴

唳⁃䡗

䉩B汩ng

72⸷.0

䥮獴慮瑡s敯us⁤慴

䄫⁔1

䉩B汩ng

1⸸⸱

䥮獴慮瑡s敯us⁤慴

䄫⁔2

䉩B汩ng

1⸸⸲

䥮獴慮瑡s敯us⁤慴

䄫⁔3

䉩B汩ng

1⸸⸳

䥮獴慮瑡s敯us⁤慴



䉩B汩ng

1⸸⸰

䥮獴慮瑡s敯us
T慴a

剩⬠T1

䉩B汩ng

5⸸⸱

䥮獴慮瑡s敯us⁤慴

剩⬠T2

䉩B汩ng

5⸸⸲

䥮獴慮瑡s敯us⁤慴

Appendix 3 to the agreement form

List and Description of Deliverables

Procedure no.
P/_/AZU/000__/12



ENERGA

OPERATOR SA





27
/
27

Ri+ T3

Billing

5.8.3

Instantaneous data

Ri+

Billing

5.8.0

Instantaneous data

Rc
-

T1

Billing

8.8.1

Instantaneous data

Rc
-

T2

Billing

8.8.2

Instantaneous data

Rc
-

T3

Billing

8.8.3

Instantaneous data

Rc
-

Billing

8.8.0

Instantaneous data

Pmax+

Billing

1.6.0

Instantaneous data